IDMS to Power i

COBOL KeePIR

for IDMS and DC to the iSeries

Technical Product Overview IDMS and DC to NATIVE ILE COBOL

PIR Group presents COBOL KeePIR for IDMS and DC

PIR Group Inc. presents its COBOL KeePIR for IDMS DC to iSeries ILE COBOL and the iSeries Universal DataBase conversion utility. This utility will convert mainframe online programs from IDMS DC to fully structured native ILE COBOLprograms. The utility will also replace the IDMS data base manager with the iSeries data base manager. The tool provides a highly automated, low risk conversion.

GENERAL FEATURES:

• The utility generates logic to handle dialog program navigation and flow;
• The tool will support global records, scratch areas, and multiple page maps;
• All comments contained in the original code appear in the same location in the converted program;
• COBOL data-names generated by the utility are extensions of existing field-names found in the program;
• All copybooks are converted and retain the same identity;
• MVS or DOS Job Control Language gets converted to iSeries Control Language

SCREEN/PROGRAM FEATURES:

• Converts the screen definition into native iSeries Data Display Specifications;
• Translates DC attribute setting into usage of indicators to manage attributes on the iSeries
• MODIFY MAP is replaced with a move of the DFLD to build the screen buffer;
• MAP OUT is replaced with the following:

Load the Display file screen buffer from the map work area

Write the screen record

• MAP IN is replaced with the following

Read the screen record;
Load the map work area from the Display file screen buffer

• IDMS TRANSFER CONTROL converts to a return to the PIR controlling program and then invokes theprogram passing control to;
• DC RETURN converts to a return to the PIR controlling program which determines next program to invoke
• DC LINK gets converted to a program call;

IDMS I/O to iSeries UDB FEATURES:

• Creates iSeries DDS for physical files from IDMS record descriptions;
• Creates iSeries DDS for logical files from IDMS set descriptions;
• A foreign key per each IDMS member is created for each physical file, thus allowing the ability of maintaining the IDMS relationship of set, owner, member;
• While COBOL permits field names up to 30 characters, the iSeries permits names only up to 10 characters. When creating the DDS data elements the KeePIR tool adheres to the following in order to reduce the name to a max of 10 characters:
   Remove hyphens from the field name;
   Remove all vowels;
   Truncate from the right

Note: The source used for the creation of the DDS physical and logical records is the IDD or Integrated Data Dictionary of IDMS.

• A COBOL copybook is generated duplicating the structure provided by IDMS via the copy IDMS statement;
• Data load programs are created to migrate the data from the IDMS database into the newly created AS400Universal Data Base;
• In the COBOL applications the following main IDMS I/O statements are converted:  COMMIT & FINISH
   CONNECT & DISCONNECT
   ERASE

 FIND & FIND CURRENT  GET
 MODIFY
 ALL TYPES of OBTAINS  READY

 ROLLBACK  STORE

• The IDMS status area is maintained from the AS400 Return Codes

PIR Group/COBOL KeePIR FEATURES NOT SUPPORTED:

• 3270 data streams

AREAS REQUIRING MANUAL INTERVENTION:

• Certain uses of BLL Cells
• JCL created by the Cobol program
• EASYTRIEVE

• DOS/VSE $LST Cards
• Assembler programs
• C programs
• BMS paging options used on screens
• Light Pen & Bar Coding functionality
• Some areas of “Report Writer” programs