MPLIR05300 - MPLIR05319

MPLIR05307W Condition condition-name raised.
A PL/I Condition was raised for which no ONUNIT was coded and with an Implicit Action of issue a message and continue.
MPLIR05308E Condition condition-name raised.
SNAP was specified on the ON-unit for the condition condition-name requesting diagnostic information to be printed when the condition is raised.
MPLIR05309E ONCODE 99140: The UNDEFINEDFILE condition was raised because a DD statement was not used in (FILE=dd-name).
At OPEN time it has not been possible to associate the logical FILE with a physical file.
MPLIR05310S Unable to allocate memory. byte-count bytes were requested.
MPLIR05311E Condition ERROR raised. insert-name.
MPLIR05312E Condition ERROR raised.
Either a SIGNAL ERROR statement has been executed, or a condition has been raised for which there is no ON-unit established and the implicit action is to raise the ERROR condition (for example, CONVERSION, ENDFILE, etc.), or a condition has been raised for which an ON-unit has been established and the normal return is to raise the ERROR condition (for example, SUBSCRIPTRANGE), or as a result of an error during program execution for which no other condition is defined (for example, protection violation).
MPLIR05313E Error(insert-name)
A PL/I RTS error has occurred as a result of an unhandled FILE condition such as KEY(), RECORD, etc. .
MPLIR05314E insert-name
A PL/I RTS error has occurred.
MPLIR05315I insert-name on
An error occurred while attempting the file IO operation shown in the message. .
MPLIR05316I FILE "file-name"
An error occurred while attempting to utilize the FILE shown in the message. .
MPLIR05317E FETCHABLE "entry-name" not found. ONCODE=9250.
An attempt has been made to FETCH a program whose entry point is not found. .
MPLIR05318I at PC
MPLIR05319I for
An error has occurred accessing this file.

Parent topic: MPLIR - PL/I Runtime Messages