SCHEDULE
Automated Job Submission System
Guide and Reference Manual

cd

Set default directory.
The cd command sets the default directory that will be used when issuing SCHEDULE commands

General Format

cd directory_name

Alternate
set default directory_name

Examples

#1
Schedule> cd /schedule/jobs/

hostname

Set the default node.
The hostname command sets (or displays) the default node for all subsequent SCHEDULE operations. To show the current node, use the cd command without the node designated.

General Format

hostname [new_node]

Alternate
set node new_node

Examples

#1
Schedule> hostname bootnode

pwd

Display the default directory.
The pwd command displays the current default directory for all subsequent SCHEDULE operations.

General Format

pwd

Alternate
show default

Examples

#1
Schedule> pwd /snow/job

show license

The SHOW LICENSE command displays the current SCHEDULE license information. If the license information is not present or up to date, the command may only be entered in full command mode and not prompt mode.

General Format

show license [-qualifier]

option summary

-server=server_name

Examples

#1
Schedule> show license PAS Information Company Name = ISE, Inc. Serial Number = L50075/WINNT/CENTER/20NOV2027/03EA/CNBVZKBPBB Controls Licensed Node = CENTER Licensed OS = WINNT Expiration = November 20, 2027, 0:00 Enabled = Client,Server,Network Bound to = Node,Product,OsInfo,CpuInfo License Status = Local system is licensed Local System Cpu Information = 2 AlphaServer 800 5/500 (1585) CPU1 OS Information = Windows NT 4.0 Network Adapter = Local Node = CENTER::, CENTER.I-S-E.COM

 
 
 
Schedule> show license 
 
PAS Information 
    Company Name              = ISE, Inc. 
    Serial Number             = L50075/WINNT/CENTER/20NOV2027/03EA/CNBVZKBPBB 
Controls 
    Licensed Node             = CENTER 
    Licensed OS               = WINNT 
    Expiration                = November 20, 2027,  0:00 
    Enabled                   = Client,Server,Network 
    Bound to                  = Node,Product,OsInfo,CpuInfo 
    License Status            = Local system is licensed 
Local System 
    Cpu Information           = 2 AlphaServer 800 5/500 (1585) CPU1 
    OS Information            = Windows NT 4.0 
    Network Adapter           = 
    Local Node                = CENTER::, CENTER.I-S-E.COM

Options

-server
Selects the server that the show license command will be performed on

show version

The SHOW VERSION command displays the current version information.

General Format

show version

Examples

#1
Schedule> show version SCHEDULE V6.0.11 - ISE, Inc. Licensed to ISE, INC. Released on August 1, 2001, 0:00 Copyright (c) 1991...2002 All rights reserved

source

Run SCHEDULE script from SCHEDULE. A SCHEDULE script is a list of SCHEDULE commands that will be executed when preceded by source .

General Format

Schedule> source schedule_script

Alternate
.script_file
@script_file

Examples

#1
Schedule> source schedule_library:schedule_standard_reports.schedule

verify

The [NO]VERIFY command is used to echo text from a SCHEDULE script to the display while the script is running. This command may be included within the file. The NOVERIFY command will end the verify process.

General Format

Schedule> verify

Examples

#1
Schedule> verify Schedule> source schedule_library:schedule_standard_reports.schedule Schedule> noverify

version

The VERSION command displays the current version information.

General Format

version

Examples

#1
Schedule> version SCHEDULE V7.0.11 - ISE, Inc. Licensed to ISE, INC. Released on August 1, 2006, 0:00 Copyright (c) 1991...2006 All rights reserved

Chapter 13
SERVER control

The SERVER process performs all scheduling activity, network communications and file I/O activity on the behalf of the user. The following commands can be used to affect its operation.

SERVER command Definition

server info Display detailed information about the current server process

server stop stop server or network operations

server start start up network operations

server restart restart the server process

server proxy_reset clear out the proxy access cache

SERVER command	Definition
server info	Display detailed information about the current server process
server stop	stop server or network operations
server start	start up network operations
server restart	restart the server process
server proxy_reset	clear out the proxy access cache

These commands are normally used only by the system manager. OPER privilege is required to execute these commands.

info

Display detailed information about the current server process. The following table describes the output fields of the server info display.

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 counts

Active threads Number of active threads Active Terminating Threads/Idle Terminating Threads/Allowed (retained) Idle Terminating Threads /Soft Max Terminating Threads/Hard Max Terminating Threads/BackLog Terminating Threads /Peak BackLog Terminating Threads/Active Worker Threads/Idle Worker Threads /Allocated to (retained) IO Worker Threads/Soft Max Worker Threads /Hard Max Worker Threads /BackLog Worker Threads/Peak BackLog Worker Threads/Worker Thread to Terminating Thread Socket Thread Over Flow

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

QD Cache size Size of in memory copy of queue file

Control flags Flag settings for control file

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 file polling events

Disk polling intrvl Interval between disk polling events

