NET/MASTER Messages Manual

2197: ZNNM-EVT-BAD-DB-REC
Event-Message Tokens
106159 Tandem Computers Incorporated 4–69
ZNNM-TKN-BAD-DB-CODE
tells what is wrong with the record and contains:
the value one, indicating that the format of the MDO header is bad. It does
not have the proper item code, or its length is wrong.
the value two, indicating that one of the items that is supposed to be a
command authority number is not a valid integer (in character form).
the value three, indicating that the field that is supposed to contain the length
of the startup parameter string (in character form) is not a valid integer.
ZNNM-TKN-UTILITY-NAME
contains the name of the utility that is the subject of the inquiry when the error
occurred. It appears as name in the message text.
ZNNM-TKN-UTILITY-TYPE
contains the type of the utility that is the subject of the inquiry when the error
occurred. It can be:
O for an OPSYS utility.
P for a PROGRUN utility.
S for a special record rather than a utility. Special records are used to hold the
command authority for unrestricted PROGRUN access, and the list of users
that are allowed to update the Utility Access database. It appears as type in
the message text.
ZNNM-TKN-XFILENAME
contains the name of the file in which the bad record appears. It appears as
filename in the message text.
ZNNM-TKN-BAD-TEXT
is present only when ZNNM-TKN-BAD-DB-CODE has the value two or three. It is
the text the program tried to interpret as a number. It appears as text in the
message text.