Displays information about the Network Services.
Syntax |
 |
[=USERS ]
[=SERVICES]
NSCONTROL STATUS [=SERVERS ]
[=ALL ]
[=SUMMARY ] |
Parameters |
|
- STATUS
Displays information about the Network Services.
Can be used to check if the Network Services were successfully initiated,
or to check on the current status using the following parameters:
- USERS
Displays the sessions on the node that are associated
with the Network Services.
- SERVICES
Displays information about the services.
- SERVERS
Displays information about the servers.
- SUMMARY
Displays a summary of the information about services,
servers, and users.
- ALL
Displays all available information about services,
servers, and users.
You can qualify the STATUS
function with one parameter or with a list of parameters separated
by commas.
Default: ALL
Discussion |
|
This function displays information on those local sessions
that were created by a DSLINE and
REMOTE HELLO and on those remote
sessions that were created by a REMOTE HELLO.
The STATUS display does not list
information on either local sessions that are using DSCOPY
without a REMOTE HELLO or temporary
remote sessions created by NFT,
RFA, or RPM.
The following examples show the information provided by the
STATUS function of the NSCONTROL
command.
Example 1 |
|
The following example shows the status of the Network Services.
Local means the service gives local users access to remote resources;
remote means the service gives remote users access to local resources.
Server indicates the type of server, NFT
or DSSERVER, used for the service.
For this example, all the services were started as indicated by
YES in the STARTED
column of the display. A NO in
that column would indicate that the service was not started. You
can use the STATUS display to verify
whether each individual service is started or not, and whether it
is available for local or remote use. This is helpful when using
the optional services list of the NSCONTROL START
and STOP functions.
:NSCONTROL STATUS=SERVICES
SERVICE TYPE STARTED SERVER DESCRIPTION
VTA REMOTE YES VTSERVER INCOMING STREAM MODE VIRTUAL TERMINAL
NSSTATL LOCAL YES NSSTATUS OUTGOING NSSTATUS SERVICE
NSSTAT REMOTE YES NSSTATUS INCOMING NSSTATUS SERVICE
LOOPBACK REMOTE YES LOOPBACK INCOMING LOOPBACK SERVICE
RPML LOCAL YES DSSERVER OUTGOING REMOTE PROCESS MANAGEMENT
RPM REMOTE YES DSSERVER INCOMING REMOTE PROCESS MANAGEMENT
PTOPL LOCAL YES DSSERVER OUTGOING PROGRAM-TO-PROGRAM COMMUNICATION
PTOP REMOTE YES DSSERVER INCOMING PROGRAM-TO-PROGRAM COMMUNICATION
RFAL LOCAL YES DSSERVER OUTGOING REMOTE FILE ACCESS
RFA REMOTE YES RASERVER INCOMING REMOTE FILE ACCESS
NFTL LOCAL YES NFT OUTGOING NETWORK FILE TRANSFER
NFT REMOTE YES NFT INCOMING NETWORK FILE TRANSFER
VTRL LOCAL YES VTSERVER OUTGOING REVERSE VIRTUAL TERMINAL
VTR REMOTE YES VTSERVER INCOMING REVERSE VIRTUAL TERMINAL
VTL LOCAL YES VTSERVER OUTGOING VIRTUAL TERMINAL
VT REMOTE YES VTSERVER INCOMING VIRTUAL TERMINAL |
Example 2 |
|
Example 2 shows the status of the servers. Here the minimum
number of NFT servers is 0 and
the maximum is 300 (the defaults). There are no NFT
servers created. The minimum number of VTSERVERS
is 6 and the maximum is 300. One, with process ID number (PIN) 50,
is active, being used for the VT service
with session #S1. The other five are not being used but are in reserve.
:NSCONTROL STATUS=SERVERS
SERVER MIN MAX ACTIVE RESERVED DEBUG PIN JOBNUM STATUS
RASERVER 0 300 0 0 OFF
NSSTATUS 0 300 0 0 OFF
LOOPBACK 0 300 0 0 OFF
VTSERVER 6 300 1 5 OFF
50 #S1 ACTIVE
51 RESERVED
49 RESERVED
41 RESERVED
58 RESERVED
57 RESERVED
NFT 0 300 0 0 OFF
DSSERVER 0 300 0 0 OFF
TOTAL NUMBER OF ACTIVE SERVERS: 1
TOTAL NUMBER OF RESERVED SERVERS: 5
TOTAL NUMBER OF SERVERS: 6 |
Example 3 |
|
In example 3, assume that a user has entered the following
commands on NODE1:
:HELLO MANAGER.SYS
:DSLINE NODE2
:REMOTE HELLO MGR.TELESUP |
The result on NODE1 is:
:NSCONTROL STATUS=USERS
JOBNUM SESSION TYPE USER.ACCOUNT
ID SERVICES NODENAME
#S1 #060507 LOCAL MANAGER.SYS
#031237 VT NODE2.DOMAIN.ORGANIZATION
TOTAL NUMBER OF LOCAL NS USERS: 1
TOTAL NUMBER OF REMOTE NS USERS: 0
TOTAL NUMBER OF NS USERS: 1 |
and on NODE2:
:NSCONTROL STATUS=USERS
JOBNUM SESSION TYPE USER.ACCOUNT
ID SERVICES NODENAME
#S3 #031237 REMOTE MGR.TELESUP
#060507 ORIGIN NODE1.DOMAIN.ORGANIZATION
TOTAL NUMBER OF LOCAL NS USERS: 0
TOTAL NUMBER OF REMOTE NS USERS: 1
TOTAL NUMBER OF NS USERS: 1 |
The display on NODE2 shows
the remote session for MGR.TELESUP
from the REMOTE HELLO on NODE1.
As illustrated in example 3, the session IDs can be used to match
up the local and remote sessions. The local session on NODE1,
with ID #060500, is the origin of the remote session on NODE2,
with ID #031237.
Example 4 |
|
In the following example, the Network Services have not been
started (no NSCONTROL START has
not been issued). The system response to the NSCONTROL STATUS=USERS,SERVICES
command shows that there are no Network Services users and no Network
Services currently active.
:NSCONTROL STATUS=USERS,SERVICES
NO CURRENT NETWORK SERVICE USERS
NO NETWORK SERVICES ARE CURRENTLY ACTIVE |
Example 5 |
|
Example 5 shows the brief summary of users, services, and
servers information. This is an abbreviated display of STATUS=ALL.
:NSCONTROL STATUS=SUMMARY
TOTAL NUMBER OF LOCAL NS USERS: 1
TOTAL NUMBER OF REMOTE NS USERS: 0
TOTAL NUMBER OF NS USERS: 1
OUTGOING SERVICES INCOMING SERVICES
SERVICE STARTED FEATURES SERVICE STARTED FEATURES
NSSTATL YES VTA YES
RPML YES NSSTAT YES
PTOPL YES LOOPBACK YES
RFAL YES RPM YES AUTOLOGON OFF
NFTL YES PTOP YES
VTRL YES RFA YES AUTOLOGON ON
VTL YES NFT YES AUTOLOGON ON
VTR YES
VT YES
SERVER MIN MAX ACTIVE RESERVED DEBUG
RASERVER 0 300 0 0 OFF
NSSTATUS 0 300 0 0 OFF
LOOPBACK 0 300 0 0 OFF
VTSERVER 6 300 1 5 OFF
NFT 0 300 0 0 OFF
DSSERVER 0 300 0 0 OFF
TOTAL NUMBER OF ACTIVE SERVERS: 1
TOTAL NUMBER OF RESERVED SERVERS: 5
TOTAL NUMBER OF SERVERS: 6 |
