Operations › Z/VSE Environments › Key to Z/VSE JCL

Key to Z/VSE JCL

• nnnnnnnn — The UPSI byte settings appropriate to the IDMSOPTI module, which you have linked with CA IDMS Schema Mapper, and to the method you are using to access CA IDMS--Local Mode or central version (CV).
• 00D — The unit address of your punch device.
• 00E — The unit address of your printer device.
• schemapr.work. and file — The name of the scratch/work file that is used for Parameter File input and Transfer File output.
• volser — The volume serial number or generic assignment of the disk volume on which the file, specified in the previous statement, resides.
• starttrack — Available disk extent on the work disk volume (1 to 6 digits).
• #tracks — Sufficient space for the input Parameter File (1 to 6 digits). Ten tracks is usually sufficient space.
• your.dict.ddldml — The data set containing the DDLDML area of the dictionary containing the description of the desired subschema.
• your.loadlib — The data set name of the core image library into which you downloaded CA IDMS Schema Mapper.
• idms.loadlib — The data set name of the core image library in which your DMCL and subschema reside.
• DBMS.sublib and IDMS.sublib — The sublibrary name of the Z/VSE library specified in the previous file name.
• your.sysctl.file — The file name of your SYSCTL file.
• SYSnnn — The programmer logical unit for the file specified in the previous DLBL statement.
• dmcl-name — Specify the name of the DMCL that should be used when accessing the dictionary.

Note: When running in local mode, the job control for the dictionary canbe defined in standard labels or partition standard labels instead of in stream.

The size parameter in this JCL specifies the PPA space needed for CA IDMS Schema Mapper and CA IDMS program storage. The remainder of the partition will be used for GETVIS storage.

The amount of GETVIS storage required depends on the size of the schema/subschema you are mapping. If you are mapping a small schema or subschema (with less than 40 records), you need about 700K; a medium-sized schema or subschema (40 to 100 records) requires about 1700K.

The files in this JCL can be ASSGNed to any device type on the system that has or that can receive the data for CA IDMS Schema Mapper to operate. (There is full device independence.) If you use disk, DLBL and EXTENT JCL must be provided either in the above JCL or in standard labels. If you use labeled tape, TLBL JCL must be included in the above JCL. Here are the DLBL/TLBL names for the corresponding file ASSGN control statements:

DIAGRAM SYS010
SCRATCH SYS012
STATFILE SYS013
XREF SYS014

These are the names for tape; disk names will be truncated to the first seven characters as necessary. Also, CA IDMS Schema Mapper writes the SCRATCH file; then reads it.

If you do not want a dump when a CA IDMS Schema Mapper job terminates abnormally, you can include a // OPTION NODUMP control statement in the JCL. If you do not use // OPTION NODUMP or if you choose to include // OPTION DUMP or // OPTION PARTDUMP, a dump will be produced for an abend in addition to any diagnostic messages from CA IDMS Schema Mapper and the Pascal run-time modules.