Display detailed information about the current server process. The following table describes the output fields of the server info display.
General format
server info
The following table describes the output of schedule server info:
Field |
Description |
Version number |
Currently installed SCHEDULE version
|
Platform
|
Operating system(s) currently running SCHEDULE
|
Local node
|
Name of server
|
Database node
|
Location of SCHEDULE database
|
Network nodes
|
Nodes that have sent network messages
|
Defined cluster
|
Nodes in local cluster
|
Active cluster |
Cluster members running SCHEDULE
|
NRQ frame count
|
Server execution sequence count
|
NRQ active count
|
Number of open processing requests
|
NRQ available count
|
Available processing request packets
|
NRQ dispatch count
|
Number of processing steps performed
|
NRQ dispatch rate
|
Number in last second interval/Average NRQs/Peak NRQs
|
PRQ dispatch 1,2,3 |
Priority queue dispatch rates |
Active threads
|
Number of active threads (UNIX) Always 1 in VMS
|
Submit count
|
Number of jobs submitted since server start
|
Notify count
|
Number of notifications since server start
|
Error count
|
Number of server errors since server start
|
Channels SDE
|
Number of channels to control file. Entries are: In use channels/Open channels which may or may not be in use/Peak channels open/Parameter file maximum channels/Absolute maximum channels/Channel request backlog/Peak backlog
|
Channels HST
|
Number of channels to history file. Entries are: In use channels/Open channels which may or may not be in use/Peak channels open/Parameter file maximum channels/Absolute maximum channels/Channel request backlog/Peak backlog
|
QD Channels
|
Number of channels to queue file. Entries are: In use channels/Open channels which may or may not be in use/Peak channels open/Parameter file maximum channels/Absolute maximum channels/Channel request backlog/Peak backlog
|
Networks
|
Available network protocols
|
TCP/IP port id
|
TCP/IP port id number
|
Field |
Description |
QD Cache size |
Size of in memory copy of queue ?le |
Control ?ags |
Flag settings for control ?le |
Controlled queues |
Queues controlled by server |
Peak working set |
Memory used by peak working set |
Current working set |
Memory used by current working set |
Peak virtual size |
Virtual memory of peak set |
Current priority |
Current priority of SCHEDULE server |
Base priority |
Starting priority level of server |
Page faults |
Page faults in virtual memory |
Buffer I/O count |
Buffer I/O count |
Direct I/O count |
Direct I/O count |
Cpu time |
CPU time devoted to SCHEDULE activity |
Elapse time |
Elapsed time devoted to SCHEDULE activity |
Cluster alias |
Schedule alias |
Cluster lock group |
Cluster lock group |
File polling intrvl |
Interval between ?le polling events |
Disk polling intrvl |
Interval between disk polling events |
Delay polling intrvl |
Interval between delay polling events |
Stuck after intrvl |
Noti?cation interval after stuck in queue |
History active |
History active or not |
Notify queue |
Queue used for SCHEDULE noti?cations |
Notify user |
User for SCHEDULE noti?cations |
Notify ?le |
File written to with SCHEDULE noti?cations |
Notify enabled |
1 or 0 toggle to indicate if noti?cations take place |
Notify priority |
Overall priority of SCHEDULE noti?cations |
P queue purge intrvl |
How long to leave jobs in P queue |
Root dir owner |
Root directory owner |
protection |
Root directory protection |
COM ?le extension |
Extension for COM ?le created to run job |
Activity level |
Activity level of server from 0-7 |
Event file: jobs |
This is a parameter file setting, that indicates if event file logging of job messages is globally turned on/off. The parameter is JOB_EVENTFILE_ENABLED. The event file is written in the location /schedule_library/schN_server_<node>.evt. The messages are in a format that can be easily parsed by automated programs and utilities.
|
Event file: server |
This is a parameter file setting, that indicates if event file logging of server messages is globally turned on/off. The parameter is SERVER_EVENTFILE_ENABLED. The event file is written in the location /schedule_library/schN_server_<node>.evt. The messages are in a format that can be easily parsed by automated programs and utilities |
Event file: tz offset |
Each event in the event file is written with a UTC timestamp, and a localtime offset. The offset can be determined by the system, or it can be hard-coded the parameter file value EVENTFILE_TIMESTAMP_OFFSET. This value should be expressed as seconds east of GMT. For example, -28800 should be used for Pacific Standard Time. |
Event file: UTC adjust |
If the UTC time in the eventfile is incorrect, it can be modified with the parameter value EVENTFILE_UTCADJ_OFFSET. This indicates the number of seconds that will be added to the system UTC time. |
Event log: jobs |
This is a parameter file setting, that indicates if Windows event logging of jobs is globally turned on/off. The parameter is JOB_EVENTLOG_ENABLED. Note that a job's Notify property page has check boxes to turn on/off specific job events. |
Event log: server |
This is a parameter file setting , that indicates if Windows event logging of server messages is globally turned on/off. The parameter is SERVER_EVENTLOG_ENABLED. Additional filtering can be done with the parameter NTEVENTLOG. |
Event log: flags |
This is a parameter file flag setting, that indicates what level of server messages will be written to the event log. The parameter is NTEVENTLOG. Bit 1 enables Success messages. Bit 2 enables Error messages. Bit 3 enables warning messages. Bit 4 enables Informational messages. |
Journaling root |
Location of journaling file |
enabled |
Journaling enabled (1) or not enabled (0) |
Current time |
Current system time at time of display |
Examples
C:\> schedule server info
Version number = V6.0
Platform = Windows NT 4.0
Local node = windows_node
Database node = windows_node
Network nodes =
Defined cluster = ,windows_node
Active cluster = windows_node
NRQ frame count = 91618
active count = 9
available count = 134
dispatch count = 203096
dispatch rate = 103/555/6039
Active threads = 5
Submit count = 0
Notify count = 0
Error count = 0
Channels SDE = 0/0/5/16/60/0/0
HST = 0/0/2/10/20/0/0
QD = 1/1/20/36/60/0/0
Networks = Tcp/Ip
TCP/IP port id = 29347
QD Cache size = 139
Control flags = NoDECnetNetwork,NoCluster
Controlled queues = B,H,I,K,L,P
Peak working set = 36226
Current working set = 36226
Peak virtual size = 36226
Current priority = 0
Base priority = 0
Page faults = 381
Buffer I/O count = 1041
Direct I/O count = 1041
Cpu time = 000 00:06:04
Elapse time = 000 03:12:58
Cluster alias =
Cluster lock group = A,1
File polling intrvl = 300
Disk polling intrvl = 300
Delay polling intrvl = 300
Stuck after intrvl = 300
History active = 1
Notify queue =
user = root
file = schedule_notify.csh
enabled = 1
priority = 14
P queue purge intrvl = 64800
Root dir owner = 65540
protection = 0
COM file extension = .SCHEDULE_SH
Activity level = 0