Once activated by TMSINIT, the CA 1 WTO subsystem passes control to CA 1 for all tape mount messages. If the mount request is nonspecific and requires a tape from a specific pool, the mount message is modified to include the tape pool identification (up to 13 characters). If the mount request is specific, the mount message reflects the location of the volume and whether it is a CA 1 controlled volume.
In all cases, a reissued operating system mount message is prefixed with a CA 1 message identification to notify the operator that the intercept is present and functioning. The original and reissued WTO appears on the SYSLOG and JESLOG; only the new WTO is displayed on the console.
On a system console, a non-pool mount message is prefixed with TMS001, while a pool-controlled mount is prefixed with TMS002.
Assume, for example, that a MINIREEL scratch pool has been assigned the range, MI0001-MI9999, and data sets using a high-level alias of MINI are authorized to write to the MINIREEL pool. When the mount request is issued, CA 1 modifies the mount message to read:
*TMS002 IEF233A M 05A0,MINIREEL,SL,6250,JOBNAME,STEP1,MINI.DATASET.NAME
For tape mounts not reflecting a data set name that is prefixed with MINI, the mount message reads:
*TMS001 IEF233A M 05A0,SCRTCH,SL,6250,JOBNAME,STEP1,NON.MINI.DATASET.NAME
JES3 messages use the prefix TMS004 for nonpool mount messages, and TMS005 for pool-controlled mounts.
Note: For CA 1 to properly intercept mount messages, it is required that the system console data set name monitor is activated. This is done by issuing the MN DSNAME system console command. During TMSINIT processing a check is made to ensure the monitor is active. A WTOR prompts the operator if it is not.
If using silos, you must have an entry coded above the silo entry in the sub-system name table. The entry is TMS.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|