Operations › z/OS Environments › Key to z/OS JCL

Key to z/OS JCL

• #K — The amount of memory needed to execute CA IDMS Schema Mapper, in kilobytes. CA IDMS Schema Mapper needs about 250K for program storage. If you are mapping a small schema/subschema (with less than 40 records), you need an additional 700K; a medium-sized schema/subschema (40 to 100 records) requires an additional 1700K.
• idms.custom.loadlib — The data set name of the library containing customized CA IDMS modules.
• idms.cagjload — The data set name of the load library containing the vanilla CA IDMS executable software.
• /*OUTPUT (JES2) and //*FORMAT (JES3) — These statements are needed only in z/OS environments for proper handling of page ejects in the DIAGRAM output. With these statements, the DIAGRAM will be in a separate SYSOUT data set from the rest of the output.
• idms.sysctl — The data set name of the CA IDMS system control file. This is used to request central version (CV) operation.
• dictdb — The DDNAME of the CA IDMS dictionary being accessed. DICTDB is the default. Your site may have changed the DDNAME in the dictionary DMCL. This statement is needed if running local mode.
• idms.dictionary — The data set name of the dictionary that contains the schema or subschema information.
• SYSJRNL — This statement is needed if running local mode.
• a — The appropriate SYSOUT class for your installation.
• schemapr.parm and transfer.file — The data set name of the Transfer File (output file) to which parameter statements are to be written.
• ds — For z/OS JES2 environments, replace with (a,,DIAG). Otherwise, use a. See a above for both.
• disk — The unit address of the disk drive you want to use for the CA IDMS Schema Mapper execution file or a generic assignment to indicate a disk drive allocation.
• schemapr.stats and input.file — The data set name of the statistics file that was created by CA IDMS/DB Analyzer
• schemapr.parm and input.file — The data set name of the file containing the parameter statements to be used as input. This can be either a Transfer File created by CA IDMS Schema Mapper during a previous run or a user-created file.

You must place a JOB card at the beginning of this JCL.

CA IDMS Schema Mapper writes the SCRATCH file and later reads it.

Instead of defining an input file (that contains parameter statements) with the SYSIPT statement in the preceding JCL, you can use this SYSIPT statement:

//SYSIPT DD *

followed by the parameter statements to be used as input.

The statistics file is needed only if you request one of the statistics fields in your output. If you do not request one of the statistics fields in your output, STATFILE can be DUMMY or undefined.

CA IDMS Schema Mapper treats a column of the diagram as a single logical page with no forced page ejects. In a z/OS environment, a page eject is usually created automatically for any SYSOUT file when the data does not include a page eject. This prevents CA IDMS Schema Mapper from writing more than 60 lines on a page. You need to include statements to suppress automatic page ejects.

The various releases of JES use different statements to suppress the automatic page eject. The sample JCL includes both JES2 and JES3 a statement for suppressing page ejects. Before using these statements, you need to check that their formats are appropriate for your environment.

You must use the following SYSIDMS statement:

 //SYSIDMS DD*

followed by SYSIDMS parameters. This file is always required for the CA IDMS physical environment parameter input to be read. For instance, DMCL=xxxxxxxx must be specified, where xxxxxxxx is the name of the specific DMCL.