rh._.exports({"0":[[" ","Phase 3: The PBEM"]],"1":[[" ","Phase \n 3: The PBEM"," ","On UNIX, the PBEM (Primary Batch Execution \n Monitor) runs as a normal program (pbem.exe) using the current security \n credentials."," ","On MVS a batch job is submitted. The \n job runs under the security of the ’dmlibsrv’ process."," ","NOTE  ","You \n can change the job card. For example, you can set up RACF surrogate authority, \n but this happens outside of Dimensions Build, and also applies to non-build \n jobs. The process is similar to the build user logging in to TSO/ISPF, \n using the editor on some JCL, and then typing SUBMIT. The job would probably \n run as the logged in user. However, it may run as someone else. For example \n you may have put USER=XXX in the job card. You may also have a JES exit, \n or a RACF rule that says jobs matching a certain standard (for example \n JOBNAME), should run as a particular user. "," ","Jobcards "," ","You can customize the jobcards that \n build steps and the controlling PBEM use by changing their templates. \n For example, for a normal build step, the jobcard is found at the top \n of the SBEM template, TEMPLATE(MDHBSBEM0). The jobcard for the PBEM is \n in TEMPLATE(MDHBPBM0). There are many template expansion variables available \n to allow a flexible scheme for naming the jobs. For details of the template \n variables see ","The Templating Language and Processor"," chapter \n of the ","Developer’s API Reference"," ","NOTE  "," ","Changing these jobcards does not \n\t in itself change security in any way, unless the site has some additional \n\t RACF rules relating to jobnames and users."," ","Care is needed to ensure that \n\t whatever jobname scheme is chosen, the PBEM and build steps can run \n\t together. For example, a build step cannot be given the same jobname \n\t as a PBEM controller, or a deadlock situation results."]],"id":"286"})