A1

Explanation

IMS returns the A1 status code for one of the following reasons:

• AUTH call for LU 6.2 input did not find a PST LU 6.2 extension block or did not find a UTOKEN.
• CHNG call against alternate response PCB when the application program has not yet issued a GU.
• The MSC program routing exit routine (DFSCMPR0) was called while processing a CHNG call and one of the following occurred:
  • The exit routine rejected the call by returning with return code 8 (A1 status code).
  • The exit routine returned with a RC=4 to route the message back to the originating system; however, the originating system has not been determined because the application program has not issued a GU.
  • The SYSID returned in R0 by the exit routine is not a valid remote SYSID.
  • The MSNAME pointed to by the address in R1, set by the exit routine, is not a valid remote MSNAME.
• The MSC program routing routine exit (DFSMSCE0) was called while processing an ISRT or CHNG call and one of the following occurred:
  • The exit routine rejected the call by setting MSPRFL3=MSPR3REJ in the DFSMSCEP user parameter list that is passed to the exit.
  • IMS detected an error while processing the reroute request from the exit. It issued a message "DFS070 Unable to route message RSN=xxyy" and wrote a 6701-MSCE log record to the IMS log. For more information about this error, see the topic on diagnosing message routing problems in the IMS diagnostic information.
• The destination name supplied in the I/O area of a CHNG call is invalid.
• The destination name supplied in the I/O area of a CHNG call is valid (the destination is a program and the PCB is not an alternate response PCB), but the transaction is Fast Path exclusive.
• AUTH call parameter list contained an invalid generic CLASS name. No access checking was done.
• The routing exit routine (DFSCMPR0 or DFSMSCE0) attempted an invalid request to override a direct routing request.
• The OTMA Destination Resolution user exit (OTMAYPRX) might have specified an incorrect 16-byte OTMA client override name. The client name cannot contain all blanks. If the client name is shorter than 16 bytes, it must be padded with blanks.
• The length of modified OTMA user data is over 1K for the OTMA DFSYDRU0 exit.
• The OTMAYPRX and DFSYDRU0 user exit routines returned an unsupported return code.
• The OTMA destination descriptor entry located for the CHNG call cannot use the IMSTRAN type.
• The OTMA member name or OTMA client override name cannot be the OTMA internal member name DFSYICAL for the OTMA ALTPCB output.