SNA NRJE Error Messages

CAUSE: At least one of the parameters passed to an NRJE intrinsic is not within user stack boundary. SEG#! (code segment#) and P=! (program counter) represents the return address right after the intrinsic call.

ACTION: The caller should check all of the parameters passed to the intrinsic and call it again.

CAUSE: DB register is not pointing to caller's stack when invoking an NRJE intrinsic.

ACTION: Make sure that the DB register is pointing to caller's stack before calling NRJE intrinsics.

CAUSE: NRJE does not have enough extra stack space reserved.

ACTION: Run or Prep program with Stack parameter equal to program requirement + 8000 words.

CAUSE: InCount parameter for reader device classes of NRJEQueue intrinsic is less than 0.

ACTION: Recall NRJEQueue with InCount greater than or equal to 0.

CAUSE: Attempt to obtain NRJE reader information from NRJE configuration failed.

ACTION: Possible configuration error. Check NRJE configuration.

CAUSE: Attempt to obtain NRJE reader information from MPE configuration failed.

ACTION: Possible configuration error. Check NRJE configuration.

CAUSE: Attempt to obtain device classes for NRJE reader failed.

ACTION: Check InCount parameter of NRJEQueue and make sure that InCount is big enough to obtain all device classes; InCount maximum value is 8.

CAUSE: Input name length in SHOW, CANCEL, or ALTER command, or NRJEShow, NRJECancel, or NRJEAlter intrinsic is not between 1 and 17 characters. The input name must be in the form of JobName, @, SpoolfileId, or UserName.AcctName.

ACTION: Make sure the input name is valid.

CAUSE: Input new priority in ALTER command or NRJEAlter intrinsic is not between 0 and 14.

ACTION: Make sure the new priority is valid.

CAUSE: Input name in CANCEL command or NRJECancel intrinsic is not valid.

ACTION: Make sure input name is in the form of JobName, @, SpoolfileID, or UserName.AcctName.

CAUSE: Input name in ALTER command or NRJEAlter intrinsic is not valid.

ACTION: Make sure input name is in the form of JobName, @, SpoolfileID, or UserName.AcctName.

CAUSE: Attempt to manipulate others' spooled files failed.

ACTION: Must have NM capability to perform this.

CAUSE: Attempt to do something that required NM capability failed.

ACTION: Must have NM capability.

CAUSE: Reader fence value is out of bounds.

ACTION: Reader fence value between 0 and 14 is required.

CAUSE: Operand code for NRJERdrAccess intrinsic is not within valid bound.

ACTION: Correct the operand code.

CAUSE: Attempt to obtain remote and JES names from NRJE configuration failed.

ACTION: Check NRJE configuration file.

CAUSE: A negative or zero value was passed in the InCount parameter to the NRJEWriter intrinsic.

ACTION: Pass a positive value in the InCount parameter to NRJEWriter.

CAUSE: Possible configuration error. A configuration error message appears right after this message to describe the exact cause.

ACTION: Check NRJE configuration file for correctness.

CAUSE: Possible configuration error.

ACTION: Check NRJE configuration file for correctness.

CAUSE: InCount parameter for NRJEJobInfo is less than the number of spooled files that qualified to be returned.

ACTION: Increase the InCount parameter value and sizes of the intrinsic arrays.

CAUSE: An attempt was made to obtain information about an inactive LU.

ACTION:

CAUSE: A negative or zero value was passed in InCount to NRJEActiveWS. A positive value is required.

ACTION: Pass a positive value in InCount to NRJEActiveWS.

CAUSE:

ACTION:

CAUSE: Possible configuration error.

ACTION: Check configuration and make sure the spooled reader is configured, spooled, and has device type 22 subtype 2.

CAUSE: The current configuration file does not have the correct version stamp to run with this version of NRJE.

ACTION: If you have recently updated to a new version of NRJE that requires a configuration file update, make sure that the configuration file was updated properly.

CAUSE: Input name in SHOW command or NRJEJobList intrinsic is not in the form of JobName, @, SpoolfileID, or UserName.AcctName.

ACTION: Correct the input name.

CAUSE: The InCount parameter for the NRJEJobInfo intrinsic is out of the allowable 1-500 range.

ACTION: Pass an InCount parameter to NRJEJobInfo within the 1-500 range.

CAUSE: This error might be caused by a variety of reasons, such as (1) unable to open the file NRJECAT.NRJE.SYS, (2) system administrator has changed NRJECAT so that some messages in it become too long to read, or (3) a message is missing in NRJECAT.

