HP 3000 Manuals HP 3000 Manuals
SNA NRJE Error Messages (continued)
---------------------------------------------------------------------------------------
131 MESSAGE STOP OR HALT IS INVALID IF WORKSTATION IS NOT
ACTIVE. (INT=131)
CAUSE The workstation may not have been started or
another NRJE manager may have already stopped or
halted the workstation.
ACTION
---------------------------------------------------------------------------------------
132 MESSAGE UNABLE TO OBTAIN A LIST OF ACTIVE LUS. (SEV=132)
CAUSE
ACTION
---------------------------------------------------------------------------------------
133 MESSAGE STOP OR HALT CODE IS NOT 0 OR 1. (INT=133)
CAUSE The StopCode parameter passed to the NRJEStopWS
intrinsic is out of range.
ACTION Correct the StopCode parameter value.
---------------------------------------------------------------------------------------
134 MESSAGE LU IS NOT ACTIVE. (INT=134)
CAUSE An attempt was made to deactivate an LU that is not
active.
ACTION
---------------------------------------------------------------------------------------
135 MESSAGE LU NAME MUST BE SPECIFIED SINCE WORKSTATION IS
ACTIVE. (INT=135)
CAUSE Attempt to start workstation was made but it is
already active.
ACTION
---------------------------------------------------------------------------------------
136 MESSAGE UNABLE TO OBTAIN A LIST OF CONFIGURED LUS.
(INT=136)
CAUSE Possible configuration error.
ACTION Check configuration file for correctness and retry.
---------------------------------------------------------------------------------------
137 MESSAGE NUMBER OF LUS INPUT IS !. IT MUST BE BETWEEN 1 AND
!. (INT=137)
CAUSE The MaxEntries parameter passed to the NRJELUList
intrinsic was out of range. The first ! parameter
of the message is the MaxEntries value. The second
! parameter of the message is the upper limit.
ACTION
---------------------------------------------------------------------------------------
139 MESSAGE INPUT LU NAMES ARE DUPLICATED. (INT=139)
CAUSE An LU name appears more than once in the list.
ACTION Delete duplicate LU names from the list.
---------------------------------------------------------------------------------------
140 MESSAGE NRJE2SUBMIT CONFIGURATION ACCESS ERROR. (INT=140)
CAUSE
ACTION Check configuration file - error occurred reading
job entry subs.
---------------------------------------------------------------------------------------
141 MESSAGE INPUT FILE RECORD SIZE EXCEEDS MAXREC PARM
(DEFAULT=80). (INT=141)
CAUSE Input or ##FD file is wider than MAXREC (default
MAXREC=80).
ACTION
---------------------------------------------------------------------------------------
142 MESSAGE MAXREC 128 SPECIFIED. 128 (POWER MAXIMUM) USED.
(INT=142)
CAUSE MAXREC parm to NRJE3Submit was too big for
VSE/POWER.
ACTION
---------------------------------------------------------------------------------------
143 MESSAGE MAXREC 252 SPECIFIED. 252 (JES/512 BYTE RU MAX)
USED. (INT=143)
CAUSE MAXREC parm to NRJE3Submit was too big for JES
using a 512 byte RU.
ACTION
---------------------------------------------------------------------------------------
144 MESSAGE MAXREC 248 SPECIFIED. 248 (JES/256 BYTE RU MAX)
USED. (INT=144)
CAUSE MAXREC parm to NRJE3Submit was too big for JES
using a 256 byte RU.
ACTION
---------------------------------------------------------------------------------------
145 MESSAGE MAXREC 80 SPECIFIED. 80 USED. (INT=145)
CAUSE MAXREC parms 80 bytes aren't allowed by
NRJE3Submit.
ACTION
---------------------------------------------------------------------------------------
146 MESSAGE MAXREC MUST BE GREATER THAN 0. (INT=146)
CAUSE Negative MAXREC parms to NRJE3Submit aren't
allowed.
ACTION
---------------------------------------------------------------------------------------
150 MESSAGE ONE OF THE PARAMETERS IS OUT OF BOUNDS: SEG#!, P=!.
(INT=150)
CAUSE At least one of the parameters passed to
NRJEHJCancel is not within the user's stack. SEG#!
(code segment #) and P=! (program counter)
represent the return address right after the
intrinsic call.
ACTION The caller should check all of the parameters
passed to the intrinsic, correct the one in error,
and redo.
---------------------------------------------------------------------------------------
151 MESSAGE USERNAME MUST BE BETWEEN 1 AND 17 CHARACTERS.
(INT=151)
CAUSE The username length passed to NRJEHJCancel was not
between 1 and 17. No jobs were cancelled.
ACTION Correct and reissue.
---------------------------------------------------------------------------------------
152 MESSAGE USERNAME OR JOBLIST MUST BE SPECIFIED. (INT=152)
CAUSE Neither a username nor a joblist was passed to
NRJEHJCancel. No jobs were cancelled.
ACTION Correct and reissue. Check UserNameLen and
JobListLen to make sure that they are not both
equal to 0.
---------------------------------------------------------------------------------------
153 MESSAGE ERROR LOCKING JOBLOG IN NRJEHJCANCEL. (INT=153)
CAUSE File system related error. A file system error msg
will appear after this message. Some jobs may not
have been cancelled.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
154 MESSAGE FFINDBYKEY ERROR IN NRJEHJCANCEL. (INT=154)
CAUSE File system related error. A file system error msg
will appear after this message. Some jobs may not
have been cancelled.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
155 MESSAGE ERROR READING FROM JOBLOG IN NRJEHJCANCEL.
(INT=155)
CAUSE File system related error. A file system error msg
will appear after this message. Some jobs may not
have been cancelled.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
156 MESSAGE USERNAME DOESN'T MATCH LOGON - NM CAPABILITY
REQUIRED. (INT=156)
CAUSE NM capability is required to cancel jobs submitted
by other users. No jobs were cancelled.
ACTION Correct the problem and reissue.
---------------------------------------------------------------------------------------
157 MESSAGE INVALID USERNAME. (INT=157)
CAUSE Only @ and UserName.AcctName are valid usernames to
cancel jobs by. No jobs were cancelled.
ACTION Correct and reissue.
---------------------------------------------------------------------------------------
158 MESSAGE CONFIGURATION ACCESS ERROR. (INT=158)
CAUSE A configuration error may have taken place. No
jobs were cancelled.
ACTION Check NRJE configuration file.
---------------------------------------------------------------------------------------
159 MESSAGE ERROR OPENING JOBLOG IN NRJEHJCANCEL. (INT=159)
CAUSE File system related error. A file system error
message will appear after this message. No jobs
were cancelled.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
160 MESSAGE ERROR READING JOBLOG FILE LABEL IN NRJEHJCANCEL.
(INT=160)
CAUSE File system related error. A file system error
message will appear after this message. No jobs
were cancelled.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
161 MESSAGE JOBLOG BELONGS TO ANOTHER WORKSTATION. (INT=161)
CAUSE There is a job log/workstation inconsistency. The
NRJE configuration file specifies a particular job
log for this workstation. That job log names a
workstation different from its owner. A
configuration error may have taken place. No jobs
were cancelled.
ACTION Check the NRJE configuration.
---------------------------------------------------------------------------------------
162 MESSAGE ERROR CLOSING JOBLOG IN NRJEHJCANCEL. (INT=162)
CAUSE File system related error. A file system error
message will appear after this message. All
specified jobs were probably cancelled successfully
despite this error.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
163 MESSAGE ERROR UPDATING JOBLOG IN NRJEHJCANCEL. (INT=163)
CAUSE File system related error. A file system error
message will appear after this message. Some jobs
specified may not have been cancelled.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
164 MESSAGE UNABLE TO UNLOCK JOBLOG FILE IN NRJEHJCANCEL.
(INT=164)
CAUSE File system related error. A file system error
message will appear after this message. Some jobs
may not have been cancelled.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
170 MESSAGE TRACE INTRINSIC ON/OFF PARAMETER MUST BE 1 OR 0.
(TRC=170)
CAUSE The TraceOnOff parameter passed to NRJETrace
contains an invalid number.
ACTION Change the value of the TraceOnOff parameter to 1
or 0.
---------------------------------------------------------------------------------------
171 MESSAGE NRJE ONLY PERFORMS LU (INTERNAL) OR INTRINSIC
(USER) TRACING. (TRC=171)
CAUSE An invalid trace type was indicated.
ACTION Correct the type of trace desired to LU (internal)
or intrinsic (user) tracing. When calling
NRJETrace, the Traces parameter must be 1 or 2.
---------------------------------------------------------------------------------------
172 MESSAGE TRACE FILE NAME MUST BE 0 TO 35 CHARACTERS LONG.
(TRC=172)
CAUSE A zero or negative number was passed in the
TraceFileLen parameter to NRJETrace.
ACTION Pass a positive number in TraceFileLen to indicate
the actual length of the trace file name.
---------------------------------------------------------------------------------------
173 MESSAGE TRACE FILE MEDIUM MUST BE DISK (0) OR TAPE (1).
(TRC=173)
CAUSE The TraceMedium parameter passed to NRJETrace was
out of range. It must contain a 0 to indicate disc
or a 1 to indicate tape.
ACTION Change the value of the TraceMedium parameter.
---------------------------------------------------------------------------------------
174 MESSAGE TRACE DEFAULT FILE LENGTH MUST BE GREATER THAN 0.
(TRC=174)
CAUSE The DefaultFileLen parameter passed to the
NRJETrace intrinsic contained a zero or negative
number. DefaultFileLen is the length of the trace
file name.
ACTION Change the value of DefaultFileLen to a positive
number.
---------------------------------------------------------------------------------------
175 MESSAGE NODE MANAGEMENT COULDN'T START OR STOP NRJE TRACE.
(SEV=175)
CAUSE
ACTION
---------------------------------------------------------------------------------------
176 MESSAGE NRJE MANAGEMENT COULDN'T START OR STOP NRJE TRACE.
(SEV=176)
CAUSE
ACTION
---------------------------------------------------------------------------------------
177 MESSAGE WORKSTATION IS NOT PERFORMING INTRINSIC (USER)
TRACING. (TRC=177)
CAUSE Attempt to stop intrinsic (user) tracing was made
but workstation is not performing it.
ACTION
---------------------------------------------------------------------------------------
178 MESSAGE WORKSTATION IS NOT PERFORMING LU (INTERNAL)
TRACING. (TRC=178)
CAUSE Attempt to stop LU (internal) tracing was made but
workstation is not performing it.
ACTION
---------------------------------------------------------------------------------------
179 MESSAGE LU (INTERNAL) TRACE MUST BEGIN WHEN WORKSTATION IS
STARTED. (TRC=179)
CAUSE Attempt to start LU (internal) trace was made but
workstation is not started or active.
ACTION Indicate internal tracing when starting a
workstation.
---------------------------------------------------------------------------------------
180 MESSAGE WORKSTATION IS ALREADY PERFORMING INTRINSIC (USER)
TRACING. (TRC=180)
CAUSE Attempt to start intrinsic (user) tracing but
workstation is performing it.
ACTION
---------------------------------------------------------------------------------------
181 MESSAGE WORKSTATION IS ALREADY PERFORMING LU (INTERNAL)
TRACING. (TRC=181)
CAUSE Attempt was made to start LU (internal) tracing,
which the workstation is already performing.
ACTION
---------------------------------------------------------------------------------------
182 MESSAGE TRACE FILE SIZE MUST BE BETWEEN 0 AND 32767
RECORDS. (TRC=182)
CAUSE An out-of-bounds trace file size value was in the
TraceSize parameter passed to NRJETrace, or its
equivalent command.
ACTION Change the TraceSize parameter to a number between
0 and 32767 records. A zero value indicates that a
default is desired.
---------------------------------------------------------------------------------------
183 MESSAGE ERROR OCCURRED WHILE TRYING TO ACCESS
CONFIGURATION. (SEV=183)
CAUSE
ACTION
---------------------------------------------------------------------------------------
184 MESSAGE WORKSTATION CANNOT INITIATE ANY NEW TRACING.
(SEV=184)
CAUSE
ACTION
---------------------------------------------------------------------------------------
185 MESSAGE WORKSTATION IS NOT PERFORMING ANY TRACING.
(TRC=185)
CAUSE
ACTION
---------------------------------------------------------------------------------------
193 MESSAGE UNABLE TO ISSUE RESET VIA "COMMAND". ERROR #!.
PARM #!. (INT=193)
CAUSE A file system related error has occurred. The
error # was issued by the MPE Command intrinsic.
The command itself is: RESET N1234567. The parm #
if returned refers to the parameter within the
command that was in error.
ACTION Determine the cause (possibly with the help of your
HP representative) and correct the problem.
---------------------------------------------------------------------------------------
194 MESSAGE PR OUTPUT DESTINATION SPECIFICATION EXCEEDS MAX
WIDTH. (INT=194)
CAUSE The job log can only handle a total of 214
characters of output destination information. The
PR specification alone is too long. (Note: file
names are fully qualified by SUBMIT before they end
up in the job log, and backreferences are expanded
to the original file equation).
ACTION Correct the problem.
---------------------------------------------------------------------------------------
195 MESSAGE PR & PU OUTPUT DESTINATIONS EXCEED MAX WIDTH.
(INT=195)
CAUSE The job log can only handle a total of 214
characters of output destination information. The
PR and PU destinations, together, are too long.
Note: file names are fully qualified by SUBMIT
before they end up in the job log, and
backreferences are expanded to the original file
equation).
ACTION Correct the problem.
---------------------------------------------------------------------------------------
196 MESSAGE PR, PU, & FO OUTPUT DESTINATIONS EXCEED MAX WIDTH.
(INT=196)
CAUSE The job log can only handle a total of 214
characters of output destination information. The
PR, PU, and FO destinations, together, are too
long. Note: file names are fully qualified by
SUBMIT before they end up in the job log, and back
references are expanded to the original file
equation).
ACTION Correct the problem.
---------------------------------------------------------------------------------------
197 MESSAGE DISALLOWED CONSOLE COMMAND STRIPPED FROM JOB
STREAM. (INT=197)
CAUSE Users without NM capability are allowed to insert
in a job stream only those host commands specified
in the configuration file.
ACTION No action is required.
---------------------------------------------------------------------------------------
198 MESSAGE UNABLE TO READ FROM CONSOLE TEMP FILE. INPUT FILE
#!. (INT=198)
CAUSE A file system error has occurred. A file system
error message will follow.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
CAUSE A severe error has occurred.
ACTION See "Problem Resolution" in chapter 5 of this
manual, and contact your HP representative for
assistance.
---------------------------------------------------------------------------------------
199 MESSAGE UNABLE TO WRITE CONSOLE DATA TO SPOOLFILE. INPUT
FILE #!. (INT=199)
CAUSE A file system error has occurred. A file system
error message will follow.
ACTION See "Problem Resolution" in chapter 5 of this
manual, and contact your HP representative for
assistance.
---------------------------------------------------------------------------------------
200 MESSAGE INCOMPATIBLE TRANS AND/OR COMP SPECIFIED. FILE #!.
(INT=200)
CAUSE The user specified that the indicated file (or one
of its ##FD include files) is already translated
and/or compressed, but this workstation is
configured to send data untranslated and/or
uncompressed.
ACTION Correct the file subcode or ##FD parameter in
error.
---------------------------------------------------------------------------------------
201 MESSAGE INCOMPATIBLE TRANSLATION SPECIFIED. FILE #!.
(INT=201)
CAUSE The user specified that the indicated file (or one
of its ##FD include files) is already translated,
but this workstation is configured "notranslate".
ACTION Correct the file subcode or ##FD parameter in
error.
---------------------------------------------------------------------------------------
202 MESSAGE UNABLE TO OPEN INPUT FILE #!. (INT=202)
CAUSE File system related error. The ! parameter is the
file number in the order of input to SUBMIT or
NRJE2Submit (The error may refer to an ##FD file
specified within this input file.) A file system
error message will appear after this message.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
203 MESSAGE INVALID CHAR FOLLOWING ##FD FILENAME. IN INPUT FILE
#!. (INT=203)
CAUSE Syntax error on ##FD record. The ! parameter is
the file number in the order of input to SUBMIT or
NRJE2Submit. An open parenthesis "(" or a carriage
return was expected following the file name.
ACTION Locate the ##FD record in error and correct the
problem.
---------------------------------------------------------------------------------------
204 MESSAGE INVALID ##FD OPTION IN INPUT FILE #!. (INT=204)
CAUSE Syntax error on ##FD record. The ! parameter is
the file number in the order of input to SUBMIT or
NRJE2Submit. N[OTRANSLATE] and T[RANSPARENT] are
the only valid options.
ACTION Locate the ##FD record in error and correct the
problem.
---------------------------------------------------------------------------------------
205 MESSAGE UNABLE TO OPEN ##FD FILE REFERENCED THROUGH INPUT
FILE #!. (INIT=205)
CAUSE File system related error. The ! parameter is the
file number in order of input to SUBMIT or
NRJE2Submit. The error refers to a ##FD file
(perhaps multiply nested) within this file. A file
system error message will appear after this
message.
ACTION Determine the cause by inspecting the file system
error.
---------------------------------------------------------------------------------------
206 MESSAGE UNABLE TO PARSE ##FD RECORD IN INPUT FILE #!.
(INT=206)
CAUSE An irreconcilable parsing error of an ##FD record
occurred. The ! parameter is the file number in
the order of input to SUBMIT or NRJE2Submit.
ACTION Locate and inspect the ##FD record for errors, and
correct the problem.
---------------------------------------------------------------------------------------
207 MESSAGE UNABLE TO CLOSE TEMPORARY FILE DURING ERROR
PROCESSING. (INT=207)
CAUSE A SUBMIT or NRJE2Submit error occurred. It was
impossible to close the (pre-job console cmd)
temporary file in the error cleanup routine. Any
file system error message following this message
does not refer to this error but to the original
error that generated a need for cleanup processing.
ACTION Report the occurrence to your HP representative.
---------------------------------------------------------------------------------------
208 MESSAGE UNABLE TO OPEN TEMPORARY FILE. (INT=208)
CAUSE File system related error. A file system error
message will appear after this message.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
209 MESSAGE MAXIMUM NUMBER OF ##FD LEVELS EXCEEDED. INPUT FILE
#!. (INT=209)
CAUSE ##FD inclusions may be nested to a maximum depth of
20. This maximum was exceeded in SUBMIT or
NRJE2Submit. The ! parameter is the file number
in the order of input to SUBMIT or NRJE2Submit.
ACTION Correct the problem.
---------------------------------------------------------------------------------------
210 MESSAGE UNABLE TO CLOSE FILEQ TEMPORARY FILE. (INT=210)
CAUSE A SUBMIT or NRJE2Submit error occurred. It was
impossible to close the (fileq) temporary file in
the error cleanup routine. Any file system error
message following this message does not refer to
this error but to the original error that generated
a need for cleanup processing.
ACTION Report the occurrence to your HP representative.
---------------------------------------------------------------------------------------
211 MESSAGE NLINFO ERROR #! WHILE LOADING TO HOST TRANSLATION
TABLE. (INT=211)
CAUSE SUBMIT or NRJE2Submit was unable to load the "to
host" translation table because of a "Native
Language Support" error. The ! parameter is the
Native Language error code.
ACTION Determine the cause by inspecting the Native
Language error code and correct the problem.
---------------------------------------------------------------------------------------
212 MESSAGE UNABLE TO CLOSE INPUT FILE. (SUB=212)
CAUSE A file system related error occurred in SUBMIT or
NRJE2Submit. While cleaning up in preparation for
exiting on account of this error, NRJE was unable
to close the currently open input file. Any file
system error message following this message does
not refer to this error but to the original file
system error.
ACTION Report the occurrence to your HP representative.
---------------------------------------------------------------------------------------
213 MESSAGE NO FILENAME FOLLOWING ##FD. IN INPUT FILE #!.
(INT=213)
CAUSE An MPE filename must follow when ##FD is found in
columns 1-4 of a record. The ! parameter is the
file number in the order of input to SUBMIT or
NRJE2Submit.
ACTION Locate the ##FD record in error and correct it.
---------------------------------------------------------------------------------------
214 MESSAGE UNABLE TO CLOSE INPUT FILE #! OR ONE OF ITS ##FD
FILES. (INT=214)
CAUSE A file system related error has occurred. The !
parameter is the file number in order of input to
SUBMIT or NRJE2Submit. A file system error message
will appear after this message.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
215 MESSAGE COMMAND ERROR #!. PARM #! IN ERROR. (INT=215)
CAUSE A file system related error has occurred. ERROR #!
refers to an error returned by the MPE COMMAND
intrinsic. The command itself is: BUILD
EQUATES;TEMP. PARM #! refers to the parameter
within the command which is in error.
ACTION Determine the cause (possibly with your HP
representative's help) by inspecting the error code
parameters provided, and correct the problem.
---------------------------------------------------------------------------------------
216 MESSAGE DISALLOWED CONSOLE COMMAND STRIPPED FROM JOB
STREAM. (INT=216)
CAUSE Users without NM capability are allowed to insert
in a job stream only those host commands specified
in the configuration file.
ACTION
---------------------------------------------------------------------------------------
217 MESSAGE HOST COMMAND AFTER 1ST JOB CARD STRIPPED OUT.
(INT=217)
CAUSE Host console commands must appear in the job stream
prior to the first job card.
ACTION No action is required.
---------------------------------------------------------------------------------------
218 MESSAGE SIGNOFF CARD STRIPPED FROM JOB STREAM. (INT=218)
CAUSE Host signoff commands are not allowed in an NRJE
job stream.
ACTION No action is required.
---------------------------------------------------------------------------------------
219 MESSAGE COMMAND ERROR #!. PARM #! IN ERROR. (INT=219)
CAUSE An error has occurred in programmatically executing
the command: LISTEQ *N1234567. ERROR #! refers
to an error returned by the MPE COMMAND intrinsic.
PARM #! refers to the parameter within the command
which is in error.
ACTION Determine the cause (possibly with your HP
representative's help) by examining the error code
parameters, and correct the problem.
---------------------------------------------------------------------------------------
220 MESSAGE UNABLE TO RESOLVE PR/PU/FO DESTINATION
BACKREFERENCE. (INT=220)
CAUSE User specified a file backreference as a print,
punch or forms destination in SUBMIT or NRJE2Submit
but has no file equations in which to resolve it.
ACTION Correct the problem.
---------------------------------------------------------------------------------------
221 MESSAGE UNABLE TO OPEN FILEQ TEMPORARY FILE. (INT=221)
CAUSE A file system related error has occurred. A file
system error message will appear after this
message.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
222 MESSAGE UNABLE TO READ FILEQ TEMPORARY FILE. (INT=222)
CAUSE A file system related error has occurred. A file
system error message will appear after this
message.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
223 MESSAGE UNABLE TO CLOSE FILEQ TEMPORARY FILE. (INT=223)
CAUSE A file system related error. A file system error
message will appear after this message.
ACTION Determine the cause by inspecting the file system
error message and correct the problem.
---------------------------------------------------------------------------------------
224 MESSAGE UNABLE TO RESOLVE PRINT DESTINATION BACKREFERENCE.
(INT=224)
CAUSE Backreferenced print destination for SUBMIT or
NRJE2Submit cannot be resolved with the user's file
equations.
ACTION Check your spelling or your file equations.
---------------------------------------------------------------------------------------