Mainframe Expected Input

IBM z/OS Qualification Path

IBM i / AS/400 Qualification Path

Micro Focus Visual COBOL Qualification Path

1. Direct files: deliver COBOL programs, copybooks, project files, build configuration, compiler directives and runtime configuration from SCM or filesystem export.
2. DBMS: deliver embedded SQL context, SQL/DDL, schemas, migration scripts and connection configuration when they identify managed database objects.
3. Data stores: deliver indexed/sequential file mappings, record definitions, runtime environment files and logical-to-physical path configuration.
4. Operations: deliver launch scripts, scheduler definitions, transfer scripts and environment files that start or orchestrate COBOL programs.

Micro Focus ACUCOBOL-GT Qualification Path

1. Direct files: deliver COBOL programs, copybooks, ACU-specific configuration, compiler directives and runtime files from SCM or filesystem export.
2. Runtime: include indexed-file configuration, file aliases, environment files, runtime libraries and deployment scripts.
3. DBMS and data stores: deliver SQL/DDL, database scripts, indexed/sequential file mappings and record definitions.
4. Unsupported context: identify screen/UI definitions separately and validate parser behavior on a small representative sample.

Micro Focus RM/COBOL Qualification Path

1. Direct files: deliver COBOL programs and copybooks as individual text files, preserving names, folders, source format and encoding.
2. Compiler context: deliver compiler directives, copybook search paths, build scripts and runtime configuration.
3. Data context: deliver database scripts, indexed/sequential file mappings, record layouts and environment files.
4. Operations: deliver run scripts and scheduler definitions; do not request z/OS JCL or PDS dumps by default.

Micro Focus COBOL-IT Qualification Path

1. Direct files: deliver COBOL programs, copybooks, project/build files, compiler directives and runtime configuration.
2. Compatibility: validate Micro Focus-style directives, copybook resolution, source format and unsupported syntax on a representative sample.
3. DBMS and data stores: deliver SQL/DDL, database scripts, file mappings, record layouts and environment files.
4. Operations: deliver scripts, schedulers and transfer definitions that invoke COBOL programs.

Fujitsu NetCOBOL Qualification Path

1. Direct files: deliver NetCOBOL programs, copybooks, project/build files and compiler option files.
2. Runtime: deliver runtime libraries, deployment scripts, environment files and platform-specific configuration.
3. DBMS and data stores: deliver database definitions, SQL/DDL, file mappings and record layouts.
4. Validation: test Fujitsu-specific syntax, preprocessing and screen/UI usage on a representative sample before confirming scope.

GnuCOBOL / OpenCOBOL Qualification Path

1. Direct files: deliver COBOL programs, copybooks, build scripts, compiler flags and preprocessing scripts.
2. Build context: include makefiles, shell scripts, package scripts and environment variables used to compile or run the application.
3. DBMS and data stores: deliver SQL/DDL, database scripts, file mappings and record layouts.
4. Validation: confirm source compatibility, copybook conventions and extensions on a representative sample before confirming scope.

Veryant isCOBOL Qualification Path

1. Direct files: deliver isCOBOL programs, copybooks, project/build files, compiler options and runtime configuration.
2. Runtime: include runtime libraries, GUI/screen configuration, environment files, deployment scripts and launch commands.
3. DBMS and data stores: deliver database definitions, SQL/DDL, file mappings, record layouts and environment files.
4. Validation: validate isCOBOL-specific syntax and GUI/screen dependencies on a representative sample before confirming coverage.

Other Unsupported Platforms

Priority 2

• IBM z/TPF COBOL
• IBM z/VSE COBOL
• IBM z/VM COBOL
• IBM COBOL for AIX
• HPE NonStop COBOL / Tandem COBOL85 / ECOBOL
• HPE NonStop Pathway / SCREEN COBOL
• OpenVMS COBOL
• Unisys ClearPath MCP COBOL
• Unisys ClearPath OS 2200 COBOL
• Stratus VOS / OpenVOS COBOL
• HP 3000 / MPE COBOL
• Bull / GCOS COBOL
• Generic Micro Focus COBOL

Priority 3

• IBM MVS / OS/390 legacy COBOL
• Fujitsu / Siemens BS2000 COBOL
• ICL VME COBOL
• NEC ACOS COBOL
• Hitachi VOS3 COBOL
• Wang VS COBOL
• Data General AOS/VS COBOL
• Prime / PRIMOS COBOL
• NCR / AT&T UNIX COBOL
• Honeywell / Multics COBOL
• DEC PDP / RSTS / RSX COBOL
• Microsoft COBOL / MS-COBOL
• Realia COBOL / CA-Realia
• Liant RM/COBOL
• TinyCOBOL

