Messages

Edit online
When the exit detects an error it directs the assembler to issue message ASMA940U and the assembly stops. The following text might be included in the ASMA940U message:
  • SYSADATA exit not coded at same level of interface definition (3) as Assembler

    The exit uses version 3 of the exit definition, but the assembler uses a different version.

  • SYSADATA exit called for other than SYSADATA

    The exit was invoked with a valid type, but the type is not one that the exit can process. This is probably caused by an incorrect ADEXIT() suboption of the EXIT assembler option.

  • SYSADATA exit not initialized, and not entered for OPEN

    The exit has not yet been initialized, but was not entered with an OPEN request (action=0). There might be a failure in communication between the assembler and the exit.

  • SYSADATA exit initialized, but was entered for OPEN

    The exit has been initialized, but was unexpectedly entered with an OPEN request (action=0). There might be a failure in communication between the assembler and the exit.

  • SYSADATA exit - Invalid action or operation type requested

    An action was requested that is inconsistent with the type of action the exit is able or was expecting to take. There might be a failure in communication between the assembler and the exit.

  • SYSADATA exit - Supplied parameters contain a syntax error

    While parsing the supplied parameter string the exit has detected a syntax error. This is probably caused by an incorrect specification of parameters on the ADEXIT(ASMAXADR(parameter-string)) suboption of the EXIT assembler option.

  • SYSADATA exit expecting input record, zero buffer length found

    The exit was expecting an input record, but the record length was zero. There might be a failure in communication between the assembler and the exit.