|
|
SNA NRJE User/Programmer Reference Manual: HP 3000 MPE/iX Computer Systems > Chapter 5 User IntrinsicsIntroduction |
|
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. NRJE intrinsics can be called from:
If you omit any parameters, you must retain the commas that follow them. No variable length calling sequences exist. Byte array parameters with the left-most character blank indicate that a default value will be used. Split-stack mode intrinsic calls are prohibited. See Table 5-1 “NRJE User Intrinsics”, "NRJE User Intrinsics" for a summary. Some user intrinsics have capabilities that can be used by NRJE managers only. NRJE intrinsics that can be used only by NRJE managers are described in Chapter 6 “NRJE Manager Intrinsics” Table 5-1 NRJE User Intrinsics
Some parameters are common to most NRJE intrinsics; each parameter is described below. 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. If the workstation identifier is less than eight characters long, it must be followed by blank characters. A Result parameter is common to all intrinsics. It is an eight-element integer array. When your intrinsic call is successful, the first element of the Result array is set to zero. See Table 5-2 “Result Array Structure”. and also see "Result Codes and Messages," in the Installing and Troubleshooting SNA NRJE manual or the SNA NRJE Node Manager's Guide. The elements of the Result array are as follows: Table 5-2 Result Array Structure
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:
You also can specify Segsize in the PREPRUN and RUN commands. You cannot specify Segsize with any compile-and-prepare or compile-and-go commands such as SPLPREP or SPLGO. These data types are used in intrinsic descriptions:
|
|