InSync is a comprehensive file and data management product designed to provide fast and easy access to business data from multiple sources, including Db2 and IMS databases and WebSphere MQ.
Mainframe data can be copied and reformatted to match new layouts or to create files in a wide range of formats, including CSV, XML and JSON, for use in a non-mainframe environment.
To protect sensitive data, such as personal information, it can be automatically altered and anonymized when copying production files to development and testing environments.
Large volumes of realistic test data can be generated automatically using randomization or specific rules. This approach reduces effort, ensures that the data is suitable for all test scenarios, and avoids the use of real production data.
We will see some of the important options in insync with examples.
OPTION 1 - This option is used to browse the dataset. Type 1 and Press Enter.
Following screen will be displayed.
Dataset Name ===> 'IBMMF.TEST.INPUT' is the input data set which conatains data. This is the name of the dataset to be viewed.
Type within single quotes '...' the name of a dataset to be viewed, and leave the other fields at their default values as shown.
Note: If you wish InSync to automatically prefix dataset names with your TSO userid, omit the single quotes.
Some of the fields on the panel may already contain data, because InSync remembers most panel settings from one session to the next.
Press Enter. The first record in the dataset will be displayed.
you can display their hexadecimal values. Type HEX (or HEX ON) at the COMMAND ===> prompt, and then press Enter.
To revert to the character-only representation, type HEX OFF at the COMMAND ===> prompt, and then press Enter.
Press PF11 to scroll forward through the records in the dataset.
Press PF10 to scroll backward towards the first record.
Type FS (or FS ON) at the COMMAND ===> prompt, and then press Enter. “FS” stands for “full-screen”.
For example, suppose that you have this COBOL record layout defined as a member in a copybook library IBMMF.TEST.COPY(INRECORD).
Type within single quotes '...' the name of a dataset to be viewed, type YES for Use COBOL or PL/I layout to format display, and supply the details of the copybook member, also within single quotes.
Dataset Name ===> 'IBMMF.TEST.INPUT' is the input data set which conatains data. This is the name of the dataset to be viewed.
Use subsequent selection criteria ===> YES
Other dataset ===> "IBMMF.TEST.COPY(INRECORD)" - This pds contains the copy book
Press Enter. The first record in the dataset is displayed
FORMAT - Code letters define data storage format.
Format codes Meanings:
Code | COBOL equivalents | PL/I equivalents |
---|---|---|
B | BINARY, COMP, COMP-4 | BINARY, OFFSET |
C | DISPLAY | CHARACTER, PICTURE |
P | COMP-3, PACKED-DECIMAL | DECIMAL |
Z | DISPLAY (zoned decimal) | - |
POS 1st digit - Number of display characters used by field.
POS 2nd digit - Start position of field within record.
DATA - Record in the dataset.
To view as many records as will fit on the screen, with each record occupying a single line, use the TFORMAT (or TFORMAT ON) command. “TFORMAT” stands for “tabular format”.
To return to single-record display, use the TFORMAT OFF command.
Navigation in formatted mode is exactly the same as in unformatted mode.
To display this | In single-record displays, use | In multi-record displays, use |
---|---|---|
Previous record(s) | PREVIOUS (PF10) | UP (PF7) |
Next record(s) | NEXT (PF11) | DOWN (PF8) |
Start of file | PREVIOUS MAX | UP MAX |
End of file | NEXT MAX | DOWN MAX |
Previous data in current record(s) | UP (PF7) | LEFT (PF10) |
Next data in current record(s) | DOWN (PF8) | RIGHT (PF11) |
Start of current record(s) | UP MAX | LEFT MAX |
End of current record(s) | DOWN MAX | RIGHT MAX |
Press PF3 return from browsing the data to the Dataset Specification panel. Press PF3 agin, to return from there to the Primary Options menu.
We are planning to create a seperate chapter to discuss each options in INSYNC. We will add it soon.
If you have any doubts or queries related to this chapter, get them clarified from our Mainframe experts on ibmmainframer Community!