ACTION: Depending on the reason, (1) check and make sure NRJECAT exists in NRJE.SYS, (2) make sure no message in the intrinsic, management, configuration and spooling categories is longer than 72 characters long, or (3) print the Status array passed to NRJEErrMsg. All error numbers used in NRJEErrMsg are in Set 1 of NRJECAT.NRJE.SYS.

CAUSE: No spool file exists whose name matches the one specified in the ALTER command or NRJEAlter intrinsic.

ACTION: None.

CAUSE: No spool file exists whose name matches the one specified in the CANCEL command or NRJECancel intrinsic.

ACTION: None.

CAUSE: No spool file exists whose name matches the one specified in the SHOW command or NRJEJobInfo intrinsic.

ACTION: None.

CAUSE: The LU named was not found in the configuration.

ACTION: Check your spelling or the configuration file.

CAUSE: The wsid named was not found in the configuration.

ACTION: Check your spelling or the configuration file.

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.

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.

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.

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.

CAUSE: The length of the welcome message text is out of range.

ACTION: Enter a welcome message whose length is within range.

CAUSE: The MaxLen parameter passed to the NRJEWelcome intrinsic is negative or zero.

ACTION:

CAUSE: Spool file must be in the READY state to be altered.

ACTION: None.

CAUSE: The NumFiles parameter passed to NRJESubmit is out of range.

ACTION: Pass a value in NumFiles to NRJESubmit that is in range.

CAUSE: ! is the file number in the order of input to NRJESubmit intrinsic or SUBMIT command.

ACTION: Correct the problem and re-execute.

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.

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.

CAUSE:

ACTION:

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.

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.

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.

CAUSE: ! is the file number in the order of input to NRJESubmit intrinsic or SUBMIT command.

ACTION: Correct the problem and re-execute.

CAUSE: The input priority value is out of bounds.

ACTION: Resubmit with an input priority within the bounds of 0 and 14.

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.

CAUSE: ! is the file number in the order of input to NRJESubmit intrinsic or SUBMIT command.

ACTION: Correct the problem and re-execute.

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.

CAUSE: ! is the file number in the order of input to NRJESubmit intrinsic or SUBMIT command.

ACTION: Correct the problem and re-execute.

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.

CAUSE: The job naming convention has been violated.

ACTION: Make sure that the job name begins with a letter and is eight or fewer alphanumeric characters long.

CAUSE: Configuration error.

ACTION: Check the configuration file for correctness. If the problem still occurs contact Hewlett-Packard for assistance.

CAUSE: The workstation reader is not available.

ACTION: Determine whether the workstation is active.

CAUSE:

ACTION:

CAUSE: A call from the console process to the system internal intrinsic ATTACHIO failed to execute properly. Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: Internal error. A call to the system intrinsic XDSNTRAP failed.

ACTION: Contact Hewlett-Packard.

CAUSE: Internal error. The console process could not access a needed file.

ACTION: Use the VERSION command to verify the NRJE installation. If versions are correct, contact Hewlett-Packard.

CAUSE: Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: The CONSOLE command executed successfully.

ACTION: None.

CAUSE: The RELEASE command executed successfully.

ACTION: None.

CAUSE: The CONSOLE command was issued but the workstation is not in session with the host.

ACTION: Use the STATUS command to verify the state of the workstation. If not active, start the workstation.

CAUSE: The workstation has disconnected from the host while the console was open. The console will be automatically released by the NRJE CI process.

ACTION: None required for NRJE CI users. Programmatic users should call the NRJERelease intrinsic to release internal resources pertaining to the console.

CAUSE: Internal error occurred in the NRJERcvMsg intrinsic.

ACTION: Contact Hewlett-Packard.

CAUSE: An attempt was made to access an NRJE console command intrinsic with a "consoleid" that was not returned by the NRJEConsole intrinsic.

ACTION: Always call NRJEConsole and obtain the consoleid prior to calling any other console intrinsics.

CAUSE: All console access ports in the NRJE extra data segment are taken. No additional users may access the console until someone releases a console access port by entering the RELEASE command.

ACTION: Try again later.

CAUSE: A user who does not possess "NM" capability issued the NRJE CONSOLE command and no commands have been allowed to non-NM users in the NRJE configuration (the NRJE Configuration: Workstation Data screen).

ACTION: The user should contact the NRJE manager. Any commands which the NRJE manager would like to allow to users who do not have NM capability should be specified in the NRJE configuration.

CAUSE: Internal error. A call to the system internal procedure CREATE'IOWAITPORT failed.

ACTION: Use the NRJE VERSION command to verify that NRJE has been installed correctly. Contact Hewlett-Packard.

CAUSE: A user who does not have NM capability issued a console command which was not allowed by the NRJE manager in the NRJE configuration (the NRJE Configuration: Workstation Data screen).

