SNA NRJE Logging Messages

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

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:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: The workstation was configured to use a Joblog file which was built by another workstation.

ACTION: Correct the configuration for the Joblog Data File and Joblog Key File fields of the NRJE Configuration: Workstation Data Page 2 screen. Note that the defaults must be changed if more than one workstation is configured.

CAUSE: UserName.AcctName of batch job running NRJEMON must be NRJE.SYS.

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: NRJE was configured to use a Formid Lookup Table, but the file does not exist.

ACTION: If you want to use a Lookup Table, create the table file, store it in the SYS account, and specify the file's name in the Formid Lookup Table File field of the NRJE Configuration: Workstation Data Page 2 screen. If you do not want to use a Lookup Table, specify all blanks in the Formid Lookup Table File field of the Workstation Data Page 2 screen.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: NRJE could not obtain a port for interprocess communication using the CREATIOWAITPORT system procedure. This is an internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: NRJE failed to read the contents of the NRJE Configuration: Reader Data screen in the configuration file.

ACTION: Use NMMGR to verify the contents of the configuration file. Ensure that the Data flag for the NRJE Configuration: Reader Data screen is "Yes". Check the versions of NRJE and NMS, using NMMAINT.

CAUSE: NRJE cannot obtain the device queue for the NRJE reader.

ACTION: Verify that the logical device number on the NRJE Configuration: Reader Data screen matches a logical device in the system I/O configuration of type 22, subtype 2, driver name=IONRDR0. Ensure that the ldev is accessed by only one workstation.

CAUSE: NRJEDEVINFO returned non-zero status.

ACTION: Verify that the logical device number in the NRJE Configuration: Reader Data screen matches a logical device in the system I/O configuration of type 22, subtype 2, driver name=IONRDRO. Ensure that the ldev is accessed by only one workstation.

CAUSE: A call to NRJESPOOLINFO returned non-zero status.

ACTION: Verify that the logical device number in the NRJE Configuration: Reader Data screen matches a logical device in the system I/O configuration of type 22, subtype 2, driver name=IONRDR0. Ensure that the ldev is accessed by only one workstation.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: The CI is ready to accept console commands.

ACTION:

CAUSE: The CI is no longer accepting console commands.

ACTION:

CAUSE: NRJELU is not run as a son of NRJEMON.

ACTION: Run NRJEMON which will run NRJELU. If the error still occurs please report it to Hewlett-Packard.

CAUSE: NRJELU is not run as a son of NRJEMON.

ACTION: Run NRJEMON which will run NRJELU. If the error still occurs please report it to Hewlett-Packard.

CAUSE: NRJELU is not run as a son of NRJEMON.

ACTION: Run NRJEMON which will run NRJELU. If the error still occurs please report it to Hewlett-Packard.

CAUSE: NRJELU is not run as a son of NRJEMON.

ACTION: Run NRJEMON which will run NRJELU. If the error still occurs please report it to Hewlett-Packard.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: LU completes its initialization; communication to host is established.

ACTION:

CAUSE: First ! contains a workstation name. Second ! contains an LU name.

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: An XPORT error occurred. The third ! contains the error message.

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: Session Control has rejected a BIND received from the host.

ACTION: Refer to configuration section in SNA link manual and reconfigure the logmode entry on the host correctly.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: An illegal BIND, that is, one that doesn't match NMCONFIG parameters, or one that doesn't match hardcoded parameters has been received from the IBM host. These messages are an expansion of, and replacement for, error message 1207.

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:

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:

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:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: All logical readers for the workstation are drained.

ACTION: Stop and restart the workstation, and start the logical readers with the JES2 $S command.

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:

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:

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:

ACTION:

CAUSE:

ACTION:

CAUSE: An error occurred attempting to write a trace record.

ACTION: See NMERR message text in the SNA Link Services Reference Manual or in Using the Node Management Services (NMS) Utilities.

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:

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:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: NRJE was configured to use an external procedure for a logical writer but the attempt to load the procedure failed.

ACTION: Refer to the MPE Intrinsics Reference Manual for information on LOAD ERR.