Delay polling intrvl Interval between delay polling events

Stuck after intrvl Notification interval after stuck in queue

History active History active or not

Notify queue Queue used for SCHEDULE notifications

Notify user User for SCHEDULE notifications

Notify file File written to with SCHEDULE notifications

Notify enabled 1 or 0 toggle to indicate if notifications take place

Notify priority Overall priority of SCHEDULE notifications

P queue purge intrvl How long to leave jobs in P queue

Root dir owner Root directory owner

protection Root directory protection

COM file extension Extension for COM file 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

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 counts
Active threads	Number of active threads Active Terminating Threads/Idle Terminating Threads/Allowed (retained) Idle Terminating Threads /Soft Max Terminating Threads/Hard Max Terminating Threads/BackLog Terminating Threads /Peak BackLog Terminating Threads/Active Worker Threads/Idle Worker Threads /Allocated to (retained) IO Worker Threads/Soft Max Worker Threads /Hard Max Worker Threads /BackLog Worker Threads/Peak BackLog Worker Threads/Worker Thread to Terminating Thread Socket Thread Over Flow
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
QD Cache size	Size of in memory copy of queue file
Control flags	Flag settings for control file
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 file polling events
Disk polling intrvl	Interval between disk polling events
Delay polling intrvl	Interval between delay polling events
Stuck after intrvl	Notification interval after stuck in queue
History active	History active or not
Notify queue	Queue used for SCHEDULE notifications
Notify user	User for SCHEDULE notifications
Notify file	File written to with SCHEDULE notifications
Notify enabled	1 or 0 toggle to indicate if notifications take place
Notify priority	Overall priority of SCHEDULE notifications
P queue purge intrvl	How long to leave jobs in P queue
Root dir owner	Root directory owner
protection	Root directory protection
COM file extension	Extension for COM file 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

General format

server info

Examples

#1
Schedule> server info Version number = V7.0.11 Platform = Digital UNIX OSF1 V4.0, DEC 3000 - M300X Local node = dus Database node = dus Network nodes = Defined cluster = ,dus Active cluster = dus NRQ frame count = 1531 active count = 5 available count = 135 dispatch count = 2993 dispatch rate = 1/423/1195 Active threads = 5 Submit count = 0 Notify count = 0 Error count = 0 Channels SDE = 0/1/1/16/60/0/0 HST = 0/0/0/0/0/0/0 QD = 1/20/20/36/60/0/0 Networks = Tcp/Ip TCP/IP port id = 29345 QD Cache size = 0 Control flags = NoDECnetNetwork,NoCluster Controlled queues = B,H,I,K,L,P Peak working set = 1544 Current working set = 17273 Peak virtual size = 1360144 Current priority = 0 Base priority = 0 Page faults = 13 Buffer I/O count = 398 Direct I/O count = 398 Cpu time = 000 00:00:13 Elapse time = 000 00:09:54 Cluster alias = Cluster lock group = A,0 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_library/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

 
 
 
 
 
    Schedule> server info 
 
    Version number       = V7.0.11 
    Platform             = Digital UNIX OSF1 V4.0, DEC 3000 - M300X 
    Local node           = dus 
    Database node        = dus 
    Network nodes        = 
    Defined cluster      = ,dus 
    Active cluster       = dus 
    NRQ frame count      = 1531 
        active count     = 5 
        available count  = 135 
        dispatch count   = 2993 
        dispatch rate    = 1/423/1195 
    Active threads       = 5 
    Submit count         = 0 
    Notify count         = 0 
    Error count          = 0 
    Channels SDE         = 0/1/1/16/60/0/0 
             HST         = 0/0/0/0/0/0/0 
             QD          = 1/20/20/36/60/0/0 
    Networks             = Tcp/Ip 
    TCP/IP port id       = 29345 
    QD Cache size        = 0 
    Control flags        = NoDECnetNetwork,NoCluster 
    Controlled queues    = B,H,I,K,L,P 
    Peak working set     = 1544 
    Current working set  = 17273 
    Peak virtual size    = 1360144 
    Current priority     = 0 
    Base priority        = 0 
    Page faults          = 13 
    Buffer I/O count     = 398 
    Direct I/O count     = 398 
    Cpu time             = 000 00:00:13           
    Elapse time          = 000 00:09:54           
    Cluster alias        = 
    Cluster lock group   = A,0 
    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_library/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

Contents

Index

SCHEDULE Automated Job Submission System Guide and Reference Manual

cd

General Format

cd directory_name

Examples

hostname

General Format

hostname [new_node]

Examples

pwd

General Format

pwd

Examples

show license

General Format

show license [-qualifier]

option summary

Examples

Options

-server

show version

General Format

show version

Examples

source

General Format

Schedule> source schedule_script

Examples

verify

General Format

Schedule> verify

Examples

version

General Format

version

Examples

Chapter 13SERVER control

info

General format

server info

Examples

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

Chapter 13
SERVER control