Extract IBM z/OS COBOL and Copybooks

1. Confirm the compiler and dialect, fixed/free source format, compiler options and whether the delivered COBOL is native source or generated code. Prefer the native source when a generator such as Telon, Pacbase, Adelia or CA Gen is used.
2. For fixed-format source, confirm the indicator column and whether columns 73–80 are sequence data or executable content. Use separate analysis units when source groups require different column settings.
3. Document how load-module names are derived: from PROGRAM-ID, source member names or a separate build/link-edit convention.
4. List the COBOL source PDS/PDSE libraries and every copybook or DCLGEN PDS/PDSE library separately.
5. Run one IEBPTPCH job for the COBOL program library.

   //PTPCHCOB JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=IEBPTPCH
   //SYSPRINT DD SYSOUT=*
   //SYSUT1   DD DSN=<COBOL.SOURCE.PDS>,DISP=SHR
   //SYSUT2   DD DSN=<OUTPUT.COBOL.DUMP>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(10,10),RLSE),DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
   //SYSIN    DD *
    PUNCH TYPORG=PO
   /*

6. Run one IEBPTPCH job for each copybook library.

   //PTPCHCPY JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=IEBPTPCH
   //SYSPRINT DD SYSOUT=*
   //SYSUT1   DD DSN=<COPYBOOK.SOURCE.PDS>,DISP=SHR
   //SYSUT2   DD DSN=<OUTPUT.COPYBOOK.DUMP>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(5,5),RLSE),DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
   //SYSIN    DD *
    PUNCH TYPORG=PO
   /*

7. Verify the dump contains the expected member banner, normally VMEMBER NAME, then deliver the COBOL dump with predefined PDS type COBX and the copybook dump with predefined PDS type CPYX.
8. If source comes from Endevor, Changeman, Panvalet, Librarian or Git, export one text file per member instead and keep COBOL and copybooks in separate folders.
9. Keep all copybooks available to every analysis package containing COBOL programs, and record the copybook search order when duplicate member names exist.
10. Keep enough JCL and transaction context to distinguish batch COBOL Program objects from transaction-mode COBOL Program TP objects in CAST Imaging.

Download the sample PDS/PDSE extraction JCL

Extract IBM z/OS JCL and PROC

1. Identify job libraries, procedure libraries, JCLLIB/INCLUDE libraries and utility control-card libraries. Record the library search order.
2. Scan the source for JOB and PROC cards, EXEC PGM=, procedure calls such as EXEC PROCNAME, INCLUDE MEMBER=, and DD statements that reference control-card members.
3. Build lists of called programs, procedures and includes. Obtain every missing application PROC or INCLUDE member; unresolved technical utilities can be classified after analysis.
4. Run IEBPTPCH on the job JCL library, verify the member banner, then deliver the dump with predefined PDS type JCLX.

   //PTPCHJCL JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=IEBPTPCH
   //SYSPRINT DD SYSOUT=*
   //SYSUT1   DD DSN=<JCL.SOURCE.PDS>,DISP=SHR
   //SYSUT2   DD DSN=<OUTPUT.JCL.DUMP>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(5,5),RLSE),DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
   //SYSIN    DD *
    PUNCH TYPORG=PO
   /*

5. Export PROC, INCLUDE and control-card members as direct .prc, .inc, .mbr and .ctl files, or use separate PDS dumps only when project-specific PDS types are configured.
6. Keep scheduler JCL, utility JCL and application JCL grouped by application or subsystem. When COBOL is split across analysis packages, include the complete related JCL set in each package so cross-analysis links can be resolved.
7. After the first analysis, review unknown procedures, external programs, launchers and site utilities. Configure application-level AdvancedJCL.xml rules when missing procedures or parameters carry program names, or when utility DD cards need explicit read/write semantics.

Download the sample JCL/PROC library extraction job

Recommended direct-file layout:
jcl/jobs/*.jcl
jcl/procedures/*.prc
jcl/includes/*.inc
jcl/control-cards/*.ctl

Extract IBM z/OS Other Languages

1. Inventory each language family: PL/I, Assembler, Easytrieve, REXX, CLIST, SAS, Focus, NOMAD, Natural or site-specific languages.
2. Export from SCM as direct text files when possible, preserving member name, language and extension.
3. If the source is stored in PDS/PDSE, run one IEBPTPCH dump per language family.

   //PTPCHSRC JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=IEBPTPCH
   //SYSPRINT DD SYSOUT=*
   //SYSUT1   DD DSN=<LANGUAGE.SOURCE.PDS>,DISP=SHR
   //SYSUT2   DD DSN=<OUTPUT.LANGUAGE.DUMP>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(5,5),RLSE),DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
   //SYSIN    DD *
    PUNCH TYPORG=PO
   /*

4. Do not mix COBOL, copybooks, Assembler macros and PL/I includes in the same dump.
5. When a project-specific PDS configuration is agreed, verify the generated dump uses the configured member banner before delivery.

Example folder delivery:
other-languages/pli/*.pli
other-languages/asm/*.asm
other-languages/easytrieve/*.ezt
other-languages/rexx/*.rexx

Extract IBM z/OS CICS

1. Scan COBOL and other application source for EXEC CICS to identify the transactional scope and the programs that must be delivered.
2. Find BMS map source by searching for DFHMSD, then extract the complete BMS/map PDS or SCM package.
3. Run IEBPTPCH for the BMS library, verify the member banner, then deliver the dump with predefined PDS type BMSX.

   //BMSCOPY  JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=IEBPTPCH
   //SYSPRINT DD SYSOUT=*
   //SYSUT1   DD DSN=<CICS.BMS.SOURCE.PDS>,DISP=SHR
   //SYSUT2   DD DSN=<OUTPUT.BMS.DUMP>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(5,5),RLSE),DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
   //SYSIN    DD *
    PUNCH TYPORG=PO
   /*

4. Export CICS CSD definitions with the CICS system definition utility, typically DFHCSDUP.

   //CSDLIST  JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=DFHCSDUP
   //STEPLIB  DD DSN=<CICS.SDFHLOAD>,DISP=SHR
   //DFHCSD   DD DSN=<CICS.DFHCSD>,DISP=SHR
   //SYSPRINT DD DSN=<OUTPUT.CICS.CSD>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(5,5),RLSE),DCB=(RECFM=FB,LRECL=133,BLKSIZE=0)
   //SYSIN    DD *
    LIST ALL
   /*

5. Deliver CSD output containing the relevant DEFINE TRANSACTION, DEFINE PROGRAM, DEFINE TDQUEUE, DEFINE FILE and DEFINE MAPSET resources as direct .csd or .cics files.
6. Cross-check that COBOL programs referenced by CICS transactions are included in the COBOL extraction.

Download the sample CICS CSD extraction JCL

Extract IBM z/OS IMS

1. Scan application source for EXEC DLI, CALL "CBLTDLI" USING, ENTRY DLITCBL USING and IMS transaction calls to identify the IMS scope.
2. Extract PSB source with IEBPTPCH, verify the member banner, and deliver it with predefined PDS type PSBX.

   //PSBCOPY  JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=IEBPTPCH
   //SYSPRINT DD SYSOUT=*
   //SYSUT1   DD DSN=<IMS.PSB.SOURCE.PDS>,DISP=SHR
   //SYSUT2   DD DSN=<OUTPUT.PSB.DUMP>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(5,5),RLSE),DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
   //SYSIN    DD *
    PUNCH TYPORG=PO
   /*

3. Extract DBD source with IEBPTPCH, verify the member banner, and deliver it with predefined PDS type DBDX.

   //DBDCOPY  JOB CLASS=A,MSGCLASS=X
   //STEP01   EXEC PGM=IEBPTPCH
   //SYSPRINT DD SYSOUT=*
   //SYSUT1   DD DSN=<IMS.DBD.SOURCE.PDS>,DISP=SHR
   //SYSUT2   DD DSN=<OUTPUT.DBD.DUMP>,DISP=(NEW,CATLG,DELETE),
   //            SPACE=(CYL,(5,5),RLSE),DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
   //SYSIN    DD *
    PUNCH TYPORG=PO
   /*

4. Export MFS format source as direct .mfs files unless a project-specific PDS type is configured.
5. Export IMS/DC transaction macros containing APPLCTN and TRANSACT statements as .tra.
6. Confirm that COBOL programs referenced by PSB, transaction and JCL context are included.

Extract IBM z/OS DBMS Input

1. Scan application source for EXEC SQL, DL/I calls and vendor-specific database statements to identify every DBMS in scope.
2. For Db2 or Oracle, export schema DDL, tables, views, indexes, aliases, stored procedures and grants as .sql or .ddl, and include DCLGEN copybooks.
3. For IMS DB, use the IMS extraction path: PSB PSBX, DBD DBDX, and related COBOL copybooks.
4. For IDMS, Datacom, ADABAS or other DBMS, collect schema/configuration exports plus the programs and copybooks using them.
5. Group delivered files by DBMS and keep database identifiers consistent with those used by application source.

Example delivery:
db2/schema/customer.ddl
ims/dbd/DBD dump delivered as DBDX
ims/psb/PSB dump delivered as PSBX

Extract IBM z/OS Data-Store Input

1. Inventory the non-DBMS storage families in scope: VSAM KSDS/ESDS/RRDS/LDS, GDGs, QSAM/GSAM, sequential datasets and PDS/PDSE libraries.
2. Collect all JCL jobs and procedures containing the relevant DD, DSN, DISP, DCB and generation references.
3. Export IDCAMS DEFINE/ALTER/DELETE, GDG definitions, sort/control cards and other utility definitions as readable text.
4. Preserve dataset qualifiers, cluster names, generation conventions and application grouping during transfer.
5. Keep catalog listings or storage reports as supporting context; do not use them as substitutes for the JCL and control definitions.

Example delivery:
data-stores/vsam/idcams-definitions.ctl
data-stores/gdg/generation-definitions.ctl
data-stores/jcl/dataset-dd-statements.jcl
data-stores/inventory/catalog-listing.txt

Extract IBM z/OS Schedulers and Operations

1. Identify scheduler products in scope: CA-7, Control-M, TWS, ESP or a site-specific scheduler.
2. Run the scheduler export/list command recommended by the tool owner.
3. Export job definitions, calendars, dependencies, triggers, variables and run conditions.
4. Include FTP, NDM, Co:Z or equivalent transfer definitions and print/output management definitions such as StreamWeaver when they participate in application flows.
5. Deliver product-native text or XML files, keeping naming conventions stable.
6. Cross-check scheduler job names against the delivered JCL members.

Example delivery:
scheduler/control-m/application.xml_controlm
scheduler/ca7/application.ca7
scheduler/tws/application.str
operations/file-transfer/*.txt

Extract IBM i COBOL/400

1. List source physical files containing COBOL members and copy/include members.
2. Export each member as a text source file with member name and member type preserved.
3. Separate COBOL programs from copy/includes in different folders.
4. Deliver source with clear extensions such as .cbl, .cob, .cpy or the project convention.
5. Attach compiler options, copybook paths and library names used for compilation.

Example delivery:
ibmi/cobol/programs/CUSTUPD.cbl
ibmi/cobol/copybooks/CUSTREC.cpy
ibmi/build/compiler-options.txt

Extract IBM i CL / CLP

1. Identify CL/CLP source members, job descriptions and run commands.
2. Export command language members as direct text files.
3. Export job descriptions or run chains as text reports when possible.
4. Keep CL/CLP separate from COBOL source.
5. Confirm analyzer or extension coverage before treating them as batch input.

Example delivery:
ibmi/commands/*.clp
ibmi/jobs/job-descriptions.txt
ibmi/runtime/run-commands.txt

Extract IBM i DBMS Input

1. Export SQL DDL for Db2 for i schemas, tables, views, indexes, aliases and routines.
2. Collect embedded SQL and database configuration used by COBOL or other application source.
3. Separate database definitions from application source.
4. Preserve schema, library and object names.

Example delivery:
ibmi/db2/schema/*.sql
ibmi/db2/routines/*.sql

Extract IBM i Data-Store Input

1. Export DDS source for physical and logical files.
2. Collect record formats, access paths and library/object naming context.
3. Include CL commands or build documentation that creates, overrides or assigns files.
4. Keep physical and logical file definitions in separate folders.

Example delivery:
ibmi/dds/physical-files/*.pf
ibmi/dds/logical-files/*.lf
ibmi/data-stores/library-inventory.txt

Extract IBM i Schedulers and Operations

1. List IBM i native job schedules and external scheduler products.
2. Export schedule entries, calendars, command chains and transfer scripts.
3. Deliver the exported definitions as direct text/XML files.
4. Cross-check scheduled commands against delivered CL/CLP and COBOL programs.

Example delivery:
ibmi/scheduler/job-schedule.txt
ibmi/operations/transfer-scripts/*.txt