Ensure that the exit procedure is in SL.NRJE.SYS or SL.PUB.SYS and that the Writer Data screen indicates the correct procedure name. Ensure that the RUN command in the NRJE stream file runs the NRJEMON program with "LIB=G".

CAUSE: NRJE failed to access the MIDAS database which returned an error number of 'CFG'.

ACTION: Ensure that the configuration file exists as NMCONFIG.PUB.SYS. It may be necessary to convert the configuration file to a new format by running the Node Management Services conversion utility NMMGRVER.

CAUSE: NRJE encountered a loadproc error while attempting to load the console exit procedure.

ACTION: Ensure that the procedure name in the Workstation Data screen is correct and that the procedure exists in SL.NRJE.SYS or SL.PUB.SYS. Ensure that the RUN command of the NRJE Stream file runs the NRJEMON program with "LIB=G".

CAUSE: Internal software error. Logged only while aborting due to a more serious error.

ACTION: None.

CAUSE: An FOPEN error occurred on the Joblog file.

ACTION: Check the preceding error message which will identify the nature of the fopen failure. Ensure that Workstation Data screen correctly identifies the name of the Joblog in the NRJE group of the SYS account. Ensure that all NRJE module versions are compatible.

CAUSE: Access error occurred while attempting to save the Joblog record length value in the NRJE XDS. An internal software error.

ACTION: Contact Hewlett-Packard for assistance.

CAUSE: FOPEN failure on the internal job temporary copy of the Lookup Table.

ACTION: Ensure that NRJE versions are correct. If versions are compatible, contact Hewlett-Packard for assistance.

CAUSE: A GETDSEG failure was encountered.

ACTION: Ensure that NRJE versions are compatible. Ensure that the system configuration for "MAXIMUM NUMBER OF EXTRA DATA SEGMENTS/PROCESS" is greater than 4.

CAUSE: NRJE could not zero out the length field for the Joblog record in the NRJE XDS. Internal software error.

ACTION: Contact Hewlett-Packard.

CAUSE: NRJE encountered an error while attempting to copy a file from the NRJE reader to the host.

ACTION: Ensure that the NRJE Reader is properly configured into the MPE I/O configuration. Ensure that NRJE versions are correct.

CAUSE: NRJE submitted a job to the host and was waiting for the host "ON READER" message which would inform NRJE of the host job number when NRJE received a command to terminate communication with the host. Termination may have been due to any number of causes including receiving an unexpected "UNBIND", a communications line failure, or a "KILL" command issued by the node manager.

ACTION: None.

CAUSE: A DMOVOUT error occurred while attempting to save the Joblog record in the Joblog extra data segment. An internal software error.

ACTION: Contact Hewlett-Packard for assistance.

CAUSE:

ACTION:

CAUSE: An exit procedure for a writer returned a non-zero value for file number. An FCHECK was executed on this file number and non-zero error value returned as FSERR.

ACTION: Correct the exit procedure.

CAUSE: NRJE failed to read the length value of the Joblog record from the NRJE XDS. Internal software error.

ACTION: Contact Hewlett-Packard.

CAUSE: NRJE Failed to execute the NLINFO intrinsic which returned an error code of NLERR.

ACTION: Refer to the Native Language Support Reference Manual for information on NLERR.

CAUSE: NRJE encountered a GETDSEG intrinsic failure while attempting to acquire the Joblog buffer XDS.

ACTION: Ensure that MPE is configured for a MAXIMUM NUMBER OF EXTRA DATA SEGMENTS PER PROCESS of 5 or more. Check NRJE versions for compatibility.

CAUSE: NRJE failed to execute the NLINFO intrinsic.

ACTION: Consult the Native Language Support Reference Manual for information regarding the NLERR error number.

CAUSE: NRJE failed to execute the NLINFO intrinsic.

ACTION: Consult the Native Language Support Reference Manual for information regarding the NLERR error number.

CAUSE: The NRJE SUBMIT intrinsic parsed the users submitted job and identified the name of the job but the parsing done by the host yielded a different job name (this job name is sent to NRJE in the 'ON READER' message).

ACTION: Contact Hewlett-Packard.

CAUSE: NRJE failed to execute the FLOCK intrinsic.

ACTION: Ensure that NRJE versions are compatible. Contact Hewlett-Packard.

