Providing Source Code for Initial CM evolveIT Discovery

When providing your Cobol system assets to us for discovery and creation of your initial CM evolveIT repository, please consider the following:

Please zip your files and upload to https://spaces.hightail.com/uplink/cmfirsttech​

Format

Source code should be provided as individual source files in standard Windows 7-bit ASCII text format zip’ed as a Microsoft Windows directory.  Please note that when using FTP from the mainframe where an EBCDIC to ASCII conversion is performed, take care that no characters are translated into Control Z.

Source

Please supply source for all of the following that are assets of your system.  If you are not aware of the full interaction set, we can complete the discovery and then tell you what source code is missing.  (Keep in mind that CM evolveIT will identify missing assets by finding unresolved references in the source code assets provided.  It is possible that each new set of source code provided may contain references to additional missing source code assets.)

• COBOL Program Source
• COBOL Copybook Source, Dclgen Copybooks
• Schema Source – DB2 DDL
• Mapsets (i.e. BMS)
• JCL Source
• JCL Procs
• Parm Cards
• CICS
• CSD extract using IBM standard program DFHCSDUP
• Supply parms to DFHCSDUP, then use subroutines from IBM (DFH$FORA) to put the format into one-line output.  The JCL needed to do this is below.
• The file sent to CM evolveIT will be limited to certain records, as the CICS file alone can have duplicates. 

Explanation of this can be found in the CICS/TS 4.2 manual Resource Definition Guide at IBM.COM

A summary explanation of the record layout in this file appears in “CICS File Extract format” below.

Special note* The output dataset must have these attributes.

Organization  . . . : PS 

Record format . . . : F  

Record length . . . : 1536

Block size  . . . . : 1536

CICS Resources

How to limit the number of resources that need to be extracted.

GRPLIST is a CICS system initialization parameter that will contain up to four “lists” of groups that contain the resources that we may need to look at.  We only want to extract the resources from the groups that are used by the application.

The resources that we are interested in are:  programs, files (FCT), queues (TDQ), transactions (PCT), and mapsets.  We can include an input dataset pointed to by the CRFINPT DD that will control which resources are extracted.  CRFINPT is a sequential file containing 80-byte records. Each record contains one object or keyword to be cross-referenced. The CRFINPT file should contain the following entries (one per line):

PROGRAM

TRANSACTION

FILE

TDQ

MAPSET

The JCL sample below can be used to extract the data once you have narrowed down the groups you want to use.

//JOBCARD  JOB MSGCLASS=H,CLASS=A,NOTIFY=&SYSUID                        

//*-----------------------------------------------

//*CSD EXTRACT                         

//*-----------------------------------------------

//EXTRACT  EXEC PGM=DFHCSDUP,

//         PARM=’CSD(READONLY)’                        

//SYSPRINT DD SYSOUT=*                                           

//CDBOUT   DD SYSOUT=*                                  

//CRFOUT   DD SYSOUT=*                                  

//CRFINPT  DD DSN=<your input dataset>,DISP=SHR

//*                                                              

//STEPLIB  DD DSN=<cicshlq>.SDFHLOAD,DISP=SHR                 

//DFHCSD   DD DSN=<your CSD dataset>,DISP=SHR       

//SYSOUT   DD *                                                  

//FOROUT   DD DSN=<your output dataset>,DISP=SHR                  

//SYSIN    DD *                                                   

  EXTRACT GROUP(program group) USERPROGRAM(DFH0FORC) OBJECTS

  EXTRACT GROUP(FCT group) USERPROGRAM(DFH0FORC) OBJECTS

  EXTRACT GROUP(TDQ group) USERPROGRAM(DFH0FORC) OBJECTS

  EXTRACT GROUP(PCT group) USERPROGRAM(DFH0FORC) OBJECTS

  EXTRACT GROUP(mapset group) USERPROGRAM(DFH0FORC) OBJECTS

/*

//

 NOTES: 

1.     The FOROUT dataset must have a record size of 1536

2.     The USERPROGRAM can be DFH$FORA for assembler, DFH0FORC for COBOL, and DFH$FORP for PL/I.

3.     The EXTRACT statement can also use LIST(listname) to get all of the groups in the list

4.     The CRFINPT dataset DCB parameters must be DSORG=PS, RECFM=F, LRECL=80, and BLKSIZE=80.

Structure

Please divide the files into named directories for each of the file types described above and zip each group at the directory level.   If you have multiple source sets of any component type, please provide a separate directory for each set.  (Copybook1, Copybook2)

Other Information

Please write a few words as a TXT or DOC that explain the directory structure that you are providing.

Transfer

We can accept ZIP files up to 10MB.  If however, you have larger sets of source code assets, we can supply an FTP location where you can upload your source code.  (For security reasons we suggest that most customers use our FTP option.

Commands for FTP of multiple members from a PDS:
 
To transfer multiple members of a PDS and assign the member name as the filename on the target server directory, the following FTP control commands are required.
 
CD:  Change directory command to set the target server directory name for the transfer.
Syntax:  CD \your\target\directory\name
LCD:  Local Change Directory command to identify the PDS name for mass transfer.
Syntax:  LCD YOUR.PDS.NAME
MPUT:  Multiple Put command to specify mass transfer of members in the PDS.  (Asterisk denotes transfer of all members in the PDS.)
Syntax:  MPUT (*)

Example:

CD \Your\Target\Directory

LCD YOUR.PDS.NAME

MPUT (*)

This will transfer each member of the PDS to the server as individual text files.

CICS File Extract format

The file extracted from CICS using the instructions above is expected to contain records formatted according to the following rules:

Record Type

The first 4 characters of each line define the CICS item type defined on the line. This in turn defines the format of the line (defined in the following tables)

File Items

Mapset Items

Program Items

CICS Queue Items

CICS Transaction Items