Using Aliases for Utility Names
Since there is no limit to the number of alternate names each utility can have, several aliases can be defined for the same utility name.
Duplicate contradicting definitions for the same alternate names are ignored.
Appropriate messages are issued indicating invalid definition lines. These lines are ignored and the processing continues.
After making changes to the CTJALUT member, the user must issue a “MODIFY ctj_monitor,REFRESH=ALL” command for the changes to take effect.
The format of definition has the following syntax:
-
Each line in the member defines one alias or comment.
-
The original utility name on column 1 (up to 8 characters)
-
Followed by at least one blank
-
The alternate (alias) name (up to 8 characters)
-
Followed by at least one blank
-
Comment (free text)
-
Asterisk in column 1 makes the entire line a comment.
For example, the following alias is defined in the CTJALUT member:
IEBGENER MYGEN1 MYGEN1 is an alias for IEBGENER
The following is the original JCL to be verified:
//COPYFILE EXEC PGM=MYGEN1
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=QUEST.JVER.ACCESS($README)
//SYSUT2 DD DISP=MOD,DSN=QUEST.JVER.ACCESS($README1)
//SYSIN DD DUMMY
The following is the result of the verification:
//COPYFILE EXEC PGM=MYGEN1
CTJP0FI INFORMATION: PGM MYGEN1 FOUND IN THE JOBLIB
CTJA.JCL.UTALIAS.LOAD
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=QUEST.JVER.ACCESS($README)
//SYSUT2 DD DISP=MOD,DSN=QUEST.JVER.ACCESS($README1)
//SYSIN DD DUMMY
CTJUV0I INFORMATION: VERIFYING UTILITY IEBGENER
CTJUV3I INFORMATION: SYSIN IS DUMMY. IEBGENER WILL USE DEFAULTS
CTJUV1I INFORMATION: VERIFYING UTILITY IEBGENER ENDED RC=0000