CAUSE: NRJE could not execute FFINDBYKEY on the Joblog while in error recovery mode for a DUPLICATE 'KEY' VALUE (FSERR 171) error on the Joblog.

ACTION: Refer to the preceding error message for the nature of the file system error. Contact Hewlett-Packard.

CAUSE: An FUPDATE intrinsic error occurred.

ACTION: Refer to the preceding error message for the nature of the file system error. Contact Hewlett-Packard.

CAUSE: An FWRITE intrinsic error occurred on the Joblog.

ACTION: Refer to the following message for the file system error number. Contact Hewlett-Packard.

CAUSE: The host sent the 'ON READER' message indicating that a job was on one of NRJE's readers but NRJE did not have a job active on a reader. The message is ignored. This may occur upon signing on to the host after having previously terminating a connection abnormally. When an abnormal termination occurs, there may be console messages queued up for transmission to the remote console which will be sent when the remote signs on again.

ACTION: None.

CAUSE: Error occurred in the DMOVIN intrinsic while attempting to obtain a record from the Joblog buffer.

ACTION: Check NRJE versions. Contact Hewlett-Packard.

CAUSE: Error encountered in NXDSUNLOCK.

ACTION: Contact Hewlett-Packard.

CAUSE: Error encountered in NXDSLOCK.

ACTION: Contact Hewlett-Packard.

CAUSE: Error encountered in NXDSWRITENL while attempting to store the LU's PIN in the XDS to reserve a reader.

ACTION: Contact Hewlett-Packard.

CAUSE: FOPEN failed while attempting to open the internal banner file (used to save host banners until banner decode succeeds).

ACTION: The preceding error message will indicate the nature of the file system error. The LU name is used as the file name of the banner file. Ensure that the LU name is a valid MPE file name.

CAUSE: The Output Destination identified in the NRJE Configuration: Writer Data screen could not be opened. One or more messages logged prior to this message identify the nature of the failure.

ACTION: Refer to the message(s) preceding this one to identify the nature of the failure. Correcting the problem will usually require either (1) reconfiguring the Writer Data screen, or (2) recovering lost disk space.

CAUSE: The Output Destination identified in the NRJE Configuration: Writer Data screen could not be opened. One or more messages logged prior to this message identify the nature of the failure.

ACTION: Refer to the message(s) preceding this one to identify the nature of the failure. Correcting the problem will usually require either (1) reconfiguring the Writer Data screen, or (2) recovering lost disk space.

CAUSE: DMOVIN failure occurred while attempting to lookup a form name in the FORMID XDS.

ACTION: Check NRJE versions. Contact Hewlett-Packard.

CAUSE: A formid was found in the Lookup Table XDS but the applicable record in the internal temporary copy of the Lookup Table could not be referenced.

ACTION: Refer to the preceding message for a description of FSERR. Contact Hewlett-Packard.

CAUSE: NRJE received what looked like an "ON READER" message but could not correctly identify the reader number in the message (valid reader number range is 1 to 7). If an actual "ON READER" message was received, then this reader will be unavailable for further job submissions.

ACTION: If the message is in fact an "ON READER" message then determine whether the format of the message has been modified by host system programmers. If the message has not been modified, contact Hewlett-Packard for assistance. If the message has been modified, install an exit procedure to parse the message. Refer to the NRJE User/Programmer Reference Manual for additional information.

CAUSE: GETWRITER was not passed a required parameter.

ACTION: Contact Hewlett-Packard.

CAUSE: FNUM or STATUS not passed to SET'OUTPUT'PARMS.

ACTION: Contact Hewlett-Packard.

CAUSE: A user wants to cancel his output, causing NRJE to route the output to $NULL which could not be opened.

ACTION: Contact Hewlett-Packard.

CAUSE: A user submitted a job specifying an alternate formid in the Lookup Table (for example, SUBMIT job;FO='formid') but NRJE is not configured to use a Lookup Table (Workstation Data screen).

ACTION: Contact the affected user.

CAUSE: A user specified an invalid routing option for print, punch, or forms disposition. Output was routed to the default destination identified in the Writer Data screen. Message number 9050 will be logged immediately following this message identifying the affected user and jobname.

