
Using Job Control Language (JCL)
User Reference
Connectivity Systems, Inc.—Copyright © 2006
Use Pursuant to Company Instructions
1-39
BIM-EPIC Job Control Language
Using Job Control Language (JCL)
Description BIM-EPIC changes the way you use job control language (JCL) and
offers many enhancements to standard VSE job controls. However,
BIM-EPIC may require some changes in order to function properly.
Physical Input/
Output Control
System
Programs that use physical input/output control systems (PIOCS) cause
conflicts with tape and disk management programs.
Physical IOCS (PIOCS) programs can cause conflicts because they often
do not follow most logical IOCS program conventions. For example,
PIOCS programs perform pre-open checking to determine the type of
device to use to process a dataset before the dataset can be opened or
before BIM-EPIC can make the assignment. Most PIOCS programs do
not update the DTF with block size, record size, record count, and address
of the last record written. Therefore, BIM-EPIC cannot find the necessary
information describing the dataset at end-of-volume/extent or close.
However, processing controlled datasets with PIOCS is not difficult. It
requires some special definitions in the JCL and, in some cases, special
settings in the BIM-EPIC dataset definition (EDD). See “
Physical IOCS
Processing” for additional information.
Cancel Status When a version record is opened, the descriptive data is entered into the
DSN Catalog and the entry is set to open status. When a version record is
closed, BIM-EPIC updates the version record and indicates that the
version has been closed and is now active/available for use as input.
If the job cancels before a version is closed, the version remains in open
status. Open versions cannot be used as input and become eligible for
scratch differently than closed versions. Open Status Generation datasets
become eligible for scratch according to the time limits set for the
TSIDUTL SCRATCH parameters THLDOPEN and DHLDOPEN. The
default is to scratch open disk datasets after two days and tape datasets
after one day. Non-generation datasets are automatically scratched the
next time an output version is created. You can also use BIM-EPIC JCL
options to delete non-generation disk datasets immediately if a job
cancels.
If a dataset successfully closes before the job cancels, the dataset becomes
an active version and is handled as if the job processed normally.
Commenti su questo manuale