Help for Supervisor Version 64.640.04
SUPERVISOR has Help pages for all commands and many other keywords
and attributes. The syntax of the HELP command is:
I-+-----------+-- HELP --+--------------------------------------+-I
+-- PRINT --+ |-- = ---------------------------------|
-- |-- ATTR -- <pattern> --+--------------|
| --- +- : <object> -|
| |
|-- CONTEXT ---------------------------|
+-- <command> --+----------------------|
+-- <sub-category> ----+
Examples: HELP FP HELP JAM WAIT
HELP CONTEXT HELP ATT SERIALNO
HELP ATT =MI=:LOG PRINT HELP =
Commands from Supervisor Windows do not need a TT prefix. An ODT
prefix must be used where for MCP commands which have a matching
Supervisor command. Ex. ODT DO for diagnostic options.
Currently, information is available for the following commands, with
their synonyms, if applicable, shown in parentheses.
Any command preceded by an asterisk (*), for example FP, may not be
accessed by sites that do not have a full Supervisor licence key.
Additional topics are referred to under the relevant <command>.
Any command preceded by an exclamation mark(!) matches a Unisys ODT
command. When entered from a Supervisor Window the prefix ODT must
be used to pass the command to the MCP instead of Supervisor.
OK, PR and QUIT only need a prefix if not preceeded by a mix number.
The HELP pages for internal SUPERVISOR commands may be displayed or
printed using the '=' variant as follows:
HELP =
or
PRINT HELP =
Note: Only Supervisor commands will be shown - Tape Library (TP)
commands will be excluded.
HELP for Attributes
HELP CONTEXT gives all the currently available objects that can be
used in SUPERVISOR. All OPAL DEFines have a object context, which
specifies what attributes can be seen.
HELP ATTR will call on OPAL to look up the specified attribute.
If the <pattern> is a simple identifier, all the information for the
requested attribute is displayed.
If the <pattern> contains wild card characters (=?@&#), the
directory entries are given for all matches.
The search can be restricted to the attributes of a particular
object by using the :<object> modifier, e.g.
All attributes of the MX object are given by: HELP ATT =:MX
For a full list of all available attributes use PRINT ATT.
Examples: HELP ATT CPMIDLE
HELP ATT =TL?=:TAPEDB
ACCESS Command
The ACCESS command allows the password associated with one
operator accesscode to be changed.
I-- ACCESS -- <accesscode> -------------------- <newpassword> --I
|- / <password> -|
-
<accesscode> must be a valid operator accesscode, known to
SUPERVISOR because of its appearance in the ACCESSCODELIST of its
usercode. <password> must appear if a password is currently
defined for <accesscode>. <newpassword> will become the only
valid password corresponding to <accesscode>.
AF Command
-- AFTER -+-----+-+-----+--- <time qual> --- <text> --------+--|
-- | | | | |
+- * -+ +- + -+ |
| | |
| +- - ----- <time qual> -+-- <text> -------+
| | |
| +-- @ <integer> --+
| |
+- ? ------------- <time qual> ----+---------+----+
| |
+- DEBUG -+
The AFTER command causes SUPERVISOR to place into or delete from
its schedule, the activity defined by <text>; or to display all
scheduled activities at a given time or times.
The AFTER command with a '-', implies that SUPERVISOR should
delete from the list of activities scheduled at each of the
specified times, any activity whose defining text exactly matches
that supplied in the current command.
For deletion, <text> may also have the form '@ <integer>' or '@='.
The <integer> implies the entry at the first valid time. '@=' may
only be used with a FOR supplied PU, and not with time ranges. It
can also be used with 'ON DATE <' form to get rid of old entries.
The appearance of a '+' implies that an activity should be
scheduled for each of the specified <times> if and only if, the
activity specified by <text> is not already scheduled at that time.
In TRIM, <text> may only be a TRIM operator command or a ??RUN.
The use of '*' before any AFTER + or AFTER - command causes that
command to be simulated. As with the normal command, the relevant
response wil be returned but prefixed by 'WOULD BE' or 'WOULD NOT
BE'.
The appearance of a '?' denotes a request by an operator, to
display upon the originating console or terminal, all activities
scheduled for each of the specified times. DEBUG causes the display
of internal schedule table data.
<time qualification> is described in the SUPERVISOR manual and also
its simpler counterpart in the TRIM manual.
Functionally, the effect of scheduling an activity is the same
as if, at the time or times specified by the <time qualifications>,
the <text> had been entered directly from the same origin.
Note that 4-digit years are handled up to the year 2035.
If <text> is a SUPERVISOR command, then it will be acted upon by
SUPERVISOR, if not it will be passed to the system (to the
Controller). If it is not a valid ODT command, it will be rejected
by Controller at that time.
An AFTER Command may be preceded by a FOR qualifier, or the FOR
qualifier may follow <time qualifications>. The <text> defining the
activity to be scheduled may itself be an AFTER command, as shown
in the examples, provided it is preceded by a 'TT' as the first
part of <text>.
The appearance of LOOKUP functions within <text>, may cause
SUPERVISOR to substitute a list of mix numbers or unit numbers for
portions of <text>.
COMMAND Command
The DO Command causes SUPERVISOR to begin execution of the
statements of an ODT Sequence.
-+- COMMAND -+----------+-+-----+---- <COM name> -- <params>---+
| | | | |
+ & DEBUG -+ +- + -+ |
| | |
+- - -+-+-- <COM name> ----+--------+
| |
+-- # <Slotno> -----+
The COM command permits execution of OPAL scripts, whose program
type is COMMAND, by assigning short-cuts for commands from
SUPERVISOR windows. These short-cuts names (specified by <COM name>)
can replace or extend existing Unisys ODT comamnds if desired.
To execute a COMMAND Sequence it must have been previously entered
by the DEFINE command (HELP DEFINE ODTSEQUENCE). If the type of the
COMMAND sequence is MX, then <params> must be a <mix number list>.
If it is of type PER,then <parameters> must be a <unit number list>.
If the COMMAND Sequence is of type SYSTEM, <parameter list> must be
empty. If of type MSG, <parameters> can be any text or empty and it
will be placed into the MSGPARAM and TEXT attributes. If the type
is TAPELABEL, <parameters> must be a <serial number list>.
Any active COMMAND may be terminated by using the '-' modifier
before its name; alternatively, where multiple COMMANDs with the
same name arec active, individual programs can be terminated by the
#<slotno> variant.
Execution of the COMMAND Sequence is subject to the limit on the
number of WHENS (HELP USE WHENS), if the number of active WHENS is
high, execution of the COMAMND Sequence will be deferred. A WHEN ?
response will show the status as QUEUED.
Examples:
TT COM MSGTEST
TT COM& DEBUG MSGTEST THIS IS A MESSAGE CONTEXT
TT COM - MSGTEST
TT COM - #4
DEBUG Command
DEBUG performs debugging functions for SUPERVISOR.
I-- DEBUG --+--+-----+---+------------------+---+---------I
| |- + -| |---<--- , ---<----| |
| +- - -+ +-- <bit number> --+ |
| |
+--------- PRINT -------------------+
+--------- DUMP ------+------------+
| +--- ALL ----+
+--------- CLOSE -------------------+
The response to the DEBUG command explains briefly the function of
each <bit number>. The functions of any bit may change without
notice. In normal use all options should be reset.
DEBUG CLOSE closes SUPERVISOR's TASKFILE and issues print request.
DEBUG PRINT is an synonym for DEBUG CLOSE.
DEBUG DUMP takes a programdump of SUPERVISOR, closes the taskfile,
and issues a print request. The 'ALL' modifer takes a full
programdump will all relevant options set.
DEFINE Command
The DEFINE command is the means to enter descriptions of SITUATIONS,
ODTSEQUENCES, DISPLAYS and COMMANDS into SUPERVISOR. It may also be
used to interrogate the Directory of OPAL programs.
More On-Line information is available by entering HELP DEF ODTS or
HELP DEF DISP respectively, but the manual should be consulted for
a fuller explanation.
The following pages describe the variants of the DEFINE Command.
DEFINE ? : Interrogating the OPAL Directory
+-- COMMAND -----+
| --- |
|-- DEFINE ------|
| --- |
|-- DISPLAY -----|
| ---- |
I-- DEFINE ------- ? -----|-- SITUATION ---|--------------------I
--- | ---- | |- <pattern> -|
|-- ODTSEQUENCE -|
| ---- |
|-- MEMO --------|
If no <pattern> is supplied DEFINE ? requests all identifiers of the
kind given (ODTSequence,SITUation,DISPlay, COMmand, MEMO) or all
kinds if DEF is specified. If a pattern is supplied and contains
any wild card characters only identifiers matching the wild card
specification will be returned.
DEFINE ? : Interrogating the OPAL Directory
If the <pattern> is a simple identifier and a kind is specified the
the corresponding definition will be returned in a form suitable for
modification.
A variant of the command shown below is used to return a previously
entered Inline Opal:-
I-- DEFINE ---- ? ----- INLINE -----I
If no Inline Opal has been defined an error message will be output
otherwise the Opal will be returned as originally entered.
DEFINE - : Deleting a Program or Memo from the Directory
+- COMMAND -----+
| --- |
|- DISPLAY -----|
| ---- |
I- DEFINE --- - ---|- SITUATION ---|----- <id> --------I
--- - | ---- |
|- ODTSEQUENCE -|
| ---- |
+- MEMO --------+
DEFINE - deletes a definition from the dictionary.
DEFINE + or *: Creating or Modifying an OPAL Program
+- COMMAND -----+
| --- |
|- DISPLAY -----|
| ---- |
I- DEFINE ---------|- SITUATION ---|- <id> --------- <definition> -I
--- |- + -| | ---- | |-<op>-|| |
|- * -| |- ODTSEQUENCE -| |- FROM <file>-|
| ---- |
+- MEMO --------+
DEFINE + adds a definition to the dictionary, or alters an existing
definition. <op> is a context and/or RE/SET LIST/CODE. See the
following section describing use of DEFINE + to save InLine Opals.
If the routine being defined is in use in any active slots Then the
new code will Not be used until that slot is resarted or Supervisor
is restarted. If the Supervisor Option NODEFACTIVE is set and the
routine is in use Then the Define command is rejected.
DEFINE * is used to redefine routines expected to be active. For
SITUATIONs or routines linked to sitiations the new code will be
used on the next Evaluation of the Situ or entry to the ODTS or
Display. Routines Not linked to a SITUATION will behave like
DEFINE + except that the NODEFACTIVE option is ignored.
DEFINE followed by a keyword (ODTS, DISP or SITU) adds a new
definition to the dictionary, if the <identifier> already exists,
the command will be rejected.
DEFINE + : Saving INLINE OPAL Programs
+- COMMAND -----+
| --- |
|- DISPLAY -----|
| ---- |
I- DEFINE ---------|- SITUATION ---|- <id> -- INLINE --I
--- |- + -| | ---- |
|- ODTSEQUENCE -|
| ---- |
|- DEFINE ------|
---
This variant of the DEFINE + command enables a previously entered
InLine Opal to be saved in the Supervisor SCHEDULE. The command may
be used to selectively save part or all of an InLine Opal eg. if the
Opal consisted of a SITUATION and an ODTSEQUENCE the ODTSEQUENCE may
be saved without the SITUATION by using the ODTS variant. If both
were to be saved in one command the DEFINE variant should be used.
DELINK Command
------ DELINK --------+--- COMS -------------+--------------------|
|--- DSILIB -----------|
|--- FLEXLIB ----------|
|--- JOBFORMATTER -----|
|--- MAILLIB ----------|
|--- METANAPLIB -------|
|--- OPALTAPELIB -----|
|--- OPALUSERLIB -----|
|--- PRINTSUPPORT -----|
+--- SURELIB ----------+
DELINK allows SUPERVISOR to delink dynamically from a variety of
SL-ed libraries without requiring a TT QUIT. If the de-linking is
successful, SUPERVISOR will display
SUPERVISOR HAS DELINKED FROM THIS LIBRARY
or
SUPERVISOR IS NOT CURRENTLY LINKED TO THIS LIBRARY
if SUPERVISOR did not currently have a linkage to the relevant
library. Note that, because the GRINDER stack is now responsible
for handling the delinking of METANAPLIB, the response will
always be the successful DELINKED message.
DIR Command
SUPERVISOR has Help pages for all commands and many other keywords
and attributes. The syntax of the HELP command is:
I-+-----------+-- HELP --+--------------------------------------+-I
+-- PRINT --+ |-- = ---------------------------------|
-- |-- ATTR -- <pattern> --+--------------|
| --- +- : <object> -|
| |
|-- CONTEXT ---------------------------|
+-- <command> --+----------------------|
+-- <sub-category> ----+
Examples: HELP FP HELP JAM WAIT
HELP CONTEXT HELP ATT SERIALNO
HELP ATT =MI=:LOG PRINT HELP =
Commands from Supervisor Windows do not need a TT prefix. An ODT
prefix must be used where for MCP commands which have a matching
Supervisor command. Ex. ODT DO for diagnostic options.
Currently, information is available for the following commands, with
their synonyms, if applicable, shown in parentheses.
ACCESS AF (AFTER) COMMAND DEBUG DEFINE
DELINK !DIR(TDIR) DO (TEST) EH ENTER
EV (EVAL) FOR *FP *!HO *HOLIDAY
!HS INLINE *INPUT JAM !LOG
LR *LU MAIL *MEMO NS
!OK *PB *PDT !PR (PRINT) !QUIT
RL (RELOAD) !REMOTESPO *!RESTRICT !SV (SAVE) *SHIFT
!SHOW SLOT SO SS *SYSLOG
TK *!TL TP USE VIA
*VL WINDOW WHEN (ONCE) WORKDAYS WS
Any command preceded by an asterisk (*), for example FP, may not be
accessed by sites that do not have a full Supervisor licence key.
Additional topics are referred to under the relevant <command>.
Any command preceded by an exclamation mark(!) matches a Unisys ODT
command. When entered from a Supervisor Window the prefix ODT must
be used to pass the command to the MCP instead of Supervisor.
OK, PR and QUIT only need a prefix if not preceeded by a mix number.
The HELP pages for internal SUPERVISOR commands may be displayed or
printed using the '=' variant as follows:
HELP =
or
PRINT HELP =
Note: Only Supervisor commands will be shown - Tape Library (TP)
commands will be excluded.
HELP for Attributes
HELP CONTEXT gives all the currently available objects that can be
used in SUPERVISOR. All OPAL DEFines have a object context, which
specifies what attributes can be seen.
HELP ATTR will call on OPAL to look up the specified attribute.
If the <pattern> is a simple identifier, all the information for the
requested attribute is displayed.
If the <pattern> contains wild card characters (=?@&#), the
directory entries are given for all matches.
The search can be restricted to the attributes of a particular
object by using the :<object> modifier, e.g.
All attributes of the MX object are given by: HELP ATT =:MX
For a full list of all available attributes use PRINT ATT.
Examples: HELP ATT CPMIDLE
HELP ATT =TL?=:TAPEDB
DO Command
The DO Command causes SUPERVISOR to begin execution of the
statements of an ODT Sequence.
To use the MCP Diagnostic Options command from a Supervisor
Window use ODT DO.
-+- TEST -+-+-----------+-+-----+-- <ODTS name> -+-------------+->
+- DO ---+ +- & DEBUG -+ +- + -+ +- [<range>] -+
+- & PRINT -+ +- - -+-+-- <ODTS name> ----+---------->
+-- # <Slotno> -----+
>-+- <params> ------------+---+---I
+- <file or directory> -+ |
>-----------------------------+
The ODT Sequence to be done must have been previously defined by
means of the DEFINE command (HELP DEFINE ODTSEQUENCE). If the type
of the ODT Sequence is MX, then <parameters> must be a <mix number
list>. If it is of type PER,then <parameters> must be a <unit number
list>. If the ODT Sequence is of type SYSTEM, <parameter list>
must be empty. If of type MSG, <parameters> can be any text or empty
and it will be placed into the MSGPARAM and TEXT attributes. If the
type is TAPELABEL, <parameters> must be a <serial number list>.
Any active DO may be terminated by using the '-' modifier before
its name; alternatively, where multiple DOs with the same name are
running, individual programs can be terminated by using slot number.
Execution of the ODT Sequence is subject the limit on the number
of WHENS (HELP USE WHENS), if the number of active WHENS is too
great, execution of the ODT Sequence will be deferred. A WHEN ?
response will show the status as QUEUED.
TEST is identical to DO except that all actions such as TAPERECORD
and ODT statements are turned into DISPLAY statements. In general,
TEST may appear wherever DO can, with the same effect.
The '& DEBUG' modifier causes tracing of code execution by the OPAL
machine to be generated to a print file. The print file is released
when the WHEN slot is terminated. The '& PRINT' forces all Opal SHOW
statements to be converted instead to PRINT statements directing
screen output to printer.
<range>: --+------------------+-- <integer>
+-- <integer> - ---+
Only valid for PD context. Enables the User to specify the
maximum number of times that ODTSequence or DISPlay can invoked
before being terminated. (i.e. The number of files processed)
and optionally that some entries should be skipped.
<file or directory>:
Is only required for PD contexts and specifies the files or
directory to be scanned. For licensed Flex customers :Flat :Fast
Or :Lin can be specified
Examples:
TT DO MSGTEST
TT DO FILESCAN [10-19] MYFILES/= ON PACK:FL
TT DO& DEBUG MSGTEST THIS IS A MESSAGE CONTEXT
TT TEST MIXREQUEST 12345
TT DO - MSGTEST
TT DO - #4
EH Command
The EH Command, requests SUPERVISOR to repeat the last output
it made to the requesting terminal.
I--- EH ---I
ENTER Command
The ENTER command is used to give SUPERVISOR input from a
symbolic disk file.
+--- AFTER ------+
| |
+--- SCHEDULE ---+
| |
+--- WHEN -------|
| |
I-- ENTER -+--------+----------------+---------- FROM -- <file> --I
| | | |
+--- DEF --- + +-<pattern list>--+
| |
+--- ODTS ---+
| |
+--- SITU ---+
| |
+--- DISP ---+
| |
+--- MEMO ---+
Supervisor looks for the file with the specified title, and builds
input commands by concatenating records until a record with a '\'
character is seen (commonly known as tilde). The response to each
command is printed along with the command itself.
The ENTER command can selectively load 'groups' of OPAL programs
or WHENS from the specified file and filter them according to name
and/or program type. The usual wildcard syntax can be used:
TT ENTER ODTS EXAMPLE= FROM (META)ENTER/OPALS ON PACK
Here, only OPALs of type ODTSequence and names beginning with the
root EXAMPLE will be compiled, all other programs will be ignored.
A <pattern list> consists of an optional list of patterns,
delimited by commas, allowing multiple programs to be ENTER'ed from
the same file. Normal rules apply for <pattern> definitions.
Example:
TT ENTER DEF TEST_=,HL,EX_= FROM MIXED/DEFINES
An important function of this command is to rebuild a schedule
from a symbolic file prepared with CANDE, but it is also
the inverse of the SAVE SCHEDULE AS variant of SUPERVISOR's SAVE
command (HELP SAVE SCHEDULE). Any SUPERVISOR command may be
present in this file.
EV Command
The EVal command allows an operator to activate and deactivate
situations, and to interrogate which situations are currently running.
Also see TT HELP WHEN.
Option 1 : EVALuate a situation.
I-- EVal -+-----------+-- <situ> --+------------------------+--->>
+- & DEBUG -+ +--- [ <eval limits> ] --+
>>---+-----------------------------------------------------+->>
+- DO----+---- <odts> -+--+---------------------------+
+- TEST -+ | +- [ -- <max entries> -- ] -+
+- DISPlay -+- <disp> -+
+- PRint ---+
>>---+-------------------------+-+-------------------------+--I
+- SORT -+-----+- <disp> -+ +-- <file or directory> --+
+- + -+
+- - -+
-
<eval limits>:
I---+---------------+--------------------------------------->>
+- <max evals> -+
+<------------------------------------------------------------+
>>-+-------------------------------------------------------------+
+-/1\--- @ --+- <range specs> --------------------------------+
+- <AF range specs> -----------------------------+
+-/1\-+- LOGNO ----- <integer> -------------------------------+
| +- TITLE ----- <file title> ----------------------------+
| |
+-/1\--- MAXLogs --- <integer> -------------------------------+
+-/1\-+- JOB -----+- <integer> -+-----------------------------+
+- SESSion -+ +- - -- <integer> ------------+
+- TASK ----+
+- MIX -----+
<range specs>:
--+-- <datetime> ---+--------------------------+----------------+
| +-- TO ---+-- <datetime> --+ |
| +-- - --+ |
+-- BEFORE -- <datetime> -----+-------------------------+-----+
| +-- AFter -- <datetime> --+ |
+-- BACK <integer> -+----------+-+----------------------------+
+- DAYs ---+ +- FOR <integer> -+----------|
+- HOURs --+ +- DAYS ---+
+- MINutes + +- HOURs --+
+- MINutes +
+- SEConds +
Allows the user to specify date and time ranges for access to
system SUMLOGs using LOG-based Opal programs. The BEFORE and AFTER
keywords provide an alternative way of providing a date-time range.
The BACK modifier allows an AFTER time to be specified by assigning
a time difference and an optional duration using FOR.
<AF range specs>:
--+-- <date> ------+-------------------- -+-----------------+
| +-- TO ---+-- <date> --+ |
| +-- - --+ |
+-- <time> -----------------------------+-----------------+
+-- TO ---+-- <time> --+
+-- - --+
Allows the user to limit the scope of an After Eval.
<datetime>:
+<-------------------------------------------------------+
I--+--/1\------ <date> -------------------------------------+----I
+--/1*\--+-- <time> -------------------------------------+
+-- <hour> -- : -- <minute> -+------------------+
+- : -- <second> --+
<max evals>: --+------------------+-- <integer> -----------------
+-- <integer> - ---+
Enables the User to specify the maximum number of times the
Situation will be evaluated before it is terminated and
optionally that some evals should be skipped
[5-10] indicates that the first 4 objects should be ignored and
that the eval should stop after 10 objects.(4 skipped + 6 evals)
<max entries>: --+------------------+-- <integer> ----------------
+-- <integer> - ---+
Enables the User to specify the maximum number of times that
ODTSequence or DISPlay can invoked before the WHEN is
terminated and optionally that some entries should be skipped.
SORT:
Sorts the output, by default descending, with a key given by the
specified Display. Note that the Display key must not exceed
255 bytes or the EVAL will fail.
<file or directory>:
Is only required for PD contexts and specifies the files or
directory to be scanned. For licensed Flex customers, :Flat,
:Fast or :Lin can be specified.
Option 2 : De-activate a situation.
I--- EVal --- <situ> -+- TEST +-+-------------------+--I
+- DO --+ +--- - -- <odts> ---+
+- DISPlay -+-+---------------+
+- PRint ---+ +- - -- <disp> -+
Option 3 : Interrogate active situations.
I--- EVal --- ? -+-----------------+--I
+--- <pattern> ---+
+- [ <Slot No> ] -+
+-- # <Slot No> --+
The EVal command alters or interrogates the state of
situations. A situation is defined by means of the DEFINE command
and describes a combination of values. Once defined, a situation
is no more than an entry in SUPERVISOR's SITUATION Dictionary. To
start monitoring for the combination of values, it is necessary
to activate the situation. The simplest case is with the variant
of EV which does not specify an action. The sitaution is EValuated
and the requesting terminal is notified of the response.
An example response for Situations of type MX would be :
SUPERVISOR/<situation name>:RETURNED TRUE FOR MX <mix list>
or
SUPERVISOR/<situation name>:RETURNED FALSE
The response is returned to the requesting terminal and is
displayed and is also returned if action variant of EV is used.
In this case for each entity that the Situation returns TRUE, the
action is performed. EV means activate the situation and perform
the associated test once, terminating regardless of the result.
Option 2 is used to deactivate a running program. The command does
not have to match the one used to initiate the program.
Option 3 is the SUPERVISOR equivalent of MX for OPAL programs.
FOR Command
The FOR command is used to 'lock' scheduled activities with a
usercode.
I----- FOR ----- <usercode> / <password> -----I
-
The FOR modifier is used to specify the usercode associated
with a scheduled activity.
If an activity is scheduled with a FOR modifier, SUPERVISOR
will check that the usercode, and the associated password if
supplied, is a valid usercode. The usercode, but not the
password, is retained with the scheduled activity and and when
the activity is performed the usercode is again checked. If valid,
the command is executed; in the case of ODT commands with the
usercode in the same way the session usercode is passed with a ?
command from CANDE. All jobs started in this way, will run under
the usercode specified at the time of entry. If the usercode is
found to be no longer valid, the activity is not performed, and
the postscript of the activity is flagged as 'BADUSERCODE'.
Deletion of a scheduled activity with an associated usercode
will only be accepted if a FOR modifier with the same usercode,
and any password matching the usercode is supplied.
One exception is that a privileged user can cancel any
scheduled activity by specifying first his usercode and a valid
password and secondly the associated usercode of the activity
without password.
Examples:
User FRED schedules a startjob
FOR FRED/PASS1 AFTER 1230 STARTJOB TEST
which FRED could cancel any time by
FOR FRED/PASS2 AF - 1230 STARTJOB TEST
provided PASS2 is a password for his usercode.
A privileged user PRIV could cancel the activity without
knowledge of usercode FRED's password with
FOR PRIV/SECRET FOR FRED AF - 1230 STARTJOB TEST
FP Command
The FP Command displays disk statistics to assist with File Placement.
I-- FP --------------------------+----------------------------+-I
+-- <pattern> --+ | +-- SUMMARY --+ |
| |-- IO --------| |
+-- : ----+-- MAXAVAIL --+---+
| --- > chnksz --- |
+<--------------------+
By default, the report lists all disks, with a summary for each
family, and includes the numbers of sectors in available areas more
than 504 sectors. Enter the <pattern> to restrict
the report to certain families. Enter :SUMMARY to list the summary
of each family only. Enter :>chnksz to report based on a limit
other than 504. Enter :MAXAVAIL to report the largest available
area instead. Enter :IO to report I/O statistics information.
FP may not be used in an AF command or in TAPECONTROL.
Examples: std report, printed: PR FP
work families (large areasize) FP WORK= : >1000
whole families only: FP:SUM
HO Command
To use the MCP HOLD command from a Supervisor Window use HOLD or
ODT HO.
HO gives a report on the files with headers open on a family.
I-- HO -- <familyname> -----------------------------------------I
| | | |
|- # <familyindex> -| |- <File Spec> -|
If a <familyindex> is specified, only the files which have active
rows on that family index will be shown. These are the only files
which are counted in the OPENCOUNT for a non-BASEPACK. However, if
no <familyindex> is given, all the files are shown. Note that HO
will show the SYSTEMDIRECTORY, which is not counted in the MCP's
OPENCOUNT. HO may not be used in TAPECONTROL or in an AF command.
If a <File Spec> is entered, only files matching this specification
will be shown. The file specification may include a wildcard eg.
HO DISK *SYSTEM=
If a specific file name is entered the Mix numbers of Tasks using
the file will be displayed.
HOLIDAY Command
Syntax:
I--- HOLIDAYS ---------- ? ------------------------------I
------- | |
|------------- <gregorian date> ------|
| | | | | |
| |- - -| |- <day and month> ----| |
| - |
|---<----<- , --<---<---<---<---<---|
-
Semantics:
The Holiday Command designates a date as a holiday, or deletes
a date from the list of holidays. The HOLIDAY ? variant displays a
list of defined holidays on the requesting terminal.
Holidays occur in two types, those where the date of the
holiday varies within each year (for example Easter) and those which
always occur on a fixed day of a fixed month (for example
Christmas). The Holiday command accepts either type. Movable
holidays must be defined by giving the georgian date (in the form
DD/MM/YY) for each year. Fixed holidays may be defined by entering
the day and the month (in the form DD/MM), in this case they are
recognised as holidays regardless of the year.
Examples:
HOLIDAY 25/12
HOLIDAY - 01/01,09/04/82
HOLIDAY 04/07,25/12,09/04/82
Pragmatics:
The list of holidays is held in the Schedule file and is thus
backed up by a SAVE command, and restored with a RL command.
Should todays date be entered as a holiday, any activities
flagged with the EXCEPT HOLIDAYS flag, will be omitted for the rest
of the day. Otherwise the test for a holiday is made at midnight.
HS Command
HS is analogous to the system HS for SUPERVISOR.
To use the System HS from a Supervisor window use ODT HS
I----- HS ---------------------------I
|-- + ----|
|-- - ----|
The HS command interrogates, sets or resets the Hold Schedule Flag.
When the Hold Schedule Flag is set, all scheduled activities will
not be performed without operator intervention. Depending on the
value of USE.. BACKTRACK, Supervisor will handle held activities
similar to BACKTRACKSCHEDULE. Hold Schedule will remain in force
across restarts and halt-loads but, if an HS has been in force for
more than 24 hours and a restart occurs, the HS will be cancelled
automatically.
INLINE Command
The INLINE command allows the User to recall a previously entered
InLine Opal program.
I----- INLINE -- ? ------------------I
If no Opal Program has previously been entered an error message will
be displayed.
NOTE: This command will de-implemented, an InLine Opal may now be
displayed by entering :-
I---- DEFINE --- ? --- INLINE ----I
INPUT Command
The INPUT command takes the contents of a disk file and passes
them to the system Controller, where they are intepreted as ODT
commands.
I--- INPUT --- <file title> ---I
Upon receipt of an INPUT command, SUPERVISOR processes an
independent stack with the name 'LOAD', which opens the file
specified by <file title> and begins reading records. Each record
is scanned, looking for the \ character and the concatenated records
are passed as one ODT
command, via the DCKEYIN intrinsics, to Controller. The command
and its response are printed on a printer file.
The file can be conveniently prepared with CANDE, and may be
of any convenient symbolic filekind, LOAD assembles commands from
columns 1-80 of files of filekind JOBSYMBOL or CDATA and columns
1-72 of all others.
No attempt is made to check that the file actually exists, it
is explicitly opened. Any NO FILE or similar conditions will
cause SUPERVISOR to hang, the normal operator actions may be
taken. This action is deliberate, as it is anticipated that that
LOAD will be used for queue setup, system option initialisation
and similar purposes where non-performance could be disastrous.
It is important to note that no particular usercode or family is
assumed, the title of the file must be specified in full.
The LOAD command may be the subject of an AFTER command, it
will not be accepted from a restricted terminal.
JAM Command
JAM runs the program METALOGIC/JAMPACK whose function is to clear
contiguous areas on a pack.
I--- JAMPACK --- <packname> --------------------------------------I
--- | | | | |
| |- # <fam.index>-| |----- <target> -|
| | | |
| |- < | |
| |
|--- HELP -----------------------------------------|
<packname> : is the family to work on.
<fam. index> : restricts JAMPACK to a single family index
<target> : is the number of segments to try and get as a contiguous
amount.
< : this option says that the reserve should be first be checked
by simulation. This can be expensive but gives a surer result.
If the simulation fails, JAMPACK will search for the closest
amount which can be found.
If the target is omitted, a full SQUASH is attempted.
The pack should normally not be in use during a SQUASH run.
HELP causes JAMPACK to print HELP info to the file LINE.
JAMPACK will start a RESERVE to do the data movement, and will
wait for an AX. For more information see HELP JAM WAIT
Note : JAMPACK is an independent METALOGIC Program Product. It may
not be available on your system.
LOG Command
The logging of SUPERVISOR commands and messages has been greatly
enhanced. SUPERVISOR now logs all command and message activity into
a dedicated file called *METALOGIC/SUPERVISOR/LOG on a nominated
family configured using the INSTALL utility. By default, this family
is set to that of DL LOG.
The LOG command has been implemented to allow varied access to these
log files; searching by category, wild card text patterns or time
and date ranges is permitted. The LOG command extensions are shown
below:
+<<-----------------------------------+
-- LOG --+--+----------------------------------+------------>>>
+-- ALL ---------------------------+
+-- CHECK -------------------------+
+-- <Category List> ---------------+
+-- <DateTimeRange> ---------------+
>>>---+---------------------------+--+--------------------+---|
+-- FIND <Text Pattern> ---+ +- + -+------------+
+- <lines> --+
<Category List>
Each SUPERVISOR log entry is identified by a <Category> field which
consists of a 3-character text string and is used to filter any log
search by message type. The following categories exist for all logs:
ALL - returns all logs records regardless of category
ERR - returns all error messages
WRN - returns all warning messages
FLT - returns all internal faults
LGC - returns all LC (Log Comment) entries
MSG - returns all solicited and unsolicited messages
LOG command requests can select multiple categories separated by a
comma. For example:
LOG ERR,MSG,FLT
SUPERVISOR-specific categories are shown below:
ODT - returns all command entries
DBG - returns specific diagnostics with DEBUG set
HTP - returns diagnostic HTTP server log entries
WHN - returns all scripting actions such as WHEN,DO and EVAL
MON - returns entries logged by the Supervisor Monitoring option
By default, SUPERVISOR will only show one page of information for
each of the above commands (except for ALL) but note this may not
always be complete if SUPERVISOR fails to find enough entries. Only
the current SUPERVISOR log file is searched unless '+' is used.
<DateTimeRange>
--+-- <hhmm> --+---------------+-+----------------------------+-|
| +- <dd/mm/yy> --+ +- - <hhmm> --+--------------|
| | | +- <dd/mm/yy> -+
+-- MORE ---------------------------------------------------+
+-- BACK --+- <nn> -+-----------+-+-------------------------+
+-- SKIP --+ +- <Units> -+ +- FOR <nn> --+-----------+
+- <Units> -+
The <dd/mm/yy> format depends on the global setting of the Metalogic
configuration variable SYS_USDATES and can be set with the INSTALL
utility. The LOG CHECK command forces the SYS_USDATES system-wide
setting to be validated at any time.
The MORE modifier set the Stop date and time to be the date and time
of the last log record reported.
The BACK and SKIP modifiers respectively allow specific start and end
time points to be more easily assigned without having to use explicit
values. BACK allows a simple log start time to be assigned whereas
SKIP assigns a log End time. The FOR specifies an optional duration
associated with the Start or End time. If FOR is omitted then both
BACK and SKIP will assign default search range periods of 24 hours.
The <Units> types are as follows:
<Units>
---+-- DAYS ------+----------------------------------------|
+-- HOURS -----+
+-- HRS -------+
+-- MINS ------+
+-- MINUTES ---+
By default, MINUTES will be used if no <Units> is given. A minimum
of one character may be used to specify any <Units> type. BACK and
FOR may be used in any combination with valid date and times.
If the '+' modifier is used, an optional count may be used to
control the number of respponse lines returned to the caller. This
modifier has a limit of 500 lines and should be used with care
if a filter is used with many logs present. Note that '+' cannot
be used as part of a <Text Pattern> unless the pattern is quoted.
If a <DateTimeRange> is specified or the '+' modifier is used in the
command text, then all available log files will be searched until a
maximum of 4,000 log entries have been returned or 20,000 log file
reads have been performed.
The FIND modifier permits the searching of each log entry for the
specified text. The FIND automatically encloses the target with '='
at both ends of the text and is NOT case-sensitive, therefore finding
both lower-case and upper-case matches. FIND must be used after all
other modifiers as spaces are permitted with in the FIND text.
The <Text Pattern> modifier may be quoted (single- or double- quotes)
allowing targets with embedded spaces to be searched.
LOG FIND RETRY
LOG FIND 'RETRY FOR'
The log files are automatically released when the file size exceeds
50,000 records or the LC CLOSE command is used.
Examples:
LOG ALL
LOG ODT +30
LOG 0001-2359
LOG BACK 2 HOURS FOR 10 MIN
LOG 0800 1/1/07 FOR 2 DAYS +
LOG 0400 12/7/07 FIND SUMLOG +
LR Command
The LR command allows the site to easily run the LOGREADER utility
to update the Metalogic TRIM database with any missed tape notices
from either the current or selected SUMLOG files.
|-----+--- LR ----------+-- UPDATE -----------+--------------|
+-- <logno> ----------+
+-- <filename> -------+
The UPDATE modifier causes LOGREADER to be process all relevant
SUMLOGs from SUPERVISOR's last known valid TRIM timestamp. This is
usually the timestamp of the last tape update applied to the
database or the time when SUPERVISOR was QUIT (assumes no TRIM
transactions were pending).
All missed tape events are passed by LOGREADER back to SUPERVISOR
for processing. WHen SUPERVISOR is restarted after a QUIT or H/L,
an implicit LR is automatically executed; a LR UPDATE may be
executed at any time.
Alternatively, LR will accept a simple SUMLOG file number or a
file title. In the former case, SUMLOG files on the DL family
and SUPERVISOR's LOG BACKUP family are searched and the log title
is retrieved. With a specific title, LOGREADER can be used to
process external log files. In both cases, the logical file SUMLOG
is file-equated to the specified log.
LOGREADER will automatically write informational entries into the
SUPERVISOR log file. These can be viewed using the LGR variant
of the LOG command (as long as SO LOGGINGACTIVE is set).
Examples:
LR UPDATE
LR 505
LR *SUMLOG/1/020209/000505 ON DEV
LU Command
LU shows the tasks which are linked to a LIBRARY or DBS.
I--- LU ------ <mix number list> ------I
The <mix number list> must contain the mix numbers of one or more
LIB or DBS tasks, as seen by the LIBS or DBS ODT messages.
The response lists the mix numbers and names for all the tasks
directly using the specified LIB or DBS.
LU may not be used in an AF command or in TAPECONTROL.
MAIL Command
+---- ABORT --------- <All/Trans>-----+
+---- ALTPortno ----- <*PortNo> ------+
+---- ALTServer ----- <*Server> ------+
+---- ATTach -------- <*Extension> ---+
+---- AUTH ---------- <*Auth/User> ---+
+---- CODEset ------- <*Codeset> -----+
+---- CONfig -------- <Modifier>------+
+---- DEBUG --------- <*On/Off> ------+
+---- DOMain -------- <*Domain> ------+
+---- DUMP ---------------------------+
+---- HELP -------- <*Command> -----+
+---- IPaddress ----- <*IpAddr> ------+
+---- LC ---------- <Text> ---------+
+---- LOAd ---------- <Modifier> -----+
+---- LOG --------- <*Modifier> ----+
+---- MAXsmtp ------- <*integer> -----+
+---- MINlines ------ <*Integer> -----+
+---- MODify -------- <All/Trans>-----+
+---- NUDge --------------------------+
+---- OPtion -------- <*Option> ------+
+---- PORTno -------- <*PortNo> ------+
+---- POSTmaster ---- <*EmailAddr> ---+
+---- QUIT ---------------------------+
+---- REBuild ------- <Modifier> -----+
+---- RESume -------------------------+
+---- SERver -------- <*Host/IpAddr> -+
+---- SHow --------- <Option> -------|
+---- SMTPfamily ---- <Family> -------|
+---- STATUS -------------------------+
+---- SUSPend ------- <*& REJECT> ----+
+---- TEST --------- <EmailAddr> ----+
+---- TRansno-------- <Integer> ------+
+---- UNload -------- <Addr/User> ----+
Most commands have both interrogation (marked by *)
where no <modifier> is required, and change capability.
See 'MAIL HELP <Command>' for individual help info.
MEMO Command
The MEMO command recalls documentation placed in a defined MEMO.
I---- MEMO ------- <memo identifier> --------I
| |
|--- ? -----------------|
|-- <pattern> --|
<memo identifier> is the name of a defined MEMO. This form is used
to display the text of the MEMO.
The MEMO ? form displays the names of all currently defined MEMOs,
with the <pattern> used to subset this list.
NS Command
The NS command causes SUPERVISOR to output the next page in a
sequence to the requesting terminal.
I--- NS ---I
If no next page exists,the response will be
NO NEXT SCREEN, SCANNING NS
otherwise the next page will be output.
OK Command
--- OK -----------+--- <ODTS name> ---+--------------------|I
+--- # <slot no> ---+
+--- + <minutes> --+
+---- * ---------+
OK is used to enter an acknowledgement to SUPERVISOR that the
operator is ready to proceed with any ODT Sequence, of that name,
having executed a WAIT(..,OK) statement. The ODTS name must appear
after the OK or, using the # modifier to be more selective, the slot
number in which the DO is active.
The OK+<mins> and OK * variants are only used during BACKTRACKing;
both are used when operator intervention is required to verify the
processing of missed activities if MODE..BACKTRACK is set to VERIFY.
OK+<mins> 'jumps' the schedule, if the backtrack is on the current
day, by the number of minutes specifed. OK * authorizes that all
future activities should be processed without intervention.
Examples:
TT OK KILLDC
TT OK #12
TT OK *
TT OK + 60
PB Command
The PB command causes SYSTEM/BACKUP to be immediately
executed as an independent process.
To Invoke the System PB command from a Supervisor window use ODT
PB
I--- PB ---- <text> ----I
Upon receipt of a PB command, SUPERVISOR will immediately
initiate SYSTEM/BACKUP passing it the text without analysis.
PDT Command
PDT is SUPERVISOR's fast tape directory routine, returning
a list of the files found on a LIBRARY/MAINTENANCE tape, wrapped
containers or Metalogic COPYWRITE archives and images.
----- PDT -+- MT -+- <unit number> -+-+---------------+-----|
| | | | |
+- CD -+ | | |
| | +-- <pattern> --+
+- IN --- <File Title> --+
PDT accepts a unit number, prefixed by CD or MT, and returns the
directory of all files found on the library maintenance volume to
the originating ODT or station. PDT will also analyze MEMORY/DUMP
volumes on either media, returning dump header information, and
BLPack backup tapes.
The IN form allows the contents of a CopyWrite Image file or Unisys
wrapped container to be displayed. The ON part of the title can
specify a CD or pack. The Usercode and Family are taken from the
USE .. EXTERNAL specs. The file may also be a BLPACK disk archive.
If a <pattern> is specified, then SUPERVISOR will return only those
files on the tape whose names match the pattern provided.
An elapsed time limit of 2 minutes is applied to the internal
process initiated in response to a PDT command. This limit allows
SUPERVISOR to continue in case a tape drive hangs or the directory
search of the media is taking too long. In particular, this will
often apply to BLPACK tape volumes or disk archives.
The internal process is called TAPEDIR and is active only as long
as is necessary to read the directory file from the library
volume.
PR Command
The PRINT command provides hardcopy reports of all or part of
the SCHEDULE, the contents of the dictionaries, the available
attributes for use within DEFINEs, and is used to run displays so
that their output goes to the site printer.
To use the MCP PR command from a Supervisor window use ODT PR
I-- PRINT ---- ATTRIBUTES ------------------------------I
-- | ---- |
|- ODTSEQUENCE --------------------------|
| ---- | |-- <pattern> --| |
|- SITUATION ---| |
| ---- | |
|- DISPLAYS ----| |
| ---- | |
|- DEFINE --------| |
| --- | |
|- MEMO ----------| |
| |
|- <Display id> ------------------------|
| |
|- <Printable Report Command> -----------|
| |
|- SCHEDULE -----------------------------|
----- |- <day specification> --|
For more information on individual PRINT command variants type
HELP PRINT followed by DISPLAY, DEFINE, ATTR, or SCHEDULE, e.g.
HELP PR DEF
PRINT may be used as a modifier for certain other commands,
called <Printable Report Commands>. These commands are currently:
HELP, AF, FP, LU, HO, LOG, MAIL, PDT, TP, RECORD, SHOW, SLOT,
INPUT, and ENTER.
After a PRINT modifier they produce a report to the site printer.
The file attributes of the printer file are determined
by an optional dummy label equation of LINE 'bound into' the
codefile to suit each installations needs. File attributes which
may be changed are MAXRECSIZE (specified in characters per line),
PAGESIZE, TRAINID and FORMID. Lower case letters will not appear
unless the SO option LPLOCASE is set.
QUIT Command
The QUIT command forces an orderly immediate termination of
SUPERVISOR, followed by a restart.
To use the MCP QUIT command from a Supervisor window use ODT QUIT
I--- QUIT ---------------------I
| |
|-- SUPERVISOR --|
| |
|-- QUIT QUIT ---|
A QUIT command with no modifier is only valid from Supervisor
Remotespos or Windows and simply closes that Remotespo or Window.
Upon receipt of a QUIT SUPERVISOR command, SUPERVISOR
performs the following sequence of events.
SUPERVISOR's REMOTESPO stack, if running, will be terminated.
SUPERVISOR will wait for termination of any processed utilities
(FILEDATA,LOGANALYZER,FAMILYMANAGER etc).
If the program SYSTEM/HARDCOPY is running (HELP SO HARDCOPY), it
will be programatically DS'ed.
All WHEN's running will be terminated, and their sessions will be
released.
Finally SUPERVISOR itself will terminate.
The QUIT SUPERVISOR command may be the subject of an AFTER.
QUIT SUPERVISOR will not be accepted from a restricted terminal.
QUIT QUIT QUIT is like QUIT SUPERVISOR with one exception,
SUPERVISOR is not restarted.
RL Command
The RELOAD command is used to recall a file backed up with the
SAVE command.
|- RL -----|
I---| |----- USERDATA ---------------------------I
|- RELOAD -| | ---- |
|- SCHEDULE -----------------------|
----- |--- ON <family> -|
Upon receipt of a RELOAD command SUPERVISOR will look for, and
attempt to copy a file from the 'SAVES' family, as specified in
using the USE FAMILY .... FOR SAVES command, to the appropriate
family. For the USERDATAFILE this is the family specified in the
ODT DL command. In the case of the SCHEDULE it is the family
specified in the USE FAMILY ...FOR SCHEDULE command.
Backup copies of the SCHEDULE may be reloaded from any family
if the ON modifier is used.
During a RELOAD process all communication to and from
SUPERVISOR is suspended.
More information is available with HELP RL USERDATA,
and HELP RL SCHEDULE.
REMOTESPO Command
The REMOTESPO command controls access to SUPERVISOR from
datacom stations .
To issue a Controller REMOTESPO command from a Supervisor window
use ODT REMOTESPO.
I--- REMOTESPO ------ - -------------------------I
| - |
|-- ? ----------------------|
| |
|------------- <file title> --|
|- - -| |----- * -------|
-
The REMOTESPO command followed by a station name causes
SUPERVISOR to attempt to open a datacom file on the requested
station.
REMOTESPO ? lists all currently active REMOTEPSOs with the station
names where they running.
REMOTESPO - <station name> will deny further access to
the specified station. REMOTESPO - turns off the REMOTESPO
facility completely, no further access is permitted to any
datacom stations. This command is not permitted from a REOMTESPO.
REMOTESPO * is a special case to allow a station
to make itself a REMOTESPO, but the controlling MCS must send a
privileged usercode along with message.
REMOTESPO - * cancels the REMOTESPO where the command was entered.
Any REMOTESPO station has the same access to SUPERVISOR
commands as does a system console, and in addition SUPERVISOR
will forward any non-SUPERVISOR commands to the system without
limitation. For this reason, the number of REMOTESPO stations
should be restricted.
RESTRICT Command
RESTRICT controls what system ODT commands are allowed.
To use the MCP Restrict command from a Supervisor Window use
ODT RESTRICT.
Syntax:
--- RESTRICT ----+-----+-------------------------------------------|
+- + -+ |- <list of ODT commands> -|
|- - -|
For example:
TT FOR ODTSECU/PASS RESTRICT PG,OP,DS
A simple RESTRICT command interrogates what commands are controlled.
Other forms need the ODTSECUSER (as a FOR modifier or TERM USER).
RESTRICT +/- with no command list suspends or resumes restriction
without changing the command list.
The command list can have any command which is implemented via the
DCALGOL SETSTATUS intrinsic, including MIX and UNIT requests. This
means that rather more commands are available than via the Infoguard
RESTRICT COMMAND ODT command. The use of the TT RESTRICT command
requires an ODTCONTROL key (displayed in the TTWS response)
When a command is in the list, it is disallowed from anywhere
other than the ODTSECUSER usercode. The caller program or CONTROLLER
gets a COMMAND RESTRICTED error. Any restricted command is logged as
a violation under the OPERATOR object and is passed to any SITU with
an OPERATOR or OPERATOR=SETSTATUS context. If the OPAL is
running with a FOR modifier specifying the ODTSECUSER usercode, its
ODT statements will by-pass the RESTRICT. This allows the OPAL
programmer to be highly selective in controlling ODT input.
Example:
To disallow DS commands from the ODT
TT For ODTSU/PW Restrict DS
TT For ODTSU/PW When (Operator=SetStatus:CommandKey="DS" and
Restricted and SourceType neq ODTKeyin) Do (ODT(CommandText))
SV Command
The SAVE or SV command makes backup copies of 'important'
system files.
To use the MCP SAVE command from a Supervisor window use ODT SAVE
+- SAVE -+
I--+ +-------+-USERDATA ----------------------------+-I
+- SV ---+ | ---- |
|- * --+-- SCHEDULE -+----------------------+-+
| ----- +--- AS <file title> --+ |
| +--- TO <family name> -+ |
| |
+-- <program set> --- AS <file title> -+
The SAVE command is used to create backup copies of
SYSTEM/USERDATAFILE or SUPERVISOR's SCHEDULE file, or symbolic
backups of the SCHEDULE contents.
More information is available with HELP SV SCHED, HELP SV AS,
HELP SV USERDATA
NOTE: Files are copied into the directory SAVED of
SUPERVISOR's usercode by default (except USERDATA and SCHEDULE).
SHIFT Command
The SHIFT command allows an operator to notify SUPERVISOR that
he or she is beginning or ending a shift.
|- Begin -|
I- SHIFT -| |--------------------------------------------->
| | |
|- END ---| |- <accesscode> ---------------------------->
|- / <accesspassword> -|
-
>------------------------------------------------------------------I
|
>------------- TO ----- <military time> -----|
Upon receipt of a SHIFT command, SUPERVISOR will respond with a
greeting like
BEGINNING OF SHIFT NOTED, GOOD EVENING <accesscode>
A LC ODT command will then be simulated, specifying the
operator identification, if supplied.
Should any activity be scheduled (with the AFTER command), for
SHIFT BEGIN (END), those activities will be immediately performed.
In particular, any REMIND commands scheduled will be activated.
If SUPERVISOR's LOGOPERATOR option is set (HELP LOGOPERATOR),
all WFL jobs commencing from this time on, will have a LJ ODT
command entered as they enter the mix, which identifies each
logged on operator.
If SUPERVISOR's NAMEOPERATORS option is set (HELP SO,HELP
NAMEOPERATORS) then the <accesscode> will be validated,
If the accesscode has an accesspassword, it must be supplied.
Invalid names will be rejected. When NAMEOPERATORS is set, and no
operators are known to SUPERVISOR, most SUPERVISOR commands will
be rejected from the system consoles, with a request
PLEASE ENTER 'SHIFT BEGIN' FOLLOWED BY YOUR ACCESSCODE
If no TO <military time> appears, SUPERVISOR will automatically
terminate a shift 8 hours after the SHIFT BEGIN was entered.
Otherwise the shift will be automatically terminated at the time
specified at logon. All shift logons are cleared after a halt load.
TO is not valid unless an accesscode is entered.
If both LOGOPERATOR and NAMEOPERATORS are set, whenever
no operators are logged on , the ADMs will be turned off on all
system consoles (each minute) until a valid log on is performed
SHOW Command
To use the MCP SHOW command use ODT SHOW.
The SHow command can be used to display details of the utilisation
of Supervisor's SCHEDULE file, Supervisor Processor utilisation ,
Supervisor Global Variables or a list of all SUMLOGs available on
the System.
The command syntax is as follows:-
I--- SH ---+---------------------------------+-----I
+--- > chunk size ----------------+
+--- MAP -------------------------+
+--- GLobals -+---+---------------+
+--- PERM ----+ +-- <pattern> --+
+--- UTIL ------------------------+
+--- LOG --+-------------------+--+
+- ON <Familyname> -+
Each option is described in more detail in the following pages.
SHow or SHow MAP : Details of Supervisor SCHEDULE utilisation.
I--- SH -------------------------------------+------I
+--- > chunk size ----------------+
+--- MAP -------------------------+
If the default option is requested details of the SCHEDULE size,
Version and the Areas In Use will be reported using a default
'chunk size' of 10. This report can also be produced for other User
'chunk sizes'.
An overview of the SCHEDULE utilisation can be obtained by using the
MAP option - this will show in-use and available areas together with
a total showing the actual number of segments in-use.
SHow Global : Details of Supervisor Global Variables.
I--- SH --- Globals -------+---------------+-----I
| |
+-- <pattern> --+
This variant of the SHow command will return a list of Supervisor
Global variables, with their current values. The use of <pattern>
allows the request to be filtered for a specific name or wild-card
pattern.
SHow PERM : Details of PERMANENT Configuration Variables.
I--- SH --- PERM ----------+---------------+-----I
| |
+-- <pattern> --+
This variant of the SHow command will return a list of all active
Magus Permanent configuration variables with their values. The use
of <pattern> allows the request to be filtered for a specific name
or wild-card pattern.
SHow UTIL : Details of Supervisor Processor utilisation.
I--- SH --- UTIL --------------------------------I
This variant of the SHow command will return Supervisor Processor
utilisation statistics together with the total time that Supervisor
has been running.
Processor utilisation is broken down into 'activities' and can give
a useful indication of problem areas.
SHow LOGs : Details of SUMLOGs available on the System.
I--- SH ------- LOG --+-------------------+------I
| |
+- ON <Familyname> -+
The SHow LOG command will list all SUMLOGs available on the System.
The current SUMLOG must be available on the DL LOG Family, the Pack
Family specified by the 'Family for LOGs' (see USE command) together
with the DL LOG Family will be searched for previous LOGs.
The 'ON <Familyname>' variant may be used to search for previous
LOGs on the DL LOG Family and the specified Family.
SLOT Command
The SLOT command returns an in-depth analysis of the specified
WHEN environment. The response shows current state information and
values for the variable heap. The PRINT modifier can be used with
this command.
----- SLOT --- <Slot Number> ----+---------+--------------|
| |
+-- + --+
The SLOT command shows local slot information, the current stack
state of the slot and all real and string variables, with their
values, taken from the heap.
Use of the PRINT modifier enables the dumping of more detailed
slot environment information and local array data.
The '+' modifier suppresses the dumping of the variable heap
and local array data but additionally displays detailed slot
environment info.
SO Command
The SO command sets, resets or interrogates the value of
SUPERVISOR's options.
---- SO ---+-------------+-----------------------+---------|
| |---<---<--- , ---<---<-| |
+--+- + -+--+-+-- <integer> ------+-+--+
+- - -+ |-- HARDCOPY -------|
|-- UserNoFor ------|
|-- LOGMINIMAL -----|
|-- NoAutoDc -------|
|-- WaitOKtask -----|
|-- NoDefActive ----|
|-- StrictODTS -----|
|-- MONITORING -----|
|-- LogOperator ----|
|-- NameOperators --|
|-- USDates --------|
|-- TAPELIB --------|
|-- NoTTLogging ----|
|-- DefineResp -----|
|-- AsyncWFL -------|
|-- NoWhenRestart --|
|-- NoValidate -----|
|-- AutoFS ---------|
|-- NoStats --------|
|-- NoEnterList ----|
|-- AutoTL ---------|
|-- NoTanking ------|
|-- UseCopyWrite ---|
|-- CompressDefine -|
+-- Logging --------+
The SO command with no following text requests SUPERVISOR to
display a page showing the name and setting of all of it's
options. This page resembles the page from the ODT OP command.
Setting or resetting one or more options is accomplished with the
SO + or SO- form of the command. The particular options to be
changed may be specified with a number (in the range 0 to 47) or
by name.
For full info on the other options enter 'HELP SO' followed by the
name of option (for example, HELP SO USDATES.)
SS Command
The SS command is used to send text to a Window Station.
To use the MCP SS command from a Supervisor window use ODT SS.
The Station is designated by its LSN or Station Name. Text may
also be sent to all active Window stations by specifying ALL.
I--- SS ------|--- <LSN of Station> ---|--- < Message Text> ---I
| |
|---- <Station Name> ----|
| |
|------- < ALL > --------|
SYSLOG Command
The SYSLOG command causes SYSTEM/LOGANALYZER to be immediately
executed as an independent process.
I--- SYSLOG --- <optional text> ---I
Upon receipt of a SYSLOG command, SUPERVISOR will immediately
initiate SYSTEM/LOGANALYZER passing the text without analysis.
TK Command
For Unisys/StorageTek tape silos only. TK commands are passed to
a process called SILOHANDLER which translates the commands into
TAPESERVER library calls. The full list of commands is shown below:
---- TK --+-- Inventory ----+---------------------------------+--|
+--- <serialno> --+---------------------------------+
| +-- + --+---+---- SCRATCH --------+
| +-- - --+ |
| | |
| +-- EJECT ------------------------+
+-- EJectNow ---------------------------------------+
Using TK <serialno> without any modifier returns the registered
status in the silo of the specified cartridge.
The SCRATCH modifier allows the scratch flag for any tape resident
in the silo to be changed to ON or OFF.
The EJECT modifier allows the tape to be queued for ejection
from the silo hardware.
EjectNow tells the Silo to process the tapes queued for ejection.
TL Command
TL releases and processes the System SUMLOG.
To invoke the MCP TL command from a Supervisor Window use ODT TL.
I--- TL -------------------------I
|--- <integer> ---|
Upon receipt of a TL command, SUPERVISOR performs the following
steps:
- Initiates an ODT TL command to release the current SUMLOG.
- For each file found in the SUMLOG directory on the DL LOG
family, SUPERVISOR copies that SUMLOG to its Log Backup family,
as specified by the USE FAMILY FOR LOGS variant (see HELP USE
for more details). If DL LOG and USE FAMILY FOR LOG are the
the same family then the COPY is NOT performed. If SUPERVISOR
finds the companion SECURITYLOG then this file will also be
copied.
- If a successful COPY is performed, both the original SUMLOG and
SECURITYLOG files are removed from the DL LOG family.
- For each SUMLOG found, SUPERVISOR starts the WFL assigned to
the USE JOB AFTER TL option of the USE command (see HELP USE
for more details) passing the title of the SUMLOG and optional
integer as parameters to the job.
If the USE FAMILY FOR LOGS is not equal to DL LOGS and the
USE USER Usercode does not have SECADMIN privilege then an error
is returned, since it would not be possibel to move the SECURITY
Log.
The optional <integer> is provided solely for site purposes, if
not specified, zero is used. TL may be scheduled, with the
AFTER command. It is not valid from restricted terminals.
Examples:
TT TL
TT TL 5
AF 2215 ON WEEKDAYS TL 255
TP Command
USE Command
The USE command changes and interrogates the value of a number
of miscellaneous parameters to SUPERVISOR.
I--- USE ---+----------------------------------------------+---I
+- BDNAME -------+-- <identifier> --+----------+
| +----- - --------+ |
| |
+- CHARGE -------+-- <chargecode> --+----------+
| +----- - --------+ |
+- DESTINATION --+-- <destination> -+----------+
| +----- - --------+ |
| |
+- FAMILY -- <family> For ---+- CONFIG ---+---+
| |- DUMPs ----| !
| |- EXTERNAL--| |
| |- LOGS ---| |
| |- SAVE -----| |
| |- SCHEDULE -| |
| +- SYSTEM ---+ |
| |
+- FILE -- <filename> For --+- REBUILD -----+-+
| +- NAPRUNLIGHT -+ |
| |
+- GETSCRATCH -+- NONE -----+--+--------+------+
| |- REPORTED -| +- SILO -+ |
| |- CREATED --| |
| +- USED -----+ |
| |
+- JOB -+- <file title> -+- AFTER --- TL ------+
| +----- NONE -----+ |
| |
+- LANGUAGE <integer> -------------------------+
| |
+- MODE -+- AUTO --+-- For ---- BACKTRACK -----+
| |- NONE --| |
| |- TODAY -| |
| +- VERIFY + |
| |
+- ODT --------- <integer> --------------------+
+- QUEUE ------- <integer> --------------------+
+- SCRATCHPOOL ---+-- <scratchpool list> --+---+
| +------- - ------------+ |
| |
+- SILO -----+-- <silokind> ----+--------------+
| +----- - --------+ |
| |
+- TASK -- <file title> For -+- RECORDER ----+-+
| |- NAPSTATSLIB -| |
| |
+- USER <usercode> --+-------+-----------------|
| +- For -+-- TAPELIB ------|
| |-- EXTERNAL -----|
| |-- ODTSECURITY --|
| +-- MAIL ---------+
| |
+- WINDOWSECURITY ---- <security level> -------+
Upon receipt of a USE with no modifiers, SUPERVISOR displays
the current values of all parameters that may be set by the USE
command. For detailed explanation of the effects of the various
options, enter HELP USE followed by one of the following keywords:
QUEUE ODT USER WINDOWSECURITY LANGUAGE JOB TASK
FAMILY FILE DESTINATION MODE
VIA Command
The VIA modifier allows the user to issue normal Supervisor
commands as if they had originated from a system ODT. Any output
generated by that command will be routed to the specified ODT.
|---------------------------- <command> -------------------|
| |
|-- VIA ---<unitno> --|
For example:
TT VIA 2 WHEN TAPELABEL DISP TAPELABEL
All the output generated by TAPELABEL would be directed to ODT 2.
Alternatively, for commands input via an SM:
<mixno>SM VIA 2 FP
would generate the output to the FP command back to ODT 2 and not
the ODT as specified by the USE ODT command (if different). Note
this technique can be used to remotely disable WHEN-DISPLAYs which
have been invoked from an ODT.
For example:
<mixno>SM VIA 3 WHEN SITU DISP
VL Command
VL simplifies the process of entering tape volumes into the
Volume library.
------ VL ---+-------+----- MT <unit list> -----------+---|
+-- + --+ |
+-- - --+----- MT <unit list> -----------+
| |
+-+----+- SN <serialno> <volume> -+
+ DK +
+ MT +
+ PK +
The VL command causes SUPERVISOR to generate and run a small
job to volume add or volume delete a single reel scratch or labelled
magnetic tape family. VL applies only on cataloging systems, and
only to scratch tapes or labelled tapes with one reel. Checks are
made that the tape is ready, available to the group,not rewinding,
not in use,labelled, and not either volumed (VL + variant) or not
volumed (VL - variant). Suitable error messages are issued if the
operation cannot be performed.
A special variant of VL- allows a tape volume to be deleted
if the media is not physically loaded. The VL - SN variant requires
both serial number and volume name. This command may also be used
for both DISK and PACK entries (e.g. FLEX CopyWrite volumes) though
the modifier PK or DK must be included in the command or MT will be
assumed. If the Metalogic FLEX package is installed, it is not
possible to VL - a volume that FLEX knows to have backup references.
Examples:
TT VL + MT 15,16-19,23
TT VL - MT 15
TT VL - SN AA0001 MYVOLUME
TT VL - PK SN DF0077 ALTIMAGE_A
WINDOW Command
The WINDOW command controls access to SUPERVISOR from COMS
Window stations.
I--- WINDOW ------ ? ---------------------------I
| |
|-- - -----------------------|
| |
|-- <Station Name> --|
The WINDOW ? command lists all currently active COMS Window stations
with their LSN and name.
WINDOW - <station name> will terminate the dialogue on that Station
and return the Station to the MARC window.
WINDOW - will terminate the dialogues on all Stations currently
accessing Supervisor via a COMS window and will return them to the
MARC window.
WHEN Command
The WHEN and ONCE commands allow an operator to activate and
deactive situations, and to interrogate which situations are
currently running or queued ready to be run.
The following pages describe the variants of the WHEN Command.
See also TT HELP EV
Option 1 : Activate a Situation.
A Situation is defined by means of the DEFINE command and describes
a combination of values. Once defined, a Situation is no more than
an entry in SUPERVISOR's SITUATION Dictionary. To start monitoring
for the combination of values, it is necessary to activate the
Situation.
WHEN - means activate the Situation until explicitly deactivated.
ONCE - means activate the Situation, but terminate after the first
time the ODT Sequence is performed, or the Display was
output.
The following RailRoad diagrams show the command syntax.
Option 1 : Activate a Situation.
I--+- WHEN -+-+-----------+- <situ> -+-------------------------+-->>
| | | | | |
+- ONCE -+ +- & DEBUG -+ +- [ -- <max evals> -- ] -+
>>-- <action> -+------------------------------+--I
| |
+- DELAY -- <num> -+-----------+
| |
+- Seconds -+
Option 1 : Activate a Situation.
<action>:
I--+- DO----+---- <odts> -+--+---------------------------+--I
| | | | |
+- TEST -+ | +- [ -- <max entries> -- ] -+
| |
+- DISPlay -+- <disp> -+
| |
+- PRint ---+
TEST is identical to DO except that all statements which have
an action are converted to DISPlays to allow debugging.
PRINT is similar to DISPlay except that output will be directed
to a print file and not to a screen.
Option 1 : Activate a Situation.
DELAY
The DELAY modifier is only valid if the SITUATION is TIME-based.
Normally, if no DELAY is given TIME-based SITUATIONs are
evaluated once a minute. The DELAY option is used to change
that frequency.
Seconds (minimum abbreviation 'S') can appear after the DELAY
to denote that the delay is in seconds. The maximum delay is
4095 seconds.
Option 1 : Activate a Situation.
<max evals>: --+------------------+-- <integer>
+-- <integer> - ---+
Enables the User to specify the maximum number of times the
Situation will be evaluated before it is terminated and
optionally that some evals should be skipped
[5-10] indicates that the first 4 objects should be ignored and
that the eval should stop after 10 objects.(4 skipped + 6 evals)
<max entries>: --+------------------+-- <integer>
+-- <integer> - ---+
Enables the User to specify the maximum number of times that
ODTSequence or DISPlay can invoked before the WHEN is
terminated and optionally that some entries should be skipped.
Option 2 : De-activate a Situation.
This option is used to deactivate a running program. The command
does not have to match the one used to initiate the program.
Use DO - #<slotno> to deactivate a specific slot. See HELP DO.
I--+- WHEN -+- <situ> -+- TEST +-+---------------------+--I
| | | | | |
+- ONCE -+ +- DO --+ +--- - -- <odts> ---+
| |
+- DISPlay -+-+-----------------+
| | | |
+- PRint ---+ +- - -- <disp> -+
Option 3 : Interrogate active Situations.
This is the SUPERVISOR equivalent of MX for OPAL programs.
If the <Slot No> option is used only information for the specified
Slot will be returned.
If the * option is used only Situations initiated by the enquiring
Station will be shown.
I--+- WHEN -+- ? -+-----------------+--I
| | | |
+- ONCE -+ +--- <pattern> ---+
| |
+- [ <Slot No> ] -+
| |
+------ * ------+
WORKDAYS Command
Syntax:
---- WORKDAYS ---+--------- ? -------------------------+----I
------- | |
+----+-----+-- <gregorian date> ------+
| +- + -+ |
| +- - -+ |
| |
+<<---------- , ----------------------+
Semantics:
The WORKDAYS Command allows the designation of a Saturday or
Sunday as an additional working day. Valid Gregorian-style dates
must be provided as either MM/DD/YY
or DD/MM/YY format (depending
on SO USDATES) and 4-digit years are also allowed. Unlike HOLIDAYS,
supplying a year is mandatory.
Only dates which map to Saturdays or Sundays are permitted.
These extra working days are use to supplement Supervisor's AFTER..
WORKDAYS extensions and supports the WORKDAY Opal function.
The WORKDAYS ? variant returns the list of all current workdays
to the originating station.
Examples:
WORKDAY + 23/11/2006
WORKDAY - 12/2/2002,15/04/2001
WORKDAY 04/07/2011
Pragmatics:
The list of workdays is held in the Schedule file and is thus
backed up by a SAVE command, and restored with a RL command.
It is not possible to assign a working date which is already
a holiday.
WS Command
The WS command displays the version and similar information
about the particular codefile in use.
I--- WS ---I
Upon receipt of a WS command, SUPERVISOR displays a page of
information describing the version of the SUPERVISOR, the system
serial number, the version of ATTRIBUTES in use, and compiletime
options .