ACTION: Contact the affected user.

CAUSE: File equation identified in the message could not be executed. Message number 335 preceded this message identifying the nature of the error.

The file equation came from one of two sources: (1) Lookup Table entry, or (2) user-specified file equation (for example, SUBMIT job;FO=*fileq)

ACTION: If source of the record was a Lookup Table entry, correct the entry and retry. Use the VERIFY command to check each record. If the source was a user specified file equation, contact the affected user.

CAUSE: FREAD intrinsic failure on the internal temporary copy of the Lookup Table.

ACTION: Contact Hewlett-Packard.

CAUSE: DMOVIN failure on the formid XDS.

ACTION: Contact Hewlett-Packard.

CAUSE: A user specified a form name which could not be found in the Lookup Table.

ACTION: Contact the affected user. Ensure that all users are informed of all form names supported by the workstation.

CAUSE: Failed to execute LOCKLOCRIN. Possibly due to a failure by NRJEMON to acquire the local rin.

ACTION: Check NRJE versions. Ensure that NRJEMON and NRJELU versions are compatible. Contact Hewlett-Packard.

CAUSE: As above.

ACTION: Depends upon the nature of the failure. Refer to other messages logged immediately prior to and after this message for corrective action.

CAUSE: A user specified an output routing option in the SUBMIT command but NRJE was unable to route the output as requested. The output was routed to the default destination specified in the writer data screen using an output priority of 2.

ACTION: Contact the affected user.

CAUSE: As above. Internal software error.

ACTION: Contact Hewlett-Packard.

CAUSE: The indicated error occurred while attempting to route a user's dataset to the proper destination.

ACTION: Contact the affected user.

CAUSE: A user specified a form name which could not be found in the Lookup Table.

ACTION: Contact the affected user. Ensure that all users are informed of all form names supported by the workstation.

CAUSE: A File System error occurred while attempting to open an output file for a user's dataset. Output will be routed to the default destination with an output priority of 2.

ACTION: Contact the affected user.

CAUSE: An exit procedure indicated it had decoded the host banner but returned a jobnumber which was not in the valid range of ASCII "-1" to ASCII "9999".

ACTION: Fix the procedure.

CAUSE: Information message. NRJE is receiving a dataset for which the host jobnumber was not found in the Joblog. This is true of all output received from POWER hosts.

ACTION: Determine whether the console message format has been changed by host system programmers. If true then install an exit procedure to correctly parse the "ON READER" message. If false, contact Hewlett-Packard for assistance.

CAUSE: If JES2 or JES3 then the job apparently did not originate at this remote. If the job did originate at this remote then either (1) NRJE did not correctly parse the host "ON READER" message indicating the host job number or (2) the host sent an output dataset prior to sending the "ON READER" message.

ACTION: Reduce the number of LU's for the workstation.

CAUSE: FLOCK intrinsic could not be executed on the Joblog file. The message logged immediately prior to this one describes the FSERR number. Internal software error.

ACTION: Contact Hewlett-Packard.

CAUSE: NRJE received a dataset with a host jobnumber for which an entry was found in the Joblog. However, the name of the job in the PDIR received from the host did not match with the name of the job in the Joblog record. This implies that the Joblog record is an 'old' entry and the host has recycled job numbers.

ACTION: Verify that the host has recycled job numbers since the indicated entry in the Joblog was made. If confirmed, execute the PURGE OLD command to clear the Joblog of old entries.

CAUSE: While writing a data set to a disk file, NRJE encountered an end of file condition on the output file.

ACTION: Inform the owner of the indicated job. The user should ensure that all disk files are large enough to contain the output.

CAUSE: NRJE received a punch dataset on the reserved command form CMD. Before NRJE can stream the file it must execute a REWIND, FREAD, and FCLOSE on the output file. The REWIND failed.

ACTION: Refer to the message logged immediately prior to this message to identify the nature of the failure.

CAUSE: NRJE received a punch dataset on the reserved command form CMD. Before NRJE can stream the file it must execute a REWIND, FREAD, and FCLOSE on the output file. The FREAD failed.

ACTION: Refer to the message logged immediately prior to this message to identify the nature of the failure.

