VM Batch Facility V2.2 Program Directory
This program directory, dated November 1993,
applies to VM Batch Facility Version 2 Release 2 (VM Batch Facility V2.2),
Program Number 5684-137 for the following:
© Copyright International Business Machines Corporation 1991, 1993. All rights reserved.
Table of ContentsProgram and Service Level Information Installation Requirements and Considerations Appendix A. Modifying Installation Exits and the CONTROL FILE Appendix B. Listing of Sample CONTROL FILE Appendix C. Changing Installation Defaults: Creating an Override Appendix D. Setting up the Proper RACF Access Authorities
Figures
NoticesReferences in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the
IBM Director of Commercial Relations
IBM Corporation
Purchase, NY 10577
Trademarks and Service MarksThe following terms, denoted by an asterisk (*), used in this document, are trademarks or service marks of IBM Corporation in the United States or other countries: IBM VM/ESA Interactive System Productivity Facility (ISPF) Resource Access Control Facility (RACF) Remote Spooling Communications Subsystem (RSCS) VM Batch Facility IntroductionThis program directory is intended for the system programmer responsible for program installation and maintenance. It contains information concerning the material and procedures associated with the installation and maintenance of VM Batch Facility V2.2. You should read all of this program directory before installing the program and then keep it for future reference. The program directory contains the following sections:
Before installing VM Batch Facility V2.2, read "Preventive Service Planning". This section tells you how to find any updates to the information and procedures in this program directory. Program MaterialsAn IBM program is identified by a program number. The program number for VM Batch Facility V2.2 is 5684-137. The program announcement material describes the features supported by VM Batch Facility V2.2. Ask your IBM marketing representative for this information if you have not already received a copy. The following sections identify the basic and optional program materials available with this program. Basic Machine-Readable MaterialThe distribution medium for this program is 9-track magnetic tape
(written at 6250 BPI) and 3480 tape cartridge.
The tape or cartridge contains all the programs and data needed for
installation.
See "Installation Instructions" for more information about how to install
the program.
Table 1 describes the tape or cartridge.
Table 2 describes the file content of the program tape or
cartridge.
Table 1. Basic Material: Program Tape
Table 2. Program Tape: File Content
Program PublicationsThe following sections identify the basic and optional publications for VM Batch Facility V2.2. Basic Program PublicationsOne copy of the following publication is included when you
order the basic materials for VM Batch Facility V2.2.
For additional copies, contact your IBM representative.
Table 3. Basic Material: Unlicensed Publications
Microfiche SupportThere is no microfiche for VM Batch Facility V2.2. Publications Useful During InstallationThe publications listed in Table 4 may be
useful during the installation of VM Batch Facility V2.2.
To order copies, contact your IBM representative.
Table 4. Publications Useful During Installation
Program SupportThis section describes the IBM support available for VM Batch Facility V2.2. Preventive Service PlanningBefore installing VM Batch Facility V2.2, check with your IBM Support Center or use either Information/Access or IBMLink (Service Link) to see whether there is additional Preventive Service Planning (PSP) information. To obtain this information, specify the following UPGRADE and SUBSET values:Table 5. PSP Upgrade and Subset ID
Statement of Support ProceduresReport any difficulties you have using this program to your IBM Support Center. In the U.S.A., if an APAR is required, submit the data to the location identified in the Programming System General Information (PSGIM) manual (G229-2228) as being responsible for the failing component. Table 6 identifies the component ID
(COMPID), RETAIN Release and Field Engineering Service Number (FESN)
for VM Batch Facility V2.2.
Program and Service Level InformationThis section identifies the program and any relevant service levels of VM Batch Facility V2.2. The program level refers to the APAR fixes incorporated into the program. The service level refers to the PTFs integrated. Information about the cumulative service tape is also provided. Program Level InformationThe following APAR fixes against previous releases of VM Batch Facility
have been incorporated into this release:
Service Level InformationThis is the initial shipment of VM Batch Facility V2.2 and there are no PTFs. Cumulative Service TapeThere is no cumulative service tape for VM Batch Facility V2.2. Installation Requirements and ConsiderationsThe following sections identify the system requirements for installing and activating VM Batch Facility V2.2. DASD Storage and User ID RequirementsThe following lists the default User IDs that VM Batch Facility V2.2 requires for installation.
Table 7 lists the user IDs and minidisks that are used to install, test and service VM Batch Facility V2.2. Important Installation Notes:
Table 7. DASD Storage Requirements for Target Minidisks
Program ConsiderationsIf you run CMS Release 7 on a user ID which is defined with more than 16 megabytes of virtual storage then VM Batch Facility will encounter an error when the code issues a PROGMAP command. If you must run CMS Release 7 then make sure that the user ID is defined with a virtual storage size of 16 megabytes or less. This problem affects both job submittor user IDs and task machine user IDs. Installation of the following corequisite products will provide optional additional function. Refer to the documentation for the individual corequisite products for additional information.
Programming RequirementsUse VMSES/E when installing and servicing this program on the following VM platforms:
When running VM Batch Facility V2.2 on VM/ESA 1.0 370 Feature, PTF UM24908 (APAR VM54104) must be applied. VM54104 addresses a CMS EXECMAP problem when running under VM/ESA 1.0 370 Feature. Program Installation/Service ConsiderationsThis section describes items that should be considered before you install or service VM Batch Facility V2.2
Installation InstructionsThis chapter describes the installation methods and the step-by-step procedures to install and activate VM Batch Facility V2.2. The step-by-step procedures are in two column format. The steps to be performed are in bold large numbers. Commands for these steps are on the left hand side of the page in bold print. Additional information for a command may exist to the right of the command. For more information about the two column format see "Understanding Dialogs with the System" in the VM/ESA Installation Guide. Installation of VM Batch Facility V2.2 with VMSES/E (VMFINS)VMFINS will be used to install VM Batch Facility V2.2. VMFINS is an installation aid supplied as part of VMSES/E to make installation of VM and Licensed Programs (LPs) consistent. For a complete description of all VMFINS installation options refer to:
Plan Your InstallationThe VMFINS command will be used to plan the installation. This is a two step process that will:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Link to the test monitor's 199 disk in write mode.
link tbatch 199 299 mr access 299 g
- Copy the EXECSAMP file to the test monitor's 199 disk.
access 296 f copyfile exitname execsamp f = = g (olddate replace
exitname is the name of the serviced exit. - XEDIT the EXECSAMP file on the 199 disk.
- Locate the Change History section at the bottom of the prolog.
- Compare the entries to the Change History section in your existing copy of the exit on the 199 disk to see what service has been added to the EXECSAMP file.
- Scan the right margin of the EXECSAMP file, looking for the APAR number associated with the new addition to the Change History section. An APAR number in the right margin indicates that line has been modified or added by the APAR.
- Determine how the service to the EXECSAMP file affects your copy of the exit, and make your changes accordingly.
- You should include the PARSE ARG statement and prolog from the EXECSAMP file in your copy of the exit, and update the Change History section with the new addition.
The presence of an EXECSAMP file on the 29E disk indicates that the corresponding user or task interface exit has been serviced. Complete the following steps for each EXECSAMP file on the disk. If there are no EXECSAMP files on the 29E disk, continue with "Verify the New Service".
- If the EXECSAMP file is for an exit that you have not
previously modified, replace the existing copy. .
access 29e e rename exitname execsamp e = exec =
exitname is the name of the serviced exit. - If the EXECSAMP file is for an exit that you have
previously modified:
- XEDIT the EXECSAMP file on the 29E disk.
- Locate the Change History section at the bottom of the prolog.
- Compare the entries to the Change History section in your existing copy of the exit on the 29E disk to see what service has been added to the EXECSAMP file.
- Scan the right margin of the EXECSAMP file, looking for the APAR number associated with the new addition to the Change History section. An APAR number in the right margin indicates that line has been modified or added by the APAR.
- Determine how the service to the EXECSAMP file affects your copy of the exit, and make your changes accordingly.
- You should include the PARSE ARG statement and prolog from the EXECSAMP file in your copy of the exit, and update the Change History section with the new addition.
- XEDIT the EXECSAMP file on the 29E disk.
Verify the New Service
- Start the test monitor (TBATCH).
autolog tbatchThis will autolog the test monitor machine and the PROFILE EXEC will invoke the monitor program.
This command must be issued from a user ID with CP privilege class A or B.
password
If you are prompted for a password, enter the logon password for TBATCH. Depending on system settings, password may be required on the autolog command line. ('autolog tbatch TBATCH. - Access the test code.
access 29e b access 29d c
- Verify that VM Batch Facility V2.2 is functioning correctly.
batch address tbatch * batch level
These commands address the TBATCH monitor machine and submit a job called DGRLEVEL. When DGRLEVEL completes the console from the task machine in which it ran will be in your virtual reader.
Note: The actual service level reported (xxx in the sample output) will vary according to the service applied and will not necessarily be the same for all components.
+---------------------------Sample Message output----------------------------+
DGRBAT555I BATCH Version 2.2, Service Level xxx. DGREXE120I YOU ARE NOW ADDRESSING MONITOR 'TBATCH' AT NODE 'yournode' DGREXE555I DGRBATCH Version 2.2, Service Level xxx. DGRIPW555I DGRIPW Version 2.2, Service Level xxx. DGRUVM555I DGRUVM Version 2.2, Service Level xxx. DGRLAF555I DGRLAF Version 2.2, Service Level xxx. DGRCHJ555I DGRCHJO Version 2.2, Service Level xxx. DGRPAS555I DGRPASS Version 2.2, Service Level xxx. DGRSUB555I DGRSUBM Version 2.2, Service Level xxx. DGRUME555I DGRUME Version 2.2, Service Level xxx. DGRMAI555I DGRMAIN Version 2.2, Service Level xxx. DGRRBT555I RUNBATCH Version 2.2, Service Level xxx. DGREXE119I JOB 'DGRLEVEL' SUBMITTED TO 'TBATCH' AT 'yournode' Ready; T=0.51/0.64 19:13:45 Job DGRLEVEL has been received Job DGRLEVEL has started RDR FILE 0063 SENT FROM youruser CON WAS 0108 RECS 0050 CPY Job DGRLEVEL has ended; RC = 0
+------------------------End of Sample Message output------------------------+
+--------------------Sample Task Machine Console Output.---------------------+
VM Batch Facility components as seen by task machine TBATCH1: DGRLVL555I DGRLEVEL Version 2.2, Service Level xxx. DGREXE555I DGRBATCH Version 2.2, Service Level xxx. DGRLAF555I DGRLAF Version 2.2, Service Level xxx. DGRRUN555I DGRRUN Version 2.2, Service Level xxx. DGRTAS555I DGRTASK Version 2.2, Service Level xxx. DGRTSK555I DGRTSK Version 2.2, Service Level xxx. DGRUVM555I DGRUVM Version 2.2, Service Level xxx. DGRUME555I DGRUME Version 2.2, Service Level xxx.
+-----------------End of Sample Task Machine Console Output.-----------------+
- Submit other test jobs, as necessary, to verify that VM Batch Facility V2.2 is functioning correctly. Remember to address the TBATCH monitor machine when submitting the test job.
- Stop the test monitor machine.
batch stop
Place the New Service into Production
- Shut down the production monitor machine (BATCH).
batch address batch * batch stop
These commands must be issued from an administrator user ID.
- Place the VM Batch Facility V2.2 monitor machine code into production.
access 296 e access 196 f vmfcopy * * e = = f (prod 5684137a%batch olddate replace
296 is the minidisk that the new code was loaded to during service application.196 is the production build disk.
- Logon to MAINT and access the serviced general user code.
link * 19e 19e mr access 19e f link P684137A 29E 29E rr access 29e e vmfcopy * * e = = f (prod 5684137a%batch olddate replace
- Re-save the CMS saved system. This will re-save CMS to put the 19E
disk back into shared status.
Refer to "Placing Components into Production" in the VM/ESA Service Guide. This is Step 11 for VM/ESA Release 1.0 370 Feature, or step 12 for VM/ESA Release 2.0 and above.
- Put the HELP code into production.
link P684137A 29D 29D rr access 29D e access 19D f vmfcopy * * e = = f (prod 5684137a%batch olddate replace
- Re-save the HELP saved segment.
Refer to "Placing Components into Production" in the VM/ESA Service Guide. This is Step 11 for VM/ESA Release 1.0 370 Feature, or step 12 for VM/ESA Release 2.0 and above.
- Make any service related changes to the
CONTROL FILE or monitor exits.
- If you made changes to the CONTROL FILE on TBATCH's 199 disk due to service applied to the CONTROL SAMPLE file, make the appropriate changes to the production monitor machine's CONTROL FILE at this time.
- If you made changes to any of the monitor exits on TBATCH's 199 disk due to service applied to the EXECSAMP files, copy the modified exits to BATCH's 199 disk at this time.
- Delete any EXECSAMP files from the 29E and 296 disks. In
addition, delete the CONTROL SAMPLE file from the 296 disk.
These files are erased so that their possible future presence on the disks will indicate that they have received new service.
access 29e e vmferase file * execsamp e
This erases all EXECSAMP files and updates the partcat on 29E.access 296 f vmferase file * execsamp f
This erases all EXECSAMP files and updates the partcat on 296.vmferase file control sample f
This erases the CONTROL SAMPLE file and updates the partcat on 296. - Start the monitor machine (BATCH).
autolog batch This will autolog the monitor machine and the PROFILE EXEC will invoke the monitor program.This command must be issued from a user ID with CP privilege class A or B.
password
If you are prompted for a password, enter the logon password for BATCH. Depending on system settings, password may be required on the autolog command line. ('autolog batch BATCH.
|
You have now finished servicing VM Batch Facility V2.2.
|
Appendix A. Modifying Installation Exits and the CONTROL FILE
Modifying Monitor Exits and the CONTROL FILE
The following instructions are for modifying the monitor exits and the CONTROL FILE. The monitor exits are:
- DGRIDO EXEC
- DGRUMSG EXEC
- DGRUAC EXEC
- DGRUCD EXEC
- DGRECUR EXEC
- DGRUJB EXEC
It is advisable to update the test monitor files and verify the
modifications before you update the files on the production monitor(s).
- Logon to an administrator user ID for the monitor you wish to modify.
- Access the monitor's 199 disk in write mode.
link monitor 199 199 mr access 199 fm
monitor is the user ID of the monitor you wish to modify.
fm is any free filemode.
- Use XEDIT to make the required changes to the file(s) on the 199 disk.
- Ensure that you are addressing the correct monitor.
batch address monitor *
monitor is the user ID of the monitor that uses the files you have modified.
- If you modified any exits then reload them.
batch reload
This will cause the monitor to reload all of the exits.
- If you modified the CONTROL FILE then reload it.
batch control set
This will cause the monitor to reload the CONTROL FILE.
|
You have now finished modifying the installation exits and
CONTROL FILE.
|
Modifying Task and User Interface Exits
The following instructions are for modifying the task and user interface exits that reside on the Y-disk (19E). These exits are:- DGROOLY EXEC
- DGREVR EXEC
- Logon to P684137A.
- Check the 29E disk contents.
If the 29E disk does not have DGROOLY EXEC and DGREVR EXEC files then you must copy the files from the sample files on the 2C2 disk..
access 2c2 e access 29e f vmfcopy dgrooly execsamp e = exec f (prod 5684137a%batch olddate vmfcopy dgrevr execsamp e = exec f (prod 5684137a%batch olddate
- Use XEDIT to make changes to the EXEC files on the 29E disk.
- Test the exits.
You should start the test monitor and submit a job that will verify that the exits function as required. Remember to address the TBATCH monitor machine when submitting the test job.
autolog tbatch
This will autolog the test monitor machine and the PROFILE EXEC will invoke the monitor program.This command must be issued from a user ID with CP privilege class A or B.
password
If you are prompted for a password, enter the logon password for TBATCH. Depending on system settings, password may be required on the autolog command line. ('autolog tbatch password')
Place the Updated Task and User Interface Exits into Production
- Logon to MAINT and access the customized exits.
link P684137A 29E 29E rr access 29E e vmfcopy * * e = = fm (prod 5684137a%batch olddate replace
fm is the filemode of the 19E disk accessed in R/W mode.
- Re-save the CMS saved system. This will re-save CMS to put the 19E
disk back into shared status.
Refer to "Placing Components into Production" in the VM/ESA Service Guide. This is Step 11 for VM/ESA Release 1.0 370 Feature, or step 12 for VM/ESA Release 2.0 and above.
|
You have now finished modifying the task and user interface exits.
|
Appendix B. Listing of Sample CONTROL FILE
+--------------------------------CONTROL FILE--------------------------------+
*--------------------------------------------------------------------*
* VM BATCH FACILITY CONTROL FILE *
*--------------------------------------------------------------------*
* Change History *
* *
* *
*--------------------------------------------------------------------*
*--------------------------------------------------------------------*
* TASK MACHINES *
*--------------------------------------------------------------------*
TASK TBATCH1 XXXXXXXX XXXXXXXX .AB 0000 2400
TASK TBATCH2 XXXXXXXX XXXXXXXX .AB 0000 2400
*--------------------------------------------------------------------*
* AUTHORIZED USERS *
*--------------------------------------------------------------------*
ADMIN P684137A
* ADMIN XXXXXXXX XXXXXXXX
*--------------------------------------------------------------------*
* CLASSES *
*--------------------------------------------------------------------*
* This sample Class A :
* - does not allow a storage override
* - does not subject jobs to LLS
* - stall values default
CLASS CLASSID=A DEFCPU=1000 MAXCPU=2000 +
DEFPRT=64 MAXPRT=1000 +
DEFPUN=64 MAXPUN=1000 +
DEFSTOR=2M +
LLSDEF=LLS
* This sample Class B :
* - allows unlimited CPU if requested
* - allows storage values between 2M and 16M
* - stall processing is suppressed
* - has a restricted window
* - does not subject jobs to LLS by default.
CLASS CLASSID = B DEFCPU = 9999 MAXCPU = NONE +
DEFPRT=64 MAXPRT=1000 +
DEFPUN=64,MAXPUN=1000 +
DEFSTOR=4M MINSTOR=2M MAXSTOR=16M +
STALLWRN=* +
SWINDOW=1700 EWINDOW=0800
*
CLASS CLASSID=AUTOLOG
*--------------------------------------------------------------------*
* LLS ACTIVITY *
*--------------------------------------------------------------------*
* LLS RESOURCE=CPU SCV=XXXX RCD=XXXX
*--------------------------------------------------------------------*
* CONTROL PARAMETERS *
*--------------------------------------------------------------------*
*
MAXIMUM-USERS 50
MAXIMUM-JOBS 500
*
DISPATCH-INTERVAL 4
CHECK-RUNNING-JOBS 10
MAXJOBS/USER:RUNNING 8
MAXJOBS/USER:RUNNING+QUEUED 32
MINIMUM-STALL-DELAY 60
MAXIMUM-STALL-WARNINGS 3
MAXIMUM-JOB-SIZE 100000
JOB-INIT-TIME/100000-RECS 4
ACCOUNT 0
CONSOLE TBATCH
*
+----------------------------End of CONTROL FILE-----------------------------+
Appendix C. Changing Installation Defaults: Creating an Override
During the planning phase of the installation step you are given the opportunity to change the default installation environment using the Make Override Panel function. You may change the name of the $PPF file, the installation and service user ID, minidisk addresses or Shared File System directories. The Make Override Panel will create an override for the component name and PPF name that are used in the VMFINS command with the PLAN option.
You may be using the component name BATCHINS for a minidisk installation or BATCHSFSINS for an installation in Shared File System. Any changes you make to the installation component must also be made to the service component. The service component name will be used at a later time, for applying service to VM Batch Facility V2.2. The service component name for BATCHINS is BATCH. The service component partner for BATCHSFSINS is BATCHSFS.
To make changes to the default installation environment (e.g. user ID, minidisks, etc.) for a minidisk installation, you must invoke the VMFINS command as follows:
vmfins install ppf 5684137a batchins (plan nomemo
and type 1 at the prompt to indicate that you wish to change the default installation values.
The Make Override Panel will generate a new $PPF. In the example that follows, BATCH22 is used as the $PPF name. The Make Override Panel will automatically compile the new $PPF with a component BATCHINS. In BATCH22 $PPF we have changed the default installation user ID from P684137A to LPMAINT.
Our example $PPF was created by the Make Override Panel during planning.
+----------------------------- BATCH22 $PPF file-----------------------------+
************************************ * VM BATCH FACILITY 2.2.0 * ************************************ :OVERLST. BATCHINS :BATCHINS. BATCHINS 5684137A :DCL. REPLACE &BATID7 USER TBATCH2 &DISK23 LINK TBATCH2 191 191 MR * TEST BATCH2 WORK DISK &BATID6 USER TBATCH1 &DISK22 LINK TBATCH1 191 191 MR * TEST BATCH1 WORK DISK &BATID5 USER TBATCH &DISK20 LINK TBATCH 194 194 MR * TEST WORK FILES &DISK21 LINK TBATCH 195 195 MR * TEST ACCOUNTING DATA &DISK25 LINK TBATCH 199 199 MR * Control file & exits &DISK18 LINK TBATCH 191 191 MR * TEST MONITOR 191 &DISK19 LINK TBATCH 193 193 MR * TEST USER JOB FILES &BATID1 USER LPMAINT &BAS1Z LINK LPMAINT 2B2 2B2 MR * BASE DISK &DISK9 LINK LPMAINT 29D 29D MR * VMBATCH HELP FILES &DISK10 LINK LPMAINT 29E 29E MR * VMBATCH USER CODE &DISK17 LINK LPMAINT 22D 22D MR * VMBATCH SOFTCOPY PUBS &191 LINK LPMAINT 191 191 MR * A DISK &SAMPZ LINK LPMAINT 2C2 2C2 MR * SAMPLE/LOCAL FILES &DELTZ LINK LPMAINT 2D2 2D2 MR * PRODUCT SERVICE &APPLX LINK LPMAINT 2A6 2A6 MR * AUX AND INVENTORY FILES &APPLZ LINK LPMAINT 2A2 2A2 MR &BLD0Z LINK LPMAINT 296 296 MR * TEST - MONITOR CODE &BLD1Z LINK LPMAINT 196 196 MR * PROD - MONITOR CODE &BATID4 USER BATCH2 &DISK16 LINK BATCH2 191 191 MR * BATCH2 WORK DISK &BATID3 USER BATCH1 &DISK15 LINK BATCH1 191 191 MR * BATCH1 WORK DISK &BATID2 USER BATCH &DISK11 LINK BATCH 191 191 MR * MONITOR 191 &DISK12 LINK BATCH 193 193 MR * USER JOB FILES &DISK13 LINK BATCH 194 194 MR * WORK FILES &DISK14 LINK BATCH 195 195 MR * ACCOUNTING DATA &DISK24 LINK BATCH 199 199 MR * Control file & exits :EDCL. :END.
+-------------------------End of BATCH22 $PPF file--------------------------+
Following are the additions that must be made to include the user ID change in the BATCH service component name used during service. The additions to this file are shown below in bold print.
+-------------------------Modified BATCH22 $PPF file-------------------------+
************************************ * VM BATCH FACILITY 2.2.0 * ************************************ :OVERLST. BATCHINS BATCH :BATCHINS. BATCHINS 5684137A :DCL. REPLACE &BATID7 USER TBATCH2 &DISK23 LINK TBATCH2 191 191 MR * TEST BATCH2 WORK DISK &BATID6 USER TBATCH1 &DISK22 LINK TBATCH1 191 191 MR * TEST BATCH1 WORK DISK &BATID5 USER TBATCH &DISK20 LINK TBATCH 194 194 MR * TEST WORK FILES &DISK21 LINK TBATCH 195 195 MR * TEST ACCOUNTING DATA &DISK25 LINK TBATCH 199 199 MR * Control file & exits &DISK18 LINK TBATCH 191 191 MR * TEST MONITOR 191 &DISK19 LINK TBATCH 193 193 MR * TEST USER JOB FILES &BATID1 USER LPMAINT &BAS1Z LINK LPMAINT 2B2 2B2 MR * BASE DISK &DISK9 LINK LPMAINT 29D 29D MR * VMBATCH HELP FILES &DISK10 LINK LPMAINT 29E 29E MR * VMBATCH USER CODE &DISK17 LINK LPMAINT 22D 22D MR * VMBATCH SOFTCOPY PUBS &191 LINK LPMAINT 191 191 MR * A DISK &SAMPZ LINK LPMAINT 2C2 2C2 MR * SAMPLE/LOCAL FILES &DELTZ LINK LPMAINT 2D2 2D2 MR * PRODUCT SERVICE &APPLX LINK LPMAINT 2A6 2A6 MR * AUX AND INVENTORY FILES &APPLZ LINK LPMAINT 2A2 2A2 MR &BLD0Z LINK LPMAINT 296 296 MR * TEST - MONITOR CODE &BLD1Z LINK LPMAINT 196 196 MR * PROD - MONITOR CODE &BATID4 USER BATCH2 &DISK16 LINK BATCH2 191 191 MR * BATCH2 WORK DISK &BATID3 USER BATCH1 &DISK15 LINK BATCH1 191 191 MR * BATCH1 WORK DISK &BATID2 USER BATCH &DISK11 LINK BATCH 191 191 MR * MONITOR 191 &DISK12 LINK BATCH 193 193 MR * USER JOB FILES &DISK13 LINK BATCH 194 194 MR * WORK FILES &DISK14 LINK BATCH 195 195 MR * ACCOUNTING DATA &DISK24 LINK BATCH 199 199 MR * Control file & exits :EDCL. :END. ************************************ :BATCH. BATCH 5684137A :DCL. REPLACE &BATID7 USER TBATCH2 &DISK23 LINK TBATCH2 191 191 MR * TEST BATCH2 WORK DISK &BATID6 USER TBATCH1 &DISK22 LINK TBATCH1 191 191 MR * TEST BATCH1 WORK DISK &BATID5 USER TBATCH &DISK20 LINK TBATCH 194 194 MR * TEST WORK FILES &DISK21 LINK TBATCH 195 195 MR * TEST ACCOUNTING DATA &DISK25 LINK TBATCH 199 199 MR * Control file & exits &DISK18 LINK TBATCH 191 191 MR * TEST MONITOR 191 &DISK19 LINK TBATCH 193 193 MR * TEST USER JOB FILES &BATID1 USER LPMAINT &BAS1Z LINK LPMAINT 2B2 2B2 MR * BASE DISK &DISK9 LINK LPMAINT 29D 29D MR * VMBATCH HELP FILES &DISK10 LINK LPMAINT 29E 29E MR * VMBATCH USER CODE &DISK17 LINK LPMAINT 22D 22D MR * VMBATCH SOFTCOPY PUBS &191 LINK LPMAINT 191 191 MR * A DISK &SAMPZ LINK LPMAINT 2C2 2C2 MR * SAMPLE/LOCAL FILES &DELTZ LINK LPMAINT 2D2 2D2 MR * PRODUCT SERVICE &APPLX LINK LPMAINT 2A6 2A6 MR * AUX AND INVENTORY FILES &APPLZ LINK LPMAINT 2A2 2A2 MR &BLD0Z LINK LPMAINT 296 296 MR * TEST - MONITOR CODE &BLD1Z LINK LPMAINT 196 196 MR * PROD - MONITOR CODE &BATID4 USER BATCH2 &DISK16 LINK BATCH2 191 191 MR * BATCH2 WORK DISK &BATID3 USER BATCH1 &DISK15 LINK BATCH1 191 191 MR * BATCH1 WORK DISK &BATID2 USER BATCH &DISK11 LINK BATCH 191 191 MR * MONITOR 191 &DISK12 LINK BATCH 193 193 MR * USER JOB FILES &DISK13 LINK BATCH 194 194 MR * WORK FILES &DISK14 LINK BATCH 195 195 MR * ACCOUNTING DATA &DISK24 LINK BATCH 199 199 MR * Control file & exits :EDCL. :END.
+---------------------End of Modified BATCH22 $PPF file----------------------+
You will need to compile the $PPF to create a usable version of it. Both component names must be compiled:
vmfppf batch22 batch vmfppf batch22 batchins
You now have a new PPF that can be used during the remainder of the installation and service instructions for VM Batch Facility V2.2.
Appendix D. Setting up the Proper RACF Access Authorities
This appendix describes the steps necessary to set up the proper
RACF environment necessary for VM Batch Facility V2.2.
For additional information, refer to the RACF Command Language
Reference.
- Logon to a user ID with RACF SPECIAL authority.
- Give the monitor machine access to the task machines' 191 disks.
- For the test system:
racf permit tbatch1.191 class(vmdisk) id(tbatch) access(update) racf permit tbatch2.191 class(vmdisk) id(tbatch) access(update)
- For the production system:
racf permit batch1.191 class(vmdisk) id(batch) access(update) racf permit batch2.191 class(vmdisk) id(batch) access(update)
- For the test system:
- Give the administrator access to the monitor's 199 disk.
- For the test system:
racf permit tbatch.199 class(vmdisk) id(p684137a) access(update)
- For the production system:
racf permit batch.199 class(vmdisk) id(p684137a) access(update)
These commands should be repeated for each administrator defined in the CONTROL FILE.
- For the test system:
- Allow the task machines to act as alternate user IDs for job
submittors.
- Activate the VMBATCH class.
racf setr classact(vmbatch)
- Indicate that profiles in the VMBATCH class can contain generic
characters.
racf setr generic(vmbatch)
- Define a generic profile for all potential alternate user IDs.
racf rdef vmbatch * uacc(none)
- Permit the task machines to function as workers with any alternate
user IDs.
- For the test system:
racf permit * class(vmbatch) id(tbatch1) access(control) racf permit * class(vmbatch) id(tbatch2) access(control)
- For the production system:
racf permit * class(vmbatch) id(batch1) access(control) racf permit * class(vmbatch) id(batch2) access(control)
Failure to establish the proper RACF environment to allow VM Batch Facility V2.2 task machines to act as alternate user IDs for job submittors will result in the following message when a job is submitted:
DGRVMC003W Job userid nodeid jobid not authorized to use ALTID userid.
- For the test system:
- Activate the VMBATCH class.
