Assigning Account Numbers to Transactions

The account number for inbound work comes from one of two places depending on whether the account is tailored. If the account is not tailored (the TP profile specifies TAILOR_ACCOUNT(NO)), the account number comes from the TP profile JCL JOB statement section as shown in the following example.

Figure 1. Example of a TP Profile for No Account Tailoring

      TPNAME(MIKES_TP)
      TPSCHED_DELIMITER(+++)
        CLASS(A)
        TAILOR_ACCOUNT(NO)
        JCL_DELIMITER(%%%)
  //MYTP     JOB  'MIKE',...
  //STEP1    EXEC PGM=MYTP  ...
        ...
  %%%
  +++

If the account is tailored (the TP profile specifies TAILOR_ACCOUNT(YES)), account numbers come from each user's security profile. Each new account number is retrieved from the WORKATTR segment of a RACF® ADDUSER or ALTUSER command, as shown in one of the following examples.

Figure 2. Example of a TP Profile for Account Tailoring

      TPNAME(MAIL)
      TPSCHED_DELIMITER(+++)
        CLASS(A)
        TAILOR_ACCOUNT(YES)
        JCL_DELIMITER(%%%)
  //MAIL     JOB  'DEPT5A' ...
  //STEP1    EXEC PGM=MAILBAG ...
       ...
  %%%
  +++

Figure 3. Example of a RACF User Profile for Account Tailoring

 ALTUSER USER22 WORKATTR (WANAME('LINDA MEYERS') WABLDG('BUILDING 9')
   WADEPT('DEPARTMENT 5A') WAROOM('ROOM 22') WAADDR1('HOMEVILLE, NY')
   WAACCNT('22LMD5A'))

For information about RACF user profiles, see Setting up Network Security. For information about how SMF audits APPC resources, see z/OS MVS System Management Facilities (SMF).

TPs that tailor account numbers can charge resources to a different account number for each instance of the TP. As account numbers change, an installation might want to validate the changed numbers. Exit IEFUAV allows for account validation before a new instance of a program runs. For information about IEFUAV, see z/OS MVS Installation Exits.