SNA NRJE Node Manager’s Guide HP 3000 MPE/iX Computer Systems Edition 3 Manufacturing Part Number: 30292-90007 E1092 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. SNA NRJE Overview 2. SNA NRJE Installation Guidelines Bulletin File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 NRJE Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 NRJE Product Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.
Contents SNA NRJE Formatting Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 SNA NRJE Output Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Tracing Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 LU Trace Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Text Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 NRJECONTROL STATUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 RDRDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 8
Figures Figure 1-1. HP 3000-to-IBM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-1. Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-2. HP-IBM Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-3. NRJE Configuration Screen Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-4.
Figures 10
Tables Table 2-1. NRJE Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table 2-2. NRJE Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Table 3-1. AFC/NCP and ACF/VTAM Macro Corresponding Values . . . . . . . . . . . . . . . . . 24 Table 3-2. AFC/NCP and ACF/VTAM Logmode Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Table 3-3.
Tables 12
Preface This manual describes Hewlett-Packard Company’s Systems Network Architecture Network Remote Job Entry (SNA NRJE) product for both the MPE V (NRJE/V) and MPE XL (NRJE/XL) operating systems. Systems Network Architecture (SNA) is a comprehensive specification for distributed data processing networks, developed by IBM. NOTE In this manual, the term NRJE is used when the information being given is true for both NRJE/V and NRJE/XL.
Organization This manual is divided into the following chapters and appendix: Chapter 1 , “SNA NRJE Overview,” contains an overview of SNA NRJE and the components of the network. Chapter 2 , “SNA NRJE Installation Guidelines,” discusses installation procedures. Chapter 3 , “SNA NRJE Configuration,” explains how to use the NM configuration manager (NMMGR) to create a hierarchical configuration file for SNA NRJE.
Related HP Publications As an SNA NRJE node manager, you can find related information in these manuals: • Getting Started With SNA Node Management (MPE V only) • Using the Node Management Services Utilities (MPE XL only) • SNA Link Services Reference Manual (MPE V only) • SNA Link/XL Node Manager’s Guide (MPE XL only) • SNA NRJE User/Programmer Reference Manual • HP SNA Products: Manager’s Guide Host System Programmer’s Reference • HP SNA Products: ACF/NCP and ACF/VTAM Guide Host System Programmer's Referen
1 SNA NRJE Overview Systems Network Architecture Network Remote Job Entry (SNA NRJE) is a data communications package that provides HP-to-IBM batch communications in a Systems Network Architecture (SNA) environment. With SNA NRJE, you can submit batch jobs for processing on an IBM host. A spool file is created to receive the input job files. Once communication with the host starts and the host begins to accept job input, each job is routed to its destination based on its position in the queue.
SNA NRJE Overview Figure 1-1 HP 3000-to-IBM Communication 18 Chapter 1
2 SNA NRJE Installation Guidelines To run SNA NRJE on your HP 3000, you and your HP representative must install the product and configure both your HP 3000 environment and the host system to support SNA NRJE. As part of the configuration process, you must ensure that the HP 3000 parameters match those on the host side. The necessary parameters are described in Chapter 3 , “SNA NRJE Configuration,” of this manual.
SNA NRJE Installation Guidelines Bulletin File Bulletin File Additional configuration and user information not documented in any of the SNA NRJE manuals can be found in the file BULLETIN.NRJE.SYS. NRJE Segments The segments listed in Table 2-1 are necessary to run SNA NRJE. On MPE V and releases 1.1, 1.2, and 2.0 of MPE XL, all four segments are located in SL.PUB.SYS. On MPE XL release 2.1 and later, NRJEINT, NRJEMISC, and NRJEMISC2 are located in NRJEXL.NRJE.SYS. NRJEMISC3 is located in SL.PUB.
SNA NRJE Installation Guidelines NRJE Product Files NRJE Product Files These NRJE product files must be in NRJE.SYS unless otherwise indicated. Refer to Table 2-2. Table 2-2 NRJE Files File Name Contents IONRDR0 NRJE Virtual Reader Driver. IONRDR0 must be in PUB.SYS (MPE V only). NRJE NRJE subsystem command interpreter. NRJECAT NRJE message catalog. NRJECONS NRJE console program. This program is run as a son process of the NRJE command interpreter. NRJELU LU program. Son process of NRJEMON.
SNA NRJE Installation Guidelines NRJE Product Files 22 Chapter 2
3 SNA NRJE Configuration This chapter describes how to use the NM configuration manager (NMMGR) to create or modify a hierarchical configuration file for SNA NRJE. For NRJE/V, you also must configure the virtual reader through the SYSDUMP utility. (See the SNA Link Services Reference Manual.) NOTE Before you can configure SNA NRJE, you must have successfully configured the SNA link (including logging).
SNA NRJE Configuration Data Required From the Host Configuration Data Required From the Host Configuration Data in an NRJE configuration file must correspond to information from the host configuration. Before using NMMGR, you should have certain information from the host configuration. You must coordinate the SNA NRJE configuration with the ACF/NCP, ACF/VTAM, JES2 or JES3, and VSE/POWER host configurations. The HP SNA Products guides explain these configurations.
SNA NRJE Configuration Data Required From the Host Configuration NOTE If you are using JES2 version 1.3.6 (or later) or 2.1.5 (or later), the &STDFORM parameter is different; use the migration tables to determine the correct &STDFORM. For JES2 version 3 (or later), use COMPRESS=YES instead of COMP. Table 3-4 shows the relationship between items from the host configuration and items in the NRJE configuration file.
SNA NRJE Configuration Data Required From the Host Configuration Table 3-5 JES3 Global Parameter Corresponding Values Host Configuration Global Parameter and Subparameter Field in NMMGR Screen SNA NRJE NMMGR Screen BUFFER BUFSIZE Logical Unit RU Size Workstation Data OUTSERV FORMS Host Standard Print Form Name Workstation Data Page 2 CDSTOCK Host Standard Punch Form Name Workstation Data Page 2 APPLID APPLID Workstation Data COMMDEFN Table 3-6 shows the relationship between items from t
SNA NRJE Configuration NMMGR Configuration Overview NMMGR Configuration Overview After you have completed the SYSDUMP configuration (for NRJE/V) to install the virtual reader, and after the link is configured, you are ready to configure NRJE. The configuration is done by using NMMGR to create or modify a configuration file. The basic operation of NMMGR is described in Using the Node Management Services Utilities; if you are not familiar with NMMGR, you should read that manual before continuing.
SNA NRJE Configuration NMMGR Configuration Overview • Readers. This is transmission and translation information about each logical reader. For JES2 and JES3, you must configure from one through seven readers. For VSE/POWER, one reader is assumed. The number of logical readers must match the number of readers configured on the host. • Writers. This is translation and formatting information about each logical writer. The logical writers receive output data streams from the host.
SNA NRJE Configuration NMMGR Configuration Overview NOTE NRJE logging is not configured through the NRJE Configuration screens. See “The Logging Facility” in Chapter 5 , “SNA NRJE Troubleshooting,” of this manual for information on logging configuration.
SNA NRJE Configuration Configuration File Validation Configuration File Validation Validating the configuration file ensures that the configuration data is logically and syntactically correct. Each SNA service’s data is also checked against the SNA node configuration data for correctness (for example, correct LU names). See Appendix A , “Result Codes and Messages,” of this manual for SNA NRJE validation error messages.
SNA NRJE Configuration Configuration File Validation CRITICAL SUMMARY - NRJE CONFIGURATION THU, FEB 16, 1989, 2:49 PM CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS Validated subsystem.
SNA NRJE Configuration Configuring SNA NRJE Configuring SNA NRJE Once you have opened the configuration file, you are placed in the NMMGR Main screen. Main Screen From the Main Screen you can select the category of network subsystems you want to configure, as shown in Figure 3-1. Figure 3-1 Main Screen To access the NMMGR branch for configuring SNA NRJE, press [f4] (Go To HP-IBM). This places you at the HP-IBM Configuration screen.
SNA NRJE Configuration Configuring SNA NRJE HP-IBM Configuration Screen From the HP-IBM Configuration Screen you can select the item you want to configure, see Figure 3-2. Figure 3-2 HP-IBM Configuration Screen To select NRJE configuration press [f3] [Go To NRJE]. NRJE Configuration Screen After you have selected NRJE configuration, NMMGR displays the NRJE Configuration Screen, as shown in Figure 3-3.
SNA NRJE Configuration Configuring SNA NRJE Figure 3-3 NRJE Configuration Screen Example Fields Path For display only. The NMMGR branch you are in. WSID Name The name of the new workstation you are configuring, or the existing NRJE workstation whose configuration you are modifying. The name can be up to eight alphanumeric characters long; the first character must be alphabetic. New Name The new name of an existing NRJE workstation.
SNA NRJE Configuration Configuring SNA NRJE fields); no more than 8 workstations can be active at one time. File For display only. The name of the configuration file. Once you have entered the name of the workstation, press [f5] [Add] if this is a new configuration, or press [f6] [Modify] if you are modifying a configuration. This places you at the NRJE Configuration: Workstation Data screen.
SNA NRJE Configuration Configuring SNA NRJE Fields Path For display only. The NMMGR path for this screen. It includes the name of the NRJE workstation you are configuring. SNAnode Name Required. The name of the SNA node the workstation is to use. Host Configuration: For troubleshooting purposes, we strongly recommend that this match the puname operand of the PU macro that defines this node on the host (VTAM); see Table 3-1. Remote Node Number Required. This identifies the workstation to the host.
SNA NRJE Configuration Configuring SNA NRJE Default: Blank (use the first entry in the Logmode Table) Host Configuration: This must match the LOGMODE parameter of the MODEENT macro in the Logmode Table entry used by this workstation (VTAM); see Table 3-2. APPLID Required. The VTAM application identifier for the host job entry subsystem. If you do not know the correct identifier to enter here, ask the host system programmer.
SNA NRJE Configuration Configuring SNA NRJE Host Command Prefix Char Required. The character preceding all host console commands. Host Configuration: • JES2 and JES3: The command prefix can be configured; this parameter must match the prefix specified in the host job entry subsystem configuration. • VSE/POWER: The value entered here is used interactively only. VSE/POWER commands must be entered using this prefix. Any non-interactive VSE/POWER command must still be preceded by *∆ . .
SNA NRJE Configuration Configuring SNA NRJE Job Management Required. Enter Y to cause the output routing options (PRINT, PUNCH, and FORMS) of the SUBMIT command to be supported; N, otherwise. Default: Y Logical Unit RU Size Required. The maximum size of the RUs, in bytes, that NRJE can send to the host. Values: 256, 512, and 768 (integer) Default: 256 Host Configuration: This must match the RUSIZES parameter of the MODEENT macro in the Logmode Table entry used by the workstation; see Table 3-2.
SNA NRJE Configuration Configuring SNA NRJE Figure 3-5 Workstation Data Page 2 Screen Example Fields Path For display only. The NMMGR path for this screen. It includes the name of the NRJE workstation you are configuring. Console Scan Procedure The name of a user-defined procedure which scans the host console for an “on reader” message. For further information about creating your own procedure, see the SNA NRJE User/Programmer Reference Manual.
SNA NRJE Configuration Configuring SNA NRJE Punch Banner Code Required. The code the punch banner is in. Enter H for Hollerith, or E for EBCDIC. Default: H Punch Banner Job Number Location Required. The location in which the host job number begins in a punch banner. Range: 0 – 76 (integer) Default: 0 (the beginning of the banner) Joblog Data File Required. The data file (in NRJE.SYS) containing information about each job submitted.
SNA NRJE Configuration Configuring SNA NRJE • JES3: This must match the FORMS subparameter of the OUTSERV global parameter; see Table 3-5. If FORMS is not specified, enter 1PRT here. • VSE/POWER: Enter all blanks. Host Standard Punch Form Name The default punch form name for the workstation. This must match the name of the form in the Peripheral Data Information Record (PDIR) for output routed to the standard form on a punch device. To determine this, see the SNA NRJE User/Programmer Reference Manual.
SNA NRJE Configuration Configuring SNA NRJE [ENTER].) The LUs implement the logical readers and the logical writers. Note that the LUs are pooled: A given LU can implement any of the logical readers or writers. Figure 3-6 LU Data Screen Example Fields Path For display only. The NMMGR path for this screen. It includes the name of the workstation whose LUs you are configuring. Configured NRJE LUs (Under Workstation) The names of the LUs you want to configure for the workstation.
SNA NRJE Configuration Configuring SNA NRJE Autostart Enter Y if you want the LU to be automatically initialized when the workstation is started up; N, otherwise. You can override this at workstation startup time. Note that you cannot enter a value in this field if a value is not also entered in the corresponding LU Name field. Default: N File For display only. The name of the configuration file. Once you have entered the data for all of the LUs, press [f6] [Save Data].
SNA NRJE Configuration Configuring SNA NRJE Figure 3-7 Reader Data Screen Example Fields Path For display only. The NMMGR path for this screen. It includes the name of the workstation whose virtual reader you are configuring. Logical Device Required. The ldev to which NRJE will spool submitted jobs. For NRJE/V, you must configure this ldev into the I/O system by using the SYSDUMP utility (see the SNA Link Services Reference Manual); this must be followed by a cold start.
SNA NRJE Configuration Configuring SNA NRJE back-referenced to the ldev number of the INP or the system disk. Set the record width to 40 words; set the unit, channel, and output device to 0. Specify driver IONRDR0. Chain Size Required. The maximum number of RUs that NRJE will transmit before requiring a definite response from the host. You can get higher throughput with larger values, but if line trouble occurs, the data might have to be retransmitted from the beginning of the chain.
SNA NRJE Configuration Configuring SNA NRJE Host Configuration: • JES2: This must be less than or equal to the NUMRD parameter of the RMTnnnn macro; see Table 3-4. • JES3: This must be less than or equal to the RD parameter of the RJPWS macro; see Table 3-6. • VSE/POWER: This field is ignored (because one reader is assumed). Compression On Required. Enter Y if the host accepts compressed in-bound data; N, otherwise.
SNA NRJE Configuration Configuring SNA NRJE Writer List Screen Once you have configured the workstation’s virtual reader, you should configure the virtual writers. You do this on the NRJE Configuration: Writer List Screen, as shown in Figure 3-8. Select this screen by pressing [f3] (Go To WRITER) on the NRJE Configuration: Workstation Data screen. (You can go directly to this screen from any screen by typing @NRJE.wsid.WRITER in the command window and pressing [ENTER].
SNA NRJE Configuration Configuring SNA NRJE Writer Name The name of the new writer you are configuring, or the existing writer whose configuration you are modifying. The name must be in one of these formats: • PRx = a logical printer, where x is an integer from 1 through 7. • PUx = a logical punch, where x is an integer from 1 through 7. Host Configuration: • JES2: This must match the PRm or PUm portion, respectively, of the Rnnnn.PRm or Rnnnn.PUm macro; see Table 3-4.
SNA NRJE Configuration Configuring SNA NRJE File For display only. The name of the configuration file. Once you have entered the name of the writer, press [f5] (Add) if this is a new configuration, or press [f6] (Modify) if you are modifying a configuration. This places you at the NRJE Configuration: Writer Data screen. Writer Data Screen After you have selected a writer, NMMGR displays the NRJE Configuration: Writer Data Screen, as shown in Figure 3-9.
SNA NRJE Configuration Configuring SNA NRJE Output Destination Required. The default destination for output received on the writer. Enter an MPE device class specification (eight alphanumeric characters or less), an ldev number of a spooled device, or a formid (in single quotes). Use the formid to specify a Lookup Table entry that defines the default output device characteristics. Forced Required.
SNA NRJE Configuration Configuring SNA NRJE must have specified the same value for the Translation Indicator field on the NRJE Configuration: Reader Data screen. Invalid values are: 201 Simplified Chinese 211 Traditional Chinese 221 Japanese 231 Korean For more information on Native Language support, see the Native Language, Message Catalogs, and User Logging manual.
4 NA NRJE Workstation Startup and Shutdown This chapter describes how SNA NRJE workstations are started up (establishing an LU-LU session) and how workstations are shutdown (terminating an LU-LU session).
NA NRJE Workstation Startup and Shutdown Before You Start a Workstation Before You Start a Workstation Before you begin starting up workstations, you must have prepared a job stream file for each workstation you want to start. Each job must be named Wsid.NRJE.SYS, where Wsid is the workstation’s configured identification. When you issue a command to start an NRJE workstation, the corresponding Wsid.NRJE.SYS file is streamed. Each job must be in this format: !JOB NRJEuser.SYS,NRJE any JCWS, etc.
NA NRJE Workstation Startup and Shutdown Starting a Workstation Starting a Workstation Once you have created the corresponding stream job files, you can start up the workstations. To use an SNA NRJE workstation, you must initiate an LU-LU session between an HP 3000 LU (the secondary LU) and a host LU (the primary LU). An NRJE LU-LU session is initiated by the LU in the HP 3000 node, with the MPE command NRJECONTROL START or the NRJE command STARTWS (see Chapter 6 , “Commands,” of this manual).
NA NRJE Workstation Startup and Shutdown Starting a Workstation Figure 4-1 SNA NRJE LU-LU Session Initiation 56 Chapter 4
NA NRJE Workstation Startup and Shutdown Stopping a Workstation Stopping a Workstation An LU-LU session exists to allow two users to communicate in an SNA network. Once that communication is completed, the LU-LU session should be terminated to allow the LUs to participate in other LU-LU sessions. Terminating an LU-LU session stops an NRJE workstation (after all NRJE LUs are down).
NA NRJE Workstation Startup and Shutdown Stopping a Workstation Figure 4-2 SNA NRJE LU-LU Session Termination 58 Chapter 4
5 SNA NRJE Troubleshooting You can troubleshoot SNA NRJE by using the tracing and logging facilities. This chapter describes the following: • The tracing facility. • The logging facility. • Using the NMDUMP utility for SNA NRJE. • Using the NMMAINT utility for SNA NRJE. • Resolutions to common problems. • Guidelines for submitting service requests (SRs). • Troubleshooting output routing problems. • Troubleshooting exit procedures.
SNA NRJE Troubleshooting The Tracing Facility The Tracing Facility Tracing is an interpretive diagnostic technique that provides data for analysis, and can be done at many levels. SNA link tracing is done at the lowest level and at an intermediate level (see the SNA Link Services Reference Manual, or the SNA Link/XL Node Manager’s Guide). SNA NRJE tracing is at the highest level, and is controlled through MPE commands or NRJE commands (see Chapter 6 , “Commands,” of this manual).
SNA NRJE Troubleshooting The Tracing Facility to a disk file. The trace file name can be specified as an argument to any of the commands used to start tracing. Naming the file this way allows the contents of the file to be overwritten each time a new trace is started (no warning is issued). Or you can let the default name be assigned: NMTCnnnn.PUB.SYS, where nnnn is a number from 0000 through 9999. The trace file can be formatted through the NMDUMP utility.
SNA NRJE Troubleshooting The Logging Facility The Logging Facility Logging records subsystem events — significant normal events, as well as error events — for use in problem determination. SNA NRJE logging is configured through NMMGR (see the SNA Link Services Reference Manual [for MPE V] or the SNA Link/XL Node Manager’s Guide [for MPE XL]), and it is controlled through the MPE commands SHOWNMLOG, SWITCHNMLOG, and RESUMENMLOG.
SNA NRJE Troubleshooting The Logging Facility Example An example of SNA NRJE console logging (logging displayed on the HP 3000 console) is shown below. In this example, the user followed the logging configuration guidelines in the SNA Link Services Reference Manual or the SNA Link/XL Node Manager’s Guide, and turned on logging for SNA NRJE class CLAS0012. Note that JES2 is NAU 1 at the host (shown as Remote NAU = 1).
SNA NRJE Troubleshooting The Logging Facility NRJE Logging SNA NRJE receives UNBIND THU, MAR 1, 1984, 11:11 AM for LU01. NRJE (R20 ;LU01 ) - RECEIVED UNBIND= 3201 (SC=1224) SNA/TRANSPORT Logging Session terminated on node PU3000E Local NAU = 1 , Remote NAU = 100 SNA Transport logs session termination. NRJE Logging SNA NRJE receives UNBIND THU, MAR 1, 1984, 11:11 AM for LU04.
SNA NRJE Troubleshooting Using NMDUMP for SNA NRJE Using NMDUMP for SNA NRJE When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the SNA NRJE ID: 2. Then, proceed normally with NMDUMP. Note that NMDUMP is described in more detail in the SNA Link Services Reference Manual (for MPE V) and in Using the Node Management Services Utilities (for MPE XL).
SNA NRJE Troubleshooting Using NMDUMP for SNA NRJE • Option 3 specifies whether character mode is to be on or off. If character mode is on, each unformatted hexadecimal or octal output line is followed by a line containing the corresponding printable characters in the character code specified by option 4. Nonprintable characters are represented as periods. • Option 4 specifies the character code the data is to be printed in: ASCII or EBCDIC.
SNA NRJE Troubleshooting Using NMDUMP for SNA NRJE Intrinsic Trace Records Intrinsic trace records are type 1, and are formatted according to two subtypes: • Subtype 0: workstation number • Subtype 1: wsid and number SNA NRJE produces a subtype 1 intrinsic trace record for the first intrinsic trace record in a trace file for a given workstation. (Any continuation records for subtype 1 intrinsic trace records are also subtype 1.
SNA NRJE Troubleshooting Using NMDUMP for SNA NRJE Logging Records Logging records that reflect an error (logging class CLAS0010 [noncritical errors] or CLAS0012 [critical errors]) are formatted with a border of asterisks. This distinguishes them from logging records that do not reflect an error (which do not have a border). The first 16 bits of a logging record are printed in the “Logging word” field.
SNA NRJE Troubleshooting Using NMMAINT for SNA NRJE Using NMMAINT for SNA NRJE The NMMAINT utility displays the version numbers of the HP data communications software installed on your system. The example below shows the SNA NRJE information displayed when you run NMMAINT. Note that the version numbers shown below are not necessarily the current version numbers for SNA NRJE; they are shown only as an example.
SNA NRJE Troubleshooting Problem Resolution Problem Resolution Problems that can occur while installing, configuring, and running SNA NRJE — and how to deal with them — are described here. Guidelines for submitting a service request (SR) are also described.
SNA NRJE Troubleshooting Problem Resolution Common Problems Some problems are common to many situations — invalid software installation, version incompatibilities, insufficient MPE resources, corrupt configuration files, and file system errors. In most cases, you can resolve these problems yourself; the resolutions to these problems are described here. However, in some cases you should submit an SR.
SNA NRJE Troubleshooting Problem Resolution to be localized to a particular item, delete that item and reconfigure it. If necessary, RESTORE a backup copy of the file. File System Errors A file system error (FSERR)might have occurred while attempting to access the configuration file. Try to access the configuration file, under the same userid, using NMMGR. Use the NMMGR error screen to find out what the underlying FSERR is. Correct the problem and retry.
SNA NRJE Troubleshooting Problem Resolution A macro could be missing a required operand or you might have specified an invalid operand for a particular macro. • Incorrect Logmode Table definition. Ensure that you are using the correct Logmode Table definitions. See the HP SNA Products: ACF/NCP and ACF/VTAM Guide Host System Programmer’s Reference for more information.
SNA NRJE Troubleshooting Problem Resolution SNA NRJE Run-Time Problems After both the hardware and software are installed, problems might occur. Many run-time problems are caused by inaccurate configuration. You might encounter some of these problems while trying to run NRJE or while actually running NRJE: • Inactive SNA node. If you try to run SNA NRJE without starting the node on which NRJE will be running, you will receive this message: Inactive node or invalid node name.
SNA NRJE Troubleshooting Problem Resolution • SNA Transport activates, but one or more SNA NRJE LUs do not (MPE V only). — Ensure that the transmit buffer size (in the Link Configuration: SNA/SDLC Link Data screen), the maximum RU size (in the SNA Configuration: LU Data screen), and the RU size (in the NRJE Configuration: Reader Data screen) are consistent.
SNA NRJE Troubleshooting Problem Resolution NOTE Remember to consult Appendix A , “Result Codes and Messages,” of this manual for a description of error messages and intrinsic result codes. You might encounter other error messages while using SNA NRJE. See the SNA Link Services Reference Manual (for MPE V) or Using the Node Management Services Utilities (for MPE XL) for generic messages produced by NMMGR and the utilities NMMAINT and NMDUMP.
SNA NRJE Troubleshooting Submitting an SR Submitting an SR Listed below are some guidelines for submitting a service request (SR). Some of the guidelines refer to Node Management Services (NMS) programs (NMDUMP, NMMAINT, NMMGR, etc.). Using NMDUMP and NMMAINT for SNA NRJE is explained earlier in this chapter. Using NMMGR for SNA NRJE is explained in Chapter 3 , “SNA NRJE Configuration,” of this manual.
SNA NRJE Troubleshooting Submitting an SR • Try to determine the general area, within the software, where you think the problem exists. If you think the problem is caused by an SNA link, refer to the SNA Link/XL Node Manager’s Guide, and follow the guidelines there for gathering information for problems. • Document your interim, or “workaround,” solution. The cause of the problem can sometimes be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur.
SNA NRJE Troubleshooting Submitting an SR SNA Transport Information For problems that might involve SNA Transport, see the SNA Link Services Reference Manual or the SNA Link/XL Node Manager’s Guide, keeping this in mind: • For NRJE/V, when using the MPE command ABORTIO ldev to try to free an SNA Transport hang, ldev specifies the INP being used.
SNA NRJE Troubleshooting Troubleshooting Output Routing Problems Troubleshooting Output Routing Problems Information to help you resolve problems you might have with output returning from the host and being routed to an unexpected destination is given below.
SNA NRJE Troubleshooting Troubleshooting Output Routing Problems Try routing with the FORMS= keyword even though the output is presumably being received on the “standard” form. If output is routed to the desired destination this time, then either the configuration for the Host Standard Print Form Name or Host Standard Punch Form Name in the NRJE Configuration: Workstation Data Page 2 Screen is incorrect, or your job is actually generating “special forms” output.
SNA NRJE Troubleshooting Troubleshooting Output Routing Problems • A Formid Lookup Table entry specifying both an environment file and hard copy form mount does not work. NRJE opens the output file with the hard copy form mount message but ignores the environment file. To select both an environment file and hard copy form, always specify the environment file first. For example, enter: :checks;dev=pp ;env=checkenv.hpenv.sys;forms=checks. Do not enter: :checks2;dev=pp;forms=checks. ;env=checkenv.hpenv.
SNA NRJE Troubleshooting Troubleshooting Exit Procedures Troubleshooting Exit Procedures If an exit procedure is needed to parse either the host banner or “Job Received” message, then these guidelines will be helpful in troubleshooting exit procedures. Using the DEBUG Facility To use the DEBUG facility, you must declare the DEBUG intrinsic in your exit procedure: Intrinsic debug; Then, at the appropriate points in your procedure you can execute calls to DEBUG.
SNA NRJE Troubleshooting Troubleshooting Exit Procedures 84 Chapter 5
6 Commands This chapter describes commands that can be used by a node manager (or any other user with NM capability) to manage NRJE operations: • MPE commands for SNA NRJE. • NRJE manager commands. Users without NM capability can be allowed to use host console commands if the commands are configured in the Allowed Host Commands field of the NRJE Configuration: Workstation Data screen. SNA NRJE displays a prompt string after a command has executed.
Commands MPE Commands MPE Commands Described below, in alphabetical order, are the MPE commands for SNA NRJE. You must have MPE node manager (NM) capability to use these commands. Table 6-1 summarizes the function of each command. Table 6-1 MPE Commands for SNA NRJE Command Function NRJECONTROL HALT Stops active LU-LU sessions immediately. NRJECONTROL START Starts a workstation or individual LUs, and optionally starts intrinsic and/or LU tracing.
Commands NRJECONTROL HALT NRJECONTROL HALT Stops active LU-LU sessions immediately. Syntax NRJECONTROL HA[LT];W[SID]=Wsid[;LU=LUName[,LUName ]...] Parameters Wsid Required. The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. The workstation must have been configured. LUName For NRJE/V, this is the name of the SNA node LU class whose LU-LU sessions you want to stop.
Commands NRJECONTROL HALT An LU-LU session can also be stopped without issuing an NRJECONTROL HALT in these ways: • By issuing the NRJE command HALT. • By issuing the NRJE command STOPWS. • By issuing the MPE command NRJECONTROL STOP. • By issuing the MPE command SNACONTROL STOP. • By the host job entry subsystem; SNA NRJE honors the request. This can happen at any time. Text Reference See NRJECONTROL STOP, HALT, and STOPWS later in this chapter.
Commands NRJECONTROL START NRJECONTROL START Starts a workstation or individual LUs, and optionally starts intrinsic and/or LU tracing. Syntax NRJECONTROL STAR[TWS];W[SID]=Wsid [;CH[AINSIZE]=NumRUs] [;LU=LUName[,LUName]...] [;TR[ACE]=Type[,Type][,File][,Size]] Parameters Wsid Required. The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. The workstation must have been configured.
Commands NRJECONTROL START Type The type of trace to be started: • LU: for NRJE LU procedures. • INTRINSIC: for intrinsics accessed by NRJE workstation users and managers. These intrinsics are traced: NRJEAlter NRJECancel NRJEConsole NRJEHJCancel NRJEHJInfo NRJEJobInfo NOTE NRJELUList NRJELUStatus NRJEQueue NRJERdrAccess NRJERdrFence NRJEStartWS NRJEStopWS NRJESubmit NRJE2Submit NRJETrace NRJEWriter NRJEWSInfo Use this option only when recommended by your HP representative.
Commands NRJECONTROL START If you omit this parameter, a default of 1024 is used. Description When the NRJECONTROL START command is issued, the NRJE monitor is streamed and runs as an MPE job. (See Chapter 4 , “NA NRJE Workstation Startup and Shutdown,” of this manual.) You can start a workstation or individual LUs. If you do not specify any LUNames, all LUs configured to be initially started are started. If you specify LUName, only those LUs are started.
Commands NRJECONTROL STATUS NRJECONTROL STATUS Displays the current status of LU sessions. Syntax NRJECONTROL STATUS[;W[SID]=Wsid][;LU=LUName[,LUName]...] Parameters Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command.
Commands NRJECONTROL STOP NRJECONTROL STOP Stops active LU-LU sessions in an orderly manner. Syntax NRJECONTROL STO[P];W[SID]=Wsid[;LU=LUName[,LUName]...] Parameters Wsid Required. The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. The workstation must have been configured. LUName For NRJE/V, this is the name of the SNA node LU class whose LU-LU sessions you want to stop.
Commands NRJECONTROL STOP An LU-LU session can also be stopped without issuing an NRJECONTROL STOP in these ways: • By issuing the NRJE command HALT. • By issuing the NRJE command STOPWS. • By issuing the MPE command NRJECONTROL HALT. • By issuing the MPE command SNACONTROL STOP. • By the host job entry subsystem; SNA NRJE honors the request. This can happen at any time. Text Reference See NRJECONTROL HALT earlier in this chapter, and HALT and STOPWS later in this chapter.
Commands NRJECONTROL TRACEOFF NRJECONTROL TRACEOFF Turns off intrinsic and/or LU tracing for a workstation. Syntax NRJECONTROL TRACEOF[F];W[SID]=Wsid[;TRACE=Type[,Type]] Parameters Wsid Required. The workstation name. This can be up to eight alphanumeric characters long; the first letter must be alphabetic. The workstation must have been configured. Type The type of trace to be stopped: • LU: for NRJE LU procedures.
Commands NRJECONTROL TRACEON NRJECONTROL TRACEON Turns on intrinsic and/or LU tracing for a workstation. Syntax NRJECONTROL TRACEON;W[SID]=Wsid [;TRACE=Type[,Type][,File][,Size]] Parameters Wsid Required. The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. The workstation must have been configured. Type The type of trace to be started: • LU: for NRJE LU procedures.
Commands NRJECONTROL TRACEON If you specify a disk file that does not exist, it will be created as the destination for trace output. If you specify an existing file, and it already is in use for trace output, then trace output records for this activity are interleaved with other trace output records. You minimize the use of disk space by using an old file appropriately; however, trace output can be overwritten.
Commands NRJECONTROL VERSION NRJECONTROL VERSION Lists the version numbers of SNA NRJE software. Syntax NRJECONTROL VERSION Description This command lists the version numbers of SNA NRJE program files, segments, the message file, and the overall version. Output from NRJECONTROL VERSION is sent to $STDLIST.
Commands NRJE Manager Commands NRJE Manager Commands Most subsystem commands are available only to NRJE managers (users with NM capability). Users without NM capability can have access to the console commands, provided that one or more of the commands have been “allowed” in the NRJE configuration file. (This is described later in this chapter.) Table 6-2 summarizes NRJE manager commands.
Commands User Commands with Manager Extensions User Commands with Manager Extensions NRJE managers (users with NM capability) use the commands in Table 6-3 with extended features. These commands are also available to users, but without features. The commands are described in the SNA NRJE User/Programmer Reference Manual. Table 6-3 User Commands with NRJE Manager Extensions Command Function ALTER Revises the priority of a submitted job or jobs. CANCEL Purges jobs awaiting transmission.
Commands Remote Console Facility for NRJE Users Remote Console Facility for NRJE Users Users who do not have NM capability can access the remote console facility, provided one or more commands have been “allowed.” This is done through the Allowed Host Commands field on the NRJE Configuration: Workstation Data screen. If desired, the NRJE manager can limit remote console access to only those who have NM capability, by setting the Allowed Host Commands field to all blanks.
Commands CONSOLE CONSOLE Obtains access to the host remote console of a workstation. Syntax CONSOLE Description This command obtains access to the host console of a workstation. While you have access to the console, the console mode prompt that you have configured for the workstation is displayed on the screen in place of the usual NRJE prompt. (The console mode prompt is configured in the NRJE Configuration: Workstation Data screen.
Commands CONSOLE While you have access to the console, you receive all console messages issued by the host. So, you can receive console messages in response to your own commands, as well as messages in response to commands by other users. You also receive all other output sent by the host to the remote console. This includes host “Job Received” messages sent by some host systems when a job is received from a remote workstation. NRJE writes this output to your job or session output device, $STDLIST.
Commands CONSOLE Text Reference Programmatic access to the host remote console is provided by these manager intrinsics: • NRJEConsole: obtains access to the console. • NRJESendCmd: transmits a console command. • NRJEConsCheck: determines whether any outstanding host remote console messages are waiting to be received. • NRJERcvMsg: receives a console message. • NRJERelease: relinquishes access to the console. These intrinsics are described in the SNA NRJE User/Programmer Reference Manual.
Commands HALT HALT Stops active LU-LU sessions immediately. Syntax H[ALT][;W[SID]=Wsid][;LU=LUName[,LUName]...] Parameters Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. LUName For NRJE/V, this is the name of the SNA node LU class whose LU-LU sessions you want to halt.
Commands HALT An LU-LU session can also be stopped without issuing a HALT in these ways: • By issuing the NRJE command STOPWS. • By issuing the MPE command NRJECONTROL HALT. • By issuing the MPE command NRJECONTROL STOP. • By issuing the MPE command SNACONTROL STOP. • By the host job entry subsystem; SNA NRJE honors the request. This can happen at any time. Text Reference See NRJECONTROL HALT and NRJECONTROL STOP earlier in this chapter, and STOPWS later in this chapter.
Commands PURGE PURGE Purges entries in the NRJE Joblog. This command does not apply if you are connected to a VSE/POWER host system. Syntax {ALL} PUR[GE] {O[LD][;DATE=Date[;TIME=Time{AM}]]}[;W[SID]=Wsid] {PM} Parameters ALL Empties the Joblog file. NRJE prompts you with PURGE ENTIRE JOBLOG, (Y/N)? OLD Purges entries for cancelled jobs and jobs that were placed in the Joblog prior to the specified date and time. (Entries are placed in the Joblog at the time of transmission to the host.
Commands PURGE Description This command allows you to purge entries in the NRJE Joblog. NOTE If you are running SNA NRJE in batch mode, the PURGE command will execute without asking you to confirm it with a Y or an N. If exclusive access to the Joblog can be obtained, then disk space can be recovered by a PURGE. Otherwise, Joblog entries will be marked for deletion with no space recovery. Exclusive access can be obtained only while the workstation is inactive.
Commands RDRDOWN RDRDOWN Disables the reader of an NRJE workstation. Syntax RDRD[OWN] [Wsid] Parameter Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. Description This command disables the reader of an NRJE workstation.
Commands RDRFENCE RDRFENCE Updates the outfence value of the NRJE workstation reader. Syntax RDRF[ENCE] ReaderOutFence[;W[SID]=Wsid] Parameters ReaderOutFence Required. The output fence for the workstation reader. This is an integer from 1 through 14; however, note that you can specify 0 to use the system output fence, instead. If you do this, the ReaderOutFence value is changed to the value of the system output fence.
Commands RDRFENCE • The value of ReaderOutFence is lowered with an OUTFENCE command for the NRJE workstation reader. • The priority of the reader spool file is raised to exceed the value of ReaderOutFence, by issuing an ALTER command or calling the NRJEAlter intrinsic. Reader spool files, once created, are disposed of when one of these actions happens: • The spool file has been transmitted to the host system. • The spool file is deleted by issuing a CANCEL command or calling NRJECancel.
Commands RDRUP RDRUP Enables the reader of an NRJE workstation. Syntax RDRU[P] [Wsid] Parameter Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. Description This command enables the reader of an NRJE workstation.
Commands RELEASE RELEASE Relinquishes access to the host remote console of a workstation. Syntax REL[EASE] Description Use this command to relinquish access to the host remote console of a workstation. You must have NM capability or be an “allowed” console user to use this command. You remain in the console of a workstation until a RELEASE command is issued, or until you exit from the NRJE CI.
Commands RELOAD RELOAD Causes NRJE to reload the Formid Lookup Table. Syntax RELO[AD][;W[SID]=Wsid] Parameter Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. Description This command causes NRJE to reload the Formid Lookup Table into its internal copy of the table.
Commands STARTWS STARTWS Starts a workstation or individual LUs, and optionally starts intrinsic and/or LU tracing. Syntax STAR[TWS][;W[SID]=Wsid] [;CH[AINSIZE]=NumRUs] [;LU=LUName[,LUName]...] [;TR[ACE]=Type[,Type][,File][,Size]] Parameters Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command.
Commands STARTWS • INTRINSIC: for intrinsics accessed by NRJE workstation users and managers. These intrinsics are NRJEAlter NRJECancel NRJEConsole NRJEHJCancel NRJEHJInfo NRJEJobInfo NOTE NRJELUList NRJELUStatus NRJEQueue NRJERdrAccess NRJERdrFence NRJEStartWS NRJEStopWS NRJESubmit NRJE2Submit NRJETrace NRJEWriter NRJEWSInfo Use this option only when recommended by your HP representative. This type of tracing can have a performance impact.
Commands STARTWS Description When the STARTWS command is issued, the NRJE monitor is streamed and runs as an MPE job (see Chapter 4 , “NA NRJE Workstation Startup and Shutdown,” of this manual). You can start a workstation or individual LUs. If you do not specify a Wsid, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. If you do not specify any LUNames, all LUs configured to be initially started are started.
Commands STATUS STATUS Displays the current status of LU sessions. Syntax STATUS[;W[SID]=Wsid][;LU=LUName[,LUName]...] Parameters Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. LUName For NRJE/V, this is the name of the SNA node LU class whose status you want displayed.
Commands STOPWS STOPWS Stops active LU-LU sessions in an orderly manner. Syntax STO[PWS][;W[SID]=Wsid][;LU=LUName[,LUName]...] Parameters Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. LUName For NRJE/V, this is the name of the SNA node LU class whose LU-LU sessions you want to stop.
Commands STOPWS An LU-LU session can also be stopped without issuing a STOPWS in these ways: • By issuing the NRJE command HALT. • By issuing the MPE command NRJECONTROL HALT. • By issuing the MPE command NRJECONTROL STOP. • By issuing the MPE command SNACONTROL STOP. • By the host job entry subsystem; SNA NRJE honors the request. This can happen at any time. Text Reference See NRJECONTROL HALT, NRJECONTROL STOP, and HALT earlier in this chapter.
Commands TRACEOFF TRACEOFF Turns off intrinsic and/or LU tracing for a workstation. Syntax TRACEOF[F][;W[SID]=Wsid][;TRACE=Type[,Type]] Parameters Wsid The workstation name. This can be up to eight alphanumeric characters long; the first letter must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. Type The type of trace to be stopped: • LU: for NRJE LU procedures.
Commands TRACEON TRACEON Turns on intrinsic and/or LU tracing for a workstation. Syntax TRACEON[;W[SID]=Wsid] [;TR[ACE]=Type[,Type][,File][,Size]] Parameters Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command. Type The type of trace to be started: • LU: for NRJE LU procedures.
Commands TRACEON If you do not specify the name of a trace output file, the default file name NMTCnnnn.PUB.SYS is used, where nnnn is a number from 0000 through 9999. The nnnn integer is incremented to form and find the next available trace file name. You can always retain trace data by using a default file name; however, considerable disk space might be used.
Commands VERIFY VERIFY Verifies the entries in the Formid Lookup Table. Syntax VERI[FY][;W[SID]=Wsid] Parameter Wsid The workstation name. This can be up to eight alphanumeric characters long; the first character must be alphabetic. If you omit this parameter, the default workstation identifier is used. You can specify a default workstation identifier in the NRJE command.
Commands VERIFY Example R18>VERIFY ............... ALL RECORDS PASSED R18> A dot is printed as each record is verified. If an error occurs, NRJE will report the nature of the error and will continue checking the remainder of the records in the table. R18>VERIFY ...... RECORD 7: UNKNOWN DEVICE CLASS. (CIERR 344) NRJE FORMID = ANNE ;FILE EQUATION ATTEMPTED: FILE TEST7 ;DEV= NOTTHERE .. RECORD 10; NONEXISTENT PERMANENT FILE (FSERR 52) NRJE FORMID = PUNOUT ;FILE EQUATION ATTEMPTED: FILE TEST10 =PUNMSG,OLD .
Commands WELCOME WELCOME Updates the NRJE subsystem welcome message. Syntax W[ELCOME] Description This command updates the NRJE subsystem welcome message. The welcome message is broadcast every time any user enters the subsystem, and when a DISPLAY INFO command is issued. It is not broadcast when a user invokes the NRJE subsystem command to change from one default workstation to another.
Commands WELCOME Example :NRJE RMT11 Enter the NRJE subsystem command interpreter using RMT11 as the default workstation. ProductNum VersionNum NRJE (C) HEWLETT-PACKARD CO. CopyrightYear NRJE displays its banner line. WELCOME MESSAGE TO BE REVISED The welcome message is displayed. RMT11> ... The NRJE subsystem command interpreter issues you a prompt. RMT11>WELCOME [RETURN] Begin WELCOME command sequence. 1>WELCOME TO NRJE. [RETURN] You are prompted with an nn> to begin each 2>RMT11 READER IS DOWN.
Commands [] ... HOST CONSOLE COMMAND [] ... HOST CONSOLE COMMAND A host job entry system console command preceded by the host command prefix character configured for the workstation. Syntax []command Parameters [] The host job entry subsystem command prefix character you have configured for the workstation. Begin every remote console command to the host with this character. command Any legitimate command recognized by the host remote console command processor.
Commands [] ... HOST CONSOLE COMMAND NRJE does not check the syntax of the command. Check the IBM documentation that applies to your host installation for the commands available and the syntax you must use. A list of IBM documents is in the preface of the SNA NRJE User/Programmer Reference Manual. Example R22>$DA Display all active jobs for a workstation. Two NRJE subsystem messages follow. OPENING CONSOLE IN PROGRESS ... (CI=780) HOST CONSOLE IS OPEN. (CI=858) 10.01.14 JOB 10.01.
Commands [] ...
A Result Codes and Messages This appendix contains messages and result codes that are unique to SNA NRJE activity. These messages are described: • Validation messages: These are messages that might occur when you validate NRJE configuration data. • NRJE error messages: These are written to $STDLIST. Note that you also can obtain an online description of each message by typing :HELP nnnn where nnnn is the error message number.
Result Codes and Messages Message Suffixes Message Suffixes Some letters and numbers appear in parentheses at the end of messages; for example, (INT=35). The numbers are either intrinsic Result codes, or message numbers printed to $STDLIST or logged through Node Management Services. Result codes are returned in the Result parameter of NRJE intrinsics. You can use the MPE intrinsic GENMESSAGE to access the message system after you have called an NRJE intrinsic.
Result Codes and Messages Validation Messages Validation Messages Listed below are the messages that might occur when you validate the NRJE configuration data. They are listed in numerical order according to message number. Configuration file validation is discussed in Chapter 3 , “SNA NRJE Configuration,” of this manual. NRJEVALERR 3 MESSAGE: Configuration file corrupt. Missing NRJE path. (NRJEVALERR 3) CAUSE: The SNA NRJE path is missing from the configuration file.
Result Codes and Messages Validation Messages NRJEVALERR 9 MESSAGE: Path: ! Logical device “!” is not a valid NRJE reader. (NRJEVALERR 9) CAUSE: The indicated ldev is invalid for the reader indicated in the path. This usually happens when the ldev is already configured for another subsystem. ACTION: Configure the correct ldev for the reader in the Logical Device field of the NRJE Configuration: Reader Data screen.
Result Codes and Messages Validation Messages NRJEVALERR 14 MESSAGE: Path: ! Logging subsystem “SUB0002” is not configured. (NRJEVALERR 14) CAUSE: The logging subsystem for SNA NRJE is not configured. ACTION: Configure the SNA NRJE logging subsystem (SUB0002) on the Logging Configuration screen. NRJEVALERR 15 MESSAGE: Path: ! Logging class “!” is not configured. (NRJEVALERR 15) CAUSE: The indicated SNA NRJE logging class is not configured.
Result Codes and Messages SNA NRJE Error Messages SNA NRJE Error Messages Listed below are the SNA NRJE messages that are written to $STDLIST. They are listed in numerical order according to the number in the message suffix; if more than one suffix is displayed, the message is listed here according to the number in the last suffix. These messages are not logged. Note that online help is available for these messages. (See the beginning of this Appendix.
Result Codes and Messages SNA NRJE Error Messages ACTION: Possible configuration error. Check NRJE configuration. 8 MESSAGE: UNABLE TO OBTAIN DEVICE CLASSES FOR THE READER. (INT=8) 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. 10 MESSAGE: INPUT NAME LENGTH IS NOT BETWEEN 1 AND 17 CHARACTERS.
Result Codes and Messages SNA NRJE Error Messages 16 MESSAGE: NODE MANAGEMENT CAPABILITY IS REQUIRED. (INT=16) CAUSE: Attempt to do something that required NM capability failed. ACTION: Must have NM capability. 17 MESSAGE: INPUT READER FENCE IS NOT BETWEEN 0 AND 14. (INT=17) CAUSE: Reader fence value is out of bounds. ACTION: Reader fence value between 0 and 14 is required. 18 MESSAGE: INVALID OPCODE FOR NRJERDRACCESS. (INT=18) CAUSE: Operand code for NRJERdrAccess intrinsic is not within valid bound.
Result Codes and Messages SNA NRJE Error Messages 27 MESSAGE: LU NOT ACTIVE. (INT=27) CAUSE: An attempt was made to obtain information about an inactive LU. ACTION: 28 MESSAGE: INCOUNT FOR NRJEACTIVEWS CALL IS NOT GREATER THAN 0. (INT=28) 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. 29 MESSAGE: SEVERE ERROR. ACTIVE LU NAME NOT CONFIGURED.
Result Codes and Messages SNA NRJE Error Messages 35 MESSAGE: NRJEERRMSG CALL COMPLETED IN ERROR STATE. (INT=35) 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.
Result Codes and Messages SNA NRJE Error Messages 51 MESSAGE: UNABLE TO READ NRJEWEL.NRJE.SYS FILE. (INT=51) 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. 52 MESSAGE: UNABLE TO WRITE NRJEWEL.NRJE.SYS FILE. (INT=52) CAUSE: File system related error. A file system error message will appear after this message.
Result Codes and Messages SNA NRJE Error Messages 63 MESSAGE: UNABLE TO OPEN NRJE READER. (SUB=63) 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. 64 MESSAGE: UNABLE TO OPEN INPUT FILE #!. (SUB=64) CAUSE: File system related error. A file system error message will appear after this message.
Result Codes and Messages SNA NRJE Error Messages ACTION: Resubmit with an input priority within the bounds of 0 and 14. 71 MESSAGE: UNABLE TO CLOSE READER. (SUB=71) 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. 72 MESSAGE: SUBMISSION CODE OF FILE #! IS NOT BETWEEN 0 AND 2.
Result Codes and Messages SNA NRJE Error Messages 78 MESSAGE: WORKSTATION READER IS DOWN. (SUB=78) CAUSE: The workstation reader is not available. ACTION: Determine whether the workstation is active. 79 MESSAGE: NM CAPABILITY REQUIRED FOR COMPRESSED FILE. (SUB=79) CAUSE: ACTION: 81 MESSAGE: ATTACHIO FAILURE IN CONSOLE PROCESS. (CI=81) CAUSE: A call from the console process to the system internal intrinsic ATTACHIO failed to execute properly. Internal error. ACTION: Contact Hewlett-Packard.
Result Codes and Messages SNA NRJE Error Messages ACTION: Use the STATUS command to verify the state of the workstation. If not active, start the workstation. 88 MESSAGE: THE WORKSTATION HAS TERMINATED. (INT=88) 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.
Result Codes and Messages SNA NRJE Error Messages 94 MESSAGE: WARNING: COMMAND NOT ALLOWED. (INT=94) 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.
Result Codes and Messages SNA NRJE Error Messages 100 MESSAGE: CONSOLE COMMAND LENGTH IS NOT BETWEEN 1 AND 80 CHARS. (CON=100) 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. 121 MESSAGE: INPUT CHAIN SIZE = !. IT MUST BE BETWEEN 0 AND !. (INT=121) CAUSE: First ! is the input chain size. Second ! is the upper limit.
Result Codes and Messages SNA NRJE Error Messages 129 MESSAGE: LU NAME IS NOT CONFIGURED FOR THE WORKSTATION. (INT=129) CAUSE: Attempt to activate or deactivate an LU that is not configured. ACTION: 130 MESSAGE: LU IS ALREADY ACTIVE. (INT=130) CAUSE: Attempt to activate an LU that is already active. ACTION: 131 MESSAGE: STOP OR HALT IS INVALID IF WORKSTATION IS NOT ACTIVE.
Result Codes and Messages SNA NRJE Error Messages MaxEntries value. The second ! parameter of the message is the upper limit. ACTION: 139 MESSAGE: INPUT LU NAMES ARE DUPLICATED. (INT=139) CAUSE: An LU name appears more than once in the list. ACTION: Delete duplicate LU names from the list. 140 MESSAGE: NRJE2SUBMIT CONFIGURATION ACCESS ERROR. (INT=140) CAUSE: ACTION: Check configuration file — error occurred reading job entry subs. 141 MESSAGE: INPUT FILE RECORD SIZE EXCEEDS MAXREC PARM (DEFAULT=80).
Result Codes and Messages SNA NRJE Error Messages 150 MESSAGE: ONE OF THE PARAMETERS IS OUT OF BOUNDS: SEG#!, P=!. (INT=150) CAUSE: At least one of the parameters passed to NRJEHJCancel is not within the user’s stack. SEG#! (code segment #) and P=! (program counter) represent the return address right after the intrinsic call. ACTION: The caller should check all of the parameters passed to the intrinsic, correct the one in error, and redo. 151 MESSAGE: USERNAME MUST BE BETWEEN 1 AND 17 CHARACTERS.
Result Codes and Messages SNA NRJE Error Messages ACTION: Correct the problem and reissue. 157 MESSAGE: INVALID USERNAME. (INT=157) CAUSE: Only @ and UserName.AcctName are valid usernames to cancel jobs by. No jobs were cancelled. ACTION: Correct and reissue. 158 MESSAGE: CONFIGURATION ACCESS ERROR. (INT=158) CAUSE: A configuration error may have taken place. No jobs were cancelled. ACTION: Check NRJE configuration file. 159 MESSAGE: ERROR OPENING JOBLOG IN NRJEHJCANCEL.
Result Codes and Messages SNA NRJE Error Messages 163 MESSAGE: ERROR UPDATING JOBLOG IN NRJEHJCANCEL. (INT=163) CAUSE: File system related error. A file system error message will appear after this message. Some jobs specified may not have been cancelled. ACTION: Determine the cause by inspecting the file system error message and correct the problem. 164 MESSAGE: UNABLE TO UNLOCK JOBLOG FILE IN NRJEHJCANCEL. (INT=164) CAUSE: File system related error.
Result Codes and Messages SNA NRJE Error Messages 174 MESSAGE: TRACE DEFAULT FILE LENGTH MUST BE GREATER THAN 0. (TRC=174) CAUSE: The DefaultFileLen parameter passed to the NRJETrace intrinsic contained a zero or negative number. DefaultFileLen is the length of the trace file name. ACTION: Change the value of DefaultFileLen to a positive number. 175 MESSAGE: NODE MANAGEMENT COULDN’T START OR STOP NRJE TRACE. (SEV=175) CAUSE: ACTION: 176 MESSAGE: NRJE MANAGEMENT COULDN’T START OR STOP NRJE TRACE.
Result Codes and Messages SNA NRJE Error Messages 181 MESSAGE: WORKSTATION IS ALREADY PERFORMING LU (INTERNAL) TRACING. (TRC=181) CAUSE: Attempt was made to start LU (internal) tracing, which the workstation is already performing. ACTION: 182 MESSAGE: TRACE FILE SIZE MUST BE BETWEEN 0 AND 32767 RECORDS. (TRC=182) CAUSE: An out-of-bounds trace file size value was in the TraceSize parameter passed to NRJETrace, or its equivalent command.
Result Codes and Messages SNA NRJE Error Messages 195 MESSAGE: PR & PU OUTPUT DESTINATIONS EXCEED MAX WIDTH. (INT=195) CAUSE: The job log can only handle a total of 214 characters of output destination information. The PR and PU destinations, together, are too long. Note: file names are fully qualified by SUBMIT before they end up in the job log, and backreferences are expanded to the original file equation. ACTION: Correct the problem. 196 MESSAGE: PR, PU, & FO OUTPUT DESTINATIONS EXCEED MAX WIDTH.
Result Codes and Messages SNA NRJE Error Messages 200 MESSAGE: INCOMPATIBLE TRANS AND/OR COMP SPECIFIED. FILE #!. (INT=200) CAUSE: The user specified that the indicated file (or one of its ##FD include files) is already translated and/or compressed, but this workstation is configured to send data untranslated and/or uncompressed. ACTION: Correct the file subcode or ##FD parameter in error. 201 MESSAGE: INCOMPATIBLE TRANSLATION SPECIFIED. FILE #!.
Result Codes and Messages SNA NRJE Error Messages 206 MESSAGE: UNABLE TO PARSE ##FD RECORD IN INPUT FILE #!. (INT=206) CAUSE: An irreconcilable parsing error of an ##FD record occurred. The ! parameter is the file number in the order of input to SUBMIT or NRJE2Submit. ACTION: Locate and inspect the ##FD record for errors, and correct the problem. 207 MESSAGE: UNABLE TO CLOSE TEMPORARY FILE DURING ERROR PROCESSING. (INT=207) CAUSE: A SUBMIT or NRJE2Submit error occurred.
Result Codes and Messages SNA NRJE Error Messages 212 MESSAGE: UNABLE TO CLOSE INPUT FILE. (SUB=212) CAUSE: A file system related error occurred in SUBMIT or NRJE2Submit. While cleaning up in preparation for exiting on account of this error, NRJE was unable to close the currently open input file. Any file system error message following this message does not refer to this error but to the original file system error. ACTION: Report the occurrence to your HP representative.
Result Codes and Messages SNA NRJE Error Messages 218 MESSAGE: SIGNOFF CARD STRIPPED FROM JOB STREAM. (INT=218) CAUSE: Host signoff commands are not allowed in an NRJE job stream. ACTION: No action is required. 219 MESSAGE: COMMAND ERROR #!. PARM #! IN ERROR. (INT=219) CAUSE: An error has occurred in programmatically executing the command: LISTEQ *N1234567. ERROR #! refers to an error returned by the MPE COMMAND intrinsic. PARM #! refers to the parameter within the command which is in error.
Result Codes and Messages SNA NRJE Error Messages 225 MESSAGE: UNABLE TO RESOLVE PUNCH DESTINATION BACKREFERENCE. (INT=225) 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. 226 MESSAGE: UNABLE TO RESOLVE FORMS DESTINATION BACKREFERENCE. (INT=226) CAUSE: Backreferenced print destination for SUBMIT or NRJE2Submit cannot be resolved with the user’s file equations.
Result Codes and Messages SNA NRJE Error Messages 231 MESSAGE: UNABLE TO TEST-OPEN PRINT DESTINATION FILE. (INT=231) 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. 232 MESSAGE: UNABLE TO TEST-OPEN PUNCH DESTINATION FILE.
Result Codes and Messages SNA NRJE Error Messages 236 MESSAGE: UNABLE TO WRITE INPUT DATA OF FILE #! TO SPOOL FILE. (INT=236) 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. 237 MESSAGE: UNABLE TO WRITE INPUT DATA OF FILE #! TO SPOOL FILE. (INT=237) CAUSE: A file system related error. A file system error message will appear after this message.
Result Codes and Messages SNA NRJE Error Messages 241 MESSAGE: NLINFO ERROR #! WHILE LOADING FROM HOST TRANSLATION TABLE. (INT=241) 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. 242 MESSAGE: UNABLE TO CLOSE CONSOLE TEMPORARY FILE. (INT=242) CAUSE: A file system related error.
Result Codes and Messages SNA NRJE Error Messages 248 MESSAGE: DATA PRECEDES JOB CARD IN INPUT FILE #!. (INT=248) 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. 249 MESSAGE: UNABLE TO OPEN OUTPUT SPOOL FILE. INPUT FILE #!.
Result Codes and Messages SNA NRJE Error Messages ACTION: Correct the punch destination. 255 MESSAGE: FORMS DESTINATION MUST BE LESS THAN 86 CHARACTERS. (INT=255) CAUSE: The forms destination for SUBMIT or NRJE2Submit must be between 1 and 86 characters if one is supplied. ACTION: Correct the forms destination. 256 MESSAGE: OUTPUT DESTINATIONS MAY NOT RESOLVE TO SYSTEM FILES. (INT=256) CAUSE: The print, punch, or forms destination resolved to $FileName. This is not supported in NRJE II.
Result Codes and Messages SNA NRJE Error Messages 263 MESSAGE: N[OTRANSLATE] ##FD OPTION INCOMPATIBLE WITH SUBMIT DIRECT. (INT=263) 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. 264 MESSAGE: MISSING “)” ON ##FD RECORD OPTION LIST IN INPUT FILE #!. (INT=264) CAUSE: The correct syntax for a ##FD record is: ##FD filename (optionlist).
Result Codes and Messages SNA NRJE Error Messages 271 MESSAGE: “,NEW” NOT VALID IN PRINT DESTINATION. (INT=271) 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. 272 MESSAGE: “,NEW” NOT VALID IN PUNCH DESTINATION. (INT=272) CAUSE: Output destination files must have been built before the job is submitted.
Result Codes and Messages SNA NRJE Error Messages 276 MESSAGE: UNABLE TO WRITE “DIRECT” TO SPOOL FILE FROM INPUT FILE #!. (INT=276) 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. 277 MESSAGE: INVALID PRINT DESTINATION. (INT=277) CAUSE: Specified print destination does not appear to be an actual file name, a backreferenced file, an ldev, a formid, or a device class.
Result Codes and Messages SNA NRJE Error Messages ACTION: Pass an InCount parameter to NRJEHJInfo that’s greater than 0. 283 MESSAGE: JOBLISTLEN FOR NRJEHJINFO IS < 0. (INT=283) 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. 284 MESSAGE: UNABLE TO OPEN JOBLOG. (INT=284) CAUSE: A file system related error.
Result Codes and Messages SNA NRJE Error Messages 290 MESSAGE: INVALID USERNAME. (INT=290) 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. 291 MESSAGE: NM CAPABILITY REQUIRED TO SHOW OTHER'S TRANSMITTED JOBS. (INT=291) CAUSE: The user’s logon account doesn’t match the specified in the SHOW command or NRJEHJInfo intrinsic.
Result Codes and Messages SNA NRJE Error Messages 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. 297 MESSAGE: UNABLE TO READ JOBLOG FILE LABEL. (INT=297) CAUSE: A file system related error.
Result Codes and Messages SNA NRJE Error Messages 310 MESSAGE: READ ERROR ON LOOKUP TABLE. (INT=310) CAUSE: ACTION: 311 MESSAGE: LOOKUP TABLE IS EMPTY. (INT=311) CAUSE: NRJE attempted to load a Lookup Table that has no entries. ACTION: Rebuild designated Lookup Table and restart workstation. 312 MESSAGE: READ ERROR ON LOOKUP TABLE. (INT=312) CAUSE: ACTION: 313 MESSAGE: DMOVOUT ERROR WHILE ATTEMPTING TO LOAD LOOKUP TABLE.
Result Codes and Messages SNA NRJE Error Messages ACTION: 321 MESSAGE: FFILEINFO ERROR WHILE ACCESSING LOOKUP TABLE. (INT=321) CAUSE: ACTION: 322 MESSAGE: FAILED TO OPEN LOOKUP TABLE. (INT=322) CAUSE: ACTION: 324 MESSAGE: GETDSEG FAILURE CODE = ! WHILE LOADING LOOKUP TABLE. (INT=324) CAUSE: ACTION: 326 MESSAGE: CLOSE FAILURE ON LOOKUP TABLE. (INT=326) CAUSE: ACTION: 328 MESSAGE: ERROR WHILE WRITING LABEL TO JOBLOG FILE.
Result Codes and Messages SNA NRJE Error Messages 339 MESSAGE: READ ERROR ON LOOKUP TABLE. (INT=339) CAUSE: ACTION: 345 MESSAGE: ERROR OBTAINING WORKSTATION STATUS. (XDS=!) (INT=345) CAUSE: ACTION: 346 MESSAGE: WORKSTATION IS NOT ACTIVE. REQUEST NOT EXECUTED. (INT=346) CAUSE: The RELOAD command was issued with the workstation inactive. ACTION: No action is required. 351 MESSAGE: CONFIGURATION FILE ACCESS ERROR. (CFG=!) (INT=351) CAUSE: ACTION: 352 MESSAGE: FAILED TO OPEN JOBLOG FILE.
Result Codes and Messages SNA NRJE Error Messages 357 MESSAGE: THE WORKSTATION IS NOT ACTIVE. (INT=357) 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. 358 MESSAGE: THE LU IS NOT ACTIVE. (INT=358) 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.
Result Codes and Messages SNA NRJE Error Messages 404 MESSAGE: ATTEMPT TO ACCESS A NON EXISTING WORKSTATION ENTRY. (MAN=404) CAUSE: There should be a message preceding this message. ACTION: Look at the preceding message and determine the error. 405 MESSAGE: ATTEMPT TO CREATE AN EXISTING AND ACTIVE LU ENTRY. (MAN=405) CAUSE: Attempt to create an LU entry that already exists. ACTION: 406 MESSAGE: NO AVAILABLE LU ENTRY LEFT FOR THE WORKSTATION.
Result Codes and Messages SNA NRJE Error Messages 415 MESSAGE: NOT ENOUGH STACK SPACE. (MAN=415) 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.
Result Codes and Messages SNA NRJE Error Messages 423 MESSAGE: A SEVERE ERROR OCCURRED IN NODE MANAGEMENT. (SEV=423) CAUSE: ACTION: 424 MESSAGE: SEVERE ERROR: WORKSTATION HAS AN UNDEFINED STATE. (SEV=424) CAUSE: ACTION: 425 MESSAGE: XDS ACCESS ERROR: NRJE XDS DOES NOT EXIST. (SEV=425) CAUSE: ACTION: 426 MESSAGE: ATTEMPT TO UNLOCK XDS LOCKED BY ANOTHER PIN. (SEV=426) CAUSE: ACTION: 427 MESSAGE: ATTEMPT TO LOCK XDS WHEN LOCKED BY SAME PIN.
Result Codes and Messages SNA NRJE Error Messages 431 MESSAGE: UNABLE TO OBTAIN PORTS FACILITY XDS FOR NRJE IPC. (INT=431) 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.
Result Codes and Messages SNA NRJE Error Messages ACTION: Locate the manager and have the file closed. 508 MESSAGE: UNABLE TO PURGE “TO MONITOR” MESSAGE FILE. (SEV=508) CAUSE: ACTION: 509 MESSAGE: UNABLE TO PURGE “FROM MONITOR” MESSAGE FILE. (SEV=509) CAUSE: ACTION: 510 MESSAGE: UNABLE TO BUILD “TO HOST” CONSOLE MESSAGE FILE. (SEV=510) CAUSE: ACTION: 511 MESSAGE: UNABLE TO BUILD “FROM HOST” CONSOLE MESSAGE FILE. (SEV=511) CAUSE: ACTION: 512 MESSAGE: UNABLE TO BUILD “TO MONITOR” MESSAGE FILE.
Result Codes and Messages SNA NRJE Error Messages 517 MESSAGE: UNABLE TO OPEN “TO MONITOR” MESSAGE FILE. (MON=517) 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. 518 MESSAGE: UNABLE TO SET TIMED READ ON “TO MONITOR” FILE. (SEV=518) CAUSE: ACTION: 519 MESSAGE: UNABLE TO FIND THE WORKSTATION, !, IN THE NRJE XDS.
Result Codes and Messages SNA NRJE Error Messages 525 MESSAGE: UNABLE TO STOP LU: !; XDS ERROR. (SEV=525) CAUSE: ACTION: 526 MESSAGE: ATTEMPT TO EXTEND WAIT ON “TO MONITOR” FILE FAILED. (SEV=526) CAUSE: ACTION: 527 MESSAGE: UNABLE TO OPEN CONFIGURATION FILE. NM CODE = ! (SEV=527) CAUSE: ACTION: 528 MESSAGE: UNABLE TO LOCK CONFIGURATION FILE. NM CODE = ! (SEV=528) CAUSE: ACTION: 529 MESSAGE: UNABLE TO HALT LU: ! ; XDS ERROR.
Result Codes and Messages SNA NRJE Error Messages 534 MESSAGE: NRJE UNABLE TO DELETE CORRUPTED JOBLOG FILE (MON=534) CAUSE: ACTION: 535 MESSAGE: NRJE ‘FPOINT’ ERROR ENCOUNTERED ON JOBLOG FILE. (MON=535) CAUSE: ACTION: 536 MESSAGE: NRJE UNABLE TO OPEN JOBLOG DUE TO FILE SYSTEM ERROR. (MON=536) CAUSE: ACTION: 537 MESSAGE: NRJE UNABLE TO CLOSE NEW JOBLOG TO PERMANENT DOMAIN (MON=537) CAUSE: ACTION: 538 MESSAGE: NRJE ENCOUNTERED FREAD ERROR WHILE ATTEMPTING TO REBUILD THE JOBLOG FILE.
Result Codes and Messages SNA NRJE Error Messages 543 MESSAGE: NRJE UNABLE TO READ WORKSTATION ID LABEL ON JOBLOG FILE. (MON=543) CAUSE: ACTION: 544 MESSAGE: NRJE UNABLE TO OPEN LOOKUP TABLE. (MON=544) CAUSE: There should be a message preceding this one. ACTION: Look at the preceding message and determine the error. 545 MESSAGE: NRJE UNABLE TO LOCK NEW JOB LOG FILE. (MON=545) CAUSE: ACTION: 546 MESSAGE: NRJE UNABLE TO ACQUIRE A LOCAL RIN.
Result Codes and Messages SNA NRJE Error Messages ACTION: 555 MESSAGE: LU: ! IS ABORTED SUCCESSFULLY. (MON=555) CAUSE: ACTION: 556 MESSAGE: LU: ! IS SUCCESSFULLY SIGNALED TO STOP. (MON=556) CAUSE: ACTION: 557 MESSAGE: WORKSTATION ! TERMINATED. (MON=557) CAUSE: ACTION: 558 MESSAGE: NO ACTIVE LU. WORKSTATION ! IS TERMINATING . . . (MON=558) CAUSE: ACTION: 559 MESSAGE: LU: ! IS SUCCESSFULLY SIGNALED TO HALT. (MON=559) CAUSE: ACTION: 600 MESSAGE: LENGTH OF DEVICE LIST IS 0.
Result Codes and Messages SNA NRJE Error Messages ACTION: Verify that the logical device number is in the MPE configuration and has been entered correctly in the RUN NRJEOUT command. 604 MESSAGE: INVALID DEVICE ID: !. (NRJEOUT=604) 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.
Result Codes and Messages SNA NRJE Error Messages 614 MESSAGE: UNABLE TO OPEN $STDLIST. (SEV=614) CAUSE: ACTION: 615 MESSAGE: SPOOL FILE CLOSE ERROR. DEV=!, SP STATUS=!. (SEV=615) CAUSE: ACTION: 616 MESSAGE: SPOOL FILE PURGE ERROR. DEV=!, SP STATUS=!. (SEV=616) CAUSE: ACTION: 617 MESSAGE: SPOOL FILE READ ERROR. DEV=!, SP STATUS=!. (SEV=617) CAUSE: ACTION: 618 MESSAGE: MAXIMUM ALLOWABLE CLASSES, 100, EXCEEDED.
Result Codes and Messages SNA NRJE Error Messages ACTION: Check the indexing range of operations that do storage. 623 MESSAGE: FAILED TO FIND PROGRAM FILE NAME. (NRJEOUT=623) CAUSE: ACTION: 624 MESSAGE: FAILED TO FIND PROGRAM FILE NAME. (NRJEOUT=624) CAUSE: ACTION: 625 MESSAGE: NRJEOUT NOT RUN FROM THE GROUP NRJE.SYS. (NRJEOUT=625) CAUSE: ACTION: 701 MESSAGE: COMMA IS EXPECTED. (CI=701) CAUSE: Parsing error. ACTION: Re-enter data. 702 MESSAGE: COMMA OR CARRIAGE RETURN IS EXPECTED.
Result Codes and Messages SNA NRJE Error Messages ACTION: Scan the data for a keyword that requires an equal sign and a parameter. Re-enter the information. 707 MESSAGE: INPUT ERROR. (CI=707) 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. 708 MESSAGE: INVALID CHAIN SIZE. (CI=708) CAUSE: The chain size parameter value is out of range.
Result Codes and Messages SNA NRJE Error Messages 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. 715 MESSAGE: NEW PRIORITY MUST BE BETWEEN 0 AND 14. (CI=715) 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. 716 MESSAGE: INVALID USER.ACCOUNT. (CI=716) CAUSE: An incorrect UserName.AcctName was entered.
Result Codes and Messages SNA NRJE Error Messages ACTION: Correct the command or parameter and re-enter the data. 723 MESSAGE: KEYWORD VALID ONLY IN SOME OF THE OPERATOR COMMANDS. (CI=723) CAUSE: A keyword has been entered and is not valid for the current command. ACTION: Refer to NRJE manual for command syntax and reenter. 724 MESSAGE: UNABLE TO PARSE THE PARAMETER LIST. (CI=724) CAUSE: A syntax error has occurred in the parameter list. ACTION: Correct the information and re-enter the data.
Result Codes and Messages SNA NRJE Error Messages ACTION: Check the parameter list, add to it, and re-enter the data. 732 MESSAGE: WARNING: EXTRA PARAMETERS ARE DETECTED AND IGNORED. (CI=732) 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. 733 MESSAGE: UNABLE TO PARSE THE COMMAND.
Result Codes and Messages SNA NRJE Error Messages ACTION: Correct the MPE command and re-enter the data. 739 MESSAGE: UNABLE TO EXECUTE MPE COMMAND. MPE ERROR # !. (CI=739) 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.
Result Codes and Messages SNA NRJE Error Messages job, consolidate the files as follows: (1) append several files together and SUBMIT again, and (2) write a routine using the NRJESubmit intrinsic. 746 MESSAGE: SEMICOLON OR CARRIAGE RETURN IS EXPECTED. (CI=746) CAUSE: A semicolon or carriage return was omitted. ACTION: Correct the information and re-enter the data. 747 MESSAGE: INFILE OPTION IS INVALID. (CI=747) CAUSE: An invalid infile option was specified.
Result Codes and Messages SNA NRJE Error Messages 756 MESSAGE: WORKSTATION ID LENGTH IS NOT BETWEEN 1 AND 8 CHARACTERS. (CI=756) CAUSE: A workstation identification length is out of range. ACTION: A workstation identification must begin with a letter and be eight or fewer alphanumeric characters long. Correct the information and re-enter the data. 757 MESSAGE: WORKSTATION ID DOES NOT EXIST. (CI=757) CAUSE: The workstation identification specified is in error, or has not been configured.
Result Codes and Messages SNA NRJE Error Messages 767 MESSAGE: CONSOLE ALREADY OPENED. (CI=767) CAUSE: ACTION: 769 MESSAGE: NULL TRACE TYPE IS NOT ALLOWED. (CI=769) CAUSE: No trace type has been specified in the TRACEON command while other keywords for the command are specified. ACTION: Re-enter. 770 MESSAGE: ILLEGAL TRACE TYPE IS DETECTED. (CI=770) CAUSE: ACTION: 771 MESSAGE: TRACE TYPE IS ALREADY SPECIFIED. (CI=771) CAUSE: ACTION: 772 MESSAGE: ILLEGAL TRACE MEDIUM: MUST BE DISC OR TAPE.
Result Codes and Messages SNA NRJE Error Messages ACTION: 783 MESSAGE: UNABLE TO RUN VERSION PROGRAM. MAKE SURE NRJEVERS.NRJE.SYS EXISTS. (CI=783) CAUSE: ACTION: 784 MESSAGE: COMMAND NOT VALID WITH NRJECONTROL. (CI=784) CAUSE: ACTION: 785 MESSAGE: KEYWORDS: SYNTAX, PARMS, OPERATION, ALL CAUSE: ACTION: 786 MESSAGE: ATTEMPTING TO REOPEN CONSOLE.
Result Codes and Messages SNA NRJE Error Messages 806 MESSAGE: NO WORKSTATION IS ACTIVE. (CI=806) CAUSE: ACTION: 807 MESSAGE: WORKSTATION IS NOT ACTIVE. DISPLAY IS USED. (CI=807) CAUSE: ACTION: 808 MESSAGE: WHEN READER FENCE IS 0, MPE SYSTEM OUTFENCE IS USED. (CI=808) CAUSE: ACTION: 818 MESSAGE: NO USER, @, SPOOLFILE, OR HOST JOB SPECIFIED. (CI=818) CAUSE: Syntax to CANCEL was invalid. ACTION: Re-enter CANCEL command with the correct parameters.
Result Codes and Messages SNA NRJE Error Messages 823 MESSAGE: KEYWORD HJ= VALID ONLY IN SHOW AND CANCEL COMMANDS. (CI=823) CAUSE: A keyword was used incorrectly. ACTION: Omit the keyword from the command and re-enter the data. 824 MESSAGE: HOST JOB NAME MUST BE BETWEEN 1 AND 8 CHARACTERS. (CI=824) CAUSE: An incorrect host job name or number was entered in a SHOW or CANCEL command. ACTION: A host job name or number is 1 to 8 characters. Correct the information and re-enter.
Result Codes and Messages SNA NRJE Error Messages 832 MESSAGE: DATE KEYWORD IS NOT VALID WITH THIS COMMAND. (CI=832) CAUSE: ACTION: 833 MESSAGE: TIME KEYWORD IS NOT VALID WITH THIS COMMAND. (CI=833) CAUSE: ACTION: 834 MESSAGE: TIME PARAMETER LENGTH IS INVALID. (CI=834) CAUSE: ACTION: 835 MESSAGE: DATE PARAMETER LENGTH IS INVALID. (CI=835) CAUSE: ACTION: 836 MESSAGE: INVALID DATE FORMAT. (NLERR=!). (CI=836) CAUSE: ACTION: 837 MESSAGE: INVALID KEYWORD. ‘ALL’ OR ‘OLD’ EXPECTED.
Result Codes and Messages SNA NRJE Error Messages 842 MESSAGE: WARNING: ‘TRANSLATED’ KEYWORD USED. ‘NOTRANSLATE’ WILL BE ASSUMED. (CI=842) CAUSE: ACTION: 850 MESSAGE: ENTIRE JOBLOG PURGED. DISC SPACE RECOVERED. (CI=850) CAUSE: ACTION: 851 MESSAGE: JOBLOG PURGED OF ! ENTRIES. DISC SPACE WAS NOT RECOVERED. (CI=851) CAUSE: ACTION: 852 MESSAGE: JOBLOG PURGED OF ! ENTIRES. DISC SPACE RECOVERED. (CI=852) CAUSE: ACTION: 853 MESSAGE: JOBLOG PURGED OF ! ENTRIES. DISC SPACE WAS NOT RECOVERED.
Result Codes and Messages SNA NRJE Error Messages 858 MESSAGE: Unauthorized SNA Server user. (CI=858) CAUSE: ACTION: 1010 MESSAGE: WORKSTATION ID NOT FOUND IN CONFIGURATION FILE. (CFG=1010) CAUSE: ACTION: 1020 MESSAGE: ARRAYS TOO SMALL TO RETURN LU CONFIGURATION. (CFG=1020) CAUSE: ACTION: 1030 MESSAGE: ARRAYS TOO SMALL TO RETURN WRITER CONFIGURATION.
Result Codes and Messages SNA NRJE Logging Messages SNA NRJE Logging Messages Listed below are the SNA NRJE messages that are logged in the log destination configured for your workstation in the Joblog Data File field of the NRJE Configuration: Workstation Data Page 2 screen. They are listed in numerical order according to the number in the message suffix; if more than one suffix is displayed, the message is listed here according to the number in the last suffix. These messages are not written to $STDLIST.
Result Codes and Messages SNA NRJE Logging Messages ACTION: 335 MESSAGE: MPE ERROR ENCOUNTERED: ‘!’ (INT=335) CAUSE: ACTION: 358 MESSAGE: THE LU IS NOT ACTIVE. (INT=358) 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. 411 MESSAGE: OFFSET MUST BE 0 OR POSITIVE. (SEV=411) CAUSE: ACTION: 412 MESSAGE: BUFFER SIZE IS TOO SMALL.
Result Codes and Messages SNA NRJE Logging Messages 424 MESSAGE: A SEVERE ERROR: WORKSTATION HAS AN UNDEFINED STATE. (SEV=424) CAUSE: ACTION: 425 MESSAGE: XDS ACCESS ERROR: NRJE XDS DOES NOT EXIST. (SEV=425) CAUSE: ACTION: 426 MESSAGE: ATTEMPT TO UNLOCK XDS BY ANOTHER PIN. (SEV=426) CAUSE: ACTION: 427 MESSAGE: ATTEMPT TO LOCK XDS WHEN LOCKED BY SAME PIN. (SEV=427) CAUSE: ACTION: 428 MESSAGE: NO ROOM FOR AN NRJE XDS DST ENTRY. (SEV=428) CAUSE: ACTION: 429 MESSAGE: NO SWAP SPACE FOR AN NRJE XDS.
Result Codes and Messages SNA NRJE Logging Messages 547 MESSAGE: NRJEMON TERMINATING — MUST BE RUN FROM NRJE.SYS. (MON=547) CAUSE: UserName.AcctName of batch job running NRJEMON must be NRJE.SYS. ACTION: 549 MESSAGE: NRJE(!): FAILED TO LOCK DUMP’LU LOCAL RIN. (MON=549) CAUSE: ACTION: 565 MESSAGE: NRJE(!): NRJE JOBLOG RECOVERY SUCCESSFUL. (MON=565) CAUSE: ACTION: 566 MESSAGE: NRJE(!): NRJE ENCOUNTERED CORRUPTED KEY FILE ON JOBLOG DUE TO A PREVIOUS SYSTEM FAILURE. REBUILD OF JOBLOG IN PROGRESS.
Result Codes and Messages SNA NRJE Logging Messages 570 MESSAGE: (!) ! (MON=570). CAUSE: ACTION: 571 MESSAGE: NRJE(!): CREATING NEW JOBLOG FILE. (MON=571 CAUSE: ACTION: 574 MESSAGE: NRJE(!): WARNING: DMOVIN FAILURE. COULD NOT EXECUTE 'RELOAD' COMMAND.
Result Codes and Messages SNA NRJE Logging Messages system I/O configuration of type 22, subtype 2, driver name=IONRDR0. Ensure that the ldev is accessed by only one workstation. 584 MESSAGE: NRJE (!): NRJE CANNOT OBTAIN OUTFENCE INFORMATION FOR THE NRJE VIRTUAL READER (SPOOLER=!) (MON=584). CAUSE: NRJEDEVINFO returned non-zero status.
Result Codes and Messages SNA NRJE Logging Messages 857 MESSAGE: UNABLE TO READ A CONSOLE MESSAGE FROM THE “FROM HOST” FILE. (SEV=857) CAUSE: ACTION: 858 MESSAGE: HOST CONSOLE IS OPEN. (CI=858) CAUSE: The CI is ready to accept console commands. ACTION: 859 MESSAGE: HOST CONSOLE IS RELEASED. (CI=859) CAUSE: The CI is no longer accepting console commands. ACTION: 1101 MESSAGE: NRJE(!;!) — WS INDEX NOT IN THE RANGE OF 1 TO 8. (LU=1101) CAUSE: NRJELU is not run as a son of NRJEMON.
Result Codes and Messages SNA NRJE Logging Messages 1107 MESSAGE: NRJE(!;!) — “FROM HOST” CONSOLE FILE OPEN FAILED. (SEV=1107) CAUSE: ACTION: 1109 MESSAGE: NRJE(!;!) — RELEASE READER CONTAINED A SEVERE ERROR. (SEV=1109) CAUSE: ACTION: 1120 MESSAGE: NRJE(!;!) — INITIALIZATION COMPLETED. (LU=1120) CAUSE: LU completes its initialization; communication to host is established. ACTION: 1121 MESSAGE: NRJE(!;!) — TERMINATED. (LU=1121) CAUSE: First ! contains a workstation name. Second ! contains an LU name.
Result Codes and Messages SNA NRJE Logging Messages ACTION: 1157 MESSAGE: NRJE(!;!) — IOWAIT RETURNS 0 FOR THE FILE NUMBER. (SEV=1157) CAUSE: ACTION: 1158 MESSAGE: NRJE(!;!) — UNABLE TO READ XPORT MESSAGE #: !. (SEV=1158) CAUSE: ACTION: 1159 MESSAGE: NRJE(!;!) — !. (COMMXPORT=1159) CAUSE: An XPORT error occurred. The third ! contains the error message. ACTION: 1201 MESSAGE: NRJE(!;!) — UNEXPECTED SDT. (SEV=1201) CAUSE: ACTION: 1202 MESSAGE: NRJE(!;!) — UNEXPECTED CLEAR.
Result Codes and Messages SNA NRJE Logging Messages 1215 MESSAGE: NRJE(!;!) — BRACKET ERROR, LU IS TERMINATING . . . (SEV=1215) CAUSE: ACTION: 1220 MESSAGE: NRJE(!;!) — SDT RECEIVED. (SC=1220) CAUSE: ACTION: 1221 MESSAGE: NRJE(!;!) — CLEAR RECEIVED. (SC=1221) CAUSE: ACTION: 1222 MESSAGE: NRJE(!;!) — RECEIVED BIND= ! (SC=1222) CAUSE: ACTION: 1224 MESSAGE: NRJE(!;!) — RECEIVED UNBIND= ! (SC=1224) CAUSE: ACTION: 1226 MESSAGE: NRJE(!;!) — LU ACTIVATION COMPLETED.
Result Codes and Messages SNA NRJE Logging Messages 1273 MESSAGE: ILLEGAL BIND — host config, use TSPROF = X‘03’ (SC=1273) CAUSE: ACTION: 1274 MESSAGE: ILLEGAL BIND — host config, PRIPROT req mode (SC=1274) CAUSE: ACTION: 1275 MESSAGE: ILLEGAL BIND — host config, SECPROT chaining (SC=1275) CAUSE: ACTION: 1276 MESSAGE: ILLEGAL BIND — host config, SECPROT req mode (SC=1276) CAUSE: ACTION: 1277 MESSAGE: ILLEGAL BIND — host config, SECPROT chain rsp (SC=1277) CAUSE: ACTION: 1278 MESSAGE: ILLEGAL BIN
Result Codes and Messages SNA NRJE Logging Messages 1282 MESSAGE: ILLEGAL BIND — host config, PSERVIC (SC=1282) CAUSE: ACTION: 1283 MESSAGE: ILLEGAL BIND — secondary RU size (SC=1283) CAUSE: ACTION: 1284 MESSAGE: ILLEGAL BIND — host config, RU infinity bit (SC=1284) CAUSE: ACTION: 1285 MESSAGE: ILLEGAL BIND — primary RU size too big (SC=1285 CAUSE: ACTION: 1286 MESSAGE: ILLEGAL BIND — compression (SC=1286) CAUSE: ACTION: 1287 MESSAGE: ILLEGAL BIND — translation (SC=1287) CAUSE: ACTION: 1288 ME
Result Codes and Messages SNA NRJE Logging Messages 3003 MESSAGE: NRJE(!;!): LINK FAILURE INDICATION RECEIVED (LU=3003) CAUSE: ACTION: 3004 MESSAGE: NRJE(!;!): TRANSPORT INTERNAL ERROR REPORTED (LU=3004) CAUSE: ACTION: 3005 MESSAGE: NRJE(!;!): HIERARCHICAL SHUTDOWN COMMAND RECEIVED (LU=3005) CAUSE: ACTION: 4001 MESSAGE: NRJE(!;!): FMD CANNOT DECOMPRESS A CONSOLE MESSAGE (SENSE=!) (SEV=4001). CAUSE: ACTION: 4002 MESSAGE: NRJE(!;!): FMD ABORTED A BAD CONSOLE MESSAGE AT THE END OF CHAIN (FMD=4002).
Result Codes and Messages SNA NRJE Logging Messages 4006 MESSAGE: NRJE(!;!): FMD CANNOT WRITE TO THE CONSOLE MESSAGE PIPE (FS=!) (SEV=4006). CAUSE: ACTION: 4007 MESSAGE: NRJE(!;!): FMD RECEIVED A CANCEL REQUEST FOR A CONSOLE MESSAGE (FMD=4007). CAUSE: ACTION: 4008 MESSAGE: NRJE(!;!): THE PLU ABORTED THE TRANSMISSION OF A CONSOLE MESSAGE (FMD=4008). CAUSE: ACTION: 4009 MESSAGE: NRJE(!;!): CONSOLE MESSAGE: ! (FMD=4009).
Result Codes and Messages SNA NRJE Logging Messages 4030 MESSAGE: NRJE(!;!): FMD CANNOT LOCK JOB FILE #O! (SPOOLER=!) (SEV=4030). CAUSE: ACTION: 4031 MESSAGE: NRJE(!;!): FMD CANNOT OPEN JOB FILE #O! (SPOOLER=!) (FMD=4031). CAUSE: ACTION: 4032 MESSAGE: NRJE(!;!): FMD CANNOT ACTIVATE JOB #O! (SPOOLER=!) (SEV=4032). CAUSE: ACTION: 4033 MESSAGE: RJE(!;!): JOB #O! CONTAINS COMPRESSED DATA, BUT READER CONFIGURATION SPECIFIES NO COMPRESSION (FMD=4033).
Result Codes and Messages SNA NRJE Logging Messages 4038 MESSAGE: NRJE(!;!): FMD CANNOT TRANSLATE JOB #O! (FMD=4038). CAUSE: ACTION: 4039 MESSAGE: NRJE(!;!): FMD CANNOT DEFER JOB #O! (SPOOLER=!) (SEV=4039). CAUSE: ACTION: 4040 MESSAGE: NRJE(!;!): FMD CANNOT CLOSE JOB FILE #O! (SPOOLER=!) (SEV=4040). CAUSE: ACTION: 4041 MESSAGE: NRJE(!;!): FMD CANNOT ACCESS THE READER AND SYSTEM FENCES (SPOOLER=!) (SEV=4041).
Result Codes and Messages SNA NRJE Logging Messages ACTION: 4047 MESSAGE: NRJE(!;!): FMD RECEIVED A NEGATIVE RESPONSE TO JOB #O! BEGIN FM HEADER (BIU=!) (FMD=4047). CAUSE: ACTION: 4048 MESSAGE: NRJE(!;!): FMD IS SENDING JOB #O! ON ! (FMD=4048). CAUSE: ACTION: 4049 MESSAGE: NRJE(!;!): FMD HAS FINISHED SENDING JOB #O! ON ! (FMD=4049). CAUSE: ACTION: 4051 MESSAGE: NRJE(!;!): FMD HAS ABORTED TRANSMISSION OF #O !; SPOOL FILE DEFERRED (SEV=4051).
Result Codes and Messages SNA NRJE Logging Messages ACTION: Stop and restart the workstation, and start the logical readers with the JES2 $S command. 4057 MESSAGE: NRJE(!;!): XDS WRITE FAILURE; CODE = ! (SEV=4057 CAUSE: ACTION: 4070 MESSAGE: NRJE(!;!): BUFFER OVERFLOW OCCURRED WHILE DECOMPRESSING OUTPUT FILE #O! (SEV=4070). CAUSE: ACTION: 4071 MESSAGE: NRJE(!;!): FMD CANNOT PROCESS OUTPUT FROM JOB ! BECAUSE DEVICE ! IS NOT SPOOLED (FMD=4071).
Result Codes and Messages SNA NRJE Logging Messages 4077 MESSAGE: NRJE(!;!): FMD RECOVERED OUTPUT FILE #O!; FILE #O! CONTAINS CORRECT DATA (FMD=4077). CAUSE: ACTION: 4078 MESSAGE: NRJE(!;!): FMD CANNOT DECOMPRESS OUTPUT FILE #O! (SENSE=!) (SEV=4078). CAUSE: ACTION: 4079 MESSAGE: NRJE(!;!): THE PLU ABORTED THE TRANSMISSION OF OUTPUT; CPU TIME= !; FILE= #O! (FMD=4079). CAUSE: ACTION: 4080 MESSAGE: NRJE(!;!): FMD CANNOT RECORD PDIR DATA IN OUTPUT FILE #O! (FS=!) (SEV=4080).
Result Codes and Messages SNA NRJE Logging Messages ACTION: 4086 MESSAGE: NRJE(!;!): FMD RECEIVED A CANCEL REQUEST FOR OUTPUT FILE #O! (FMD=4086). CAUSE: ACTION: 4087 MESSAGE: NRJE(!;!): FMD CANNOT COMPLETE PHYSICAL I/O TO OUTPUT FILE #O! AT END OF CHAIN (FS=!) (SEV=4087). CAUSE: ACTION: 4088 MESSAGE: NRJE(!;!): FMD DEFERRED BAD OUTPUT FILE #O! AT END OF CHAIN (FMD=4088). CAUSE: ACTION: 4089 MESSAGE: NRJE(!;!): FMD HAS FINISHED RECEIVING OUTPUT; CPU TIME= !; WALL TIME= !; FILE= #O! (FMD=4089).
Result Codes and Messages SNA NRJE Logging Messages 4115 MESSAGE: NRJE(!;!): FMD RECEIVED A NEGATIVE RESPONSE TO A SIGNAL REQUEST (BIU=!) (FMD=4115). CAUSE: ACTION: 4116 MESSAGE: NRJE(!;!): FMD RECEIVED A RESPONSE TO AN LUSTAT (BIU=!) (SEV=4116). CAUSE: ACTION: 4117 MESSAGE: NRJE(!;!): FMD RECEIVED ILLEGAL OPCODE ! FROM DFC (SEV=4117). CAUSE: ACTION: 4118 MESSAGE: NRJE(!;!): FMD DID NOT RECEIVE AN RU FROM DFC (SEV=4118).
Result Codes and Messages SNA NRJE Logging Messages ACTION: 5001 MESSAGE: NRJE(!;!): NS RECEIVED A MAIL MESSAGE FROM A NONEXISTENT MODULE (MESSAGE=!) (SEV=5001). CAUSE: ACTION: 5002 MESSAGE: NRJE(!;!): NS RECEIVED A MAIL MESSAGE OF THE WRONG LENGTH (MESSAGE=!) (SEV=5002). CAUSE: ACTION: 5003 MESSAGE: NRJE(!;!): NS RECEIVED AN ILLEGAL OPCODE (MESSAGE=!) (SEV=5003). CAUSE: ACTION: 5004 MESSAGE: NRJE(!;!): NS RECEIVED AN RU WHICH WAS NOT FROM THE SSCP (MESSAGE=!) (SEV=5004).
Result Codes and Messages SNA NRJE Logging Messages 5009 MESSAGE: NRJE(!;!): NS RECEIVED A MAIL MESSAGE WHICH CANNOT BE RECEIVED WHEN THE LU IS IN STATE ! (MESSAGE=!) (SEV=5009). CAUSE: ACTION: 5010 MESSAGE: NRJE(!;!): NS RECEIVED A MAIL MESSAGE WHICH CANNOT BE RECEIVED WHEN NS IS IN STATE ! (MESSAGE=!) (SEV=5010). CAUSE: ACTION: 5011 MESSAGE: NRJE(!;!): NS RECEIVED A NEGATIVE RESPONSE TO AN INITSELF REQUEST (SENSE=!) (NS=5011).
Result Codes and Messages SNA NRJE Logging Messages 5017 MESSAGE: NRJE(!;!): NS RECEIVED A NOTIFY REQUEST (BIU=!) (NS=5017). CAUSE: ACTION: 5018 MESSAGE: NRJE(!;!): NS RECEIVED AN NSPE; LU TERMINATING (BIU=!) (NS=5018). CAUSE: ACTION: 5019 MESSAGE: NRJE(!;!): NS RECEIVED AN UNSUPPORTED REQUEST (BIU=!) (NS=5019) CAUSE: ACTION: 5020 MESSAGE: NRJE(!;!): NS CANNOT UPDATE STATUS INFORMATION IN THE NRJE EXTRA DATA SEGMENT (XDS=!) (SEV=5020).
Result Codes and Messages SNA NRJE Logging Messages 6604 MESSAGE: NRJE(!;!): NMWRITETRACE ERROR; NMERR= ! (INT=6604) 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.
Result Codes and Messages SNA NRJE Logging Messages 7009 MESSAGE: NRJE(!;!): NEGATIVE RESPONSE TO CANCEL RECEIVED (SEV=7009) CAUSE: ACTION: 7010 MESSAGE: NRJE(!;!): NEGATIVE RESPONSE TO SHUTC RECEIVED (SEV=7010) CAUSE: ACTION: 7010 MESSAGE: NRJE(!;!): NEGATIVE RESPONSE TO SHUTC RECEIVED (SEV=7010) CAUSE: ACTION: 7011 MESSAGE: NRJE(!;!): ILLEGAL RESPONSE TO SHUTD RECEIVED (SEV=7011) CAUSE: ACTION: 7012 MESSAGE: NRJE(!;!): ILLEGAL RESPONSE TO DFC REQUEST RECEIVED (SEV=7012) CAUSE: ACTION: 7013 MES
Result Codes and Messages SNA NRJE Logging Messages 7018 MESSAGE: NRJE(!;!): HOST RESPONSE LACKS EC (SEV=7018) CAUSE: ACTION: 7019 MESSAGE: NRJE(!;!): HDX/FF ERROR ON OUTBOUND RESPONSE (SEV=7019) CAUSE: ACTION: 7020 MESSAGE: NRJE(!;!): HDX/FF ERROR ON OUTBOUND REQUEST (SEV=7020) CAUSE: ACTION: 7021 MESSAGE: NRJE(!;!): ILLEGAL FMD RESPONSE (SEV=7021) CAUSE: ACTION: 7022 MESSAGE: NRJE(!;!): XDS WRITE FAILURE; CODE= ! (SEV=7022) CAUSE: ACTION: 7023 MESSAGE: NRJE(!;!): INVALID SEND CODE; BIU= ! (SEV
Result Codes and Messages SNA NRJE Logging Messages 7028 MESSAGE: NRJE(!;!): NXDSUNLOCK FAILED (SEV=7028) CAUSE: ACTION: 7029 MESSAGE: NRJE(!;!): NXDSLOCK FAILED (SEV=7029) CAUSE: ACTION: 7030 MESSAGE: NRJE(!;!): NXDSREAD FAILED (SEV=7030) CAUSE: ACTION: 7031 MESSAGE: NRJE(!;!): NXDSWRITE FAILED (SEV=7031) CAUSE: ACTION: 7032 MESSAGE: NRJE(!;!): NXDSUNLOCK FAILED (SEV=7032) CAUSE: ACTION: 7033 MESSAGE: NRJE(!;!): NXDSWRITE FAILED (SEV=7033) CAUSE: ACTION: 7700 MESSAGE: NRJE(!;!): NMCONFIG FILE
Result Codes and Messages SNA NRJE Logging Messages 8001 MESSAGE: NRJE(!;!): SNACLOSEUSER FAILED; RESULT=! (LUX=8001) CAUSE: ACTION: 8002 MESSAGE: NRJE(!;!): AUTORECOVERY CONFIGURATION CHECK FAILED; RESULT=! (LUX=8002) CAUSE: ACTION: 8003 MESSAGE: NRJE(!;!): SNARCV FAILED ON RECOVERY; RESULT=! (LUX=8003) CAUSE: ACTION: 8004 MESSAGE: NRJE(!;!): NAU FAILED TO ACTIVATE ON RECOVERY; RESULT=! (LUX=8004) CAUSE: ACTION: 8005 MESSAGE: NRJE(!;!): SNAOPENUSER FAILED; RESULT=! (LUX=8005) CAUSE: ACTION: 9000
Result Codes and Messages SNA NRJE Logging Messages file to a new format by running the Node Management Services conversion utility NMMGRVER. 9002 MESSAGE: NRJE(!:!): WARNING: COULD NOT LOAD CONSOLE EXIT PROCEDURE. INTERNAL DECODE ROUTINE WILL BE USED. (LOAD ERR=!) (LU=9002) 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.
Result Codes and Messages SNA NRJE Logging Messages 9008 MESSAGE: NRJE(!:!): FAILED TO WRITE TO NRJE XDS (XDS=!) (LU=9008) CAUSE: NRJE could not zero out the length field for the Joblog record in the NRJE XDS. Internal software error. ACTION: Contact Hewlett-Packard. 9009 MESSAGE: NRJE(!:!): READ ERROR ON SUBMITTED SPOOLFILE (SPOOLER=!) (LU=9009) CAUSE: NRJE encountered an error while attempting to copy a file from the NRJE reader to the host.
Result Codes and Messages SNA NRJE Logging Messages ACTION: Contact Hewlett-Packard. 9015 MESSAGE: NRJE(!:!): FAILED TO LOAD NATIVE-3000 TRANSLATION TABLE (NLERR=!) (LU=9015) 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.
Result Codes and Messages SNA NRJE Logging Messages 9021 MESSAGE: NRJE(!:!): FAILED TO EXECUTE FFINDBYKEY INTRINSIC ON JOBLOG (LU=9021) 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. 9022 MESSAGE: NRJE(!:!): FAILED TO UPDATE JOBLOG FILE (LU=9022) CAUSE: An FUPDATE intrinsic error occurred.
Result Codes and Messages SNA NRJE Logging Messages 9028 MESSAGE: NRJE(!:!): FAILED TO WRITE TO NRJE XDS (XDS=!) (LU=9028) CAUSE: Error encountered in NXDSWRITENL while attempting to store the LU’s PIN in the XDS to reserve a reader. ACTION: Contact Hewlett-Packard. 9029 MESSAGE: NRJE(!:!): FAILED TO OPEN BANNER FILE (FSERR=!) (LU=9029) CAUSE: FOPEN failed while attempting to open the internal banner file (used to save host banners until banner decode succeeds).
Result Codes and Messages SNA NRJE Logging Messages 9033 MESSAGE: NRJE(!:!): FPOINT FAILURE ON LOOKUP TABLE (FSERR=!) (LU=9033) 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. 9034 MESSAGE: NRJE(!:!): WARNING: FAILED TO PARSE ‘ON READER’ MESSAGE: ! INVALID READER NUMBER DETECTED = !.
Result Codes and Messages SNA NRJE Logging Messages 9039 MESSAGE: NRJE(!:!): WARNING: INVALID OUTPUT ROUTING OPTION SPECIFIED FOR JOB NUMBER !. (LU=9039) 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.
Result Codes and Messages SNA NRJE Logging Messages ACTION: Check NRJE versions. Ensure that NRJEMON and NRJELU versions are compatible. Contact Hewlett-Packard. 9049 MESSAGE: NRJE(!:!): FILE SYSTEM ERROR OCCURRED ON ‘!’: ‘!.’ (LU=9049) 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. 9050 MESSAGE: NRJE(!:!): COULD NOT ROUTE OUTPUT AS REQUESTED FOR JOB NAME = !.
Result Codes and Messages SNA NRJE Logging Messages 9055 MESSAGE: NRJE(!:!): BAD JOBNUMBER RETURNED BY WRITER EXIT PROCEDURE JOBNUMBER = !, IGNORED. (LU=9055) 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. 9056 MESSAGE: NRJE(!:!): UNSOLICITED OUTPUT RECEIVED FOR HOST JOB NUMBER !. (LU=9056) CAUSE: Information message.
Result Codes and Messages SNA NRJE Logging Messages 9059 MESSAGE: NRJE(!:!): END OF FILE ENCOUNTERED WHILE RECEIVING OUTPUT FOR JOB !. REMAINDER OF DATA SET ROUTED TO DEFAULT DESTINATION, OUTPUT PRIORITY = 2. (LU=9059) 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.
Result Codes and Messages SNA NRJE Logging Messages 9064 MESSAGE: NRJE(!:!): DATASET LOST FOR HOST JOB ! OUTPUT FILE COULD NOT BE OPENED. ! RECORDS WERE RECEIVED (LU=9064) 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.
Result Codes and Messages SNA NRJE Logging Messages 9069 MESSAGE: NRJE(!:!): NRJE HAS PASSED AN ENTIRE PRINT DATASET TO A USER EXIT PROCEDURE (LU=9069) 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.
Result Codes and Messages SNA NRJE Logging Messages 9077 MESSAGE: REQUIRED PARAMETERS NOT PASSED TO RELEASEPRINTER (LU=9077) CAUSE: Internal software error. ACTION: 9078 MESSAGE: REQUIRED PARAMETERS NOT PASSED TO RELEASEPUNCH (LU=9078) CAUSE: Internal software error. ACTION: 9079 MESSAGE: NRJE(!:!): FAILED TO OPEN OUTPUT FILE ON REMOTE NODE: OUTPUT FILE NAME = ‘!’ HOST JOBNUMBER = !. OUTPUT ROUTED TO DEFAULT DESTINATION, OUTPUT PRIORITY = 2.
Result Codes and Messages SNA NRJE Logging Messages 9083 MESSAGE: NRJE(!:!): FAILED TO OPEN OUTPUT FILE WHILE PROCESSING A CANCEL REQUEST. SENSE CODE RETURNED TO HOST=!. (LU=9083) CAUSE: ACTION: 9084 MESSAGE: FPOINT INTRINSIC ERROR WHILE PROCESSING CANCEL REQUEST. (LU=9084) CAUSE: FPOINT call failed even though NRJE had random access to an output file. Internal Software error. ACTION: Contact Hewlett-Packard. 9085 MESSAGE: NRJE(!:!): FREAD INTRINSIC ERROR WHILE PROCESSING A CANCEL REQUEST.
Result Codes and Messages SNA NRJE Logging Messages 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. 9090 MESSAGE: NRJE(!:!): CANNOT ROUTE TO A NEW, DISC FILE OUTSIDE OF THE SYS ACCOUNT. JOB NUMBER= !.
Result Codes and Messages SNA NRJE Logging Messages ACTION: Contact Hewlett-Packard. 9094 MESSAGE: NRJE(!:!): FAILED TO READ FROM NRJE XDS. STATUS=! (LU=9094) CAUSE: Internal error. ACTION: Contact Hewlett-Packard. 9095 MESSAGE: NRJE(!:!); FAILED TO WRITE TO NRJE XDS. STATUS=! (LU=9095) CAUSE: Internal error. ACTION: Contact Hewlett-Packard. 9096 MESSAGE: NRJE(!:!): FAILED TO UNLOCK NRJE XDS. STATUS=! (LU=9096) CAUSE: Internal error. ACTION: Contact Hewlett-Packard.
Result Codes and Messages SNA NRJE Logging Messages 9102 MESSAGE: NRJE(!:!): WARNING: OUT OF MESSAGE FRAMES FOR REMOTE CONSOLE FACILITY; (NUM FREE=!) (NUM NEEDED=!) (LU=9102) 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.
Result Codes and Messages SNA NRJE Logging Messages 9108 MESSAGE: NRJE(!:!): CANNOT CHANGE STATE AND PRIORITY OF OUTPUT SPOOLFILE. (SPOOLER=!) (LU=9108) 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. 9109 MESSAGE: NRJE(!:!): FAILED TO CHANGE STATE OF AN OUTPUT SPOOLFILE.
Result Codes and Messages SNA NRJE Logging Messages ACTION: Check preceding log messages to determine if a workstation had just terminated. 15001 MESSAGE: ILLEGAL STRING ITEM (SEV=15001). CAUSE: ACTION: 15002 MESSAGE: ILLEGAL SPOOL FILE INDEX (SEV=15002). CAUSE: ACTION: 15003 MESSAGE: NONEXISTENT DEVICE (SPOOLER=15003). CAUSE: ACTION: 15004 MESSAGE: ILLEGAL STRING ITEMS COUNT (SEV=15004). CAUSE: ACTION: 15005 MESSAGE: ILLEGAL NEW ITEM VALUE (SEV=15005).
Result Codes and Messages SNA NRJE Logging Messages 15011 MESSAGE: ILLEGAL ITEMS COUNT (SEV=15011). CAUSE: ACTION: 15012 MESSAGE: SPLIT STACK CALLS NOT SUPPORTED (SEV=15012). CAUSE: ACTION: 15013 MESSAGE: END OF SPOOL FILE (SPOOLER=15013). CAUSE: ACTION: 15014 MESSAGE: NO SPOOL FILES IN QUEUE (SPOOLER=15014). CAUSE: ACTION: 15015 MESSAGE: DEVICE CLASS CAN’T BE CONFIGURED FOR MORE THAN ONE DEVICE (SPOOLER=15015).
Result Codes and Messages Reverse NRJE Messages Reverse NRJE Messages Listed below are the messages that are written to the host system console; they are not displayed at the workstation, written to $STDLIST, or logged. MESSAGE: REMOTE JOB nnnn STREAMED CAUSE: The output for host job nnnn was successfully streamed by NRJE. ACTION: No action required. MESSAGE: REMOTE JOB nnnn FAILED CIERR=cccc CAUSE: Output for host job nnnn could not be streamed due to the command interpreter error cccc.
Glossary A B ACF: See Advanced Communication Function. batch communications: A form of data communications in which a facility collects data over a period of time and then submits the collected information to a host computer. Typical batch communications consist of large amounts of information transmitted at infrequent intervals. ACF/NCP: See Advanced Communication Function for the Network Control Program. ACF/VTAM: See Advanced Communication Function for the Virtual Telecommunications Access Method.
through a local channel attachment or through modems and phone lines. Command Interpreter (CI): The part of MPE which analyzes and processes commands entered during a session or submitted as part of a job. communications controller: A type of front-end processor, such as an IBM 3705, 3720, or 3725, that communicates between the communications facility and a host computer. IBM supports both programmable and nonprogrammable communication controllers.
to carry out many of the functions of an IBM 8100 DPPX/RJE workstation. F FMD: See Function Management Data services. FMH: See Function Management Header. front end processor: A smaller computer that relieves a larger host computer of certain processing tasks, such as error detection, line control, and message handling. Function Management Data (FMD) services: A generic term that describes two SNA layers: Session Presentation and Session Network Services.
Job Entry Subsystem 2 (JES2): A common IBM job entry subsystem used under the MVS operating system. logical punch: Receives card punch images from a host system. logical reader: Transmits card punch images to a host system. ob Entry Subsystem 3 (JES3): An IBM job entry subsystem that is an extension of the Asymmetric Multiprocessing System (ASP) program. JES3, which supports multiprocessing, receives jobs into the system and processes all output produced by a job. L ldev: See logical device.
Logical Unit Type 3 (LU.T3): A session between an application program and a printer. IBM`3270 Data Stream Capability (3270`DSC) is provided. Many devices support both LU.T1 and LU.T3 print requests. logical writer: A logical printer or a logical punch. Multiple Virtual Storage (MVS): An IBM operating system that is an extension of OS/MVT. MVS is also known as OS/VS2 Release 2.
network: A series of points interconnected by a communications channel. These may be computers, terminals, or other peripherals. Network Services Procedure Error (NSPE): An SNA request from the SSCP to the LU indicating an error during session startup or shutdown. Network Addressable Unit (NAU): Either a program or group of programs that represents the source and destination of data in a network. The three kinds of network addressable units are SSCP, LU, and PU.
P R Physical Unit (PU): A component of an SNA node. A PU controls the resources of a node and reports errors and physical failures to the SSCP. One PU exists per node. A PU is the access method in a host node, the NCP in the communications controller node, and the hardware and software in the peripheral nodes. PU types for each kind of node are: remote: A workstation that is not local to the host system, and is configured under the host job entry subsystem.
sense data that defines the exception condition. If the response unit is positive, it may contain additional information; for example, it may contain session parameters in response to BIND SESSION. RH: See Request Header or Response Header. RJE: See Remote Job Entry. RU: See Request Unit or Response Unit. may be transmitted in duplex or half-duplex over switched or nonswitched links. The link configuration may be point-to-point, multipoint, or loop.
Path Control layers of SNA for routing and sequencing data sent through an SNA network. transmission queue: A queue of jobs to be transmitted to the host; spooled reader. V virtual reader: A logical device configured into the operating system that is used to queue files waiting for transmission to the host on a logical reader. Virtual Storage Extended (VSE): An operating system that manages data processing resources for IBM System/370 mainframes.
Index A allowed commands, 38, 85, 99, 101, 128 ALTER, 111 APPLID, 37 auto recovery configuration, 38 autostart configuration LUs, 44 B BIND, 55 bulletin file, 20 C CANCEL, 111 chain size configuration, 46 CINIT, 55 COMMAND command description, 102 command interpreter NRJE subsystem, 21 commands node manager, 85, 86 NRJE manager, 99 with manager extensions, 100 communications link problems, 79 compressed data configuration, 47 concurrent jobs, 71 configuration host, 19, 23 I/O, 19 job entry subsystem, 36, 3
Index file configuration, 40 reloading, 114 sample file, 21 verify entries, 124 FORMS, 81 H HALT, 57, 88, 94, 119, 120 command description, 105 hardware problems, 73 hardware requirements host, 19 HASP100 message JES2, 82 host configuration, 23 host banner, 81, 83 host command prefix character, 102, 128 host command prefix character configuration, 38 host console access, 102 host console command, 128 I I/O configuration, 19 IAT6101 message JES3, 82 IBM 8100 DPPX/RJE workstation, 17 inactive SNA node, 74 in
Index M Main Screen NMMGR, 32 message catalog NRJE, 21 monitor NRJE, 21 MPE resources problem resolution, 71 N Native Language Support (NLS), 46 Native Language support (NLS), 52 NLS (Native Language Support), 46 NLS (Native Language support), 52 NM capability, 102 NM configuration manager (NMMGR), 23, 27 NMCONFIG, 72, 75 NMCONFIG problems, 75 NMCONFIG.PUB.
Index output routing options configuration, 39 output routing problems, 80 P parsing algorithms used by SNA NRJE, 80 password configuration terminal, 37 PCB entries configured, 71 Physical Unit Type 2 (PU.
Index software installation problem resolution, 71 software requirements host, 19 SPOOK, 111 spool file priority, 110 SPOOLF, 111 SR (service request), 77 stack size, 71 start a workstation, 55, 91, 115 Start Data Traffic (SDT), 55 STARTWS, 55, 60, 61, 75, 91, 117 command description, 115 STATUS, 79, 82 command description, 118 status of LU sessions, 92, 118 STIOWS, 57 stop LU-LU session in an orderly manner, 119 stop LU-LU sessions immediately, 105 STOPWS, 88, 94, 105, 106, 120 command description, 119 SU
