Validating user accounts using the IEFUAV exit

After the IEFUAV exit receives control for forked or spawned address space, the accounting information can be checked.

If the _BPX_ACCT_DATA environment variable and the account data was not specified in the spawn inheritance structure for _spawn only, then the account data passed to the exit is the same as the account data of the parent of the forked/spawned address space.

If the _BPX_ACCT_DATA environment variable or account data was specified in the spawn inheritance structure for _spawn, then this is the account data that is seen in this exit. For spawned address spaces, the account data in the spawn inheritance structure takes precedence over account data from the _BPX_ACCT_DATA environment variable.

If the IEFUAV exit sets a return code indicating that the user is not to be allowed to continue, the reason code 0BFC0432 is issued and the address space is terminated.

0BFC0432 — issued from module BPXPRJSR
Reason code 0432 - JRJsrUavXit - The IEFUAV exit rejected the accounting data

If users are running in the shell, they might see the following message:

FSUM9209 cannot execute: reason code 0bfc0432

Message BPXP005I is written to the job log for the user:

BPXP005I  A fork or  spawn error was encountered.
  Return code 00000070 Reason code 0BFC0432