JCL and packaging changes for Enterprise COBOL Version 5 and Version 6
There have been a number of changes to the packaging, installation and JCL with Enterprise COBOL V5 and V6.
Changes apply to Enterprise COBOL V5 and V6
The SIGYCOMP
data
set is now a PDSE, rather than a PDS data set as in prior versions.
Enterprise COBOL V5 and V6 requires additional
data sets:
- When compiling under z/OS® TSO
or batch, the COBOL compiler now requires 15 utility data sets,
SYSUT1
toSYSUT15
- The
SYSMDECK
data set is now required for all compilations.SYSMDECK
may be specified as a utility (temporary) data set if theNOMDECK
option is specified. WhenMDECK
is specified, theSYSMDECK DD
allocation must specify a permanent data set. - The alternate DDNAME list parameter, used when the COBOL compiler is invoked from an assembly language program, is expanded with entries for the additional work data sets.
The following JCL cataloged procedures are no longer supported,
and have been deleted with Enterprise COBOL V5 and V6. Because they
all use the Language Environment® Prelinker or the DFSMS Loader, which are no longer
supported for use with Enterprise COBOL V5 and V6.
- IGYWCG
- IGYWCPG
- IGYWCPL
- IGYWCPLG
- IGYWPL
The catalogued procedures that ship with Enterprise COBOL V5 and V6 have been modified.
- IGYWC
- IGYWCL
- IGYWCLG
Changes apply to Enterprise COBOL V6
To change to uppercase English or Japanese compiler messages in COBOL V6, in addition to using the LANGUAGE compiler option, you must also set the Language Environment runtime option NATLANG at compile time. We recommend using CEEOPTS DD in the compile JCL.
For example,
to change messages to Japanese, use the LANGUAGE(JA) compiler option
and also specify the NATLANG LE runtime option at compile time:
//CEEOPTS DD *
NATLANG(JPN)
/*