DL/I Status code

This appendix describes DL/I status codes and how to handle them.

The result of DL/I Call processing can be identified using the code value of the PCB status code field. Application programmers can check causes for the results of processing and how to respond to them, by checking the status code field.

  • AB

    Cause

    In function calls that require an I/O Area and an I/O Area has not been specified as a parameter.

    Action

    Specify the correct data area that corresponds to the function calls.

  • AD

    Cause

    Specified PCB that does not correspond to the function call as a parameter.

    (1) IO-PCB was not used in the system service call.

    (2) ALT-PCB was used rather than IO-PCB in the GU call or GN call.

    (3) The message GU call was used for the IO-PCB without defining IN=trancode in BMP JCL.

    Action

    Determine if the PCB is appropriate to the function call.

  • AZ

    Cause

    (1) Used the PURG call to send the SPA.

    (2) The first message segment is not SPA when a conversational transaction issues an ISRT ALTPCB call.

    Action

    Correctly use the PURG and ISRT call.

  • A2

    Cause

    Used the CHNG call incorrectly.

    (1) Used the CHNG call if not ALT-PCB.

    (2) Used the CHNG call for the PCB not for ALT-PCB.

    (3) Used the CHNG call for the PCB whose message segment has not been sent.

    Action

    (1) Use a modifiable ALT-PCB as the CHNG call.

    (2) If the destination needs to be changed after sending a segment, change the destination using the CHNG call after a message purge.

  • A3

    Cause

    For the modifiable ALT-PCB, ISRT or the PURG call was used without specifying the destination. The PURG call is processed as a parameter for a single I/O Area.

    Action

    Use ISRT or the PURG call for the PCB which defined the destination using the CHNG call.

  • A4

    Cause

    No access to the destination designated by CHNG Call.

    Action

    Check if the sender designated by CHNG Call is correct and check whether the sender is authorized.

  • A5

    Cause

    Used the wrong parameter list when using a message ISRT call. It is not the first segment of the output message but the 4th parameter (MOD name) was specified.

    Action

    If it is not the first segment of the message, do not specify the 4th parameter.

  • A6

    Cause

    The size of a message segment that is sent using the message ISRT call or PURG call is bigger than the SEGSIZE of the TRANSACT macro.

    Action

    Make the size of the message segments to be sent, smaller than the SEGSIZE of the TRANSACT macro.

  • QC

    Cause

    As a message for the applicable program does not exist in the input queue, the GU call was used.

    Action

    The applicable code is output to notify status information, as application programs stop.

  • QD

    Cause

    The GN call was used but there is no segment in the applicable message.

    Action

    Process the message properly in the application program as there is no segment.

  • QE

    Cause

    The message GU call was not used but the message GN call.

    Action

    To use the message GN call, first use the message GU call.

  • QH

    Cause

    The name of the output logical terminal or transaction code was not registered in IMS. The length of the message segment that was sent using the message ISRT call or PURG call is smaller than 5 bytes.

    Action

    Check the name of the logical terminal and transaction code.

  • XA

    Cause

    After responding to the originating terminal, SPA was sent to another program.

    Action

    Modify application programs.

  • XB

    Cause

    After sending the SPA to another program, the output message was sent to the originating terminal.

    Action

    Modify application programs.

  • X2

    Cause

    The destination of ALT-PCB is interactive transaction. The first ISRT call was not sent to the SPA.

    Action

    After the SPA is inserted, messages are inserted.

  • X3

    Cause

    As the SPA’s first 6-byte field has changed, it cannot be defined as the SPA message.

    Action

    Do not change SPA’s first 6 bytes.

  • X4

    Cause

    The SPA was sent using a transaction in which interactive processing is not defined.

    Action

    Request data messages, except for the SPA, to be inserted.

  • X5

    Cause

    Tried to send the SPA using the ISRT call, more than twice.

    Action

    Send a SPA to a message.

  • X6

    Cause

    Invalid transaction code for transmitting SPA through an ISRT call.

    Action

    Specify the destination using interactive transaction code that is registered in the MS system.