NMH1101
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : NO
NMH1101 SYNTAX ERROR IN CLASS-2-OPTION 'MSG(&00) = (&01)'. DEFAULT '(&02)' USED
Meaning
One of the class-2-options has an invalid value. The message handling uses
a default value, therefore the system is nevertheless able to run.
(&00): Name of the class-2-option (LPRI, CENTL)
(&01): Value generated for this class-2-option
(&02): Default value used :
(1) MSGLPRI = ED (First language is English,
second language is German).
(2) MSGCENTL = 128 (All the cache entries have a
standard length of 128 bytes).
Response
Generate the system again with valid values for the UGEN
statement PARAM.
NMH1102
Destination: USER-TASK, CONSOLE Routing code: A Weight: 30
Warranty : YES
NMH1102 MESSAGE OUTPUT FILE '(&00)', ACCESS=(&01), ACTION=(&02)
Meaning
This file has been included as message output file into the System Vector
Table (SVT) or into the Task Vector Table (TVT).
In general, this message output file is an ISAM file.
By STARTUP a message file can be declared as DLAM
file (cf. class-2-option MSGDLAM and message NMH1107).
In this case, the message output file is read into the
virtual memory and processed as an addressed ISAM file.
(&00): Fully qualified name of the message output file.
(&01): Used access method (ISAM, DLAM, DLAM+ISAM).
(&02): Action on this file (STARTUP, ADD, DEL, STD).
NMH1103
Destination: USER-TASK, CONSOLE Routing code: A Weight: 99
Warranty : YES
NMH1103 DMS ERROR CODE '(&01)' ON FILE '(&00)'
Meaning
During the access on file (&00), the DMS branched
to an EXLST exit and issued the error code (&01).
(&00): Fully qualified file name
(&01): DMS error code (from FCB).
Response
Check if the file is a messages-file or analyse the DMS error code.
NMH1104
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
NMH1104 Specified userid does not exist in home pubset
NMH1105
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
NMH1105 SYNTAX ERROR IN FILE NAME '(&00)'
Meaning
The Message Handling cannot recognize (&00) as the name of a message
output file.
Except for obvious syntax errors, this message is also issued
in the following case :
Class-2-options MSGFILi or the operator's reply to message NMH1107
contain(s) the name of a message file with a catalog name other
than "TSOS". Such an input is invalid because JOINMAN has not yet
been activated.
- (&00): fully qualified file name.
Response
(1) Enter the correct file name in the following console message NMH1107.
(2) Correct the class-2-options at the next system generation.
NMH1106
Destination: USER-TASK, CONSOLE Routing code: A Weight: 99
Warranty : YES
NMH1106 '(&00)' NO MESSAGE OUTPUT FILE
Meaning
The administration records of file (&00) are missing, incomplete or
have an invalid format
- (&00): fully qualified filename.
Response
If the specified file name was not correct, retry the action with
correct filename.
If the specified filename was correct, create the message output file
again, using the utility routine MSGLIB or MSGMAKER.
NMH1107
Destination: CONSOLE Routing code: R Weight: 98
Warranty : NO
NMH1107 ENTER NAME OF MESSAGE OUTPUT FILE. REPLY (EOT;END;<NAME>,ISAM/DLAM;<NAME>, ISAM/DLAM,END;<NAME>,END)
Meaning
This message is issued on console only during STARTUP. In this way,
the operator can define further message output files for the system.
This message is issued only in the following cases :
(1) Value of class-2-option MSGNOFL is binary zero.
(2) Values of class-2-options MSGNOFL, MSGDLAM, MSGFIL1,...
MSGFIL15 syntactically not correct or unconsistent.
(3) Specified file is no ISAM file or does not exist under userid TSOS.
(4) Administration records from specified file are not correct.
Response
The following replies are possible:
(1) <TSN>. No further questions will be output.
In case of an invalid MSGFIL<i>, the next
MSGFIL<i+1> will be analysed.
(2) <TSN>.END No further questions will be output.
In case of an invalid MSGFIL<i>, the next
MSGFIL<i+1> will not be analysed.
(3) <TSN>.<file name> The specified file will be established as
message output file with ISAM access +
eventual DLAM access.
Afterwards the question will be repeated.
(4) <TSN>.<file name>,ISAM The specified file will be established as
message output file with ISAM access.
Afterwards the question will be repeated.
(5) <TSN>.<file name>,DLAM The specified file will be established as
message output file with DLAM access.
The file will be read into virtual space
via PAM. Afterwards the question will be
repeated.
(6) <TSN>.<file name>,END Same as (3), but the question will not be
repeated, if no error occurred.
In case of an invalid MSGFIL<i>, the next
MSGFIL<i+1> will be analysed.
(7) <TSN>.<filename>,ISAM,END Same as (4), but the question will not be
repeated, if no error occurred.
In case of an invalid MSGFIL<i>, the next
MSGFIL<i+1> will be analysed.
(8) <TSN>.<filename>,DLAM,END Same as (5), but the question will not be
repeated, if no error occurred.
In case of an invalid MSGFIL<i>, the next
MSGFIL<i+1> will be analysed.
NMH1108
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1108 '(&00)' DOES NOT EXIST IN MESSAGE VECTOR TABLE
Meaning
There should be deactivated a message output file which is not
included in the System (SVT) or Task Vector Table (SVT).
- (&00): fully qualified file name.
Response
Try macro or command again with the correct file name.
NMH1109
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1109 '(&00)' ALREADY EXISTING IN MESSAGE VECTOR TABLE
Meaning
There should be added a message output file which is already
included in the System (SVT) or Task Vector Table (TVT).
- (&00): fully qualified file name.
Response
Try macro or command again with correct file name.
NMH1110
Destination: CONSOLE Routing code: R Weight: 99
Warranty : NO
NMH1110 NO CLASS 4 MEMORY AVAILABLE FOR THE MSG CACHE. MSG STARTUP ABORTED
Meaning
MSG startup aborted due to one of the following reasons :
1. Error in the class-2-options MSGCENTN or MSGCENTL.
2. No more class 4 memory available.
All the messages during this system-run will be issued with the
text 'MSG TASK NOT AVAILABLE'.
Response
Check class-2-options MSGCENTL and MSGCENTN.
NMH1111
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1111 INTERNAL ERROR DURING MESSAGE PROCESSING STARTUP
NMH1112
Destination: CONSOLE Routing code: R Weight: 30
Warranty : NO
NMH1112 MESSAGE PROCESSING READY
NMH1113
Destination: CONSOLE Routing code: R Weight: 99
Warranty : NO
NMH1113 MSG TASK COULD NOT BE CREATED. MSG STARTUP CONTINUES
Meaning
The message processing will continue without it but all the messages
will be issued with the text 'MSG TASK NOT AVAILABLE'.
NMH1114
Destination: CONSOLE Routing code: R Weight: 99
Warranty : NO
NMH1114 INVALID MSG FILE ACCESS METHOD. CORRECT REPLY TO MSG:'NMH1107'
Meaning
The file access type can only be 'ISAM' or 'DLAM'.
NMH1115
Destination: CONSOLE Routing code: R Weight: 99
Warranty : NO
NMH1115 NO CLASS 4 MEMORY AVAILABLE FOR THE VARIABLE CACHE. MSG STARTUP ABORTED
Meaning
No more class 4 memory available.
NMH1116
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
NMH1116 MIP parameter file contains an invalid first line '(&00)'
Meaning
If the first line of the MIP parameter file is not 'MIPPAR=SYSTEM', none
of the msgfiles found in the parameter file are activated.
Response
Correct the first line.
NMH1117
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
NMH1117 MIP parameter file contains invalid MSGFILE line '(&00)'
Meaning
The concerned line contains a syntax error. The syntax is 'MSGFILE=file
name'.
Response
Correct this line for the next startup.
NMH1118
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 99
Warranty : NO
NMH1118 Enter msg file name. Reply (EOT;<name>)
Meaning
This message is issued on console only during STARTUP when MIP activates
all the msgfiles found in the MIP parameter file. A msgfile is requested
if MIP receives a DMS error or if an invalid line is found in the
parameter file.
Response
Possible replies :
(1) <TSN>. No msgfile is activated.
(2) <TSN>.<filename> The given msgfile is activated
NMH1119
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : NO
NMH1119 NO CLASS 4 MEMORY AVAILABLE FOR LOCAL DLAM. MSG STARTUP ABORTED
NMH1120
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1120 MESSAGE TEXT FOUND IN 'SYSDLAM' OR 'LOCAL-DLAM'. NO FURTHER INFORMATION AVAILABLE
NMH1121
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1121 INTERNAL ERROR. COMMAND REJECTED
Meaning
Relevant diagnostic information can be contained in the SERSLOG file or
in the previous messages sent on console or on sysout.
Response
Contact system administrator.
NMH1122
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1122 MIP parameter file contains more than 255 msgfile names. Only 255 first ones are displayed
NMH1123
Destination: USER-TASK Routing code: Weight:
Warranty : YES
NMH1123 No more space available on userid to extend MIP parameter file '(&00)'. Parameter file not modified
Meaning
If a msgfile must be added in the parameter file, MIP tries to extend
the parameter file with 3 PAM pages. If this file can not be extended,
no operation on the parameter file are done.
Response
Erase some unuseful files and reenter the previous command.
NMH1124
Destination: USER-TASK Routing code: Weight:
Warranty : YES
NMH1124 MIP parameter file '(&00)' cannot be locked or unlocked
Meaning
To protect the parameter file, MIP locks it during a /MODIFY-MIP-
PARAMETERS. If MIP can not lock the parameter file, the modification in
the parameter file are not done.
Response
If the parameter file is locked by another task, please delock it and
reenter the previous command.
NMH1125
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1125 Error during processing of MIP parameter file
Meaning
You can find more information either in the serslog file or in the
previous sent messages on console.
NMH1126
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1126 Command or operand no longer supported
NMH1127
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1127 Enter a MIP parameter file name. Reply (EOT;<name>)
NMH1128
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1128 Warning : MIP is working without any parameter file
Meaning
Any further operation on the current parameter file will be rejected
with the message NMH1129.
NMH1129
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1129 Warning : Command not processed. No MIP parameter file is beeing used during this session
NMH1130
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : NO
NMH1130 WARNING : The USER-ACCESS of the system msgfile "(&00)" is not set to SPECIAL
Meaning
In order to have the full HELP function also available for user id
SERVICE, the USER-ACCESS of a system msgfile must be set to SPECIAL.
NMH1131
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1131 The USER-ACCESS of the msgfile "(&00)" can not be set to SPECIAL
Meaning
FSTAT error after reading the USER-ACCESS of the msgfile or CATAL error
after trying to set USER-ACCESS=*SPECIAL. The USER-ACCESS of a startup
msgfile must be set to SPECIAL to be available for the user id SERVICE.
Response
Try to set USER-ACCESS=*SPECIAL with the command MODIFY-FILE-ATTRIBUTES.
NMH1132
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : NO
NMH1132 The USER-ACCESS of the startup msgfile "(&00)" has been set to SPECIAL
Meaning
In order to be available for the user id SERVICE, the USER-ACCESS of a
startup msgfile is automatically changed to SPECIAL.
NMH1133
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1133 Temporary file can not be written in a MIP parameter file. Command is rejected
Meaning
At startup time, when MIP reads the parameter file, temporary files can
not be accessible. So, MIP rejectes all operations to write a temporary
file in a MIP parameter file.
NMH1134
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH1134 Dump requested by the command MODIFY-MIP-OPTION
NMH1150
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1150 COMMAND RESTRICTED TO SYSTEM ADMINISTRATOR. COMMAND REJECTED
NMH1151
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1151 TOO MANY CLOSING PARENTHESES. COMMAND NOT PROCESSED
NMH1152
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1152 UNKNOWN OR MULTIPLE OCCURRING OPERAND. COMMAND NOT PROCESSED
Response
Correct command and retry.
NMH1154
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1154 NO MEMORY AVAILABLE. COMMAND NOT PROCESSED
Meaning
No more memory can be requested, the desired function can therefore
not be performed.
Response
Release memory and repeat command.
NMH1155
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1155 INVALID MSGID
Meaning
Invalid message identifier specification in /HELP-MSG-INFORMATION
command.
Valid message identifiers consist of exact 4 or exact 7 characters.
Response
Correct command.
NMH1156
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1156 INVALID VALUE FOR 'INFORMATION' OPERAND. COMMAND NOT PROCESSED
Response
Correct command (valid values are F, C, D, M).
NMH1157
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1157 INVALID VALUE FOR 'LANGUAGE' OPERAND. COMMAND NOT PROCESSED
Response
Correct command (valid is only one alphabetical character).
NMH1158
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1158 ISP INTERNAL ERROR. COMMAND NOT PROCESSED
Response
Take diagnosis material and sent it to diagnosis staff.
NMH1161
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1161 MEANING : NO FURTHER INFORMATION
Meaning
No meaning text is available for the desired message number.
NMH1162
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1162 RESPONSE : NONE
Meaning
No response text is available for the desired message number.
NMH1165
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1165 DMS ERROR '(&01)' ON HELP-FILE '(&00)'
Response
Analyse DMS error code.
NMH1166
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1166 HELP-FILE '(&00)' DOES NOT EXIST
Meaning
The HELP-file belonging to the message output file is not cataloged
(The name of this HELP-file is noted in the message output file).
Response
Catalog the missing HELP-file.
NMH1174
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1174 SYNTACTICAL ERROR IN THE COMMAND. COMMAND NOT PROCESSED
Response
Repeat the command with the right syntax.
NMH1175
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1175 INVALID 'FILE' OPERAND. COMMAND NOT PROCESSED
Response
Correct command.
NMH1178
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1178 SAME COMMAND ALREADY PROCESSED. COMMAND IGNORED
NMH1180
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1180 FILE '(&00)' HAS BEEN ADDED
Meaning
The message output file (&00) has been added to the message handling
system.
- (&00): name of the message output file.
NMH1181
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1181 FILE '(&00)' COULD NOT BE PROCESSED
Meaning
The file (&00) couldn't be processed by the /MODIFY-MSG-FILE-ASSIGNMENT
or /MODIFY-MIP-PARAMETERS command.
The reason is specified by another message sent on console or sysout.
Response
Correct command.
NMH1182
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1182 FILE '(&00)' NOT PROCESSED
Meaning
The file (&00) has not been processed by the /MODIFY-MSG-FILE-ASSIGNMENT
or /MODIFY-MIP-PARAMETERS command because of an error in processing file.
Response
Correct command.
NMH1183
Destination: USER-TASK Routing code: Weight: 99
Warranty : YES
NMH1183 FILE '(&00)' HAS BEEN REMOVED
Meaning
The message output file (&00) has been removed from the message handling
system.
- (&00): name of the message output file.
NMH1199
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH1199 THE MANDATORY OPERAND IS MISSING OR INVALID
NMH5000
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5000 ILLEGAL STATEMENT
Meaning
The last entered statement for the message editor is illegal.
NMH5001
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5001 SYNTAX ERROR IN '(&00)' STATEMENT
NMH5005
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5005 MESSAGE PRIMARY FILE MISSING. FIRST GIVE 'OPEN' STATEMENT
Meaning
The last statement can only be processed after an 'OPEN' statement was
entered first.
NMH5010
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5010 PROGRAM TERMINATED ABNORMALLY DUE TO USER ERROR IN BATCH MODE
NMH5050
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5050 FILE NAME MISSING
Meaning
The name of the file, which is to be processed, has not been entered.
Response
Enter the name of the file, which is to be processed, via OPEN statement,
and repeat the last statement.
NMH5052
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5052 ACCESS ON FILE (&00) RETURNS DMS ERROR CODE (&01)
Meaning
The access on file (&00) by FSTAT-, FILE-, OPEN-macro returns DMS error
code (&01).
Response
Search for reason of DMS error code and repeat correct instruction.
NMH5053
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5053 FILE (&00) IS LOCKED
Meaning
The file (&00) is locked. Perhaps another user is using this file.
NMH5054
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5054 FILE '(&00)' IS LOCKED BY PASSWORD OR ACCESS=READ
Response
Remove file protection by /ADD-PASSWORD or /MODIFY-FILE-ATTRIBUTES
command.
NMH5055
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5055 FILE NOT CATALOGED OR INVALID POSITION OF OPERAND
Meaning
The file specified in last entered statement is not contained in the
catalog, or the position of the operand is inconsistent.
Response
Enter this file into the catalog and repeat the incorrect statement,
or correct the statement.
NMH5056
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5056 FILE '(&00)' IS THE SAME AS WORK FILE. INPUT FILE IGNORED
Meaning
File (&00) was already specified in OPEN instruction. It is not used
as input file.
NMH5057
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5057 FILE (&00) IS EMPTY
NMH5060
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5060 FILE (&00) NOT SHAREABLE
Response
Ask file owner to make file shareable.
NMH5065
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5065 FILE (&00) IS NOT A VALID MESSAGE PRIMARY FILE
Meaning
The file is not a message primary file.
(Correct file parameters are: FCBTYPE=ISAM, RECFORM=V, KEYPOS=5,
KEYLEN=10).
Response
Because probably a wrong file name has been entered, repeat the above
statement with the correct name.
NMH5066
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5066 MESSAGE FILE '(&00)' IN NEW FORMAT. MSGEDIT CAN'T PROCESS THIS FILE
Meaning
This format of message file can't be processed by MSGEDIT and MSGLIB.
Response
Use MSGMAKER to process the file.
NMH5105
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5105 MESSAGE UNIT (&00) ALREADY EXISTING
Meaning
There does already exist a message unit with this message identifier in
this message primary file.
(&00): message identifier.
Response
Either the message unit concerned has to be deleted in this message
primary file or it has to be changed by the MODIFY instruction of the
message editor.
NMH5110
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5110 MESSAGE UNIT (&00) DOES NOT EXIST
Meaning
A message unit with this message identifier does not exist in the message
primary file.
NMH5115
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5115 MESSAGE IDENTIFIER (&00) NOT IN RANGE
Meaning
The message identifier (&00) doesn't match with any of the message
identifier ranges of this message primary file.
(&00): message identifier.
Response
Add a suitable message identifier range into this message primary file via
RESERVE statement.
NMH5129
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5129 ERROR IN THE RANGE (&00)
Meaning
- The range (&00) is distributed on more than one class.
- The range limits must belong to the same class.
(&00): message identifier range.
Response
Check input and repeat correct instruction.
NMH5130
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5130 SYNTAX ERROR IN MESSAGE IDENTIFIER RANGE (&00)
Meaning
The value for the message identifier range (&00) is syntactically wrong.
(&00): value of the IDRANGE or IDENTIFIER operand.
NMH5131
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5131 RANGE '(&00)' OVERLAPS RANGE '(&01)'
NMH5132
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5132 RANGE '(&00)' MISSING
Meaning
The message range (&00) is missing in the workfile (OPEN-statement).
NMH5134
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5134 MESSAGE RANGE STILL CONTAINS MESSAGE UNITS. 'RESERVE'-STATEMENT NOT PROCESSED
Meaning
Before a message range can be deleted or reduced, all message units
existing in it have to be deleted.
NMH5136
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5136 RANGE '(&00)' OF FILE '(&01)' OVERLAPS RANGE '(&02)' OF FILE '(&03)'
Meaning
In a MERGE statement, none of the message ranges of the files to be
merged may overlap.
- (&00): 1. message range
- (&01): 1. input file
- (&02): 2. message range
- (&03): 2. input file.
Response
Correct statement.
NMH5150
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5150 LANGUAGE SPECIFICATION MISSING
Meaning
The specification of the language for the text is missing.
Response
Repeat the input with the correct language.
NMH5151
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5151 TEXT OF MESSAGE NOT SPECIFIED
Meaning
When adding a message, the text of the message is mandatory when the
language is specified.
Response
Correct the command and retry.
NMH5152
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5152 INVALID LANGUAGE VALUE
Meaning
The value for the operand LANGUAGE is invalid.
Response
Repeat the input with a correct LANGUAGE-value
(valid is only a single alphabetical character).
NMH5190
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH5190 NO MORE SPACE AVAILABLE
Meaning
The handling of the actual file can not be continued because of shortness
of space.
NMH6000
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6000 ILLEGAL STATEMENT
Meaning
The last entered statement for the message librarian is illegal.
NMH6001
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6001 SYNTACTICAL ERROR IN STATEMENT
Meaning
The last entered statement for the message librarian is syntactically
incorrect.
NMH6005
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6005 NO ACTION MODE SPECIFIED OR SECOND ACTION STATEMENT NOT ALLOWED OR INVALID STATEMENT FOR CURRENT ACTION MODE
Meaning
1) No ACTION statement given.
2) A second ACTION statement is entered with a first one already active.
3) The last entered statement is incompatible with the current ACTION
mode. See manual for more details.
Response
1) Give an ACTION MODE=CREATE|UPDATE|ERASE|MODIFY statement before this
one.
2) Use the INITIALIZE statement before giving a new ACTION one.
NMH6010
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6010 ABNORMAL END BECAUSE OF USER ERROR IN BATCH JOB
Meaning
The message librarian has been abnormally ended because of an incorrect
input. An interactive correction is not possible in a Batch job.
NMH6011
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6011 OUTPUT FILE WITH TYPE (&00) MISSING
Meaning
The message output file with type (&00) is missing.
Insert (&00): type of message output file (MSG,HELP,BAMR,BAMP).
Response
Enter OUTFILE statement for this message output file, and after that
repeat above statement.
NMH6012
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6012 INFILE STATEMENT MISSING OR ILLEGAL ACCESS IN THE RANGE
Meaning
- Within a step with MODE=CREATE has no INFILE-statement been entered.
- The file specified in the INFILE command contains all records with
ACCESS=NONE.
Response
- Enter a INFILE statement and repeat the above statement.
- Correct the access value for the range by means of the RESERVE command.
NMH6030
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6030 FILE (&00) NOT CATALOGED
Meaning
The input file (&00) isn't cataloged.
(&00): name of the input file concerned.
Response
Because probably there has been entered a wrong file name, repeat the
input with the correct file name.
NMH6031
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6031 FILE (&00) NO MESSAGE PRIMARY FILE
Meaning
The file (&00) is no message primary file (perhaps invalid administration
records).
Response
Check file and file name.
NMH6032
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6032 SYNTAX ERROR IN (&01) (&00)
Meaning
(&00): value of the IDRANGE- or IDENTIFIER- or CLASS-PARAMETER.
(&01): word 'IDRANGE' or 'IDENTIFIER' or 'CLASS'.
Response
Repeat the correct instruction.
NMH6034
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6034 RANGE '(&00)' OVERLAPS RANGE '(&01)'
Response
Correct statement.
NMH6035
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6035 RANGE (&00) OVERLAPS RANGE (&01) IN INPUT FILE (&02)
Meaning
The message identifier range (&00) of the input overlaps the message
identifier range (&01) of the input file (&02).
(&00): message identifier range
(&01): message identifier range
(&02): name of the input file.
Response
Repeat correct instruction.
NMH6036
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6036 (&02) (&00) MISSING IN FILE (&01)
Meaning
(&02) (&00) is missing in the input file (&01).
(&00): message identifier range or class number.
(&01): name of the input file.
(&02): word 'IDRANGE' or 'IDENTIFIER' or 'CLASS'.
Response
Check input and input file and repeat correct instruction.
NMH6038
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6038 TEXT IN LANGUAGE '(&00)' MISSING IN FILE '(&02)' FOR RANGE '(&01)'
Response
Correct statement.
NMH6039
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6039 NO TEXT IN ANY OF THE DESIRED LANGUAGES EXISTS FOR THE RANGE (&00) IN THE FILE (&01)
Meaning
There doesn't exist any text in one of the desired languages for the
message identifier range (&00) in the input file (&01).
This message identifier range is not entered into the output files.
(&00): message identifier range
(&01): name of the input file.
NMH6040
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6040 'INFILE' INSTRUCTION WITHOUT RANGE, BUT WITH MODE=EXCLUDE IGNORED
Meaning
An INFILE instruction without message identifier range, but with
MODE=EXCLUDE is invalid.
The instruction is ignored.
NMH6041
Destination: USER-TASK Routing code: Weight: 98
Warranty : NO
NMH6041 RANGE (&00) EXISTS IN INPUT FILE 1 (&01) AND IN INPUT FILE 2 (&02). WHICH IS RELEVANT? REPLY (1,2)
Meaning
The message identifier range (&00) does either exist in the input file no.
1 (&01), either in the input file no. 2 (&02). Which of these is to be
used for the output file?
(&00): message identifier range
(&01): 1. input file
(&02): 2. input file.
Response
Enter the number (1 or 2) of the input files, which shall be used by the
librarian.
NMH6042
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6042 RANGE (&00) EXISTS EITHER IN FILE (&01), EITHER IN FILE (&02)
Meaning
The message identifier range (&00) exists either in the input file (&01),
either in the input file (&02). The instruction has been ended.
(&00): message identifier range
(&01): 1. input file
(&02): 2. input file.
Response
Repeat correct instruction.
NMH6043
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6043 RANGE (&00) OF FILE (&01) OVERLAPS RANGE (&02) OF FILE (&03)
Meaning
The message identifier range (&00) in the input file (&01) overlaps the
message identifier range (&02) in the input file (&03).
(&00): 1. message identifier range
(&01): 1. input file
(&02): 2. message identifier range
(&03): 2. input file.
Response
Repeat correct instruction.
NMH6044
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6044 RANGE '(&00)' DOES NOT HAVE '(&01)' ACCESS
Meaning
(&00): message range.
(&01): access method.
NMH6050
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6050 INPUT FILE IS EMPTY
Response
Correct statement.
NMH6051
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6051 FILE IS LOCKED OR ACCESS=READ
Meaning
The file, which name has been entered, is locked (perhaps an other user
has this file in use) or the file is protected by ACCESS=READ.
Response
If ACCESS=READ: remove the file protection by /MODIFY-FILE-ATTRIBUTES cmd.
NMH6060
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6060 NO FILE SPECIFIED IN 'DISPLAY' OR 'PRINT' STATEMENT
NMH6061
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6061 'PRINT' OR 'DISPLAY' STATEMENT NOT PROCESSED WHILE 'CREATE' MODE STILL ACTIVE
Response
Leave the MODE=CREATE, using the INITIALISE statement and repeat the
statement.
NMH6070
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6070 PARTIALLY QUALIFIED FILE NAME NOT ALLOWED
Response
Correct file name.
NMH6071
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6071 OUTPUT FILE OF TYPE (&00) ALREADY SPECIFIED
Meaning
The output file of the type (&00) has already been specified. This
instruction is ignored.
(&00): type of the output file (MSG, HELP, BAMR, BAMP).
NMH6072
Destination: USER-TASK Routing code: Weight: 98
Warranty : NO
NMH6072 OUTPUT FILE OF TYPE '(&00)' ALREADY SPECIFIED. OVERWRITE? REPLY (Y=YES; N=NO)
Meaning
- (&00): type of the output file (MSG, HELP, BAMR, BAMP).
Response
- Y : This last specified file name will be used.
- N : The previous file name specification remains in use.
NMH6073
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6073 FILE '(&00)' NOT SHAREABLE
Meaning
- (&00): file name.
Response
Ask file owner to make file sharable.
NMH6074
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6074 DMS ERROR '(&01)' DURING ACCESS ON FILE '(&00)'
Meaning
Access on file (&00) by FSTAT, FILE, OPEN macro returns DMS error
code (&01).
(&00): file name
(&01): DMS error code.
Response
Analyse DMS error code and correct statement.
NMH6075
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6075 OUTPUT FILE '(&00)' ALREADY CATALOGED
Meaning
- (&00): name of the output file.
NMH6076
Destination: USER-TASK Routing code: Weight: 98
Warranty : NO
NMH6076 OUTPUT FILE ALREADY CATALOGED. OVERWRITE DESIRED? REPLY (Y=YES; N=NO)
Response
Y : output file is overwritten.
N : output file will not be overwritten. Statement not processed.
NMH6078
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6078 INVALID OUTPUT FILE OF TYPE (&00)
Meaning
The output file (&00), specified above, doesn't have the file parameters,
suitable for a message output file.
(&00): name of the output file.
Response
Check the output file and the name of this file and re-enter the correct
instruction.
NMH6079
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6079 CREATION OF FILE '(&00)' NOT POSSIBLE. DMS ERROR CODE '(&01)'
Meaning
- (&00): name of the file
- (&01): DMS error code.
Response
Analyse DMS error.
NMH6080
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6080 FILE IS PROTECTED BY PASSWORD OR 'ACCESS=READ'
Response
Remove file protection by means of /ADD-PASSWORD or
/MODIFY-FILE-ATTRIBUTES
command.
NMH6081
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6081 FILE ALREADY SPECIFIED AS INPUT FILE
Meaning
The file, specified above, has already been specified as an input file.
Response
Check the input and re-enter the correct instruction.
NMH6082
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6082 FOR ACTION MODE=UPDATE/ERASE ONLY MESSAGE OUTPUT FILE NECESSARY
Meaning
For a step with ACTION=UPDATE or =ERASE only the message output file
(TYPE=MSG) has to be specified. The related HELP-file is specified in this
file.
NMH6083
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6083 OUTPUT FILE OF TYPE '(&00)' IS NOT CATALOGED
Meaning
For a MSGLIB step with MODE=UPDATE or =ERASE, the message output file
or the HELP-file found out by MSGLIB is not cataloged.
Response
Specify a HELP-file or another message output file.
NMH6084
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6084 NONE OR INVALID INFORMATION IN MESSAGE OUTPUT FILE (TYPE=MSG)
Meaning
The message output file (TYPE=MSG) contains none or invalid administration
records. The processing of this file is cancelled.
Response
Check the message output file.
NMH6085
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6085 INVALID OR INCONSISTENT INFORMATION IN MESSAGE FILES
Meaning
The message work files contain invalid administration records, or they are
inconsistent. The processing of these files is cancelled.
Response
Check the message work files (HELP-file and message output file).
NMH6086
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6086 FILE (&00) OF TYPE (&01) CANNOT BE ERASED
Meaning
The file (&00) of the type (&01) cannot be erased because of $USERID.
(&00): file name
(&01): type of the output file (MSG, HELP, BAMR, BAMP).
NMH6090
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6090 MESSAGE IDENTIFIER (RANGE) (&00) MISSING IN 'IDRANGE'
Meaning
The message identifier (range) (&00) is not contained in any of the
ranges, entered via IDRANGE. The statement is cancelled.
NMH6091
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6091 'LANGUAGE' ONLY VALID FOR COMPLETE RANGES
Meaning
The LANGUAGE operand is only valid for complete message identifier ranges,
not for single identifiers or incomplete ranges.
The statement is cancelled.
NMH6120
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6120 NO FURTHER SPACE AVAILABLE
Meaning
The handling of the actual file cannot be continued because of shortness
of space. The status of this file is undefined.
NMH6129
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6129 DISCREPANCY BETWEEN THE MSG- AND THE HELP-FILE FOR THE MESSAGE (&00) IN LANGUAGE (&01)
Meaning
The MSG-file and the HELP-file have been created from two different
primary files. The message (&00) has been tried to be modified but
this one didn't exist in the MSG-file.
(&00): message identifier.
(&01): language key.
Response
No action must be taken, the message has been modified in the HELP- and
MSG-file and the error doesn't longer occur for this message.
NMH6130
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6130 INVALID RECORD TYPE (&02) IN MESSAGE UNIT (&01) OF THE INPUT FILE (&00)
Meaning
In input file (&00) there has been detected an invalid record type (&02)
for the message unit (&01). This record has been ignored.
Response
Check this message unit in the input file.
NMH6131
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6131 ATTRIBUTE RECORD FOR MESSAGE UNIT (&00) MISSING
Meaning
The attribute record for the message unit (&00) is missing.
This message unit has been ignored.
Response
Check this message unit in the input file.
NMH6132
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6132 ATTRIBUTE RECORD FOR MESSAGE (&00) DEFECT
Meaning
The attribute record of the message unit (&00) is incorrect.
The message unit gets default values for the message attributes.
NMH6133
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6133 INVALID MESSAGE IDENTIFIER (&00)
Meaning
The message identifier (&00) doesn't follow the 'Guidelines for Creation
of Messages'. This message unit is ignored.
(&00): message unit.
Response
Check this message unit in the input file.
NMH6134
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6134 NO TEXT FOR MESSAGE (&00)
Meaning
There doesn't exist a text in any of the desired languages for the message
unit (&00).
- (&00): message identifier.
NMH6135
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6135 INVALID LANGUAGE KEY IN MESSAGE (&00)
Meaning
Invalid language key in message unit (&00). This text is ignored.
- (&00): message identifier.
Response
Check this message unit in the input file.
NMH6136
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6136 NO TEXT IN LANGUAGE (&01) FOR MESSAGE (&00)
Meaning
There doesn't exist a text in the language (&01) for the message unit
(&00).
- (&00): message identifier
- (&01): language key.
Response
Check this message unit in the input file.
NMH6140
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6140 INVALID WEIGHT (&01) IN MESSAGE (&00)
Meaning
There is a bad weight code (&01) in the message unit (&00).
- (&00): message identifier
- (&01): weight code.
Response
Check this message unit in the input file or change the
weight code in the MODIFY statement.
NMH6141
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6141 INVALID ROUTING CODE X'(&00)' IN MESSAGE (&01). ROUTING CODE IGNORED
NMH6142
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6142 INVALID MANUAL CODE X'(&00)' IN MESSAGE '(&01)'. DEFAULT 'USER' IS USED
NMH6143
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6143 INVALID 4-BYTE-IDENTIFIER X'(&00)' IN MESSAGE '(&01)'. VALUE IGNORED
NMH6144
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6144 INVALID ACCESS METHOD X'(&00)' IN MESSAGE '(&01)'. DEFAULT 'ISAM' IS USED
NMH6145
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6145 INVALID INFORMATION X'(&00)' IN MESSAGE (&01) FOR THE LANGUAGE (&02)
Meaning
The error is probably due to a bad manipulation of the message file.
The processing of this message isn't done.
(&00): value of the invalid information.
(&01): message identifier.
(&02): language key.
Response
Check the message text of this message unit in the input file.
Delete the message and re-enter the correct one.
NMH6151
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6151 MORE THAN 15 INSERTS IN MESSAGE '(&00)' FOR LANGUAGE '(&01)'
Meaning
The surplus inserts are stored as text.
- (&00): message identifier
- (&01): language key.
Response
Check the message text of this message unit in the input file.
NMH6152
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6152 INVALID INSERT '(&00)' IN MESSAGE '(&01)' FOR LANGUAGE '(&02)'
Meaning
(&00): insert number
(&01): message identifier
(&02): language key
- *1 If syntactical error: this insert has been stored as text.
Check the text of this unit in the input file.
- *2 If length too long: this insert has been stored normally but an
error can occur if it is used with the maximal length
(max. length= 180).
Response
Check the text of this message unit in the input file.
NMH6153
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6153 DUPLICATE KEY FOR MESSAGE '(&00)'
Meaning
Several text records for the same message, or file with duplicate key
allowed.
Response
Correct the file and retry the statement.
NMH6154
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6154 SYNTAX ERROR IN MESSAGE '(&00)'
Meaning
The text of the message is not correct,
e.g. an insert definition is not complete.
Response
Correct the text and retry.
NMH6155
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6155 DUPLICATE KEY '(&00)' IN FILE '(&01)'. STATEMENT NOT PROCESSED
Meaning
The error is probably due to an invalid modification of the message file.
(&00): duplicate key.
(&01): name of the message file.
Response
Delete record with duplicate key and repeat the statement.
NMH6157
Destination: USER-TASK Routing code: Weight: 98
Warranty : NO
NMH6157 MORE THAN ONE INDEX BLOCK IN MESSAGE OUTPUT FILE. CONTINUE? REPLY (Y=YES; N=NO)
Meaning
ISAM requires more than one index block in the message output file
(TYPE=MSG). The result is a loss of performance when accessing this file.
Response
- Y: The creation of the message output file continues.
The indexes are spread onto several index blocks.
- N: The creation of the message file is terminated. As there
is already more than one index block, enter INFILE command with
less CLASSES or less RANGES.
NMH6158
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6158 MORE THAN 36 CSECTS FOR THE SAME CLASS. RANGE (&00) NOT ACCEPTED
Meaning
The messages in range (&00) are not taken into account for
the creation of the BAMP-BAMR-CSECT because there are already 36 CSECTS.
(&00): message range.
Response
Check the number of ranges for this class in the input file.
NMH6159
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH6159 WARNING: MORE THAN ONE INDEX BLOCK IN MESSAGE OUTPUT FILE (TYPE=MSG)
Meaning
ISAM needs more than one index block in message output file (TYPE=MSG).
The result is a loss of performance when accessing this file.
The processing is aborted.
Response
As there is already more than one index block, the user can restart the
processing:
- giving less CLASSES or less RANGES (INFILE statement)
- or enforcing the creation of the message output file (previous statement
OPTION LET=YES).
NMH9001
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9001 MIP TASK NOT AVAILABLE
Meaning
The MSG task is for another task not available or doesn't exist.
Response
New startup.
NMH9002
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9002 UNABLE TO CREATE THE MIP TASK
NMH9003
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9003 IF THE MESSAGE IS SENT IN A BCAM BUFFER, ANOTHER DESTINATION IS NOT ALLOWED
NMH9004
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9004 CLOSE ERROR ON A MSG-FILE
NMH9005
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9005 CLOSE ERROR ON A HELP-FILE
NMH9006
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9006 ERROR DURING DMS-ACCESS TO HELP-FILE
NMH9007
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NMH9007 Error during access to parameter-list
NMH9008
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9008 PROBLEM WITH THE $APCB MACRO
NMH9009
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9009 UNEXPECTED 'RDTFT' RETURN CODE
Meaning
Error occurred in the processing to complete a file name.
NMH9010
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9010 UNABLE TO REQUEST CLASS 4 MEMORY
NMH9011
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9011 UNABLE TO REQUEST CLASS 5 MEMORY
NMH9012
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9012 UNABLE TO RELEASE CLASS 4 MEMORY
NMH9013
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9013 UNABLE TO RELEASE CLASS 5 MEMORY
NMH9014
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9014 BOURSE INTERFACE ERROR
Meaning
Unexpected return code after a bourse call between calling task
and MSG task or by the creation or the suppression of the different
bourses used in the message processing.
NMH9015
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9015 UNABLE TO SET USERID TSOS INTO SRPM DATABASE
NMH9016
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9016 PROBLEM WITH A SYSTEM INTERFACE
NMH9017
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9017 ERROR DURING PRODUCTION OF S-VARIABLES FOR COMMAND- OR PROGRAM OUTPUT
Meaning
An error occurred during a SDF-P interface call.
NMH9018
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NMH9018 ERROR DURING PRODUCTION OF S-VARIABLES FOR MESSAGE OUTPUT
Meaning
An error occurred during a SDF-P or VAS interface call.