NSSTATUS Intrinsic

Figure 6-2 Service List Data Structure

Figure 6-3 Service List Entry Data Structure

Figure 6-4 Server List Data Structure

Figure 6-5 User List Data Structure

Figure 6-6 User List Entry Data Structure

Figure 6-7 Server Type List Data Structure

Figure 6-8 Server Entry Data Structure

Figure 6-9 Env List Data Structure

Figure 6-10 Env List Entry Data Structure

Figure 6-11 Initiator's Information Format

1. Determine if the VT service is started on the local node:

   Name := 'VT'; NameLength:=2; ItemNum:=4; NSSTATUS (Name, NameLength, , , Status, ItemNum, VtStarted);

   If the VT service is started, VtStarted will be set to 1; otherwise it will be set to -1 or 0.

2. Determine if the VT service is started on the remote node NODE1:

   Name := 'VT'; NameLength:=2; Node Name:= 'NODE1' NodeLength:=5; ItemNum:=4; NSSTATUS (Name, NameLength, NodeName, NodeLength, Status, ItemNum, VtStarted0;

   If the VT service on NODE1 is started, VtStarted will be set to 1; otherwise it will be set to -1 or 0.

3. Determine if the NFT service is started and to find out how many active and reserved NFT servers currently exist on the local node:

   Name := 'NFT'; NameLength:=3; ItemNum4:=4; ItemNum10:=10; ItemNum11:=11; NSSTATUS (Name, NameLength, , , ,Status, ItemNum4,NftStarted, ItemNum10, ActiveServers, ItemNum11, ReservedServers);

   This sets NftStarted to 1 if NFT is started, and returns the number of active and reserved NFT servers to ActiveServers and ReservedServers, respectively. This example uses the fact that NFT is the name of both the service and the server.

4. To obtain all the status information for services, servers, and users on the remote node NODE1:

   NodeName := 'NODE1' NSSTATUS (, , NodeName, NameLength, Status, ItemNum1,ServiceList, ItemNum2, ServerList, ItemNum3, UserList);

   This returns to the arrays ServiceList, ServerList, and Userlist the information formatted as defined in the data structures in this chapter.

5. Suppose #S1 (Manager.sys) on node A creates a remote session #S5 (using VT) on node B. The initiator of #S5 information can be obtained by running the following NSSTATUS intrinsic call on node B.

   Name := '#S5' {or logon string of #S5} NameLength :=3; ItemNum :=21;

   NSSTATUS (Name, NameLength, , , Status, ItemNum, InitiatorInfo);

   If the intrinsic returns without an error then the following information will be in the InitiatorInfo record.

   InitiatorInfo.JobType --- 1 { indicates Session}InitiatorInfo.JobNum --- 1 { session num }InitiatorInfo.Ldev --- 20 { logical device numb of #S1 }InitiatorInfo.LocRem --- 1 { local session. not a VT session}InitiatorInfo.Logon --- 'MANAGER.SYS'InitiatorInfo.NodeLen --- 8InitiatorInfo.NodeName--- 'A.IND.HP'

6. Consider the above example. The same information can be obtained by running the following NSSTATUS intrinsic on Node C, which is on the same network.

   Name := '#S5' {or logon string of #S5} NameLength:=3; ItemNum:=21; NodeName :='B', NodeLength :=1;

   NSSTATUS (Name, NameLength, NodeName,NodeLength, Status, ItemNum, InitiatorInfo);

   In this case, the intrinsic on Node C first goes to Node B and gets #S5's information. From this information, it gets the initiator's SID and node name and then goes to that node--in this case Node 'A'. It then gets the initiator's session information based on the SID — in this case #S1. Note: all the three systems involved in this scenario must have this fix.

   See Table 6-2 “NSINFO Errors” for NSINFO Errors.

   Table 6-2 NSINFO Errors

   Error Number	Meaning
   0	Successful completion of NSSTATUS intrinsic.
   1	Required parameter missing.
   2	Invalid item number. Item number must be an integer in the range 1 to 18.
   3	Item number specified without corresponding item array.
   4	Item array specified without corresponding item.
   5	Name length too large.
   6	Name length too small.
   7	Expected a job or session number.
   8	Non-numeric character in the job or session number.
   9	Expected "#" as first character in Name parameter.
   10	Bounds violation.
   11	Unknown or invalid node name.
   12	Node name specified without node name length.
   13	Node name length specified without node name.
   14	Communications error occurred with the remote NSSTATUS server. Most likely the remote system does not support the NSSTATUS intrinsic.
   15	Node Manager (NM) capability required to retrieve the requested item.
   16	DB not stack. (NM) capability required to retrieve the request.
   17	Local NSSTATUS service has not been started. See Node Manager.
   18	Internal Resource Error. Could not create reply port. Try again.
   19	Remote node does not support option 21 (Remote node does not have this enhancement).
   20	Option 21 works for only VT sessions. Given session is not a VT session.
   21	Could not access initiator node using the node name in $BACK environment.