NSCONTROL [ MPE/iX Commands Reference Manual Volume I ] MPE/iX 5.0 Documentation
MPE/iX Commands Reference Manual Volume I
NSCONTROL
Controls the Network Service subsystem.
Syntax
NSCONTROL function[;function]...
function may be
START=[service [,service]...] STOP=[service [,service]...] ABORT
AUTOLOGON= [{ON }] [{,ALL }] LOADKEYS LOG= [{ON }]
[{OFF}] [{[,service [,service]]}] [{OFF}]
[,ALL ]
[,RPM ]
[,ENV ] [{,LOW }] SERVER={servername}[,minservers][,maxservers]
[,DSDAD ] [{,HIGH}] {ALL }
[,DSSERVER]
[,VTSERVER]
[USERS ]
[SERVICES]
STATUS=[SERVERS ] VERSION[=MOD]
[SUMMARY ]
[ALL ]
[[,...] ]
Parameters
START [=service
[,service]...]... Starts Network Services that are installed on your
system. By default, all installed services are
started. Optionally you may specify one or more
specific services to be started. Possible specific
services include:
LOOPBACK Enables remote users to run loopback diagnostic
programs that connect to the local node.
The following services are available if you have the NS/3000 product
installed:
NFT Enables remote users to transfer files to or from
the local node using the DSCOPY command and
intrinsic.
NFTL Enables local users to transfer files to or from
remote nodes using the DSCOPY command and
intrinsic.
NSSTAT Enables remote users to use the NSSTATUS intrinsic
and DSLINE;SERVICES command to retrieve NS
information from the local node.
NSSTATL Enables local users to use the NSSTATUS intrinsic
and DSLINE;SERVICES command to retrieve NS
information from the local and remote nodes.
PTOP Enables remote users to create and communicate with
PTOP slave processes on the local node. The VT
service must also be started. PTOP can be used
only by HPDESK.
PTOPL Enables local users to create and communicate with
PTOP slave processes on remote nodes. The VTL
service must also be started. PTOPL can be used
only by HPDESK.
RFA Enables remote users to access files and data bases
on the local node.
RFAL Enables local users to access files and data bases
on remote nodes.
RPM Enables remote users to create and kill processes
on the local node using the Remote Process
Management (RPM) service.
RPML Enables local users to create and kill processes on
the local and remote nodes using the Remote Process
Management (RPM) service.
VT Enables remote users to logon to the local node
using HP's TCP message mode.
VTA Enables remote users to logon to the local node
using TCP stream mode.
VTL Enables local users to log onto remote nodes using
the REMOTE HELLO command.
VTR Enables remote users to access local terminals
using the Virtual Terminal service.
VTRL Enables local users to access terminals on remote
nodes using the Virtual Terminal service.
There may be additional services that can be
enabled if other network products, such as Personal
Productivity Center, are installed. Refer to that
network product's documentation to obtain the
appropriate service names.
STOP [=service
[,service]...]... Stops Network Services, although existing users of
the service(s) can continue until they terminate
their use. By default, all installed services are
stopped. Optionally you may specify one or more
specific services to be stopped. Possible services
include any of the same service names that you are
allowed to specify for the START parameter
described above.
ABORT Immediately terminates all the servers and
services.
AUTOLOGON Enables or disables the autologon feature of the
NFT, RFA and/or RPM services. Default: ON,ALL.
AUTOLOGON= [{ON }] [{,ALL }]
[{OFF}] [{[,service [,service]]}]
LOADKEYS Loads the Network Service command keywords while
NS/3000 is active.
[,ALL ]
[,RPM ]
LOG= [{ON }] [,ENV ] [{,LOW }]
[{OFF}] [,DSDAD ] [{,HIGH}]
[,DSSERVER]
[,VTSERVER]
ON Enables detailed event logging of the specified
module.
OFF Disables detailed event logging of the specified
module.
For each Network Service software module, two
levels of event logging are provided. These are
HIGH, which logs all events, and LOW, the default,
which logs a subset of the events, as specified
below.
ALL LOW Logs LOW events for all modules. HIGH Logs HIGH
events for all modules.
RPM LOW Logs RPMCREATE and RPMKILL requests. HIGH Same as
LOW.
ENV LOW Logs environment information from DSLINE and REMOTE
HELLO commands.
ENV HIGH Same as LOW, plus environment table locking and use
counts.
DSDAD LOW Logs creation and deletion of sockets, ports, and
server processes.
DSDAD HIGH Same as LOW, plus all received service requests and
internal messages between DSDAD and server
processes.
DSSERVER LOW Logs internal initialization messages between DSDAD
and DSSERVER processes.
DSSERVER HIGH Same as LOW, plus all received messages from other
processes.
VTSERVER LOW Logs internal initialization messages between DSDAD
and VTSERVER processes.
VTSERVER HIGH Same as LOW, plus all received messages from other
processes.
SERVER={servername} [,minservers][,maxservers]
{ALL }
Dynamically alters the minimum or maximum number of servers. By default
applies to all servers. Optionally you may specify one or more specific
servernames. Possible servernames and their default minserver and
maxserver values are:
LOOPBACK For the Loopback Service. Default
minserver,maxserver values are 0,300.
NSSTATUS For the NSSTAT service (NSSTATUS intrinsic and
DSLINE; SERVICES command). Default minserver,
maxserver values are 0,300.
VTSERVER For VT and Reverse VT. Default minserver,maxserver
values are 0,300.
The following servers are available if you have the NS/3000 product
installed:
NFT For NFT (DSCOPY). Default minserver,maxserver
values are 0,300.
DSSERVER For RFA, RDBA, PTOP and RPM. Default minserver,
maxserver values are 0,300.
There may be additional servers to control if other network products,
such as Personal Productivity Center, are installed. Refer to that
network product's documentation to obtain the appropriate server names.
minservers The minimum number of servers which must be
available at all times. Available servers which
are not in active use are kept in reserve until a
service request is received. If necessary,
additional servers are created immediately to fit
the new minimum specified. Valid range: 0..1250;
however, see note below. Default for all current
servers is 0.
maxservers The maximum number of servers of this type allowed
to be active at one time. If necessary, reserved
servers are terminated to fit the new maximum.
Valid range: 0..32767; however, see note below.
Default varies by server.
NOTE The total number of all active servers may not exceed 1250. The
sum of all minservers must always be 1250 or less. You may specify
a number greater than 1250 as one or more maxservers values, but
there will never be more than a total of 1250 servers of all kinds
at any one time.
STATUS Displays current status information about NS3000/XL
Services.
STATUS[=USERS|SERVICES|SERVERS|SUMMARY|ALL[,...]]
The STATUS parameter can be unqualified, or can be
keyword equated to one or more of the following
values:
USERS Display the jobs and sessions
on this node that are using
Network Services.
SERVICES Display information about the
services.
SERVERS Display information about the
servers.
SUMMARY Display a summary of
information about services,
servers, and users.
ALL Same as specifying SERVICES,
SERVERS and USERS. (DEFAULT)
VERSION Displays the overall version of the NS/3000
software. If qualified with the MOD keyword, also
displays the version of each of the Network
Services software modules.
VERSION[=MOD]
Operation Notes
NSCONTROL START Starts the Network Services subsystem.
NSCONTROL STOP Stops the Network Services subsystem. STOP executes a
shutdown of Network Services. Existing users may continue using the
Network Services until they complete their NS activity, but new users are
prevented from using the services. When all users have finished using
the NS subsystem, the subsystem will stop entirely.
NSCONTROL ABORT Immediately terminates all the servers and services of
the Network Services. Note that STOP is the normal way to shutdown
Network Services. The ABORT function should only be used in abnormal
situations.
NSCONTROL AUTOLOGON Enables or disables the autologon feature of the NFT,
RFA and RPM services. When disabled, remote users are required to
establish a regular session via VT and :REMOTE HELLO before they can use
NFT, RFA or RPM on this system. This is useful if you wish to force all
remote users to execute a logon security UDC before they access anything
on this system. When NS is first started, this feature is ENABLED.
NSCONTROL LOADKEYS Loads the Network Services command keywords from the
ASCAT.NET.SYS catalog. You need to use this command only if the catalog
is modified, such as for localization.
NSCONTROL LOG Enables or disables detailed event logging for the Network
Service.
NSCONTROL SERVER Alters the characteristics of the Network Service
processes.
NSCONTROL STATUS Displays information about the Network Services.
NSCONTROL VERSION Displays the overall version of the Network Services
subsystem, and optionally the version of each of its modules.
Examples
Start the transport subsystem on the "LAN1" and "WIDE" networks, then
start all of the NS network services:
:NETCONTROL START;NET=LAN1
:NETCONTROL START;NET=WIDE
:NSCONTROL START
Stop all Network Services, while letting existing users continue their
work:
:NSCONTROL STOP
Stop the VT and Reverse VT services only. Let all other started services
remain available:
:NSCONTROL STOP=VT,VTR
Enable logging of information from DSLINE and REMOTE HELLO commands, and
service requests received by the DSDAD process:
:NSCONTROL LOG=ON,ENV,LOW;LOG=ON,DSDAD,HIGH
Set the minimum number of running DSSERVER processes to 2 and the maximum
to 10:
:NSCONTROL SERVER=DSSERVER,2,10
Show the status of Network Services:
:NSCONTROL STATUS=SERVICES
SERVICE TYPE SERVER DESCRIPTION
.
RPM REMOTE DSSERVER INCOMING REMOTE PROCESS MANAGEMENT
VTL LOCAL VTSERVER OUTGOING VIRTUAL TERMINAL
VT REMOTE VTSERVER INCOMING VIRTUAL TERMINAL
.
.
.
Display the overall version and product number of the Network Services
subsystem:
:NSCONTROL VERSION
Network Services overall subsystem version: B.00.10
NS3000/XL SERVICES: 36920B
Related Information
Commands NETCONTROL
Manuals Migration Process Guide (30367-60003)
MPE/iX 5.0 Documentation