SNA NRJE User/Programmer Reference Manual HP 3000 MPE/iX Computer Systems Edition 5 Manufacturing Part Number: 30292-90006 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. Introducing SNA NRJE Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Primitive Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Infile Designation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Default FOPEN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Other Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Special Forms Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Multiple Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Output to Disk Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Output to Tape Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 Text Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 NRJEErrMsg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents NRJERdrAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents SPOOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 MPE Spooling Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 A. Parsing Algoithms and User Exit Procedures Parsing Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . “Job Received Message” Parsing Algorithm . . . .
Contents 12
Figures Figure 2-1. Relationship Among Files in a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Figure 2-2. Order of Card Images Transmitted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Figure 2-3. Priority Card to Job Stream Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 14
Tables Table 1-1. Relationship Between Network Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Table 3-1. NRJE User Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Table 3-2. Workstation States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Table 3-3. Default FOPEN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Table 4-1.
Tables 16
Preface This manual describes Hewlett-Packard Company’s Systems Network Architecture Network Remote Job Entry (SNA NRJE) 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.
NOTE In this manual, the term SNA link product is used when the information being given is true for all of the SNA link products: SNA Link/V, SNA/SDLC Link/XL, and SNA/X.25 Link/XL. The terms SNA Link/V, SNA/SDLC Link/XL, and SNA/X.25 Link/XL are used when a distinction among the three products is necessary. An NRJE user submits jobs to a remote host system. Users can determine the status of their jobs to be submitted to a host, alter the status of their jobs, and cancel their jobs.
Organization This manual is divided into the following chapters and appendix: Chapter 1 , “Introducing SNA NRJE,” provides an overview of NRJE, its operating environment, what it can do, and hardware and software requirements. Chapter 2 , “Getting Started,” describes, in general terms, how to get NRJE to submit a job to your host and how output is handled for your job. Chapter 3 , “User Commands,” provides a description of every NRJE user command, its syntax, and its parameters.
Related HP Publications • Installing and Troubleshooting SNA NRJE, Node Manager’s Guide • SNA NRJE Node Manager’s Guide • SNA Link Services Reference Manual • SNA Link/XL Node Manager’s Guide • Getting Started With SNA Node Management • HP30020A/B Intelligent Network Processor (INP) Installation and Service Manual • MPE Commands Reference Manual • Console Operator’s Guide • MPE System Utilities • System Operation and Resource Management Reference Manual • MPE Software Pocket Guide • MPE Quick Reference Guid
Related IBM Publications • Systems Network Architecture Reference Summary • IBM Synchronous Data Link Control • Marketing Publications KWIC Index • Field Engineering Handbook, SNA • System Network Architecture - Sessions between Logical Units • IBM 3704, 3705-I, and 3705-II Communication Controllers Principles of Operation ACF/NCP/VS Publications: • Introduction to the IBM 3704 and 3705 Communications Controllers • Introduction to the IBM 3725 Communications Controller • Guide to Using the IBM 3705 Communic
JES2 Publications (version 1): • Operator’s Library: JES2 Commands • Systems Programming Library: JES2 Initialization and Tuning • Operator’s Library: OS/VS2 Remote Terminals (JES2) • Operator’s Library: JES2 Command Language Reference Summary JES2 Publications (version 2): • JES2 Operations: XA JES2 Commands • JES2 System Programming Library: XA Initialization and Tuning • JES2 Operations: XA JES2 Command Syntax • MVS/XA JES2 Licensed Program Specifications • Message Library: XA JES2 Messages JES2 Publicat
• JES3 Initialization and Tuning • JES3 Messages • JES3 Commands • MVS/SP JES3 Licensed Program Specifications • JES3 Conversion Notebook, Version 2 Release 2.1 • JES3 Conversion Notebook, Version 2 Release 1.
1 Introducing SNA NRJE This chapter introduces you to SNA NRJE and describes the following: • SNA NRJE workstation emulation • SNA NRJE product features • SNA NRJE hardware and software requirements 25
Introducing SNA NRJE Introduction Introduction Network Remote Job Entry (NRJE) is a data communications subsystem that provides HP-to-IBM batch communications in a Systems Network Architecture (SNA) environment. SNA is a comprehensive specification for distributed data processing networks, developed by IBM. SNA NRJE users at remote locations submit jobs to a host system for processing. The host sends output to SNA NRJE users at the remote location.
Introducing SNA NRJE Introduction A Workstation A batch workstation is known to the host as a combination of one or more of the following peripheral devices, or their equivalents: • Card Readers • Line Printers • Card Punches • Operator Console It is identified by RMTnnnn which represents the remote workstation number. Jobs are submitted from a remote workstation through card readers, or their equivalent, over a communication line to a host system.
Introducing SNA NRJE Introduction • Use the workstation console The user of an advanced workstation can work independently of the availability of the host system. Most actions relate to the domain of the workstation and do not enter into the host domain. An advanced workstation performs many functions without communicating with its host. SNA NRJE Emulation of a Workstation NRJE on an HP 3000 emulates an advanced batch workstation.
Introducing SNA NRJE Introduction output device that holds submitted jobs until they are transmitted to the host. Workstations receive output data sets from the host via logical writers. NRJE assembles job input into a spool file. When communications with the host exist, job input spool files are transmitted to a host system as logical card reader data streams.
Introducing SNA NRJE Introduction Multiple data sets can be created for each job submitted to a host. An output data set is always created for each job submitted to a host for Job Control Language (JCL) logging. Data sets are received at an HP 3000 using an SNA link product. Data is decompressed and translated if desired. Data sets are returned to a logical output device, a logical writer, with those from a specific job typically making up one spool file.
Introducing SNA NRJE NRJE Features NRJE Features The basic features available with SNA NRJE are as follows: • The HP 3000 can emulate the major functions of an IBM 8100 DPPX/RJE workstation. • Multiple HP 3000 users can have simultaneous batch access to the host. • An HP 3000 user can submit jobs and receive output by NRJE subsystem commands, and programmatically by NRJE intrinsics. • A maximum data communications line speed of 64Kbps is supported.
Introducing SNA NRJE NRJE Features • Data compression and character code translation are performed (or disabled if desired). • Multiple console users can be allowed, or access can be restricted to those with node manager (NM) capability. • User exits are available to enable manipulation of data.
Introducing SNA NRJE How to Use NRJE How to Use NRJE Examples of how to use NRJE are in Chapter 2 , “Getting Started.” For descriptions of subsystem commands, see Chapter 3 , “User Commands.” You can write routines to perform the same functions as NRJE commands. These are described in Chapter 5 , “User Intrinsics,” and Chapter 6 , “NRJE Manager Intrinsics.” Output from the host may be received routinely at any supported HP 3000 output device.
Introducing SNA NRJE HP 3000 Hardware and Software Requirements HP 3000 Hardware and Software Requirements Hardware Requirements The HP 3000 hardware requirements for SNA NRJE are as follows: • An HP 3000 Series 37, 39, 4x, 5x, 6x, or 7x that supports an HP 30020A/B/C Intelligent Network Processor (for NRJE/V). • A HP 3000 900 Series that supports an HP30263A Programmable Serial Interface (for NRJE/XL). • Communications line, leased or switched.
Introducing SNA NRJE Host Hardware and Software Requirements Host Hardware and Software Requirements Hardware Requirements Host hardware requirements for SNA NRJE are as follows: • An IBM System/370-compatible mainframe, such as the Model 370, 43xx, or 303x. • An IBM 37xx-compatible communications controller that supports an SNA line. An HP 3000 can also be connected to the communications controller via an IBM 3710 network controller.
Introducing SNA NRJE Host Hardware and Software Requirements CAUTION Hewlett-Packard has not verified the NRJE product with all possible combinations of host system software releases. We are continually certifying with new host system software releases. Check with your Hewlett-Packard representative for the most up-to-date list. Hewlett-Packard does not require that the customer run on one of the verified versions.
2 Getting Started This chapter describes how to perform the following tasks: • Plan jobs to send to a host system. • Use NRJE to send jobs to a host system. • Start and stop NRJE.
Getting Started Planning Jobs Planning Jobs When preparing jobs for a host, an NRJE user must consider host system characteristics, such as the type of job entry subsystem and programming languages supported, as well as the HP 3000 resources configured for SNA NRJE. Job Input Jobs sent to a host system using a physical card reader normally consist of Job Control Language (JCL) and data. These cards are concatenated to form a job stream.
Getting Started Planning Jobs FD Files FD files are similar to Infiles in that they may contain the same kind of information, they are constructed in the same way, and they can be transmitted without translation. They are referenced directly by means of ##FD cards in the Infile. (SeeFigure 2-1). FD files may reference other FD files. This nesting can be continued up to 20 levels deep. Figure 2-1 illustrates the relationships among several card image files that have been merged into a single job stream.
Getting Started Planning Jobs Figure 2-1 shows the relationship among infiles and FD files in a job stream. Figure 2-2 shows the order in which the card images from the files in Figure 2-1 are transmitted to the host. Figure 2-2 Order of Card Images Transmitted Host System Job Control SNA NRJE checks for valid JOB cards, SIGNOFF cards, and host console commands before transmission. If NRJE detects a SIGNOFF card, it prints a warning message. The card is not transmitted to the host.
Getting Started Planning Jobs on JOB1. The second priority card is transmitted to the host as part of JOB1 and therefore does not influence JOB2. When priorities are important, each job should be submitted to SNA NRJE separately. Figure 2-3 Priority Card to Job Stream Relationship Input File Libraries The job streaming feature of SNA NRJE allows you to construct jobs from job control cards, programs, and data that already exist in disk files.
Getting Started Sending Jobs to a Host Sending Jobs to a Host To operate NRJE you must do the following: • Log on to the HP 3000. • Optionally define any formal designators you will use. • Invoke NRJE. • Issue a SUBMIT command. Defining Formal Designators Define formal file designators with a FILE command. You can do this before you invoke NRJE, or within NRJE. When a formal designator is used, it must be preceded by an asterisk (*). The asterisk indicates a reference to a previous FILE command.
Getting Started Sending Jobs to a Host Sample NRJE Session on an HP 3000 See Chapter 3 , “User Commands,” for a description of each of the commands in the following sample session. In this sample, user input is shown in the first column, and instructions and explanations are in the second. Log onto the HP 3000 :HELLO USER.ACCT,GROUP WELCOME TO THE HP 3000 Invoke the NRJE subsystem by entering the NRJE command and specifying RMT11 as the default workstation identifier.
Getting Started Sending Jobs to a Host You may want to find out about the jobs you have submitted, cancel your jobs, or change their transmission priority. The commands available for these tasks are described in Chapter 3 , “User Commands,” and summarizes all of the routine commands. (Manager commands required for day-to-day workstation operations are described in the SNA NRJE Node Manager’s Guide.
Getting Started NRJE Startup NRJE Startup Later in this chapter, an example illustrates how to start and stop NRJE. To start NRJE, you must do the following: • Activate the data communications line and host PU and LUs. • Start the SNA node using an MPE SNACONTROL START command. • Start the NRJE workstation using an MPE NRJECONTROL START command or an NRJE STARTWS command. NOTE A job stream file must exist before you start a workstation. An MPE job stream file is required to start each workstation.
Getting Started NRJE Shutdown NRJE Shutdown Two ways to shut down NRJE using MPE commands exist: • Stop NRJE using an NRJECONTROL STOP or NRJECONTROL HALT command from MPE. • Issue an SNACONTROL STOP command from MPE. This shuts down the SNA link and NRJE. A STOPWS issued from within NRJE has the same effect as an NRJECONTROL STOP. A HALT issued from within NRJE has the same effect as an NRJECONTROL HALT.
Getting Started NRJE Shutdown Use of NRJEJCW The following example can be used to restart NRJE after the host system disconnects: !JOB NRJE,MANAGER>>SYS/password,NRJE;OUTCLASS=,1 !RUN NRJEMON;INFO="wsid" !IF NRJEJCW = 1224 OR NRJEJCW = 3005 THEN ! CONTINUE << Received unbind or hierarchical shutdown >> ! SNACONTROL START;NODE=nodename ! NRJECONTROL START;WSID=wsid !ENDIF !EOJ The example below includes SNACONTROL commands, which are the responsibility of the SNA node manager and are described in the SNA L
Getting Started NRJE Shutdown Default punch form name: STD WELCOME MESSAGE: WELCOME TO NRJE Issue STARTWS command. A job number is returned identifying the file that has been streamed. R20>startws #J745 Immediately issue another DISPLAY INFO command.
Getting Started NRJE Shutdown LU03 LU04 LU05 LU06 LU07 LU08 * * 99 99 99 99 99 99 * 3 4 0 0 0 0 YES YES NO NO NO NO = The LU is active. Now jobs that have been submitted are transmitted. Data sets can be received. Console commands can be sent. Console messages can be received. Identify the status of all sessions, PU-SSCP, LU-SSCP, LU-LU. R20>:snacontrol status;node=ibmnode SNACONTROL commands can be entered from your configured NRJE prompt by preceding them with colon ( : ).
Getting Started NRJE Shutdown Stop the SNA node, and so all workstations, in a quiescent manner. R20>:snacontrol stop;node=ibmnode;type=q Issue an SNACONTROL STATUS command after the node is closed. R20>:snacontrol status;node=ibmnode NODE SPECIFIED IS NOT ACTIVE. (SNAERR 11) Issue another DISPLAY INFO command. R20>display;info Workstation: R20 GENERAL INFORMATION State: INACTIVE Workstation is INACTIVE.
3 User Commands SNA NRJE is used to transmit and receive batch jobs between a workstation and an IBM or IBM plug-compatible host system, and to control the workstation. This chapter describes how to use NRJE to submit jobs and receive data between a host system and an HP 3000 serving as a workstation. It also describes how NRJE is used to perform the following tasks: • Display information about your jobs. • Display information about the workstation. • Alter the status of your jobs. • Cancel your jobs.
User Commands Introduction Introduction Some user commands have NRJE manager extensions. You must be configured with NM capability to use them. Job Output Output from a job is automatically received from a host whenever communication is established between a workstation and a host. You do not need to issue an NRJE subsystem command or related intrinsic to receive your job output. Job output can be directed to any output device that is supported by your HP 3000.
User Commands Introduction Workstation Identification Whenever you enter NRJE, you can identify a workstation to serve as the default identifier for all subsequent subsystem commands. The following is an example: :NRJE RMT11 This MPE command invokes NRJE for workstation RMT11. product number version number NJRE (C) HEWLETT-PACKARD CO. copyright year NRJE WELCOME MESSAGE The NRJE welcome message is configured by the SNA node manager or provided by an NRJE manager.
User Commands Introduction Access Methods You can access NRJE two ways: interactively and programmatically. Interactive access is through the NRJE subsystem command interpreter. Use NRJE this way from your terminal or from a streamed job. Interactive commands have a simple format and provide the most common parameter values as defaults. As a convenience, abbreviations and a flexible range of parameter values are supported. Programmatic access allows your program to call NRJE intrinsics.
User Commands Command Structure Command Structure The structure of most NRJE commands is as follows: Syntax COMMAND [parameters][;W[SID]=Wsid] Parameters parameters Each command may have its own parameters. Wsid Some commands also have an optional parameter to override the default workstation identifier. Description Each NRJE subsystem command starts with a command name, which may be abbreviated and which may be followed by parameters.
User Commands User Commands User Commands This subsection describes each NRJE subsystem command available to a user. Some user command parameters are available only to NRJE managers. Those are described in this section, also. NRJE manager commands are described in the SNA NRJE Node Manager’s Guide. Users who do not have NM capability can access the remote console facility, provided one or more commands have been “allowed” by their node manager.
User Commands User Commands Table 3-1 NRJE User Commands Command Description SHOW * Provides information about jobs you have submitted. If you are connected to a VSE/POWER host system, only those jobs awaiting transmission are shown. SUBMIT * Prepares a batch input job stream for transmission to a host system. VERSION Identifies the software version of SNA NRJE. [] A host job entry system console command preceded by the host command prefix character configured for the workstation.
User Commands ALTER ALTER Changes the transmission queue priority of a submitted job or group of jobs. Syntax A[LTER] { SpoolfileID { Name {UserName.AcctName { @ } },Newpri [;W[SID]=Wsid] } } Parameters SpoolfileID Use to alter the priority of a specific job to Newpri. The SpoolfileID parameter is assigned by the spooler after execution of a SUBMIT command. Its form is #0nnnnn, where n is a digit. You enter just the nnnnn portion of the ID.
User Commands ALTER Newpri Specifies the new priority value you want for jobs. The value of Newpri must be an integer from 0 through 14, where 14 is the highest priority. You can defer submitting your job by setting Newpri less than or equal to the value of RDRFENCE, which is described in the SNA NRJE Node Manager’s Guide. The initial priority of a job is established when you submit it via a parameter of the SUBMIT command. Wsid Overrides the default Wsid named in the NRJE command, for this command only.
User Commands ALTER Example RMT53>... You have entered NRJE for RMT53. RMT53>DISPLAY;QUEUE Use this command to obtain the value of Reader fence. Workstation: R53 READER QUEUE Reader ldev: Chain size: Number of readers: Compression: Translation code: Reader status: Reader fence: System fence: 12 99 1 YES 0: Native-3000 UP 6 6 RMT53>SHOW @ It is useful to see the priorities of your jobs. If you are logged on as KEN.NRJE, you would see this display. #O Name Pri State Rank Size User.
User Commands CANCEL CANCEL Purges jobs awaiting transmission. Deletes returning output data sets for jobs already transmitted to the host. If you are connected to a VSE/POWER host system, only jobs awaiting transmission are cancelled. Syntax CA[NCEL] { SpoolfileID { Name { UserName.AcctName { @ { ;HJ=HostJob [,HostJob [,...]] } } } [;W[SID]=Wsid] } } Parameters SpoolfileID Cancels one of your jobs. The SpoolfileID is assigned by the spooler after a job is submitted.
User Commands CANCEL If your logon UserName.AcctName is different from the jobs you want to cancel, you must be a user configured with NM capability to use this parameter. @ Cancels all jobs from the current logon UserName.AcctName. Jobs awaiting transmission to the host under the current UserName.AcctName are purged. Data sets returning from the host for jobs submitted under this UserName.AcctName prior to this command are purged as they return.
User Commands CANCEL Wsid parameter when you start an NRJE workstation with an NRJE command. You must confirm each interactively issued CANCEL command (see example). Restrictions • Jobs you want to cancel before they are transmitted must be in the READY state. You can enter a SHOW command to determine the state of a job. • If you are configured with NM capability, you can cancel any job. However, if you do not have NM capability, you can cancel only those jobs submitted under your logon UserName.AcctName.
User 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.
User 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.
User 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 Chapter 6 , “NRJE Manager Intrinsics.
User Commands DISPLAY DISPLAY Provides display of workstation and workstation-related information. Syntax D[ISPLAY] [I[NFO]] [;Q[UEUE]] [;WR[ITER]] [;AC[TIVEWS]] [;LUT[ABLE]] [;W[SID]=Wsid] Parameters INFO Provides this information: • Whether your workstation is active or inactive. • Which Job Entry System the host uses. • The name of the remote workstation. • The host command prefix character. • The host console commands allowed for users without NM capability.
User Commands DISPLAY • The value of the reader outfence. You might need to know this when you use the PRIORITY parameter of the SUBMIT command. • The system OutFence value. WRITER Displays information about each logical writer configured for this workstation: • Name of the writer. • Logical device number (ldev), logical device class names, or “formid” entry in the Lookup Table.
User Commands DISPLAY When you enter DISPLAY INFO, or DISPLAY without any parameters, the State of a workstation is one of those described in Table 3-2. The information that DISPLAY provides is presented one screen at a time if the command is issued from an interactive session. Table 3-2 Workstation States State: Meaning: ACTIVE The workstation is connected to the host job entry subsystem. STOPPEND * One of these has been issued and is pending: • An NRJE subsystem STOPWS command.
User Commands DISPLAY Example R19>DISPLAY Workstation: R19 GENERAL INFORMATION State: Jes: Remote: Host command prefix char: Allowed console commands: Formid lookup table: Default print form name: Default punch form name: Pending JES2 RMT19 $ $D NRJETABL.
User Commands DISPLAY Text Reference The intrinsics related to this command are described in Chapter 5 , “User Intrinsics.” These are as follows: • NRJEQueue: obtains information about the workstation transmission queue. • NRJEWSInfo: obtains general information about the workstation. • NRJEWriter: obtains information about configured host logical writers for a given workstation. • NRJEActiveWS: finds out how many and which NRJE workstations are active. • NRJEWelcome: receives the NRJE welcome message.
User Commands EXIT EXIT Causes the user to exit from the NRJE command interpreter (CI) and returns control to the process from which the CI was run. Syntax E[XIT] Description The EXIT command exits you from the NRJE command interpreter (CI) and returns control to the process that called the CI. If you have specified a default workstation (or no workstation) and then changed it by using an NRJE command, use the NRJE command to return to the previous workstation.
User Commands ##FD ##FD Used within a job to include the contents of a file. Syntax ##FD Infile [(Options)] [Comment] Parameters Infile Specifies the file whose contents are to be included. This is any valid MPE file name. For both $STDIN and $STDINX you must close with :EOD. (Options) Any combination of these: N[OTRANSLATE] T[RANSPARENT] • NOTRANSLATE causes the FD file to be transmitted to the host without translation.
User Commands ##FD If a job card is included in the Infile, then its format must adhere to the same syntax as that specified for the SUBMIT command. Refer to the “Description” section of the SUBMIT command discussed later in this chapter. If a file is built that requests input from $STDIN or $STDINX, the optional comment field on the ##FD card should be used to identify the type of input that is expected.
User Commands HELP HELP Provides you with information about subsystem commands. Syntax H[ELP] [NRJECommand [,Keyword]] [MSGnumber] Parameters NRJECommand A full or abbreviated version of any NRJE command. If you omit this parameter you receive a list of all NRJE commands. NRJE displays the command name, the command syntax, and a list of keywords for the command. MSG Number An integer representing any valid NRJE message. Information on most frequently referenced error messages is available.
User Commands HELP Description The HELP command enables you to obtain online information about NRJE commands and error messages. If you enter HELP without any parameters, NRJE displays a list of commands. If you specify any NRJE command in the NRJECommand parameter and omit the Keyword parameter, you receive a one-line description of that particular command and its syntax. Output is displayed one screen at a time, and you are prompted for a carriage return before each new screen.
User Commands NRJE NRJE Invokes the subsystem command interpreter. It is also an NRJE subsystem command and allows you to switch to a different default workstation. Syntax N[RJE] Wsid Parameter Wsid Identifies a specific workstation you wish to use as a default. The Wsid parameter is an alphanumeric string that must begin with a letter and can be up to eight characters long. You must use Wsid in an NRJE subsystem command; it is optional in an MPE command.
User Commands NRJE If you enter an NRJE command from MPE, the Wsid parameter is optional; however, it is required if you issue the command within the NRJE subsystem. In either case, when you specify a Wsid in an NRJE command, you designate a default workstation for your NRJE session. A workstation specified in an NRJE command remains the default workstation for your NRJE session until you enter another NRJE command with its own Wsid.
User Commands NRJE Example : ... You are logged on to MPE. :NRJE RMT11 Enter NRJE with RMT11 as the default workstation. product number version number NJRE (C) HEWLETT-PACKARD CO. copyright year NRJE WELCOME The NRJE WELCOME text is configured by an NRJE manager. RMT11> ... Execute NRJE commands with RMT11 as the default workstation. The prompting string is configured in the NMMGR Workstation Data screen. RMT11>NRJE RMT99 Switch to RMT99 as the default workstation. RMT99> ...
User Commands REDO REDO Allows you to modify and/or execute the previous NRJE subsystem command. Use this like the MPE REDO command. Syntax RED[O] Subcommands D Deletes the character above the D. If the D is repeated, each character above each D is deleted. I Inserts one or more characters ahead of the character above the I. The D and I subcommands can be used together to replace strings of unequal length. R Replaces the characters above the R with the characters that immediately follow it.
User Commands REDO Example >SHEW MINE An incorrect command was entered. NO SUCH COMMAND. (CI=721) >REDO SHEW MINE RO The incorrect command is displayed. Enter the R subcommand below the character “E” you are replacing, followed by the correct character “O”. You could have omitted the R subcommand. SHOW MINE [RETURN] The correct command is displayed. Enter another carriage return to execute this command.
User Commands REMARK REMARK Provides a way to do in-line comments when you use NRJE subsystem commands in an HP 3000 job. Syntax REM[ARK] [String] Parameters Contains any printing character. If you omit the String in an HP 3000 job, only the REMARK command itself is printed. String Description The REMARK command enables you to include comments or notes within a sequence of subsystem commands in job listings produced on hard copy devices, to create headings or explain the purpose of commands.
User 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 NJRE CI.
User Commands RUN RUN Executes a prepared program. Syntax RU[N] ProgramFile [;PARM=n] Parameter ProgramFile Identifies a program file. A ProgramFile is an actual designator of a program file containing a prepared program. PARM Contains the run time parameter. Set to zero if not specified. Description The RUN command enables you to execute a prepared ProgramFile from within the subsystem. This command is different from an MPE RUN command.
User Commands SHOW SHOW Provides information about jobs you have submitted. If you are connected to a VSE/POWER host system, only those jobs awaiting transmission are shown. Syntax SH[OW] { SpoolfileID { Name { UserName.AcctName { @ {;HJ=HostJob [,HostJob[,...]] {;HJ=FirstJob/LastJob {;HJ=#O SpoolfileID } } }[;W[SID]=Wsid] } } } } Parameters SpoolfileID Use when you want to show information about a specific job. The SpoolfileID parameter is assigned by the spooler after you submit a job.
User Commands SHOW @ Use to show information about all jobs you submitted, when your logon UserName.AcctName is the same as the job UserName.AcctName. If you have NM capability, all jobs submitted by other users are shown, also. HostJob Either the jobname from the job card or the job number assigned by the host. Jobs can be shown by HostJob only after they have been entered in the Job Log (that is, transmitted to the host).
User Commands SHOW Untransmitted Files The list you receive identifies each specified job by SpoolfileID, Name, and UserName.AcctName. The priority, state, rank size, and time when each specified job was submitted are also displayed. Each column of output provided by the SHOW command for untransmitted files is described below. Column Heading Contents #O A SpoolfileID Name The name of the file associated with your job. Pri The spool file transmission queue priority number.
User Commands SHOW Restriction You must be configured with NM capability to use this command for jobs outside of your logon UserName.AcctName. Example RMT32>REMARK THIS SHOW @ IS BY A USER WITH NM CAPABILITY Provide information about all jobs. RMT32>SHOW @ #O Name 1069 1075 Pri 13 12 State READY READY Rank 1 2 Size 32 20 User.Account KEN.NRJE ANNE.NRJE Time 10:48 10:55 2 JOB(S) AWAITING TRANSMISSION TO HOST. --JOB#=1030 JOBNAME=DS1 USER=ANNE.
User Commands SHOW Text Reference The following intrinsics are related to this command: • NRJEJobInfo: returns information about jobs awaiting transmission. • NRJEHJInfo: returns information about transmitted jobs from the Job Log. These intrinsics are described in Chapter 5 , “User Intrinsics.
User Commands SUBMIT SUBMIT Prepares a batch input job stream for transmission to a host system. Syntax (N) S[UBMIT] Infile [ (NOTRANSLATE) ], ... [ [ [ [ [ [ [ [ ;D[IRECT] ] ;PRIO[RITY] = n ] ;J[OBNAME] = Name ] ;W[SID] = Wsid ] ;PR[INT] = PrintFile ] ;PU[NCH] = PunchFile ] ;F[ORMS] = FormFile ] ;M[AXREC] = MaxRecSize ] Parameters Infile Identifies a file to be submitted.
User Commands SUBMIT DIRECT When you use this parameter, translation and compression will be done during transmission to the host. You cannot use (NOTRANSLATE) and DIRECT together. n Identifies a spool file transmission queue priority number. The highest priority is 14, and the lowest is 1. Job transmission to the host can be deferred by specifying a priority value less than or equal to the reader fence value, RDRFENCE, for a workstation.
User Commands SUBMIT PunchFile Used to specify routing for output data sets that are sent to an NRJE logical punch on the standard form. FormFile Refers to print or punch output routed to any form other than the standard form. PR=, PU=, and FO= specifications require the use of the Job Log. Use of these parameters is not supported for workstations connected to a VSE/POWER host.
User Commands SUBMIT wrapped by NRJE. If a received record exceeds the width of the destination file, output is segmented and any extra characters are written to the line immediately following the truncated record. MaxRecSize Identifies the maximum record size (in bytes) that will be encountered in the Infiles or ##FD files. The minimum usable value is 80. The maximum usable values are as follows: • 248 for JES2 or JES3 workstations that use a 256-byte RU.
User Commands SUBMIT SNA NRJE provides the capability of submitting files that are stored at remote locations. The :Envid parameter is used to identify the remote location from which the file is to be submitted. This capability is possible if you have either DS/3000 services in a point-to-point connection to the remote, or NS/3000 services if you are connected in a Local Area Network (LAN) with the remote.
User Commands SUBMIT • A TRN SNA Character String (SCS) control word in bytes 1 and 2. • An IRS SCS, which is used to delimit records, as the last byte. If these restrictions are not met, NRJE features such as job management and output management and support of ##FD files may not function correctly for these jobs. Default FOPEN Parameters Table 3-3 lists the default FOPEN parameters that NRJE uses when opening the output file for PRINT output. (Differences for PUNCH and FORMS output are noted.
User Commands SUBMIT is routed to a device class or ldev, the name of the form is passed in the forms field of the FOPEN intrinsic. This causes a hard copy forms mount request for the form specified to be sent to the HP 3000 console when the spoolfile goes active. If the FCB field is specified in your JCL, and FORMS output is routed without the Lookup Table, and you do not specify any alternate PR=, PU=, or FO= destinations, the FCB field is passed to FOPEN as an environment file name in the group HPENV.
User Commands SUBMIT Embedded console commands must be preceded by a host console command prefix so that they are recognized as commands. The host console command prefix you use depends on the host system to which you are connected: • JES2: commands must be preceded by /*[], where [] is the host command prefix configured for your workstation in the NMMGR Workstation Data screen.
User Commands SUBMIT CAUTION Do not direct multiple output data sets of different types (that is, PRINT, PUNCH, or FORMS) to the same disk file; for example, SUBMIT myjob;PR=myfile;FO=myfile This causes data to be overwritten in the file myfile. Example :FILE OUTLIST;DEV=PP;ENV=LP2.HPENV.SYS :NRJE R20 product number version number NRJE (C) HEWLETT-PACKARD CO. copyright year WELCOME TO NRJE R20>SUBMIT myjob;pr=*outlist;fo='long';prio=9 JOB SUCCESSFULLY SUBMITTED. THE SPOOL FILE IS: #O86 R20>...
User Commands SUBMIT The (NOTRANSLATE) parameter after the BINDATA file name indicates that this file has already been translated into the character code configured for the host system. In the second example, the file NEWJOB is already in EBCDIC and does not need to be translated by NRJE. Note that NEWJOB must still contain a valid job card. Multiple files can be included by submitting a single file that contains ##FD statements referencing the JCL and/or data files.
User Commands VERSION VERSION Identifies the software version of SNA NRJE. Syntax V[ERSION] Description The VERSION command enables you to identify the versions of SNA NRJE program files, segments, the message file, and the overall version of the subsystem. Output from this command is sent to $STDLIST. Example R20>version *************** PROGRAM PROGRAM PROGRAM PROGRAM PROGRAM SL SEGMENT SL SEGMENT SL SEGMENT SL SEGMENT SL SEGMENT MESSAGE FILE NRJE VERSION CHECK NRJE.NRJE.SYS NRJECONS.NRJE.
User 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.
User Commands [] ... HOST CONSOLE COMMAND NRJE does not check the syntax of the host console 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 this 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.
4 Job Output This chapter details the procedures you follow to use SNA NRJE to receive output from jobs you have submitted to your host system. The topics discussed are as follows: • Job output handling, including a number of general considerations that apply to all output received from the host. • Job management, by which final destination of output can be controlled when a job is submitted for transmission to the host.
Job Output Job output can be directed to any output device that is supported on your HP 3000. These include laser printers, line printers, and disk and tape files. These devices can be spooled or non-spooled. Job management is the ability to specify the final destination of the output at the time the job is submitted to NRJE to be transmitted. These procedures are described under “Job Management with the SUBMIT Command” later in this chapter.
Job Output Job Output Handling Job Output Handling SNA NRJE’s control hierarchy for resolving any potentially conflicting output routing specifications is as follows: 1. Use the SUBMIT command specifications PR, PU, or FO, if supplied. 2. If no SUBMIT command routing specifications are supplied, use the Lookup Table. 3. If no specifications are in the SUBMIT command and the Lookup Table is not in use, route the data sets to the default destination specified in the NMMGR Writer Data Screen. 4.
Job Output Job Output Handling Table 4-1 JES2 Example for Default Output Destination Writer Data Screen Specifications Selected Form in JCL ‘FORMID’ DEVICE CLASS “A” LDEV “N” FORCED=Y FORCED=N FORCED=N FORCED=N STANDARD FORM ‘STD’ ‘FORMID’ ‘FORMID’ “A” “N” FORM “X” ‘FORMID’ “X” “X” “X” General Considerations Regardless of the method you use to control the output returning from the host, a number of general considerations must be taken into account: • Matching data set output class to de
Job Output Job Output Handling • The use of host job entry subsystem console commands, if you are an NRJE manager. Host Configuration The configuration of logical writers and output classes is described in the SNA Link Services Reference Manual or the SNA NRJE Node Manager’s Guide. Also, see the Preface of this manual for a list of IBM publications. JCL Class Specification You associate data sets with output classes by using JCL in your jobs.
Job Output Job Output Handling modified by console command to be associated with class=D. VSE/POWER JECL Class Specification If you are connected to a VSE host system (using VSE/POWER), associate the output data sets with a specific output class in the following way: • The CLASS=class parameter of either the * $$ LST statement or the * $$ PUN statement; for example, * $$ LST,CLASS=x where x is a class letter.
Job Output Job Output Handling VSE/POWER Commands If your NRJE workstation is connected to a VSE/POWER host system, you can modify the class of the output to match the class of a logical output device configured on your host as your remote.
Job Output Job Output Handling Table 4-2 describes the relationship between the control codes and the operation performed on printer devices by each code. NOTE HP line printers interpret channel skipping control codes (%300–%313) differently from one another. You can redefine channel skipping control codes using environment files containing VFCs. See the SNA Link Services Reference Manual, the SNA NRJE Node Manager’s Guide, and the HP 2608S Line Printer Reference.
Job Output Job Output Handling Table 4-2 SNA and HP 3000 Printer Carriage Control Codes SNA Character String HP 3000 Control Code and Function Inter-record separator (IRS) %201 ! 1E Space one line. Transparent Data (TR) No code; indicates transparent data follows. ! 35 All SNA character strings are hexadecimal numbers depicted by !abcd. All HP 3000 control codes are octal numbers depicted by %abc.
Job Output Job Output Handling • In a file equation that you backreference directly as a SUBMIT command output destination. • In a Lookup Table file equation that you reference in a SUBMIT command by its form name. If you do not specify an environment file by one of these methods, the default environment file configured for the HP 268xx is used. The recommended procedure is to use the Lookup Table and map form names to environment files that can be used when output is routed to the laser printer.
Job Output Job Output Handling Table 4-3 Peripheral Device Information Record Structure Byte Contents and Meaning 0 The length of this record, including this byte 1 Function Management Header (FMH) concatenation. An FMH is SNA-specific information which may be present to perform the following functions: • Select a destination and control the way data is handled there. • Change the characteristics of data or its destination.
Job Output Job Output Handling Table 4-3 Byte Peripheral Device Information Record Structure Contents and Meaning The default FCB value is all blank characters. 36–43 Printer train name to be mounted, in ASCII, left-justified, with trailing blank characters. JES2 uses 0 as a default train. 44–51 Number of additional copies of the data set to be reproduced, in ASCII characters, right-justified, with leading blank characters. The default value is 0.
Job Output Job Output Handling Unless you have specified PR=‘formid’ or PU=‘formid’ options in your SUBMIT command (not available if NRJE is connected to a VSE/POWER host system), output routed to the standard form is not controlled by the Lookup Table even if it is in use.
Job Output Job Output Handling Specifying Multiple Copies You can direct NRJE to print multiple copies of a data set when output is routed to an NRJE print device. You select multiple copies by using the COPIES parameter in your JCL. For example, for MVS JCL, //ddname DD SYSOUT=C,COPIES=27 To select multiple copies of a single data set, you should specify a unique class for each data set.
Job Output Job and Output Management Job and Output Management Job management is the ability to specify the final destination of the output at the time the job is submitted to NRJE to be transmitted to the host. NRJE accomplishes this through parameters included in the SUBMIT command which can directly or indirectly identify a final destination. Output management is the ability to route output by specifying special forms for output data sets using file equation records in a lookup table.
Job Output Job and Output Management necessary, NRJE also checks the Lookup Table configured for NRJE for routing information. The special form names used to access the information from the Lookup Table are specified in the job stream or as part of the SUBMIT command. The special form name is sent back to NRJE in a PDIR generated by the host. Job Management with the SUBMIT Command Details for use of the SUBMIT command are in Chapter 3 , “User Commands.
Job Output Job and Output Management names for these files are as follows: NRJEJOB KSAM data file containing a maximum of 10,000 records, with information about each job submitted. NRJEKEY KSAM key file used to access the data file. The elements are the job numbers for JES2 and JES3 that are returned from the host. Alternate keys are the UserName.AcctName of the user that submitted the job, and the host job name.
Job Output Job and Output Management With either of the above DD statements, the applicable data set will be routed to special form PYCK. The form name is placed into the PDIR by the host system. When it receives the PDIR for the data set, NRJE will use the name of the special form PYCK to key into the Lookup Table. This table must be built by the NRJE manager and must contain all special formids supported at your remote, along with file equation attributes for each formid.
Job Output Job and Output Management • Continuation records are allowed, using the ampersand (&) as the last non-blank character. • Concatenated records cannot exceed 260 non-blank characters. • The file can be kept either numbered or unnumbered. • No distinction is made between upper and lower case characters. • An entry for each formid to be supported by the workstation must appear in the table. Each entry is limited to 6 characters if configured in the writer screen.
Job Output Job and Output Management into error recovery. In error recovery, NRJE issues an error message indicating the failure to locate the formid specified. If this formid cannot be found in the Lookup Table, NRJE will attempt to route output to the default destination with a priority of 2. This default destination is specified in the Output Destination field of the NMMGR Writer Data screen.
Job Output Job and Output Management support four characters or less for a special form name in their job control language. However, a user can direct forms output to this entry by using the SUBMIT command with solicited output: SUBMIT filename;FORMS='PAYROLL' disc =mydata.nrje,new Output is routed to a disk file with the above entry. Output destined for the formid disc is sent to the disk file mydata.nrje.sys. The new parameter overrides the default value of old. NRJE builds the file for you.
Job Output Job and Output Management CAUTION You can do this only in NRJE.SYS. File equations of this type apply only to the logon group and account of the NRJE monitor stream job. Always use a unique host jobname with this feature. Use of non-unique host jobnames may cause data to be lost in an attempt to create duplicate permanent files.
Job Output Job and Output Management • Gaining access to HP 3000 peripherals (HP 268xx laser printer, reading STORE tapes, etc.). • Uploading and downloading files. (Due to limitations of the host subsystem, deblocking may be necessary.) • Performing postprocessing of data on the HP 3000 before printing. • Deferring printing. • Providing a method for routing unsolicited output to disk files without compromising system security. See “System Security Considerations” earlier in this chapter.
Job Output Unsolicited Output Unsolicited Output Unsolicited output is defined as data sets received from a host or another remote that are not recognized by SNA NRJE as coming from jobs that were submitted on your workstation. Causes of Unsolicited Output Output can be considered unsolicited because of any of these circumstances: • The output was generated by a user on the host or another remote, not by a job submitted on the workstation.
Job Output Unsolicited Output Make sure in the job JCL that the output is directed to a spooled output device. See “Host Output Classes and Logical Writers” earlier in this chapter. Use COPY, FCOPY or (for MPE V and MPE XL prior to release 2.1) the MPE utility SPOOK to copy the output data set to another disk file, or output the data set to tape or to an output device. • Banner decode exit procedure You can configure your workstation to use an exit procedure that you supply to parse the host banner page.
Job Output Unsolicited Output 128 Chapter 4
5 User Intrinsics This chapter describes NRJE user intrinsics. Some of these intrinsics have NRJE manager extensions. You must be configured with NM capability to use the extensions to the intrinsics. Any MPE user can call these intrinsics without the manager extensions.
User Intrinsics Introduction Introduction All of these intrinsics are related to NRJE commands described in Chapter 3 , “User Commands.” The manager extensions to the commands are also indicated in this chapter. NRJE consists of a subsystem command interface and a set of user-callable intrinsics. An NRJE intrinsic, or a set of intrinsics, corresponds with each subsystem command that affects job stream input or output.
User Intrinsics Introduction Table 5-1 NRJE User Intrinsics Name Description NRJEActiveWS Provides the number and identification of active NRJE workstations. NRJEAlter * Revises the priority of a submitted job or jobs. NRJECancel * Cancels previously submitted jobs not yet transmitted. NRJEErrMsg Obtains and writes an NRJE error message string. NRJEHJCancel * Cancels jobs already transmitted to the host, by marking the Job Log to dispose of returning data sets.
User Intrinsics Introduction Parameters Common to NRJE Intrinsics Some parameters are common to most NRJE intrinsics; each parameter is described below. Workstation Identification The workstation identification (Wsid) parameter is common to all NRJE intrinsics. It is an eight-character input byte array. It must always begin with a letter followed by alphanumeric characters and be left-justified with trailing blank characters.
User Intrinsics Introduction Stack Size The NRJE user and manager intrinsics require 8500 words for local variables and working space. If your program requires 9000 words for its data stack, you should prepare your program file with a Segsize value of 17500 words. Your PREP command would look like this: :PREP USLFILE,PROGFILE;MAXDATA=17500 You also can specify Segsize in the PREPRUN and RUN commands.
User Intrinsics NRJEActiveWS NRJEActiveWS Provides the number and identification of active NRJE workstations. Syntax I BA I IA NRJEActiveWS ( InCount, WorkStations, OutCount, Result ) Parameters InCount An integer input variable by reference. The InCount parameter specifies the maximum number of entries that can be returned in the WorkStations array, from 1 through 8. If InCount is less than the actual number of active WorkStations, an error code will be returned in Result.
User Intrinsics NRJEActiveWS Description The NRJEActiveWS intrinsic provides a list of active workstations. The maximum list length is entered in the InCount parameter. The list is in the Workstations array. The number of active workstations is returned in the OutCount parameter. The Result array contains any intrinsic execution error codes. Text Reference This intrinsic is used to provide information for the DISPLAY command. See Chapter 3 , “User Commands.
User Intrinsics NRJEAlter NRJEAlter Revises the priority of a submitted job or jobs. Syntax BA BA I I IA NRJEAlter ( Wsid, Name, NameLen, NewPri, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. Name An input byte array.
User Intrinsics NRJEAlter NewPri An input integer variable. All jobs that are qualified by Name have their transmission priority revised to NewPri, which is from 0 through 14. The highest priority is 14. Result An eight-element integer output array (required). The Result array contains error codes that occurred during execution of this intrinsic. The first element of the Result array is set to zero if no errors took place.
User Intrinsics NRJECancel NRJECancel Cancels previously submitted jobs not yet transmitted. Syntax BA BA I IA NRJECancel ( Wsid, Name, NameLen, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. Name An input byte array.
User Intrinsics NRJECancel The first element of the Result array is set to zero if no errors took place. The structure of the Result array is described in “Parameters Common to NRJE Intrinsics” in the introduction to this chapter. Always test the first element of Result immediately after you call this intrinsic. If the first element of Result is not zero, test the other elements of Result to determine the nature of the problem that has occurred.
User Intrinsics NRJEErrMsg NRJEErrMsg Obtains and writes an NRJE error message string. Syntax IA I BA I I NRJEErrMsg ( Error, FileNum, Message, OutLen, Result ) Parameters Error An input integer array. The Error array is the result of another NRJE intrinsic call for which ASCII text is desired. The structure of the Error array is the same as the Result array. See “Parameters Common to NRJE Intrinsics” in the introduction to this chapter. FileNum An input integer variable.
User Intrinsics NRJEErrMsg occurred. See “Result Codes and Messages,” in the Installing and Troubleshooting SNA NRJE manual or the SNA NRJE Node Manager’s Guide. Description Use NRJEErrMsg to obtain and write messages that correspond with Result arrays of calls to other NRJE intrinsics. Information associated with Error is returned in Message. Find out the actual size of Message from OutLen. Set FileNum=0 if you want to prevent NRJEErrMsg from writing the contents of Message.
User Intrinsics NRJEHJCancel NRJEHJCancel Cancels jobs already transmitted to the host, by marking the Job Log to dispose of returning data sets. This intrinsic does not apply if you are connected to a VSE/POWER host system. Syntax BA BA I BA I NRJEHJCancel (Wsid, UserName, UserNameLen, JobList, JobListLen, I IA NumCancelled, Result) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation.
User Intrinsics NRJEHJCancel exception to this is a logon with NM capability. When cancelling by job number, you must have NM capability to cancel jobs submitted by another user. Numbers are those assigned by the host system. Each entry is eight characters long, left-justified, and blank-filled. An example of JobList with four entries is: DS1 1099 2122 FIRSTONE JobListLen An input integer variable (value required if JobList is supplied).
User Intrinsics NRJEHJCancel Text Reference See the CANCEL command in Chapter 3 , “User Commands.
User Intrinsics NRJEHJInfo NRJEHJInfo Obtains a list of jobs transmitted to the host, the number of data sets received against those jobs, and the special destinations of those data sets. This intrinsic does not apply if you are connected to a VSE/POWER host system.
User Intrinsics NRJEHJInfo • A UserName.AcctName. You must have NM capability to specify jobs submitted by other users. UserNameLen An input integer variable (required if UserName is supplied). The UserNameLen parameter specifies the number of bytes in UserName, from 0 through 17. JobList An input byte array (required if UserName and UserNameLen are not supplied. If JobList and JobListLen are supplied, then UserName and UserNameLen are not required parameters and are ignored).
User Intrinsics NRJEHJInfo that met the specification in UserName and JobList. Each entry in JobName is eight characters long, left-justified, and blank-filled. Each entry in JobName corresponds to an entry in JobNum. User An output byte array (required). The User array is a list of users of all submitted jobs that meet the specifications in UserName and JobList. Each entry in User corresponds to an entry in JobNum.
User Intrinsics NRJEHJInfo An entry is one of these: • file equation (:FILE filename, etc.). • ldev of an MPE output device (numeric entry). • an MPE device class name, enclosed in double quotes. • an actual file reference. • an alternate formid in the Lookup Table, enclosed in single quotes. PU An output byte array (required). The PU array is a list of destinations for output routed to NRJE punches on the standard form.
User Intrinsics NRJEHJInfo Description Use NRJEHJInfo to obtain information about jobs that have already been transmitted to the host. Input information to this intrinsic is as follows: • Workstation identification: Wsid. • Logical starting position within the Job Log: StartPos. • Maximum number of elements to be returned in all output arrays except Result: Incount. • Job set desired: UserName, UserNameLen, JobList, and JobListLen.
User Intrinsics NRJEJobInfo NRJEJobInfo Obtains a list of jobs submitted, but not transmitted to the host, and job spool file characteristics. Syntax BA I BA I I IA BA NRJEJobInfo ( Wsid, InCount, Name, NameLen, OutCount, FileId, User, BA DA IA IA LA IA IA JobName, JobSize, Priority, Rank, Time, State, Result Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter.
User Intrinsics NRJEJobInfo FileId An output integer array. The FileId array is a list of file identifications of all submitted jobs that met the specification in Name. Each entry is an integer reference to a spool file identification. User An output byte array. The User array is a list of users of all submitted jobs that met the specification in Name. Each entry in User corresponds to an entry in FileId. Each entry is eighteen characters long, left-justified, and blank-filled, in the form UserName.
User Intrinsics NRJEJobInfo Each entry in Rank corresponds to an entry in FileId. Time An output logical array. The Time array is a list of four-word entries describing when a spool file was created. Each entry in Time corresponds to an entry in FileId. The structure of each four-word entry is as follows: year day of the year hour minute where day of the year is from 1 through 366. State An output integer array. The State array is a list of the spooling states of each file.
User Intrinsics NRJEJobInfo Always test the first element of Result immediately after you call this intrinsic. If the first element of Result is not zero, test the other elements of Result to determine the nature of the problem that has occurred. Description Use NRJEJobInfo to obtain information about jobs that have been submitted, but are not yet transmitted. Input information to this intrinsic is as follows: • Workstation identification: Wsid.
User Intrinsics NRJEJobInfo Table 5-3 Use of Name Structure Form Effect File identification A five-character numeric string in the form nnnnn. Information is wanted for a submitted job with a spool file identifier of nnnnn. Job name An eight-character alphanumeric string beginning with a letter. Information is wanted for all submitted jobs that have this job name. @ A single @ character. Information is wanted for all jobs submitted by the logon user. Username.
User Intrinsics NRJELUList NRJELUList Provides a list of all LUs and related characteristics for a workstation. Syntax NRJELUList BA I I BA IA (Wsid, MaxEntries, ReturnEntries, LUList, ChainSizeList, DA DA IA MinJobSizeList, MaxJobSizeList, ActiveLuNameList IA IA AutoStartList, Result Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter.
User Intrinsics NRJELUList LUList An output byte array. The LUList array contains a list of entries of all LU names for the workstation. Each entry is eight characters, left-justified, with trailing blanks. Following is an example of a three-entry LUList: ERST NEXTONE LAST ChainSizeList An output integer array. The ChainSizeList array contains a list of chain sizes for each LU in a workstation. A chain size is the number of RUs sent from the workstation to the host before requesting a positive response.
User Intrinsics NRJELUList A zero element is returned if an LU is not initially started when a workstation is started. A -1 element is returned if an LU is initially started. following is a three-entry AutoStartList corresponding to LUList, above: 0 ERST is not initially started. -1 NEXTONE is initially started. -1 LAST is initially started. Result An eight-element integer output array (required). The Result array contains error codes that occurred during execution of this intrinsic.
User Intrinsics NRJEQueue NRJEQueue Obtains information about a workstation transmission queue (the spooled reader). Syntax BA I I BA I I NRJEQueue (Wsid, Reserved, QueueLdev, Reserved, Reserved, ChainSize, I I I I CompFlag, TransIndicator, ReaderStatus, ReaderFence, I IA SystemFence, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter.
User Intrinsics NRJEQueue CompFlag An output integer. Use the value of CompFlag to learn the state of compression configured for a workstation transmission queue. The values of CompFlag are as follows: • Any odd number: Data is transmitted to the host in compressed form. • Any even number: Data transmitted to the host is not in compressed form. TransIndicator An output integer.
User Intrinsics NRJEQueue When ReaderFence = 0, each output spool file whose priority is less than or equal to SystemFence is not transmitted. Result An eight-element integer output array (required). The Result array contains error codes that occurred during execution of this intrinsic. The first element of the Result array is set to zero if no errors took place. The structure of the Result array is described in “Parameters Common to NRJE Intrinsics” in the introduction to this chapter.
User Intrinsics NRJESubmit NRJESubmit Prepares a batch input job stream for transmission to a host system. NOTE The NRJESubmit intrinsic is documented to provide backward compatibility with releases of the SNA NRJE product prior to version A.52.00. Use of the NRJE2Submit intrinsic, available on version A.52.00 or later, is the preferred method because of the enhanced capabilities available with that intrinsic.
User Intrinsics NRJESubmit 86-character maximum per file reference). The format of a file reference is as follows: infile[/lockword][.GrpName[.AcctName[:envid]]] The meanings of the parameters used in this reference are described in Chapter 3 , “User Commands,” in the SUBMIT command description. FileLens An input integer array (required). The FileLens array contains the length in bytes of each file identifier in the FileList array.
User Intrinsics NRJESubmit The settings for Direct are as follows: • An odd number means your job file is written directly. Any translation and compression will be done during transmission of the job file to the host. • An even number means that any required translation or compression is done while copying the files you specified in FileList to the spool file of your job. Table 5-4, in this intrinsic’s description, shows how the Direct and SubCode parameters relate to each other.
User Intrinsics NRJESubmit This intrinsic does not transmit your job to the host. Job transmission takes place after communication is established with the host. See NRJECONTROL START in the SNA NRJE Node Manager’s Guide. Use the Wsid parameter to identify your workstation. The NumFiles parameter must specify the number of files that comprise your job input stream. The FileList, FileLens, and SubCode parameter arrays contain an entry for each file that goes into the job stream.
User Intrinsics NRJE2Submit NRJE2Submit Creates a job input stream on the transmission queue to send to a host system, and allows the user to specify output destinations for data sets returning from the job submitted to the host. If you are connected to a VSE/POWER host system, the output routing capabilities are not available.
User Intrinsics NRJE2Submit You must provide sufficient elements for this array. The maximum length for this array is 3440 bytes (40 files * 86 character maximum per file reference). The format of a file reference is as follows: Infile[/LockWord][.GrpName[.AcctName[:Envid]]] The meanings of the parameters used in this reference are described in Chapter 3 , “User Commands,” in the SUBMIT command description. FileLens An input integer array (required).
User Intrinsics NRJE2Submit The settings for Direct are as follows: • An odd number: your job file is written directly to the MPE Spooler. Any translation or compression is done during transmission of the job file to the host. • An even number: any required translation or compression is done while copying the files you specified in FileList to the spool file of your job. Table 5-4, in the NRJESubmit intrinsic description, shows how the Direct and SubCode parameters relate to each other.
User Intrinsics NRJE2Submit MaxJobs An input integer. The MaxJobs parameter specifies the maximum number of elements to be returned in the SpoolList array. SpoolList An output integer array. The first NumJobs or MaxJobs (whichever is less) elements of the SpoolList array contain the MPE spool file identification numbers of the host jobs (one per spool file) successfully submitted.
User Intrinsics NRJE2Submit the job. Otherwise, the command is stripped out and an error message is written to $STDLIST (the remainder of the job is submitted). Console commands embedded between jobs supplied on a single input stream are not supported. SIGNOFF card images are stripped from the input stream and a warning message is written to $STDLIST. See the SUBMIT command explanation in Chapter 3 , “User Commands,” for additional information.
User Intrinsics NRJEWelcome NRJEWelcome Obtains the contents of the NRJE welcome message. Syntax I I BA IA NRJEWelcome ( MaxLen, ActLen, Msg, Result ) Parameters MaxLen An input integer variable. The MaxLen parameter specifies the maximum text length that can be returned in Msg. The maximum length of the NRJE welcome message is 1912 characters. (This includes the carriage return and the line feed.) ActLen An output integer variable.
User Intrinsics NRJEWelcome Text Reference NRJE welcome messages are output immediately after the product identification banner when the subsystem command interface is used.
User Intrinsics NRJEWriter NRJEWriter Obtains information about the logical writers configured for a workstation. Syntax BA I I BA BA IA NRJEWriter ( Wsid, InCount, OutCount, WriterList, LdevList, PrList, IA BA BA IA IA TransList, Reserved, Reserved, Forced, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter.
User Intrinsics NRJEWriter a logical device class, or a ‘formid.' Each entry is eight characters long, left-justified, and filled with trailing blanks. PriList An output integer array. The PriList array is a list of output priorities that correspond to logical device numbers in LdevList. Each entry is an output priority, where PriList[i] is from 0 through 14; 14 is the highest priority. When PriList[i]=0, the system-configured default value is used. TransList An output integer array.
User Intrinsics NRJEWriter Description NRJEWriter is used to obtain information about the logical writers configured for your workstation. Enter your workstation identification (Wsid) and the maximum number of writers you expect (InCount). You receive the following output from NRJEWriter: • The number of writers (the OutCount parameter value). OutCount is also the length of the lists shown below.
User Intrinsics NRJEWSInfo NRJEWSInfo Obtains general information about a workstation. Syntax BA I BA BA BA IA NRJEWSInfo ( Wsid, ActiveFlag, JES, Remote, Reserved, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. ActiveFlag An output integer variable.
User Intrinsics NRJEWSInfo errors took place. The structure of the Result array is described in “Parameters Common to NRJE Intrinsics” in the introduction to this chapter. Always test the first element of Result immediately after you call this intrinsic. If the first element of Result is not zero, test the other elements of Result to determine the nature of the problem that has occurred. Description NRJEWSInfo is used to obtain general information about a workstation.
6 NRJE Manager Intrinsics This chapter describes intrinsics that can be used only by an NRJE manager (a user with NM capability).
NRJE Manager Intrinsics Introduction Introduction All user intrinsics, including those with manager extensions, are, described in Chapter 5 , “User Intrinsics.” An NRJE manager also can call user intrinsics that do not have manager extensions. All NRJE commands relate to intrinsics. The commands directly related to the intrinsics described in this chapter are described in the SNA NRJE Node Manager’s Guide. User commands, including those with manager extensions, are described in Chapter 3 , “User Commands.
NRJE Manager Intrinsics Common Parameters and Languages Common Parameters and Languages The introduction to Chapter 5 , “User Intrinsics,” describes the following: • Supported languages • Programming constraints • Common parameters • Stack size required These apply to NRJE manager intrinsics, also.
NRJE Manager Intrinsics Manager Intrinsics Manager Intrinsics Table 6-1 lists the NRJE manager intrinsics. These intrinsics require NM capability. NOTE If you are allowed access to the host console facility, you can use the console intrinsics: NRJEConsCheck, NRJEConsole, NRJERcvMsg, NRJERelease, and NRJESendCmd. Table 6-1 NRJE Manager Intrinsics Name Description NRJEConsCheck Indicates whether any outstanding host remote console messages are waiting to be received.
NRJE Manager Intrinsics User Intrinsics with Manager Extensions User Intrinsics with Manager Extensions Table 6-2 lists the NRJE user intrinsics with manager extensions. NRJE managers (MPE users configured with NM capability) use these intrinsics with extended features. These intrinsics are also available to all NRJE users, but with limited features. See Chapter 5 , “User Intrinsics.
NRJE Manager Intrinsics User Intrinsics User Intrinsics NRJE managers and users specify these intrinsics in the same way: • NRJEActiveWS • NRJEErrMsg • NRJELUList • NRJEQueue • NRJEWelcome • NRJEWriter • NRJEWSInfo See Chapter 5 , “User Intrinsics.
NRJE Manager Intrinsics NRJEConsCheck NRJEConsCheck Indicates whether any outstanding host remote console messages are waiting to be received. Syntax D IA NRJEConsCheck ( ConsoleId, Result ) Parameters ConsoleId An input double-word integer variable. The ConsoleId parameter is the remote host console identification. Obtain the value for this parameter by calling NRJEConsole before you call this intrinsic. Result An eight-element integer output array.
NRJE Manager Intrinsics NRJEConsCheck NRJEConsCheck is used with the following intrinsics: • NRJERcvMsg: to read one recent remote host console message. • NRJERelease: to relinquish ownership of the remote host console. Text Reference See the SNA NRJE Node Manager’s Guide for the description of “Host Console Commands.
NRJE Manager Intrinsics NRJEConsole NRJEConsole Obtains the host remote console of a workstation. Syntax BA D IA NRJEConsole ( Wsid, ConsoleId, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. ConsoleId An output double-word integer variable.
NRJE Manager Intrinsics NRJEConsole • NRJERcvMsg: to receive a host remote console message. • NRJERelease: to relinquish control of the host remote console. After NRJEConsole has returned control to your program, test the first element of Result. Text Reference CONSOLE also obtains access to the host remote console. See the SNA NRJE Node Manager’s Guide for more information.
NRJE Manager Intrinsics NRJELUStatus NRJELUStatus Reports the status and state of an LU session of a given LU name. Syntax BA BA IA IA NRJELUStatus ( Wsid, LUName, InfoArray, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. LUName An input byte array.
NRJE Manager Intrinsics NRJELUStatus Description The NRJELUStatus intrinsic reports the status and states of an LU session of a given LUName in InfoArray (a description of InfoArray is given below). Transmission chain size is also reported. Obtain the LUName of a Wsid by calling NRJELUList. When NRJELUStatus returns control to your routine, test the first element of Result. Table 6-3 InfoArray Structure Word Contents and Meaning 0–3 LU name 4 LU Entry State.
NRJE Manager Intrinsics NRJELUStatus Table 6-3 InfoArray Structure Word Contents and Meaning 10 Session Control Status. Values are as follows: • 0 = reset • 1 = waiting for Start Data Traffic • 2 = normal flow • 3 = UNBIND received • 4 = terminate state 11 Monitor Request Status. Values are as follows: • 0 = rest • 1 = init-self requested • 2 = term-self requested 12 Reserved. 13 Network Service Status.
NRJE Manager Intrinsics NRJERcvMsg NRJERcvMsg Reads one recent host remote console message. Syntax D LA I I IA NRJERcvMsg ( ConsoleId, OutBuffer, MaxOutBuf, OutputLength, Result ) Parameters ConsoleId An input double-word integer variable. The ConsoleId parameter is the remote host console identification. Obtain the value for this parameter by calling NRJEConsole before you call this intrinsic. OutBuffer An output logical array. The OutBuffer array contains the text of a host remote console message.
NRJE Manager Intrinsics NRJERcvMsg Description Call NRJERcvMsg to read one recent host console message. Obtain the ConsoleId by calling NRJEConsole first. Indicate the maximum byte length of the OutBuffer array in the MaxOutBuf parameter. Obtain the actual message length from the OutputLength parameter. While you own the host remote console, you receive all recent host remote console messages that are directed to your workstation. These messages may be in response to commands other than those you issued.
NRJE Manager Intrinsics NRJERdrAccess NRJERdrAccess Enables or disables NRJE user access to the NRJE reader. Syntax BA I IA NRJERdrAccess ( Wsid, OpCode, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. OpCode An input integer.
NRJE Manager Intrinsics NRJERdrFence NRJERdrFence Updates the outfence value of the NRJE workstation reader. Syntax BA I IA NRJERdrFence ( Wsid, NewOutFence, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. NewOutFence An input integer.
NRJE Manager Intrinsics NRJERdrFence Text Reference The RDRFENCE command also updates the outfence value of the NRJE workstation reader. See the SNA NRJE Node Manager’s Guide for a discussion of the command, spool files, and output priorities.
NRJE Manager Intrinsics NRJERelease NRJERelease Relinquishes access to the host remote console of a workstation. Syntax D IA NRJERelease ( ConsoleId, Result ) Parameters ConsoleId An input double-word integer variable. The ConsoleId parameter is the remote host console identification. Obtain the value for this parameter by calling NRJEConsole before you call this intrinsic. Result An eight-element integer output array (required).
NRJE Manager Intrinsics NRJERelease Text Reference RELEASE also relinquishes access to the host remote console of a workstation. See the SNA NRJE Node Manager’s Guide for more information on this command.
NRJE Manager Intrinsics NRJESendCmd NRJESendCmd Sends a remote host console command. Syntax D LA I IA NRJESendCmd ( ConsoleId, CmdBuffer, CmdLength, Result ) Parameters ConsoleId An input double-word integer variable. The ConsoleId parameter is the remote host console identification. Obtain the value for this parameter by calling NRJEConsole before you call this intrinsic. CmdBuffer An input logical array. The CmdBuffer array contains the remote host console command text to be transmitted.
NRJE Manager Intrinsics NRJESendCmd contain the command length in bytes. Use NRJESendCmd with the following intrinsics: • NRJERcvMsg: to read one recent remote host console message. • NRJEConsCheck: to determine whether any outstanding console messages are waiting to be received. • NRJERelease: to relinquish access to the remote host console. After NRJESendCmd returns control to your program, test the first element of Result.
NRJE Manager Intrinsics NRJEStartWS NRJEStartWS Initiates a workstation or LUs. Syntax BA I BA I IA NRJEStartWS ( Wsid, ChainSize, LUNames, LUNamesLen, Traces, I I I BA TraceFileLen, TraceMedium, TraceSize, TraceFile, BA IA DefaultFile, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter.
NRJE Manager Intrinsics NRJEStartWS If the value of LUNamesLen is 0 and the workstation is inactive, the configured auto-start LU names are initiated. If LUNamesLen=0 and the workstation is active, a Result will indicate an error. The maximum LUNamesLen value is 16. Traces A two-element input integer array. Each element of Traces contains an integer that represents a type of tracing to turn on or off. The use of two elements allows you to enable multiple trace types simultaneously.
NRJE Manager Intrinsics NRJEStartWS qualified 35-character disk file name, with lockword, in this form: filename[lockword][groupname[acctname]] The contents of TraceFile must be left-justified, with trailing blanks, and meet MPE standards for an actual file designator. If you specify a disk file that does not exist (a NEW file), then it will be created as the destination for trace output.
NRJE Manager Intrinsics NRJEStartWS Description The NRJEStartWS intrinsic initiates the NRJE workstation. It causes the NRJE monitor to be streamed and run as an MPE job. See the SNA NRJE Node Manager’s Guide for more information. When you call NRJEStartWS, you can start all LUs of a workstation that are configured for automatic starting (by setting LUNamesLen to zero), or you can supply a list of LUs in LUNames and set LUNamesLen to the length of the list.
NRJE Manager Intrinsics NRJEStopWS NRJEStopWS Stops or halts LU-LU session or workstation. Syntax BA I BA I IA NRJEStopWS ( Wsid, NumLUs, LUNames, StopCode, Result ) Parameters Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks. NumLUs An input integer.
NRJE Manager Intrinsics NRJEStopWS Result An eight-element integer output array (required). The Result array contains error codes that occurred during execution of this intrinsic. The first element of the Result array is set to zero if no errors took place. The structure of the Result array is described in “Parameters Common to NRJE Intrinsics” in the introduction to Chapter 5 , “User Intrinsics.” Always test the first element of Result immediately after you call this intrinsic.
NRJE Manager Intrinsics NRJETrace NRJETrace Initiates or terminates NRJE tracing. Syntax BA I IA I I NRJETrace ( Wsid, TraceOnOff, Traces, TraceFileLen, TraceMedium, I BA BA IA TraceSize, TraceFile, DefaultFile, Result ) Parameter Wsid An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks.
NRJE Manager Intrinsics NRJETrace Following is an example of Traces for LU tracing only: 1 0 TraceFileLen An input integer. The TraceFileLen parameter is the length in characters of the trace file designator, TraceFile. The number of characters may be between one and thirty-five. If this parameter is zero, the trace is recorded in the DefaultFile. TraceMedium An input integer. TraceMedium indicates the TraceFile device type. This parameter is called by reference.
NRJE Manager Intrinsics NRJETrace intrinsic, only the status array will be traced. DefaultFile An output byte array. The DefaultFile parameter is the file designator of the default trace file. A default file name is created whenever TraceFileLen is zero. Default file names are in the form NMTCnnnn.PUB.SYS, where nnnn is a four-digit number that is incremented each time a default trace is created. Default file names are up to 27 bytes long. The last character is always a blank.
NRJE Manager Intrinsics NRJEUpdWel NRJEUpdWel Updates the NRJE subsystem welcome message. Syntax BA I IA NRJEUpdWel ( Message, MessageLen, Result ) Parameters Message An input byte array. The Message parameter contains the message to be broadcast to any NRJE subsystem command interpreter user. The maximum Message length is 1920 characters. Separate each line of text by a carriage return character and a line feed character. A carriage return is %15, or !0D; a line feed is %12, or !0A.
NRJE Manager Intrinsics NRJEUpdWel Text Reference The WELCOME command also updates the NRJE subsystem welcome message. See the SNA NRJE Node Manager’s Guide for more information on this command. The NRJEWelcome intrinsic retrieves the text of the welcome message. See Chapter 5 , “User Intrinsics.
NRJE Manager Intrinsics NRJEUpdWel 210 Chapter 6
7 MPE Support Utilities and Commands This chapter describes certain MPE support utilities and commands that can be used with NRJE: • SPOOK (MPE V, and MPE XL releases prior to 2.1, only) • MPE spooling commands (MPE XL release 2.1 and later). Several other MPE commands are used in day-to-day NRJE operations: • LINKCONTROL (MPE V only) • NRJECONTROL • RESUMENMLOG • SHOWNMLOG • SNACONTROL • SWITCHNMLOG The NRJECONTROL commands are described in the SNA NRJE Node Manager’s Guide.
MPE Support Utilities and Commands SPOOK SPOOK If, after submitting jobs to NRJE readers, spooled files have not been transmitted to the host system, an HP 3000 user can use the SPOOK utility to alter the spooled files’ priority or to purge the files. You also can manipulate output spool files. This utility is described in MPE System Utilities. NOTE SPOOK exists only on MPE V and releases 1.1, 1.2, and 2.0 of MPE XL.
MPE Support Utilities and Commands MPE Spooling Commands MPE Spooling Commands Table 7-1 lists MPE commands that can be used to affect spooling. Table 7-1 MPE Spooling Commands MPE V, and MPE XL prior to release 2.1 MPE XL release 2.1 and later ALTSPOOLFILE SPOOLF ;ALTER Alters the characteristics of a spool file. DELETESPOOLFILE SPOOLF ;DELETE Deletes a spool file. OPENQ OPENQ Opens the spool queue for a specified logical device or device class.
MPE Support Utilities and Commands MPE Spooling Commands 214 Chapter 7
A Parsing Algoithms and User Exit Procedures These procedures are supplied with SNA NRJE and are required for the full job and output management capabilities of NRJE to function.
Parsing Algoithms and User Exit Procedures Parsing Algorithms Parsing Algorithms To route output properly, SNA NRJE must parse both “Job Received” messages (such as the $HASP100 message from JES2) and host system output banner pages of the received data sets. This capability is necessary for NRJE to be able to interpret the host system job number. This chapter describes the algorithms used to perform the parsing.
Parsing Algoithms and User Exit Procedures Parsing Algorithms “Job Received Message” Parsing Algorithm The algorithms used by NRJE to parse JES2 or JES3 “Job Received” console messages are shown below. Output variables are JobNumber, ReaderNumber, and JobName.
Parsing Algoithms and User Exit Procedures Parsing Algorithms JES2 Algorithm scan buffer for one of three keywords: "JOB" or "STC" or "TSU"; if found then skip trailing blanks; if "JOB" found then move while numeric to JobNumber variable else if "STC" or "TSU" found then JobNumber := "-1"; NOTE A JobNumber value of -1 indicates that the output is unsolicited and that the Job Log should not be checked for routing information.
Parsing Algoithms and User Exit Procedures User Exits User Exits Two exits have been added to SNA NRJE to facilitate job management and output management operation. One exit calls a customer’s procedure that decodes the host banner (separator page) and informs NRJE of the host job number for the data set. A separate exit procedure can be specified for each logical writer.
Parsing Algoithms and User Exit Procedures Banner Decode Exit Procedure Specification Banner Decode Exit Procedure Specification A description of the exit procedure to be used to parse host output banner pages is given below. NOTE In NRJE/XL, the Banner Decode Exit Procedure is called the Writer Decode Exit Procedure Specification.
Parsing Algoithms and User Exit Procedures Banner Decode Exit Procedure Specification text from the output data set. If DataLine contains a PDIR, RecordType is set to one. Jobnum An output byte array (of 4 bytes). This array’s size is from zero through three ASCII characters. Jobnum is initialized to ASCII blanks prior to each call of the exit procedure. If successful in decoding the host banner, the exit procedure is to return the job number in ASCII, left-justified, padded with blanks if necessary.
Parsing Algoithms and User Exit Procedures Banner Decode Exit Procedure Specification 2. Open the output file for NRJE by returning Filenum rather than Jobnum. NRJE then writes the data set to the file. 3. Open and write the entire data set to the output file. This is accomplished by not setting either of the output parms (Filenum or Jobnum), which causes NRJE to pass the entire data set to the procedure. FWRITE error handling is then the responsibility of the procedure.
Parsing Algoithms and User Exit Procedures Banner Decode Exit Procedure Specification If neither Filenum nor Jobnum is returned, NRJE passes the entire data set to the procedure and logs a warning message. NRJE assumes that the exit procedure is handling all output routing and writing operations.
Parsing Algoithms and User Exit Procedures Banner Decode Exit Procedure Specification Example procedure get'jobnumber(work'area,record,length,cctl,type,jobnumber, file'num,action); value length,cctl,type; logical array work'area; ! In, scratch area. byte array record; ! In, a line of data (or a PDIR) from ! the host. integer length, ! In, num bytes in record. cctl, ! In, carriage control value. type; ! In, if 0 record is data, if 1 record ! is a PDIR.
Parsing Algoithms and User Exit Procedures Banner Decode Exit Procedure Specification < ********************* Begin Get'Jobnumber ******************* > if type = DATA'RECORD then begin if record(JOB'STRING'POS) = "JOB" then begin ! A hit. scan record(JOB'STRING'POS + 3) while " ",1; @bptr := tos; ! Skip any leading blanks. move job number := bptr while N; ! Move while numeric. end ! If "JOB" found.
Parsing Algoithms and User Exit Procedures “Job Received” Message Exit Procedure “Job Received” Message Exit Procedure A description of the exit procedure to parse the console stream for a “Job Received” message is shown below; the message is HASP100 for JES2 and IAT6101 for JES3. Syntax LA BA I I Integer Procedure CON(UserWorkArea, ConsoleRecord, Length, ReaderNum, BA BA Jobnum, JobName) Function Return: Integer (-32768 through 32767).
Parsing Algoithms and User Exit Procedures “Job Received” Message Exit Procedure An output byte array (of 4 bytes). Jobnum is initialized to blanks by NRJE prior to each call to the exit procedure. If ConsoleRecord contains the “Job Received” message from the host, Jobnum is to be returned here, left-justified (four bytes maximum). JobName Output byte array (of 8 bytes). JobName is initialized to blanks prior to each call to the exit procedure.
Parsing Algoithms and User Exit Procedures “Job Received” Message Exit Procedure ########################################################### ! ! Scans the console record from the host and checks for whether a ! HASP100 (Job Received message) was received from the host. Returns ! reader number, job number and jobname if HASP100 detected. ! ! The format of the console message is as follows: ! ! hh.mm.ss JOB nnnn $HASP100 jobname ON Rxx.
Parsing Algoithms and User Exit Procedures “Job Received” Message Exit Procedure begin ! It's a hit! ! Need to skip leading blanks, if any, so that what we return is ! left justified. scan record(JNAME'POS) while BLANK,1; @bptr := tos; move jobname := bptr,(scan bptr until " "); ! Move until blank. scan record(JNUM'POS) while BLANK,1; @bptr := tos; move job number := bptr while N; ! Move while numeric.
Parsing Algoithms and User Exit Procedures “Job Received” Message Exit Procedure 230 Appendix A
Glossary A ASCII American Standards Committee on Information Interchange. A standard used by computers for interpreting binary numbers as characters. Console: A logical device through which commands are transmitted to the host job entry system, and responses (messages generated by the host) are received by NRJE. D B Batch communications: A form of data communications in which a facility collects data over a period of time and then submits collected information to a host computer.
transmission control for one of the sessions of a network addressable unit (NAU). JES3: A common IBM job entry subsystem used under the MVS operating system. Host: A host system is a central computer which provides services for other computers and terminals attached to it. Job: A file to be transmitted to a host computer, to be executed as a job. I INIT-SELF: An SNA request to the SSCP to initiate an LU-LU session. Intrinsic: A subprogram provided by Hewlett-Packard systems.
Logical device: See ldev. N Logical printer: A logical printer receives line printer images from a host system. NAU: Network addressable unit. The NAU represents the source and destination of data in a network. A communications session must exist before data can be transferred. Three types of NAUs exist: SSCPs, PUs, and LUs. Sessions are established by the SSCP, Logical punch: A logical punch receives card punch images from a host system.
Output management: The ability to route output by using special form identifiers (formids) in the job JCL. The formids are used to key into a Lookup Table that maps the formid to a file equation identifying the final destination of the output. P Physical unit: See PU. RH: Request or response header. These are attached to SNA RUs to control data flow and support other network services. RU: Request or response unit. S SDLC: Synchronous Data Link Control.
Spooled reader: The MPE ldev for holding jobs to be sent to the host for a given NRJE workstation. SSCP: System services control point. An SSCP manages nodes within its domain. An SSCP stores status information for personnel to maintain a network. It exists only in the host node and is implemented by the communications access method T TERM-SELF: An SNA request to the SSCP to terminate an LU-LU session. VTAM: Virtual Telecommunications Access Method.
Index A access the host console, 64 ACF/NCP, 35 ACF/VTAM, 35 active NRJE workstations NRJEActiveWS, 134 allowed commands, 56, 64, 83 ALTER command, 137 MPE, 213 ALTER command description, 58 alter spool file, 213 alter spooled files’ priority, 212 ALTSEC command MPE, 124 ALTSPOOLFILE command MPE, 213 B banner decode exit procedure, 127 batch communications, 26 batch input job stream prepare for transmission, 90 batch jobs, 42 block mode terminal, 34 C CANCEL command, 61, 139, 144 cancel jobs awaiting trans
Index default workstation changing, 77 default workstation identifier, 53 defer files, 97 DELETE command MPE, 213 delete output data sets, 61 delete spool file, 213 DELETESPOOLFILE command MPE, 213 device class, 118 DIRECT, 90 disable user access to NRJE reader, 192 disk file fixed-width, 116 undefined-width, 116 variable-width, 116 disk files, 28, 52, 104 diskette, 28 DISPLAY command, 135, 157, 160, 174, 176 DISPLAY command description, 67 display job information, 85 DS/3000 services, 94 E EBCDIC, 73 enab
Index interactive access NRJE, 30, 54 intrinsic data types, 179 intrinsic tracing, 200 intrinsics, 30, 54 intrinsics with manager extensions, 181 invoke subsystem command interpreter, 77 invoking NRJE, 42 IRS SCS, 95 ISO (International Standards Organization), 26 J JES2, 35 JES2 Set command, 108 JES3, 35 JES3 *START command, 108 JOB cards, 40, 41 Job Control Language (JCL), 30, 38 job delimiters, 73 job entry subsystems, 29, 35 job input stream create, 165 Job Log, 63, 117, 118, 119, 126, 143 job managemen
Index NMDUMP, 65 NMMGR Workstation Data screen, 96 NMMGR Writer Data Screen, 105 NMMGR Writer Data screen, 111, 115, 122 Node Management Services, 65 non-printable characters, 94 non-spooled device, 52 NOTRANSLATE, 73, 90 NRJE (Network Remote Job Entry), 26 NRJE command, 42, 63, 91, 208 NRJE command description, 77 NRJE Configuration Workstation Data screen, 101 NRJE Logical Unit (NRJELU), 117 NRJE manager, 55 NRJE monitor, 202 NRJE welcome message, 170 NRJE2Submit intrinsic, 99, 163 NRJE2Submit intrinsic
Index output routing, 119, 163 control hierarchy, 105 output routing specification resolution, 105 override default workstation identifier, 55 P packed decimal numerical data, 94 parse Job Received messages, 127 parse the host banner page, 127 parsing algorithms, 118 PDIR (Peripheral Device Information Record), 112, 118 Peripheral Device Information Record (PDIR), 118 Peripheral Device Information Record (PDIR), 112 PR= option SUBMIT command, 115 PR=option SUBMIT command, 118 PREP command, 133 prepare ba
Index RUN command description, 84 S sample session NRJE, 43 segments identify version, 100 Selected Form, 105 send a remote host console command, 197 sending jobs to a host, 42 share file restriction, 39 SHOW command, 59, 62, 63, 91, 149, 153 SHOW command description, 85 show job information, 85 SHOWLOG command MPE, 211 SHUTQ command MPE, 213 SIGNOFF card images, 169 SIGNOFF cards, 40, 96 SNA (Systems Network Architecture), 26 SNA character strings, 109 SNA format headers, 29 SNA link product, 29 SNA Link/
Index NEW, 207 OLD, 207 TRACEOFF command, 207 TRACEON command, 207 tracing NRJE, 205 start NRJE, 205 stop NRJE, 205 translation of data, 29, 91 transmission priority, 97 changing, 58 transmission queue, 28, 139 display information, 68, 158 TRANSPARENT, 73 TRN SNA Character String (SCS) control, 95 U unsolicited output, 126 user commands, 51, 56 user intrinsics, 129, 182 user tasks, 42 V VERSION command description, 100 version of SNA NRJE software, 100 virtual reader, 29 VPLUS, 34 VSE/POWER, 35 VSE/POWER A
