CA ACF2 for z/VM RSCS support lets a job you submit to JES2 or JES3 over the NJI line driver inherit the logonid of the submitter. This means that you no longer need to put logonid statements in your z/OS job streams for them to run under your logonid. CA ACF2 for z/VM RSCS support works with any level system, although it requires CA ACF2 for z/VM for z/OS to take advantage of the logonid inheritance feature.
The CA ACF2 for z/VM RSCS Version 3 Release 1 and later support consists of the DMTAC2V3 TEXT text file. To install the CA ACF2 for z/VM RSCS Version 3 Release 1 and later support:
EXIT nn {ON|OFF} entry1 (entry2 ... entryn)
To specify that an EXIT 11 condition calls CA ACF2 for z/VM, code the EXIT 11 statement as EXIT 11 ON DMTAC2. You can call multiple entry points for a particular exit. You can specify DMTAC2 anywhere in the EXIT 11 list. To specify multiple entry points for an EXIT 11, code the statement as EXIT 11 ON DMTAC2 myexit11. For additional information on RSCS exits, see the IBM publication Virtual Machine Remote Spooling Communications Subsystem Exit Customization.
INCLUDE DMTAC2V3 (name of text deck) ENTRY DMTAC2 (name of entry point) NAME DMTAC2 (name in LOADLIB)
To put the CA ACF2 for z/VM exit in your own LOADLIB, create a LKEDCTRL file with these three lines of text:
INCLUDE DMTAC2V3 (name of text deck) ENTRY DMTAC2 (name of entry point) NAME DMTAC2 (name in LOADLIB)
Execute VMFLKED to rebuild the LOADLIB.
RSCS must have the name of your LOADLIB in its search sequence. To tell RSCS where to find your exit, modify the GLOBAL LOADLIB statement in the PROFILE exec. For example, if you put the CA ACF2 for z/VM exit into a LOADLIB called USEREXIT, the GLOBAL statement reads GLOBAL LOADLIB RSCS USEREXIT.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|