ACTION: The user should contact the NRJE manager. Any commands which the NRJE manager would like to allow to users who do not have NM capability should be specified in the NRJE configuration.

CAUSE: An attempt was made to access an NRJE console command intrinsic with a "consoleid" that was not returned by the NRJEConsole intrinsic.

ACTION: Always call NRJEConsole and obtain the consoleid prior to calling any other console intrinsics.

CAUSE: A user who does not have NM capability issued a console command with a semicolon (;) in it. Multiple commands may not be concatenated by using a semicolon. Each command must be issued separately.

ACTION: Reissue the command without a semicolon.

CAUSE: Returned only by NRJEConsCheck when no messages have been received from the host since the last call to NRJERcvMsg.

ACTION:

CAUSE: A console command was issued and although the workstation was active at the time the command was issued, no LU was found to be active. The command is rejected. The workstation may be in the process of terminating.

ACTION: Use the STATUS command to check the status of each LU. If necessary, use the STARTWS command to restart the workstation.

CAUSE: The maximum buffer length parameter specified for the console message in NRJERcvMsg was negative or zero.

ACTION: Revise the maximum buffer length parameter value for the NRJERcvMsg intrinsic to a positive number. Console messages range from 80 to 132 characters long.

CAUSE: The length of the console command indicated in the NRJESendCmd intrinsic call was negative or zero.

ACTION: Revise the length of the console command to a positive number between 1 and 80 characters.

CAUSE: First ! is the input chain size. Second ! is the upper limit.

ACTION: Input chain size with the range between 0 and second !.

CAUSE: First ! is the number of LUs input. Second ! is the upper limit.

ACTION: Input number of LUs with the range between 0 and second !.

CAUSE: NRJE unable to stream monitor job. The monitor job is a streamable file residing under NRJE.SYS and has the same name as the workstation name.

ACTION: Refer to the manual and create or update the monitor job so that it is streamable.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Attempt to activate or deactivate an LU that is not configured.

ACTION:

CAUSE: Attempt to activate an LU that is already active.

ACTION:

CAUSE: The workstation may not have been started or another NRJE manager may have already stopped or halted the workstation.

ACTION:

CAUSE:

ACTION:

CAUSE: The StopCode parameter passed to the NRJEStopWS intrinsic is out of range.

ACTION: Correct the StopCode parameter value.

CAUSE: An attempt was made to deactivate an LU that is not active.

ACTION:

CAUSE: Attempt to start workstation was made but it is already active.

ACTION:

CAUSE: Possible configuration error.

ACTION: Check configuration file for correctness and retry.

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:

CAUSE: An LU name appears more than once in the list.

ACTION: Delete duplicate LU names from the list.

CAUSE:

ACTION: Check configuration file — error occurred reading job entry subs.

CAUSE: Input or ##FD file is wider than MAXREC (default MAXREC=80).

ACTION:

CAUSE: MAXREC parm to NRJE3Submit was too big for VSE/POWER.

ACTION:

CAUSE: MAXREC parm to NRJE3Submit was too big for JES using a 512 byte RU.

ACTION:

CAUSE: MAXREC parm to NRJE3Submit was too big for JES using a 256 byte RU.

ACTION:

CAUSE: MAXREC parms 80 bytes aren't allowed by NRJE3Submit.

ACTION:

CAUSE: Negative MAXREC parms to NRJE3Submit aren't allowed.

ACTION:

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.

CAUSE: The username length passed to NRJEHJCancel was not between 1 and 17. No jobs were cancelled.

ACTION: Correct and reissue.

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.

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.

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.

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.

CAUSE: NM capability is required to cancel jobs submitted by other users. No jobs were cancelled.

ACTION: Correct the problem and reissue.

CAUSE: Only @ and UserName.AcctName are valid usernames to cancel jobs by. No jobs were cancelled.

ACTION: Correct and reissue.

CAUSE: A configuration error may have taken place. No jobs were cancelled.

ACTION: Check NRJE configuration file.

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.

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.

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.

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.

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.

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.

CAUSE: The TraceOnOff parameter passed to NRJETrace contains an invalid number.

ACTION: Change the value of the TraceOnOff parameter to 1 or 0.

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.

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

CAUSE: The TraceMedium parameter passed to NRJETrace was out of range. It must contain a 0 to indicate disk or a 1 to indicate tape.

ACTION: Change the value of the TraceMedium parameter.

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.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Attempt to stop intrinsic (user) tracing was made but workstation is not performing it.

ACTION:

CAUSE: Attempt to stop LU (internal) tracing was made but workstation is not performing it.

ACTION:

CAUSE: Attempt to start LU (internal) trace was made but workstation is not started or active.

ACTION: Indicate internal tracing when starting a workstation.

CAUSE: Attempt to start intrinsic (user) tracing but workstation is performing it.

ACTION:

CAUSE: Attempt was made to start LU (internal) tracing, which the workstation is already performing.

ACTION:

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.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

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.

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.

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.

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.

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.

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 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: A file system error has occurred. A file system error message will follow.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

CAUSE: Users without NM capability are allowed to insert in a job stream only those host commands specified in the configuration file.

ACTION:

CAUSE: Host console commands must appear in the job stream prior to the first job card.

ACTION: No action is required.

CAUSE: Host signoff commands are not allowed in an NRJE job stream.

ACTION: No action is required.

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.

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.

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.

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.

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.

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.

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.

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.

CAUSE: A severe error may have occurred. Another, more specific message should follow this.

ACTION: See the message following this one to determine the error.

CAUSE: SUBMIT or NRJE2Submit test most output destinations to be sure they're there. NRJE was unable to close the print destination file after test-opening it. A file system related error. A file system error message will follow.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: SUBMIT and NRJE2Submit test most output destinations to be sure they're there. NRJE was unable to close the punch destination file after test-opening it. A file system related error. A file system error message will follow.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: SUBMIT and NRJE2Submit test most output destinations to be sure they're there. NRJE was unable to close the forms destination file after test-opening it. A file system related error. A file system error message will follow.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: SUBMIT and NRJE2Submit test most output destinations (by opening them) to be sure they're there. A file system related error. A file system error message will follow.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: SUBMIT and NRJE2Submit test most output destinations (by opening them) to be sure they're there. A file system related error. A file system error message will follow.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: SUBMIT and NRJE2Submit test most output destinations (by opening them) to be sure they're there. A file system related error. A file system error message will follow.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: While trying to clean up from a previous file system error in preparation for an error return, SUBMIT or NRJE2Submit was unable to close the currently open output spool file. Any file system error message following this message refers not to this error but to the original file system error.

ACTION: Exit NRJE to close the spool file. Then use SPOOK (or NRJE) to delete it. Report problems of this nature to your HP representative.

CAUSE: A compaction SCB was found in the input file specified or one of its ##FD include files.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

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.

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.

CAUSE: One cause of this message is an invalid JOB card. If this message is caused by an invalid JOB card, no file system error message will follow.

ACTION: Check the format of the JOB card for the first input file specified in your SUBMIT command. Make sure it meets the specifications of the host JCL.

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.

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. See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: A severe error has occurred.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: SUBMIT or NRJE2Submit was unable to load the "from 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.

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. See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: An MPE filename is expected following ##FD in columns 1-4 of an input record. The ! parameter is the number of the file in order of input to SUBMIT or NRJE2Submit.

ACTION: Locate and correct the ##FD record in error.

CAUSE: An ##FD syntax error. The ! parameter is the number of the file in order of input to SUBMIT or NRJE2Submit.

ACTION: Locate and correct the ##FD record in error.

CAUSE: An ##FD syntax error. The ! parameter is the number of the file in order of input to SUBMIT or NRJE2Submit.

ACTION: Locate and correct the ##FD record in error.

CAUSE: Only host console commands and ##FD records that include host console commands are allowed prior to the first nontransparent job card. A transparent job card was encountered before a nontransparent job card. The ! parameter is the number of the file in the order input to SUBMIT or NRJE2Submit.

ACTION: Correct the job stream.

CAUSE: Only host console commands and ##FD records that include host console commands are allowed prior to the first nontransparent job card. Something else was encountered. The ! parameter is the number of the file in the order input to SUBMIT or NRJE2Submit.

ACTION: Correct the job stream.

CAUSE: A file system related error. A file system error message will appear after this message. The ! parameter is the number of the file being processed in order input to SUBMIT or NRJE2Submit.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: A file system related error. A file system error message follows this message.

ACTION: Determine the cause by inspecting the file system error message and correct the problem. Notify Hewlett-Packard if you cannot determine the cause.

CAUSE: The NRJE logical reader should be configured as a type 2, subtype 22 device.

ACTION: Correct the reader configuration.

CAUSE: These system files are not allowed as input to SUBMIT or NRJE2Submit.

ACTION: Correct and reissue.

CAUSE: The print destination for SUBMIT or NRJE2Submit must be between 1 and 86 characters if one is supplied.

ACTION: Correct the print destination.

CAUSE: The punch destination for SUBMIT or NRJE2Submit must be between 1 and 86 characters if one is supplied.

ACTION: Correct the punch destination.

CAUSE: The forms destination for SUBMIT or NRJE2Submit must be between 1 and 86 characters if one is supplied.

ACTION: Correct the forms destination.

CAUSE: The print, punch, or forms destination resolved to $FileName. This is not supported in NRJE II.

ACTION: Correct the output destination.

CAUSE: A non-alphanumeric character was found in an output destination backreference.

ACTION: Correct the output destination.

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.

CAUSE: The subcode of an input file must be between 0 and 2. The ! parameter is the file number in order input to SUBMIT or NRJE2Submit.

ACTION: Correct subcode array element to a value within range.

CAUSE: A severe error has occurred.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: A severe error has occurred.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: The ##FD option N[OTRANSLATE] cannot be used within a job that is submitted with the ";DIRECT" option, i.e., jobs already translated cannot be submitted ;DIRECT.

ACTION: Correct the problem and resubmit the job.

CAUSE: The correct syntax for a ##FD record is: ##FD filename (optionlist). The ! parameter is the file index in order of input to SUBMIT or NRJE2Submit.

ACTION: Correct the ##FD record and resubmit the job.

CAUSE: A file system related error. A file system error message follows this message. NRJE, after successfully test-opening the print destination, was unable to obtain information about it.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: A file system related error. A file system error message follows this message. NRJE, after successfully test-opening the punch destination, was unable to obtain information about it.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: An error occurred in programmatically executing the command RESET N1234567.

ACTION: Determine the cause (possibly with your HP representative's help) by examining the error codes and correct the problem.

CAUSE: An error occurred in programmatically executing the command FILE N1234567 = EQUATES,OLDTEMP.

ACTION: Determine the cause (possibly with your HP representative's help) by examining the error codes, and then correct the problem. See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: Output destination files must have been built before the job is submitted.

ACTION: Build the output destination file and correct the file designator and/or file equations.

CAUSE: Output destination files must have been built before the job is submitted.

ACTION: Build the output destination file and correct the file designator and/or file equations.

CAUSE: Output destination files must have been built before the job is submitted.

ACTION: Build the output destination file and correct the file designator and/or file equations.

CAUSE: A file system related error. A file system error message follows this message.

ACTION: Determine the cause by inspecting the file system error message, and then correct the problem.

CAUSE: A severe error has occurred.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: A file system related error. A file system error message follows this message.

ACTION: Determine the cause by inspecting the file system error message, and then correct the problem.

CAUSE: A severe error has occurred.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: A file system related error. A file system error message follows this message.

ACTION: Determine the cause by inspecting the file system error message and correct the problem.

CAUSE: Specified print destination does not appear to be an actual file name, a backreferenced file, an ldev, a formid, or a device class.

ACTION: Correct the problem.

CAUSE: Specified punch destination does not appear to be an actual file name, a backreferenced file, an ldev, a formid, or a device class.

ACTION: Correct the problem.

CAUSE: Specified forms destination does not appear to be an actual file name, a backreferenced file, an ldev, a formid, or a device class.

ACTION: Correct the problem.

CAUSE: One or more of the parameters passed to NRJEHJInfo (SHOW;HJ=) is not within the user's stack boundary. SEG# ! (code segment #) and P=! (program counter) are the return address after the intrinsic call. If this error was returned when you typed SHOW;HJ=... from the NRJE command interpreter, then a severe error has occurred.

ACTION: If you are calling NRJEHJInfo directly, check all of the parameters passed to the intrinsic, correct the problem, and call it again. If you typed SHOW;HJ=..., see "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: The UserName.AcctName length is out of range.

ACTION: Correct the problem and execute again.

CAUSE: The InCount parameter for the NRJEHJInfo intrinsic is out of the allowable range.

ACTION: Pass an InCount parameter to NRJEHJInfo that's greater than 0.

CAUSE: The JoblistLen parameter for the NRJEHJInfo intrinsic is out of the allowable range. A list of host job names and numbers cannot have a negative number of elements.

ACTION: Pass a JoblistLen parameter to NRJEHJInfo that's greater than 0.

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.

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.

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.

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.

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.

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.

CAUSE: The username in the SHOW command or the NRJEHJInfo intrinsic parameter is not in the proper form for a UserName.AcctName or @.

ACTION: Correct the username.

CAUSE: The user's logon account doesn't match the specified in the SHOW command or NRJEHJInfo intrinsic.

ACTION: A user must have NM capability to manipulate jobs submitted outside the logon UserName.AcctName.

CAUSE: Neither a UserName nor a list of host job names and numbers was supplied to the SHOW command or NRJEHJInfo intrinsic. One or the other must be supplied.

ACTION: Make sure that either a UserName or JobList is supplied and that UserNameLen or JobListLen is greater than 0 (NRJEHJInfo).

CAUSE: The StartPos parameter to NRJEHJInfo must be greater than or equal to 1. StartPos is out of range.

ACTION: Make sure the value is in range.

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.

CAUSE: The SHOW command or NRJEHJInfo intrinsic was unable to access the workstation information. A more specific configuration file error message should follow this one.

ACTION: Determine the cause, if possible, by inspecting the message that follows this, and correct the problem. If the problem still occurs, contact your HP representative for assistance.

CAUSE: A job log file label specifies the workstation that owns the job log. The configuration file specifies the job log file that each workstation owns. The job log file specified for this workstation has a label naming a different workstation as owner. Possible configuration error.

ACTION: Check that the configuration file specifies the appropriate job log for the workstation. If the problem still occurs, contact your HP representative for assistance.

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.

CAUSE: Internal software error. Possibly out of disk space on the system.

ACTION: Contact your HP representative.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: NRJE attempted to load a Lookup Table that has no entries.

ACTION: Rebuild designated Lookup Table and restart workstation.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Record length out of bounds.

ACTION: Rebuild Lookup Table < 260 bytes.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION: Make sure the Lookup Table is configured in the configuration file.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: The RELOAD command was issued with the workstation inactive.

ACTION: No action is required.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: A command such as STARTWS or STOPWS was entered which exceeded the maximum supported length.

ACTION: Re-enter as separate commands.

CAUSE: A control command sent to the NRJE monitor could not be processed because the monitor is not active.

ACTION: Use the STATUS command to verify the state of the workstation.

CAUSE: A control command sent to an LU cannot be processed because the LU is not active.

ACTION: Use the STATUS command to verify the state of the LU.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Attempt to start a workstation that is already active.

ACTION:

CAUSE: NRJE allows only eight workstations to be active concurrently.

ACTION: Bring down some active workstations if other workstations need to be started.

CAUSE: There should be a message preceding this message.

ACTION: Look at the preceding message and determine the error.

CAUSE: Attempt to create an LU entry that already exists.

ACTION:

CAUSE: User attempted to use more LUs than are available (maximum=16).

ACTION:

CAUSE: Attempt to access an LU entry but it does not exist in the NRJE extra data segment.

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION

CAUSE:

ACTION:

CAUSE: If this message appears when executing the NRJE subsystem, then a severe error has occurred.

ACTION: See "Problem Resolution" in Chapter 5 “SNA NRJE Troubleshooting” of this manual, and contact your HP representative for assistance.

CAUSE: If this problem took place during the execution of a user program, then the NRJE intrinsics did not have sufficient stack space.

ACTION: PREP or RUN the user program with a larger STACK=StackSize parameter.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Attempt to start a workstation that is in the pending activation state. Pending state is the state when the workstation is about to be active.

ACTION:

CAUSE: Attempt to start or stop a workstation but it is in the monitor pending state. Monitor pending state is the state when workstation monitor is about to be active.

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: The NRJE extra data segment is being deleted due to a system or NMMON shutdown. NRJE workstations can no longer be activated.

ACTION: Restart the system or NMMON before using NRJE.

CAUSE: NRJE was unable to obtain an extra data segment for use in the ports facility to provide interprocess communication between the several NRJE processes.

ACTION: Verify that all versions are correct. Increase the size of the DST table using SYSDUMP (SYSTEM TABLE CHANGES). Refer to the SNA Link Services Reference Manual for system configuration information.

CAUSE: Attempted to run NRJE monitor (NRJEMON) without calling NRJEStartWS or issuing a STARTWS command.

ACTION: Call NRJEStartWS or issue STARTWS command.

CAUSE:

ACTION:

CAUSE: NRJE monitor (NRJEMON) is run with the Info parameter containing an invalid workstation name length.

ACTION: Rerun NRJEMON with a valid and existing workstation name. Note: NRJEStartWS intrinsic must have been previously called or STARTWS command previously issued.

CAUSE:

ACTION:

CAUSE: "TO HOST" console message file is being opened by an NRJE operator and NRJE monitor is terminating.

ACTION: Locate the operator and tell it to close the file.

CAUSE: "FROM HOST" console message file is being opened by an NRJE manager and NRJE monitor is terminating.

ACTION: Locate the manager and have the file closed.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: NRJE performed a kill on LU class ! but the kill failed.

ACTION: Bring down the workstation job whenever possible. If the problem still occurs, contact HP for assistance.

CAUSE:

ACTION:

CAUSE: The message file between the command interpreter and the workstation monitor failed to open.

ACTION: Attempt to start the workstation again. If the problem continues, contact your HP representative for assistance.

CAUSE:

ACTION:

CAUSE: The NRJE monitor (NRJEMON) is being run without preparation. ! is the workstation name.

ACTION: Issue a STARTWS command or call NRJESTARTWS intrinsic before running the monitor.

CAUSE: The workstation monitor could not start the LU.

ACTION: See subsequent messages that appear for an explanation.

CAUSE: File system error has occurred.

ACTION: Determine the cause of the file system error.

CAUSE:

ACTION:

CAUSE:

ACTION: Ensure that the NRJELU program exists under NRJE.SYS.

CAUSE: Neither the START command nor the NRJE configuration specified any LUs to be initiated.

ACTION: Issue a START command with the LU parameter, and/or revise the NRJE configuration.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: There should be a message preceding this one.

ACTION: Look at the preceding message and determine the error.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: NRJEOUT is run without a device list or the Info parameter.

ACTION: Rerun NRJEOUT with the Info parameter that contains an MPE device list.

CAUSE: A syntax error occurred in parsing the Info parameter after issuing RUN NRJEOUT.

ACTION: Redo RUN NRJEOUT command.

CAUSE: An unidentified device class name was specified in the Info parameter of a RUN NRJEOUT command.

ACTION: Verify that the device class name is in the MPE configuration and has been entered correctly in the RUN NRJEOUT command.

CAUSE: An unidentified logical device number was specified in the Info parameter of a RUN NRJEOUT command.

ACTION: Verify that the logical device number is in the MPE configuration and has been entered correctly in the RUN NRJEOUT command.

CAUSE: An incorrect logical device number or device class name was indicated in the Info parameter of a RUN NRJEOUT command.

ACTION: Verify that the logical device number or device class name is configured to be with a logical writer by Network Management Services.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: There are too many characters in a device class name in the Info parameter of a RUN NRJEOUT command.

ACTION: Correct the device class name so that it begins with a letter and is eight or fewer characters long.

CAUSE:

ACTION:

CAUSE: An access error occurred on a file.

ACTION: See subsequent messages identifying the file.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Too many device classes have been indicated in the Info parameter of a RUN NRJEOUT command.

ACTION: Reduce the number of device classes indicated in the Info parameter of the RUN NRJEOUT command. Separate jobs or sessions may be suitable.

CAUSE: Too many logical device numbers have been indicated in the Info parameter of a RUN NRJEOUT command.

ACTION: Reduce the number of logical device numbers indicated in the Info parameter of the RUN NRJEOUT command. Separate jobs or sessions may be suitable.

CAUSE: There are too many spool files in one chain.

ACTION: Alter the host job so that fewer data sets are generated.

CAUSE: NRJEOutData, supplied by a user, destroyed the integrity of data, DB through Q, in the NRJEOUT routine.

ACTION: Check the indexing range of operations that do storage.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Parsing error.

ACTION: Re-enter data.

CAUSE: Parsing error.

ACTION: Re-enter data.

CAUSE: A keyword was used out of context.

ACTION: Re-enter data without the keyword.

CAUSE: A keyword was used more than once where prohibited.

ACTION: Re-enter data and do not repeat the keyword.

CAUSE: This is an information message for an NRJE manager entering a welcome message.

ACTION: Enter welcome message data lines followed by a [RETURN]. Enter a [RETURN] immediately after a prompt to terminate the welcome message.

CAUSE: A data entry error has occurred. An equal sign following a keyword has been omitted.

ACTION: Scan the data for a keyword that requires an equal sign and a parameter. Re-enter the information.

CAUSE: An error has occurred in reading from $STDIN.

ACTION: Re-enter the NRJE subsystem and then re-enter the data. If this occurs again, contact your HP representative for assistance.

CAUSE: The chain size parameter value is out of range.

ACTION: Correct the chain size parameter value and re-enter data.

CAUSE: The priority value is out of range.

ACTION: Correct the priority value and re-enter data.

CAUSE: An incorrect job name, job number or UserName.AcctName was entered.

ACTION: Job names must begin with a letter and be eight or fewer alphanumeric characters long. Job numbers are five digit numeric strings. A UserName and AcctName each must begin with a letter and be eight or fewer alphanumeric characters long; a period must separate the two.

CAUSE: An incorrect job name was entered.

ACTION: A job name must begin with a letter and be eight or fewer alphanumeric characters long. Correct the information and re-enter the data.

CAUSE: An incorrect job number was entered.

ACTION: A job number is a string of five or fewer numbers. Correct the information and re-enter the data.

CAUSE: An unknown keyword was entered.

ACTION: Correct the information and re-enter the data.

CAUSE: An invalid LU name was entered.

ACTION: An LU name must begin with a letter and may be eight or fewer alphanumeric characters long. Correct the information and re-enter the data.

CAUSE: An invalid new priority value was entered.

ACTION: A priority must be between 0 and 14. Correct the information and re-enter the data.

CAUSE: An incorrect UserName.AcctName was entered.

ACTION: Verify that the UserName and AcctName exist. A UserName and AcctName must each begin with a letter and may be eight or fewer alphanumeric characters long. One must be separated from the other by a period.

CAUSE: An invalid workstation identification was entered.

ACTION: Verify that the workstation identification exists. A workstation must begin with a letter and may be eight or fewer alphanumeric characters long. Correct the information and re-enter the data.

CAUSE: The workstation identification contains too many, or too few characters.

ACTION: A workstation identification must begin with a letter and may be eight or fewer alphanumeric characters long. Correct the information and re-enter the data.

CAUSE: The new priority value was omitted.

ACTION: Correct the information and re-enter the data.

CAUSE: A superfluous parameter was entered.

ACTION: Correct the information and re-enter the data.

CAUSE: An unknown command was entered.

ACTION: Correct the information and re-enter the data.

CAUSE: An unknown command or parameter was entered.

ACTION: Correct the command or parameter and re-enter the data.

CAUSE: A keyword has been entered and is not valid for the current command.

ACTION: Refer to NRJE manual for command syntax and reenter.

CAUSE: A syntax error has occurred in the parameter list.

ACTION: Correct the information and re-enter the data.

CAUSE: A semicolon was omitted.

ACTION: Correct the information and re-enter.

CAUSE: A keyword was used incorrectly.

ACTION: Omit the keyword from the command and re-enter the data.

CAUSE: The $STDINX input file could not be opened.

ACTION: Another routine may be using $STDINX. Wait and then try to open again.

CAUSE: The $STDLIST output file could not be opened.

ACTION: Another routine may be using $STDLIST. Wait and then try to open again.

CAUSE: The keyword use is limited to the SUBMIT command.

ACTION: Delete the keyword from this command and re-enter the data.

CAUSE: The current workstation and the new workstation are identical.

ACTION: Switching workstation is superfluous.

CAUSE: There are too few parameters.

ACTION: Check the parameter list, add to it, and re-enter the data.

CAUSE: There are too many parameters.

ACTION: No action is required. If this error message was printed because of prestored input, delete the extra parameters to prevent this message from being printed again.

CAUSE:

ACTION:

CAUSE: An attempt was made to RELEASE the console when it was not open.

ACTION: Issue a CONSOLE command, or call NRJEConsole, then enter a host console command or call NRJESendCmd.

CAUSE: A workstation identification was omitted from this command and there is no default workstation. The NRJE subsystem was entered without specifying a workstation identification.

ACTION: Re-enter this command including a workstation identification parameter. Or enter an NRJE command with a workstation identification parameter to establish a default workstation, and then enter this command.

CAUSE: NRJE command interpreter unable to read input welcome messages from the user. A file system error should follow to clarify the situation.

ACTION: Investigate the file system error message and if possible reenter.

CAUSE: NRJE command interpreter received an end of file condition from MPE file system when attempting to read user input.

ACTION:

CAUSE: An undefined MPE command was entered from the NRJE subsystem.

ACTION: Correct the MPE command and re-enter the data.

CAUSE: An MPE command that was entered from the NRJE subsystem could not be executed. The meaning of MPE error number ! can be found in System Operation and Resource Management Reference Manual. The command to be executed may be limited to non-break mode.

ACTION: In order to execute the MPE command, EXIT from NRJE, execute the MPE command, and then re-enter NRJE.

CAUSE: There are more than five LU name parameters in the command.

ACTION: Reduce the number of LU names to five, or less, and re-enter the command.

CAUSE: An InFile reference is too long.

ACTION: An InFile reference can be a fully qualified file name, or * followed by a formal designator reference to a FILE command. All parts of a fully qualified file name, and a formal designator, must begin with a letter and are eight or fewer alphanumeric characters long.

CAUSE: An InFile reference was followed by a (C,C) or (T,T).

ACTION: Correct the command and re-enter it.

CAUSE: A right parenthesis was omitted.

ACTION: Correct the command and re-enter it.

CAUSE: A token that is not a comma, semicolon, or carriage return is detected after an infile option.

ACTION: Refer to NRJE manual and re-enter.

CAUSE: Too many infiles have been specified.

ACTION: If the SUBMIT command is for more than one job, divide the task into several SUBMIT commands. If the SUBMIT command is for one job, consolidate the files as follows: (1) append several files together and SUBMIT again, and (2) write a routine using the NRJESubmit intrinsic.