JES2 problems after z/OS, JES2, or ACF2 upgrades or maintenance

Products

• ACF2
• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

Problems related to JES2 after an ACF2, JES2, upgrade or maintenance:

• JES2($HASPxxx) errors.
• ACF2($ACF or$ACFJ messages).
• JES2 related Abends
• Submit failures
• Logonid inheritance issues, the wrong logonid picked up
• ACF01009 LOGONID NOT VALID FOR SUBMISSION BY PROGRAM
• ACF01032 LOGONID/SOURCE COMBINATION lid/src NOT VALID
• ACF01008 UNAUTHORIZED INPUT SOURCE FOR LOGONID lid
• ACF9C007 COULD NOT LOCATE JCT, BATCH DEFAULT ASSIGNED

Environment

Release: 16

Component : CA ACF2 for z/OS

Resolution

The following documentation may be needed or items need to be verified.

1. Verify that the ACF2/JES interface was re-assembled and linked with the appropriate z/OS macro libraries. For JES2 running the JXBUMJ2 job provided in the CAI.CAX1JCL0 data set. Review the job output for JXBUMJ2 to assure the correct JES libraries are being picked up for the appropriate z/OS version.
   
   
2. Verify that all of the ACF2/JES2 exits are properly specified in the JES2 initialization parms, with the proper LOAD and STOR parameters.JES2 initialization statements for the CA ACF2 exits follow:
   LOAD(ACFJ2ITF) STOR=CSA
   EXIT2 ROUTINE=ACFEXIT2
   EXIT4 ROUTINE=ACFEXIT4
   EXIT20 ROUTINE=ACFEXT20
   EXIT24 ROUTINE=ACFEXT24
   EXIT26 ROUTINE=ACFEXT26
   EXIT31 ROUTINE=ACFEXT31
   EXIT34 ROUTINE=ACFEXT34
   EXIT46 ROUTINE=ACFEXT46
   EXIT50 ROUTINE=ACFEXT50
   EXIT52 ROUTINE=ACFEXT52
   EXIT54 ROUTINE=ACFEXT54
   EXIT56 ROUTINE=ACFEXT56
   EXIT225 ROUTINE=ACFEX225
   EXIT227 ROUTINE=ACFEX227,STATUS=DISABLE (Test message exit)
   LOAD(ACFJ2USR) STOR=CSA -OPTIONAL
   EXIT223 ROUTINE=ACFJ2PRE,STATUS=DISABLE (Prevalidation)
   EXIT224 ROUTINE=ACFJ2PST,STATUS=DISABLE (Postvalidation)
   EXIT228 ROUTINE=ACFJ2PRU,STATUS=DISABLE (Prevalidation-user environment)
   EXIT229 ROUTINE=ACFJ2PSU,STATUS=DISABLE (Postvalidation-user environment)
   
   
3. Verify that the ACF2/JES2 exits are defined and enabled by issuing the console command $DEXIT(*) 
   
   
4. If the ACF2/JES2 exits are defined and enabled the ACF2/JES2 ACFEX227 exit can be used to provide more diagnostics to help identify the cause of the problem. The ACF2/JES2 ACFEX227 exit formats three test messages($ACFJ217, $ACFJ218, $ACFJ222)and issues them to the console(WTO)for CA ACF2 debugging purposes. This exit should normally be disabled. Enable/disable this exit at the operator's console using the following commands:
   to enable: $T EXIT227,ENABLE
   to disable: $T EXIT227,DISABLE
   
   Once the EXIT227 is enabled, the problem should be re-created and the console log or joblog containing the $ACFJ217, $ACFJ218and$ACFJ222messages should be provided. 
   *Note: When the EXIT227 is enabled ALL jobs processed by JES2 will generate the $ACFJ217, $ACFJ218and$ACFJ222messages.
   
   
5. The display output from a TSO, ACF, LIST logonid of the logonid(s) in question.