CAUSE: Output was routed to either a Lookup Table file equation entry or to a file equation entered by a user with the SUBMIT command. NRJE failed to open using this file equation. The output was routed to the default destination with an output priority of two.

ACTION: Refer to the message logged immediately following this message to identify the nature of the failure. If failure was due to a Lookup Table entry, correct the entry (use the VERIFY command to ensure all entries are valid).

CAUSE: An FWRITE error occurred on an output file while receiving data from the host.

ACTION: Refer to the message logged immediately prior to this one which identifies the nature of the file system error.

CAUSE: NRJE received a dataset for which banner decode failed and the default Output Destination specified in the in the NRJE Configuration: Writer Data screen could not be opened to route the output.

ACTION: Refer to the messages logged immediately prior to this one to identify the nature of the failure to open the output file.

CAUSE: A banner decode exit procedure configured for a writer was loaded successfully.

ACTION: None.

CAUSE: A job was submitted to the host which returned a host job number. This number was found to represent an entry in the Joblog which already existed. This indicates that the host has begun to recycle job numbers and has therefore overwritten the Joblog entry.

ACTION: Execute the PURGE OLD command to clear the Joblog of expired entries.

CAUSE: Attempt was made to route output to a file of greater than 256 bytes, the maximum supported by NRJE. NRJE will still route the output to the destination file but will write a maximum of 256 bytes per record. NRJE pads with EBCDIC blanks when routing to fixed width disk files and will pad only to the maximum record width of 256 bytes.

ACTION: Inform the user of the affected job of the maximum supported record width.

CAUSE: A user is attempting to route output to a destination with a record width of less than 40 bytes.

ACTION: Inform the affected user of the supported record widths (40 to 256 bytes).

CAUSE: Advisory message only. An exit procedure did not return either JOBNUMBER or FILENUMBER to NRJE causing NRJE to pass the entire dataset to the exit procedure. It is presumed that the exit procedure has routed the dataset to the proper destination.

ACTION: None.

CAUSE: Advisory message only. An exit procedure did not return either JOBNUMBER or FILENUMBER to NRJE causing NRJE to pass the entire dataset to the exit procedure. It is presumed that the exit procedure has routed the dataset to the proper destination.

ACTION: None.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: A PDIR record was received. The first four bytes are displayed in hexadecimal, the remainder in ASCII.

ACTION:

CAUSE:

ACTION: Print STDLIST output and contact your HP representative.

CAUSE:

ACTION:

CAUSE: The indicated CPU time is in milliseconds.

ACTION:

CAUSE: Internal software error.

ACTION:

CAUSE: Internal software error.

ACTION:

CAUSE: A remote environment ID was specified in the Joblog entry which was appended to the output file name by the NRJE LU. The FOPEN of this file failed.

ACTION: Refer to the message logged immediately following this one to identify the nature of the failure. If the NS connection to the remote system has been lost then terminate and restart the workstation. Contact the affected user.

CAUSE: Occurs only while communicating with a JES3 host. NRJE was attempting to obtain information about Joblog records in the Joblog XDS by reading from the NRJE XDS. Internal software error.

ACTION: Contact Hewlett-Packard.

CAUSE: Access error on the Joblog buffer XDS. Internal software error.

ACTION: Contact Hewlett-Packard.

CAUSE: NRJE could not close a non-spooled output file while attempting to process a cancel request. NRJE returned the indicated sense code to the host.

ACTION: Refer to the message logged immediately prior to this one to identify the nature of the failure.

CAUSE:

ACTION:

CAUSE: FPOINT call failed even though NRJE had random access to an output file. Internal Software error.

ACTION: Contact Hewlett-Packard.

CAUSE: FREAD intrinsic failed on a non-spooled file even though NRJE had read access to the output file. Internal software error.

ACTION: Contact Hewlett-Packard.

CAUSE: A Joblog record built by the SUBMIT intrinsic contained an invalid format code. The SUBMIT and NRJELU software modules are incompatible.

ACTION: Check NRJE versions. Reinstall NRJE.

CAUSE: An attempt was made to route output to a job temporary file with a filename which duplicated that of one in the permanent system domain. Upon receiving the end of the dataset, NRJE will attempt to close the output file in the system domain which will fail.

