Using the IEFUJV job validation exit

At the time of the first fork or spawn, IEFUJV is entered with a subsystem value of OMVS and a job name of BPXYOEJS, which is the job that is used to create the SWA control blocks used by all subsequent forked or spawned address spaces. The IEFUJV exit is not given control for forked or spawned address spaces under subsystem OMVS.

The BPXAS initiators, in which the forked or spawned processes run, do go through the IEFUJV exit with a subsystem value of STC. The IEFUJV exit is given control when the BPXAS initiator is first started. When subsequent fork/spawn requests use that BPXAS initiator address space, the IEFUJV exit is not called because the BPXAS initiator is already active.

The account data that is on the job card for the BPXAS procedure is propagated from the BPXOINIT job. If a BPXOINIT job is defined in SYS1.STCJOBS and the SYS1.STCJOBS data set is set up so that it is used during IPL, then an installation can define account data there that will be propagated to the BPXAS procedure.

The BPXOINIT job is started and the account data is saved in SWA blocks in internal text format. Then, later, when the first BPXAS procedure is started, z/OS UNIX reads the account data that was saved in the SWA blocks and adds the account data to the default job card that it builds. The default job card looks like the following:

//BPXYOEJS JOB(acct-data),MSGLEVEL=(0,0),REGION=54M,TIME=60

z/OS UNIX takes the account data and reconstructs the internal text to a format that can be placed on a JCL statement. The account data is reconstructed by placing quotes around each account data field and then parentheses around the account data. As a result, the account data might look different than it did when it was defined on the BPXOINIT job. For example, if BPXOINIT had the account data defined as (AA,BB), then when z/OS UNIX adds it to the BPXYOEJS job card, the account data is reconstructed as ('AA','BB').