ACTION: Inform the affected user. Output files should not be routed to the job temporary domain of NRJE.

CAUSE:

ACTION:

CAUSE: FCONTROL with parm=48 failed on the pipe file.

ACTION: Refer to the message logged immediately prior to this one for information on FSERR. Stop the workstation and purge any files in the group NRJE.SYS with the names THnnnnn and FHnnnnn, then restart the workstation. If the error is encountered a second time, contact Hewlett-Packard for assistance.

CAUSE: An attempt was made using a Lookup Table entry to route to a new disk file outside of the SYS account which is not allowed. NRJE cannot save new files across account boundaries.

ACTION: Delete any Lookup Table entries which attempt to direct NRJE to build files across account boundaries. Output should be routed to permanent disk files built by the user if routed outside of the SYS account. Alternately, output can be routed to new files in the SYS account but this can be done only once for each file. A second alternative is to use REVERSE NRJE to stream a job which can then build files in alternate accounts.

CAUSE: NRJE could not save a new disk file in the permanent domain due to a duplicate permanent file which already existed by this name. NRJE therefore saved the file with the new name of NRJEnnnn where nnnn represents the time (hours/minutes) at which the file was renamed.

ACTION: If a dataset is to be routed on a continual basis to the permanent disk domain then it should be routed to a permanent disk file. Replace the offending entry in the Lookup Table with one which uses the default domain of "old, permanent".

CAUSE: Output was routed to a new disk file which could not be closed to the permanent domain due to a duplicate permanent file of the same name. NRJE attempted to rename the output file to NRJEnnnn but this rename failed. The output for the data set was lost.

ACTION: If a dataset is to be routed on a continual basis to the permanent disk domain then it should be routed to a permanent disk file. Replace the offending entry in the Lookup Table with one which uses the default domain of "old, permanent".

CAUSE: Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: NRJE could not obtain a port for interprocess communication using the CREATIOWAITPORT system procedure. Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: The IOWAIT intrinsic return CCL. Internal error.

ACTION: Refer to the message logged immediately prior to this one for additional information on the file system error. Contact Hewlett-Packard.

CAUSE: An NRJE LU attempted to release the console facility when it was owned by another LU. Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: An NRJE LU attempted to access the "to host" console pipe to retrieve data without receiving a message indicating that console data was present. Internal error.

ACTION: Contact Hewlett-Packard.

CAUSE: An NRJE LU has console data from the host to deliver to one or more console users but the number of available message frames in the ports facility is insufficient. This message is repeated every 60 seconds until sufficient message frames become available. All NRJE activity will suspend until the console message can be delivered.

ACTION: Check any application programs which may have opened the console (with NRJEConsole) but has failed to receive messages using the NRJERcvMsg intrinsic.

CAUSE: A call to an NRJE intrinsic (such as NRJEConsole) failed.

ACTION:

CAUSE: FOPEN returned CCL on a the file.

ACTION: Refer to the preceding file system error message logged by NRJE.

CAUSE: File system error occurred on the output file.

ACTION: Refer to the preceding file system error message logged by NRJE.

CAUSE: NRJE cannot setup for multirecord access to an output spool file.

ACTION: Refer to the file system error message logged immediately prior to this message.

CAUSE: NRJE could not temporarily change the priority of an output spool file to 1 while attempting to set up for multi-record access to the output spool file.

ACTION: Contact Hewlett-Packard.

CAUSE: The system procedure NRJESPOOLALTER returned non-zero status while attempting to reset the output spool file priority and change its state to OPENED.

ACTION: Contact Hewlett-Packard.

CAUSE: The system procedure NRJESPOOLALTER returned non-zero status while attempting to change the state of an output spool file to READY.

ACTION: Contact Hewlett-Packard.

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE:

ACTION:

CAUSE: While releasing the console the access portid in the NRJE extra data segment could not be released. May have occurred while a system shutdown was in progress.

ACTION: Contact Hewlett-Packard.

CAUSE: A user in the host console facility released the console but the console access portid could not be found in the NRJE extra data segment. May have resulted from a workstation terminating just prior to the user attempting to release the console.

ACTION: Check preceding log messages to determine if a workstation had just terminated.

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: