Unisys MCP Commands 86000395-514
Unisys MCP Commands 86000395-514
Servers
System Commands
Operations Reference Manual
Printed in USA
April 2006 8600 0395514
.
ClearPath Enterprise
Servers
System Commands
Operations Reference Manual
UNISYS
Printed in USA
April 2006 8600 0395514
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information
described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to
purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the
products described in this document are set forth in such agreement. Unisys cannot accept any financial or other
responsibility that may be the result of your use of the information in this document or software material, including
direct, special, or consequential damages.
You should be very careful to ensure that the use of this information and/or software material complies with the laws,
rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice. Revisions may be issued to advise of such
changes and/or additions.
Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at
private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard
commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data
rights clauses.
Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries.
All other brands and products referenced in this document are acknowledged to be the trademarks or registered
trademarks of their respective holders.
Contents
Section 1 Commands
System Commands Overview ............................................. 1
A (Active Mix Entries) ........................................................ 5
ACCOUNTING (Resource Accounting)................................. 11
ACQUIRE (Acquire Resource) ............................................ 13
AD (Access Duplicate)...................................................... 21
ADM (Automatic Display Mode) ......................................... 23
AI (Automatic Initiation) .................................................. 32
ARCCOPY (Copy Archive Directory).................................... 34
AR (Archive Release) ....................................................... 35
ARCDUPLICATE (Duplicate Archive Directory) ..................... 36
ARCREPLACE (Replace Archive Directory) ........................... 37
ASD (Actual Segment Descriptor)...................................... 39
ASDU (ASD Usage).......................................................... 42
AT (At Remote Host) ....................................................... 43
AT (At Remote Host): Use with Host Services ..................... 44
AT (At Remote Host): Use with FTAM................................. 47
CHANGE (FTAM File Management Command)...................... 48
FILES (FTAM File Management Command).......................... 48
LFILES (FTAM File Management Command) ........................ 48
MODIFY (FTAM File Management Command) ...................... 49
REMOVE (FTAM File Management Command)...................... 51
AUTORESTORE (Archiving AUTORESTORE Option) ............... 53
AX (Accept) .................................................................... 54
BADFILE (Bad File) .......................................................... 56
BNA............................................................................... 57
BNAVERSION.................................................................. 59
BR (Breakout)................................................................. 60
C (Completed Mix Entries) ................................................ 62
CA (Candidate) ............................................................... 65
CACHE (Disk Cache) ........................................................ 67
CC (Control Card)............................................................ 70
CF (Configuration File) ..................................................... 71
CHECKFILE (Check for Nonresident Files) ........................... 73
CL (Clear) ...................................................................... 75
CLOSE (Close Pack) ......................................................... 79
CM (Change MCP) ........................................................... 83
CO (CONTROLLER Options) .............................................. 94
8600 039-514 i
Contents
ii 8600 0395-514
Contents
iv 8600 0395-514
Contents
8600 0395-514 v
Contents
UL (Unlabeled)...............................................................709
UP (Up Resource) ...........................................................710
UQ (Unit Queue) ............................................................715
UR (Unit Reserved).........................................................717
USERLICENSE................................................................722
W (Waiting Mix Entries) ..................................................726
WM (What MCP).............................................................729
X25MCS (Command Prefix) .............................................733
XD (Bad Disk)................................................................735
Y (Status Interrogate) ....................................................737
??CD (Conditional Dump) ................................................741
??CL (Clear) ..................................................................743
??CM (Change MCP) .......................................................744
??CMPAUDIT (CMP Audit) ................................................745
??COPY (Copy Files) .......................................................746
??DIALT (Dial Trace).......................................................747
??DS (Discontinue).........................................................748
??DUMP (Dump Memory) ................................................749
??FS (Force Schedule) ....................................................750
??HALT (Halt System).....................................................751
??HS (Hold Schedule) .....................................................753
??LH (Load Host) ...........................................................754
??MARC (Transfer to Menu-Assisted Resource Control) .......755
??MEMDP (Dump Memory) ..............................................758
??ODT (Return from Menu-Assisted Resource Control) ........759
??OK (Reactivate) ..........................................................760
??OL (Display Label and Paths) ........................................761
??PD (Print Directory) .....................................................762
??PHL (Programmatic Halt/Load)......................................764
??REMOVE (Remove File) ................................................765
??RESTRICT (Restrict ODT) .............................................766
??RJ (Remove JOBDESC File)...........................................767
??RUN (Run Code File)....................................................768
??RV (Restart Volume Directory) ......................................769
??SECAD (Security Administrator Authorization) ................770
??ST (Stop) ...................................................................772
??TRACE (Trace Table)....................................................773
??UNWRAP (Unwrap Files) ...............................................774
??UR (Unit Reserved) .....................................................777
??W (Waiting Mix Entries) ...............................................778
??ZFA (Zero Failure Analysis) ..........................................779
vi 8600 0395-514
Contents
To use this document, you should understand system concepts such as cataloging,
queuing, file storage, file attributes, initialization of halt/load units, and library
maintenance procedures.
Notation Conventions
The following elements are used in this document to explain the system commands.
Syntax Diagrams
A railroad diagram represents the syntax of each system command.
Arithmetic operators
The following symbols are the standard arithmetic operators used in this document.
8600 039-514 1
System Commands Overview
Arithmetic Meaning
Operator
+ Addition
Subtraction
* Multiplication
/ Division
** Exponentiation
2 8600 0395-514
System Commands Overview
Examples of various forms of the command and possible responses from the
system. The system responses are indented to distinguish them from the
commands.
Additional information, if any, that might affect the use of the command is given
under the heading Considerations for Use.
Internationalization
For the convenience of sites where English is not the primary language, system
messages and responses can be displayed in other languages. The response to the
WM (What MCP) command includes a list of languages in which translations are
available on your system.
Use of the TERM CONVENTION command has an impact upon the presentation
format of decimal numeric values in responses to those ODT commands that provide
numeric values. The setting of the TERM CONVENTION value provides different
numeric separator characters. For example, use of the ASERIESNATIVE convention,
which is the default setting, provides a comma (,) as the numeric separator, so the
decimal number 1234567 is presented as 1,234,567.
The use of other TERM CONVENTION values such as BELGIUM, NORWAY, and
SWITZERLAND, provide the numeric separator character normally used by the
selected language or convention. Following are some examples.
8600 0395-514 3
System Commands Overview
CU (Core usage)
DU (Disk usage)
O (Overlay)
4 8600 0395-514
A (Active Mix Entries)
Syntax
<wild card>
<delim>
One of the following characters:
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters.
Character Description
8600 0395-514 5
A (Active Mix Entries)
You can include lowercase characters and space characters by prefixing the wild-card
string with LIT and enclosing the wild-card string in delimiters.
For example, if you enter the following syntax, the system returns entries that
contain the string "PACK":
A NAME =pack=
If you enter the following syntax, the system returns entries that contain the string
"pack":
Explanation
A
ACTIVE
Display all active jobs or tasks that have not been suppressed by the SUPPRESS
(Suppress Display) command or automatically suppressed by the SUPPRESSED
option of the MP (Mark Program) command. Display of jobs, freeze control libraries,
and database task stacks is controlled by the value of the SUPPRESSACTIVE system
option; for the purpose of this option, jobs include active jobs and tasks with no
parent.
A ALL
AA
Display all active jobs or tasks, including any that were suppressed, either by the
SUPPRESS (Suppress Display) command, the SUPPRESSED option of the MP (Mark
Program) command, or by the setting of the SUPPRESSACTIVE system option.
A QUEUE
AQ
Display all active jobs or tasks initiated from any queue.
A CPU
A CPURATE
6 8600 0395-514
A (Active Mix Entries)
A SORT CPU
A SORT CPURATE
Displays active jobs or tasks and their CPU processor time used (CPU) or their CPU
processor rate (CPURATE). If the SORT option is used, the display is in the order of
decreasing central processing unit (CPU) time used or decreasing CPU rate.
The CPURATE option causes the display of processor time used (CPU Time column) to
be replaced with the recent processor rate as a percentage (CPU Rate column). This
rate shows the ratio of processor time divided by a recent elapsed time interval. If
the interval is 20 seconds (the default), the MCP computes the processor rates of
each task every 20 seconds and displays the percentages in a CPU Rate column. For
example, a task using 2 seconds of CPU time during the last 20 seconds would have
a CPURATE of 10% if the default time interval is in effect. This option enables you to
determine which tasks are currently using the most system processor resources.
Notes:
Use the SBP (System Balancing Parameters) command to specify the time
interval for CPURATE calculations.
If the SORT option is used, the output is limited to the number of processes
that can fit in approximately 10 pages of the display.
A USER <usercode>
Displays only active jobs or tasks running with the specified usercode.
Note: MCSs and tasking programs do not show up when filtered by usercodes.
Examples
Example 1
A
Work Flow Language (WFL) jobs do not appear if they are waiting for a task to
complete.
The heading line appears on the first page of the Active Entries display and before
the active mix entries in automatic display mode (ADM). The number in the heading
indicates the total number of active entries, including suppressed entries.
8600 0395-514 7
A (Active Mix Entries)
At the beginning of each entry line, an E indicates that a syntax error was discovered
during compilation. An asterisk (*) indicates that the task is being displayed for the
first time.
The Mix field shows the job or task mix number of the active entry. To determine the
number of the job that started a task, refer to Y (Status Interrogate).
The CPU Time field shows the accumulated central processor time for each displayed
task. A maximum of 999 hours can be displayed. If the SORT CPU option is specified
in the command, the display is sorted according to decreasing CPU time used. The
job or task that has used the largest amount of CPU time is the first item displayed.
If an entry is greater than 999, the field is set to the following value to indicate an
overflow condition:
***:**:**
The next column contains the word Job if the task has no parent, Lib if the task is a
library process, or DBS if the task is a database stack. Otherwise the column is
blank.
The usercode of the originator appears before the job or task name. Some tasks and
jobs can have two usercodes shown for the following reasons:
Tasks other than compiler tasks display with the following format:
Throughout the Active Entries display, fields are wrapped around if they need extra
space. The next line begins in the first column of the field. In the example, the name
information for job number 7240 is continued on another line, beginning in the first
column of that field. However, fields are not wrapped if TRUNCATE = TRUE or ADM.
Example 2
This example shows the command and response for a specific queue:
A QUEUE 5
8 8600 0395-514
A (Active Mix Entries)
Example 3
This example shows the command and response for the USER option when no
usercode is specified. The command lists the programs running without a usercode.
A USER=""
8600 0395-514 9
A (Active Mix Entries)
Example 4
This example shows the command and response for the SORT CPURATE option:
A SORT CPURATE
The CPU Rate column shows the recent processor rate (processor time divided by
elapsed time) as a percentage of the total CPU usage over a recent time interval.
The default interval is 20 seconds. For information about changing this interval, refer
to the SBP (System Balancing Parameters) command.
10 8600 0395-514
ACCOUNTING (Resource Accounting)
Syntax
Explanation
ACCOUNTING
Displays the current settings for the task and file resource use selections.
8600 0395-514 11
ACCOUNTING (Resource Accounting)
Examples
Example 1
This example sets the highest priority of system resource utilization accounting:
Example 2
This example sets the minimum level of file resource accounting:
12 8600 0395-514
ACQUIRE (Acquire Resource)
Many of the forms of the ACQUIRE command cause a brief system pause.
If the command is rejected, wait for the current command to complete and enter the
command again.
Note: ACQUIRE is a synonym for UP. Use ACQUIRE on IOM systems. Use UP on
IOP systems.
Syntax
<unit specification>
8600 0395-514 13
ACQUIRE (Acquire Resource)
<CTL specification>
Explanation
ACQUIRE DOMAIN <number>
ACQUIRE SYSTEM <number>
Acquire the modules contained in the DOMAIN or SYSTEM. The concept of DOMAIN
describes a group of hardware modules that share power, cooling, maintenance
access, and partitioning logic.
To acquire a module, you must acquire the DOMAIN in which the module resides.
When you acquire a DOMAIN, modules in that DOMAIN are acquired and possibly put
into use, subject to the saved state of the individual module. When you acquire an
individual module, other modules in the DOMAIN are acquired but marked as saved.
14 8600 0395-514
ACQUIRE (Acquire Resource)
The CPM and IOM numbers must be integers in the range 0 through 11. On VM
systems, the range of CPM numbers is 4 through 11.
8600 0395-514 15
ACQUIRE (Acquire Resource)
Caution
Be very careful when you use the :TEMP option with intelligent peripheral
interface (IPI) units. Because the subsystem enforces ownership of these units,
explicit FREE unit action is required to give up physical ownership. Such action
does not always occur when a partition is halted. You might have to use the
OVERRIDE option of the ACQUIRE system command to physically take over such
temporary devices before the next halt/load of the system has been completed. If
the LOADER reconfigures the group by using the RECONFIGURE GROUP operation
before the next system initialization, subsystem ownership might not be
relinquished for IPI units that are either logically free or no longer described in a
new peripheral configuration diagram (PCD). Note that using the ??PHL, ??CM,
??HALT, or RECONFIGURE GROUP commands to halt/load the system causes
physical ownership to be relinquished before halting.
This form of the command might also be a necessary step in recovering from certain
CTL and PORT failures. You might need to perform the following steps to recover
CTLs that are involved in such failures:
16 8600 0395-514
ACQUIRE (Acquire Resource)
UNABLE TO PERFORM
This message indicates that the system cannot acquire the LINEID.
For more information, refer to Understanding IEA-1 IOPs in "Considerations for Use."
8600 0395-514 17
ACQUIRE (Acquire Resource)
Examples
Example 1
Before you acquire a unit, you can use the PER (Peripheral Status) command to
display the current peripheral status and to determine if the unit is available to a
group. In this example, the first PER display shows that magnetic tape (MT) units 82
and 83 are not available to a group. The operator then acquires MT 82.
PER MT =
ACQUIRE MT 82
This PER display shows that unit 82 was acquired and automatically readied. The
operator then acquires MT 83 in the saved state.
PER MT =
ACQUIRE MT 83:SAVE
MT 83 WILL BE ACQUIRED
This PER display shows that unit 83 was acquired but not readied:
PER MT
Example 2
This example acquires the designated control units:
18 8600 0395-514
ACQUIRE (Acquire Resource)
Example 3
This example acquires a Telephony Services Platform (TSP) unit:
State Description
Savednot in Module is saved because there have been no requests for it.
use If the domain containing the module is freed, the module is
marked as ready.
You can use the ACQUIRE command only on a domain, or on a module within the
domain, that has been freed. If the domain has already been acquired, you must use
the RY (Ready) command.
The ACQUIRE command does not put additional MSUs into use unless you use the
READY option. You must use the RY (Ready) command to acquire additional
memory.
8600 0395-514 19
ACQUIRE (Acquire Resource)
The configuration on the IEA-1 consists of a single networking port and an Ethernet
port for each physical connection served by the IOP.
The networking port is a device on the IOP that enables the I/O subsystem to access
and manage the networking functions provided by this IOP. This port provides the
connection between the networking software components. Its state controls whether
host networking is active on the IOP. However, the state of the LINEID controls
determines whether the physical connection served by the IOP can be used.
Each Ethernet port contains a LINEID control that enables networking use of the
physical connection. That is, if the port is enabled and the dependent LINEID is
acquired, networking can activate the connection group that is associated with this
physical port.
Acquiring VC Units
To acquire a voice channel (VC) unit, enter the following command syntax:
All 26 units outboard of a voice interface module (VIM) CTL also have the same
number as their VIM CTL. However, unlike the NSP, acquiring the VIM CTL does not
acquire the VC units. You must acquire all 26 VC units outboard of a VIM CTL by
entering a single ACQUIRE VC <unit number> command, which is separate from the
ACQUIRE CTL <unit number> command. For example, if you enter the command
ACQUIRE VC 200, you acquire all 26 VC units. You must also enter the command
ACQUIRE CTL 200 to acquire the VIM CTL.
Acquiring a Disk Pack Associated with the Mirrored Disk Pooling Facility
(MDPF)
When you acquire a disk pack that has been assigned to the free spares pool for a
mirrored disk set, the system generates a status change message. When all the
members of a mirrored set are brought online as in-use spares, the system
generates a status change message for each member. The status change message is
defined in the MCP System Interfaces Programming Reference Manual.
20 8600 0395-514
AD (Access Duplicate)
AD (Access Duplicate)
The AD (Access Duplicate) command duplicates the active access structure or
removes a duplicate structure. If you are running cataloging, the name of the active
access structure is SYSTEM/CATALOG/<family index>; otherwise, its name is
SYSTEM/ACCESS/<family index>.
The system places the duplicate structure on the same family as the original catalog
family, but the duplicate structure must be on a different member of the family. The
name of the duplicate structure is like that of the original structure except that the
family index is different.
By default, the system places the access structure on the halt/load family. You can
change this location by using the DL CATALOG command.
When you enter the AD command, if it is free of syntax errors, the system starts a
visible independent runner named AD. Use the C (Completed Mix Entries) command
to find out if the AD command has completed.
Syntax
Explanation
AD (<family index>)
Creates a duplicate access structure on the catalog family member specified by
<family index>.
AD (<family index>)
Removes the duplicate access structure from the specified member of the catalog
family.
Examples
Example 1
AD (2)
8600 0395-514 21
AD (Access Duplicate)
After you enter the command, the system starts a process called AD. You can check
on the progress of the job by entering one of the following monitoring commands:
Example 2
AD - ON DISK (2)
22 8600 0395-514
ADM (Automatic Display Mode)
Two different modes exist: event-driven automatic display mode (ADM) and time-
driven ADM. With event-driven ADM, any new event for which an option has been
specified is automatically reflected in the updated display. The default delay time for
event-driven ADM is 10 seconds. Time-driven ADM updates its display at specified
intervals.
Syntax
<timed options>
8600 0395-514 23
ADM (Automatic Display Mode)
<printlabel specs>
Explanation
ADM
Displays the current ADM options under which the ODT is operating. If ADM is
canceled, this command sets up ADM with the following default options:
24 8600 0395-514
ADM (Automatic Display Mode)
ADM
Cancels ADM. Any options set up for the ODT are discarded and the default setting is
used for all subsequent initiations of the ADM command.
ADM ST
Stops ADM. ADM instructions are retained but are not executed.
ADM OK
ADM GO
Resume ADM. OK is used after ADM ST, and also to restart ADM after a program has
opened a file that the system has assigned to that ODT and is still using it.
You can specify multiple pages of time-driven ADM by entering more than one group
of timed options enclosed in parentheses. The display rotates from one page to the
next.
A list of the items that can be displayed as timed options follows. The syntax for
each option except PS is the same as for its system command counterpart.
Option Meaning
A Active entries
8600 0395-514 25
ADM (Automatic Display Mode)
Option Meaning
MIX Mix entries by job structure (also includes RSVP and DISPLAY
messages)
S Scheduled entries
U System utilization
W Waiting entries
<number>
The number in the timed options syntax diagram specifies the number of lines to
allow for each item displayed. Two or more lines must be specified for each category
because the heading occupies one line. Lines need not be specified for the last entry
on a page; if lines are not specified, that entry fills the rest of the page. The system
utilization information as well as information for O (Overlay), CU (Core Usage), ASD
(Actual Segment Descriptor), ML (Mix Limit), and PS (Print System) is displayed in
its entirety no matter what value has been specified for the number.
DELAY <number>
Specifies the number of seconds of delay before the next ADM page is to be
displayed.
26 8600 0395-514
ADM (Automatic Display Mode)
ADM EVENT
If the first syntactical item following ADM is the word EVENT, the system
automatically updates the appropriate screen display when a change occurs in the
status of one of the named displays. For example, if the command ADM EVENT W is
entered, the waiting mix list page is displayed whenever the system stops a task
requiring operator attention. No matter how frequently events occur, messages are
displayed only at intervals of DELAY <number> seconds, or 10-second intervals if no
DELAY is specified. EVENT options are as follows.
Option Meaning
A Active entries
MIX Mix entries by job structure (also includes RSVP and DISPLAY
messages)
S Scheduled entries
W Waiting entries
ADM + EVENT
Adds the new ADM instruction to the current ADM specification, which must be for
event-driven ADM.
8600 0395-514 27
ADM (Automatic Display Mode)
Option Description
MCSNAME = <MCS Displays only entries that originated from the specified
name> message control system (MCS)
You can extend the formatting specification by using a plus sign (+) after word ADM.
After this ADM type is set up, the state of the automatic display is marked as
stopped. The proper forms can then be inserted before actual data is received. To
test the formatting specification, enter PRINTLABEL to display a sample tape label
that has all numeric items filled with Ns and all alphabetic items filled with As. Once
the formatting is correct, enter ADM OK to activate the printing of tape labels each
time a tape file is closed.
If nothing follows the word PRINTLABEL, the CONTROLLER sets default values. A site
can change this default setting. The default setting is as follows:
28 8600 0395-514
ADM (Automatic Display Mode)
Examples
Example 1
This example shows the current ADM settings:
ADM
At the beginning of each entry line, E indicates that a syntax error was discovered
during compilation. Each time the ODT screen is updated, new mix entries appear
along with old ones. An asterisk (*) to the left of the mix number means that the job
or task is being displayed on the ODT screen for the first time.
For further information about the various parts of the ADM display, use the
references in the following table.
8600 0395-514 29
ADM (Automatic Display Mode)
Example 2
The ADM (J 10, MSG) 5 command causes the system to display pages with 10 job
lines every 5 seconds. The rest of the page contains message lines.
Example 3
The SORT CPURATE option of the ACTIVE command causes the system to display the
recent processor rates of running programs, in descending order of processor rate.
The display has the following format:
The CPU Rate column shows the recent processor rate (processor time divided by
elapsed time) as a percentage of the total CPU usage over a recent time interval.
The default interval is 20 seconds. This interval can be changed by using the SBP
(System Balancing Parameters) command.
System Limit
The overall system limit is 120 ADM options for all ODTs combined. Each timed
option requested counts as a rule. If an ADM request is made that would bring the
total options specified to more than 120, one of the following error messages is
displayed:
30 8600 0395-514
ADM (Automatic Display Mode)
These error messages can also be displayed during system initialization, when ADM
is initially set up on the ODTs. If either of these error messages occurs during normal
system operation, reduce the number of options in use at the other ODTs.
8600 0395-514 31
AI (Automatic Initiation)
AI (Automatic Initiation)
The AI (Automatic Initiation) command can be used to specify a list of programs that
are automatically initiated when the system is initialized.
The specified programs must not take any run-time parameters. No warnings are
issued if such a program is specified in an AI command. An exception to this rule is
that a program can have a single parameter that is a one-dimensional unbounded
array, in which case the program receives a one word array containing nulls (that is,
4"000000000000").
Syntax
<AI name>
An AI name is an identifier.
Explanation
AI
Displays the list of programs previously specified by AI commands.
AI <AI name>
Displays the entry identified by the AI name.
AI - <AI name>
Deletes an entry identified by the AI name.
32 8600 0395-514
AI (Automatic Initiation)
AI + <file title>
Adds a new entry for the specified code file.
AI - <file title>
Deletes the entry for the specified code file.
Example
AI
AI HARDCOPY = *SYSTEM/HARDCOPY
AI SUPER = *SYSTEM/SUPERVISOR
8600 0395-514 33
ARCCOPY (Copy Archive Directory)
Syntax
Explanation
ARCCOPY <family name> <file title>
The family name indicates the name of the family whose directory is to be copied.
The file title specifies the new name for the backup archive directory when it is
copied. If the specified file title already exists, the system replaces it. Unless you use
the syntax ON <family name>, the system automatically copies the archive directory
to DISK.
Example
The following example copies the archive directory for family PACK and uses the new
name BACKUPARCHIVE/PACK. The system copies the directory to family member 1
of the family named WORKPACK.
34 8600 0395-514
AR (Archive Release)
AR (Archive Release)
The AR (Archive Release) command supports the catalog subsystem, not the archive
(backup and restore) subsystem. It starts the MCP independent runner called
ARCHIVEHANDLER, which releases an old archive log and creates a new one. The
system stores the archive log on the CATALOG family. When the archive log is full (it
holds about 60,000 records), the operating system automatically releases it. When it
is released, an archive log is crunched and marked as a nonsystem file.
To use this command, the cataloging and archiving options must be set. Refer to
CATALOGING (Option 23) and ARCHIVING (Option 28) in the OP (Options)
command.
Explanation
AR
If no file title is specified, the online archive log is released and a new one created.
AR <file title>
If a file title is specified and that file is an archive log, the file is released so that it
can be removed. (Archive logs are system files.) This feature is useful when a
change of the halt/load family causes an archive log to remain on disk as a
nonremovable system file.
Example
AR
MSG
8600 0395-514 35
ARCDUPLICATE (Duplicate Archive Directory)
When you enter the ARCDUPLICATE command, if it is free of syntax errors, the
system starts a visible independent runner named ARCDUPLICATE. Use the C
(Completed Mix Entries) command to find out if the ARCDUPLICATE command has
completed.
Syntax
Explanation
<family name>
Specifies the disk family for which the archive directory is created or deleted.
Examples
Example 1
This example creates a duplicate archive directory for the family named WORKPACK
on family member 2:
Example 2
This example deletes the duplicate archive directory for the family named
WORKPACK on family member 2:
36 8600 0395-514
ARCREPLACE (Replace Archive Directory)
When you enter the ARCREPLACE command, the system starts a visible independent
runner named ARCREPLACE. Use the C (Completed Mix Entries) command to find out
if the ARCREPLACE command has completed.
Syntax
Explanation
ARCREPLACE <family name> <file name> ON <catalog family>
The family name indicates the name of the family whose archive directory is to be
replaced. If no catalog family is specified after the file name, the ARCREPLACE
program assumes that the file in on the DISK family. The file name with the catalog
family name indicates the name of the backup archive directory. This file must
already reside on the catalog family and must be a valid copy of the archive
directory. For more information about the catalog family, refer to the CATALOG
option of the DL (Disk Location) command.
The backup archive directory cannot be in use when the ARCREPLACE command is
executed. After the archive directory has been replaced, the former backup directory
is renamed SYSTEM/ARCHIVE/<family name>/nnn and the old archive directory is
renamed OLD/ARCHIVE/<family name>/nnn.
Examples
Example 1
Example 1 obtains the name of the family name of the catalog:
DL CATALOG
DISK LOCATION:
CATALOG ON DMSIITEST
Example 2
Example 2 closes the archive directory for the family named PACK and replaces that
directory with the file BACKUPARCHIVE/PACK. The file BACKUPARCHIVE/PACK is
then renamed SYSTEM/ARCHIVE/PACK/nnn.
8600 0395-514 37
ARCREPLACE (Replace Archive Directory)
Example 3
Example 3 changes the pack name of a disk from WORK to XPACK, retains all the
files on the family, and changes the name of the archive directory for the family to
match the new name of the family.
38 8600 0395-514
ASD (Actual Segment Descriptor)
Syntax
Explanation
ASD
Displays the following information about the ASD table:
The factor and memory size used to calculate the size of the ASD table at the
last halt/load.
The factor and memory size to be used to calculate the size of the ASD table
at the next halt/load only if the factor was changed from its previous value by
an ASD command.
The number of ASDs in the ASD table.
The percentage of available ASDs currently in use.
The maximum percentage of ASDs actually used at one time since the last
halt/load.
The ASD table entry size, which is the number of words used for each ASD
entry.
ASD <factor>
Specifies the factor to be used to calculate the size of the ASD table at the next and
all subsequent halt/loads. The factor is an integer value that is the estimated
average size (in words) of each memory segment having an allocated ASD. The ASD
table size is inversely proportional to the value of factor. The table size, in units of
ASDs, is calculated according to the following equation:
The total memory is the total physical memory (in words) available online to the
system.
8600 0395-514 39
ASD (Actual Segment Descriptor)
after the next and all subsequent halt/loads. If you did not specify this value (or if
you entered only ASD <factor>), the system uses the available system memory at
the time of the halt/load, which excludes memory reserved for memory disk or disk
cache.
You can use the memory size feature on systems where memory can be added or
removed dynamically without having to perform a halt/load. The feature enables you
to specify in advance that the memory configuration for the system might change
and that the ASD table is to be allocated for a specific amount of memory. You
should specify the maximum expected amount of system memory to avoid running
out of ASDs on the system. Note that you must still perform a halt/load to change
the size of the ASD table.
The system uses a maximum of 25 percent of its memory for the ASD table. If you
specify a memory size that would cause the system to allocate more than the
maximum that is allowed, the system still uses only 25 percent of its memory after
the halt/load.
If you use a specified memory size to calculate the size of the ASD table, the system
displays that value as part of the ASD display, as shown in example 3. If the system
is to use a memory size following a halt/load, it also displays that value, as shown in
examples 2 and 4.
Examples
Example 1
ASD
Example 2
ASD 60
Example 3
ASD
40 8600 0395-514
ASD (Actual Segment Descriptor)
Example 4
ASD 50 28 MEGAWORDS
The minimum, maximum, and default factor values are proportional to the ASD entry
size to maintain a range from 2 to 25 percent of memory used for the ASD table,
with a default value of 8 percent. For an entry size of 4 words, the minimum,
maximum, and default factor values are 16, 200, and 50, respectively. For an ASD
entry size of 8 words, the minimum, maximum, and default factor values are 32,
400, and 100, respectively.
If an ASD command specifies a factor that produces an ASD table size outside the
range, the previous factor value is unchanged and an error message appears.
The memory size option is used to specify a change in the system memory
configuration in advance. Systems that can dynamically change memory allocation
should use this option. The maximum amount of memory that can be allocated to
the ASD table is 25 percent of the actual system memory. System memory does not
include memory reserved for memory disk or disk cache. If the calculated ASD table
size based on the factor and memory size parameters is greater than 25 percent of
the system memory, only the maximum (25 percent) is used.
Any ASD calculations performed by the MCP do not include the system memory that
is dedicated to memory disk and to the Host Memory Cache.
8600 0395-514 41
ASDU (ASD Usage)
Syntax
Explanation
For every job or task in the specified mix number list, the <mix number list> ASDU
command displays the number of ASDs currently in use and the maximum number of
ASDs used since the job or task began.
Example
0007, 1234, 5449 ASDU
42 8600 0395-514
AT (At Remote Host)
Syntax
Explanation
The software determines which service to use for the AT command according to the
following order:
3. Default selection.
The software determines the service most likely able to support the command
and then automatically routes the command to that service.
When HOSTSERVICES (or HS) is specified, the content of the remote system
command is not checked for syntax at the local host, but is transferred to the remote
host. The command syntax must conform to the operator command language of the
remote host and must not violate any security or access control restrictions that are
in effect at that host.
The syntax for FTAM commands is checked at the local host. If there is an error, the
command is not accepted and can be tried again.
The local host name can be used in an AT command only if the remote system
command is NW (Network Prefix) and if the BNAVERSION is BNAV2.
8600 0395-514 43
AT (At Remote Host): Use with Host Services
If the local host name is used in an AT command without these remote commands,
an error is displayed. You should resubmit the command without the AT
<hostname> prefix.
Examples
Example 1
AT BLUE W
Example 2
AT BLUE J
Example 3
AT BLUE 1568 FA TITLE=(USER)A ON DISK
NO RESPONSE GENERATED
The response from the remote host uses the language and conventions defined by
the LANGUAGE and CONVENTION system options of the remote host. For more
information about the LANGUAGE and CONVENTION attributes, refer to the SYSOPS
(System Options) command and to the MultiLingual System Administration,
Operations, and Programming Guide.
44 8600 0395-514
AT (At Remote Host): Use with Host Services
Any remote user can enter Work Flow Language (WFL) jobs. When the system
command containing the job is received, the local alias usercode of the usercode
used to transfer the job is examined. If the local alias usercode is marked as a
SYSTEMUSER, the job runs without a usercode; otherwise, it runs under the local
alias usercode. If the job contains a usercode, it runs under that usercode.
A remote user who is not a SYSTEMUSER can use the following system commands to
monitor jobs and tasks running under that usercode.
Command Meaning
AX Accept
CU Core Usage
DS Discontinue
FA File Attribute
FR Final Reel
HI Cause EXCEPTIONEVENT
MX Mix Entries
NF No File
OF Optional File
OK Reactivate
8600 0395-514 45
AT (At Remote Host): Use with Host Services
Command Meaning
RM Remove
SQ Show Queue
ST Stop
TI Times
Y Status Interrogate
In addition, a remote user who is not a SYSTEMUSER can also use the following
commands to display the status of the system.
Command Meaning
CS Change Supervisor
CU Core Usage
MM Memory Module
SC System Configuration
SI System Intrinsics
SL Support Library
WM What MCP
46 8600 0395-514
AT (At Remote Host): Use with FTAM
When FTAM services are requested, the command text can also include an optional
USER statement. The USER statement can contain the usercode, password, and
account information. The following diagrams show the syntax for the USER
statement and the FTAM file management commands.
Syntax
USER statement
<log-on info>
After all the delimiters are stripped out, the three components are interpreted by
FTAM in the following way:
The log-on information values are optional with the USER statement and with
each other. If the password is specified, the right slash (/) is required. All
specified values must be valid. If a value is invalid, a diagnostic message is
returned and the AT command must be corrected and entered again.
8600 0395-514 47
CHANGE (FTAM File Management Command)
The USER statement must contain a value when it is used. If you do not use a
specific value for the usercode, you can specify the null value by using two
double quotation marks ("") as shown in the following examples:
USER = "";<file command>
Syntax
Explanation
The first universal file name must specify an existing file at the remote host and
must also include a volume identification.
Syntax
Explanation
The universal file name specifies the directory and name of the file. The returned
information about the specified file includes the file name and the DOCUMENTTYPE
attribute value. If a universal file name is not specified with the FILES command, a
list of all available files, containing the FILENAME and DOCUMENTTYPE attributes are
returned.
PERMITTEDACTIONS
DOCUMENTTYPE
48 8600 0395-514
MODIFY (FTAM File Management Command)
CREATIONDATE
ALTERDATE
LASTREADDATE
FILEAVAILABILITY
FILESIZE
The software returns the message NOT SUPPORTED when you enter an attribute that
is not supported by the remote host.
Syntax
<FTAM attributes>
Explanation
The universal file name specifies the directory or name of the file. The file name and
the values of any specified attributes are returned by the remote host. If a file name
is not specified with the LFILES command, a list of all available files is returned. The
values of all attribute values specified with the command are returned as part of the
file list. If no attributes are specified, all file attribute values are returned.
Syntax
8600 0395-514 49
MODIFY (FTAM File Management Command)
<attribute list>
Explanation
The universal file name specifies the directory and name of the file.
The storage account specifies the account that is responsible for file storage charges.
The file availability indicates whether a delay is expected before the file can be
opened.
The future file size indicates the nominal size in octets to which the file can grow.
When the remote host starts to process a MODIFY command, it notifies the local host
about which classes or groups of attributes are supported. If none of the specified
attributes is supported, the command is not sent to the remote host and the local
host displays the following response:
If one or more attributes is supported, the remote host processes the command.
Supported attribute values are changed, as requested. Unsupported attributes are
not processed; the remote host returns the following response:
***** FTAM HOST <remote host name> DOES NOT ALLOW USE OF THE
<attribute name> ATTRIBUTE *****
Certain attributes might be recognized by the remote host, but the specified value is
not valid. If a request contains one or more valid attribute values, the remote host
processes the valid attributes and ignores the invalid ones. The remote host returns
the following message if the command results in one or more successful attribute
modifications:
If the same attribute is specified more than once, the last specified value is used.
The remote host returns the following response:
50 8600 0395-514
REMOVE (FTAM File Management Command)
Syntax
Example 1
This example inquires about all files on the specified host:
Example 2
This example specifies a usercode and password with the USER statement. Because
the usercode is used as the file directory, the command inquires about all files on the
specified host that are contained in the file directory.
Example 3
This example shows two commands that access detailed information about all files.
The first command requests all information, and the second commands requests only
information about the date the files were last altered.
Example 4
This example inquires about all files with the specified file name on a remote host
that is not an MCP system. File names that do not conform to the MCP file name
syntax are enclosed in apostrophes (' ').
Example 5
This example changes the name of a file on the remote host:
8600 0395-514 51
REMOVE (FTAM File Management Command)
Example 6
This example removes the specified file:
Example 7
This example changes the file name attribute of a file that belongs to the $AB
usercode:
Example 8
This example changes three attributes of a file named X:
52 8600 0395-514
AUTORESTORE (Archiving AUTORESTORE Option)
Syntax
Explanation
AUTORESTORE
Displays the current value for the archiving option.
AUTORESTORE DONTCARE
Sets the default value of the AUTORESTORE task attribute to FALSE for every task.
AUTORESTORE NEVER
Specifies that the archiving restoration process is not to be started automatically
when a NO FILE condition occurs. This value overrides the AUTORESTORE task
attribute value for all tasks and jobs.
AUTORESTORE YES
Sets the default value for the AUTORESTORE task attribute to TRUE for every task.
The archiving restoration process is automatically started when a NO FILE condition
occurs.
Example
The following example specifies that the system never automatically starts an
archiving restoration process.
AUTORESTORE NEVER
8600 0395-514 53
AX (Accept)
AX (Accept)
The AX (Accept) command passes text to a program. This transfer of text can be in
response to, or in anticipation of, a task requesting an ACCEPT message.
Syntax
Explanation
<mix number list> AX <user text>
Passes the specified user text to the tasks in the mix number list when they request
an ACCEPT message. User text cannot exceed 960 characters, exclusive of any
leading colon. To send lowercase characters to a program, enclose the <user text>
in quotation marks. Both the quotation marks and the <user text> are sent to the
program.
Example
In the following example, an AX command is entered in response to an ACCEPT
message from the task named TEST:
54 8600 0395-514
AX (Accept)
If you enter SYSOPS QUEUEDAX RESET and if the system has already queued some
messages, subsequent ACCEPT messages issued by a task continue to take
messages from the front of the queue until the queue becomes empty. However, the
next AX command produces the following results:
Caution
AX input goes to the next ACCEPT action performed on the stack, whether this
act is performed by library code or the code of the program. This process
might cause AX messages to be unintentionally routed to a library when they
were intended for the client task.
8600 0395-514 55
BADFILE (Bad File)
Syntax
Explanation
When an error occurs on tape while library maintenance is copying from tape, you
can use this response to direct library maintenance to continue copying the file to
disk even though the resulting file will contain some corrupted data. Library
maintenance changes the names of the output disk files so that the node BADFILE is
attached to the beginning of the file name. Library maintenance also stores a
summary of the errors that occurred in the BADINFO disk file header attribute. For
output tape files, library maintenance treats the BADFILE response like an OF
(Optional File) responsethat is, it does not copy the corrupted file to tape.
Example
MSG
1970 BADFILE
MSG
56 8600 0395-514
BNA
BNA
The BNA command initiates and terminates the portion of BNA Version 2 that
provides for Program Agent access, and handling of a subset of BNA Version 2
commands. After you issue a BNA + command, BNA is considered to be in isolated
mode. When BNA terminates, its state is considered to be not running. To provide
full BNA capabilities, you must issue the NW NET + command. For complete
information on the NET command, refer to the Networking Commands and Inquiries
Help.
Syntax
Explanation
BNA
Indicates whether BNA is available.
BNA
Moves BNA Version 2 to a not running state from the mode it was in previously.
BNA +
Moves BNA Version 2 from a not running state to isolated mode.
Examples
Example 1
BNA
BNA IS AVAILABLE
NEXT INIT/INFO FILE WILL BE *BNAV2/INIT/TRPROGD/TCPIP
Example 2
BNA +
Example 3
BNA -
The message BNAV2 IS UNAVAILABLE appears only after BNA shuts down. This
process might be lengthy.
8600 0395-514 57
BNA
BNAMEMOSUPPORT
BNASUPPORT
CNSMANAGERS
CNSSUPPORT
CNSTRANSLATION
NPSUPPORT
Before you can use Heritage Host Services, you must specify the DSSSUPPORT
library with an SL command. However, the DSSSUPPORT library is not a required
library. You must also specify the PASCALSUPPORT library before BNA Version 2 can
be initialized.
For information about BNA Version 2 reinitialization after a halt/load, refer to the
description of option 40 in the OP (Options) command.
58 8600 0395-514
BNAVERSION
BNAVERSION
The BNAVERSION command specifies the version of. BNA to bring up after the next
halt/load. This command can also display the version of BNA already in use.
Syntax
Explanation
BNAVERSION
Displays the BNA version currently in use.
BNAVERSION = BNAV2
Specifies that BNAV2 is to be brought up after the next halt/load.
8600 0395-514 59
BR (Breakout)
BR (Breakout)
The BR (Breakout) command initiates a checkpoint for a task. This command applies
only to tasks, and is rejected when applied to jobs. For more information about task
management, refer to the Task Management Programming Guide.
Syntax
Explanation
<mix number> BR
Displays the status of a task for checkpoint and recovery purposes.
The response to this form of the BR command depends on the value of the task
CHECKPOINTABLE and BRCLASS attributes. If the CHECKPOINTABLE attribute is
TRUE, a checkpoint can be initiated. A TRUE value does not imply that a checkpoint
will be successful. If the BRCLASS attribute is NOBR, a checkpoint cannot be initiated
for the task. The BRCLASS attribute is set by the programmer.
<mix number> BR +
Initiates a checkpoint for a task, if allowed.
<mix number> BR
Cancels an unsatisfied BR + request.
Examples
Example 1
1234 BR
If you are not allowed to use the BR command to initiate a checkpoint for this task:
60 8600 0395-514
BR (Breakout)
Example 2
2345 BR +
Either message indicates that you have already sent a BR + command for this task,
and the checkpoint has not yet been initiated. The BR command can be used to
cancel the request at this time.
Example 3
5678 BR
A checkpoint is being taken for this task. The checkpoint might be a programmed or
an operator-initiated checkpoint. In the latter case, the phrase (CANNOT CONTINUE
AFTER BR), if present, indicates that the task is not allowed to continue at the end
of the checkpoint.
At the completion of the checkpoint, you can nullify the BR request with an OF
(Optional File) command.
Example 4
6789 BR
The task is being restarted from a checkpoint. The word PROGRAM indicates that the
checkpoint was created by the program. The word ONCEONLY indicates that the
checkpoint is to be removed at the end of the restart phase. The word MULTIPLE
indicates that the checkpoint is to be kept after the completion of the restart phase.
The phrase (CANNOT CONTINUE AFTER BR) appears if the BRCLASS attribute is set
to ONCEONLY for either the job or the task.
8600 0395-514 61
C (Completed Mix Entries)
Syntax
Explanation
C
Lists recently completed jobs and tasks. The number of jobs and tasks displayed is a
function of the TERM LINES and TERM FIRST values of the ODT. For more
information, refer to the TERM (Terminal) command.
C FULL
Specifies that the system is to display all available completed entries, for a maximum
of the specified value of the MAX COMPLETED command. Refer to the MAX
(Maximums) command.
C USER <usercode>
C FULL USER <usercode>
Specifies that the system is to display only those completed entries that ran with the
specified usercode. The system searches the entire list, for a maximum of the
number previously specified by the MAX COMPLETED command. Refer to the MAX
(Maximums) command.
Examples
Example 1
This example shows a general response to the C command:
62 8600 0395-514
C (Completed Mix Entries)
The heading line appears on the first page of the Completed Entries display and on
the ADM display of completed mix entries.
The header Hist stands for history. History is the term used for reason for
termination. Reasons for job and mix termination are as follows.
Reason Description
The name of the task or job is shown, prefixed by the usercode of the originator.
8600 0395-514 63
C (Completed Mix Entries)
Example 2
This example shows the response to a request that the system display only those
completed entries that ran with the usercode PDW:
C USER PDW
64 8600 0395-514
CA (Candidate)
CA (Candidate)
The CA (Candidate) command displays the BNAV2 candidates for those unmatched
local subports and remote subports whose HOSTNAME attribute equals the local host
name. A candidate is a subport that is offered for use but not yet matched
(connected) to another subport.
Syntax
Explanation
CA
CANDIDATE
Displays the following attributes for each candidate.
MY CODEFILE INTNAME
AVAILABLE ONLY
CA <port name>
Displays those candidates whose port names (TITLE file attribute values) are equal
to <port name>.
8600 0395-514 65
CA (Candidate)
Example
The following example shows a candidate display:
CA NETCONTROLPORT
FILENAME = NETCONTROLPORT
MY HOST = RED MY HOST GROUP = COLORS
APPLICATION GROUP = *BNA_CNTRL_AGENT MY USERCODE =
REQUESTED CHAR SET = EBCDIC TRANSLATE = NOTRANS
OFFER TYPE = NO OFFER MATCHING STATUS = NOT OFFERED
MY NAME = LCF YOUR NAME = REMOTESYSTEMCONTRO
MY CODEFILE = *SYSTEM/CNS/SUPPORT ON PACK
USING PROCESS = 2952/2952 INTNAME =
SUBPORT INDEX = 12 YOUR HOST =
YOUR HOST GROUP =
REQUESTED YOUR USERCODE =
AVAILABLE ONLY - IGNORE DIRECTORY +
SECURITY TYPE = PRIVATE
66 8600 0395-514
CACHE (Disk Cache)
Syntax
<megaword limits>
<gigaword limits>
Explanation
CACHE
Displays the following information:
The number of disk units that are currently under the control of the disk caching
subsystem
The ration of disk cache read hits to cache requests for all cached disks within
the last sampling interval
The total number of cache requests for all cached disks within the last sampling
interval
The overall data transfer rate of data for all cached disks within the last sampling
interval
Traffic statistics for each cached disk within the last sampling interval
8600 0395-514 67
CACHE (Disk Cache)
Examples
Example 1
CACHE
Caching Packs
The number of online packs you are currently caching. Each cached mirrored set
counts as one pack, and packs that are closed or are without a path are not
counted.
Overall ReadHits/Requests
The percentage of cache requests that were read hits.
Cache Size
The size of the disk cache. Mwords indicates that the size is in megawords.
Reqs/Sec
The average number of cache requests per second.
Kbytes/Sec
The average number of kilobytes per second requested by cache requests.
68 8600 0395-514
CACHE (Disk Cache)
Unit Statistics
The rest of the displayed information is unit statistics. In order for a unit to be
included in the display, at least one cache request must have been entered for that
unit during the preceding time interval. Inactive units and noncached units are not
included in this display.
Reqs/Sec
The average number of cache requests for this unit per second.
% Rhit/Read
The percentage of read requests for this unit that were read hits.
% Read/All
The percentage of all requests for this unit that were reads.
% Rhit/All
The percentage of all requests for this unit that were read hits. This column is
always equivalent to the product of the previous two columns.
Kbytes/Sec
The average number of kilobytes per second requested by cache requests for this
unit.
Example 2
This example turns on caching for disk pack 149:
CACHE + PK149
Example 3
This example turns off caching for disk pack 149:
CACHE - PK149
Example 4
This example resizes cache memory to 16 megawords:
8600 0395-514 69
CC (Control Card)
CC (Control Card)
The CC (Control Card) command directs the system to pass the subsequent Work
Flow Language (WFL) statement on to the WFL compiler for processing. A synonym
for CC is a question mark (?).
Syntax
Examples
Example 1
The following command passes the WFL statement MOVE XYZFILE TO NEWFAMILY to
the WFL compiler for processing:
Example 2
The following command passes the WFL statement RESTORE XYZFILE ORIGIN
NEWFAMILY FROM ATAPE; to the WFL compiler for processing:
Note: Certain WFL statements do not require any special construct or command
when entered at an ODT; they are automatically passed to the WFL compiler. Other
WFL statements cannot be entered at an ODT at all. Refer to Starting Work Flow
Language (WFL) Jobs at an ODT for more information.
70 8600 0395-514
CF (Configuration File)
CF (Configuration File)
The CF (Configuration File) command displays the title of the current configuration
file or designates a new title. A configuration file is created by the
SYSTEM/CONFIGURATOR utility. The input to this utility and the file created by the
GC (Group Configuration) command are not suitable for use as the configuration file.
The family name provided in the ON-part of the <file title> if <file title>
contains an ON-part.
The family labeled DISK if the <file title> provided contains no ON-part.
Additional verification is done to ensure that the FILEKIND attribute of the
designated <file title> is DATA, and that the designated family is NOT a shared disk
family.
Upon successful verification, all allocated rows of the designated file are relocated to
the base unit of the designated family if necessary. System tables are updated to
reflect the <file title> as being the selected configuration file for use by subsequent
system reconfiguration actions.
If you did not specify a configuration file or if the file does not exist, when you issue
a RECONFIGURE GROUP command, the RECONFIGURE GROUP command terminates
with the following message:
Syntax
Explanation
CF
Displays the title of the current configuration file.
CF +
Designates SYSTEM/CONFIGURATION, the default title, as the configuration file.
CF
Removes the designation of a configuration file from the system tables.
8600 0395-514 71
CF (Configuration File)
CF <file title>
Designates the file specified by <file title> as the configuration file. This file must
have a file type of DATA.
Examples
Example 1
CF XYZ
Example 2
CF
Example 3
CF NEW/CONFIG ON MYFAMILY
Example 4
CF+
72 8600 0395-514
CHECKFILE (Check for Nonresident Files)
Although the SL (Support Library) command checks for the residence of the code file
when you first define a function name mapping, the code file can be removed later.
When CHECKFILE finds a function name that points to a missing code file, you must
determine whether the code file needs to be restored or the function name is no
longer needed and can be deleted.
Syntax
Explanation
CHECKFILE SL
Displays the function names and file names of all functions that are assigned to files
that are not resident on disk.
CHECKFILE SL *
Displays the function names, file names, and attributes of all functions that are
assigned to files that are not resident on disk.
Examples
Example 1
CHECKFILE SL
8600 0395-514 73
CHECKFILE (Check for Nonresident Files)
Example 2
CHECKFILE SL *
74 8600 0395-514
CL (Clear)
CL (Clear)
The CL (Clear) command clears all exception flags maintained by the operating
system for a peripheral unit, and, in some cases, clears the FORMID for the unit and
terminates tasks that are using that unit. The FORMID for the unit is not cleared
when the unit is in use and you enter the CL command.
Syntax
Explanation
CL <device type> <unit number list>
Clears the devices in the specified unit number list.
Note: If you clear a device assigned to a task, the task might be discontinued
immediately.
Examples
Example 1
This command requests that the operating system clear tape unit 116. The system
response shows that it has cleared the unit:
CL MT 116
MT 116 CLEAR
Example 2
This command clears line printers 10 through 12. The system responses show that it
has cleared units 10 and 12. Because an I/O operation on LP11 is still in process
when you issue the command, the CONTROLLER returns the WILL BE CLEAR
message for that unit.
CL LP 10-12
LP 10 CLEAR
LP 11 WILL BE CLEAR
LP 12 CLEAR
8600 0395-514 75
CL (Clear)
Example 3
This example clears a Telephony Services Platform (TSP) unit:
CL TSP 200
TSP200 CLEAR
No Yes CANCEL
No No None
Yes No CANCEL
No Yes DS
No No None
76 8600 0395-514
CL (Clear)
Action Codes
The action codes shown previously are defined as follows.
Code Description
DS All queued I/O operations are canceled, and the task using the unit is
discontinued with a DS (Discontinue) command. However, DS does not
override a previous QT (Quit) command if the unit is controlled by the
print server.
DS* Same as DS except that, if the unit is a printer in use by the print
server, the task is terminated with a QT command instead of a DS
command.
CANCEL All I/O operations to the unit are canceled until subsequent operating
system or operator action occurs. For example, you must release packs
with a CLOSE (Close Pack) command.
If a tape unit that is in use is assigned to a task, the system discontinues the task if
it was not already terminated with a QT (Quit) command.
The following table explains the special effects that the CL command can have on
certain kinds of units. In general, all queued I/Os are marked as canceled.
Device Effect
LP Clears the FORMID for the unit or terminates the tasks that are using
that unit. The system does not clear the FORMID for the unit when the
unit is in use and you enter the CL command.
8600 0395-514 77
CL (Clear)
Device Effect
MT Causes the tape to rewind and the label to be reread. This is a handy
way to sometimes resolve an unwanted UNLABELED PER MT
indication. If an I/O is outstandingsuch as at the drive or in the tape
controllerthe physical I/O subsystem waits for the I/O to complete. In
some cases, this wait can last for several minutes before the CL MT
command actually takes effect.
PK On IOM systems, all queued disk I/O operations are returned with a
canceled result descriptor. Therefore, any program that uses direct I/O
can handle an exception result descriptor by including the appropriate
code. All subsequent I/O operations are canceled until the disk pack is
closed by the command CLOSE PK<unit number>. Otherwise, data
could be corrupted if some I/O operations were allowed to resume after
other I/O operations were canceled. In this state, the pack is shown as
BLASTED in the response to the PER PK command. To close a disk pack
you must close all open files. The disk pack can then be readied back
onto the system. If the ready action is successful, access to the unit is
allowed.
TSP If you are using Telephony Services Platform (TSP) units, you can clear
a unit by entering the following syntax:
CL TSP <external unit number>
The system clears a TSP unit in the same manner as a VC unit. That is,
user tasks are never discontinued; they are always canceled. You must
enter a command once for each TSP unit that you want to clear.
Note: You cannot use the CL command to clear a path. You must use the UR (Unit
Reserved) command for path manipulations. The CL VC and CL TS commands never
cause user tasks to be discontinued; they are always canceled.
78 8600 0395-514
CLOSE (Close Pack)
You can use the CLOSE command to bring a pack from an online state to an offline
state. A disk is online to the system if all the following conditions are true:
The disk pack is mounted on a unit that has been logically connected to the
system with the ACQUIRE (Acquire Resource) command.
The disk pack is mounted on a unit that has not been reserved with the UR
(Unit Reserved) system command.
The disk pack has not been logically detached from the system with the
CLOSE (Close Pack) or FREE (Free Resource) command.
The label and flat directory of the disk pack have been read successfully.
A disk pack is offline to a particular system if any of the previous criteria have not
been met.
You can use the CLOSE command to prevent the system from using a particular disk
pack. You can reserve the closed pack by using the UR (Unit Reserved) command,
save the closed pack by using the SV (Save) command, or free the closed pack by
using the FREE (Free Resource) command.
You cannot close a disk pack for any of the following reasons:
Files on that pack are open at the time you enter the command, unless you
use the DS (Discontinue) option.
The pack family is the halt/load family.
The pack family is one of the overlay families.
The pack family is the log family.
The entire pack or the family base pack is in use by the MCP.
MCP tasks that use an entire pack include the following:
RY (Ready)
MIRROR CREATE
SQUASH (Consolidate Disk Allocation)
RES (Reserve)
DD (Duplicate Directory)
RC (Reconfigure Disk)
LB (Relabel Pack or Host Control Unit)
PG (Purge)
Use either the SHOWOPEN (Show Open Disk Files), PER (Peripheral Status), or OL
(Display Label and Paths) command to check for open files and to identify the tasks
that are using them. The SHOWOPEN command also indicates whether the family is
8600 0395-514 79
CLOSE (Close Pack)
the halt/load family, one of the overlay families, or the log family, and whether the
entire base pack or family base pack is in use by the MCP, and it lists the files that
are open on the disk and the tasks that are using those files. You can force a pack to
close by using the :DS option if none of the open files is critical to the system.
If the command is rejected, wait for the current command to complete and enter the
command again.
The CLOSE command also performs the same functions for compact disk units.
Syntax
Explanation
CLOSE PK <unit number list>
CLOSE CD <unit number list>
Close the pack or compact disk unit specified by the unit number list.
If you want to verify that the disk pack or compact disk unit is closed, you can use
the PER (Peripheral Status) command. If the PER command shows that the disk pack
or compact disk unit is closed, you can use the RY (Ready) command to make the
disk pack or compact disk unit available to the system again.
If the disk pack is mirrored, all members of the set are closed. In addition, the
members are marked as matchingwhich indicates that the entire set has been
taken offline in an orderly fashionand are removed from the system mirror
structures.
80 8600 0395-514
CLOSE (Close Pack)
CD-ROM and then close the pack. Refer to the SHOWOPEN (Show Open Disk Files)
command for information about finding users of a pack. Note that it might still be
impossible to close the pack if the MCP considers it to be in use.
If program termination was started but was not completed, the system displays the
following message:
After the system displays this message, you can check the status of the pack by
using the PER <unit number> command. The status of the pack should be BLASTED.
You can then use the CLOSE <unit number> command to close the pack.
Examples
Example 1
This example closes a disk pack, checks the status of the pack, and readies the
device for use:
CLOSE PKO65
PER PK
-----PK STATUS-----
65*U C L O S E D
RY PKO65
Example 2
This example closes PK066 and cancels all queued I/O operations on that pack:
CLOSE PKO66:DS
8600 0395-514 81
CLOSE (Close Pack)
Example 3
This example closes a CD unit, checks the status of the unit, and readies the device
for use:
CLOSE CD 1302
CD 1302 CLOSED
PER CD
-----CD Status------
1302 C L O S E D
RY CD 1302
You can sometimes use the CLOSE command, followed by the RY (Ready) command,
to clear a pack with a LABEL ERROR, because the MCP must attempt to reread the
label (by itself, the RY command cannot resolve a label error). This technique works
well if the label error was caused by a transient read error.
Closing a mirrored set removes all information pertaining to that set from the
mirroring structures of the MCP. This includes information used by MDPF to replace
or recreate members of the set. Any deferred creations pending in Assistant for a set
that is closed are not initiated.
82 8600 0395-514
CM (Change MCP)
CM (Change MCP)
The CM (Change MCP) command provides the following capabilities:
Displays the status of the MCP on the halt/load pack, on a specified disk
family, or on all disk families that contain a halt/load capable MCP
Cancels a pending CM action
Displays the name of the next MCP to be used, if any
Halt/loads the system and changes the current MCP to a permanent or a
temporary MCP
Converts a temporary MCP to a permanent MCP
Alters the status of the current halt/load pack
Causes the system to use multiple copies of the MCP
Establishes the halt/load capability for a family
Alters the status of a family
Cancels the halt/load capability of a family
Syntax
8600 0395-514 83
CM (Change MCP)
<hldump option>
<options>
Explanation
CM
Displays the name of the next MCP, if a CM <file name> command is pending.
CM?
CM? ON <family name>
Display the MCP name, creation date, the family indexes on which an MCP was
specified in a previous CM command, the HLDUMPDISK setting, and the next MCP to
be used. If the current MCP is a temporary MCP, the MCP name is displayed as
PENDING. If a delayed MCP is present, that MCP name is displayed. If you do not
specify a family, the system displays the information for the halt/load family.
The response to the CM? command also lists the standby halt/load packs of the
current halt/load pack. The response to the CM? ON <family name> command lists
the standby halt/load packs of the specified pack.
CM ? ALL
Causes the equivalent of a CM? ON <family name> command to be performed for all
disk families that contain a halt/load capable MCP (one that has been specified in a
previous CM command). In addition to the information normally displayed by the
CM? ON <family name> command, the display includes:
84 8600 0395-514
CM (Change MCP)
These forms of the command establish the new MCP code file on the same family
member or members that currently have an active MCP code file.
If you specify the number sign (#), the change in the MCP is temporary. After the
initial halt/load to change to the new MCP, any subsequent halt/load makes the
system revert to the operating MCP code file in use before you executed the CM #
<file name> command.
If the change is temporary, the bootstrap continues to point to the old MCP code file.
A subsequent halt/load causes a return to the old operating system. If the change is
permanent, the old MCP code file can be removed after the halt/load to the new MCP
code file.
After it locates the new MCP code file, the CHANGEMCP process checks for a null
mix; if the mix is not null, CHANGEMCP appears in the list of waiting entries. The
waiting MCP change is called a pending change. (Libraries such as GENERALSUPPORT
do not constitute mix entries.) In contrast, the primitive version of the CM command
(??CM) does not wait for a null mix count. Refer to the ??CM (Change MCP)
command.
Note: It is usually difficult or impossible to terminate every task and job in the mix.
Therefore, it is usually mandatory that you use the primitive version of the
CM command (??CM) to change the executing MCP. But the primitive ??CM command
does not have all the features of the normal CM command. For example, the
primitive ??CM command does not allow you to use the index list option. When you
need to invoke one of these special features, proceed as follows:
CM ON <familyname>
Remove halt/load capability from a family or specific members of that family (the
index units). The system locates the MCP code file (and any duplicate MCP code files)
and resets the system file bit for each of these files. If the family is a standby
halt/load family, the system implicitly removes that status. If the family has a
delayed MCP, the system removes the reference to the delayed MCP.
8600 0395-514 85
CM (Change MCP)
You might want to use this form of the command when you have established a
delayed MCP on a family. Then, rather than performing a halt/load operation on that
family, you used the HLUNIT command to switch to another halt/load family and
subsequently halt/loaded it. However, the delayed MCP is still linked to the original
unit. Using the CM ON <family name> :DELAY form of the command delinks the
delayed CM from the original family.
Use this form of the CM command to establish halt/load capability for a family. To
start up on the new MCP, use the HLUNIT (Halt/Load Unit) command to designate
the unit as the new halt/load family, and then perform a manual halt/load.
If you have not performed a CM command on the designated family, this form of the
command puts the new MCP code file on the base pack of the designated family. If
you have previously performed a CM command on the designated family, this form of
the command establishes the new MCP code file on the same member or members of
the family that the previous command did.
When you create a family with halt/load capability, you must copy SYSTEM/KEYSFILE
to that family, and re-copy the file when it is updated as the result of an IK (Install
Keys) command. The MCP uses the keys file on the halt/load family, and absence of
run-time keys might result in programs failing to run, and security options being
reset.
CM : DELAY
Removes the reference to the delayed MCP.
CM :PERM
Transforms the current MCP from a temporary MCP to the permanent MCP by
updating the bootstrap to point to the new MCP. This version of the command is
valid only when used on a temporary MCP (for example, CM #).
86 8600 0395-514
CM (Change MCP)
If the CM command is for the current halt/load family, to ensure that the CM
command takes effect, perform the following sequence of steps:
If the list is omitted, the current list is used. If no list is in use, only the base unit is
assumed. Observe the following guidelines:
<options>
The following options apply to the CM command:
+ HLDUMPDISK
Causes the system to search the specified family for a
SYSTEM/HLDUMPDISK/<nnn> file. If the system finds one, it verifies that the file
is a usable dumpdisk file. If the system does not find a usable
SYSTEM/HLDUMPDISK/<nnn> file, it creates one. If you include a
[<kilosectors>] specification, the new file has the specified capacity. Otherwise,
you must supply the desired capacity for a new dumpdisk file in response to an
AX (Accept) message.
When the + HLDUMPDISK option applies to the current halt/load family, the
SYSTEM/HLDUMPDISK/<nnn> file immediately becomes a dumpdisk file in use.
If you have enabled dumpdisk capabilities through both the DN (Dump Name)
and CM + HLDUMPDISK commands, the system uses the HLDUMPDISK file for
dumps that occur during system initialization and then uses the file named in the
DN command for subsequent dumps.
8600 0395-514 87
CM (Change MCP)
For more information about dumpdisk files, refer to the DN (Dump Name)
command.
CM + STANDBY ON <family name>
Causes the specified family to become a standby halt/load family for the current
halt/load family. The specified family must already be a halt/load capable family.
Whenever data such as configuration information or the mirror information table
(MIT) is preserved on the halt/load family, that data is also preserved on all
online standby halt/load families of the current halt/load family. An example of
configuration information data is the FREE/ACQUIRE/UR/UR status of units and
data link processors (DLPs), disk locations (DLs), support libraries (SLs), memory
disk and disk cache specifications. In this way, all the information transferred to
the target families during the execution of the original CM <file name> ON
<family name> command is kept continuously up to date. The information on
online standby halt/load family is always current. If the current halt/load family
fails, one of its standby halt/load families can be used without concern as to
when a CM operation was last performed on it.
Note that although disk location (DL) specifications are kept up-to-date on all
online standby halt/load families, the files located by way of these specifications
(such as backup files, log file, and JOBDESC file) are maintained only on the
specified families.
When you create a standby halt/load family, you should copy SYSTEM/KEYSFILE
to that family, and recopy the file when it is updated. The MCP uses the keys file
on the halt/load family, and absence of run-time keys can result in security
options being reset. When these options are reset, they are also reset on all
other standby halt/load families.
The system preserves a self-inclusive list of standby halt/load families on the
current halt/load family and on its standby halt/load families. Thus, if you make B
a standby halt/load family for A, A automatically becomes a standby halt/load
family for B.
If the system does not find a given standby halt/load family for the current
halt/load family after a halt/load, its specification remains in the list of standby
halt/load families. The system issues the following message: STANDBY H/L UNIT
<family name> NOT FOUND. Failure to respond to this RSVP message does not
delay completion of system initialization.
The response to a CM? command indicates the offline status of these standby
halt/load families. If the status of the standby halt/load family changes to online
and the unit is still halt/load capable, the system updates it so that its preserved
data structures are current, and the family remains a standby halt/load family for
the current halt/load family. If the status of the standby halt/load family changes
to online but the family is not halt/load capable, the system removes it from the
list of standby halt/load families for the current halt/load family. The system
issues the following message:
88 8600 0395-514
CM (Change MCP)
You can close a standby halt/load family for the current halt/load family and
place it in the same offline state described in the previous paragraph; the system
does not delete it from the standby halt/load families for the current halt/load
family.
CM <file name> ON <family name> + STANDBY
Causes the specified family to be made halt/load capable and to become a
standby halt/load family for the current halt/load family. (If you do not specify
+ STANDBY, the specified family does not become a standby halt/load family at
the end of the operation, whether or not it had been at the start.)
CM STANDBY ON <family name>
Causes the specified family (which must already be a standby halt/load family )
to no longer be a standby halt/load family. The specified family remains halt/load
capable. The specified family must already be a family with halt/load capability.
Examples
Example 1
This example displays the name of the next MCP.
CM
MCP: SYSTEM/51145/MCP/DELTA/DIAG
NEXT MCP: *SYSTEM/MCPD/51122
Example 2
This example changes the MCP code file on the current halt/load family to the
specified file name. However, the change in the MCP is only temporary. After the
initial halt/load to change to the new MCP, any subsequent halt/load makes the
system revert to the previous MCP code file that was in use.
CM # SYSTEM/DELTA/MCP511
Example 3
This example changes the MCP code file on the current halt/load family to the
specified file name
CM SYSTEM/DELTA/MCP511
Example 4
This example produces a display of the MCP name, creation date, family indexes on
which an MCP was specified in a previous MCP command, and the HLDUMPDISK
setting. This information is applicable to the halt/load family.
8600 0395-514 89
CM (Change MCP)
CM ?
CM STATUS :
MCP : *SYSTEM/DELTA/MCP/511 ON DISK
CREATION DATE : Thursday November 17, 2005 (2005321)
CM'ED MCP ON FAMILY INDEX : 1
HLDUMPDISK : SET
Example 5
This example shows the display for a CM query. Notice that a delayed MCP is listed.
CM?
CM STATUS:
MCP : *SYSTEM/MCP/DELTA/DIAG ON TESTPACK
CREATION DATE : Monday, August 30, 2004 (2004243)
CM'ED MCP ON FAMILY INDEX : 1
HLDUMPDISK : RESET
DELAYED MCP: *SYSTEM/MCP/DELTA/DIAG/DELAYED
Example 6
This example produces a display of all disk families that contain a halt/load capable
MCP.
CM ? ALL
Example 7
This example creates a halt/load DUMPDISK file on the halt/load family.
CM + HLDUMPDISK
90 8600 0395-514
CM (Change MCP)
You can supply one copy of the MCP code file, and the CM procedure produces
the extra copies that are needed and gives them names that include
FMLYINX<nnn>. The chief disadvantage of this method is loss of profitable
system timewhile the CM procedure is running, the rest of the system is
idle.
You can make two or three copies of the code file yourself before you execute
the CM command. The disadvantage of this method is that it is more difficult
to make the copies correctly.
If the CM command is for the current halt/load family, to ensure that the CM
command takes effect, perform the following sequence of steps:
1. Copy the MCP code file to the halt/load family or the family for which you
want to issue the CM command.
2. Issue the CM command with the file name and the index unit list of the family
members that are to receive the duplicated copies of the MCP code file.
The command syntax for the halt/load family is as follows:
8600 0395-514 91
CM (Change MCP)
1. Make a copy of the MCP code file that is to be duplicated or triplicated onto
each member of the family in the index unit list. Use the following syntax:
COPY <file name> AS <file name>/FMLYINX<nnn>
TO <family name> (PACK,FAMILYINDEX=<nnn>)
The variable nnn is the 3-digit family index number of one of the members of the
family in the index unit list that is to receive a copy of the MCP code file.
2. Repeat step 1 for each member that is to receive a copy of the MCP code file.
Be sure to change nnn appropriately in both places in the COPY statement.
3. Issue the CM command and specify one of the new names in full with the
index units list.
The command syntax for the halt/load family is as follows:
The following error messages can be generated both by the CM command and during
subsequent halt/loads when the standby halt/load feature is active.
MCP ON STANDBY H/L UNIT <family name> TOO OLD. IT WILL NOT BE
UPDATED.
The CM command is applied to the specified family that contains an MCP that is
too old to correctly interpret the structures in use by the current MCP. The
specified family remains in the list of standby halt/load families for the current
halt/load unit, but its structure is not updated. In the response to the CM?
command, the specified family is flagged with the following phrase:
[[[ MCP INCOMPATIBLE ]]]
The most common occurrence of this message is upon the first CM to a new MCP
software release level. It indicates that the system on the specified family is
several software release levels older, and must be replaced by an MCP with a
more recent software release level.
STANDBY H/L UNIT <family name> NO LONGER CMED. IT WILL BE DELETED
FROM LIST.
The specified family is no longer halt/load capable. It will be deleted from the list
of standby halt/load units for the current halt/load unit.
NO MCP FOUND ON STANDBY H/L UNIT <family name>. IT WILL NOT BE
UPDATED.
92 8600 0395-514
CM (Change MCP)
The specified family is halt/load capable, but no MCP was found on it. The
specified family remains in the list of standby halt/load units for the current
halt/load unit, but its structures are not updated. In the response to the CM?
command, the specified family is flagged with the following phrase:
[[[ ERROR ]]]
8600 0395-514 93
CO (CONTROLLER Options)
CO (CONTROLLER Options)
The CO (CONTROLLER Options) command enables individual sites to set
CONTROLLER functions according to the specific needs of that site. CONTROLLER
options can be set or reset and include diagnostic functions as well as the capability
to suppress deimplementation warning messages.
Options specified using the CO command are maintained after a halt/load. If the ??RJ
(Remove JOBDESC file) primitive command is used to remove the JOBDESC file, the
CONTROLLER option settings are also removed.
Syntax
Explanation
Option values are set using the plus sign (+) and reset using the minus sign (). The
default value for all CONTROLLER options is reset.
CO
Displays the current settings for all the CONTROLLER options.
CO + ERRORDP
CO ERRORDP
Cause a program dump of the CONTROLLER stack whenever the CONTROLLER
scanner detects a syntax or semantic error, or whenever a CONTROLLER internal
error occurs. When this option is set and an error occurs, all processing stops until
the program dump completes. The dumps are not released for printing until the
option is reset.
Note: Each program dump taken by the CONTROLLER requires a lot of time
(perhaps a minute) and disk space. You should set this option only when you are
trying to diagnose a particular problem in the CONTROLLER.
CO + INPUT
CO INPUT
Cause a program dump whenever any input other than another CO command is sent
to the CONTROLLER.
94 8600 0395-514
CO (CONTROLLER Options)
Note: The INPUT option should always be reset unless your customer service
representative sets this option for diagnostics of a problem that is unique to your
site.
CO + MONITOR
CO MONITOR
Currently reserved for use only by your customer service representative.
CO + SEPARATEMSGS
CO SEPARATEMSGS
Control the response of the MSG command. When this option is reset, the MSG
command returns both system and network messages. When this option is set, the
MSG command returns only system messages.
CO + SUPPRESSWARNING
CO + SPRWARN
CO SUPPRESSWARNING
CO SPRWARN
Control the display of deimplementation warning messages for system commands.
When this option is set, the messages are not displayed. A deimplementation
message is an advisory that the command just entered will be deimplemented in a
future release. The command is still executed.
CO + TRACE
Enables the CONTROLLER tracing facility. When this command is entered, the system
attempts to create a memory-resident trace table in save memory. If memory space
is successfully allocated, then CONTROLLER tracing commences. If memory space
cannot be successfully allocated, then the system issues the following message:
When the tracing facility is running, the system stores data in the trace table in a
cyclical manner from the end of the table with the lowest index to the end with the
highest index. When the high end of the table is reached, then the next trace table
entry is placed at the low end of the table, thus overwriting the oldest trace table
entry.
You can retrieve CONTROLLER trace data with the System CONTROLLER Trace
Information (Type 18) call in SYSTEMSTATUS. Refer to the SYSTEMSTATUS
Programming Reference Manual.
You can analyze the CONTROLLER trace data in a memory dump with the CTRACE
command in the DUMPANALYZER utility. Refer to the System Software Utilities
Manual.
CO TRACE
Disables the CONTROLLER tracing facility if it is active. The save memory space
assigned to the CONTROLLER trace table is returned to the system.
8600 0395-514 95
CO (CONTROLLER Options)
Examples
Example 1
The following CO command example displays the current option settings:
CO
--------------------------CONTROLLER OPTIONS-------------------------
Run time options: (CO+ will SET, CO- will RESET the option)
Errordp is RESET.
Input is RESET.
Monitor is RESET.
Suppresswarning is RESET.
Trace is RESET.
Separatemsgs is SET.
Example 2
The following example sets the ERRORDP and SUPPRESSWARNING options:
CO +ERRORDP, +SPRWARN
--------------------------CONTROLLER OPTIONS-------------------------
Run time options: (CO+ will SET, CO- will RESET the option)
Errordp is SET.
Input is RESET.
Monitor is RESET.
Suppresswarning is SET.
Trace is RESET.
Separatemsgs is SET.
96 8600 0395-514
CO (CONTROLLER Options)
Example 3
The following example resets the ERRORDP option and sets the SUPPRESSWARNING
option:
CO - ERRORDP, + SUPPRESSWARNING
--------------------------CONTROLLER OPTIONS-------------------------
Run time options: (CO+ will SET, CO- will RESET the option)
Errordp is RESET.
Input is RESET.
Monitor is RESET.
Suppresswarning is SET.
Trace is RESET.
Separatemsgs is SET.
8600 0395-514 97
COMPILERTARGET (Set Default Target Value)
Syntax
Explanation
Many of the language compilers can produce code files that run only on a particular
set of computer families. For more information, refer to the description of the
TARGET compiler option in the appropriate language reference manual. The code
files are optimized for the machine specified as the primary target; however, no
machine instruction that is unacceptable to any of the secondary targets is placed in
the code file.
The MCP maintains a default value for the TARGET compiler option. With the default
value supplied by the manufacturer, the compilers generate code tailored to the
system on which the compilers are running. The COMPILERTARGET command
changes the default value of TARGET. The new value remains in effect until it is
changed by another COMPILERTARGET command. The value specified in the
COMPILERTARGET command is preserved across all halt/loads, but not across cold-
starts. After a cold-start, the value is reset to the default value supplied by the
manufacturer.
Target Values
The primary and secondary targets can be any of the following values.
98 8600 0395-514
COMPILERTARGET (Set Default Target Value)
Most compilers generate code files that are optimized for the systems represented by
the primary target, subject to the compatibility constraints of the systems
represented by the secondary targets. For example, the compiler optimizes the code
for the primary target but does not generate an operator unless it is supported by all
of the secondary targets.
If the specified target is a system, the compiler optimizes the code file for the
system characteristics. If the target is a LEVEL, the compiler optimizes the code file
for the most common characteristics of the systems in that LEVEL.
The default value supplied by the manufacturer is THIS, which causes a compiler to
generate code tailored to the system on which it is running. THIS is a synonym for
the target value of the system on which the code file is being compiled.
ALL and LEVEL5 are currently synonyms. If these values are specified, the generated
code file can run on all supported machines, but is currently tailored to LEVEL5
systems.
CS590 FS1600
CS680 CS690
COMPILERTARGET
Displays the current default value of the TARGET compiler option.
8600 0395-514 99
COMPILERTARGET (Set Default Target Value)
Examples
Example 1
This example shows the COMPILERTARGET command set to LEVEL5 and the
response that appears:
COMPILERTARGET LEVEL5
Example 2
This example shows the COMPILERTARGET command set to LEVEL6 and the
response that appears:
COMPILERTARGET LEVEL6
Syntax
Explanation
The mix number displays the sequence number of the source record being processed
by the compiler, as well as the number of syntax errors detected. The mix number
must designate a compiler task.
Examples
Example 1
This example shows the sequence number and reports that no errors were detected:
4537
Example 2
This example shows the sequence number and reports that three errors were
detected:
3621
When you enter the COPYCAT command, if it is free of syntax errors, the system
starts a visible independent runner named COPYCAT. COPYCAT displays no status
messages or completion messages. Use the C (Completed Mix Entries) command to
find out if the COPYCAT command has completed.
Syntax
Explanation
COPYCAT <file title>
Copies the active system catalog or access file and gives it the name specified by the
file title variable. If the specified file title already exists, the system replaces the
existing file with the new file.
Example
The following example creates a copy named BACKUP/CATALOG/002 on family
member number 2 of the family named PACK:
CQ (Clear Queue)
The CQ (Clear Queue) command clears system messages queued for display. On
remote ODTs, use the ?BRK command instead of CQ.
Syntax
Explanation
The CQ command clears all system messages queued for display. After all messages
are cleared from the display queue, the system response is MESSAGES FLUSHED.
Example
CQ
MESSAGES FLUSHED
CS (Change Supervisor)
The CS (Change Supervisor) command displays or cancels a supervisor program, or
designates a code file as a supervisor program. At halt/load time, the supervisor
program is automatically entered in the mix. It runs before any other jobs are
initiated. If the operating system run-time option DUPSUPERVISOR is set (OP + 9),
the system tries to execute a code file <file name>/FMLYINXnnn, where nnn
represents the family index. If the DUPSUPERVISOR option is reset, the system tries
to execute the designated supervisor program.
Syntax
Explanation
CS
Displays the current supervisor program.
CS
Cancels the current supervisor program.
CS <file title>
Designates the code file as a supervisor program.
Examples
Example 1
CS
SUPERVISOR: SYSTEM/SUPERVISOR
Example 2
CS-
Example 3
CS
Example 4
CS SYSTEM/HARDCOPY
SUPERVISOR: SYSTEM/HARDCOPY
CU (Core Usage)
The CU (Core Usage) command displays information about the memory usage either
of a particular task or of the entire system.
Memory disk, if used, is not included in the display; to display memory disk
information, use the MM (Memory Module) command.
For detailed information about the buffer statistics refer to the SF (Set Factor)
command and the File Attributes Programming Reference Manual. For detailed
information about the overlay mechanism, refer to the Managing Memory section of
the System Operations Guide.
Syntax
Explanation
<mix number list> CU
Displays memory usage statistics for the tasks in the specified mix number list.
These statistics include total and save sizes of both the stack and the code. If the
system schedules the specified task, the display shows the number of words required
for the task.
CU
Displays information about memory usage, ASD usage, and logical I/O buffer usage
for the entire system. The memory information includes the number of available
words, the number of in-use words (both save and nonsave), and the number of
words overlaid to the DL OVERLAY family (or families). The ASD information includes
the percentage of in-use ASDs. The logical I/O buffer information is broken down by
the source of the buffersize (buffergoal, buffersize, or blocksize).
CU AVAIL
Displays the all the information shown for a regular CU command as well as a
differentiation of the number of available words into values for nonsave available,
save available, and the number of available words that are not linked into either a
nonsave or save available list. The number of words from the nonsave and save
counts are not mutually exclusive, because the same block of available words can be
both nonsave or save, depending on its address and the relationship of that address
to the a mount of in-use nonsave and save memory. This means that the total of
nonsave available, save available, and not linked available words might be greater
than the available words listed in the memory summary that allows the available
header. The CU AVAIL command cannot be used in conjunction with the ADM
command. Only the CU version is applicable to the ADM command.
Examples
Example 1
The following example of a CU display shows all memory used by the process and
main memory usage:
CU
Example 2
The following shows a <mix number> CU command and the resulting display:
9508 CU
Example 3
The following shows a CU AVAIL command and the resulting display that shows
individual available memory totals:
CU AVAIL
DA (Dump Analyzer)
The DA (Dump Analyzer) command executes the utility SYSTEM/DUMPANALYZER to
analyze a memory dump.
Syntax
Explanation
DA
Starts a DUMPANALYZER session that accepts commands from the ODT at which the
DA command was entered, and allows interactive mode to be selected. An interactive
DUMPANALYZER session on an ODT is different from an interactive DUMPANALYZER
session on a remote terminal. Only limited output, such as the HELP command
information, is sent to the ODT. The output from most commands is sent to the
printer when the session is terminated (or during the session if the interactive RELX
command is in effect).
DA <unit number>
Specifies a tape drive where a memory dump tape has been mounted.
Example
DA
Syntax
<wild card>
<delim>
Use one of the following characters:
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters.
Character Description
You can include lowercase characters and space characters by prefixing the wild-card
string with LIT and enclosing the wild-card string in delimiters.
For example, if you enter the following syntax, the system returns entries that
contain the string "PACK":
If you enter the following syntax, the system returns entries that contain the string
"pack":
Explanation
DBS
Displays all unsuppressed database stacks.
DBS ALL
Displays suppressed and unsuppressed database stacks.
An asterisk (*) appears before a database stack display if this active stack is being
displayed for the first time.
Example
Each entry in the following display consists of, from left to right, the mix number, the
priority of the database, the number of users of the database stack, and the
database name:
DBS
The heading line shows the total number of active databases. The heading line
appears on each page of the Database Stack Entries display and before the database
stack entries in automatic display mode (ADM).
DD (Directory Duplicate)
The DD (Directory Duplicate) command creates or deletes a backup copy of the flat
directory of a pack family.
When you enter the DD command, if it is free of syntax errors, the system starts a
visible independent runner named DD. Use the C (Completed Mix Entries) command
to find out if the DD command has completed.
Syntax
Explanation
DD ON <family name> (<family index>)
Starts the DD procedure as an independent runner and performs an immediate copy
operation. The duplicate directories are named SYSTEMDIRECTORY/nnn, where nnn,
an integer from 1 through 255, is the family index of the unit receiving the duplicate.
Example
DD ON MASTERPACK (2)
DIRECTORY ONLY
The DIRECTORY ONLY command marks a member of a disk family as usable for disk
directories only. Once marked, the system does not allocate any AREAS of files
other than directories on the marked disk volume.
Syntax
Explanation
DIRECTORY ONLY ON <family name> (<family index>)
Marks the indicated family member as reserved for use by directories only. This
includes the SYSTEMDIRECTORY for the family, an optional local
SYSTEM/ACCESS/<family name> directory for the family, the central
SYSTEM/ACCESS or SYSTEM/CATALOG directory, and SYSTEM/ARCHIVE directories.
Example
The following example shows the DIRECTORY ONLY command:
You can check the DIRECTORY ONLY status of a disk volume with the OL PK<unit
number> command and the DU ON <family name> (<family index>) command.
A disk volume that contains an MCP code file marked by the CM command cannot be
marked as DIRECTORY ONLY.
The SQUASH ON <family name> command does not work effectively on family
members that are marked as DIRECTORY ONLY.
Syntax
Explanation
DF
Initiates the independent runner, DUMPDISKMASTER, which empties the dumps from
the current dumpdisk file. For more information about establishing a dumpdisk file,
refer to the DN (Dump Name) and CM (Change MCP) commands.
DF <file name>
DF <file name> ON <family name>
Initiates the independent runner, DUMPDISKHANDLER, which empties the specified
dumpdisk file.
Before the system discards the dumps, it displays the name of each dump in the file
and an RSVP message that prompts you to respond. If you respond with PURGE, the
system removes the dump from the file. If you respond with OK, the system
removes the dump from the file and sends it to the default family specified by the DL
DPFILES command. If the default family is null, the system sends the dump to tape.
If you respond with SAVE, the system removes the dump from the file and creates a
SAVEDUMP by interfacing with DUMPANALYZER. The SAVEDUMP file is created on the
default family specified by the DL DPFILES command. If the default family is null, the
system sends the dump to the halt/load family. If you respond with SKIP, the system
does not remove the dump and it continues to present the name of the next dump in
the dumpdisk file. For more information about managing the specification of
DPFILES, refer to the DL (Disk Location) command.
Example
The DF command tells the system to empty the dumps from the current dumpdisk
file. The Waiting Entries display shows the name of the first dump in the file, and
possible operator responses. You can then enter OK, which instructs the system to
remove the first dump as shown in this example:
DF
3971AX OK
DIR (Directory)
The DIR (Directory) command lists the directory of files on the system disk or on
another disk pack. This command invokes the utility SYSTEM/FILEDATA. Refer to the
System Software Utilities Operations Reference Manual for more information about
the SYSTEM/FILEDATA utility.
Syntax
Explanation
DIR
Generates a standard report for all files on the DISK family. This report contains a
directory list and the files area layout in response to FILENAMES, STRUCTUREMAP,
and CHECKERBOARD task requests.
DIR
Causes SYSTEM/FILEDATA to generate a report for all files on the DISK family. This
report contains a directory list in response to the FILENAMES task request.
Examples
Example 1
The following DIR command requests a standard report of the directory A/B on the
family HLUNIT:
Example 2
The following DIR command requests a list of filenames on the family HLUNIT:
DIR F:FAMILY=HLUNIT
DL (Disk Location)
The DL (Disk Location) command specifies on which disk families certain system files
are to reside. The OVERLAY specification can have more than one family.
Syntax
<on part>
<olay request>
The valid range for <sectors per area> is 365 to 2912, inclusive.
<family list>
Explanation
DL
DISKLOCATION
Display the current settings of the various specifications.
DL <type>
Displays the current setting for the specific type. The type can be BACKUP,
CATALOG, JOGS, LIBMAINTDIR, LOG, SORT, USERDATA, DPFILES, PDUMPFILES,
ROOT, OR OVERLAY.
Any jobs that are already running when the DL BACKUP family is changed continue
to use the old backup family until the jobs are restarted. The backup family of the
job is inherited by its tasks through the BACKUPFAMILY task attribute. Thus, if such
jobs initiate further tasks after DL BACKUP is changed, these tasks continue to
inherit the old backup family. (Note that CANDE is an exception to this rule. If you
initiate tasks from CANDE after a DL BACKUP change, the tasks inherit the new
backup family. By contrast, tasks initiated from a MARC session continue to inherit
the original backup family.)
1. Issue the PS QUIT command and wait for the Print System (PrintS) to
terminate. (PrintS uses the DL BACKUP family to store information about print
requests and devices.)
2. Issue the new DL BACKUP ON <family name> command.
The operating system checks for the presence of the specified DL BACKUP family
at system initialization time and whenever you enter a new DL BACKUP ON
<family name> command. If the family is not present, the RSVP message DL
BACKUP REQUIRES FAMILY: <name> gives you the following options:
Enter the OK (Reactivate) command after you make the family base unit
available.
Enter the OF (Optional File) command to keep the missing family as the DL
BACKUP specification.
Enter the DS (Discontinue) command to end the RSVP wait and dissociate the
DL BACKUP specification from the missing family. If you reply with the DS
command at initialization time, the DL BACKUP specification defaults to the
halt/load family name. If you reply with the DS command after specifying an
incorrect DL BACKUP ON <family name> command, the system retains the
previous DL BACKUP family specification.
3. Enter the following WFL COPY syntax:
COPY *SYSTEM/BACKUPFILELIST, *SYSTEM/PRINTERINFO, *SYSTEM/PRINTSYSTEMCONFIG
*SYSTEM/PRINT/FONTSUPPORT/=
FROM <old family name>(PACK)
TO <new family name>(PACK);
If the catalog family is not present when the system is halt/loaded, you can use one
of the following system commands:
The IL (Ignore Label) command directs the search to another family. The
catalog or access structure is read on the other family, and the DL (Disk
Location) specification is changed to the other family.
The OF (Optional File) command directs the search for the catalog or access
structure to the halt/load family.
Note that changing the DL CATALOG setting can cause time-consuming family
rebuilds to occur after the next halt/load. Avoid this result by stopping or terminating
all active tasks and then placing a copy of the active catalog on the newly designated
catalog family just before the halt/load. Sometimes you can use library maintenance
to copy the active catalog. Otherwise, you can use one of the following COPYCAT
commands:
Use the file name CATALOG if the installation uses cataloging (OP + CATALOGING).
Use the file name ACCESS if the installation does not use cataloging (OP
CATALOGING). The numbers nnn are the family index of the disk in the new family
that is to receive the copy of the catalog.
DL DPFILES.
DL DPFILES ON <family name>
Provides a default family on which DUMPDISKMASTER creates a disk file after the
system takes a memory dump to a dumpdisk file. When DUMPDISKMASTER empties
a memory dump from a dumpdisk file to a disk file, it can be either a raw memory
dump image, or it can be formatted by performing a DUMPANALYZER SAVE
command on the file. When the file is a raw memory dump file, it is given a file name
A dump stored in a DP or SAVEDUMP file on disk can be analyzed in the same way as
a MEMORY/DUMP tape by label equating TAPEIN to the file when running
SYSTEM/DUMPANALYZER. For more information about running the DUMPANALYZER
utility, refer to the System Software Utilities Reference Manual. For more information
about dumpdisk files, refer to the DN (Dump Name) command, the CM +
HLDUMPDISK form of the CM (Change MCP) command, Memory Dump Processing,
and Memory Dump Commands.
DL DPFILES lists the current setting of DPFILES. DPFILES is null until set otherwise.
The system sets DPFILES to null when you specify DL DPFILES with a period (.) at
the end of the command (DL DPFILES.). If DPFILES is null, it is not displayed in the
list of DL family specifications returned in response to a simple DL command, and the
response to a DL DPFILES command is DPFILES - NO SPECIFICATION.
For more information about memory dump processing, refer to Memory Dump
Processing and Memory Dump Commands.
If the command specifies a family on which there is an old JOBDESC file, the items
stored in that file reflect the conditions that existed when that file was last used.
When you halt/load the system, the job queues, terminal and ADM specifications,
queued jobs, and so forth revert to their old states.
If the DL JOBS command specifies a family on which there is no old JOBDESC file,
the system creates a new file with the default settings for ADM, TERM, and job
queues. In this case, the job queues are empty. None of the jobs that were queued
or running at the time of the halt/load can start.
The system does not allow the JOBDESC file to be copied by library maintenance.
For additional information about these files, refer to the WFL Programming Reference
Manual.
During system initialization, if the specified family is not present, the DL LOG
specification defaults to the halt/load family name.
If the new family is not present when you issue the DL command, an RSVP wait
occurs. The following options are available:
To make the family base unit available and enter the OK (Reactivate)
command
To enter the OF (Optional File) or DS (Discontinue) command to discard the
request and retain the previous DL LOG specification
If the required family is present, the MCP performs the following steps:
Note: If you change the DL OVERLAY family list, the next time that BNA initializes,
it might not be able to find its old recovery file. Refer to the NP option of the
SEND (Send Message) command.
Caution
This command forces all currently overlaid areas back into memory and writes
them to the specified family list. As a result, depending on the amount of system
memory available and the amount of overlay activity, using this command can
cause a system to appear unresponsive for a brief period while the overlay change
is in progress. Additionally, system behavior might show a large FALSE IDLE
count. Such behavior is also possible when you add or delete a family member
from a list of overlay families.
an error message is displayed that indicates the number of areas that could not
be allocated.
If you want to use a large family list, you might want to incorporate special
routines in the SYSTEM/ASSISTANT that you can call to establish or reestablish a
new family list. For more information, refer to the System Assistant Programming
and Operations Guide.
DL OVERLAY + <family list>
Adds the families that you specify to the list of families on which the system is
currently storing the overlay data. The new families become candidates for use
as overlay families when the system initiates new tasks. The system generates
an error message if the current number of overlay families is 47 or if the
specified family name has already been designated as an overlay pack.
DL OVERLAY <family list>
Deletes the families that you specify from the list of families on which the system
is to store overlay data. If any tasks that are already assigned to an overlay file
occupy space on the family that is to be removed, the system allocates space on
other members of the overlay list, and moves the data for those tasks. If not
enough space exists on another family, the system rejects the command. If you
specify a family name that is not in the current list of overlay families, the system
issues an error message. The system also issues an error message if only one
family exists in the overlay list when you enter this version of the command.
DL OVERLAY <sectors per area> <family list>
Specifies or modifies the OLAYROWSIZE in sectors that you want the system to
apply when it allocates overlay disk areas. The valid range for <sectors per area>
is 365 (for the default page size of the system in sectors) to 2912 (maximum I/O
size in sectors)inclusive. This action equally affects all families that contain
overlay areas. If the new size differs from the current size, the system first brings
the data back into main memory and then discards all existing disk overlay
assignments. If the system needs to write the area back to disk, it makes a new
assignment. Note that this option also requires that you specify a new list of
families you can specify all, some, or none of the current families. You can add or
subtract families either before or after the size adjustment. For information about
space requirements, refer to Considerations for Use later in this subsection.
The DL OVERLAY command also determines the location of the files
NP/SUPPORT/RECOVERY and NP/TANKED/INPUT/nnn. The system does not
relocate these files when you change the DL OVERLAY family.
DL PDUMPFILES .
DL PDUMPFILES ON <family name>
Provides a default family on which PROGRAMDUMP creates the program dump disk
file created with the TODISK option. When the option is set, all generated program
dump files are placed on the specified family under the usercode of the task. You can
override the location and name of the program dump file by using the standard file
equation of the file named PDUMP. If the DL setting for PDUMPFILES is not set, the
system uses the standard method of determining the location of the program dump
file.
DL PDUMPFILES.
Sets PDUMPFILES to null. If PDUMPFILES is null, the system does not display it in
the list of DL family specifications that are returned when you enter a DL
command. If you enter the DL PDUMPFILES command, the system displays the
following messge:
PDUMPFILES - NO SPECIFICATION
DL ROOT .
Sets ROOT to null. If ROOT is null, it is not displayed in the list of DL family
specifications returned in response to a simple DL command, and the response to
the DL ROOT form of the command is the message
ROOT - NO SPECIFICATION
A duplicate of the *dev/null file is found and it is not of the appropriate type.
Possible Responses:
Enter the DS (Discontinue) command to discard the request and set ROOT to
null.
Enter the OK (Reactivate) command after you dispose of the file in some
other way.
The DL ROOT setting remains null until all RSVP waiting messages are satisfied.
The preceding RSVP messages can also occur on system that is already initialized.
In this case, the possible causes and responses are as follows:
Cause: The DL ROOT ON <family name> command was entered, and the
specified family is not present.
Possible responses:
o Enter the DS (Discontinue) command to discard the request and retain the
previous DL ROOT specification.
o Enter the OK (Reactivate) command after you make the family base unit
available.
If the new USERDATA family is not present, at the resulting RSVP wait you can enter
either the OF (Optional File) or DS (Discontinue) command to terminate the change
and retain the previous DL USERDATA specification.
Examples
Example 1
DL
DISK LOCATION:
LIBMAINTDIR ON DISK
ROOT ON DISK
SORT ON DISK
CATALOG ON DISK
DPFILES ON MEMDUMPS
JOBS ON DISK
USERDATA ON DISK
BACKUP ON BKPACK
LOG ON DISK
OVERLAY 504 ON USERPACK
ON VACATION
ON PACK
Example 2
DL OVERLAY + ON DISK, ON USERS
MSG
Example 3
DL OVERLAY 504 ON DISK
MSG
BACKUP
CATALOG
JOBS
LOG
OVERLAY
ROOT
USERDATA
If the families associated with the DPFILES, PDUMPFILES, and SORT locations are
missing, the system takes no action until the independent runner DUMPDISKMASTER
makes a request (for DPFILES), a program dump to disk is taken (for PDUMPFILES),
or the SORT intrinsic is used by a program (for SORT).
The following table lists actions to be taken when DL families are missing.
DN (Dump Name)
The DN (Dump Name) command controls the creation and assignment of the disk file
used for system memory dumps to disk. After you have established a dumpdisk file,
the system uses it instead of a tape whenever the system performs a memory dump
subsequent to system initialization. In general, the memory dump process takes less
time when it writes to a dumpdisk file rather than to a tape. After the system
activates a dumpdisk file, it marks the file as a secured DATA file.
Although all memory dumps to disk could be sent to HLDUMPDISK by using the
command CM + HLDUMPDISK, physical space limitations of the halt/load unit make
the use of a dumpdisk file residing elsewhere desirable. The dumpdisk file specified
in a DN command can reside on any family of a system and can have areas on any
member of its family. The only restrictions imposed are the following:
The DN command cannot assign a dumpdisk file to a family that has mirrored
members.
You can establish the dumpdisk file by either of the two following methods:
If both dumpdisk capabilities have been enabled, the system uses the HLDUMPDISK
file for dumps that occur during system initialization and uses the file named in the
DN command for subsequent dumps.
Syntax
Explanation
DN
Displays the complete dumpdisk status of the system. The display includes the name
of the current dumpdisk file, if assigned, and the total kilosectors and free kilosectors
for each in-use dumpdisk. The system also displays the current DL DPFILES setting if
a dumpdisk or an HL dumpdisk is assigned.
DN
Immediately takes the current dumpdisk file out of use. The system negates the
assignment of the dumpdisk file, but does not actually remove the file. The system
then displays the following message to show that it has negated the file assignment:
DN <file name>
DN <file name> ON <family name>
Assign the file identified by <file name> as the dumpdisk file. DUMPDISKMASTER
searches for the designated file on the specified family. If you do not specify a family
name, DUMPDISKMASTER searches the current halt/load family. If
DUMPDISKMASTER finds the file, it verifies that the file is usable and loads the file as
the current dumpdisk file. If the file is not usable, the system displays an error
message, and DUMPDISKMASTER terminates without loading the file. Under no
circumstances does DUMPDISKMASTER remove an existing file. If DUMPDISKMASTER
does not find the file, it creates a new file.
If DUMPDISKMASTER creates a new file, an ACCEPT message asks you to specify the
number of kilosectors the file is to hold. The message lists guidelines for setting the
dumpdisk file size based on current memory and whether dumps are to be
compressed. Refer to the MDT (Memory Dump Type) command for an explanation of
the term compressed. The system applies a noncompressed format to a COMPLETE
memory dump whenever the system MDT NONCOMPRESSED option is set. The
system takes all other memory dumps in compressed format.
If the file specified already exists, DUMPDISKMASTER does not adjust the file size. If
the file is not the desired size, you can specify a new file name and a new size.
DUMPDISKMASTER loads the new file as the current dumpdisk file, and then you can
manually remove the old file. Alternatively, you can use the DN syntax to unload
the current file, remove the file with the REMOVE command, and then create a new
file by using the DN <file name> command.
Examples
Example 1
This example shows a command that creates a dumpdisk file named DUMPER on the
family named DISK. The response shows that the system has created and loaded the
file.
DN DUMPER ON DISK
Example 2
This example shows a request for the name of the dumpdisk file. The response
indicates that DL DPFILES is null (DL DPFILES.).
DN
Example 3
This example shows a request for the name of the dumpdisk file. The response
shows that DL DPFILES = PACK.
DN
Response Action
SKIP Retains the dump and presents any other dumps that are
waiting for disposition.
When responding with the AX SAVE system command, the software versions of
DPASUPPORT and SDASUPPORT are compared. If a mismatch is detected, the save
operation is not completed and DUMPDISKMASTER reports an open error and
displays a message indicating which code file settings are incorrect. At this point,
either the dump can be unloaded as a raw dump by responding with the AX OK
system command, or the SL settings can be corrected and the AX SAVE system
command can be tried again.
DO (Diagnostic Options)
The DO (Diagnostic Options) command displays, sets, or resets various diagnostic
options. The system records all mainframe hardware errors in the system summary
log (SUMLOG) and can report the errors in a mainframe hardware report.
Syntax
Explanation
DO
Displays the options that are currently set.
DO + DCI
Caution
DCI should be set only under the direction of a Unisys Customer Service
Representative (CSR). This option is intended for on-site debugging of IOP
problems.
Disables the MCP/IOP check-in mechanism. The ability to detect and recover from
hung IOPs is disabled.
DO DCI
Enables the MCP/IOP check-in mechanism. This is the default setting.
DO + DRD
If a data transfer unit (DTU) fails when this option is set, the system does not
attempt to automatically reinitialize the DTU. The system leaves the DTU out of
service so that someone can manually gather diagnostic information from it at a later
time. At any point, you can attempt manual reinitialization of the DTU by using the
UR (Unit Reserved) command.
DO DRD
Turns off the DRD option. This is the default setting.
DO + DRI
If a non-distinguished I/O module (IOM) fails when this option is set, the system
does not attempt to automatically reinitialize the IOM. The system leaves the IOM
out of service so that someone can manually gather diagnostic information from it at
a later time. This option does not affect a distinguished IOM, which cannot be
recovered.
DO DRI
Turns off the DRI option. This is the default setting.
DO + DRP
If an IOM system port is marked as broken, the system notifies you with an RSVP
message. However, the system does not automatically reinitialize the bus. Instead,
the system leaves the inactive port in its broken state. You can take a manual IOM
state dump when it is a convenient time to gather information about the cause of the
error. At any point, you can attempt to manually reinitialize the port with the UR
command.
DO DRP
Turns off the DRP option.
DO + IOD
If you set this option, selected I/O dumps result in a DEAD 20D error. You can then
take state dumps and a force dump. If DEADSTOP handling has been disabled, you
must manually take a state dump and a force dump.
You should set this option only if your customer support personnel make the request
so that you can gather information to resolve problems.
DO IOD
Turns off the IOP option.
DO + LAO
If this option is set, it alters the handling of 1-bit memory errors and is used in
testing memory on nonproduction systems. Use of this option can cause severe
system performance degradation and halt/loads.
DO LAO
Sets the option to its default setting. The system logs only those repetitive single-bit
errors that indicate a malfunction.
When the value of the LAO option is RESET for each MSU or MSM , and if the MSU
has had at least one single-bit error in each of the past three consecutive days (such
as Monday, Tuesday, and Wednesday), then the MCP records into SUMLOG the first
single-bit error found on the third day (Wednesday, in this case). The purpose of
resetting this option is to avoid filling SUMLOG with single-bit error reports.
Note: This operation is intended primarily for internal use. If you set DO + LAO,
the result can include such undesirable system consequences as flooding the
SYSTEM/SUMLOG with single-bit error reports. Furthermore, these reports generally
do not indicate a malfunction, because the system automatically corrects the errors.
DO + RST
If this option is set, an internal MCP trace is turned on to track the number of array
resizes being performed on the system. Use of this option can cause severe system
performance degradation. The array resize trace information is for use only by
Unisys engineering.
DO RST
Is the default setting. The array resize trace is inactive.
Note: DOWN is a synonym for FREE. Use DOWN on IOP systems. Use FREE on
IOM systems.
Syntax
<CTL specification>
<unit specification>
Note: For Libra Model systems, you can separate the variables with either hyphens
(-) or underscores (_).
<pod>
An integer from 0 through 3 that identifies a particular pod on an IOP system.
<subpod>
An integer (either 0 or 1) that identifies a particular pod on an IOP system.
<IP unit>
An integer from 0 through 3 that identifies an instruction processor (IP) within a
subpod on an IOP system.
<mio>
An integer (0 or 1).
<bus>
An integer identifying a PCI bus within a PCI bridge or IONODE on an IOP system.
Valid numbers are 1 through 3 for a Libra Model 185 or 500 Series system and 0
through 7 for a Libra Model 680 or 690 system.
<cell>
An integer from 0 through 3 that identifies a particular cell on a Libra Model 680 or
690 system.
<unit>
An integer from 0 through 7 that identifies a processor within the cell.
Explanation
DOWN CTL <CTL specification>
Detaches the specified CTL units from their former group and makes them available
to any group. CTL numbers may be any integer from 1 to 65535.
This form of the command might also be a necessary step in recovering from certain
CTL and PORT failures. You might need to perform the following steps to recover
CTLs that are involved in such failures:
DOWN PCI-BUS-<pod>-<mio>-<bus>
DOWN PCI_BUS_<cell>_<bus>
Detaches the specified PCI bus or buses from the partition. A DOWN PCI Bus request
is rejected if any IOPs involved in the reconfiguration are in use. The following
message is displayed for each in-use IOP:
Server Sentinel must be available to perform the DOWN request. Multiple PCI buses
can be specified in a single request. I/O activity is not significantly impacted by this
command as long as no PCI bridges are specified.
The DOWN PCI-BUS request might be rejected if one or more of the specified
buses have been disabled and the request does not result in the detaching of
the IONODE. The following message is displayed:
DOWN PCI-BRIDGE-<pod>-<mio>
Removes the specified PCI bridge and all of its associated PCI buses from the
partition. The bridge must be UP (see UP Command) and be defined in the PCD for
the partition. None of the buses served by the PCI bridge can be in use.
A DOWN PCI BRIDGE request is rejected if any IOPs involved in the reconfiguration
are in use. The following message is displayed for each in-use IOP:
All I/O activity is automatically suspended as part of the DOWN request causing a
pause that can last from several seconds to a few minutes. I/O activity resumes
upon completion of the request. The DOWN request allows multiple PCI bridges to be
specified in a single request so several bridges can be removed with only one pause
in I/O activity.
You can also specify multiple PCI-BUS entries as part of a DOWN PCI-BRIDGE
request. However, such requests are redundant because the command removes all
PCI buses connected to a specified PCI bridge.
DOWN IONODE_<cell>
Detaches the specified IONODE and all of its associated PCI buses from the partition.
The bridge must be acquired (see UP Command) and be defined in the PCD for the
partition. None of the buses served by the IONODE can be in use.
A DOWN IONODE request is rejected if any IOPs involved in the reconfiguration are
in use. The following message is displayed for each in-use IOP:
All I/O activity is automatically suspended as part of the DOWN request causing a
pause that can last from several seconds to a few minutes. I/O activity resumes
upon completion of the request. The DOWN request allows multiple IONODEs to be
specified in a single request so several IONODEs can be removed with only one
pause in I/O activity.
You can also specify multiple PCI-BUS entries as part of a DOWN IONODE request.
However, such requests are redundant because the command removes all PCI buses
connected to a specified PCI bridge.
DOWN SUBPOD-<pod>-<subpod>
Detaches all IP units corresponding to the specified subpod from the partition. If the
specified subpod is the last IP in the partition, the system displays an error message
and does not remove the IPs of the subpod.
DOWN IP_<cell>_<unit>
Detaches the specified IP from the partition. If the specified IP is the last IP in the
partition, the system displays an error message and does not remove the IP.
DOWN PROCNODE_<cell>
Detaches all IP units in the specified cell from the partition. If the partition has only
one cell, the system displays an error message and does not remove any IP units.
Examples
Example 1
This example frees a CTL unit.
Example 2
This example frees a tape unit.
DOWN MT 12
MT 12 WILL BE FREED
Example 3
This example detaches multiple PCI buses.
Example 4
This example detaches a PCI bridge and all associated PCI buses. Each of the
following has the same result.
Example 5
This example detaches multiple PCI buses.
Example 6
This example detaches an IONODE and all associated PCI buses. Each of the
following has the same result.
DOWN IONODE_2
DOWN IONODE_2 PCI-BUS_2_1
DOWN IONODE_2 PCI_BUS_2_3 PCI_BUS_2_4 PCI_BUS_2_5 PCI_BUS_2_6 PCI_BUS_2_7
DQ (Default Queue)
The DQ (Default Queue) command designates a specific queue as the system default
queue. This queue is used for jobs that do not specify a queue.
It is not essential to have a default queue. If none exists, the system puts each job
in the lowest queue whose limits can accommodate it. When the system creates a
new JOBDESC file, it defines the default queue to be queue 0 (zero).
For more information about job queue processing, refer to the following commands:
MQ (Make or Modify Queue), PQ (Purge Queue), QF (Queue Factors), SQ (Show
Queue), and UQ (Unit Queue).
Syntax
Explanation
DQ
Displays the current default queue.
DQ
Voids the current default queue specification.
DQ <queue number>
Assigns a new default queue specification.
Examples
Example 1
On a system without a currently defined default queue, the command DQ 999
establishes queue 999 as the default queue. The system response confirms the
action.
DQ 999
Example 2
This example shows a query about the default queue number and the system
response.
DQ
Example 3
This example changes the default queue value established in Example 1 as 999 to
77. The system response confirms the change.
DQ 77
Example 4
This example cancels the default job queue specification that currently is queue 8.
DQ -
DR (Date Reset)
The DR (Date Reset) command changes the system date used by the system. The
system performs checks to help prevent a change that might result in logging,
auditing, and billing problems.
Note: If the DRTRRESTRICT system option is set, you cannot change the system
date. The DRTRRESTRICT option is set through the OP (Options) command.
Syntax
<day of month>
An integer from 1 through 31.
<month>
<year>
A 4-digit integer.
Explanation
DR <day of week> <month> <day of month> <year>
DR <day of week> <day of month> <month> <year>
Changes the system date to the date specified by <day of week>, <month>, <day
of month>, and <year>. The <day of month> value is an integer in the range 1
through 31 that is not greater than the number of days in the month specified by
<month>.
Example
This example shows a command, entered on Wednesday, July14, 2004, that sets the
system date back 30 days:
The operator enters a W (Waiting Mix Entries) command to display the entries:
1234 OK
The operator again checks the waiting messages and sees that another confirmation
is needed because the backward change involves a difference of 30 days:
After confirming the change, use the TD (Time and Date) command to display the
system time and date:
1234 OK
TD
If you want to set the date forward for more than three days, the system creates a
waiting entry that indicates the number of days difference. Then you must enter
either a DS (Discontinue) command to cancel the request or an OK (Reactivate)
command to confirm it.
If you enter OK and the backward change involves more than one days difference,
an additional waiting entry message is created. The second message shows the
difference in the number of days. For example,
Syntax
Explanation
DRC
Displays the current state of the disk resource control system. The following are the
states that the DRC command can display:
Inactive state
Initializing
Active
Terminating
After a cold-start, the default state of the DRC is inactive.
DRC +
Causes the disk resource control system to be started after the next halt/load if it is
not already active or initializing. Note that if the disk resource control system is
active or initializing at the time of a halt/load, it is automatically restarted after the
halt/load. The DRC+ command is not allowed while the disk resource system is in
the process of terminating.
DRC
Causes the disk resource control system to be terminated if it is active. The DRC
also cancels a pending DRC + request. The DRC command is not allowed while the
disk resource control system is in the process of initializing.
Examples
Example 1
This example displays the current state of the disk resource control system:
DRC
Example 2
This example directs the MCP to start the disk resource control system after the next
halt/load:
DRC +
Example 3
This example directs the MCP to terminate the disk resource control system after the
next halt/load:
DRC -
Example 4
This example informs the MCP that a family named ABC was changed to XYZ when
the family was not visible to the MCP. Respond with OK to receive confirmation as
follows:
<mix number> OK
Example 5
This example informs the MCP that a family named ABC was purged when the family
was not visible to the MCP. Respond with OK to receive confirmation as follows?
<mix number> OK
Because these commands can cause substantial changes to information stored in the
USERDATAFILE, the system issues one of the following RSVP messages before it
executes a DRC LB or DRC PG command:
If you enter the DS (Discontinue) system command, the system does not perform
the operation. If you enter the OK (Reactivate) system command, the system
continues the operation.
DS (Discontinue)
The DS (Discontinue) command terminates specified jobs and tasks. It has no effect
on a process that has been locked by the LP (Lock Program) command.
Syntax
<option list>
Explanation
<mix number list> DS
<mix number> DISCONTINUE
Terminate the jobs and tasks specified by the mix number list.
<option list>
If a program has been started, the following options, if specified in the option list,
control a program dump taken at the time of termination.
Option Description
Option Description
You can verify that the system is executing the program dump by entering the Y
(Status Interrogate) command.
For details about the effects of the TODISK and TOPRINTER options, refer to the
Task Attributes Programming Reference Manual.
If the asterisk (*) is not specified, all the dump options are reset, except those
explicitly specified in the command.
On a system with the Secure Access Control Module security enhancements or with
the Security Accountability Facility, when the PROGDUMPFILTER option is set, a
dump taken TOPRINTER contains only the data belonging to the environment of the
dumping program. The data in a dump taken TODISK is filtered to display only the
data belonging to the environment of the dumping program, unless the dump is
analyzed by a privileged user or process.
For more information on the DS command, refer to the ??DS (Discontinue) primitive
command.
Examples
Example 1
3132 DS
Example 2
If you enter a DS command and the system replies that the program is locked, check
to make sure that you used the correct mix number and that the task really should
be discontinued. Then use the <mix number> LP command to unlock the task.
Then reissue the <mix number> DS command.
4352 DS
PROGRAM IS LOCKED
4532 LP -
4532 DS
Some tasks, including tasks that access Enterprise Database Server databases,
might execute exception or epilog procedures when the DS command is
applied. These procedures could release locks the task held at the time the DS
command was applied. These procedures might take time to complete, or they might
have a problem, preventing completion.
If a discontinued task does not terminate because one or more dependent tasks will
not terminate, the discontinued task will appear in the waiting entries with the
following message:
DU (Disk Utilization)
You can use the DU (Disk Utilization) command to display the amount of disk space
being used by a disk family or the amount of space being used in the
SYSTEMDIRECTORY of a disk family. The usage displays include the total capacity,
the total number of available sectors, and the size, in sectors, of the largest available
area on the family or in the SYSTEMDIRECTORY for the family.
Syntax
Explanation
DU ON <family name>
Displays the capacity of the family, the total number of available sectors on the
family, the total number of sectors in use on the family, the largest available area,
the number of available sectors in areas of fewer than 504 sectors, the number of
sectors in areas of 504 or more sectors, and the number of disk areas 504 sectors
long that can be allocated.
If the disk family capacity exceeds 2**39 - 1 bytes, the sector and byte counts are
displayed in units of thousands.
Examples
Example 1
DU ON DISK
Example 2
DU ON MCPMAST 1046
Example 3
DU ON TEST_MEDIA_A (CD)
Example 4
Following is an example of the output for a large family:
DU ON BIGFAMILY
Example 5
DU SYSTEMDIRECTORY ON MCPMAST
-- Sectors -- Percent
Available: 3,170 32 %
In Use : 6,830 68 %
Capacity : 10,000 100 %
Syntax
<memorydump option>
Explanation
DUMP
Interrupts processing on the system and initiates the memory dump process, which
dumps the entire contents of memory or all in-use or partial memory. The type of
memory dump depends on the memory dump option included with the dump
request. If no option is specified, a COMPLETE memory dump will be taken. The
setting of the MDT option does not affect the type of memory dump for operator
requests.
For additional information, refer to the MDT (Memory Dump Type) command. For
information about how to handle the memory dump process, refer to the Memory
Dump Processing topic, ??DUMP (Dump Memory), and ??MEMDP (Dump Memory).
DUMP <text>
Causes the first 18 characters of <text> to appear in the memory dump as the
reason for the dump.
Option Description
ALL Sets all future dump options, including DSED and FAULT.
No program dump is taken at this time (when the command
is entered).
Option Description
PRESENTARRAYS Dumps only present arrays. If the ARRAYS option and the
PRESENTARRAYS option are both specified, then all arrays
are dumped.
For details about the effects of the TODISK and TOPRINTER options, refer to the
Task Attributes Programming Reference Manual.
When the DUMP command is invoked for a program, the dump options for that
program are permanently set or reset. If the asterisk (*) option is not specified, all
the dump options are reset, except those explicitly specified in the command.
On a system with the Secure Access Control Module security enhancements or with
the Security Accountability Facility, when the PROGDUMPFILTER option is set, a
dump taken TOPRINTER contains only the data belonging to the environment of the
dumping program. The data in a dump taken TODISK is filtered to display only the
data belonging to the environment of the dumping program, unless the dump is
analyzed by a privileged user or process.
Examples
Example 1
This example shows a program dump that sets all options for the program with the
specified mix number:
Example 2
This example requests a partial memory dump for the program with the specified
mix number:
Example 3
These two examples request minimal memory dumps by using the DUMP command
with the MINIMAL <memorydump option>:
DUMP LOW_MEMORY:MINIMAL
Syntax
Explanation
<directory name>
The <directory name> must be the name of an active directory, such as a
SYSTEMDIRECTORY, SYSTEM/ACCESS, SYSTEM/CATALOG, or SYSTEM/ARCHIVE.
<family name>
The <family name> is the name of the disk on which the specified directory is
located.
<number>
The <number> specifies the total number of AREAS the directory should have. If the
directory is one of a duplicated or triplicated set of directories, the expand process
expands the specified directory and all of its duplicates. If the directory already has
the requested number of AREAS or more, the expand process terminates without
adding any AREAS to the directory.
Example
This example expands SYSTEMDIRECTORY for the family PACK to 400 AREAS:
If there is not enough available disk space initially to expand the directory to the
specified size, the expand process invokes a special internal form of the "SQUASH
<family name>" command to make enough disk space available to allocate all the
requested AREAS. This squash process can move areas of files from the target disk
to other members of the family. Because only one SQUASH or RES command can run
on a family at a given time, you should not use EXPAND while a SQUASH or RES
command is running for the family containing the directory.
In the case of disks that contain several directories, such as the DL CATALOG family,
you should not run EXPAND for one directory on a family while an expand process is
already running for another directory on that family.
Make a new copy of the SYSTEMDIRECTORY and, in the process, assign new
record numbers to each record (each disk file header) copied from the old
directory to the new directory.
Adjust the linkages between segments of all segmented disk file headers in
the directory (for example, the disk file headers for files with more than 2000
AREAS).
Execute a family rebuild or catalog rebuild for the family to update the record
number information in the FAST or CATALOG.
Go through the main memory and update the record numbers in the disk file
headers for all permanent disk files that are currently open or are in the
STRUCTURE HEADER cache.
To make a coherent copy of the directory, the process procures various locks to
block all access to the SYSTEMDIRECTORY by programs and system software. This
activity blocks the opening and closing of files on the family, the removal of files
from the family, the changing of the file name or other attributes of files on the
family, and so forth. The locks also block the use of the PD (Print Directory) and
other system commands, CANDE FILES and LFILES commands, and MARC
commands that reference the family. In some cases, the blockage can extend to
uses of the PER PK command either manually or in an ADM display.
It searches for available disk space and adds spare AREAS to the
SYSTEMDIRECTORY.
If it cannot find enough available disk space to reach the number of AREAS
that you specified in the command, the system might try performing a special
form of the "SQUASH <family name>" process and then try to find more
space.
Using EXPAND SYSTEMDIRECTORY is much less disruptive than using SQUASH
SYSTEMDIRECTORY and NEW SYSTEMDIRECTORY because it does not need to block
all access to the SYSTEMDIRECTORY while it is running. Using the EXPAND
SYSTEMDIRECTORY command consumes very little processor or I/O time except in
cases where it runs out of available disk space. In such cases, it attempts to move
files to make space available.
FA (File Attribute)
The FA (File Attribute) command enables you to respond to RSVP messages that
indicate incompatible attributes, NO FILE, NO LIBRARY, FUNCTION IS NOT DEFINED,
or REQUIRES <device type> conditions. The command enables you to specify a new
value for certain file or library attributes. For information about the attributes that
can be changed, refer to the File Attributes Programming Reference Manual.
The FA command response to an RSVP message does not apply to missing code files.
You cannot use this command for library maintenance tasks except for the SERIALNO
and SCRATCHPOOL attributes.
Syntax
Explanation
The <mix number list> FA <file attribute assignment> command assigns a new or
changed value to one or more of the file attributes of the tasks in the mix number
list.
Refer to the WFL Programming Reference Manual for the syntax of the file attribute
assignment parameter.
Examples
Example 1
In this example, the W (Waiting Mix Entries) command displays a system message
showing that no tape can be found with the filename ABC. Then, a PER (Peripheral
Status) command shows that the tape file is named ABCD. The FA command
changes the filename attribute to conform to the required value.
PER MT
7988 FA FILENAME=ABCD
Example 2
In this example, the W (Waiting Mix Entries) command displays a system message
showing that the specified library is missing. The FA command specifies the library
attributes to use.
Using the FA command for a single SERIALNO value (as opposed to a list of
SERIALNO values) at tape-reel-switch time causes that SERIALNO value to be
applied to the continuation reel being sought. The system can display either of the
following two tape-reel-switch RSVP messages (the first message is for output tapes,
and the second message is for input tapes):
In these messages, file section is an integer greater than 1. File section equal to 1
indicates an initial open. For either of these messages, you can use FA to specify the
serial number of the next reel as follows:
After you enter this response, the system immediately searches for the specified
tape.
Alternatively, you can use the FA command to specify a new list of serial numbers to
be used for the file:
For this response, the system merges the serial numbers you specify with any serial
numbers already specified for the file. The system then takes the serial number
corresponding to the requested file section number and searches for that tape.
2230 FA SERIALNO=("A","B","C")
This response causes the system to use tape B, because the requested file section is
2 and B is the second number in the list. After it finishes writing tape B, the program
requests tape C.
The use of local system access directories enables you to move disks from one
system to another without having to perform a family rebuild on the system
receiving the disks.
You also can use the FAMILYACCESS command to remove a local system access
directory and restore the information to the central directory, or to make a copy of a
local system access directory.
Syntax
Explanation
FAMILYACCESS LOCAL <family name>
Moves directory information for a family from the central SYSTEM/ACCESS or
SYSTEM/CATALOG directory to a local system access directory on the family itself.
The Disk Resource Control (DRC) feature cannot be used on the system if any disk
families use local system access directories.
Syntax
Explanation
FAS
Displays the error threshold and counts.
Examples
Example 1
FAS
CPM threshold : 10
CPM 5 : 2 errors
Example 2
FAS LIMIT CPM 5
CPM threshold : 5
No CPM errors
FI (File Information)
The FI (File Information) command reports information about open files that are
owned by the specified tasks.
Syntax
Explanation
<mix number list> FI
The report displays information about each file being used by the programs specified
in the mix number list. The information includes the kind of file (such as disk or
printer), the type of I/O operations performed, the number of read and write
operations and total transactions performed on the file, the I/O time used by the file,
and the title of the file. This information is intended to help you estimate the amount
of work a program has completed and how much longer it needs to run.
If the file being reported on is a foreign file (that is, the physical file resides at a
remote host), the KIND attribute is not displayed and the file title is displayed as
Foreign File.
Read-Modify-Write count
Write count
Read-Modify-Write to Write ratio
BLOCKSIZE attribute value
FILESTRUCTURE attribute value
FRAMESIZE attribute value
TITLE attribute value
The display is limited to disk files, and for each file displays only the items in the
preceding list. The display does not include the other types of data items reported by
the simple <mix number list> FI command.
Note: For any file that an application has opened at a remote host, the FI command
displays only the file title and none of the other attributes. On the line below the file
title, the display includes the message Foreign file - cannot analyze file attributes.
For information about the VSS disks, refer to the Peripherals Information File on the
Product Documentation CD-ROM.
Examples
Example 1
This example shows a report for one mix number. If the number of reads, writes, or
transactions is larger than 999,999, the number is displayed as ***. If the time is
larger than 999:59:59, the time is displayed as ***:**:**.
9886 FI
Note: Because Reads, Writes and Time each refer to a count of physical operations,
and Transaction (Trans) to a count of logical operations, the physical count does not
necessarily equal the logical count. Unsuccessful operations such as end-of-file
results are included with the logical count and thus contribute to the inequality
between the logical and physical counts.
Example 2
This example shows a report for one mix number with larger counts requested. If the
minus sign () modifier is used, times up to 1,000,000 hours and transaction counts
up to 10,000,000,000 can be displayed.
3154 FI -
Example 3
This example shows a report for one mix number, with VSS-2 information requested:
9886 FI VSS2
FILE/4
Foreign file - cannot analyze file attributes.
Syntax
Explanation
FILELOCKTLIMIT
Displays the system-wide default time limit used by the record-locking protocols,
which specifies the maximum time that the record-locking protocols wait when they
attempt to obtain a read or write lock over some file region. If a FILELOCKTLIMIT
command has never been entered with an integer value, the system behaves as if
FILELOCKTLIMIT 0 had been entered.
FILELOCKTLIMIT <integer>
Establishes or changes the system-wide time limit used by the record-locking
protocols. The time limit is expressed in seconds.
Examples
Example 1
This example shows a query for the FILELOCKTLIMIT command. The response shows
that the system is using the default value of unlimited.
FILELOCKTLIMIT
FILELOCKTLIMIT = UNLIMITED
Example 2
This example changes the FILELOCKTLIMIT to 30 seconds.
FILELOCKTLIMIT 30
FILELOCKTLIMIT = 30 SECONDS
FIND
The FIND command searches the mix, disk, and tape subsystems to find items with
specific attributes and reports them.
Syntax
<object type>
<selection attribute>
<wild card>
<delim>
One of the following characters
/ \ I ~ ! @ # $ % ^ & * '
<date value>
Explanation
FIND LIBS <selection attribute>
Finds library mix entries that match the selection attribute. For each library entry,
this command returns the mix number and name as well as the selection attribute.
The following table describes the library attributes that can be used in this command.
QUEUE Integer The job queue, if any, that is the source of the
process
The mix attributes that can be specified are the same as the library attributes that
were listed previously.
Use the FIND command and the following attributes to query mounted tapes.
SPARE Boolean TRUE if unit has been entered in the spare disk
pool (as either a free spare or an in-use spare)
A value of FALSE reports objects for which the attribute has a value of FALSE.
If neither TRUE nor FALSE is specified, the value is assumed to be TRUE. For
example, FIND MIX PU reports all the privileged programs in the mix.
Note: You cannot use the SORT option with Boolean attributes.
Relation Meaning
= Equal to
Character Description
Character Description
For example, if you enter the following syntax, the system returns entries that
contain the string "SYSTEM":
If you enter the following syntax, the system returns entries that contain the string
"system":
Examples
Example 1
The following output from the FIND MIX command consists of one line per program.
The first two items on the output display are the mix and job numbers, followed by
the item used for the selection, and then the program name.
The exception to this format is the Boolean attributes. Their values are not shown in
the display because they all have the required value, so the display for FIND MIX PU
reports all the privileged programs showing mix number, job number, and name
only.
MixNo-JobNo----Memory-Name----------------------------------------------
7397 7397 77,015 (RPC)SYSTEM/ONC/RPCSUPPORT ON MCPS
7388 7388 537,553 (RPC)SYSTEM/WIN/RPCSUPPORT/DIAGNOSTICS/52103/M ON MCPS
704 702 2,028,216 *SYSTEM/NEWP ON SYS00
6482 6482 191,961 *SYSTEM/MARC/COMMANDER
6459 6459 407,514 *SYSTEM/DSSSUPPORT/DIAGNOSTICS
6454 6454 146,093 *SYSTEM/CNSOBJMGR/51008
6450 6450 227,883 *SYSTEM/SNMPAGENT/51008
6438 6438 105,913 *SYSTEM/CNS/TRANSLATION/51008
6434 6434 106,045 *SYSTEM/CCF/PCM/PIPES
6420 6420 543,940 *SYSTEM/CNS/MANAGERS/51008
6417 6417 1,329,226 *SYSTEM/COMS
6579 6417 99,589 *COMS/ODT/DRIVER
6403 6403 73,943 *SYSTEM/CCF
6436 6403 99,591 *SYSTEM/CCF/PCM/LOGON
6435 6403 135,796 *SYSTEM/CCF/PCM/TCPIP
6433 6403 113,252 *SYSTEM/CCF/PCM/TERM
6431 6403 104,879 CCF/CUCIPCM
6380 6380 504,384 *SYSTEM/BNA/SUPPORT/51008
Example 2
If SORT (minus sign) is appended to the end of the command, the list is sorted in
descending order of the selected item:
MixNo-JobNo----Memory-Name------------------------------------------------
704 702 2,062,340 *SYSTEM/NEWP ON SYS00
6378 6378 1,667,773 *SYSTEM/TCPIPSUPPORT/51008/DIAG
6417 6417 1,329,226 *SYSTEM/COMS
6420 6420 543,940 *SYSTEM/CNS/MANAGERS/51008
7388 7388 537,553 (RPC)SYSTEM/WIN/RPCSUPPORT/DIAGNOSTICS/52103/M ON MCPS
6380 6380 504,384 *SYSTEM/BNA/SUPPORT/51008
6459 6459 407,514 *SYSTEM/DSSSUPPORT/DIAGNOSTICS
6314 6314 321,379 *SYSTEM/KERBEROS/SUPPORT
6450 6450 227,883 *SYSTEM/SNMPAGENT/51008
6292 6292 216,771 *SYSTEM/PRINT/SUPPORT
6482 6482 191,961 *SYSTEM/MARC/COMMANDER
6376 6376 173,638 *SYSTEM/LPPSUPPORT/DIAGNOSTICS
6454 6454 146,093 *SYSTEM/CNSOBJMGR/51008
6435 6403 135,796 *SYSTEM/CCF/PCM/TCPIP
6293 6293 129,792 *SYSTEM/GSSAPI/SUPPORT
6296 6296 123,920 *SYSTEM/NETWORKSUPPORT/DIAGNOSTICS
Example 3
This example reports all packs on the system with a name starting with the string
SYS:
UnitNo-Serial-Familyindex-Name----------------------
47 203152 1 SYS00
49 209088 1 SYS511
Example 4
This example reports all packs on the system with unit numbers less than or equal to
50:
UnitNo-Serial-Familyindex-Name----------------------
44 192045 1 PACK
45 427321 2 DISK
47 190343 1 DMSIITEST
Example 5
This example reports units with less than 300,000 sectors of available space:
UnitNo-Serial-Familyindex-AvailSects-Name-----------
44 192045 1 250,827 PACK
Example 6
This example reports the unit and serial number of the mounted tape:
FIND MT SCRATCH
---UnitNo--Serial----Name----------------------
45 PHIL
Example 7
The following example uses the ALL option to display mix entries whose RELEASEID
matches the string =DIAGNOSTICS=, without truncation:
--------------------------------------------------------------
MixNo: 38018
JobNo: 38016
ReleaseID: CANDE-051.1A.4 (51.189.8015)<OPTIONAL DIAGNOSTICS>
Name: *SYSTEM/CANDE ON SUPPORT
--------------------------------------------------------------
Example 8
The following example reports a mirrored pack that has been certified:
FIND PK CERTIFIED
UnitNo-Serial-FamilyIndex-Type-Name
100 000100 1 B OASIS
Example 9
The following example reports the certification timestamp for all certified mirrors
which were certified today:
FM (Form Message)
The FM (Form Message) command restarts a program that has been suspended
because it has tried to open a file whose FORMID attribute is set. Alternatively, the
program can be terminated with a DS (Discontinue) command, or the FORMID
attribute can be altered by an FA (File Attribute) command.
The FM command specifies the output unit to which the file is to be assigned. The
command does not override the existing forms message on a device. It lets a print
job requiring forms to be temporarily assigned to any available printer. When the job
terminates, the printer is saved and the FORMID, if any, is left unchanged. You can
use the RY (Ready) command to restore a unit from a saved status. Usually, if the
FM command assigns a task to a printer whose FORMID and TRAINID do not match
the requirements of the printer file, the printing task is discontinued.
An FM command is rejected if the designated device does not exist or does not
match the KIND attribute of the file. The system generates the following message to
indicate the expected devices:
The system reissues the RSVP message that requested the FM command. For a more
detailed discussion of the FORMID attribute, refer to the File Attributes Reference
Manual.
Syntax
Explanation
The <mix number> FM <device type> <unit number> command specifies the task
to be assigned to the device. The device must be LP (line printer).
Example
In this example, the W (Waiting Mix Entries) command shows that a program was
suspended because the specified FORMID could not be located. The FM command
restarts the program, directing the file to the line printer whose unit number is 4.
Refer to PS CONFIGURE and PS DEVICES for related discussions.
1127 FM LP4
FR (Final Reel)
The FR (Final Reel) command is used as a reply to the following system messages:
NO FILE (MT) #n
This reply designates that the input tape reel just read by a program is the final
reel of an unlabeled tape file. Use the FR command only if the program has set
the file attribute LABELTYPE = OMITTED.
RECOPY REQUIRED
When you enter the FR command during a COPY, ADD, or ARCHIVE action, the
destination unit on which the copy error occurred cannot be used any longer. The
COPY, ADD, or ARCHIVE process continues copying to any other destination disks
or tapes.
BACKUP REQUIRES VOLUMED UNIT
The system copies nothing to the specified disk.
Syntax
Explanation
<mix number list> FR
Designates the input file reels associated with the mix number list as the final reel of
an unlabeled tape file.
Example
4423 FR
FS (Force Schedule)
You can use the FS (Force Schedule) command to start jobs listed in a job queue and
to start a task or job listed in the schedule mix.
Syntax
Explanation
<mix number list> FS
Specifies that the jobs or tasks in the mix number list are to be unconditionally
started as long as enough memory is available. If not enough memory is available,
the task or job remains scheduled and the following message appears at the ODT:
Refer to the S (Scheduled Mix Entries) and HS (Hold Schedule) commands for related
discussions on scheduling.
You can also use the FS command to force the start of a job residing in a job queue.
You can use FS to override any STARTTIME or FETCH statements in a Work Flow
Language (WFL) job. Refer to the SQ (Show Queue) and ML (Mix Limit) commands
for information on jobs residing in job queues.
Examples
Example 1
This example shows the display after an operator enters the S command to list
scheduled entries. The operator then uses the FS command to start job 6559.
6599 FS
Example 2
This example shows using the SQ command to list the jobs in queue 1. The operator
then uses the FS command to start job 1115.
SQ 1
QUEUE 1
1115 50 X
QUEUED: 10/13/93 AT 11:26:50
1115 FS
If the command is rejected, wait for the current command to complete and enter the
command again.
Note: FREE is a synonym for DOWN. Use FREE on IOM systems. Use DOWN on
IOP systems.
Syntax
Explanation
FREE DOMAIN <number>
Saves and then frees all modules that are included in the system. The system might
not free the module for the following reasons:
The IOM is not freed because it contained the last path to a critical unit.
The memory in the MSM is still used by the system.
The requestor is the last requestor of that type in use by the system.
FREE CPM <CPM list>
FREE CPM <CPM list> :READY
FREE CPM <CPM list> :SAVE
If you use the READY option, the system marks the module as not in use. If you use
the SAVED option, the system marks the module as user saved. If all other modules
in the domain containing the specified module are saved, the system frees the
domain; otherwise, the system displays the following message:
If you use the READY option, the system marks the module as not in use. If you use
the SAVED option, the system marks the module as user saved. If all other modules
in the domain containing the specified module are saved, the system frees the
domain; otherwise, the system displays the following message:
This form of the command might also be a necessary step in recovering from certain
CTL and PORT failures. You might need to perform the following steps to recover
CTLs that are involved in such failures:
UNABLE TO PERFORM
This message indicates that the system cannot acquire the LINEID.
For more information, refer to Understanding IEA-1 IOPs in "Considerations for Use."
Examples
Example 1
This example frees a central processing module:
FREE CPM 6
Example 2
This example frees a memory subsystem module:
FREE MSM 1
Example 3
This example frees an I/O module:
FREE IOM 1
Example 4
This example frees a CTL unit:
Example 5
This example frees a tape unit:
FREE MT 12
MT 12 WILL BE FREED
Example 6
This example frees a Telephony Service Platform (TSP) unit:
Configuring Groups
FREE permanently alters the current definition of the group so that the results of
alteration are maintained across halt/loads but not across reconfigurations. The
original group definition, whether obtained from the configuration file or through a
default configuration, specifies the initial definition of a group. When a
reconfiguration command alters the current definition of a group, it does not alter
the group definition in the configuration file. You can interrogate the current
definition by using the GC (Group Configuration) command.
Halt/load family
OVERLAY family
JOBDESC family
CATALOG family
SYSTEM/SUMLOG family
Saving Memory
To obtain a successful release of a memory module (that is, an MSM, an MSU, or a
QUAD), consider some or all of the following options:
If disk caching is active, either terminate the system caching or downsize the
cache area.
Assure that adequate overlayable disk space is available.
Reschedule the freeing of the memory resource to a time when the system is
idle or is not highly active.
Wait for the next system halt/load.
Issue the SF (Set Factor) system command with the OLAYGOAL option
(Factor 1). OLAYGOAL is the percentage of overlayable memory that is to be
overlaid on a per-minute basis.
Use the CU (Core Usage) system command to monitor memory usage.
Issue the HS (Halt Schedule) system command to stop the initiation of any
new jobs or tasks.
Wait until the tasks terminate to perform the memory save.
If necessary, terminate tasks with the DS (Discontinue) system command
before you perform the memory save.
Freeing Units with a Single Command
For units that can be referenced either by device and unit number or by CTL and unit
number, you need enter the FREE command only once. You can use the same
number to reference an NSP either as a control or as a unit. For example, you can
free NSP 108 by entering either FREE CTL 108 or FREE DC 108. It is not necessary
to enter both.
The configuration on the IEA-1 consists of a single networking port and an Ethernet
port for each physical connection served by the IOP.
The networking port is a device on the IOP that enables the I/O subsystem to access
and manage the networking functions provided by this IOP. This port provides the
connection between the networking software components. Its state controls whether
host networking is active on the IOP. However, the state of the LINEID controls
determines whether the physical connection served by the IOP can be used.
Each Ethernet port contains a LINEID control that enables networking use of the
physical connection. That is, if the port is enabled and the dependent LINEID is
acquired, networking can activate the connection group that is associated with this
physical port.
Freeing VC Units
To free all 26 voice channel (VC) units outboard of a voice interface module (VIM)
DLP, you need enter only the following command syntax:
On IOM systems, all 26 VC units outboard of a CTL have the same unit number.
Freeing a Disk Pack Associated with the Mirrored Disk Pooling Facility (MDPF)
When you free a disk pack that has been assigned to the free spares pool for a
mirrored disk set, the system generates a status change message. When you free
each member of a mirrored set of in-use spares, the system generates a status
change message. The status change message is defined in the MCP System
Interfaces Programming Reference Manual.
GC (Group Configuration)
The GC (Group Configuration) command displays the current group configuration or
creates a disk file containing card images that can be used as input to create a group
description for a configuration file that matches the current configuration.
Syntax
Explanation
GC
Displays information about the permanent and temporary resources of the system.
GC TO <file title>
Creates a disk file with the specified file title that you can use as input to the
SYSTEM/CONFIGURATOR file to create a configuration file that matches the current
configuration. Units and DLPs acquired temporarily are not included in the disk file.
If you specify a file title that already exists, the CONTROLLER/GC/TASK issues the
following error message:
<mix no> GC: THE SPECIFIED OUTPUT FILE ALREADY EXISTS: <filename>
The task then terminates without changing or removing the conflicting file.
Example
Example 1
This example shows the response returned by a CS7101 server.
GC
GROUP DEFAULTNAME
MACHINECLASS: CS7101
PERIPHERALS:
PK 502 VIA 10403
PK 501 VIA 10402
PK 500 VIA 10401
CD 51 VIA 10301
CD 50 VIA 10201
NP 210
LP 20 VIA 10101
SC 1-2,16 VIA 10001
OPERATIONS:
HN MP046
DL SORT ON DISK
DL CATALOG ON DISK
DL JOBS ON DISK
DL USERDATA ON DISK
DL BACKUP ON PACK
DL LOG ON DISK
DL DPFILES ON PACK
DL LIBMAINTDIR ON DISK
DL OVERLAY ON DISK
SF OLAYGOAL 0
AVAILMIN 0
FACTOR 100
BUFFERGOAL 0
OLAYSATURATION 15
OLAYCHANGE 10
SEGARRAYSTART = 8192
NETWORKS:
BNAV1: *NULL
BNAV2: *NULL
X25: *NULL
LPP: *NULL
NAMESERVICE: *NULL
TCPIP: BNAV2/INIT/MP046/TCPIP
CNS: BNAV2/INIT/MP046/CNS
BNA: BNAV2/INIT/MP046/BNA
SNA: *NULL
Example 2
This example shows the response returned by an IOP system.
GC
GROUP DEFAULTNAME
MACHINECLASS: CS580
PERIPHERALS:
SC 1-8 VIA 401
MT 38 VIA 3138
PK 3201 VIA 321
PK 3202 VIA 322
PK 3203 VIA 323
PK 3204 VIA 324
PK 3205 VIA 325
PK 3206 VIA 326
PK 3207 VIA 327
SC 9-10,13,15 VIA 1291
OPERATIONS:
DL SORT ON DISK
DL CATALOG ON DISK511
DL JOBS ON DISK511
DL USERDATA ON DISK511
DL LOG ON DISK511
DL LIBMAINTDIR ON DISK511
DL OVERLAY ON DISK511
SF OLAYGOAL 0
AVAILMIN 0
FACTOR 100
BUFFERGOAL 0
OLAYSATURATION 15
OLAYCHANGE 10
SEGARRAYSTART = 8192
NETWORKS:
BNAV1: *NULL
BNAV2: *NULL
X25: *NULL
Syntax
Explanation
<mix number list> HI
Causes the exception event of the processes in the mix number list.
Example
The following example sets the VALUE task attribute for mix 4312 to 5:
4312 HI 5
When you request halt/load information, the system displays the unit type, unit
number, and path information. When you designate a new halt/load ODT, you can
specify only the unit type and unit number. The MCP selects the path to the unit.
When you specify a new halt/load pack (whether it is the primary halt/load pack or
the alternate halt/load pack), you can include the path to the unit. If you do not give
a path for the pack unit, the system selects a path.
Syntax
< via part>
Explanation
HLUNIT
Displays all the halt/load unit information, including the packs and the ODT that are
specified as halt/load units.
HLUNIT PK (BACKUP)
Designates the alternate halt/load unit parameter to be cleared.
Examples
Example 1
This example shows the display generated by an HLUNIT command:
HLUNIT
HALT/LOAD DISK = 13
HALT/LOAD DISK (BACKUP) NOT SPECIFIED
HALT/LOAD ODT = 58
Example 2
The following input changes the halt/load disk information to the unit number and
path for PK 48. The I/O processor selects the path. The new halt/load information is
then displayed.
HLUNIT PK 48
Example 3
Like the previous example, the following input changes the halt/load ODT information
to the unit number and path for ODT 3:
HLUNIT SC 3
The HOLD command is valid only for magnetic tape units and ODTs.
Syntax
Explanation
A unit that is held aside for operator use cannot be assigned to any file, but the unit
is still accessible to the system. Unit-related operator commands are not affected by
the hold status of a unit. Hold status is lost if the unit is the subject of a FREE
command. Because the unit cannot be assigned to any file, an attempt to assign it
by using an IL (Ignore Label), UL (Unlabeled), or OU (Output Unit) command is not
effective.
Examples
Example 1
HOLD MT 10
Example 2
HOLD - MT 10
Example 3
HOLD SC 1
PER SC
1 S C R A T C H (HOLD)
1. Acquire the unit with the SAVE option by entering one of the following
command strings:
2. If you have an IOM system, enter the following syntax:
ACQUIRE MT <unit number> :SAVE
2. Enter the HOLD command to prevent the system from assigning files to the
unit.
3. Enter the RY command so that the system can read the tape label.
4. Enter the PER MT command so that you can read the name, status and serial
number of the tape.
Because the command TDIR <unit number> initiates the FILEDATA utility, which
tries to open the tape on the specified unit, you cannot use that command on a tape
drive for which you entered a HOLD command.
HOSTNAME (Hostname)
The HOSTNAME (Hostname) command either displays the current host name of the
system or establishes a new host name at the time of the next halt/load.
Each host in a BNA network is identified by a host name. This name identifies the
location of a resource (for example, a file) to which access is desired. No two
systems in the network can have the same host name at the same time. Each host
must have a host name assigned before it tries to establish communication with a
remote host.
Syntax
Explanation
HOSTNAME
HN
Display the current host name and the host names of any BNA hosts that have active
dialogues. When port communications are established with a host for the first time,
the remote host name is added to the displayed list.
Hosts not listed can still be accessed. When port communications are successful, the
host names are added to the list.
HOSTNAME = <hostname>
HN = <hostname>
Specify the new host name to be established at the time of the next halt/load. A
valid host name contains from 1 to 17 alphanumeric characters and must begin with
a letter.
HN
Specifies that the current name of the system is removed after the next halt/load.
After you enter this form of the command, the system displays the following
message:
Examples
Example 1
HOSTNAME
HOSTNAME: BLUE
Example 2
HN = HOST
HS (Hold Schedule)
The HS (Hold Schedule) command stops or resumes the initiation of new jobs or
tasks, or displays the current status of job selection. The system does not preserve a
hold-schedule action across halt/loads. Refer to the S (Scheduled Mix Entries)
command for related discussions on scheduling.
Syntax
Explanation
HS
Stops the initiation of jobs and tasks.
HS
Resumes the initiation of jobs and tasks.
HS?
Indicates the current status of job selection.
Examples
Example 1
HS
Example 2
HS-
Example 3
HS?
HU (Host Usercode)
The HU (Host Usercode) command designates a usercode for certain distributed
systems services (DSSs) Host Services requests if they come from an ODT that has
no terminal usercode assigned to it. For more information, refer to the TERM
(Terminal) command. BNA also checks the host usercode for security purposes.
Syntax
Explanation
HU
Displays the current host usercode.
HU <usercode>
Specifies <usercode> as the host usercode.
HU
Deletes the current host usercode.
The receiving host generates an error if it does not recognize the validity of the
usercode associated with the request.
For the usercode associated with a DSS to be valid at a receiving host, the
USERDATAFILE at that host must contain the following:
A REMOTEUSER entry that specifies the local alias usercode for the usercode
and host name of the initiating user
A USER entry that describes the local alias usercode of the user
Note: If this usercode is marked as having a SYSTEMUSER status, it has the same
ODT capabilities as the local system ODT operator.
Examples
Example 1
HU
Example 2
HU LASYSTEM
IB (Instruction Block)
The IB (Instruction Block) command displays the requested instruction block for a
job. For more information about job processing, refer to the WFL Programming
Reference Manual.
Syntax
Explanation
<mix number> IB
Displays the current instruction block of the active job. If the job is currently queued,
its first instruction block is displayed.
Examples
Example 1
3178 IB
Example 2
2657 IB 1
Syntax
Explanation
ID
Displays the current DATACOMINFO prefix, the next prefix (if any), total number of
pseudostations used, and any options that are set.
ID <unit number>
Specifies an EDCDLP or a DCHA unit number. If the unit is not already running, it is
initialized. If the unit is currently running, you must execute an ID :QUIT command
before this command syntax. The unit identified by the unit number must be
declared in the DATACOMINFO file, or else initialization terminates and the system
displays the following message:
If the data comm information tables are not initialized, you can initialize them by
entering this command syntax.
If you set the AUTODC run-time option to TRUE (OP + AUTODC), the system
executes the ID <unit number> command whenever an MCS attaches a station
associated with the NSP or issues a reconfiguration request that involves the NSP.
Also, after a system halt/load, if the AUTORECOVERY run-time option (OP +
AUTORECOVERY) is TRUE, the system attempts to initialize those NSPs that were
running before the halt/load.
Other events that cause the data comm information tables to be initialized, if
AUTODC is TRUE, are the following:
ID
Sets the DATACOMINFO prefix to SYSTEM, the default value. Be aware, however,
that your DATACOMINFO file might be removed if someone enters the command
syntax REMOVE SYSTEM/= on the system software release medium (such as tape)
that contains SYSTEM/DATACOMINFO.
ID <file name>
Specifies the prefix for the DATACOMINFO file to be used by the EDCDLP or the
DCHA. If the file name exceeds 24 characters when it is converted to standard form
the system responds with the following message:
The system verifies the presence of the constructed file by using the specified prefix,
that is, <file name>/DATACOMINFO. If the file is not present or if a corresponding
NIF file is not present (<file name>/NIF), the system responds with the following
message:
The first node of the filename cannot start with a number, and cannot be enclosed in
quotation marks.
After an ID <file name> command is issued, the new DATACOMINFO file (whether it
is of the same name or not) cannot be used until data comm is brought down
through an ID :QUIT command or a halt/load.
The system verifies the presence of the constructed file by using the specified prefix,
that is, <file name>/DATACOMINFO. If the file is not present or if a corresponding
NIF file is not present (<filename>/NIF), the system responds with the following
message:
ID :QUIT
Causes all NSP stacks to terminate and all remote files to be closed. Any active MCS
loses its MCS status. All pseudostations become disabled. The system discards the
data comm information tables.
ID :QUIT NSP
Causes all NSP stacks to terminate. Any active sessions or open remote files with
stations connected by NSPs close. No other data comm activities become effective.
All MCSs retain their MCS status and the data comm information tables remain
active. This option does not affect a change to any new DATACOMINFO file. You can
use this option to terminate all NSP tasks without terminating MARC dialogs that are
active at ODTs.
Value Meaning
Value Meaning
4 Reserved.
The audit trail operation can be analyzed with SYSTEM/DCAUDITOR. Because each
audited item requires a write operation to the audit file, auditing can use a great deal
of disk space and seriously drain system resources, adversely affecting system
performance. Likewise, transaction response time increases because the auditing
causes additional serialization and delay during message processing. Performance
can be seriously affected if all data comm messages are audited. Audit options apply
to all NSPs in the data comm subsystem.
ID :MAXPSEUDO
ID :MAXPSEUDO = <number>
ID :MAXPSEUDO = <number> UNLIMITED
If you do not specify a number for MAXPSEUDO, the system displays the maximum
number of pseudostations that it can currently allocate.
If you specify a number, it is assigned as the pending MAXPSEUDO value. The value
you enter in the MAXPSEUDO clause is used by the data comm subsystem to allocate
entries in certain tables built at data comm initialization time. Note that you can
enter a change to the MAXPSEUDO value at any time, but the pending change does
not take effect until the next time that the system initializes the data comm
subsystem.
Although the special value of 0 (zero) can still be used to indicate that there is no
limit on the maximum number of pseudostations, the process used to adjust the
number of pseudostations based on actual usage is not very efficient and might
require you to initialize the data comm subsystem several times. It is recommended
that you use the UNLIMITED option to enable the system to incrementally allocate
additional pseudostations (in blocks of 100) beyond the specified initial value, when
they are needed. Note that other system functions might be suspended until the
additional pseudostations are allocated, so you should still specify a sufficiently large
initial value.
If you specify the special value of 0 (zero), the system allocates a minimum of 100
pseudostations during data comm initialization. If more pseudostations than this
number exist in the DATACOMINFO file, they remain allocated. The next time that
the system initializes the data comm subsystem, the number of pseudostations is
changed only by a maximum of 100, so you might need to initialize the data comm
subsystem several times before reaching an appropriate number of pseudostations.
The system incrementally allocates additional pseudostations (in blocks of 100) as
needed to supply requests from MCSs.
Pseudostations are assigned (given ownership rights) to MCSs with a variant of the
STATION ATTACH DCWRITE request. A pseudostation allocation request is denied if
the number of pseudostations already allocated equals the value specified in the
MAXPSEUDO clause, unless the value specified was zero or the UNLIMITED option
was specified.
While the Interactive Datacomm Configurator (IDC) utility is running against the
current DATACOMINFO file, the system rejects any new attempts to allocate
pseudostations.
ID :DCTRACE ON
ID :DCTRACE OFF
Causes the value of DCTRACE to be set as specified. When DCTRACE is set to ON,
the system continuously gathers request and result information for the specified
NSP. The trace provides a snapshot of recent data comm activity. For each NSP
being traced, the most recent 250 requests or results are kept in a DCTRACE table
within the MCP. This information can aid in memory dump analysis by providing a
picture of data comm activity immediately before the dump.
The DCTRACE option applies to a particular NSP if the unit number value specifies a
particular unit number. If you omit the unit number, the trace applies to all units, but
only if you enter the command while data comm is running. If the unit number that
you specify is that of an NSP that is not running, the system initializes that NSP with
the specified DCTRACE setting. The DCTRACE OFF option discontinues the trace
procedure for the specified NSP.
The information collected by the DCTRACE option can be examined through the
DUMPANALYZER DCTRACE command. For information about DUMPANALYZER, refer
to the System Software Utilities Operations Reference Manual.
Examples
Example 1
This example displays the DATACOMINFO prefix as well as the option settings for DC
AUDIT and MAXPSEUDO:
ID
NIF:SSDNDL
DC AUDIT OPTIONS: 7,5
MAXPSEUDO: 0
NEXT MAXPSEUDO: 0
NUMBER OF PSEUDOS IN-USE: 200
Example 2
This example specifies an NSP unit number. The system responds that NSP 108 is
initialized:
ID 108
Example 3
This example specifies that the DATACOMINFO file to be used by NSP 108 is to have
a prefix of SYSTEST.
ID 108 SYSTEST
NIF: SYSTEST
5430 NSP 108 INITIALIZED
Example 4
This example changes the DATACOMINFO file prefix from SYSTEST to the default
value SYSTEM:
ID-
NIF: SYSTEST
NIF TO BE: SYSTEM
Example 5
This example sets the option byte to all zeros and sets options 0 and 7 to the value
1. The system is to audit all I/O activity to the NSP initiated by DCINITIAL and to
audit all NSP error conditions.
Example 6
This example directs device 110 to dump its memory to a file named
DUMP/NSP/110/YYMMDDHHMMSS:
ID 110: DUMP
IK (Install Keys)
The IK (Install Keys) command adds, merges, deletes, and installs system keys,
processor license keys, and digital signature algorithm (DSA) keys. The command
also activates processor license keys, sets partition processor performance
characteristics, sends processor metering information, displays processor metering
characteristics, and extracts DSA keys. It also adds, merges, deletes, installs, and
activates I/O license, memory license and Java capacity on demand (COD) keys.
System keys enable you to access specific features or products and are maintained
in a file called SYSTEM/KEYSFILE on your halt/load unit. System keys can include the
following types:
Software file keys needed to install files from release media for a new release
or for a new product between releases.
Software feature keys needed to access special optional products and
features.
Software user keys needed to use certain software products
Processor license keys are system-wide by design and license one or more partition
processor images. Processor license keys are maintained in system-wide
interpartition permanent storage.
A DSA key set contains a Unisys system public DSA key and other relevant DSA
information for a particular software level. The set enables you to unwrap Unisys
software that has been wrapped and signed with a corresponding Unisys system DSA
private key. Creation of public and private key pairs for use in signing wrapped files
also requires information from an appropriate DSA key set. All DSA key sets are
maintained in a file called SYSTEM/DSAKEYSFILE on your halt/load unit.
Syntax
<key>
One or more fields, separated by a hyphen (-). Each field consists of one or more
alphanumeric characters, with no embedded blanks.
<password>
10 to 17 characters.
<DELETE option>
<DSASHOW option>
<partition image>
N = nonredundant
R = redundant
<image ID>
<IP identifier>
Libra Model 580, 590, 585, and 595 systems use IP-<pod>-<subpod>-<IP unit>,
whereas Libra Model 680 and 690 systems use IP-<cell>-<unit>.
Note: You can separate the variables with either hyphens (-) or underscores (_).
<pod>
An integer from 0 through 3 that identifies a particular pod on an IOP system.
<subpod>
An integer (either 0 or 1) that identifies a particular pod on an IOP system.
<IP unit>
An integer from 0 through 3 that identifies an instruction processor within a subpod
on an IOP system.
<cell>
An integer from 0 through 3 that identifies a particular cell on a Libra Model 680 or
690 system.
<unit>
An integer from 0 through 7 that identifies a particular unit within the cell.
Explanation
IK
Displays the syntax diagram for the IK command.
IK DELETE <key>
Deletes the specified key from the system keys file *SYSTEM/KEYSFILE on the
halt/load family, creates a new version of the file, and removes the old version.
Caution
Use of the ALL option can result in a keys file that no longer contains the keys
needed to run your system.
Even under normal circumstances there is a risk of inadvertently deleting keys that
are still in use. Before using the ALL option, perform both of the following:
Because of the potential risk associated with the ALL option, it is recommended that
you use the alternate file option and verify the results with the IK SHOW option
before replacing your active file.
To minimize chances of deleting needed keys from your active keys file, the following
restrictions have been applied to strings:
IK MERGE<file name>
Merges the keys from the specified keys file into the system keys file
*SYSTEM/KEYSFILE on the halt/load family, creates a new version of the file, and
removes the old version.
IK SHOW
IK SHOW <string>
Display keys in the system keys file *SYSTEM/KEYSFILE on the halt/load family. If
you omit the string parameter, the system displays all strings. If you specify a string
parameter, the system displays only keys that begin with the parameter.
IK DSASHOW
IK DSASHOW <string>
These commands display DSA key set IDs and their corresponding software levels in
the system DSA keys file. If you omit the string parameter, the system displays all
IDs. If you specify a string parameter, the system displays only DSA key set IDs that
begin with the parameter.
IK IOSHOW
On systems that support I/O capacity on demand (COD), displays general I/O
capacity licensing information for the system and general key information for all keys
installed into Server Control.
IK IOSHOW ACTIVE
On systems that support I/O capacity on demand (COD), displays detailed I/O
capacity licensing information for the system and detailed key information for the
currently active key.
IK IOSHOW ALL
On systems that support I/O capacity on demand (COD), displays detailed I/O
capacity licensing information for the system and detailed key information for all
keys installed into Server Control.
Each system has a minimum performance level that is supported by Unisys. If you
set the processor performance to a level that is below that minimum supported
performance level, the system adjusts the requested processing power value only to
the minimum supported level. Subsequent system displays show the adjusted limit
as TARGET LIMIT.
IK IPLIMIT <percentage> %
Sets the partition level of performance for standard processors to the specified
percentage of system-wide licensed performance. This command is valid for
nonmetering systems, beginning with the Libra Model 585.
IK IPSEND ACTIVATION
IK IPSEND CONFIG
IK IPSEND LOCAL
IK IPSEND METER
IK IPSEND DATE <yyyymmdd>
IK IPSEND FILE <file name>
IK IPSEND FILE <file name> ON <family>
Generates an e-mail message that contains a report and sends it to the currently
configured e-mail destinations that are specified in the METER/EMAIL/DESTINATIONS
file.
Metering data files are found on the halt/load family by using the following naming
convention:
IK IPSHOW
Displays general active processor licensing information and general key information
for all keys installed into Server Control or the Console.
IK IPSHOW ACTIVE
Displays detailed active processor licensing information and detailed key information
for the currently active key.
IK IPSHOW ALL
Displays detailed active processor licensing information and detailed installed key
information for all keys installed into Server Control or the Console.
IK IPSHOW METER
Displays an interim system processing power metering report on the ODT.
IK MEMSHOW
Displays general memory licensing information for the system and general key
information for all keys installed in Server Control.
IK MEMSHOW ACTIVE
Displays detailed memory licensing information for the system and detailed key
information for the currently active memory licensing key.
IK MEMSHOW ALL
Displays detailed memory licensing information for the system and detailed key
information for all memory licensing keys installed in Server Control.
Example 1
This example adds the key 511-CANDE-CDE-S with the password
AHQWOMNWEFUMDQE:
IK ADD 511-CANDE-CDE-S:AHQWOMNWEFUMDQE
Example 2
This example deletes the key 511-CANDE-CDE-S:
IK DELETE 511-CANDE-CDE-S
Example 3
This example merges SYSTEM/KEYS/511ON NI to the *SYSTEM/KEYSFILE on the
halt/load family, creates a new version of the keys file, and removes the old version:
IK MERGE SYSTEM/KEYS/511 ON NI
Example 4
This example displays the specified key, 511-ALGOL-ALG:
IK SHOW "511-ALGOL-ALG"
511-ALGOL-ALG
Example 5
This example displays the keys in the specified keys file, SYSTEM/KEYS/511ON
TEST:
511-ADDSPROPERTIES-SAP
511-ADDSPROPERTIES-SAP-S
511-ALGOL-ALG
511-ALGOL-ALG-S
.
.
.
Example 6
This example displays maintenance license keys:
IK SHOW "MAINTKEY"
MAINTKEY-MK1 12/1/2005
Example 7
This example deletes the DSA key set specified by the SSR511DSAKEYID DSA key
set ID:
IK DSADELETE SSR511DSAKEYID
Example 8
This example merges SYSTEM/DSAKEYSFILE/511 ON NI with the system DSA keys
file, creates a new version of the DSA keys file, and removes the old version:
IK DSAMERGE SYSTEM/DSAKEYSFILE/511 ON NI
Example 9
This example displays DSA key set IDs and their corresponding software levels in the
DSA keys file SYSTEM/DSAKEYSFILE/511:
IK DSASHOW KEYSFILE=SYSTEM/DSAKEYSFILE/511
Example 10
This example extracts DSA key sets whose IDs begin with SSR51 from the file
*SYSTEM/KEYSFILE on the halt/load family to the new DSA keys file
SYSTEM/KEYSFILE/SSR51 ON MCPMAST:
Example 11
This example illustrates how keys associated with ClearPath MCP Release 10.0
(release identifier 51.1) can be deleted from an active keys file.
The active keys file is first backed up to tape. The prefix string is verified with an IK
SHOW command. Keys associated with release identifier 51.1 are removed. Finally,
the delete is verified.
IK SHOW "511"
IK SHOW "511"
NO KEYS FOUND
Example 12
This example illustrates how to send a processing power metering information report
by e-mail:
IK IPSEND METER
Example 13
This example illustrates the display of metering information on a prepaid metering
system:
IK IPSHOW METER
Example 14
This example illustrates the display of metering information on a base-plus-use
metering system:
IK IPSHOW METER
Image 4@57N/2
Time 545,410 seconds 1,848 seconds
Base 0 RPM sec 0 RPM
Maximum 33,680 RPM
Total Used 42,289,541 RPM sec 78 RPM 143,289 RPM sec
Metered 42,289,541 RPM sec
--> Billable 16 RPM month (standard)
==> 1 MIPS month (standard) ID=012000ABE41A3560E03
Example 15
This example shows the display in response to an IK IPSHOW ALL command for a
system running with Java COD licensing:
IK IPSHOW ALL
IP1-RC04HBXEC87Y7T0YJCSU7TRYZEYYDN5597J381WPS2U6ANP4FZ7B
2 PERM ACTIVE A) 1@40R(100%), 1 Java IPs
IP1-RNX2MZ48HEWHBRQXJSNQZF9J7GEGB33WE0AKPYBJ8KCACTN4GZJPD
Example 16
For systems that support Java COD, this example shows how to assign a processor
to the Java processor set:
IK IPJAVA + IP-0-0-0
Example 17
For systems that support Java COD, this example shows how to remove a processor
from the Java processor set:
IK IPJAVA - IP-0-0-0
Example 18
This example shows a response to an IK IOSHOW command entered on a Libra 585
system:
IK IOSHOW
Example 19
This example shows a response to an IK IOSHOW ALL command entered on a Libra
585 system:
IK IOSHOW ALL
Example 20
This example shows the display in response to an IK IPSHOW ALL command from a
system that has defined a custom processor set:
IK IPSHOW ALL
Example 21
This example manually resends a monthly monitoring report from June 1, 2005:
IK IPSEND 20050601
Example 22
This example manually resends a monthly monitoring report specified by file name
and family name:
Example 23
For systems that support custom processor sets, this example shows how to assign a
processor to STD:1, the custom processor set:
Example 24
For systems that support custom processor sets, this example shows how to remove
a processor from STD:1, the custom processor set:
Example 25
This example shows the display in response to an IK IPSHOW ALL command on a
system running with Libra 680 Java processor licensing:
IK IPSHOW ALL
Example 26
This example shows the display in response to an IK IPSHOW ALL command on a
system running with standard processor metering and Java processor licensing:
IK IPSHOW ALL
Timeout Limitations
The system closes the KEYSFILE after 15 seconds of no activity.
To resend a missing monthly metering e-mail report to Unisys, select one of the
following commands:
One of the following three responses appears on the ODT after you send the
command:
IL (Ignore Label)
The IL (Ignore Label) command indicates that the file requested by a program
resides on the specified unit, regardless of the label on the unit. This command is
often useful for responding to NO FILE, DUPLICATE FILE, DUPLICATE PACK, or
REQUIRES PK messages.
Syntax
Explanation
If you enter the <mix number list> IL <device type> <unit number> command in
response to a NO FILE message, it specifies that the file requested by the program
identified by the mix number list is located on the specified device. This command
causes the program to open the file. If the file is unlabeled, you must use the UL
(Unlabeled) command instead of the IL command.
If entered in response to a DUPLICATE FILE message, this command has the same
effect. In this case the requested file will always be a labeled file.
Example
This example shows the response to a waiting entry and the action that the operator
took to tell the program to ignore the tape label and read the tape mounted on unit
162.
1109 IL MT 162
If the command is rejected, wait for the current command to complete and enter the
command again.
Syntax
<oldname list>
<sector format>
VSS1 or VSS2.
Explanation
This command
After the INITIALIZE command completes, you can perform one of the following
actions:
Mark the disks as scratch disks with the PG (Purge) system command.
Use the RC (Reconfigure Disk) system command to create new disk families,
add them as continuation packs to existing disk families, or create them as
SPARE mirror disks.
Note: You can avoid using the INITIALIZE system command altogether by including
the INIT and VSS options in the PG or RC system commands.
VSS1, which initializes the disk to the VSS-1 format. This format enables the
maximum amount of data to be stored on disk, but might slow performance
for some applications relative to the same disk initialized as VSS-2.
VSS2, which maps two logical, 180-byte sectors onto each physical 512-byte
disk sector. This format enables system software and applications designed
for 180-byte sector disks to efficiently use industry-standard, 512-byte sector
disks.
You must specify the VSS format for the command to be executed. If you omit the
VSS clause, the system generates the following RSVP message:
Examples
Example 1
This example initializes disk 43 to VSS2 mode:
Example 2
This example initializes disks 80, 81, and 836 to VSS2 mode. Disks 80 and 81 were
already named TEST, and disk 836 was already named ALPHA.
An attempt was made to initialize a member of a mirrored set. You must release the
mirrored disk with the MIRROR RELEASE command before the disk can be initialized.
The capacity of the disk being initialized exceeds the maximum disk capacity
supported by the MCP. The disk will be initialized to the maximum capacity
supported by the MCP.
The disk capacity is less than 64 megabytes, which is the minimum capacity required
for a self identifying disk with variable sector size.
You can use the INSTALL APPLICATION command to install the KEYSFILE, the
INSTALLDATA file, the Simple Installation (SI) program, and the files required for a
minimal running system from a specified tape or CD-ROM. If you do not specify a
tape or CD-ROM, the system uses the first ready and available library tape. If no
ready library tape exists, the installation terminates.
The other forms of the INSTALL command install only system files. These files are
needed for a running system environment and include the operating system, the
message control systems (MCSs), and any libraries, compilers, utilities, help books,
menugraphs, and so on. To install source files or generation data files such as
sample files, test files, manuals, and notes, run the Simple Installation (SI) program
interactively under either a privileged usercode or no usercode.
For more information about the Simple Installation program, refer to the Simple
Installation Operations Guide.
Syntax
<application source>
Explanation
INSTALL APPLICATION
INSTALL NECESSARYONLY
INSTALL SYSTEMSOFTWARE
INSTALL ALL
INSTALL DATAONLY
INSTALL SUPPORT
Specify the files to copy and optionally install.
APPLICATION copies the KEYSFILE, the INSTALLDATA file, the Simple Installation
(SI) program, and files required for a minimal running system from the specified
tape or CD-ROM. If you do not specify a tape or CD-ROM, the system uses the first
ready and available library tape. If no ready library tape exists, the installation
terminates.
NECESSARYONLY (the default value) copies only files needed for a minimum running
system. These files include the data comm files, Menu-Assisted Resource Control
(MARC) files, and Print System files.
ALL copies all system software files, including Enterprise Database Server software
files, needed for a running system environment. Symbol files and generation data
files are not copied.
DATAONLY copies the INSTALLDATA file in the following form if SI is already resident
on disk:
INSTALLDATAFILE/=
SUPPORT copies files from a support release. Information from the previous software
installation is used to copy the updated files to the correct families. When you use
this form of the command, the software assumes that the UPDATEINFO file (named
INSTALLDATAFILE/SYSTEM/<processor-type>) is on one of the following packs:
The pack family, if any, that you specified in the optional DISK = <family
name> clause.
The pack named DISK, if it exists on your system.
The current halt/load unit.
INSTALL KEYSFILE
Copies and merges information into the system keys file *SYSTEM/KEYSFILE from
the file SYSTEM/<release ID>/KEYSFILE for the current software release. Copies the
optional keys file SYSTEM/DSAKEYSFILE from the media to the halt/load family if the
file is on the media. The file from which information is to be copied must be on a CD-
ROM named SYSTEM_KEYS. For more information about the keys file, refer to IK
(Install Keys) earlier in this section.
If you specify CDROM, FROM, or ON, the file from which information is to be copied
must be on the media whose name is specified by <cdrom name>. If you omit the
media, the default media is used (see INSTALL KEYSFILE above).
The default value for <release ID> is the current release number such as 50.1, 51.1,
52.1 and so on.
In the file name, <compressed release ID> is the <version ID> with all
nonalphanumeric characters removed.
Examples
The following table contains examples of the INSTALL command and an explanation
of each example.
INSTALL CDROM 51150 Copies and installs the following software from a
CD-ROM named SYSTEM_51150:
INSTALLDATAFILE
SI code files
WFLSUPPORT library
GENERALSUPPORT library
CENTRALSUPPORT library
Files needed for a minimal running system
INSTALL KEYSFILE CDROM Copies the following files from the CDROM named
51150 SYSTEM_KEYS (if the system is running on MCP
software release 51.1):
SYSTEM/511/KEYSFILE
SYSTEM/DSAKEYSFILE
INSTALLDATAFILE
SI code files
WFLSUPPORT library
GENERALSUPPORT library
CENTRALSUPPORT library
Files needed for a minimal running system
INSTALL SUPPORT CDROM Copies and installs the following software from a
51150 CD-ROM named SYSTEM_51150:
Updated files
Files needed for a minimal running system
INSTALLDATAFILE
SI code files
WFLSUPPORT library
GENERALSUPPORT library
CENTRALSUPPORT library
Syntax
<time-out value>
<subtype>
Each subtype number identifies a type of disk pack, as shown in the following list.
Subtype Description
29 SCSI/131 pack
30 SCSI/130 pack
31 SCSI/577 pack
37 SCSI/674 pack
38 SCSI/280 pack
39 SCSI/564 pack
40 SCSI/287 pack
41 SCSI/552 pack
44 SCSI/286 pack
Subtype Description
45 SCSI/546 pack
49 IPI/M2671P pack
53 SCSI/1545, SCSI/1545-1, or
SCSI/1545-n packs
55 SCSI/2001, SCSI/2001-1, or
SCSI/2001-n packs
56 SCSI/3019
Explanation
Use the IOTIMER command to change the time-out value the operating system is to
use for disk READ and WRITE operations. The time-out value is used to control the
length of time allowed for an I/O operation. The assignment is independent of the
requester of the I/O operation, such as a user application or MCP. The measurement
does not represent what an application might consider to be I/O elapsed time,
because there are some architectural factors that can affect the amount of time an
I/O request takes, which are independent of the I/O time limit specified. If an error
occurs, the time-out value is used for each retry performed by the MCP.
The unit list parameter enables you to specify a time-out value for a single disk, a
range of disks, a set of disks based on a subtype (such as 53 for a SCSI/1545 pack),
or all devices defined as disks in the peripheral control diagram (PCD).
The MCP default (DEFAULT) time-out value is 80 seconds. Only valid time-out values
can be specified. A time-out value is preserved over a halt/load of the system, and
remains in effect until the user specifies a new time-out value.
All members of a mirrored set must have the same READ and WRITE time-out value
in effect. If an IOTIMER command specifies a time-out value for any member of a
mirrored set, a corresponding change is automatically made to all members of the
set.
Note: The PER PK command indicates whether or not a disk has a user-specified I/O
time-out value. The OL PK command and the IOTIMER command both display the
time-out limit currently in effect.
IOTIMER
IOTIMER PK
IOTIMER PK ALL
Displays the I/O time-out value status of all disk units in the system.
Examples
Example1
This example shows the response to a simple inquiry. The display includes the unit
number of the disk, the disk label, the family index, the time-out value in effect and
if it was set as the MCP default, the disk description, and the disk subtype number.
IOTIMER
Example 2
This example shows the response to
Example 3
This example shows the response to
Example 4
This example shows the response to
Example 5
This example shows the response to
Syntax
<wild card>
<delim>
Use one of the following characters
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters.
Character Description
You can include lowercase characters and space characters by prefixing the wild-card
string with LIT and enclosing the wild-card string in delimiters.
For example, if you enter the following syntax, the system returns entries that
contain the string "PACK":
J NAME =pack=
If you enter the following syntax, the system returns entries that contain the string
"pack":
J NAME LIT^=pack=^
Explanation
J
JOBS
Display any active jobs or tasks that have not been suppressed by the SUPPRESS
(Suppress Display) command. The J command does not display jobs in the job
queue; the SQ (Show Queue) command serves that purpose. The display includes
databases and freeze control libraries (but not other types of server libraries).
J ALL
Displays all active jobs or tasks, including any that were suppressed.
J QUEUE
JQ
Display active jobs or tasks in all queues.
J USER <usercode>
Displays only jobs or tasks running with the specified usercode.
Examples
Example 1
This example shows the response to a simple inquiry:
The heading line appears on the first page of the job and task display and before the
job and task entries in automatic display mode (ADM).
At the beginning of each entry line, an E indicates that a syntax error was discovered
during compilation. An asterisk (*) indicates that the task is being displayed for the
first time.
The Pri field shows the priority of the job or task; the priority can be followed by a
waiting (W) or scheduled (S) flag.
The next column contains the word Job if the task has no parent, Lib if the task is a
library process, or DBS if the task is a database stack. Otherwise the column is
blank.
The next column contains the job or task name of each entry.
A task initiated by a job or another task is indented by two dots under its parent. The
system can display from one to five levels of indentation. If the parent task is
suppressed, it is displayed only if the ALL option is used.
The usercode of the originator appears before the job or task name. Some tasks and
jobs can have two usercodes shown for the following reasons:
Tasks other than compiler tasks display with the following format:
Example 2
This example shows the command and response for the USER option when no
usercode is specified. The command lists the programs running without a usercode.
J USER=""
When you enter this command, the MCP clears the screen of the ODT and then
displays the file name you have entered on line 2 of the display, regardless of the
setting of the FIRST option of the TERM (Terminal) command.
When you assign a logical file name to an ODT, automatic display mode (ADM) is
stopped until one of the following conditions takes place:
Syntax
Explanation
LABEL <file name>
Attaches the specified file name to the ODT from which you enter the command.
When a program attempts to open an input ODT file with a file name that matches
the label name, the system assigns the file to the matching ODT. A program can
override this normal assignment if it specifies the UNITNO file attribute. When a
program attempts to open an output ODT file, the system assigns a SCRATCH ODT
(an ODT that has no label specification).
Any input to the attached file must be preceded by the delta character. All other
input is treated as normal ODT input.
To indicate end-of-file (EOF) to the attached file, enter a delta character followed by
?END.
Example
LABEL ODTINPUT
ODTINPUT.
PER SC
-------SC STATUS-------
1 S C R A T C H
3 ODTINPUT
CL
RESTRICT
??MARC
A halt/load also clears label assignment.
A unit cannot be relabeled if the disk pack is not ready or has any files open when
the command is entered. A disk pack assigned to the spare disk pool for the Mirrored
Disk Pooling Facility (MDPF) cannot be relabeled unless you respond OK to the RSVP
message that appears.
If the command is rejected, wait for the current command to complete and enter the
command again.
Syntax
<relabel pack>
Explanation
LB PK <unit number>
LB DK <unit number>
Relabel the pack or disk specified by the unit number.
If you attempt to label a pack that has been scratched, you receive the following
message:
Once a pack has been scratched, it must be reconfigured using the RC (Reconfigure
Disk) command before it can be brought on line.
CAPACITY <integer> MB
CAPACITY <integer> GB
CAPACITY LIKE PK <unit number>
CAPACITY FULL
For supported system models and disk models, changes the disk capacity to the
specified size, where
The LB command can only increase the capacity of a disk; it cannot reduce
the capacity.
You can use the LB command to increase disk capacity even while there are
open files on the disk.
Any modern SCSI or Fibre Channel disk can be resized. Old SCSI disks
appearing in the OL display as SCSI/419, SCSI/805, SCSI/1545, or
SCSI/3019 cannot be resized.
At the completion of the command, the following message is displayed on the ODT.
This message tells the user that the capacity of the specified unit was changed:
When the CAPACITY parameter is used, the only other parameter that can be
specified is OLDNAME. Any other combinations are rejected.
If you use the CAPACITY option on a system that does not support this feature, the
following message is displayed:
If you use the CAPACITY option for a disk unit that does not support this feature, the
following message is displayed:
FAMILY
Initiates a process to update the labels of all the family members of the family
corresponding to the PK <unit number> in the command. The process locates all the
online members of the family (the base pack must be online) and then updates their
labels. If some of the members of the family are offline, the process does not update
those labels.
You can use the FAMILY specification to change the NAME of all the disks in a family
with one command.
Note: The family and all its members must not be in use at the time or the process
cannot close the packs and is thus unable to update the labels.
The pack name entered is then compared with the pack name in the pack label. If
there is a mismatch, the task is terminated with the following error message:
OWNER = <name>
Specifies the owner identification to be assigned. The name must be from 1 to 14
characters long. If <name> contains special characters or blanks, it must be
enclosed in quotation marks. If OWNER is not specified, and either the Owner field in
the old disk pack label is blank or the pack is new, the field is filled with blanks. If
the disk pack has a nonblank owner identification, a message is displayed. You must
verify the request by entering a <mix number> OK command. To remove the
OWNER attribute, reconfigure or relabel the disk pack with the option OWNER=""
specifiedtwo sets of quotation marks indicate a null string. The equal sign (=) is
optional; either of the following is valid:
OWNER <name>
OWNER = <name>
SERIAL = <number>
Specifies the volume serial number to be used. The number must be in the range 1
through 999999. The equal sign (=) is optional. If the serial number you specify
matches an existing online serial number, the system displays the following
message:
As a result of this condition, the system leaves the unit offline with a LABEL ERROR
condition.
If you do not specify this option, the system assumes that the original serial
numberthe defaultis to be used.
If you attempt to change the volume serial number of a pack that belongs to a
multipack family, the system terminates the LB process and displays the following
error message:
SR
Specifies that the pack is to be labeled as a system resource pack. A system
resource pack is assigned the name PACK.
LB HC <unit number>
Labels the specified host control (HC) unit with the name of the hub to which it is
attached.
command fails. If more space is needed, a HUBMAP must be declared for the GROUP
specification and the RECONFIGURE action invoked.
Examples
Example 1
The following LB command assigns the name JD to the pack with unit number 66 and
owner identification JOHNDOE:
Because this command does not specify the old name of the pack (JOHN), the
system requires you to verify that it is the correct pack.
If the reply is 2273AX OLDNAME = JOHN, the labeling process can proceed.
Example 2
This example extends the capacity of PK 3104 to 5 gigabytes without affecting the
data files:
Example 3
This example shows how to change the NAME of all the disks in a family with one
command.
Example 4
This example assigns a hubname of ISC03 to the host control unit with the number
123:
If you respond OK, the designated family name is assigned to the pack, the disk is
removed from the spare disk pool, and a status change message is generated for the
disk. The status change message is defined in the MCP System Interfaces
Programming Reference Manual. The following message is displayed, confirming that
the label has been changed:
PK <unit number> UNIT LB'ED AND REMOVED FROM THE SPARE DISK POOL
If you respond DS, the following message confirms that the disk pack remains in the
spare disk pool:
When you attempt to relabel a disk assigned to the spare disk pool on a system that
does not have the Mirrored Disk Pooling Facility (MDPF) installed, the following RSVP
message appears:
If you respond OK, the designated family name is assigned to the pack and the disk
is removed from the spare disk pool. The following message is displayed, confirming
that the label has been changed:
PK <unit number> UNIT LB'ED AND REMOVED FROM THE SPARE DISK POOL.
If you respond DS, the following message confirms that the disk pack remains a free
spare in the spare disk pool:
If your system does not support MDPF, relabeling a disk removes the disk from the
spare disk pool and no message appears.
LC (Log Comment)
The LC (Log Comment) command enters a comment in the system log file
SYSTEM/SUMLOG.
Syntax
Explanation
LC <text>
Enters the specified text in the SYSTEM/SUMLOG file.
Example
LC BEGIN COMPILER TESTS
COMMENT LOGGED
Syntax
Explanation
<mix number list> LG
Starts logging all events for the tasks in the specified mix number list.
Value Significance
You can specify any number from 0 through 15. For example, a value of 5 (value 1
plus value 4) causes logging of all successful actions and all security-relevant
actions.
Examples
Example 1
4872 LG
Example 2
3298,3367 LG 0
See Considerations for Use for an explanation of default high-end memory (HEM)
firmware and for instructions on copying firmware files.
Syntax
<source>
<mark>
A one- or two-digit integer.
<cycle>
A one-, two-, or three-digit integer.
Explanation
:TEMP
Use the current firmware once. Then the device reverts to using default HEM
firmware.
:KEEP
Use the current firmware indefinitely. This is the assumed duration when you load
non-HEM firmware, unless you specify :TEMP.
LH ALL :TEMP
Loads no firmware. The duration of all LH-loadable devices is changed so that all
devices revert to HEM firmware use when they are next initialized.
LH ALL :KEEP
Loads no firmware. The duration of all LH-loadable devices is changed so that all
devices remain on their current firmware indefinitely.
FIRMWARE/<mark2>_<cycle3>/FCIOP ON <family>
FIRMWARE/<mark2>_<cycle3>/C4FT ON <family>
FIRMWARE/<mark2>_<cycle3>/FC2IOP ON <family>
FIRMWARE/<mark2>_<cycle3>/CA/<component> ON <family>
The <component> variable is either SCSI or FCHP, the <mark2> variable is a two-
digit representation of <mark>, and the <cycle3> variable is a three-digit
representation of <cycle>.
The MCP determines the component based on the model of the port.
Examples
Example 1
The following command loads the FCIOP card of FC-2IOP 1 with the proper FC2IOP
default HEM firmware. IOP1 has its SAVED status reset and is initialized after the
load.
Example 2
The following command loads the FCIOP card of FC-1 IOP 2 with the firmware file
TESTFW/FCIOP ON TESTPACK. The SAVED status of IOP 2 is reset. The C4FT
connection of IOP 2 is loaded with the firmware file TESTFW/C4FT ON TESTPACK as
IOP 2 is initialized. The firmware images are used only for this single initialization of
IOP 2, after which IOP 2 and its C4FT revert to using default HEM firmware.
Example 3
The following command loads the firmware file FIRMWARE/01_015/CA/FCHP ON
MYFAMILY to the high-performance Fibre Channel adapter at port 31001. The port is
initialized on the new firmware and the RESERVED state is reset if previously set.
The port continues indefinitely to initialize on this firmware.
Example 4
The following command loads the firmware from file MY/FIRMWARE/CA/FCHP ON
THEFAMILY for legacy FCHP port 31001. The port is initialized on the new firmware
and the RESERVED state is reset if previously set. However, the port reverts to
default HEM firmware on future initializations.
Example 5
The following command changes the duration of the firmware currently loaded into
port 31001 to PERMANENT. The port continues to initialize on its current firmware
indefinitely. No other immediate action is taken with regard to port 31001. (This
action might be appropriate if the test firmware loaded to port 31001 by the previous
example proved to function correctly.)
The firmware I/O CD-ROM used when a system data set (SDS) was created
A substituted I/O CD-ROM that a user has loaded into server control
HEM firmware is the default firmware used to initialize IOPs and ports unless you
specify otherwise with LH commands.
Firmware files are provided on an I/O firmware CD-ROM. You can download firmware
updates from the Unisys Product Support Web site. The only files that you need to
copy are the IOF files (*.IOF). The MCP supports loading of all the IOF files except
the file named FCIOP.PSD.nnn.nnn.IOF.
You can either create a CD-ROM from the download to mount in a PC, or you can
copy the files directly to a PC. Then you can copy the necessary files to a directory in
an MCP disk family share that has been created with Client Access Services (formerly
NX/Services) by using a normal Windows Explorer copy-and-paste operation.
Here is an example of the supported IOF files contained on an I/O firmware CD-ROM:
C4FT.02.013.iof
CA.FCHP.23.011.iof
CA.SCSI.93.552.iof
FC2IOP.02.105.iof
FCIOP.01.017.iof
C4FT
CA/FCHP
CA/SCSI
FC2IOP
FCIOP
These files should normally be copied into a subdirectory such as IOCD_01_034 that
describes the source of the files. Note that the required file structure adds an extra
directory node, CA, to the location of the channel adapter firmware files.
When you load a firmware file using the DIRECTORY syntax, the appropriate suffix is
always added to the DIRECTORY specification to get the target firmware file. For the
FCIOP card of an FC-1 IOP, the firmware file sought is <directory name>/FCIOP ON
<family name>. The <version ID> form of <source> is equivalent to a <source>
specification of DIRECTORY FIRMWARE/<mark>_<cycle> ON <family name>.
For example, assume that the firmware files are copied into subdirectory
IOCD_01_034 of the share IOFIRMWARE and are renamed within that subdirectory
as previously described. Also assume that the IOFIRMWARE share is defined as
(ADMIN)IOFW on a family named HL. The required <directory name> in the LH
syntax would be (ADMIN)IOFW/IOCD_01_034 and the <family name> would be HL.
Syntax
Notes:
Explanation
For IOM systems, the mnemonic DLP is always treated as identical with the
mnemonic CTL. The nonpreferred synonym DLP is often used when referring to a
control device that is an MLI-protocol data link processor.
The default title is determined by the type of the disk pack controller. The type of a
controller is shown in the second line of the response to an OL PK <number>
command that specifies any pack controlled by that controller. Depending on the
controller type, the file title is as follows.
B9387 CONTROLWARE/B9387
B9387S CONTROLWARE/B9387S
B9389 CONTROLWARE/B9389
The DLP or control must have been reserved previously. You can reserve or
unreserve a device by using the UR (Unit Reserved) system command or by using
the maintenance console.
Once you enter this command, the system creates a waiting entry with an RSVP
message warning that the system will stop all traffic to the ODT and Maintenance
LAN devices, such as SCP and SCX units. You can make either of the following
replies.
Reply Action
On partitions with multiple Maintenance LAN channels in use, you must reserve the
alternate port (the port not being downloaded) before entering the LH PORT
command; and unreserve the port after completion, using the UR (Unit Reserved)
command. The microcode file to be downloaded must be located on the halt/load unit
family.
Examples
Example 1
The following commands load the specified pack controlware files to the specified
CTL or DLP:
Example 2
The following command loads the firmware from the file
SYSTEM/CON2/FIRMWARE/0322B ON HLUNIT451 to the Maintenance LAN Channel
Adapter flash PROM for port 18101:
As a result of the preceding command, a waiting entry with the following RSVP
message appears:
Syntax
<wild card>
<delim>
Use one of the following characters
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters.
Character Description
You can include lowercase characters and space characters by prefixing the wild-card
string with LIT and enclosing the wild-card string in delimiters.
For example, if you enter the following syntax, the system returns entries that
contain the string "PACK":
If you enter the following syntax, the system returns entries that contain the string
"pack":
Explanation
LIBS
LIBRARIES
Display all unsuppressed frozen library stack entries.
LIBS ALL
Displays all frozen library stack entries, including suppressed ones.
LIBS Q
Shows all libraries that were originally initiated from a job through a job queue.
Examples
Example 1
This example shows output from the LIBS command:
LIBS
An asterisk (*) at the beginning of an entry line indicates that the entry is being
displayed for the first time. The Mix field gives the mix number of the library stack
entry. The Frz (Freeze Type) field shows whether the library is a permanent server
library (Perm), temporary server library (Temp), control server library (Ctrl), or
connection library (Conn).
The Shr (Shared Specifications) field contains one of the following values.
Value Meaning
Priv Private
The Usr (Users) field shows the number of clients linked to a server library. No value
is listed for connection libraries.
The letters SL after the User Count field indicate a support library.
Example 2
This example shows output from a LIBS command that uses the NAME option with a
wild-card string:
LIBS NAME=SERV=
Syntax
<option>
The following table shows valid options, their categories, and their purposes. Items
followed by asterisks in parentheses (*) are standard options. Specify the
STANDARD option to set or reset all standard options.
Explanation
LIBTRACE
LIBTRACE SHOW
Display the existing SET options and the existing RESET options.
LIBTRACE +
LIBTRACE SET
Display the existing set options.
LIBTRACE
LIBTRACE RESET
Display the existing reset options.
LIBTRACE NONE
LIBTRACE RESET ALL
Reset all options.
LIBTRACE HELP
LIBTRACE <invalid syntax>
Display the LIBTRACE syntax diagram.
LIBTRACE + <option>
LIBTRACE SET <option>
LIBTRACE SET STANDARD
Set designated options.
LIBTRACE <option>
LIBTRACE RESET <option>
LIBTRACE RESET STANDARD
Reset designated options.
Example
Example 1
This example turns on the LINKING, LOCKING, TOLOG, and LOGIC options.
Example 2
Based on the command entered in Example 1, this example shows an inquiry
concerning options that have been set and its response.
LIBTRACE +
Example 3
This example turns off the DELINKING, TEMP, and LINENUMBERS options.
Example 4
Based on Example 3, this example shows an inquiry concerning options that have
been reset and its response.
Example 5
This example shows a command that resets all options.
LIBTRACE NONE
Example 6
This example shows the command and response for the standard set of options.
LICENSESTATUS
The LICENSESTATUS command returns information about the master license keys
and the status of the LICENSESUPPORT library. The command enables the operator
to restart the collection of data about the usage of license keys.
Syntax
Explanation
LICENSESTATUS
LS
Displays information about the master license keys stored in the system keys file,
the machine control number (MCN), and the status of the LICENSESUPPORT library.
LICENSESTATUS RESTART
LS RESTART
Terminates linkage to the existing LICENSESUPPORT library and initiates a new copy
of the library.
Examples
Example 1
LICENSESTATUS
MCN: 1234567890ABCD
Example 2
LS RESTART
LJ (Log to Job)
The LJ (Log to Job) command enters a comment for a specific job or task in the job
log and in the system log, SUMLOG.
Syntax
Explanation
<mix number list> LJ <user text>
Enters user text into the job logs and system log for the jobs in the specified mix
number list.
Example
The following command makes the comment GREAT JOB appear on the
JOBSUMMARY printout for job 3335:
Syntax
<version>
Explanation
LOADMICROCODE CPM <mark>.<cycle>
LOADMICROCODE IOM <mark>.<cycle>
Load microcode with the stated version level for the central processing module (CPM)
or I/O module (IOM).
Example
This example loads microcode for a CPM.
Error Conditions
If the console determines that the specified microcode version is not installed, the
system displays the following error message:
If the console determines that the specified microcode version is not compatible with
the current Logic Release Level (LRL), the system displays an error message similar
to the following:
Syntax
Explanation
LOG
Performs a complete analysis of the current system log if no log parameters are
specified.
Examples
LOG 1700 BOT EOT MAINT MSG
LOG MAINT MT 48
If security administrator status is authorized for the system, then the forms of this
command that change the logging options can be invoked only by a security
administrator usercode. The forms of the command that display logging options are
not restricted.
For more information about logging options, refer to the System Log Programming
Reference Manual.
Syntax
<major>
<minor>
If you specify SUMLOG or JOBFILE, the system applies ALL or NONE to that log only.
If you do not specify SUMLOG or JOBFILE, the system applies ALL or NONE to both
the SUMLOG and the JOBFILE. The specification ALL means that the system should
log the unspecified major or major and minor type. The specification NONE means
that the system should not log the specified major or major and minor type.
Explanation
LOGGING
Displays the current logging option specification.
LOGGING <major>
Displays the current logging option specification for all minor types under the
specified major type.
LOGGING <major>,<minor>
Displays the current logging option specification for the specified minor type under
the specified major type.
LOGGING *
Sets the current logging option specification to the system default value. For a
definition of the default value, refer to the System Log Programming Reference
Manual.
LOGGING DEFAULT
LOGGING *
Sets the current logging option specification to the system default value. For a
definition of the default value, refer to the System Log Programming Reference
Manual.
LOGGING MINIMAL
Sets the current logging option so that only the most required records are logged.
For more detailed information, refer to the System Log Programming Reference
Manual.
LOGGING ALL
Removes the logging option specification, with the result that all log records are
written to the SUMLOG file and the applicable job file.
Examples
Example 1
LOGGING DEFAULT
Logging Settings:
(display of default logging settings)
Example 2
LOGGING 1,8
Logging Settings:
Logging 1,8 Sumlog None, Jobfile All
Example 3
LOGGING 17 SUM ALL
Logging Settings:
Logging 17 Sumlog All, Jobfile None
Example 4
LOGGING 4; 7,5
Logging Settings:
Logging 4,1 All;4,2 All;
Logging 4,3 All;4,4 All;
Logging 4,5 All;4,6 All;
Logging 4,7 All;4,8 None;
Logging 4,9 None;4,10 All;
Logging 4,11 All
No Minor Type 7,5. Logging 7 All;
LP (Lock Program)
The LP (Lock Program) command prevents DS (Discontinue), QT (Quit), and
RESTART (Restart Jobs) commands from terminating the specified processes or
programs.
A process is automatically locked if the code file has been marked with the MP +
LOCKED form of the MP (Mark Program) command.
Syntax
Explanation
<mix number list> LP
Locks the processes in the specified mix number list and prevents them from being
discontinued by a DS (Discontinue), QT (Quit), or RESTART (Restart Jobs) command.
Once a process is locked, any internal offspring initiated by the process is also
automatically locked. Internal offspring are processes that result when a parent
process initiates an internal procedure with the CALL or PROCESS statement.
The <mix number list> LP command does not affect the object code file of the
processes. Other processes created by initiating the same object code file do not
receive the effects of this form of the LP command.
Examples
Example 1
4872 LP
Example 1
3298 LP
MAX (Maximums)
The MAX (Maximums) command interrogates or sets various maximum values for
some system variables.
Syntax
<number>
For the MESSAGES and COMPLETED options, the maximum value is 500.
Explanation
The maximum values (<number>) for SESSION, MIX and STACK options are
determined by the systems architecture and configuration.
MAX
Returns the current maximum values for the variables and the current MoreTasks
state. The maximum configurable value for each option is displayed as well.
Note: The values of the variables apply to both network and non-network
messages.
The maximum mix number is always less than or equal to the maximum session
value. If the maximum mix value specified is greater than the maximum session
value, then the maximum session number is automatically increased to equal the
maximum mix number. Currently, the maximum session number that can be
specified is 65535. Higher specifications are automatically reset to that number.
When the maximum session number is greater than the maximum mix number, then
session values range from 1 greater than the maximum mix number through the
maximum session number. When all the session numbers in that range are allocated,
additional session numbers are allocated from unused numbers in the mix range.
When the maximum session number is the same as the maximum mix number, then
session numbers and mix numbers are allocated from the same pool.
Larger session numbers ( greater than 9999) are given to a program only if that
program has indicated in the MCSLOGGER call that a larger session number is
acceptable. MCSLOGGER is a DCALGOL intrinsic that message control systems
(MCSs) use to allocate session numbers.
If the MORETASKS option is RESET, then the maximum mix number value is always
9999. If the MORETASKS option is SET, then you can set the maximum mix number
value to any number up to 65535. If you assign a maximum mix number value
higher than 65535, the system changes the value to 65535.
The maximum mix number value is always less than or equal to the maximum
session number value. If you specify a maximum mix number value that is greater
than the current maximum session number value, then the system automatically
increases the maximum session number value to equal the new maximum mix
number value.
If the MORETASKS option is RESET, then the maximum stack number value is always
4095. If the MORETASKS option is SET, then you can set the maximum stack
number value to any number up to 32767. If you assign maximum stack number a
value higher than 32767, the system changes the value to 32767.
When you increase the maximum stack number value, the change might not take
effect until the next halt/load. This delay occurs if the requested maximum stack
number value requires the use of more ASDs than the system has currently reserved
for that purpose. If sufficient ASDs are already reserved, then the change takes
effect immediately.
Examples
Example :
This example displays the current settings.
MAX
Example 2
This example updates the number of messages to be saved by the system.
Example 3
This example updates the number of completed messages to be stored by the
system.
Example 4
This example updates the mix and stack limits. It assumes that the MORETASKS
system option is SET; otherwise, the new MIX and STACK values would not have
been accepted. Note also that the SESSION maximum in this example is
automatically increased to match the new MIX maximum.
Syntax
Explanation
The MCS command provides the following summary and status information.
Display Meaning
MCS SUMMARY The name of the MCS. Any family specified for an MCS
name is the default family for that MCS in the
DATACOMINFO file. It is not necessarily the family upon
which the currently active MCS code file actually resides.
Example
MCS
--Mix-Status---Tasks--Stations--Num------MCS SUMMARY-------
1234 ACTIVE 14 356 1 SYSTEM/CANDE
354 ACTIVE 32 127 2 SYSTEM/COMS
INACTIVE 3 3 SYSTEM/RJE
Set a system-wide memory dump type to override the dump call initiated by
the operating system.
Set the noncompression option for system dumps.
Suppress dumps by dump number.
Automatically suppress repeat occurrences of a given dump.
Set up a history file for collection of dump information.
Interrogate the various dump parameters.
Set the option to automatically unload a dump from the dumpdisk file.
Set the option to automatically create a Dumpanalyzer SAVEDUMP when
unloading a dump from the dumpdisk file.
For more information, refer to Memory Dump Processing and Memory Dump
Commands.
A dump number is a unique 7-digit number assigned by the system to each memory
dump request and used to identify a dump for suppression. The dump number
appears on the memory dump status screen at the time of the dump, in the heading
printed by DUMPANALYZER, and in response to an MDT SHOW request.
An autosuppress entry number is relevant only when an MDT HISTORY file has been
loaded, and corresponds to a unique entry in the file. The entry number is used to
identify dump occurrences that are candidates for automatic suppression.
Explanation
MDT
Displays the current settings for the MDT options, including the dump type, the
HISTORY file name, and counts of dumps in the dump history file.
MDT ALLINUSE
Specifies that all subsequent partial memory dumps are to be overridden by
ALLINUSE memory dumps. Only the memory areas that are present in memory and
are being used are to be dumped.
MDT AUTOSAVE
Sets the AUTOSAVE option. When this option is set, a memory dump is automatically
unloaded and converted into a DUMPANALYZER SAVEDUMP.
MDT AUTOSAVE
Resets the AUTOSAVE option.
Note that automatic suppression can occur only for dumps recorded in the dump
history file, which you must have created previously with the MDT HISTORY
command.
MDT AUTOSUPPRESS
Sets the global AUTOSUPPRESS option. This option specifies that, if any dump in the
dump history file occurs again, the system logs the new dump request but
suppresses the actual dumping of memory.
This option does not change the AUTOSUPPRESS flags for individual entries in the
dump history file. Instead, this global option overrides the effect of all individual
flags until the global option is reset.
MDT AUTOSUPPRESS
Resets the global AUTOSUPPRESS option.
MDT AUTOUNLOAD
Sets the AUTOUNLOAD option. When this option is set, a memory dump is
automatically unloaded from the dumpdisk file.
MDT AUTOUNLOAD
Resets the AUTOUNLOAD option. When this option is set, a memory dump is
automatically unloaded from the dumpdisk file.
MDT COMPLETE
Specifies that all subsequent memory dumps are to be complete, and that the entire
memory is to be dumped, regardless of the type of dump requested by the operating
system.
MDT DEFAULT
Specifies that no value has been defined. The type of dump initiated by the system is
not overridden.
MDT HISTORY
Displays the name of the MDT history file, or specifies that no history file is available.
MDT HISTORY
Removes the current dump history file name.
MDT MINIMAL
Specifies that all subsequent memory dumps are to be overridden by MINIMAL
memory dumps. A MINIMAL memory dump captures only a subset of the information
contained in a conventional dump. For a list of the items reported in a MINIMAL
dump, refer to DUMP (Dump Memory).
The MDT MINIMAL command does not immediately take effect; instead, it creates a
waiting entry that requests operator verification of the change. To confirm the
change, enter an OK response. To prevent the change, discontinue the waiting entry
with the DS (Discontinue) system command.
Caution
The MDT MINIMAL command is intended for use only by sites that find the delay
involved in a conventional memory dump to be unacceptable. Be aware that the
information in a MINIMAL dump might not be sufficient to resolve the problem for
which the dump was requested. User Communication Forms (UCFs) submitted
with MINIMAL dumps might be suspended or ultimately closed because of
insufficient information.
MDT NONCOMPRESS
Resets the NONCOMPRESS option.
MDT SHOW
Is synonymous to the MDT SHOW ALL request.
Examples
Example 1
This example displays the memory dump options.
MDT
Example 2
This example suppresses all SETSTATUS dumps.
The settings for Memory Dump options have been changed as follows:
Example 3
This example shows suppressed dumps.
--- Dump Number -- Dump Reason --------- Dump Action & Type ----
Example 4
This example shows the current dump history.
Example 5
This example shows the history for SETSTATUS dumps.
Autosuppress Entry #: 23
--------------------
Autosuppress Flag: Off
Autosuppress Count: 3, Last Suppressed: 12/13/1995 @ 11:28
Example 6
This example marks dump entry 23 for automatic suppression.
MDT AUTOSUPPRESS 23
The settings for Memory Dump options have been changed as follows:
The number of MDT units is based on the current configuration. Therefore, if MDT
units are acquired in a partition but do not really exist, they should be freed from the
partition. For more information, refer to the Free (Free Resource) command for IOM
systems and the DOWN (Down Resource) command for IOP systems.
Manual
Automatic
Using Manual Suppression
Manual suppression is based solely on the dump number of a particular memory
dump request. It guarantees that no additional memory dumps for a particular dump
number are to be taken, regardless of the circumstances leading to the dump
request. This action might result in dumps being suppressed for problems not
previously reported, but it also allows suppression of a dump that occurs under many
different circumstances for the same problem.
The SAVEDUMP file is created on the DL DPFILES family. If the DL DPFILES family is
unspecified or unavailable, the SAVEDUMP file is created on the halt load family. The
title of the file includes the SAVEDUMP prefix. The remaining nodes are formatted in
the same manner as a DP file as described in the explanation for the DL DPFILES
(Disk Location) command.
When using the MDT AUTOSAVE mechanism or responding with the AX SAVE system
command, the software versions of DPASUPPORT and SDASUPPORT are compared.
If a mismatch is detected, the save operation is not completed and
DUMPDISKMASTER reports an open error and displays a message indicating which
code file settings are incorrect. At this point, either the dump can be unloaded as a
raw dump by responding with the AX OK system command, or the SL settings can be
corrected and the AX SAVE system command can be tried again.
When you use the MDT HISTORY option, the system ignores the history file and
disables automatic dump suppression.
Syntax
Explanation
MEMORYCEILING
Displays the current and maximum memory ceiling values and indicates whether the
fast memory dump feature is enabled.
MEMORYCEILING
Removes the current memory ceiling.
MEMORYCEILING DEFER
Removes the current memory ceiling on the next halt/load.
Example
This command queries the memory ceiling size:
MEMORYCEILING
On systems that do not require memory licensing, the licensed memory size is
simply the partition memory size.
If you are using host-based mirroring, all MIRROR commands require the
MIRRORING system option to be set by the OP (Options) command before the
previous halt/load. You can use the MIRROR commands with the MIRRORING system
option reset with Business Continuance Volume (BCV) disks.
On systems with the Mirrored Disk Pooling Facility (MDPF) installed, the MIRROR
command is also used to set or reset the in-use spare attribute on labels for disks
assigned to the spare disk pool. Use this command initially to establish the pool of
in-use spare disks, and thereafter to manually add disks to or delete disks from that
pool.
You cannot use this command on a pack that has an active DUMPDISK or
HLDUMPDISK file. Mirror disks must have the same capacity as the disks for which
they are copies.
Syntax
<global options>
<readdistribution option>
Explanation
MIRROR AUDIT PK <unit number>
Closes the pack specified by the unit number, leaving the remaining members of the
set online. An audit table is established for the pack, so it can be synchronized with
the other members of the set if it is later returned online.
After auditing has been established with this command, I/O activity is not resumed
to the auditing member until a RY PK <unit> command is executed. Refer to the RY
(Ready) command.
Caution
As with any offline mirror, a member that is being audited as a result of this
command is released from the set and must be recreated if a halt/load occurs
before it is brought back online.
One benefit of this command is that it enables you to create a new mirror without
incurring the penalty of retrying I/Os to the offending mirror. That is, if a mirror
experiences a number of recoverable errors, you can take it offline with the MIRROR
AUDIT PK command, then create a replacement mirror with the MIRROR CREATE
command. Since I/Os are not being issued to the offline mirror, the CREATE
operation is not affected by I/O retries.
When the CREATE operation completes, you no longer need the offline mirror and
can release it with the MIRROR RELEASE OFFLINE COPIES command.
If the CREATE operation fails to complete, you can still recover the offline mirror,
because the MCP maintains an audit trail. Issuing an RY PK command brings the
mirror back into the set. The RY PK command can also be used if the condition
causing the recoverable errors is corrected without writing to the pack.
The pack designated by the unit number must be an online member of the set. If the
command is issued to a member that is not online, the command is rejected and the
following message is displayed:
At least one other online member must be present. If the command is issued to the
last online member of a set, the command is rejected and the following message is
displayed:
Once the command is entered, copying begins. The new member automatically goes
online when the copying is complete.
A disk added to the mirrored set is given the same time limit value as the current set
members. The time limit of the set applies to the new member as it is being created.
If an error prevents the disk from becoming an online member of the set, the
original time limit is restored to the disk.
The command is rejected if four members already exist in the mirrored set. If the
destination pack is in use or is already a member of a mirrored set, the command is
also rejected.
A check is first made to verify that the SAN Mirror Disk Manager key is present.
If not, the operation is aborted and the following message is displayed:
A check is made to verify that all family members are present. If not, the
operation is aborted and the following message is displayed:
PK <unit number> NOT ALL FAMILY MEMBERS PRESENT. MIRROR IMPORT HAS BEEN
ABORTED. I/O ACTIVITY CAN BE RESUMED.
A check is made to verify that all family members have been marked. If not, the
import operation is aborted and the following message is displayed:
PK <unit number> NOT ALL FAMILY MEMBERS ARE MARKED. MIRROR IMPORT HAS
BEEN ABORTED. I/O ACTIVITY CAN BE RESUMED.
A check is made for each mirror set that comprises the family to ensure that the
snapshot copy and at least one other member of the mirror set is online. If not,
the operation is aborted and the following message is displayed:
PK <unit number> MIRROR SET MUST CONTAIN AT LEAST TWO ONLINE MEMBERS.
MIRROR IMPORT HAS BEEN ABORTED. I/O ACTIVITY CAN BE RESUMED.
After the initial verification is complete, the members of the mirror set to be
imported are placed offline by the MCP and are audited until successfully imported.
The audit is maintained for the sake of error recovery. Once all the units are being
audited, I/O activity can be resumed to the quiesced family. At this time the
following message is displayed:
PK <unit number> MIRROR IMPORT COMMAND INITIATED. I/O ACTIVITY CAN BE RESUMED.
If an I/O error is encountered while trying to import a snapshot candidate, the failing
mirror member is released from the mirror set. Family members that had been
successfully updated prior to the I/O error are restored and are returned to the
MARKED state. Audits are applied and these members are brought back online.
A mirror must be recreated to replace the failing disk. The new snapshot candidate
must then be marked. If this situation occurs, the following message is displayed:
A check is first made to verify that the HOST COMPONENT FOR EMC TIMEFINDER
key is present. If not, the operation is aborted and the following message is
displayed:
A check is made to verify that all family members are present. If not, the
operation is aborted and the following message is displayed:
A check is made to verify that all family members have been marked. If not, the
operation is aborted and the following message is displayed:
PK<unmarked unit number> UNIT NOT MARKED. MIRROR IMPORT OF PK<unit number>
ABORTED.
A check is made to verify that all family members are present. If not, the
operation is aborted and the following message is displayed which specifies the
family index of the member which is not present:
PK<unit number> UNIT NOT AVAILABLE. FAMILY INDEX <family index> MISSING. MIRROR
IMPORT ABORTED.
When the RETAIN option of the MIRROR IMPORT command is entered, the original
copy of the BCV device should not be online. Use the CLOSE (Close Pack) and FREE
(Free Resource) commands to place the original copy off line. This action avoids the
generation of a duplicate serial number and allows the BCV device to be acquired
using the ACQUIRE (Acquire Resource) command.
A check is first made to verify that the HOST COMPONENT FOR EMC TIMEFINDER
key is present. If not, the operation is aborted and the following message is
displayed:
A check is made to verify that all family members are present. If not, the
operation is aborted and the following message is displayed:
A check is made to verify that no family member has been marked. If so, the
operation is aborted and the following message is displayed:
If any I/O error occurs during the IMPORT operation of a BCV device, the operation is
aborted and the following message is displayed:
PK<unit number> IMPORT OPERATION FAILED. SEE THE SYSTEM MESSAGE MANUAL FOR
RECOVERY INSTRUCTIONS.
To recover, you must first close and free all the BCV devices representing the family
by using the CLOSE (Close Pack) and FREE (Free Device) commands, including the
BCV device that received the error. This action informs the MCP that these units are
no longer accessible.
Using EMC TimeFinder, you can then establish a BCV mirror using the ESTABLISH
command to replace the BCV which failed and RE-ESTABLISH the remaining BCV
mirrors representing the family in order to apply any audits maintained by
TimeFinder. Once the BCV units representing a family are RE-ESTABLISHED, the
process of creating a snapshot can be repeated.
This command provides unique identification for a snapshot copy. This enables it to
be imported from its original. This command checks the following:
The SAN Mirror Disk Manager key must be installed to mark a snapshot
candidate.
If a member that has been marked in the mirror set already exists , the
operation is aborted.
If the disk has been marked, the phrase MARKED is displayed. If the disk has not yet
been marked, the phrase UNMARKED is displayed. This information is displayed in
the following format for each family member:
------------------MARK STATUS-------------------
If an I/O error is encountered while trying to update a snapshot candidate, the failing
disk is released from the mirror set and you are notified. A mirror must be recreated
to replace the failing disk. The snapshot candidate must then be marked. If this
situation occurs, the following message is displayed:
PK<unit number> MARK OPERATION FAILED. THE FAILING MIRROR HAS BEEN RELEASED.
RECREATE A MIRROR TO REPLACE THE RELEASED MIRROR.
The HOST COMPONENT FOR EMC TIMEFINDER key must be installed in order to
mark a BCV. If it isn't installed, the following message is displayed:
A check is made to verify that the serial number is unique. If it isn't unique, the
operation is aborted and the following message is displayed:
If the BCV has been marked, the phrase MARKED is displayed. If the BCV has not yet
been marked, the phase UNMARKED is displayed. This information is displayed in the
following format for each family member:
-----------------MARK STATUS-----------------
If any I/O error occurs during the MARK command, the operation is aborted and the
user is notified that the process to mark the unit has failed. The following message is
displayed:
To recover, the user must first CLOSE and FREE all the BCV devices representing the
family, including the BCV that received the error. This informs the MCP that these
units are no longer accessible.
Using EMC TimeFinder, you can ESTABLISH a BCV mirror to replace the BCV that
failed and RE-ESTABLISH the remaining BCV mirrors representing the family in order
to apply any audits maintained by EMC TimeFinder. This is necessary to ensure that
the data on the family is coherent. Once the BCV units representing a family are RE-
ESTABLISHED, the process of creating a snapshot can be repeated.
The value must be a number between 0 and 20. A non zero value causes the
MIRROR_CREATE independent runner to wait <value>*1/20ths of a second between
data transfers when it is applying an audit to a returning off-line member. The value
0 clears a previously specified delay, so that audit transfers are executed without
any induced delay.
This delay is not used when creating a new mirror (for example: MIRROR CREATE PK
<x> FROM PK <y>).
The following example changes the global delay setting to 3/20ths second.
Auditing offline members. If the system takes this action, it displays the
following message during initialization. This message remains until
acknowledged with an OK command, but does not delay system initialization:
Releasing the missing members. The system takes this action if the outstanding
write list (OWL) was lost for a RECOVERY=DISCARD mirrored set. The system
displays the following message during initialization. This message remains until
acknowledged with an OK command, but does not delay system initialization:
Note that the HLAUDIT setting forces the mirrored set online only if the set was
previously online and the partial set condition arose during halt/load initialization. If
a partial mirrored set condition arises for a set that was never completely online, or
for which there was no MIT entry, or at any other time during system running, the
system reverts to its default behavior of waiting for operator intervention. This
restriction prevents the possibility of automatically bringing online an out-of-date
copy of a mirrored volume. This restriction also prevents the system from breaking a
mirrored set needlessly if one copy is erroneously made accessible to a system, or if
the operator fails to enable access to all members of a mirrored set being brought
online.
For information about how the system distributes read operations among mirrored
disks, refer to the description of the READDISTRIBUTION option later in this
discussion.
The READDISTRIBUTION option takes effect on the next read from an online
member of the mirrored set. The READDISTRIBUTION option is preserved across
halt/loads.
The READDISTRIBUTION option can be used with any disk that is eligible for
mirroring.
If the mirrored set is not caching, read operations are rotated evenly among the
online members of the mirrored set.
For example, assume a mirrored set consisting of PK 45 and PK 55. The following
command assigns the default read distribution algorithm to the mirrored set. If the
mirrored set is caching, the static partitioning algorithm is used. If the mirrored set
is not caching, reads are distributed evenly between PK 45 and PK 55.
address space is not rotated. Following are the effects of this value for various types
of sets:
For a two member set, the first half of the address space is assigned to the first
online mirror, and the second half of the address space is assigned to the second
online mirror.
If a third member is added to the set at a later time, the address space is
automatically divided into thirds.
Depending on the application environment, use of the BYADDRESS value can provide
a dramatic performance boost. For example, consider a mirrored set consisting of
disk devices having their own cache. If the application data is larger than the cache
memory of the disk, it might be possible to set the READISTRIBUTION so that the
cache memory of each mirrored set member holds a portion of the application data,
thus increasing the frequency of read hits from cache memory.
For example, assume a mirrored set that consists of PK 100, 101 and 102, each
having a capacity of 3 million sectors. The following command causes the MCP to
assign the address space evenly among the online members of the set since no
explicit stripe size was provided, as follows:
Note that if PK 100 is offline (not ready) at the time the command is entered, the
system assigns address 0 through 1,499,999 to PK 101 and addresses 1,500,000
through 2,999,999 to PK 102. When PK 100 returns online, the system automatically
divides the address space in thirds between all three online members.
Since the BYADDRESS qualifier does not use rotation of address space, it is a good
idea to choose a stripe size that involves all members of the mirrored set. This
selection ensures that a member does not go unnoticed, if broken. Read operations
that are directed to multiple address regions of the set can be directed to one
member, while read operations to other regions are directed to different members.
This interleaving of the read distribution might be better suited to a random read
environment.
For example, assume a mirrored set that consists of PK 500 and PK 600, each
member having a capacity of 8 million sectors. The following command assigns the
address space in stripes of 2 million sectors:
Note that if PK 500 is offline (not ready) at the time the command is entered, all
reads are directed to PK 600. When PK 500 returns online, the address space is
automatically divided as previously described.
If a third member, PK 700, is added to this mirrored set, the address space is
assigned as follows:
As another example, assume a mirrored set that consists of PK 900 and PK 920,
each member having a capacity of 4 million sectors. The following command assigns
the address space in stripes of 3 million sectors:
If the outstanding write list (OWL) is lost and the DMS option is set, the mirrored
packs are brought up as a set after a halt/load and are not necessarily identical.
You can select the RECOVERY option for an entire mirrored set by specifying the
option for any one of its members.
Note: Do not use the DMS option if the pack includes items that are not audited.
For example, you should put the DMSII database control file on a mirrored pack that
does not have RECOVERY = DMS specified. If you specify the DMS option for sets
that include items that are not audited, the sets might not be identical and might
give inconsistent results on future read operations.
Use the following options to initially establish the pool of in-use spare disks and
thereafter to manually add disks to or delete disks from that pool.
Note: Use the RC (Reconfigure Disk) command to identify a disk as a free spare.
SPARE ON. Enters all online members of the mirrored set into the MDPF spare
disk pool. This pool is a collection of disks available for automatic replacement of
failed mirrors. If your system does not have MDPF installed, the command is
rejected and the following RSVP message appears:
<mix #> PK<unit number> REQUEST REJECTED: THE REQUIRED FEATURE KEY
IS NOT INSTALLED
A system message and a status change message are generated for each member
successfully added to the spare disk pool. The status change message is defined
in the MCP System Interfaces Programming Reference Manual. The following
system message appears:
SPARE OFF. Removes all members of the mirrored set from the MDPF spare disk
pool. If your system does not have MDPF installed, the command is rejected and
the following system message appears:
<mix #> PK<unit number> REQUEST REJECTED: THE REQUIRED FEATURE KEY
IS NOT INSTALLED
A system message and a status change message are generated for each member
successfully removed from the spare disk pool. The status change message is
defined in the MCP System Interfaces Programming Reference Manual. The
following system message appears:
When a mirrored set previously assigned to the spare disk pool has been moved
to a system that does not support MDPF, its members are not recognized as spare
disks. The in-use spare attribute can be cleared from the pack labels with no
operator notification.
Note: The MIRROR RELEASE command has no effect on the time limit assigned to
either the released or remaining members of a mirrored set.
in the pending state, the mirror is removed from its set during the subsequent
system initialization.
In general, all members of a mirrored set share the same time limit value. The
default time limit for disk READ and WRITE operations is 80 seconds. If the IOTIMER
command or the SETSTATUS interface is used to change the time limit for a unit that
is a member of a mirrored set, the change also applies to the other members of the
set.
VSS-1 continues to be available for mirroring all pre-existing 180-byte sector disks
with 512-byte sector disks.
A 180-byte disk cannot be mirrored onto a VSS-2 disk, unless the 180-byte disk was
reconfigured with the VSS = VSS2 option of the RC command.
If you enter a MIRROR CREATE command that specifies a VSS-2 disk as the
destination and a VSS-1 or incompatible 180 byte disk as the source, the system
replies with the following message:
A VSS-2 disk cannot be mirrored onto a VSS-1 disk. Likewise, a 180-byte disk with
the VSS=VSS2 attribute cannot be mirrored onto a VSS-1 disk. If you enter a
MIRROR CREATE command that violates one of these restrictions, the system
displays the following message:
To convert the selected disk to a compatible destination for this source, enter the
following system commands:
The following chart shows the various source-target combinations and indicates
whether a MIRROR CREATE is allowed for each.
Notes:
2. The target 180-byte disk no longer uses VSS-2 file allocation after this mirror
create operation is started.
5. The target 180-byte disk uses VSS-2 file allocation after this mirror create
operation is started.
The Mirrored Disk Pooling Facility (MDPF) follows the same rules when selecting a
disk from the spare disk pool for mirror replacement. The following table identifies
the spares eligible to replace a released mirror.
180-byte VSS-2 No
VSS-1 VSS-2 No
VSS-2 VSS-1 No
Notes:
1. Any eligible candidate has the same capacity as the released mirror.
2. The target 180-byte disk no longer uses VSS-2 file allocation after this mirror
replacement is started.
3. The target 180-byte disk uses VSS-2 file allocation after this mirror replacement
is started.
ML (Mix Limit)
The ML (Mix Limit) command sets or displays the current mix limit.
Syntax
Explanation
ML
For every job queue, displays the queue number, the active count (the sum of all
waiting, scheduled, and active jobs and associated tasks), the mix limit (the
maximum number of active, waiting, and scheduled jobs and associated tasks that
can be in this queue at one time), and the number of jobs queued. The letter D at
the left side of the display indicates the default queue, if any.
ML = <number>
Sets the mix limit (used for bringing jobs into the system) to the specified value. The
mix limit is the maximum number of jobs (and associated tasks) that can be
introduced, regardless of the sum of the mix limits set for all queues. If the mix limit
is zero, no jobs can be run. The limits for each queue are not changed.
ML
Removes the mix limit setting.
Example
ML
MM (Memory Module)
The MM (Memory Module) command lists memory module size and the number of
system memory modules.
Syntax
Explanation
The MM command lists ready, to be saved, and unused memory modules. The
unused modules are those that could not be verified at the time of the halt/load.
On all systems, the basic response lists the size of the memory modules and the
number of modules currently in use.
For systems that support the memory disk feature, the response to an MM command
includes memory allocated to memory disk, if any.
On systems with dedicated cache memory, the MM display identifies dedicated cache
memory quadrants. Refer to Example 1 for a typical display.
Number of MSUs
Contained by Each MSM
System Type
NX5600 1 or 2
NX5800 1 to 3
NX6820 1 to 3
NX6830 1 to 3
VM 1
Examples
Example 1
This example shows the MM display on systems that support dedicated cache
memory:
MM
2 MSMS 0-1
MEMORY USAGE:
SYSTEM 88 Mwords
MEMORY DISK 8 Mwords
DISK CACHE 32 Mwords
TOTAL IN USE 128 Mwords
MSM STATUS:
MSUS QUADS ON LINE SAVED TO BE SAVED CACHE
MSM 0 0 0-3 0-3 NONE NONE 0,1
1 0-3 0-3 NONE NONE NONE
MSM 1 0 0-3 0-3 NONE NONE 3
1 0-3 0-3 NONE NONE NONE
Example 2
This example shows the MM display on a CS7101 server:
MM
Syntax
<iopartner specifications>
Explanation
MODE DK <unit number> IO
MODE PK <unit number> IO
MODE MT <unit number> IO
Allow the device to revert to normal operation.
A MODE...IN command prevents the following attributes of the physical file from
being updated when the file is accessed or executed. However, the file header in
memory is updated regardless of the MODE setting of the physical unit; this means
header on disk is not updated.
Examples
Example 1
MODE HC 096 OUT
Example 2
MODE MT 48 AUTOUNLOAD OFF
Direction can be specified only for a closed HC unit; this is the default state of an HC
unit.
The IOPARTNER specifications can be used only for labeled HC units. The minus sign
() syntax removes an I/O partner restriction from a labeled HC unit and causes any
related hubindex to be ignored. A null READPARTNER or WRITEPARTNER
specification is indicated by a value of 1.
ON CLOSE(F) Rewound/unloaded
CLOSE(F,REEL) Rewound/unloaded
CLOSE(F,PURGE) Rewound/unloaded
CLOSE(F,LOCK) Rewound/unloaded
CLOSE(F,LOCK) Rewound/unloaded
The default value of OFF for the AUTOUNLOAD option is preserved across a halt/load.
A program can override the setting of the AUTOUNLOAD MODE by using the
AUTOUNLOAD file attribute. You can interrogate the value of AUTOUNLOAD by using
the system command OL (Display Label and Paths).
For mirrored pack units, the effect of the MODE command is carried through to all
members of the mirrored set.
Syntax
Note: To use the WFL MOVE statement, enter the syntax ?MOVE or
CC MOVE followed by the appropriate syntax elements.
Explanation
MOVE <mix number list> <mix number>
MOVE <mix number list> : <mix number>
Change the order of the jobs in the mix number list so that they appear in the queue
immediately after the job with the specified mix number.
The jobs identified by the mix number list and the mix number must be in the same
queue and must have the same priority; otherwise, no action is taken. After a
halt/load, all jobs are returned to their original sequence.
This facility is convenient if a drive fails while in use. Another available drive can be
chosen and, provided the destination unit is powered off, this form of the MOVE
command can be entered. The system responds with the following message:
The first drive can then be turned off, the pack can be moved to the second drive,
and the second drive can be powered up. If the pack is not to be moved, the MOVE
job can be discontinued with a DS (Discontinue) command and the pack can be put
back on the first drive.
If the disk pack to be moved is a critical unit such as the halt/load unit, catalog unit,
or overlay unit, an RSVP warning message is displayed concerning a possible system
interruption. This condition results during the pack movement process because the
system suspends all I/O activity to the pack being moved.
Use the CLOSE (Close Pack) command to close the destination unit.
Enter the MOVE command with the following syntax:
MOVE PK <source unit number> TO PK <destination unit number>
If there is a pack in the destination drive, turn the drive off and remove the
pack.
When the system requests that you begin the move operation, turn off the
source unit, physically move the pack to the destination unit, and turn on the
destination drive.
The time-out value in effect for the source drive is retained on the source drive and
is assigned to the destination drive, so that when the move operation is completed,
both drives have the same time-out value in effect. For more information about I/O
timer handling, refer to the IOTIMER (Specify Time-out Value) command.
Examples
Example 1
The following command alters the job queue so that job 7419 is executed after job
7421. An SQ (Show Queue) command indicates the new place of the job in the
queue.
SQ7
QUEUE 7:
7418 50 ?JOB B;
QUEUED: 08/21/1995 AT 0:01:21 STARTTIME = 0:01:00 ON 08/22/1995
7421 50 ?BEGIN JOB DIRDUMP(BOOLEAN HARDCOPY);
QUEUED: 08/21/1995 AT 0:01:25 STARTTIME = 20:00:00
7419 50 ?BEGIN JOB DIRDUMP(BOOLEAN HARDCOPY);
QUEUED: 08/21/1995 AT 0:01:22 STARTTIME = 20:00:00
7423 50 ?BEGIN JOB STCEDITOR;
QUEUED: 08/21/1995 AT 0:01:29 STARTTIME = 22:00:00
Example 2
This command places jobs 6627, 6629, and 6631 after job 6630 in the queue. An SQ
(Show Queue) command shows the modified queue.
SQ50
QUEUE 50:
6630 50 ?JOB B;
QUEUED: 08/21/1995 AT 0:01:37 STARTTIME = 0:01:00 ON 08/22/1995
6631 50 ?BEGIN JOB PAYROLL;
QUEUED: 08/21/1995 AT 0:01:39 STARTTIME = 20:00:00
6629 50 ?BEGIN JOB SCHEDULEA;
QUEUED: 08/21/1995 AT 0:01:25 STARTTIME = 20:00:00
6627 50 ?BEGIN JOB DUMPTAPETODISK(BOOLEAN HISTORY);
QUEUED: 08/21/1995 AT 0:01:13 STARTTIME = 22:00:00
Example 3
This command logically moves the disk pack mounted on the drive identified by unit
number 67 to the drive identified by unit number 69:
A MSG (Display Messages) command shows that the MOVE is being initiated:
MSG
The disk pack mounted on the drive identified as PK67 must then be physically
moved to the drive identified as PK69. When the MOVE is completed and no I/O
errors are reported, the C (Completed Mix Entries) command confirms that the
move was successful:
MP (Mark Program)
The MP (Mark Program) system command displays or changes any of a number of
options that apply to object code files.
Notes:
Syntax
<granulated privilege>
Explanation
MP
Displays a list of all the allowable code file options.
MP <file title>
Displays the code file options that are set for the specified object code file.
The resident program status of the code file is also shown if the RP system command
was used to make the code file into a resident program.
The ALLOWCOMS and ALLOWDMS code file options are also shown if they are set.
These attributes can be set only by Unisys. If ALLOWCOMS is shown, the code file
can be run by Transaction Server even if the Transaction Server run-time key nnn-
TSAPPACCESS-TS is absent. If ALLOWDMS is shown, the code file can open an
Enterprise Database Server database even if the Enterprise Database Server run-
time key nnn-EDSAPPACCESS-EDS is absent.
COMPILER
The COMPILER option specifies whether the object code file has compiler status. Only
object code files with compiler status can create other object code files.
If you assign the COMPILER option to an object code file that has TADS capability,
and the system is running with the security option TADSWARN set, a warning
message is displayed.
CONTROL
The CONTROL option specifies whether the object code file is a control program. A
control program is never scheduled or suspended due to a lack of available memory.
Additionally, a control program runs in the same priority category as message
control systems (MCSs). This category provides higher priority than WFL jobs or
most other types of programs. For a detailed discussion of process priority
categories, refer to the System Administration Guide.
If you assign the CONTROL option to an object code file that has TADS capability,
and the system is running with the security option TADSWARN set, a warning
message is displayed.
EXECUTABLE
The EXECUTABLE option specifies whether an unsafe object code file is executable.
IDENTITY
The IDENTITY option, if set, associates a message prefix identifier with an object
code file. The system adds the specified prefix identifier to all messages produced by
that object code file. If you do not set the IDENTITY option, the system adds no
prefix identifier to messages displayed by the process.
The identifier that is used as a prefix comes from the code file that causes the
system to display a message. For example, if a program with an identity of PROG
calls a library with an identity of LIB, any messages that either the system or
program produces while it is executing the library procedures are preceded by LIB.
Messages that either the system or program produces while it is executing
procedures contained in the PROG code are preceded by PROG.
KERBEROS
The KERBEROS option, if set, marks the specified program as having the privilege to
create, access, and update disk files with the Boolean file attribute
KERBEROSACCESS = TRUE.
The system software generation process sets this option for the Kerberos library.
This option gives the Kerberos library the privilege to open, read from, and write to
the Kerberos KeyTable file. This file contains security-sensitive data that should be
accessed only by the Kerberos library.
LOCKED
The LOCKED option specifies whether the program is protected from being
discontinued by a DS (Discontinue) or QT (Quit) system command. If the LOCKED
option is set and an operator tries to discontinue a program, the system displays a
PROGRAM IS LOCKED error message. To discontinue a program that is locked, the
operator must first use the <mix number> LP form of the LP (Lock Program)
command, and then enter a DS or QT command.
The LOCKED option of an object code file is inherited by any internal tasks initiated
by that object code file. Internal tasks are those resulting from statements that call
or process an internal procedure in the object code file.
ONEONLY
The ONEONLY option, if set, prevents more than one process stack from using the
object code file.
PU
The PU option specifies whether the object code file is a privileged program. The
system allows privileged programs to perform some system functions that would
otherwise be denied, such as creating or removing files under another usercode,
reading and copying the files of another usercode, and invoking certain operating
system control privileges. For further information about the rights of privileged
programs, refer to the Task Management Programming Guide.
If you assign the PU option to an object code file that has TADS capability, and the
system is running with the security option TADSWARN set, a warning message is
displayed.
Note that the PU option and the PU TRANSPARENT option are mutually exclusive.
Refer to the description of the PU TRANSPARENT option later in this subsection.
SECADMIN
The SECADMIN option specifies whether an object code file has security
administrator status. Note that the SECADMIN option has an effect only if the system
is running Secure Access Control Module security enhancement software. For further
information about security administrator status, refer to the Task Management
Programming Guide.
If you assign the SECADMIN option to an object code file that has TADS capability,
and the system is running with the security option TADSWARN set, a warning
message is displayed.
Note that the SECADMIN option and the SECADMIN TRANSPARENT option are
mutually exclusive. Refer to the description of the SECADMIN TRANSPARENT option
later in this subsection.
SERVICE
The SERVICE option enables the security administrator to manage a list of security-
related attributes for a code file. This option specifies that a program is allowed to
use a specific service name as its secure identification.
A code file can be marked to use multiple service names, but each marking must be
done with a separate MP command.
When removing a service name from a program, you can use an asterisk (*) to
remove all service names associated with that program.
In order to enable backward compatibility, any programs that have been marked as
a TASKING program (including MCSs) are treated as if they were marked with the
HOST service name. That service name is generally used to denote the service that
allows general access to a system.
SUPPRESSED
The SUPPRESSED option specifies whether processes that are instances of a given
object code file are to appear in the output from mix display commands such as the
A (Active Mix Entries) system command. If the SUPPRESSED option is set for an
object code file, then the operator must add the ALL option to mix display commands
to display instances of that object code file in the mix. If the SUPPRESSED option is
not set, then such processes are visible in mix display output even if the ALL option
is not used.
TASKING
The TASKING option specifies whether a given object code file has tasking status.
Tasking status is a security category that allows the program to perform some
system functions that otherwise can be done only by an MCS program. For example,
a tasking program can assign a usercode without knowing the password, and can
commit some normally fatal task attribute errors without being discontinued. For a
complete list of the capabilities of a tasking program, refer to the Task Management
Programming Guide.
If you assign the TASKING option to an object code file that has TADS capability, and
the system is running with the security option TADSWARN set, a warning message is
displayed.
Note that the TASKING option and the TASKING TRANSPARENT option are mutually
exclusive. Refer to the following explanation of the TASKING TRANSPARENT option.
WORKLOADGROUP
Assigns or deletes the WORKLOADGROUP code file attribute.
The WORKLOADGOUP code file attribute is used to determine the default value for a
task that is initiated with that code file. If the code file attribute has an asterisk (*)
prefix, the value overwrites a user-supplied task attribute, and the task attribute
cannot be changed.
and then
<granulated privilege>
The <granulated privilege> option specifies whether an object code file has any of
the granulated privileges. The PU or PU TRANSPARENT status is removed when the
code file is granted a granulated privilege or a granulated privilege transparency. In
addition, assigning an object code file with either the USERDATA or USERDATA
TRANSPARENT option resets the SECADMIN TRANSPARENT or SECADMIN option
respectively.
Granulated Meaning
Privilege
CHANGE A process with this privilege can change the titles of other
users' disk files, including the file ownership. However file
overwrite is not allowed, unless accompanied by the REMOVE
privilege, when a new file name is identical to another user's
existing disk file.
CHANGESEC A process with this privilege can modify the security file
attributes of disk files belonging to other users.
CREATEFILE A process with this privilege can create disk files under another
usercode without replacing existing files. However, the privilege
does not apply to files created through the WFL CHANGE or
library maintenance copy operation.
EXECUTE A process with this privilege can execute disk files of other
users, regardless of their security attributes.
Granulated Meaning
Privilege
GETSTATUS A process with this privilege can use the GETSTATUS intrinsic to
retrieve information about jobs, tasks, the status of peripherals,
the status of the operating system and mainframe
configuration. However, it does not include those GETSTATUS
directory and volume requests where privileged-user status is
required.
LOCALCOPY A process with this privilege can copy files and directories
belonging to other users on the local host through library
maintenance.
READ A process with this privilege can have read access to other
users files, regardless of their security attributes.
REMOVE A process with this privilege can remove files belonging to other
users. An existing disk file can either be replaced or removed
when used in conjunction with either the CREATEFILE,
LOCALCOPY, or CHANGE privilege. A close with a purge on a
non-owned file also requires the process to have this privilege.
SETSTATUS A process with this privilege can use the SETSTATUS intrinsic to
control MCP, mix, unit, and operational functions. However, it
does not include those SETSTATUS directory and volume
requests where privileged-user status is required.
Granulated Meaning
Privilege
USERDATA A process with this privilege can access the USERDATA intrinsic.
USERDATA functionality, as allowed to the process, includes all
privileges that are available to a privileged user on a system
with security administrator disabled, and all privileges that are
available to a security administrator on a system with security
administrator status enabled.
WRITE A process with this privilege can have write access to other
users disk files, regardless of their security attributes. It can
also change all modifiable non-security-related file attributes.
PU TRANSPARENT
SECADMIN TRANSPARENT
TASKING TRANSPARENT
<granulated privilege> TRANSPARENT
The TRANSPARENT option is intended primarily for use by libraries. The effect is to
make exported library procedures inherit privileges of the programs that call those
procedures. Each type of transparent privilege is treated separately by the system.
For example, a library object code file might have privileged transparent status, but
no security administrator or TASKING status. If a user program with privileged status
and security administrator status calls a procedure in that library, the procedure is
executed with privileged status, but without security administrator status.
You cannot use privileged transparent status to determine file access rights for a file.
These access rights are based only on the object code file in which the file was
declared.
For further information about transparent privileges, refer to the Task Management
Programming Guide.
Examples
Example 1
The following MP command displays the options that are set for the object code file
SYSTEM/GENERALSUPPORT ON DISK:
MP SYSTEM/GENERALSUPPORT ON DISK
SUPPRESSED
LOCKED
NON-EXECUTABLE: UNSAFE
IDENTITY: GENSUPP
Example 2
The following example adds control program status and compiler status to the object
code file OBJECT/DELTA. This command also suppresses the object code file from
most mix displays, and adds the prefix PROG to messages generated by the
program.
Example 3
The following example adds privileged transparent status and security administrator
transparent status to the object code file OBJECT/DELTA. This command also
removes control program status from the program.
Example 4
The following example associates the program named MY/CODE/FILE with the
service called MyService. When this program is initiated, it enters the mix with the
MyService identifier.
Example 5
The following example removes the association between the program named
SYSTEM/PAYROLL and the service named Payroll.
NONE SET
IDENTITY: PAYROLL
Example 6
The following example assigns the code file (MYUC)OBJECT/MYCODE with several
granulated privileges.
COMPILER
EXECUTABLE
IDENTITY
<granulated privilege>
<granulated privilege> TRANSPARENT
PU
PU TRANSPARENT
SECADMIN
SECADMIN TRANSPARENT
SERVICE
TASKING
The MP command affects only instances of an object code file that are initiated after
that MP command was issued. Refer to the discussion of privileges assigned to object
code files in the Task Management Programming Guide.
Every job queue has several attributes. When selecting jobs to enter the mix, the
CONTROLLER program considers them in order of priority. Queue attributes provide
constraints that affect the way jobs are assigned to queues and selected for
execution.
If an MQ command does not specify a value for every queue attribute, only the
values of the specified attributes are changed or initialized. If a new job queue is
being created, unspecified attributes are assigned default values as described in the
following text.
All job queues in existence before a halt/load continue to exist and maintain
attributes through the halt/load. Jobs that do not have a class specified and are not
affected by a unit queue assignment are placed in the default queue. If, however,
the CONTROLLER compile-time option QFACTMATCHING is set, those jobs are placed
in the highest numbered queue that accepts their attributes.
For more information about job queue processing, refer to the PQ (Purge Queue), QF
(Queue Factors), SQ (Show Queue), and UQ (Unit Queue).
Syntax
<queue factors>
<queue attributes>
<limits>
<family specification>
<tape specification>
Explanation
MQ <queue number>
Makes a queue with the specified queue number. The highest queue number allowed
is 1023. No more than 1024 queues can exist at one time.
MQ <queue number>
Eliminates the queue from the system. If the queue contains any active entries, the
message QUEUE HAS ACTIVE JOBS appears and the queue is not deleted. (If the
queue was deleted, and a halt/load occurred before an active job terminated, the job
would be impossible to restart after the halt/load because the queue from which it
started would no longer exist.) If the queue contains any waiting jobs, they are
moved to another queue, if possible, or discontinued if no suitable queue exists.
MIXLIMIT = <number>
Assign <number> as the value of the MIXLIMIT attribute. This value is used by the
CONTROLLER when selecting jobs from the queues. If the number of scheduled and
running jobs (and associated tasks) in the mix that originate from this queue is
greater than or equal to the MIXLIMIT value of the queue, the CONTROLLER does not
take any more jobs into the mix from the queue.
After a halt/load, the MIXLIMIT for all queues is set to 0 (zero) if the run-time
operating system option AUTORECOVERY is reset.
TASKLIMIT = <number>
Assigns <number> as the value of the TASKLIMIT attribute, where <number> is in
the range 0 through 31. This attribute limits the number of descendants that a job
can have. The limit applied is cumulative. That is, it limits the total number of
descendants that a job can have during its history, not just the number of
descendants a job can have at the same time.
A user who has a family statement specified in the USERDATAFILE must also exactly
match the family statement of the queue to run anything through that queue.
FAMILY.
Removes family specifications from the specified queue.
DEFAULTS
Specifies the default system usage limits that are assigned to jobs selected from that
queue. These defaults can be overridden by limit statements placed in the job.
LIMITS
Specifies the maximum system usage limits that the control statements of a job can
specify and still be accepted as an entry in that job queue. Thus, if a job specifies
larger estimates than the LIMITS values for the desired queue, it is not admitted to
the queue and a message is displayed. You should usually specify DEFAULTS
whenever you specify LIMITS; otherwise, jobs that do not contain an explicit usage
limit statement are not subject to the limits specified in the MQ command. If you set
a lower LIMITS value than the DEFAULTS value for the same queue attribute, the
system automatically reduces the DEFAULTS value to the specified LIMITS value.
The options described in the following paragraphs specify system usage limits and
can be specified for both the DEFAULTS and the LIMITS queue attributes. The
exception is the tape specification, which applies to LIMITS only. For each option, the
equal sign (=) can be omitted.
PRIORITY = <number>
Assigns <number> as the value of the PRIORITY attribute, where <number> falls in
the range 0 through 99. The value of this attribute is the priority to be assigned to a
job when it is entered in the mix. Changes to this value can result in all jobs in the
queue being requeued (possibly into other queues) at the time the command is
issued.
IOTIME = <number>
Assigns <number> as the value of the MAXIOTIME attribute, where <number> is in
units of seconds. The value of this attribute is the maximum input/output (I/O) time
to be allowed when the job is executed. If this option is not specified, an unlimited
amount of job I/O time is allowed by default.
PROCESSTIME = <number>
Assigns <number> as the value of the MAXPROCESSTIME attribute, where
<number> is in units of seconds. The value of this attribute is the maximum
processor time to be allowed when the job is executed. If this option is not specified,
an unlimited amount of job processor time is allowed by default.
LINES = <number>
Assigns <number> as the value of the MAXLINES attribute. The value of this
attribute is the maximum number of lines of printed output that can be generated by
the execution of the job. If this option is not specified, an unlimited number of lines
are allowed by default.
WAITLIMIT = <number>
Specifies <number> as the value for the WAITLIMIT attribute, where <number> is in
units of seconds. This attribute specifies the maximum amount of time that a task
waits for an event.
ELAPSEDLIMIT = <number>
Specifies <number> as the value for the ELAPSEDLIMIT attribute, where <number>
is in units of seconds. The value of this attribute is the maximum time that a job can
be active in the system.
SAVEMEMORYLIMIT = <number>
Specifies <number> as the value of the SAVEMEMORYLIMIT attribute, where
<number> is in units of words. The value of this attribute is the maximum amount of
memory a task can allocate to save.
<tape specification>
Specifies the following values:
The maximum number of tape units a job can specify in a RESOURCE task
attribute specification
The maximum number of tape units that a task within the job can specify in a
RESOURCE task attribute
The system enforces this limit only when the RESOURCECHECK option is set. TAPE0
nullifies the resource limits for all tape types and reestablishes unrestricted use of all
tape resources.
Note: This attribute can be used only when LIMITS is specified; it cannot be used
with DEFAULTS.
Example
Example 1
This example makes a queue with a queue number of 37, a MIXLIMIT of 2, and no
DEFAULTS or LIMITS system usage specifications:
MQ 37 ML = 2
QUEUE 37:
MIXLIMIT = 2
DEFAULTS:
NONE
LIMITS:
NONE
Example 2
This example creates a queue, numbered 4, with the specified attributes:
QUEUE 4:
MIXLIMIT = 3
TURNAROUND = 2.50
DEFAULTS:
PRIORITY = 60
PROCESSTIME = 3
IOTIME = 20
LINES = 50
LIMITS:
PRIORITY = 80
PROCESSTIME = 20
IOTIME = 60
LINES = 200
RESOURCE:
TAPE = 14
Example 3
This example causes all jobs in queue 5 without a FAMILY specification to be
assigned a family specification of DISK=STUDENTFILES OTHERWISE DISK, and jobs
with a FAMILY specification other than DISK=STUDENTFILES OTHERWISE DISK to be
denied entry into queue 5.
By default (when the message suppression feature is inactive), the system displays
system messages as follows:
Messages resulting from jobs initiated at the ODT appear on the ODT screen.
Messages resulting from jobs initiated at a remote terminal appear on the
screen of that terminal and on the ODT screen.
With the MSC command, you can dynamically suppress or display system messages
by identifying:
At the ODT
At remote terminals
At both the ODT and remote terminals
Specifically, the MSC command enables you to perform the following message
control operations:
Syntax
<type>
<source>
<destination>
<file title>
<file name>
Wild-Card Characters
Many MSC command variables (items enclosed in angle brackets (< >) in the
command syntax) can include wild-card characters. Wild-card characters are
symbolic characters taken to indicate that any character or sequence of characters
can appear in the corresponding position or positions in the command.
Character Meaning
Tilde (~) Match any sequence of characters excluding the slash (/) file
node separator.
The wild-card mechanism enables to you perform pattern matching (to instruct the
system to search for messages that contain one or more common elements of a
given message characteristic). For example, the following command suppresses all
display of all messages from any job that has a charge code value in which the
fourth digit is 9:
Similarly, since all warning message IDs consist of the characters MSRWARNG
followed by a number, the following command suppresses from display at the ODT all
warning messages resulting from jobs initiated from a remote terminal:
Explanation
The MSC command enables you to control the display or suppression of system
messages.
For details on type and destination specifications, see Suppressing and Showing
Messages under "Considerations for Use." For details on files of MSC commands, see
Creating and Using MSC Command Files under "Considerations for Use."
Note: The MSC command permits the suppression of messages that warn of
potentially disastrous situations such as errors in copying during a backup operation,
or disk errors during a file copy operation. Be aware of this possibility when you and
your operators decide which messages are to be suppressed and where message
suppression or display is to take place.
MSC
Displays a list of the currently active MSC commands, in the order in which they
were entered. The order of entry is significant, as a later command might partially or
completely override an earlier command.
MSC CLEAR
Removes every current MSC command. This command causes the system to revert
to its default system message display procedures, outlined earlier in this discussion.
MSC SUSPEND
Temporarily suspends any message suppression currently in effect. The system
follows its default system message display procedures until either an MSC RESUME
command is issued or a halt/load occurs.
MSC RESUME
Resumes message suppression after it was temporarily suspended by an MSC
SUSPEND command.
Examples
Example 1
The following example suppresses the display at the remote terminal of messages
from all programs initiated from a remote terminal and executed under the usercode
OPS:
Example 2
The following example suppresses the display at the ODT of messages from all
programs, such as OBJECT/EDITOR, having a task name that begins with the
characters OBJECT/ED:
Example 3
The following command suppresses from display at both the ODT and the remote
terminal all occurrences of message MSRDIR4 resulting from jobs executed under
usercode STAT:
Example 4
The following command suppresses from display at the ODT all occurrences of
message MSRDIR3 stemming from jobs initiated at remote terminals:
Messages with the message ID value of MSRDIR3 are of the following form:
These messages are usually of more interest to the user of the program than to the
operator of the system. The messages still appear on the terminal from which the
job originated.
Example 5
The following command suppresses the display at the ODT of messages from all jobs
that are initiated from a remote terminal and that specify chargecode XXXX:
These messages still appear at the terminal or terminals from which the job or jobs
were initiated.
Example 6
The following command suppresses the display at the ODT of messages with the
identity MYPROG:
The system prefixes messages with an identity if the MP (Mark Program) system
command was used on the code file of the program displaying the message. For
example, if you use the system command MP PROG + IDENTITY = MYPROG to
give the program PROG an identity of MYPROG, messages displayed by PROG are
prefixed with the identity MYPROG.
Example 7
The following command suppresses the display at the ODT of all warning messages
displayed from programs with an identity of TEST:
The system always executes MSC commands in the order they are entered. A more
recently entered MSC command thus takes precedence over an earlier command. In
determining whether to display or suppress a given message, the system follows the
most recently entered MSC command that applies to that message.
This procedure enables you to suppress a set of messages with one MSC command
and then enter another MSC command to reactivate the display of a subset of those
messages. This ability is useful when you want to suppress most, but not all, of a
given set of messages. See Combining Commands for Unique Message Control for
more information.
Messages that are suppressed are still available in the system. They still appear in
printed job summaries, and you can list them at the ODT by entering the system
command:
MSG ALL
When no message suppression commands are currently active (that is, if no message
control commands reside in memory, or after an MSC CLEAR or MSC SUSPEND
command has been entered, the operating system displays all job messages at their
default destinations as outlined earlier in this discussion.
When an MSC command is entered, that command is added to the end of the list of
current message suppression commands in system memory. These commands
remain active until one of the following events occurs:
MSC
If MSC commands are active on your system, a list of all MSC suppression and
display commands appears on your screen in the order they are processed. If no
MSC commands are currently in use, a message to that effect is displayed.
The following topics discuss your options in MSC SUPPRESS and MSC SHOW
commands:
REMOTE Qualifier
Message Type Specifications
Message Destination Specifications
REMOTE Qualifier
You can precede the type specification with the optional REMOTE qualifier to limit the
effect of the command to only those messages produced by a job or jobs that were
initiated at a remote terminal. An MSC SUPPRESS or MSC SHOW command without
this qualifier affects messages regardless of job origination.
For example, the following command suppresses the display at the ODT of all
messages from programs that are executed under the usercode OPS, regardless of
where those jobs originate:
Messages from jobs executed under the usercode OPS still appear on the remote
terminals from which the jobs were initiated.
In contrast, the following command suppresses the display at the ODT of messages
from programs running under the usercode OPS, but it suppresses only a subset of
those messages--specifically, those that result from jobs initiated from a remote
terminal:
The messages still appear on the terminal from which the job was initiated.
Note: An MSC command that specifies a task name takes effect only when that
name matches the task name in a current mix entry.
If you want to reference a message that is not listed in the preceding table, run the
utility program SYSTEM/LOGANALYZER. This utility enables you to display the
message ID and text of some or all of the system messages recorded in the system
log file. To select system messages, use the MSG option. Additionally, you can
specify one of the following options to specify the destination where messages are
displayed.
See the System Software Utilities Manual for detailed information on the
LOGANALYZER utility.
For additional information on system messages, see the System Messages Support
Reference Manual. This manual discusses selected system messages generated by
the master control program (MCP). For each message presented, the manual
describes the cause and suggests possible responses.
When you enter an MSC SUPPRESS MSG or MSC SHOW MSG command, you can
include the optional FROM qualifier to limit the selection of messages with the
specified message ID to only those occurrences of that message coming from a
specified source. For example, you can suppress or show only occurrences of a
specified message that come from a particular job by specifying the appropriate job
number in a FROM TASK qualifier following the message ID.
The following table lists the values you can specify in the FROM qualifier.
Note: An MSC command that specifies a task name takes effect only when that
name matches the task name in a current mix entry.
For example, the following command suppresses from display on the ODT all
occurrences of message MSRDPC97 resulting from all jobs, regardless of origin, with
a charge code value of 8179:
Destination Meaning
For example, the following command suppresses from display at the ODT messages
from all jobs executed under the usercode HDS, regardless of where they originated:
Messages from jobs running under usercode HDS still appear on the terminal or
terminals from which the job or jobs originated.
In contrast, the following command suppresses messages from all jobs executed
under the usercode HDS, but the suppression occurs at the terminal or terminals
from which the job or jobs originated:
You can include the REMOTE qualifier in this command if you choose, but it is
unnecessary to do so. The only messages that ever appear on remote terminals are
from jobs initiated from remote terminals. In either case, messages from jobs run
under usercode HDS still appear on the ODT.
As a small example, the following commands suppress from display at the ODT all
messages from all jobs run under the usercode OPS, regardless of where the jobs
originated, but displays all messages at the ODT from job number 7683 even if that
job is executed under usercode OPS:
As another example, the following command suppresses the display at the ODT of all
messages from jobs that originate from a remote terminal and have a message ID of
MSRDIR54, but allows all such messages to appear on the remote terminal from
which the job originated:
If the following command is entered subsequently, all messages from jobs initiated
from a remote terminal and running under usercode OPS, including messages with a
message ID of MSRDIR54, appear at both the ODT and the remote terminal, their
normal message destinations:
Messages with a message ID value of MSRDIR54 from all jobs initiated from remote
terminals under other usercodes continue to be suppressed at the ODT.
The following example illustrates the importance of the order in which you enter MSC
commands. As shown, these commands combine to suppress messages from display
at the ODT messages from all jobs initiated at remote terminals under the usercode
XYZ, except messages from jobs that have the task name MY/PROGRAM:
If these commands were reversed, the MSC SHOW command would have effect only
if it applied to an earlier message suppression operation, and all messages from all
programs initiated at a remote terminal under the usercode XYZ would be
suppressed at the ODT.
See the examples for additional illustrations of how MSC SUPPRESS and MSC SHOW
commands can be used in combinations to achieve very specific message control.
Create one or more MSC command files (one or more files containing one or
more MSC commands that direct the operating system to suppress or display
selected system messages)
Create a default MSC command file that is to be loaded after a halt/load
occurs.
Dynamically load a new file of MSC commands.
Dynamically save the current list of MSC commands on a file.
If you choose to create the file with an editor or a program, follow these guidelines:
To define a file as the default message suppression command file (the file that the
system loads automatically after a halt/load) name the file *MESSAGES/STARTUP
and place it on the disk file family where the code file pointed to by the
MESSAGESUPPORT function resides. You can determine that family by entering the
command:
SL MESSAGESUPPORT
If this command returns just the file name, that file resides on family DISK. For
further information about the SL command, refer to the SL (Support Library)
command.
For example, you could use the CANDE command MAKE to create a file containing
the following MSC commands you want to be automatically loaded after a halt/load:
Note the absence of MSC at the beginning of these commands. The first four
commands suppress the display at the ODT of four selected messages from jobs
initiated at remote terminals. The three SHOW commands override the SUPPRESS
commands in the cases of three particular usercodes the usercodes of the system
operators.
This sequence suppresses the repetitious display at the ODT of routine messages
from jobs initiated from remote terminals, but displays on the ODT any occurrences
of those messages if they result from a job submitted by an operator.
Suppose that you assign this file the name DEFAULT/MESSAGES and that the code
file pointed to by the MESSAGESUPPORT function resides on the disk file family
named SYSTEM.
You can create more than one file of MSC message suppression commands to suit
different situations. You might want to suppress one set of messages during daily
operations or at system initialization, but want a different set of messages
suppressed during nightly or weekend processing.
The MSG command returns network messages depending on the setting of the
CONTROLLER option SEPARATEMSGS. If the option is SET, network messages will be
returned only if the NW modifier is used. If the option is RESET, the NW modifier will
return no messages. The following descriptions assume that SEPARATEMSGS is SET.
Messages preceded by asterisks (*) have not appeared on this ODT before. If the
MSG command is entered again, the asterisks preceding those messages disappear.
Unsuppressed messages are those that have not been specified in an MSC (Message
Control) command. Non-network messages are those that do not originate from
networking software or from a remote host.
Syntax
Explanation
MSG
Displays unsuppressed, non-network messages. The number of messages displayed
is a function of the TERM LINES and TERM FIRST values for the ODT. Refer to the
TERM (Terminal) command for more information.
MSG ALL
Displays non-network messages, regardless of whether they have been suppressed
by the MSC (Message Control) command. The number of messages displayed is a
function of the TERM LINES and TERM FIRST values for the ODT.
MSG FULL
Displays non-network messages regardless of whether they have been suppressed
by the MSC (Message Control) command. The number of messages displayed is
determined by the value of MAX MESSAGES. Refer to MAX (Maximums) earlier in
this section.
MSG NW
MSG NW ALL
MSG NW FULL
MSG NW USER <usercode>
MSG NW ALL USER <usercode>
MSG NW FULL USER <usercode>
Have the same effects as the equivalent commands without the NW (Network
Commands) option, except that the display includes network messages instead of
non-network messages.
Examples
Example 1
The following example shows the display for all unsuppressed messages. The
heading line appears on the first page of the Messages display and before the
Messages entries in automatic display mode (ADM). The Mix field contains the
number of the job or task from which the message was sent. Messages from an
unknown origin have two asterisks (**) in the Mix field. The Time field shows the
time of day that the message originated. The time is shown in 24-hour format.
MSG
Example 2
This example shows all messages displayed by programs running with the usercode
PDW:
Example 3
The following example shows all unsuppressed network messages:
MSG NW
MU (Make User)
The MU (Make User) command creates a new usercode and an associated password.
Syntax
Explanation
MU <usercode>
Causes the specified usercode to be entered in the USERDATAFILE as a valid
usercode.
MU <usercode> / <identifier>
Causes the specified usercode to be entered in the USERDATAFILE as a valid
usercode, and designates the identifier following the slash (/) as the password for
the usercode.
MU <usercode> PRIVILEGED
Specifies that the usercode is to be privileged.
MU <usercode> PRIVILEGED
Removes privileged status from the designated usercode.
Examples
Example 1
MU JOHN PRIVILEGED
JOHN PRIVILEGED
Example 2
MU - JOHN PRIVILEGED
Example 3
MU JOE/JOE
MX (Mix Entries)
The MX (Mix Entries) command gives the same response as the J (Job and Task
Display) command, except that display lines (RSVP and DISPLAY messages) are
displayed with each job and task.
Syntax
<wild card>
<delim>
Use one of the following characters
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters.
Character Description
You can include lowercase characters and space characters by prefixing the wild-card
string with LIT and enclosing the wild-card string in delimiters.
For example, if you enter the following syntax, the system returns entries that
contain the string "PACK":
MX NAME =pack=
If you enter the following syntax, the system returns entries that contain the string
"pack":
MX NAME LIT^=pack=^
Explanation
MX
Displays RSVP and DISPLAY messages for each unsuppressed job or task in the mix.
MX ALL
Displays all active jobs or tasks, including any that are suppressed.
MX QUEUE
MX Q
Display jobs that were initiated from a job queue and tasks that are descendants of
jobs initiated from a job.
MX USER <usercode>
Displays only jobs or tasks running with the specified usercode.
Examples
Example 1
This example shows RSVP and DISPLAY messages for all unsuppressed jobs or tasks
in the mix:
MX
The heading line appears on the first page of the Job Entries display and before the
mix entries in automatic display mode (ADM).
At the beginning of each entry line, an E indicates that a syntax error was discovered
during compilation. An asterisk (*) indicates that the task is being displayed for the
first time.
The Mix field shows the job or task number. The Pri field shows the priority of the job
or task.
The entry names are indented to reflect the job structure. Five levels of indentation
are supported.
The next column contains the word Job if the task has no parent, Lib if the task is a
library process, or DBS if the task is a database stack. Otherwise the column is
blank.
The usercode of the originator appears before the job or task name. Some tasks and
jobs can have two usercodes shown for the following reasons:
Tasks other than compiler tasks display with the following format:
Example 2
This example displays jobs that were initiated from a job queue (including those that
are suppressed) and tasks that are descendants of jobs initiated from a job queue
(including those that are suppressed).
MX ALL QUEUE
Example 3
This example displays jobs that were initiated without a specified usercode.
MX USER=""
NAMEMAP
Use the NAMEMAP command to display the port names associated with control
devices or to display all the port names visible to a channel adapter (port). You can
also use the NAMEMAP command to add, update, or remove the port name
associated with a control. You can list multiple controls can be listed in one
command. You can also output displayed information to a file. You can designate a
file containing a NAMEMAP command as input to the NAMEMAP command.
Syntax
<port name>
Explanation
NAMEMAP
Displays a list of all controls with their associated port names. Only controls with an
associated port name are shown.
The new port names are not associated with any controls in the NAMEMAP. If all
other port names in the Fibre Channel fabric are in the NAMEMAP, the only port
names listed are the names of the new devices.
Examples
Example1
This example displays the controls that have an associated port name.
NAMEMAP
Example 2
This example creates a disk file named XYZ of FILEKIND SEQDATA. Note that this file
is in the same form as the display for Example 1 except that a comment that
provides the date and time when the file was create is listed after the percent sign
(%) in the first record of the file.
NAMEMAP TO XYZ
Example 3
This example associates port name 21:00:20:78:90:AB:CD:EF with control 2001 and
removes the port name associated with control 1000:
Example 4
This example edits a file called XYZ to change or insert entries in the file.
Example 5
This example provides a display of all Fibre Channel port names known to port
31107.
NAMEMAP:
Example 6
This example creates the file XYZ, shown in the output. Note that this file is in the
same form as the file created in Example 2 (NAMEMAP TO) except that there is a
comment following each port name indicating the dynamic Fibre Channel fabric
address assigned at the time the file was created. This information can useful in
determining the actual location of the device, because it includes the domain, area,
and port values that identify the switch to which the device is physically connected.
Example 7
This example causes the output of port 31107 to be altered so than only port names
not associated with a control are displayed.
NAMEMAP:
CTL 0 = 21:00:00:20:37:32:82:A2;
CTL 0 = 21:00:00:20:37:32:82:DB;
CTL 0 = 21:00:00:20:37:32:7B:6E;
Example 8
This example creates an output file named XYZ that lists the output of port 31107 for
port names where the control is 0.
NET (Network)
The NET command is identical to the NW NET operations interface command, except
that the NW prefix is omitted from the syntax. For information about the NW NET
command, refer to the Networking Commands and Inquiries Help.
Syntax
Explanation
NETEX
Displays
The status of NETEX software. The status is one of the following: not running,
initializing, running, or terminating.
The title of the current NETEX initialization file if NETEX software is initializing,
running, or terminating.
The title of the NETEX initialization file to be used at the next initiation of
NETEX software.
NETEX = *NULL
Specifies that no NETEX initialization file is to be used at the next initiation of NETEX
software. If this option is used, the default PAMFILE title must be usedthat is,
SYSTEM/NETEX/PAMFILE.
NETEX = *DEFAULT
Specifies that the default NETEX initialization file (SYSTEM/NETEX/INITFILE) is to be
used at subsequent initiations of NETEX software.
NETEX +
Starts NETEX software, using the initialization file previously specified with the
NETEX = command or the default NETEX initialization file if a NETEX = command
has not been entered.
NETEX + *NULL
Starts NETEX software and specifies that no initialization file is to be used.
Subsequent initiations of NETEX software also do not use an initialization file unless
this option is overridden by another NETEX = command. If the null option is
specified, the default PAMFILE must be used. Its title is SYSTEM/NETEX/PAMFILE.
NETEX + *DEFAULT
Starts NETEX software and specifies that the default NETEX initialization file
SYSTEM/NETEX/INITFILE is to be used. Any subsequent initiation of NETEX software
also uses the default initialization file unless this option is overridden by another
NETEX = command.
NETEX
Stops NETEX software immediately. All user sessions terminate, and NETEX software
itself stops.
Explanation
Example 1
This example shows the response to a NETEX command when NETEX software is not
running:
NETEX
Example 2
This example shows how to set the NETEX initialization file for a subsequent initiation
of NETEX software.
The command copies records from the current SYSTEMDIRECTORY for the specified
family and replaces the current SYSTEMDIRECTORY with the copy. You can use the
NEW SYSTEMDIRECTORY command to expand or reduce the number of allocated
areas in the SYSTEMDIRECTORY for a family.
Before you use this command, make a complete backup of the files on the family.
This backup gives you a method of recovery if software or hardware errors cause the
NEW SYSTEMDIRECTORY command to generate defective records.
Syntax
Explanation
NEW SYSTEMDIRECTORY ON <family name> AREASECTORS 2000
You can use this form of the command to convert a SYSTEMDIRECTORY with an
AREASECTORS value of 600 sectors to 2000 sectors. You can store more files on a
family if the AREASECTORS value of the directory is 2000 instead of 600.
Copies records from the current SYSTEMDIRECTORY for the specified family and
replaces the current SYSTEMDIRECTORY with the copy. The area sectors for the new
SYSTEMDIRECTORY is 2000. The new SYSTEMDIRECTORY has the minimum number
of AREAS necessary to hold the disk file headers copied from the old
SYSTEMDIRECTORY.
Copies records from the current SYSTEMDIRECTORY for the specified family and
replaces the current SYSTEMDIRECTORY with the copy. The new SYSTEMDIRECTORY
has at least the number of areas requested. If the disk file headers copied from the
old SYSTEMDIRECTORY do not fit in the new directory, then the system increases the
number of areas so that they fit. The area sectors for the new SYSTEMDIRECTORY
stay the same as for the old SYSTEMDIRECTORY.
Copies records from the current SYSTEMDIRECTORY for the specified family and
replaces the current SYSTEMDIRECTORY with the copy. The new SYSTEMDIRECTORY
will have at least the number of areas requested. If the disk file headers copied from
the old SYSTEMDIRECTORY do not fit in the new directory, then the system increases
the number of areas so that they fit.
Example
The following example shows how to create a new SYSTEMDIRECTORY for the disk
family named PACK with AREASECTORS set to 2000 sectors.
You cannot use the NEW SYSTEMDIRECTORY command on a family with a duplicate
or triplicate SYSTEMDIRECTORY, or on a disk family that is marked as SHARED. By
using the "DD - ON <family name>" and "DD ON <family name>", and the "SHARE -
<family name>" and "SHARE <family name> LEVEL <number>" commands
respectively, you can cancel these features before using the NEW
SYSTEMDIRECTORY command and restore them after the new SYSTEMDIRECTORY
process is finished.
Avoid using the NEW SYSTEMDIRECTORY command when the system is running
critical application programs. The process that copies and creates the NEW
SYSTEMDIRECTORY runs at a very high priority. The new SYSTEMDIRECTORY
process uses about twice as much time as a DD process. After creating the new
SYSTEMDIRECTORY, the process performs a family (and catalog) rebuild for the
family. The new SYSTEMDIRECTORY process procures the directory lock for the
family while it is running. This action blocks all access to the SYSTEMDIRECTORY of
the family. Any program or command (such as PD or SL) that attempts to use the
SYSTEMDIRECTORY must wait for the new SYSTEMDIRECTORY process to finish.
Avoid using the NEW SYSTEMDIRECTORY command on disk families that are
STANDBY halt/load units during times when the system is running critical application
programs. The new SYSTEMDIRECTORY process procures the directory lock for the
family while it is running. In the case of a family that is a STANDBY halt/load family,
this blocks the system from updating any of the special tables on that family. If there
are other STANDBY halt/load families online, the blockage on the family for which
the new SYSTEMDIRECTORY process is running might block the system from
updating the tables on some of those other STANDBY halt/load families, too. The
tables include the Mirror Information Table, the Configuration Table, the SL Table,
and others.
Make a new copy of the SYSTEMDIRECTORY and, in the process, assign new
record numbers to each record (each disk file header) copied from the old
directory to the new directory.
Adjust the linkages between segments of all segmented disk file headers in
the directory (for example, the disk file headers for files with more than 2000
AREAS).
Execute a family rebuild or catalog rebuild for the family to update the record
number information in the FAST or CATALOG.
Go through the main memory and update the record numbers in the disk file
headers for all permanent disk files that are currently open or are in the
STRUCTURE HEADER cache.
To make a coherent copy of the directory, the process procures various locks to
block all access to the SYSTEMDIRECTORY by programs and system software. This
activity blocks the opening and closing of files on the family, the removal of files
from the family, the changing of the file name or other attributes of files on the
family, and so forth. The locks also block the use of the PD (Print Directory) and
other system commands; CANDE FILES and LFILES commands, and MARC
commands that reference the family. In some cases, the blockage can extend to
uses of the PER PK command either manually or in an ADM (Automatic Display
Mode) display.
It searches for available disk space and adds spare AREAS to the
SYSTEMDIRECTORY.
If it cannot find enough available disk space to reach the number of AREAS
that you specified in the command, the system might try performing a special
form of the "SQUASH <family name>" process and then try to find more
space.
Using EXPAND SYSTEMDIRECTORY is much less disruptive than SQUASH
SYSTEMDIRECTORY and NEW SYSTEMDIRECTORY because it does not need to block
all access to the SYSTEMDIRECTORY while it is running. Using the EXPAND
SYSTEMDIRECTORY command consumes very little processor or I/O time except in
cases where it runs out of available disk space. In such cases, it attempts to move
files to make space available.
NF (No File)
The NF command is used to respond to a NO FILE message for a file that has a value
of FALSE for the OPTIONAL attribute. The program that tried to open the missing file
can continue processing the next action without being terminated as would occur if
the DS command was used.
Syntax
Explanation
The program specified by the mix number value receives an error result, and the
program can then determine whether to continue processing or terminate.
Example
In the following example, the W command indicates that a NO FILE condition has
occurred for the program specified by the mix number 7777. The NF command
enables the program to determine whether to continue processing or terminate.
7777 NF
Syntax
Explanation
<mix number list> NOTOK
Specifies that NO is the response for any RSVP messages for the tasks in the
specified mix number list.
NS (Next Screen)
The NS (Next Screen) command displays the next screen, if any, when a previously
entered system command requires several screens to display its output.
You can enter any command, such as CQ, to terminate the display of the first
command. However, WFL statements, such as REMOVE, do not cancel the display.
Syntax
Explanation
NS
Displays the next page of output when a previously entered system command
requires several screens to display its output. If several screens are required, the
display of each screen except the last includes an NS command ready for entry, and
the display waits until the NS is entered before proceeding to the next screen.
The next screen flag (NS) is usually set up only when there might be more
information to display. In some cases, the NS response might not be able to find
more entries to display. In those cases, one of the following messages is displayed
after the header line:
The second message indicates that more entries would have been shown if ALL had
been specified with the previously entered system command.
NW (Network Prefix)
The NW (Network Prefix) command directs BNA Version 2 and OSI operator input
commands to the BNA operations interface.
If the error message HOST USERCODE NOT SET results when you enter an NW
command, check to see whether a usercode is available for the command; some
types of networks accept operator input commands only with a usercode. If the
command is entered at an ODT, either the Host Usercode or the TERM Usercode is
used. If neither of these usercodes have been established, the command may be
rejected. For information about assigning these usercodes, refer to the HU (Host
Usercode) and TERM (Terminal) commands.
Syntax
Explanation
NW NS
Passes the operator command to the network selector interface for processing. Refer
to the Networking Commands and Inquiries Help for more information about
BNA Version 2 network operator input commands.
Example
This example shows typical NW NS commands to start and stop BNA using the
previously established NETINIT file name, and to show the default NETINIT file
currently associated with BNA.
For more information about NW NS command input, refer to the Distributed Systems
Services (DSS) Operations Guide.
If the NETEX library is initializing, running, or terminating, the character string that
follows NX is passed to the NETEX operator stack for processing and response.
If the NETEX library is not running when you enter the NX command, the following
message appears:
Syntax
Explanation
For the format of NETEX software operator commands, refer to vendor software
documentation.
O (Overlay)
The O (Overlay) command displays the current system overlay utilization statistics.
It can also be used as a timed option for the ADM (Automatic Display Mode)
command. For more detailed information, refer to ADM (Automatic Display Mode).
Syntax
Explanation
The O (Overlay) command displays the current system overlay utilization statistics,
which include the amount and percentages of overlay disk usage and the system
percentages for the overlay.
The statistics display has two parts: processor overlay utilization statistics and
overlay disk utilization statistics.
Component Description
Change per Second The smoothing factor used to determine current overlay
activity. You can change this value by setting the
OLAYCHANGE factor in the SF (Set Factor) system
command.
Component Description
Overlay Disk Allocated The percentage of Total Overlay Sectors that are
allocated for use by overlayable arrays.
Example
OVERLAY
OF (Optional File)
You can enter the OF (Optional File) command in response to a NO FILE message, if
the file being sought has its OPTIONAL attribute set equal to TRUE. The program that
generated the NO FILE message proceeds without this optional file by taking end-of-
file (EOF) action. If library maintenance encounters certain errors, it issues a RECOPY
REQUIRED message. You can enter the response OF to cause library maintenance to
skip the failing file and allow the COPY to proceed with other files.
You can also use the OF command in response to some REQUIRES PK and REQUIRES
DK messages. The OF command enables the program to continue processing without
the requested disk; however, the outcome of using the OF command varies,
depending on the reason that the program first requested the disk:
Syntax
Explanation
<mix number list> OF
Causes the programs specified in the mix number list to proceed without the optional
file.
Example
In this example, the W (Waiting Mix Entries) command indicates a NO FILE condition
for the program identified by mix number 3968. An OF command causes the
program to proceed without the optional file XYZ (DK).
3968 OF
OK (Reactivate)
The OK (Reactivate) command reactivates tasks if they have been suspended or
stopped for some reason. For some examples of situations in which the OK command
can be used, refer to the RES (Reserve) and ST (Stop) commands.
Syntax
Explanation
<mix number list> OK
Reactivates the suspended tasks in the mix number list.
Example
This example shows a W (Waiting Mix Entries) command and the OK response that
the operator enters.
9080 OK
Syntax
Explanation
OL <device type> <unit number list>
Displays the label and path information for the devices. The OL unit display is divided
into two parts: an upper area composed of several lines describing information
specific to the unit, and a lower area describing the control or controls that the unit
services. The following information is provided in the OL display of a unit.
CTL The device number of the control that services the unit.
STATUS The status of the CTL. The following list shows the
possible status conditions:
The system displays an open count for disk packs and CD-ROM units that includes
the number of open files and the number of MCP tasks that are using the entire
pack. If the total time to compute the number of open files for all packs or CD-ROM
units on a screen is under 60 seconds, the system displays the open count. The
system does not display an open count for the remaining packs or CD-ROM units on
the screen (including the one being computed when the time limit was reached). This
case is different from a pack or CD-ROM unit without open files, which displays an
open count of zero. The system displays an asterisk (*) for packs that have run out
of time.
Firmware CTL specific Firmware. If the CTL does not have Firmware
loaded, the status will be either: FREED, RES MAINT,
RESERVED, HUNG, OUT OF SERVICE, or NO PATH.
STATUS The status of the port the CTL is servicing. The following
list shows the possible port status conditions:
For an FC2 OSR CTL that is connected to a storage processor that is configured for
multipath operation, the following message is shown on a separate line in the
display:
SP-x is SP-A if the control is for a connection on storage processor A or SP-B if the
control is for a connection on storage processor B.
<mio>
The internal bus within the pod on an IOP system
<bus>
The PCI bus within a PCI bridge on an IOP system
<slot>
The slot in the PCI bus occupied by the IOP
<bus>
The PCI bus within an IO node on an IOP system
<slot>
The slot in the PCI bus occupied by the IOP
PORT Description
Information
IOP Examples
These examples show an OL command display for an IOP SCSI port.
OL IOP 7
OL IOP 10
Port
Information Description
Port
Information Description
Download Capable The Download Capable state of the port can be either Yes or
No.
Subprotocol State For ports that have subprotocols, an additional line appears
following the first line of the display. The state of the port
can be
Offline
Initializing
Initialized
Downloading
Maximum For SCSI ports only. The port either supports or does not
Blocksize support Maximum Blocksizes. An additional line appears
Capability following the subprotocol state, with the following possible
values:
CTL The device number of the CTL that services the port.
CTL Information
Description
Port
Information Description
STATUS The status of the CTL that services the port. The following
list shows the possible CTL status conditions:
VIA PORT All ports that can access the control. The names of ports not
online are enclosed in parentheses.
Examples
Port Examples
This example shows an OL command display for a SCSI port. This port does support
Maximum Blocksizes because all of the ports in its port group support Maximum
Blocksizes.
OL PORT 28145
This example shows an OL command display that includes the Fibre Channel port
name and node name of the Fibre Channel adapter. Both of the 64-bit Fibre Channel
port names are displayed as 16 hexadecimal digits. If the adapter is not capable of
returning this information, the lines are notpresent in the display
OL PORT 31031
OL PORT 5001
OL PORT 15001
CTL Examples
This example shows an OL command display for a SCSI tape CTL:
OL CTL 1451
This example includes the Fibre Channel port name that has been associated with
that control. The 64-bit Fibre Channel port name is displayed as 16 hexadecimal
characters. If a port name is not associated with the control, the line is not present
in the display.
OL CTL7541
This example shows the display for an OSR CTL control for a CLARiiON disk
subsystem that is configured for multipath operation. The control is for a connection
on storage processor A. It is port 0 on that storage processor.
OL CTL 16001
OL MT 52
The following table describes letters or symbols that are not shown in the example,
but which can appear on the first line of the Tape Unit display.
Value Description
R Indicates that the unit has had security restrictions imposed on it. For
more information, refer to the RESTRICT (Set Restrictions) command.
K Indicates that the tape is a library maintenance tape that contains one
or more files with LICENSEKEY.
@ The tape is write-enabled but has been locked by the LOCKED file
attribute.
Notes:
If you mount a scratch tape that is not write-enabled, the tape is displayed as
UNLABELED. This is useful in case you accidentally purged the tape. The
scratch label overwrites only the first few records on the tape. Write-
protecting the tape volume enables you to recover the rest of the data by
reading the tape as an unlabeled tape.
If you mount a tape that contains an ordinary data file that is expired, and
SYSOPS TAPEEXPIRATION is FALSE, and the tape is write-enabled, the OL
display shows the tape as SCRATCH. If you write-protect the tape and
remount it, the OL display shows the name of the expired file.
The following table explains other fields pertaining to tape units.
CREATION DATE The date that the first file was written on the tape.
EXPIRATION The creation date plus the value (in days) of the
DATE MALEFACTOR file attribute.
CREATION SITE The system serial number of the site where the first file on
the tape was written.
LIBMAINTDIR File name of the tape directory disk file for library
maintenance tape. This file should reside on the DL
LIBMAINTDIR disk family.
UNIT HAS The tape drive supports LOCATE and READLOCK commands.
LOCATE FAST
ACCESS
CAPABILITIES
MAXIMUM A number that represents the maximum block size (in bytes,
BLOCKSIZE not words) that can be handled by the unit.
LOCKEDFILE The tape has been locked by the LOCKEDFILE attribute. For
TAPE (PURGE more information about the LOCKEDFILE attribute, refer to
REQUIRES the File Attributes Programming Reference Manual.
CONFIRMATION)
BLOCKSIZE The label of the tape mounted on a tape drive indicates that
<number> TOO the block size of the file exceeds the maximum block size
LARGE, CAN'T that the unit can handle.
READ
OL PK 101
Each pack entry in the display includes the unit number, type of pack, label
information (family name and serial number), and the time limit value in effect for
READ and WRITE operations to the disk. The following fields are displayed.
Field Description
3 The pack type. The following codes are displayed: B: Base pack C:
Continuation pack U: A pack that is not available for normal use.
4 The letter A if the disk is a base pack and it has a local system access
directory. Refer to the FAMILYACCESS (Directory Location) command.
This display does not show such an example.
6 The letter D indicates that the disk pack is listed in the Volume Directory.
Field Description
7 The letter R if security restrictions were imposed on the pack. For more
information, refer to RESTRICT (Set Restrictions) in Section 10. This
display does not show such an example.
11 A letter r indicates that the disk unit was resized. Otherwise the column
is blank. This display does not show such an example.
12 The letter c indicates that caching is desired for the pack. That is,
caching was previously indicated in a successful CACHE + system
command. If the letter c has parentheses around it, caching is desired
for the pack, but the disk caching subsystem has not attempted to
activate caching. Packs in this caching state are not included in the count
of caching packs displayed by the CACHE command. This state can occur
for one of the following reasons:
The disk caching subsystem is not running.
The pack is offline or has no path.
If the letter c is followed by a minus sign (), caching is desired for the
pack, and the disk caching subsystem has attempted to activate caching,
but has failed for one of the following reasons:
No active data transfer units (DTUs) are on the system.
Memory reconfiguration has resulted in insufficient cache memory.
Packs in the c state are included in the count of caching packs
displayed by the CACHE command.
Field Description
13 The disk pack family description in brackets ([ ]). The family description
consists of the following three items, with colons (:) separating them:
Item 1. The serial number of the disk pack on this unit.
Item 2. The serial number of the pack used to identify the family;
that is, the first pack created in the family. Note that this is not
necessarily the base pack if the family has duplicated directories
Item 3. The unit number of the current base pack for this family.
If item 3 refers to the unit itself, then it is omitted. If item 3 refers to the
unit itself and item 2 is the serial number of the pack on this unit, then
items 2 and 3 are omitted.
16 The open count (in parentheses) on the disk. This count includes the
number of open files and the number of MCP tasks that are using the
entire pack. A pack with no open files and that is not in use by the MCP
displays an open count of zero. If the value in parentheses is an asterisk
(*), the computation time to derive the in-use count was excessive.
17 (TO BE SAVED) text, if applicable. This text indicates that the pack is a
critical pack which will be saved at the next halt/load. A critical pack is a
pack that has been specified in a DL (Disk Location) command.
OL PK 800
OL PK 245
OL PK 408
PK 408*B [123456:000000] #1 S P A R E
FAMILY CREATED ON: 07/27/2005 AT 11:15:34
CREATION SITE 5
SCSI/674 PACK
CAPACITY: 3,746,952 SECTORS (674,451,360 BYTES)
CTL FIRMWARE STATUS
2384 0024 ONLINE
2344 0024 ONLINE
Note: Packs assigned to MDPF as spares are recognized by the system as scratch
packs. They can be assigned to an existing or new family after the spare disk pool
designation is removed by the RC (Reconfigure Disk) command.
OL PK 1673
OL PK 19100
OL PK 19100
OL DK 255
OL PK 701
OL PK 15182
The OL system command displays the USS 5100 Cabinet ID and Logical Volume ID
for any disk pack that is emulated by a USS 5100 subsystem. If the MCP is unable to
determine what the cabinet id or the logical volume id are, the text UNKNOWN is
displayed in lieu of the numeric value. For example, if neither the cabinet id nor the
logical volume id are valid, the format will be as follows:
60-word boundaries. For information about VSS-1 and VSS-2 directory formats, refer
to the Peripherals Information File on the Product Documentation CD-ROM.
Following is a display for a 180-byte disk that was reconfigured using the RC
(Reconfigure Disk) command with the VSS = VSS2 option:
OL SC 2
SC 2 S C R A T C H
CTL STATUS
2001 ONLINE
OL SC 3
SC 3 RESTRICTED
CTL STATUS
2001 ONLINE
The following display is for a restricted ODT under Menu-Assisted Resource Control
(MARC) control:
OL SC 3
The following example shows an ODT in that configuration in its normal operating
condition:
OL SC 1
SC 1 S C R A T C H
CTL IP Address STATUS
5500 123.45.678.90 IN USE
5600 123.45.678.90 ONLINE
In the preceding example, the IP Address is the address of the workstation hosting
the Web Enabler application. The path currently being used by the MCP is indicated
by the status IN USE. The status ONLINE and the presence of the IP address
indicates the path is connected.
The following example shows an ODT that is connected to only one path:
OL SC 1
SC 1 S C R A T C H
CTL IP Address STATUS
5500 123.45.678.90 IN USE
5600 Not connected OFFLINE
OL LP 11
LP 11 S C R A T C H EBCDIC96
MAXIMUM BLOCKSIZE 132 BYTES
B9246-12 PRINTER
CTL STATUS
1301 ONLINE
OP (Options)
The OP (Options) command displays, sets, or resets run-time operating system
options that affect various system operations.
Syntax
<option list>
Here are the available run-time operating system options and their corresponding
numbers.
1 OPEN 25 MOREBACKUPFILES
2 TERMINATE 26 LOGPOSITIONING
3 NOCHECK 27 SERIALNUMBER
4 LPBDONLY 28 ARCHIVING
5 AUTORM 29 CDRUNITNUMBER
6 DIAGNOSTICS 30 LIBRARYDEBUG
8 AUTORECOVERY 32 MORETASKS
9 DUPSUPERVISOR 33 KEYEDIOII
10 DUPINTRINSICS 34 MIRRORING
11 TRANSWARNINGS 35 DIAGNOSTICDUMP
12 AUTODC 36 AUDIT
13 NODUMP 37 FILESATURATION
15 AUTORUNNING 39 STRICTSCHED
16 CRUNCH 40 NETRECOVERY
17 BACKUPBYJOBNR 41 GRAPHDEBUG
18 PDTODISK 42 ISCDEBUG
19 NOFETCH 43 IODIAGNOSTICS
20 RESOURCECHECK 44 PORTDEBUG
21 DRTRRESTRICT 45 USECATDEFAULT
22 DIRDEBUG 46 CATTEST
23 CATALOGING 47 MCPTEST
24 OKTIMEANDDATE
Explanation
OP
Displays all options and their respective states.
OP +
Displays all options that are set.
OP + <option list>
Sets all options in the option list.
OP
Displays all options that are reset.
OP <option list>
Resets all options in the option list.
OP <option list>
Displays the options in the option list and their respective states.
<number>
Identifies the option desired. The number is between 1 and 47; however, some
values are not used. The number of each option is listed with the following
descriptions.
OPEN (option 1)
If this option is set, the system displays a message whenever a task opens a file.
TERMINATE (option 2)
If this option is set, abnormal task terminations are processed normally.
If the option is reset, abnormal terminations, faults, configuration errors, file open
failures, and other various error conditions result in a memory dump. Some of the
conditions that cause dumps when the option is reset, such as file open failures, can
occur frequently. Because frequent file open failures results in a large number of
system memory dumps, the TERMINATE option normally should be set. Reset it only
if you need a memory dump to assist in diagnosis of a problem.
If a file open operation fails while the TERMINATE option is reset, a system memory
dump is taken with a dump cause of OPEN ERROR #n. The value of n corresponds to
the values of the HISTORYREASON task attribute for HISTORYTYPE=4 (DSEDV) and
HISTORYCAUSE=8 (SOFTIOERRORCAUSEV). These attribute values are listed in the
description of the HISTORYREASON attribute in the Task Attributes Programming
Reference Manual. For example, a dump by OPEN ERROR #0000093 indicates that
the open failed because the file was not available.
NOCHECK (option 3)
If this option is set, memory dumps under FORGETCHECK conditions are inhibited.
These dumps are automatic if the option is reset.
LPBDONLY (option 4)
If this option is set, normal printer output files are assigned to a printer backup disk
or tape. (The printer backup disk or tape is determined by the SB and DL BACKUP
specifications.) Printer backup disk files can then be printed by the Print System, the
SYSTEM/BACKUP utility, or the Work Flow Language (WFL) PRINT statement. The
LPBDONLY option does not affect the assignment of printer files that are DIRECT
files, files that have the UNITNO file attribute set to a nonzero value, files that have
the PRINTDISPOSITION file attribute set to DIRECT, or files that have the
BACKUPKIND file attribute set to a specific type of device, such as TAPE.
AUTORM (option 5)
If this option is set, the system automatically removes the old disk file when a
duplicate-file condition occurs. If the option is reset, an RM (Remove) or OF
(Optional File) command is required when such a condition occurs.
DIAGNOSTICS (option 6)
If this option is set, an RSVP message (for example, RF DEGRADATION) is displayed
at the ODT any time the reliability of a hardware unit is degraded by a set amount
and other diagnostic messages and dumps occur. If the option is reset, an
informational message is displayed. For more information about the reliability of
system units, refer to the RF (Reliability Factor--IOM Systems) command.
If this option is set with Option 6 of the ID system command also set, the system
takes programmatic NSP dumps after the following errors: abnormal process
If this option is set, the system reissues the recall request for outstanding station
messages, if they are not recalled by the first request. If the second recall request is
unsuccessful, the system takes a non-fatal dump.
AUTORECOVERY (option 8)
If this option is set, a halt/load is attempted after all system-fatal memory dumps
(except dumps caused by a suspended processor). After the halt/load, DCPs or NSPs
that were running before the halt/load are reinitialized.
If this option is reset, the system reports a deadstop condition after all system-fatal
memory dumps. For systems with Console Recovery support, a deadstop condition
specifies halt/loading the partition. If the Console Recovery option is set to load the
partition, the system is automatically loaded. Otherwise, the system remains halted.
Furthermore, the AUTORECOVERY operations do not occur after a halt/load, and the
mix limit of all queues is set to a value of 0 so that no jobs are automatically
restarted.
DUPSUPERVISOR (option 9)
If a code file titled <file name> is designated as the supervisor program and this
option is set, at halt/load time the system executes a code file titled <file
name>/FMLYINXnnn. If this option is reset, the system executes the designated
supervisor program. The number <nnn> in the file name represents the family index
of the current halt/load unit. If you use this option, it is recommended that you
locate the supervisor file on each halt/load pack and name the file with the
appropriate suffix.
For more information about the supervisor program, refer to the CS (Change
Supervisor) command.
For more information on the intrinsics file, refer to the SI (System Intrinsics)
command.
If the option is reset, the translation warning mechanism is inactive. By default, the
TRANSWARNINGS option is reset. For more information about translation, refer to
the I/O Subsystem Programming Guide.
For more information about memory dump processing, refer to Memory Dump
Processing.
AUTORUNNING also controls the way that operator intervention is handled during
memory dumps. When the AUTORUNNING option is set, the DUMPDISKMASTER
independent runner always creates a dump file on disk. If the DL DPFILES
specification is null, the default disk location is the halt/load family.
System initialization takes the following default actions when you set the
AUTORUNNING option:
If the halt/load unit is not in the current configuration, the unit is acquired
without an RSVP.
If the CATALOG family cannot be found and the site is not cataloging (the OP
CATALOGING option is not set), the DL (Disk Location) specification defaults
to the halt/load family.
If the CATALOG family cannot be found and the site is cataloging (if the OP
CATALOGING option is set), no default action is taken.
System memory dumps take one of the following default actions when you set the
AUTORUNNING option:
For more information about the Dumpanalyzer utility, refer to the System Software
Utilities Manual.
If this option is set, the system automatically sends all program dumps to
disk.
If this option is reset, the system automatically sends all program dumps to a
printer, unless the PROGRAMDUMP statement in the program or either the
<mix number> DS command or the <mix number> DUMP command has
specified TODISK.
When you want to print the program dump contained in the PDUMP file, you must
run SYSTEM/DUMPANALYZER to process that file.
Note: You can enable or disable this option during the OKTIMEANDDATE
verification. If you enable or disable the option after system initialization is
completed, the change does not take place until a halt/load occurs.
If the option is set, the system displays the current TIME and DATE settings on the
ODT after a halt/load, and you must enter TIMEOK in response to the message
PLEASE VERIFY TIME AND DATE to resume normal processing. To correct TIME or
DATE before entering TIMEOK, use the DR (Date Reset) or TR (Time Reset)
commands.
Caution
If you use disk mirroring at your site, a halt/load performed during the delay
while the system waits for the response to the RSVP message causes the mirrors
to lose their contents.
If you reset this option, but the hardware that maintains the system time of day was
reinitialized, or the time was set at the console by an operator before a halt/load, or
the system date does not match the console date, an OK_TIME_AND_DATE job waits
asynchronously for you to reply with an OK response. Normal processing continues.
*BD/<7 digit job number>/<7 digit mix number>/...<12 digit file number>/<file
name>
*BD/<7 digit job number>/<7 digit mix number>/...<3 digit file number><file
name>
Note: Changes to the MORETASKS option to not take effect until the next halt/load.
For more information, refer to the MAX (Maximums) command.
Resetting this option ensures that all new files created with FILEORGANIZATION =
VALUE (INDEXED) or VALUE (INDEXEDNOTRESTRICTED) are linked to the
SYSTEM/KEYEDIO library and are created as KEYEDIO files. Existing files are
correctly linked to either SYSTEM/KEYEDIO or SYSTEM/KEYEDIOII depending on how
they were created. KEYEDIOII files are created only when the FILEORGANIZATION is
explicitly set to VALUE (KEYEDIOII). Otherwise, a KEYEDIO file is created.
Mirrored sets are allowed to come online only if the MIRRORING option was set
before the last halt/load, and it has remained set.
In this display, hhh denotes the hours, mm denotes the minutes, and ss.s denotes
the seconds (rounded to the nearest tenth).
Note: Because of the increased likelihood of the scheduling of new tasks, setting
STRICTSCHED is not recommended for most systems.
The GRAPHDEBUG option enables the tracing of diagnostic information about stack
search graph additions, deletions, search actions, and stack termination prevention
actions. A process called GRAPHDEBUG_LOGGER, which writes the trace information
into the log, is active while this option is set. The processor and memory
requirements for this option are minimal.
Examples
Example 1
The following example shows the response to a simple OP command. Options that
have an asterisk (*) next to them are set; all others are reset.
OP
Example 2
This example shows the display for a status query of option 1:
OP 1
1 OPEN RESET
Example 3
This example displays all reset options:
OP -
Example 4
These commands set or reset particular options:
OP + 3
3 NOCHECK SET
OP - 3
3 NOCHECK RESET
OPLOCKTIMEOUT
The OPLOCKTIMEOUT command interrogates and sets the time-out values used by
the opportunistic locking feature of Client Access Services. It controls the parameters
of the algorithms that time out requests to return opportunistic locks.
You can use the minimum values during off-hours while using library maintenance to
back up files and use the default values during normal working hours. This usage
minimizes the delay to library maintenance caused by powered-off PCs.
Syntax
Explanation
If you enter the command without integers, the system displays the current values.
<integer>
The first integer specifies the maximum time, in seconds, a user or program
attempting to access a file has to wait, while an outstanding opportunistic lock is
recalled. If the workstation holding the lock does not return it and remains connected
for this time period, a NOTAVAILABLERSLT result is sent to the workstation client or
the MCP environment user that is requesting access to the file.
Reducing this value reduces the delay in the case where the client with the
opportunistic lock is in some undesirable state and cannot return the
opportunistic lock.
Increasing this value can reduce the cases where a NOTAVAILABLERSLT
result is returned because the client with the opportunistic lock is slow to
respond but is responding. (The slow response can result from the client not
giving high priority to the task of returning the opportunistic lock, or because
it is behind a congested TCP/IP router.)
The second integer specifies the allowed idle time, in seconds, before the connection
is dropped to a client workstation that is not responding to an opportunistic lock
recall command. Any workstation activity restarts this time period. Therefore, the
elapsed time, before connection to the workstation is dropped can be greater than
the allowed idle time. (When Client Access Services drops the connection to a client,
it closes all files opened by that client. This implicitly frees any opportunistic locks
held by that client.)
Reducing this value reduces the delay in the case where the client, with the
opportunistic lock is either powered off, in software failure, or otherwise not
responding.
Increasing this value can reduce the cases where a long pause in activity is
interpreted as complete failure. (Long pauses in activity, as seen by the
server, can be caused by poor processor scheduling by the client or by
packets being dropped by a congested TCP/IP router.)
OPLOCKTIMEOUT = 30, 10
OPLOCKTIMEOUT = 10, 3
Syntax
Explanation
<mix number> OT <number>
Displays the contents of the stack cell specified by <number> for the task identified
by <mix number>. The <number> must be an integer between zero and the length
of the task stack. The stack cell is selected by adding <number> to the offset of the
base of the outer block in the task stack. The program stack number is displayed in
hexadecimal characters, followed by the contents of the stack cell, including its
extent (for IOP systems), its tag, and its 48 data bits. Their values are presented in
hexadecimal form. If the stack cell contains a single-precision integer, its decimal
value is also presented.
Examples
Example 1
8903 OT 2
Example 2
8904 OT 5
Note: The selected stack word in this example contains a nonzero extension (1).
Example 3
8904 OT 6
OU (Output Unit)
The OU (Output Unit) command directs output from the specified task or tasks to a
specified output device or to any available device of the specified type. Sometimes
you can use the OU MT form of the command to respond to a MT <unit number>
RECOPY REQUIRED <filename> RSVP message issued by library maintenance.
Syntax
Explanation
<mix number list> OU MT <unit number>
Directs output from the task specified by the mix number to the specified tape unit,
provided it is write-enabled and identified as SCRATCH. (This command overrides
locked units.) This form of the command can override a request for a specific type of
tape unit and can substitute any other type of unit, if no units of the requested type
are available. Any substitute backup setting set by the SB (Substitute Backup)
command is ignored. The OU MT command overrides any tape serial number and
density specifications made by the program.
If the file has a family name specified, the file is sent to the pack with that
family name.
If a file has no family name specified, it is sent to PACK by default. If a
substitute backup medium was established for PACK by the SB (Substitute
Backup) command, output goes to the substitute medium instead.
<mix number list> OU PK <unit number>
Places the files on the specified disk pack unit. Only a write-enabled base pack with
the specified name can be designated. Any substitute backup setting set by the SB
(Substitute Backup) command is ignored.
If the file has a family name specified, the file is sent to the pack with that
family name. Only a write-enabled base pack with the specified name can be
designated.
If a file has no family name specified, it is sent to DISK by default. If a
substitute backup medium was established for DISK by the SB (Substitute
Backup) command, output goes to the substitute medium instead.
<mix number list> OU DK <unit number>
Places the files on the memory disk unit identified by <unit number>. Any substitute
backup setting set by the SB (Substitute Backup) command is ignored.
Example
Several RSVP messages accept a response of OU. One such message is the
REQUIRES message, which is generated when a task cannot locate a unit that
matches the selection attributes of an output file. The MCP generates a message
similar to the following:
2121 OU MT 28
The first message is generated because a direct file asking for a line printer cannot
go to backup under any circumstances. Direct means that the program is using direct
I/O and must therefore deal with an actual target peripheral. Refer to the I/O
Subsystem Programming Guide for a description of direct I/O.
You can also use the OU MT command to override the complying tape volume
requirement at installations that use the tape security subsystem. However, the OU
MT command cannot override the <family owner> specification of the tape security
subsystem.
You can use the OU command to override a mismatch between the FORMID attribute
of the file, if specified, and the form of a printer, if any. However, these commands
cannot override the KIND attribute of the file.
Any attempt to override the KIND attribute of the file generates the following
message that indicates the devices expected by the OU command:
PARTIALSETS
The PARTIALSETS command provides information on mirrored sets with missing
members.
Syntax
Explanation
PARTIALSETS
PSETS
This command displays a list of all mirrored sets with missing members.
Examples
Example 1
This example shows a response to a PARTIALSETS command.
PARTIALSETS
AVAIL273
#1 ( 273)
DISK00
#1 ( 802) #2 ( 184) #3 ( 272)
.
.
.
ZEBRA
#7 ( 800)
Example 2
This example shows a response to a PARTIALSETS command for two mirror sets.
DISK00
#1 ( 802) #2 ( 184) #3 ( 272)
ZEBRA
#7 ( 800)
PB (Print Backup)
The PB (Print Backup) command prints backup tape files.
Syntax
Explanation
PB MT <unit number>
Starts an MCP task called TAPEPRINT/LPnnnn/MTnnnn. The task rewinds the
specified drive, reads the tape, and sends the contents to the first available printer.
Note: To use the WFL PB statement, enter the syntax ?PB or CC PB followed by the
appropriate syntax elements.
Following are some examples of the PDIR command. For a detailed discussion of this
command, refer to the PDIR Utility and PMIX Utility section of the System Software
Utilities Operations Reference Manual.
Example 1
This request examines all the files on disk that have no usercode and returns a list of
files that are using more than 5000 sectors of disk space. The returned file list is to
be sorted in decreasing number of sectors occupiedthat is, from largest to
smallest.
Example 2
This example lists all usercoded files on PACK that have a FILEKIND of
MCPCODEFILE:
Example 3
This example retrieves all nonusercoded files that are using more than 10,000
sectors of disk space and puts the output in a JOBSYMBOL file named LARGE/FILES:
Example 4
This example opens a remote file and routes it to a particular station:
Example 5
This example opens a remote file at a station at host MP456:
Syntax
Explanation
Note: If a <unit number range> is specified, the response is limited to unit
numbers within the range.
PER
Displays the status of all peripheral units.
PER =
PER
Displays the status of all peripheral units, including unlabeled and unready devices.
For mirrored disks, this command displays all members (PER PK displays only one
member of each mirrored set).
If a pack or a CD-ROM on a given unit has a status of U (unavailable for normal use),
any of the following messages might be displayed.
Message Explanation
DUP SERIAL Indicates that a serial number for the pack matches a
serial number of another pack on the system.
NOT AVAILABLE TO Indicates that the unit has not been acquired into the
GROUP current running system group.
RESERVED Indicates that the pack has been taken offline with
the UR (Unit Reserved) command.
SCRATCH Indicates that the pack has been purged with the PG
(Purge) command.
Examples
Example 1
This example shows a response for a PER MT command:
PER MT
A write-enabled flag
Symbol Description
@ Indicates that the tape is write enabled but has been locked by the
LOCKEDFILE file attribute.
A media-type flag
Symbol Description
Symbol Description
Optional flags
Value Description
R Indicates that the unit has had security restrictions imposed on it. For
more information, refer to RESTRICT (Set Restrictions).
K Indicates that the tape is a library maintenance tape that contains one
or more files with LICENSEKEYS.
Name Description
UNLABELLED Indicates that the tape does not have a recognizable label.
If the label of the tape mounted on a tape drive indicates that the block size of the
file exceeds the maximum block size that the unit can handle, the following message
is displayed in place of the title, <I> is the block size in the label:
The first three lines of the example contain messages that pertain to tape
compression. MT 56 represents an unlabeled tape on a compression-capable drive.
MT 59 represents a compressed tape mounted on a compression-capable drive. MT
97 represents a compressed tape mounted on a drive that does not support
compression.
Note: If you load a tape with a write ring, and the tape contains an ordinary data
file that is expired, and the SYSOPS TAPEEXPIRATION option is set to TRUE, then the
display shows the tape as a SCRATCH tape. If an expired tape is mounted without a
write ring, the display shows the tape with the name of the expired file.
Example 2
This example shows the response for a PER PK command:
PER PK
Each pack entry in the PER PK display includes the unit number, type of pack, and
label information (family name and serial number). The display also indicates
whether the pack is currently being used by an MCP procedure (for example,
READPACKLBL). For all systems that support the Mirrored Disk Pooling Facility
(MDPF), the display identifies free spare disks assigned to the spare disk pool. Spare
disks can be assigned to a new or existing family if you remove the spare
designation with the RC (Reconfigure Disk) command. The following fields are
displayed.
Field Description
2 This field displays an asterisk (*) if the write-enable switch is on and the
MODE is IO or OUT; a blank if the write-enable switch is off or the MODE
is IN.
3 This field displays the pack type. The following codes can be displayed:
B: Base pack
C: Continuation pack
U: A pack that is not available for normal use
4 The letter A indicates that the disk is a base pack and has a local system
access directory. Refer to FAMILYACCESS (Directory Location).
6 The letter R if security restrictions were imposed on the pack. For more
information, refer to RESTRICT (Set Restrictions).
9 The letter c indicates that caching is preferred for the pack. That is,
caching was previously indicated in a successful CACHE + system
command.
If the letter c has parentheses around it, caching is desired for the pack,
but the disk caching subsystem has not attempted to activate caching.
Packs in this caching state are not included in the count of caching packs
displayed by the CACHE (Disk Cache) command. This state can occur
when the pack is offline or has no path.
On IOM systems, if the letter c is followed by a minus sign (), caching is
preferred for the pack, and the disk caching subsystem has attempted to
activate caching, but this action has failed for one of the following
reasons:
No active data transfer units (DTUs) are on the system.
Memory reconfiguration has resulted in insufficient cache memory.
Packs in the c state are included in the count of caching packs
displayed by the CACHE (Disk Cache) command.
Field Description
11 The letter r indicates that the disk was resized by an LB (Relabel Pack or
Host Control Unit) or RC (Reconfigure Disk) command.
12 The disk pack family description in brackets ([ ]). Use the IOTIMER or OL
PK command to display the actual time limit value. The family description
consists of the following three items, with colons (:) separating them:
Item 1. The serial number of the disk pack on this unit.
Item 2. The serial number of the pack used to identify the family;
that is, the first pack created in the family. Note that this is not
necessarily the base pack if the family has duplicated directories.
Item 3. The unit number of the current base pack for this family. If
item 3 refers to the unit itself, then it is omitted. If item 3 refers to
the unit itself and item 2 is the serial number of the pack on this
unit, then items 2 and 3 are omitted. If the base pack is absent, the
continuation packs display the warning indication NO BP. The base
pack for the family might be offline, freed, saved, not ready, closed,
reconfigured, or purged. All continuation packs in the family might be
unusable. You need to determine the status and history of all base-
capable packs for the family and whether the continuation packs
from another backup directory are usable.
15 The open count (in parentheses) on the disk. This count includes the
number of open files and the number of MCP tasks that are using the
entire pack. A pack with no open files and that is not in use by the MCP
displays an open count of zero. If the value in parentheses is an asterisk
(*), the computation time to derive the in-use count was excessive.
16 (TO BE SAVED) text, if applicable. This text indicates that the pack is a
critical pack which will be saved at the next halt/load. A critical pack is a
pack that has been specified in a DL (Disk Location) command.
Example 3
This example shows a display for a memory disk. The designation B designates a
base pack:
PER DK
Example 4
This example shows the response to a PER DC command. DC designates a data-
comm-type device: an EDCDLP or a DCHA. The first entry describes the NSP type,
and the second entry describes its firmware level (the first number describes the
patch level, and the second number describes the PROM level). If no firmware has
been loaded, NOT LOADED is displayed as the firmware level.
PER DC
------------------------------ DC STATUS----------------------------
180 NSP (DC-CTL,LEVEL:85.0) (8896)
Example 5
This example shows the response to a PER DC command after the unit has been
freed. The status on IOM systems is always NOT AVAILABLE TO GROUP.
PER DC -
Example 6
The open count of each pack is displayed in parentheses if the total time to compute
the number of open files for all packs on a page does not exceed 5 seconds. If the
computation time exceeds 5 seconds, the field is not displayed. (A pack without open
files, on the other hand, displays an open count of zero.)
If the value in parentheses is an asterisk (*), the computation time to derive the in-
use count was excessive.
PER PK
Example 7
This example shows the display for three ODTs. The first two are not restricted; the
third is restricted:
PER SC
-------------------------------- SC STATUS--------------------------
1 S C R A T C H
2 S C R A T C H
3 (MCP) COMS/ODT/DRIVER RESTRICTED
Example 8
This example shows displays for line printers attached to the system:
PER LP =
-------------------------------- LP STATUS--------------------------
4 S C R A T C H EBCDIC96
5 (0007) SERVER/LP5/"R#8476"/"J#3284" ASCII86
7 (0030) *SYSTEM/PRINTCOPY (UNKNOWN TRAINID)
8 (6969) FORMED : MEDFORM SERVER/LP8/"R#8476"/"J#3299"
9 FORMED : "MEDICAL FORM # 2"
10 (MCP) SAVED (DEFAULT DESTINATION)
11 N O T R E A D Y EBCDIC96 (DEFAULT DESTINATION)
12 R E S E R V E D
Each entry in the PER LP display includes the external unit number and the status of
the printer. The following fields are displayed.
Field Description
3 If the printer is in use, this optional field indicates the system or the
mix number of the stack using the printer.
If the printer is not in use, this optional field indicates that the printer
is configured for special forms with the designation FORMED, followed
by the form identifier.
5 If the printer is not in use, this optional field contains either the name
of the TRAINID character or the statement (UNKNOWN TRAINID).
TRAINID is a file attribute that refers to the character set that is
available to the printer.
Example 9
This example shows the response to a PER NP command. NP represents network
processors:
PER NP
-------------------------NP STATUS--------------------------------------
155 (ICPIIIM, LEVEL: 2.1) ACTIVE, COMMUNICATING
Entry Description
1 NP number.
Example 10
This example shows the response to a PER VC command. The command displays all
26 units and their status for each voice interface module (VIM) CTL in the
configuration. The first number in the display is the voice channel (VC) unit number
followed by either the mix number of the task (in parentheses) and the task name or
the word SCRATCH.
PER VC
Example 11
This example shows the response to a PER TSP command on an IOM system. The
first number is the TS unit number. If the TS unit number is followed by SCRATCH,
the unit is not in use. If the unit is in use, the TS unit number is followed by the mix
number of the task (in parentheses) and the name of the task.
PER TSP
Example 12
This example shows the response to a PER TSP command. The system displays
information about all TSP units, both online and offline. PER TSP displays only
information about online units.
PER TSP -
Example 13
This example shows the response for a PER command with a unit range:
PER 100-199 PK
PF (Print Fetch)
The PF (Print Fetch) command displays the FETCH message of a WFL job.
Syntax
Explanation
<mix number> PF
Displays the FETCH message from the specified WFL job.
Sometimes WFL jobs are submitted that contain a FETCH statement. If the NOFETCH
option has been reset (OP NOFETCH), any job that contains a WFL FETCH
statement appears in an SQ (Show Queue) display with an F after the mix number.
When the system attempts to start a job that has a FETCH statement, the following
RSVP message appears:
You can handle these jobs while they are still in the queue or after the system issues
the RSVP message by responding with any of the following commands.
Command Result
<mix number> PF Displays the text of the FETCH statement so that you can
react appropriately
<mix number> OK Clears the FETCH statement so that the job can execute in
its normal manner
<mix number> FS Clears the FETCH statement and immediately start the job,
even if the job is not at the top of the queue
The FETCH waiting entry might disappear and reappear as ML (Mix Limit) and MQ
(Make or Modify Queue) commands are entered and as jobs and tasks enter and
leave the mix.
Note: You can enter a <mix number> OK command for a job marked with an F in
the job queue before it is selected for execution. If you do, when the system deletes
the F from the SQ display and when the system selects the job for execution, the job
starts without issuing an RSVP message.
Example
In this example, the W (Waiting Mix Entries) command display shows that a FETCH is
required for the job whose mix number is 3738. The PF command displays the full
text of the FETCH message.
3738 PF
PG (Purge)
The PG (Purge) command purges tape, disk pack, or host control units, and erases
CD-RW media. The disk pack and tape units must be ready and not in use, and the
units must be write enabled. Host control units can be purged when they are not
ready.
If the command is rejected, wait for the current command to complete and enter the
command again.
Syntax
<density>
<scratch pool>
<oldname list>
<serial list>
Explanation
PG CD <unit number list>
You can use this command to erase CD-RW media that is mounted on a CD-RW
drive.
Notes:
If the CD-RW media was previously written successfully, the OLDNAME form
of the command must be used and the specified <name> must match the
name the of the previously written CD.
If the CD-RW media was previously written unsuccessfully, you cannot specify
an OLDNAME.
DVD-RW and DVD+RW media are not supported. Use PG CD only with CD-RW
media.
PG MT <unit number list>
Purges the volumes mounted on the tape units in the unit number list. That is, the
command names the tape units S C R A T C H, a name that prevents any programs
from retrieving data from that volume. The PG command requires that the tape is
labeled and has a serial number; however, this serial number is not affected by the
command. To assign serial numbers to tapes, use the SN (Serial Number) command.
Note: If a tape has only one allowable output density, no density specification is
necessary and any PG command that specifies density is rejected with the error
INVALID DENSITY SPECIFIED.
For more information about this option, refer to Considerations for Use.
If the disk packs have OWNER identification, you must verify purge permission
through an OK response to an RSVP message.
Reply as follows:
<mix number> OK
For labeled disk packs, the process checks their family names. If you specified
names with the OLDNAME option, the process checks to see if each disk family name
matches one of those names; if not, it terminates with an error message. If you did
not use the OLDNAME option, you must verify that you are purging the correct disks
by replying as follows for each labeled, nonscratch disk:
Reply as follows:
The <pack name> entered is compared with the pack name in the pack label. If
there is a mismatch, the task is terminated with the following error message:
PG HC <unit number>
Marks the host control (HC) unit identified by <unit number> as unlabeled. If the
unit is the last unit of a given hub to be purged and the hubname was not specified
in the group configuration, then the temporary hubmap is purged.
Examples
Example 1
This example shows a command that purges a tape:
PG MT 66
MT 66 WILL BE PURGED
Example 2
This example shows a command that purges a tape with a density of 1600:
PG MT 114 (1600)
Example 3
This example shows a command that purges a tape and assigns it to a scratch pool
named ACCOUNTING:
PG MT 55 SCRATCHPOOL = ACCOUNTING
MT 55 WILL BE PURGED
Example 4
This example shows a command that purges a tape on a compression-capable device
and writes a label that indicates compression was requested:
PG MT 55 COMPRESSED
Example 5
This example shows a command that purges a tape and writes a label that indicates
compression was not requested:
PG MT 55 NONCOMPRESSED
Example 6
This example shows a command that purges a tape with a density of 38000, assigns
it to a scratch pool named ABC and writes a label that indicates compression was
requested:
Example 7
This example purges a host control (HC) unit:
PG HC 66
HC 66 WILL BE PURGED
Example 8
This example purges a labeled disk pack:
PG PK 47 OLDNAME = DMSIITEST
PK 47 WILL BE PURGED
After you have purged the disk pack, you can enter a PER (Peripheral Status)
command to verify the results:
PER PK 47
Example 9
This example purges disks 80, 81, 836, and 837. Disks 80 and 81 have the name
TEST. Disks 836 and 837 have the name ALPHA. Disk 81 receives a new serial
number: 818181. Disk 836 receives the new serial number 836836.
Example 10
This example initializes disks 100 through 107 in VSS1 format, gives them the serial
numbers 555100 through 555107, and marks them as scratch disks in use:
If you respond to this message by entering <mix number> OK, the tape is purged.
To cancel the purge operation, enter DS.
A purged pack can no longer be labeled. Once a pack has been purged, it must be
reconfigured with the RC (Reconfigure Disk) command prior to its being allowed
online.
Decide if you want the system to remove the LIBMAINTDIR file or associated disk file
and continue to purge the tape. To locate the LIBMAINTDIR file or associated disk
file, use the OL MT <unit number> command to find the name of the LIBMAINTDIR
disk file or associated disk file. If you respond to this message by entering
<mix number> OK, the system removes the LIBMAINTDIR disk file or associated
disk file and purges the tape. To cancel the purge operation, enter <mix number>
DS.
Expired tapes are treated as though they were scratch tapes from the pool specified
in the nonscratch label.
Tape Compression
If you enter a simple PG command, which does not include a compression keyword,
to a device that does not support compression, and the original label indicates
compression was requested, the system processes the command with the following
results:
The system writes the label to tape as if you had specified the
NONCOMPRESSED option.
The system issues the following messages to serve as an operator warning:
MT<unit number> [<serial number>] UNABLE TO SET COMPRESSION
MT<unit number> [<serial number>] PURGED
Once a pack has been purged, it must be reconfigured with the RC (Reconfigure
Disk) command prior to its being allowed online.
The PG command does not remove the family index number. This number continues
to appear in PER PK command displays. For example, if a pack is the second
member of a disk family, and you purge that pack, the resulting PER PK display
includes the family index #2, as in the following example:
If you respond OK, the pack is purged, the pack label remains SCRATCH, a system
message states that the disk is no longer a free spare disk in the spare disk pool,
and a status change message is issued. The status change message is defined in the
MCP System Interfaces Programming Reference Manual. The system message is
PK <unit number> UNIT PG'ED AND REMOVED FROM THE SPARE DISK POOL
If you respond DS, the command is rejected and a system message states that the
pack remains a free spare disk in the spare disk pool. The message is
When a disk previously assigned to the spare disk pool has been moved to a system
that supports MDPF but does not have MDPF installed, if you attempt to purge that
disk, the following RSVP message appears:
If you respond OK, the pack is purged, the pack label remains SCRATCH, a system
message states that the disk is no longer a free spare disk in the spare disk pool,
and a status change message is issued. The status change message is defined in the
MCP System Interfaces Programming Reference Manual.
If you respond DS, the command is rejected and a system message states that the
pack remains a free spare disk in the spare disk pool.
When a disk previously assigned to the spare disk pool has been moved to a system
that does not support MDPF, the PG command clears the FREE SPARE attribute from
the pack label with no operator notification.
Syntax
Explanation
PLI
Displays the current logging parameters.
PLI +
Enables interval logging.
PLI
Disables interval logging.
Example
PLI
Following are some examples of the PMIX command. For a detailed discussion of this
command, refer to the PDIR Utility and PMIX Utility section of the System Software
Utilities Operations Reference Manual.
Note: Because the PMIX command generates a quoted string parameter to the
SYSTEM/PMIX program, any quotation mark in the input must be doubled.
Example 1
This example selects all mix entries with a name containing the string "PRINT"
excluding segment dictionaries. It displays the mix number, name, and process type.
Example 2
This example selects all mix entries that have a non-empty usercode. It displays the
name, usercode, and mix number.
Example 3
This example selects all mix entries that have a name beginning with the string
"*SYSTEM". It displays the mix number, name, task type, and ready queue time,
sorted in descending order of ready queue time.
Syntax
Explanation
POWER DOWN SYSTEM
POWER OFF SYSTEM
Requests that the MCP environment be shut down immediately.
Caution
Be careful if you use the immediate form of the POWER OFF or POWER DOWN
command. The system should be in an idle state so that no user jobs are
affected by the shut down.
At intervals, the system broadcasts a message to warn users about the impending
loss of power. Messages are sent at the following intervals:
PQ (Purge Queue)
The PQ (Purge Queue) command terminates all jobs in a queue but leaves intact the
attributes established by the QF (Queue Factors) command. The system does not
print job summaries for the terminated jobs. Active jobs that originated in the queue
are not affected by this command.
Syntax
Explanation
PQ <number>
Terminates all jobs in the specified queue.
Example
PQ 3
QUEUE 3 PURGED
PR (Priority)
The PR (Priority) command sets the priority of jobs or tasks. Changing the priority of
a job that is in a job queue can change the order of jobs in that queue, because the
system orders jobs in a job queue by job priority and then by time of entry.
The changes made by this command are temporary. If a halt/load occurs, the
changes are not preserved across the halt/load.
Syntax
Explanation
<mix number list> PR <number>
Assigns the priority specified by <number> to the PRIORITY task attribute of the
jobs or tasks in the mix number list. The value of the PRIORITY attribute can range
from 0 through 99, where 99 is the highest priority.
Examples
Example 1
4972,4980 PR 90
Example 2
4975 PR 30
PRIMITIVE RUN
The PRIMITIVE RUN command enables you to run a program from the ODT. The
effect is the same as the ??RUN primitive command. However, the ??RUN command
can be entered only at ODTs, whereas the PRIMITIVE RUN command can also be
entered from
Syntax
Explanation
When this command is successful, the operating system responds with the following
message:
If the program cannot run, an appropriate error message is displayed. For instance,
if the file specified does not exist, the following error message is displayed:
NO FILE
This command has the following effects in common with the ??RUN command:
Command Purpose
PS ADDFILES Add print requests for existing backup files with standard
system-generated titles that do not have an active task,
job, session, or print request associated with them.
Command Purpose
Command Purpose
PS DEFAULT Set (or display the current setting of) the following
defaults for the Print System:
The compression of the SYSTEM/BACKUPFILELIST file
at each system initialization.
The configuration of unknown remote devices.
The printer group to be used for printing requests that
do not have a specific destination.
The printing of job summary files when the
JOBSUMMARY task attribute has the value DEFAULT.
The PAGECOMP specification to be used with job
summary files.
The system-wide PAGECOMP specification to be used
with backup files or data files.
The point in a job when a print request is generated.
The PRINTERKIND specification to be used for printing
files.
The removal of backup files with a value of TRUE for
the LOCKEDFILE file attribute.
The maximum value that can be assigned as a print
request number.
The ordering of print requests displayed by the PS
SHOWREQUESTS command.
The identification of code that is to manipulate
attributes of print requests before the Print System
deals with those requests.
The identification of specific disk units where certain
Print System administrative files are kept.
The identification of when the Print System is to report
capacity warnings when a large number of print
requests exist.
Whether print request volumes are to be specified in
lines or pages.
The estimated number of records for files sent directly
to devices without being spooled.
The identification of the default EXTMODE mappings
for files of certain EXTMODE values.
Whether print request volumes are to be flagged with
a special indication if they are only estimates.
Whether the formatting of header and banner pages is
to be affected by the PAGECOMP of the file being
printed.
Determining of the system-wide behavior of the NOTE
file attribute.
474 8600 0395-514
Determining when files in a print request are eligible
for removal.
Specifying how long file are to be retained after
Print System (PS) Introduction
Command Purpose
PS DELETE Delete print requests from the print queue, or delete a file
within a print request.
PS HEADER Display or set the contents and format of the header page
which marks the start of each print request.
Command Purpose
PS RESTART Restart the Print System after it has been closed down by
a PS QUIT command.
PS SKIP Make the print server skip forward or backward from the
current position in the backup file and continue printing
from the new position.
PS TRAILER Display or set the contents and format of the trailer page
that marks the end of each print request.
Each of these commands is described in the Print System documentation. For more
information about using them to meet the needs of your site, refer to the Print
System and Remote Print System Administration, Operations, and Programming
Guide.
PV (Print Volume)
The PV (Print Volume) command displays all the information in the volume library
about a volume or volume family.
The PV command is valid only for installations where the CATALOGING option is in
effect.
Syntax
Explanation
PV MT <serial number>
Displays the information for the tape volume identified by <serial number>. The
serial number can be any number that is accepted by the SN (Serial Number)
commandthat is, it can be from 1 to 6 alphanumeric characters. The number can
also be enclosed in quotation marks (").
PV PK <serial number>
Displays the information for the pack volume identified by <serial number>.
PV DK <serial number>
Displays the information for the disk volume identified by <serial number>.
Examples
Example 1
PV MT 223344
Example 2
PV PK 000096
QF (Queue Factors)
The QF (Queue Factors) command displays the current values of all attributes of the
designated job queue.
Refer to the MQ (Make or Modify Queue) command for a detailed explanation of the
relevant queue attributes.
In any form of the QF command, the active count for a queue can be greater than
the mix limit of that queue if either of the following conditions is true:
A job or task from that queue has been forced from the job queue with a FS
(Force Schedule) command.
A job from the queue processes a dependent task.
Syntax
Explanation
QF
Displays the value of all attributes of each job queue. Any disk families assigned to
the queue are displayed.
QF <queue number>
Displays the value of all attributes of the job queue identified by the queue number.
If the queue number has not been previously defined, the following message is
issued:
If the system has no previously defined queues, the following message is issued:
Example
The following example shows no active jobs for queue 5 or queue 6:
QF
QUEUE 0:
DEFAULT QUEUE
MIXLIMIT = 10
ACTIVE COUNT = 1
DEFAULTS:
PRIORITY = 50
LIMITS:
PRIORITY = 50
QUEUE 5:
MIXLIMIT = 5
DEFAULTS:
PRIORITY = 50
PROCESSTIME = 900
IOTIME = 900
LINES = 1500
LIMITS:
NONE
QUEUE 6:
MIXLIMIT = 4
TURNAROUND = 1.00
DEFAULTS:
PRIORITY = 60
.
.
.
QT (Quit)
The QT (Quit) command terminates the printing of a backup file. QT is equivalent to
PS REQUEUE <device type> when the file is being processed by the Print System;
however, you cannot use QT for files being printed by the Remote Printing System.
The backup file remains in the directory and can be printed later with a Work Flow
Language (WFL) PRINT statement, the SYSTEM/BACKUP utility, or a command such
as PS MODIFY <request> if the file was processed by the Print System.
You can also use the QT command as a response to certain RSVP messages issued
by the system, such as the following:
Syntax
Explanation
When you use the <mix number list> QT command for backup disk files being
processed by the Print System, the file currently being printed stops printing and is
marked as an exception. However, the system does not remove the file from the disk
directory. The equivalent Print System command is PS REQUEUE <device
type>,where <device type> is a site printer (not a remote printing device) being
serviced by one of the programs in the mix number list.
If the mix number you specify is for a TAPEPRINT task processing a backup tape, the
system terminates output for the current file. TAPEPRINT then spaces forward to the
end-of-file marker and begins printing the next file on the tape if one exists;
otherwise, the tape rewinds
The QT command has no effect on a process that has been locked by the LP (Lock
Program) command.
Examples
Example 1
This example terminates the printing of a backup file:
6823 QT
Example 2
This example shows the command sequence to use if a task is locked:
2420 QT
PROGRAM IS LOCKED
2420 LP -
2420 QT
RA (Register Application)
The RA (Register Application) command enables programs to use the
REGISTER_APPLICATION procedure, which enables the MCP to monitor the programs
and to initiate recovery action if the programs fails to report to the MCP within a
specified interval.
Syntax
<application name>
A 1-to-17-character identifier that specifies the name of the application to be
monitored.
<user spec>
<code spec>
<restart spec>
Explanation
RA
Reports the following information on the applications being monitored.
Response Meaning
Response Meaning
Recovering The application has been restarted but has not checked in
yet
RA <application name>
Reports details of the specified application. This report includes running information
if the application is being monitored.
RA <application name>
Deletes the specified application from the list of programs being monitored.
RA + <application name>
RA + <application name> <user spec>
RA + <application name> <code spec>
RA + <application name> <restart spec>
RA + <application name> <user spec> <code spec> <restart spec>
Adds the specified application to the list of programs being monitored, or adds the
automatic restart option to the application. You can optionally add the user
specification, code specification, restart specification, or two of them, or all of them.
The restart specification specifies whether the program named as the RECOVERY
code file for the application is to be automatically restarted after a halt/load of the
system if it was running before the halt/load occurred. If the RESTART value is set to
TRUE, the system automatically restarts the recovery file when the system
reinitializes. The recovery program is given three minutes after being restarted to
check in by calling the REGISTER_APPLICATION procedure in the library
MCPSUPPORT. If it fails to check in, it is eliminated from the list of monitored
programs. The default RESTART value is FALSE.
Note: For more information about the restart feature, refer to the
REGISTER_APPLICATION procedure in the MCP System Interfaces Programming
Reference Manual.
Examples
Example 1
This example adds an application to the list of applications being monitored and
shows the system response:
Example 2
This example shows the command to list the application that was added in Example
1 and the system response:
RA PAYROLL
Example 3
This example deletes the application PAYROLL from the list of applications being
monitored and shows the system response:
RA - PAYROLL
Example 4
This example restarts the program OBJECT/PROG under the USER1 usercode after a
halt/load of the system if it was running when the halt/load occurred:
If the entry point REGISTER_APPLICATION is called on a system where the key is not
present, the system returns 12, which means FEATURE NOT INSTALLED.
RB (Rebuild Access)
The RB (Rebuild Access) command causes the system to read the entire flat directory
of a family and build a new file access structure for that family in the catalog
directory called either SYSTEM/CATALOG/nnn or SYSTEM/ACCESS/nnn. For more
information about the flat directory and file access structure, refer to the System
Administration Guide.
Syntax
Explanation
RB & ERASE
Erases bad records from the directory and rebuilds the access structure for the
directory.
RB ON <family name>
Builds a new access structure for the flat directoryand for the catalog if the
installation is running with the CATALOGING operating system option enabled.
Note: While the access structure is being rebuilt, the family appears to be offline to
programs performing file residency checks using the RESIDENT file attribute or
GETSTATUS directory requests. Even though the RB command does not require a
pack to be closed, its use can cause unpredictable program behavior if the process
has files open on the family.
RB ON TAPE
Builds a new key structure, the file access structure table (FAST), for cataloged tape
files. This form of the command can be used only on systems that are running with
the OP CATALOGING (OP + 23) option set.
RB ON VOLUME LIBRARY
Builds a new key structure, the volume access structure table (VAST), for the volume
library. This form of the command can be used only on systems that are running with
the OP CATALOGING (OP + 23) option set.
RB ON VOLUME DIRECTORY
Builds a new key structure for the volume directory. This form of the command is
useful for correcting a partly out-of-date or corrupted volume directory key
structure. This form of the command can be used only on systems that are running
with the security option TAPECHECK set to AUTOMATIC.
Example
RB ON PARTS
MSG
RC (Reconfigure Disk)
The RC (Reconfigure Disk) command purges all files and creates a new set of volume
labels on a disk pack or memory disk unit.
On systems with the Mirrored Disk Pooling Facility (MDPF) installed, the RC
command is also used to set or reset the free spare attribute on labels for disks
assigned to the spare disk pool. Use this command initially to establish the pool of
free spare disks, and thereafter to manually add disks to or delete disks from that
pool.
When using the RC command to reconfigure a disk, the following attributes are
inherited from the current values of that disk unless you specify new values in the
RC command:
CAPACITY
GAPS
NAME
OWNER
SIMPLE
SERIAL
VSS = VSS2
The following attributes are not inherited:
AREAS
BP
FAMILYINDEX
The following options are directions to the RC command and are not inherited or
stored as attributes on the disk:
DONTKEEP
KEEP
OLDNAME
The unit to be reconfigured must be ready or saved and must not have any files
open at the time the command is entered. If the RCBP system option is set and you
attempt to reconfigure a base pack of a multipack family, you must respond with OK
to the system message that appears to confirm the reconfiguration request.
If the command is rejected, wait for the current command to complete and enter the
command again.
Restrictions
You cannot use the RC command in the following instances:
You cannot use the RC command on a unit that has been reserved for
maintenance with a UR (Unit Reserve) command.
You cannot use the RC command for online mirrored packs. You must release
a pack that is part of a mirrored set with the MIRROR RELEASE command
before you can enter the RC command.
You cannot use the RC command to resize a disk that is a member of a
multivolume family.
Syntax
<oldname list>
<serial list>
Explanation
RC PK <unit number list>
RC DK <unit number list>
Purge the disk pack or memory disk units of all their files and create a new set of
volume labels.
If you do not specify either SPARE = ON or BP = <serial number>, the first or only
disk becomes the base pack of a new family with a new SYSTEMDIRECTORY. The row
size of the SYSTEMDIRECTORY is 4000 sectors if the disk is formatted in VSS2
mode; otherwise, the row size is determined by the SYSOPS SYSTEMDIRECTORY
option. Refer to the SYSOPS (System Options) command for more information.
AREAS = <number>
Specifies the number of AREAS that the system should allocate for the
SYSTEMDIRECTORY of the new disk family. The default value is 2. You can specify a
value from 2 to 1000. Do not specify AREAS for continuation packs (RC commands
that include the BP (BASEPACK) option).
By specifying a suitably large number for AREAS, you can avoid directory expansion
conflicts. If you specify a small value, then, as you add files to the family, the system
eventually has to expand the size of the SYSTEMDIRECTORY. But, when that time
comes, there might not be enough available space on the disk to expand the
directory. This can lead to delays while the operator tries to make space available
on the disk. To use the AREAS option to its best advantage, you need to anticipate
how much directory space the family needs in the long run, based on the number of
files you put on the family and the size of their disk file headers.
Note: After you have established a disk family with the RC command, you can use
the DU SYSTEMDIRECTORY command to monitor the space usage in the
SYSTEMDIRECTORY for the family. You can use the EXPAND, SQUASH
SYSTEMDIRECTORY, and NEW SYSTEMDIRECTORY commands to change the size of
the SYSTEMDIRECTORY for the family. You can use the SQUASH SYSTEMDIRECTORY
command to reduce the number of AREAS in an active SYSTEMDIRECTORY to the
minimum size required. You can use the NEW SYSTEMDIRECTORY command to
reduce or expand the number of AREAS and the AREASECTORS of the
SYSTEMDIRECTORY for the disk family. You can use the EXPAND command to
expand the number of AREAS of the SYSTEMDIRECTORY for the disk family.
BP <serial number>
Makes the disks specified in the <unit number list> continuation packs of the base
pack with the specified serial number. The serial number is an integer in the range 1
through 999999. The base pack specified must be online. Use the NAME option in the
command and give the continuation pack the same family name as the base pack.
If the family already includes a pack with the same serial number, the following
message appears:
CAPACITY <integer> MB
CAPACITY <integer> GB
CAPACITY LIKE PK <unit number>
CAPACITY FULL
Note: You can resize any modern SCSI or Fibre Channel disk. You cannot resize old
SCSI disks appearing in the OL display as SCSI/419, SCSI/805, SCSI/1545, or
SCSI/3019.
For supported system models and disk models, change the disk capacity to the
specified size, where
If you use the CAPACITY option on a system that does not support this feature,
the following message is displayed:
INVALID MACHINE TYPE
If you use the CAPACITY option for a disk unit that does not support this feature,
the following message is displayed:
INVALID DISK TYPE
GAPS = TRUE
GAPS = FALSE
You can only use the GAPS parameter for VSS1 disk volumes.
If you specify GAPS = TRUE, the system allocates AREAS for files on the disk with
gaps between those AREAS. By separating the AREAS of various files from each
other, you ensure that writes to one file do not involve writes to another, unrelated
file. This insulates the unrelated file or files from hardware failures that might take
place. For each individual AREA the system allocates, it chooses a gap size so that
two different AREAS from the same file or different files never share parts of the
same physical 512-byte sector. The system leaves a gap between any two AREAS of
3, 2, 1, or 0 180-byte logical sectors, depending upon the exact ending address of
the first AREA. The average size of an inter-area gap is slightly less than two 180-
byte logical sectors.
A disk family can have a mixture of disks with GAPS = TRUE and disks with GAPS =
FALSE.
When you use the GAPS = TRUE option, the system marks the label of the disk with
a special identifier so that only 48.1 and later systems can use the disk. This
prevents old systems from violating the AREA separation rule.
If you do not specify GAPS, the RC process inherits the current value of GAPS for the
disk. You can check the old value with the OL PK<unit number> system command.
If you specify GAPS = FALSE, the system allocates AREAS for files contiguously.
FAMILYINDEX = <number>
FAMILYINDEX = <number> KEEP
FAMILYINDEX = <number> DONTKEEP
FAMILYINDEX is not a valid option when the <unit number list> specifies more than
one unit.
In combination with the NAME and BP options, this option adds a new member to the
named family or replaces an existing member in the named family. The value of
<number> must be in the range 1 through 255. This command places the new pack
in the family with the family index of <number>.
If there is no member in the family with a matching family index number, the RC
process simply adds the target disk volume to the family that gives the target disk
volume a specified family index number. In this case, the RC process ignores any
KEEP or DONTKEEP option that you might have specified in the RC system command.
If there is a member in the family with a matching family index number, the RC
process attempts to delete that member and replace it with the new target volume.
In this case, if you did not specify the options KEEP or DONTKEEP, the RC process
issues the following ACCEPT message:
PK<unit number> REPLACING CONTINUATION PACK; REPLY 'AX KEEP' OR 'AX DONTKEEP'
The RC process examines the family directory and performs the following steps:
Removes code files and certain other special files (such as BOOTCODE,
CANDE recovery files, and CANDE schedule files) that reference the replaced
pack.
Removes BADDISK files on the replaced pack.
Removes a JOBDESC file residing anywhere on the family.
If DONTKEEP is specified, removes all other files that refer to the replaced
pack. If KEEP is specified, any areas that refer to the replaced pack are
marked deleted. An I/O error occurs whenever a program tries to read from
or write to these areas.
If you specify a FAMILYINDEX greater than 1 in the absence of the BP option, the
system displays the following message:
If the given family index corresponds to a current backup pack (a member with a
directory on it), the following error message appears:
FAMILYINDEX REQUIRES DD -
If the family is the active DL JOBS family, the following error message appears:
When this option is used in conjunction with the SPARE OFF option and your system
has the Mirrored Disk Pooling Facility (MDPF) installed, the following system message
appears:
PK <unit number> RC'ED AND REMOVED FROM THE SPARE DISK POOL.
When this option is used without the SPARE OFF option and the disk is assigned to
the spare disk pool, the following RSVP message appears:
If you respond OK, the designated family name is assigned to the pack, a system
message states that the disk is no longer a free spare disk in the spare disk pool,
and a status change message is issued. The status change message is defined in the
MCP System Interfaces Programming Reference Manual. The system message is
PK <unit number> RC'ED AND REMOVED FROM THE SPARE DISK POOL.
If you respond DS, the command is rejected and the following message states that
the pack remains a free spare disk in the spare disk pool:
If your system does not have MDPF installed, the following RSVP message appears:
If you respond OK, the designated family name is assigned to the pack, the pack is
removed from the spare disk pool, and the following system message appears:
PK <unit number> UNIT RC'ED AND REMOVED FROM THE SPARE DISK POOL.
If you respond DS, the command is rejected and the system message states that the
pack remains a free spare disk in the spare disk pool.
When a disk previously assigned to the spare disk pool has been moved to a system
that does not support MDPF, it is not recognized as a free spare disk. The free spare
attribute is cleared from the pack label with no operator notification.
OWNER = <name>
Specifies the owner identification to be assigned. The name must be from 1 to 14
characters long. If the name contains special characters or blanks, you must enclose
it in quotation marks (""). If OWNER is not specified, and either the owner field in the
old disk pack label is blank or the pack is new, the system fills the field with blanks.
If the disk pack has a non-blank owner identification, the system displays a
message, and you must verify the request by entering the <mix number> OK
command.
To remove the owner identification, reconfigure or relabel the disk pack with the
following null string:
OWNER=""
SIMPLE = TRUE
SIMPLE = FALSE
SIMPLE is not a valid option when the <unit number list> specifies more than one
unit.
If you specify SIMPLE = TRUE, the system creates a single disk family and gives the
SYSTEMDIRECTORY an AREALENGTH of 300 sectors. The system ignores the SYSOPS
SYSTEMDIRECTORY <rowsize> value for the SIMPLE case.
To reconfigure a simple disk and change it to a normal disk, use SIMPLE = FALSE in
the RC command.
You cannot use the RC PK <unit number> BP <serial no> command to add
continuation packs to a simple disk family. You cannot use the DD command to
duplicate the SYSTEMDIRECTORY of a simple disk family. You cannot use the
MIRROR CREATE command to create a mirror copy of a simple disk.
The system does not add AREAS to the SYSTEMDIRECTORY when the first disk of the
directory fills up. This means that you can store a maximum of 120 disk files on a
simple disk. You cannot store a file with more than approximately 2000 AREAS on a
simple disk.
SPARE ON
SPARE OFF
Valid only for systems with the Mirrored Disk Pooling Facility (MDPF) installed.
Assigns or removes a disk pack from the spare disk pool. This pool contains two
classes of spare disks: in-use spares (on-line members of a mirrored set) and free
spares (available for assignment to a mirrored set). A free spare disk can be used to
replace a failed disk in a mirrored set defined with MDPF. For more information about
MDPF, refer to the System Operations Guide.
Note: Use the MIRROR (Mirror Disk) command to designate a disk as in-use spare.
The SPARE ON option assigns a disk to the spare disk pool by setting the free spare
attribute in the label of the specified pack. You cannot use the NAME = option with
the SPARE ON option because disks in the spare disk pool are not permitted to have
a family name assigned to them. If both options appear in the same command, the
command is rejected with the system message
The following system message is displayed if the disk is successfully added to the
spare disk pool:
PK <unit number> UNIT RC'ED AND ENTERED IN THE SPARE DISK POOL
A status change message is issued if the free spare attribute of the disk was not
already set. The status change message is defined in the MCP System Interfaces
Programming Reference Manual.
If the free spare attribute of the disk was already set, no status change message is
issued and the following system message appears:
The SPARE OFF option releases the disk from the spare disk pool by resetting the
free spare attribute. You can use the NAME = option with the SPARE OFF option to
simultaneously release the disk from the spare disk pool and assign it to the
designated family. The following system message is displayed if the disk is
successfully removed from the spare disk pool:
PK <unit number> RC'ED AND REMOVED FROM THE SPARE DISK POOL
If the free spare attribute of the disk was not set, the SPARE OFF option is ignored
and the RC command is completed as requested. The following system message
appears:
A status change message is issued if the free spare attribute of the disk is removed.
The status change message is defined in the MCP System Interfaces Programming
Reference Manual.
If your system does not have MDPF installed, the command is rejected and the
following message appears:
<mix #> PK<unit> REQUEST REJECTED: THE REQUIRED FEATURE KEY IS NOT INSTALLED
VSS = VSS2
Configures a 180-byte disk with a VSS-2 format directory. This option makes it
possible to configure a 180-byte disk as the base member or continuation member of
a family using a VSS-2 format directory and VSS-2 allocation algorithms. (You can
revert the directory format for a 180-byte disk to the native format by omitting the
VSS = VSS2 modifier from the RC command.) This format ensures that if the disk is
mirrored or replaced by a 512-byte disk, the performance of the mirror or
replacement disk will be optimized.
If the VSS = VSS2 clause is present on an RC request to a VSS-1 disk, the request is
rejected and the following message displayed:
THIS DISK MUST BE INITIALIZED TO THE VSS-2 FORMAT BEFORE IT CAN BE RCED AS VSS-
2.
When a Reconfigure (RC) is requested for a 180-byte disk with VSS-2 characteristics,
the directory format defaults to standard 180-byte format unless the VSS=VSS-2
option is entered as part of the RC command or SYSOPS SYSTEMDIRECTORY = 4000
is in effect.
For further information about the VSS-2 format, refer to either the INITIALIZE
(Initialize Disk) command or the Peripherals Information File on the Product
Documentation CD-ROM.
Examples
Example 1
The following RC command reconfigures the pack identified by the unit number 066
and sets the options NAME and OWNER:
If the disk already has a name, the system displays a message and creates a waiting
entry.
Example 2
This example assigns PK 3104 the same capacity as PK 1372, removes the data files,
and assigns a new family name:
Example 3
This example assigns PK 3104 the same capacity as PK 1372, removes the data files,
and retains the old family name:
Example 4
This example changes the capacity of PK 3104 to be 4 gigabytes, removes the data
files, and assigns a new family name:
Example 5
This example initializes the disk on unit 80 in the VSS1 format and makes it a base
pack with the family name DATAPACK and the serial number 808080.:
Example 6
This example creates a new six-pack family with the family name TEST. The pack on
unit 100 becomes the base pack. The packs on units 200 through 204 become
continuation packs #2 through #6, respectively. The RC process gives the pack on
unit 100 the serial number 555100, the pack on unit 201 the serial number 555201,
and the pack on unit 202 the serial number 555202. The disks on the other units
(200, 203, and 204) retain their original serial numbers.
The OLDNAME list of XPACK and TEST cause RC to check each of the six packs to
make sure that their original family names match one of those two names. If there is
a mismatch, the RC process stops at the mismatching unit and does not reconfigure
that unit or any of the remaining units.
Example 7
This example adds five continuation packs to the existing disk family with the family
name TEST. Because the OLDNAME option was not used, the operator must reply
<mix number> AX OLDNAME = <family name> for each of the five disks that
already have family names. The operator does not have to reply for disks that do not
already have family names, such as disks that have been purged (they have the
pseudoname SCRATCH).
Example 8
This example creates four spare disks, PK80, PK 81, PK836, and PK837, if either of
the following circumstances exists:
Previously, the disks did not have names (they were purged SCRATCH disks).
The disks were either named TEST or DATA.
RC PK 80-81, 836-837 SPARE = ON OLDNAME = (TEST,DATA)
BADDISK Files
The RC command attempts to put any old BADDISK files created by RES (Reserve),
XD (Bad Disk), or RC (Reconfigure Disk) commands into the directory for the new
family of the pack. If the pack is the base pack, the information goes into the
directory of the base pack. If the pack is a continuation pack, the information goes
into the directory of the base pack to which the continuation pack is directed.
Generally, you can display the status of these files by entering the following
command syntax:
BADDISK files created by the RC command can be removed only by the PG (Purge)
command. The PG command purges all files on the pack, including BADDISK files.
A user group from the loaded configuration file might contain certain actions to be
performed as part of the initial halt/load of the group.
If you specify either the MINIMAL group or the DEFAULT group, after the initial
halt/load, a partition begins running on either the MINIMALNAME group or the
DEFAULTNAME group. From then on, these groups behave just like any user-defined
group.
Unless you specify the NOW option, tasks become scheduled while the
reconfiguration process waits for a null mix.
Syntax
<group ID>
The name assigned to a group.
Note: The name that you provide for a group ID must match a name listed in the
configuration file. You assign such names by defining those names in a configuration
symbol file, compiling the file with the SYSTEM/CONFIGURATION utility, and then
linking the compiled file with the CF (Configuration File) command.
Explanation
RECONFIGURE GROUP AS <group ID>
RECONFIGURE GROUP AS DEFAULT
RECONFIGURE GROUP AS MINIMAL
Reconfigure all resources assigned to the group associated with the ODT at which the
command was entered. The new configuration can be specified with a <group ID> or
the DEFAULT or MINIMAL designations. You must be sure that the resources
requested for your partition by the new group are not in use by another partition,
except where sharing of disks is explicitly desired.
If DEFAULT is designated, the system attempts to acquire all units and controls
specified by the Peripheral Configuration Diagram (PCD) list. After the initial
halt/load, use the FREE (Free Resource) command to remove devices from use in the
resulting DEFAULTNAME group.
The MINIMAL specification alters the system configuration so that only the halt/load
units that are specified by the SYCON Configure menu are valid. If the MINIMAL
specification is chosen, the system acquires only the halt/load units and the
necessary controls to communicate with those units. After the initial halt/load, use
the ACQUIRE (Acquire Resource) command to add other devices to be used to the
resulting MINIMALNAME group. For more information on halt/load units, refer to the
HLUNIT (Specify Halt/Load Unit) command.
NOW
NOW specifies that the group that initiated the reconfiguration is not to wait for a
null mix before reconfiguration.
On all systems, if NOW is not specified, RECONFIGURE waits for a null mix on the
reconfiguring partition before it completes the reconfiguration.
HALT
Specifies that the system stops immediately following the reconfiguration. The
SYCON program (except VM systems that use the Console for MCP) must then be
used to load the group and to specify any new path information or to acquire and
free resources. If the HALT option is not specified, the system automatically performs
a halt/load to the new group.
Examples
RECONFIGURE GROUP AS TWOBY
JOBDESC File
Job restarting might be affected by what happens to the JOBDESC file. Because the
JOBDESC file contains the information needed to restart jobs, whether and when a
job restarts is determined by the JOBDESC file being used by a group. The DL JOBS
specification contained in the configuration file can be used to determine the group
that uses a given JOBDESC file. Refer to the System Configuration Guide and to the
DL (Disk Location) command for information about the DL JOBS specification.
Suppose two one-processor groups each have a JOBDESC file. When they are joined
into a two-processor group, only one JOBDESC file is activated. The queued and
running jobs that are recorded in the selected JOBDESC file are either requeued,
restarted, or both requeued and restarted. If the JOBDESC file belonged to one of
the one-processor groups, the jobs from that group are restarted. The queued jobs
and running jobs described in the other JOBDESC file or files are not requeued or
restarted at this time. Their job summaries cannot be printed, and no DQ (Default
Queue), MQ (Make or Modify Queue), ML (Mix Limit), UQ (Unit Queue), ADM
(Automatic Display Mode), or TERM (Terminal) specification listed in that JOBDESC
file is propagated to the active JOBDESC.
When a two-processor system is split into two one-processor groups, each group has
its own JOBDESC file again and restarts any jobs that are described in that JOBDESC
file. If one of the groups is assigned to use the same JOBDESC file as the two-
processor group, all the jobs that were queued or running on the two-processor
group are requeued or restarted on that group.
Syntax
Examples
Depending on the condition of the IOM units and the settings of the switch and
options, the system response to the RECOVER command can be one of the following:
If any IOM units are marked as out of service when the RECOVER command is
issued, the system halts, the console performs corrective action on the out of service
units, and the system continues. This procedure might cause the system to be halted
for several minutes; therefore, it is recommended that you use the RECOVER
command during off-peak hours only. If no recovery phases are set on the console,
no corrective action is taken and the system remains halted.
If you reset the IOM Interrupt Halt switch in the SYCON environment, the system
defers recovery of failed IOM units until the RECOVER ODT command is issued. Since
the console requires operating system time to recover the failed units, you can use
this option to postpone the halt/continue system interruption to a more convenient
time.
The following table shows the four ways in which the system can respond to a failed
non-distinguished IOM unit, depending on the settings of the Interrupt Halt switch
and the diagnostic options.
IOM
Interrupt DO,DRP,
Halt DRI, DRD
Switch Options System Response When Any IOM Unit Fails
Set All reset 1. The system pauses automatically for the console
to perform state dumps and to perform console
corrective action.
2. The operating system takes MCP corrective action.
Set All set 1. The system pauses automatically for the console
to perform state dumps and to perform console
corrective action
2. The operating system does not take MCP
corrective action.
3. An operator must enter a UR command to bring
the failed unit or units back online.
Reset All reset 1. The system does not pause automatically. The
device state at the time of the error is lost.
2. The operating system takes MCP corrective action.
3. If this action is insufficient to recover the units,
the RECOVER command can be issued at a later
time to initiate a system pause to perform the
required console corrective action on the failed
units.
Reset DRP set; 1. The system does not pause automatically. The
either or device state at the time of the error is preserved
both DRI until either an operator enters a UR command to
and DRD bring the failed unit or units back online, or the
set RECOVER command is issued.
REMOTEDISK
The REMOTEDISK command allows you to mark disk units as remote disk units. You
can use this command to improve performance for a mirrored set that contains some
disk units that are near the system and other disk units that are farther away. Once
a member is marked as a remote disk, the system avoids sending read operations to
that disk, and sends the read operations to local disks instead.
The REMOTEDISK command can also be applied to non-mirrored disk units, but has
no effect on the performance of such units. If the remote disk later becomes a
member of a mirrored set, the system biases read operations away from that disk
unit.
Syntax
Explanation
REMOTEDISK PK <unit numbers>
Reports whether the specified disk units are local or remote units. If a specified unit
is a member of a mirrored set, this command displays the local or remote condition
for each member of the set.
Examples
Example 1
The following command marks disk unit 705 as a remote disk unit:
REMOTEDISK + PK 705
Example 2
The following command marks disk unit 710 as a local disk unit:
REMOTEDISK - PK 710
Syntax
Explanation
REMOTESPO
Displays a list of active REMOTESPO stations. The system marks a REMOTESPO
station as active when it receives a message from that station. Merely designating a
station as a REMOTESPO station does not activate it until that station confirms that it
is active.
When the maximum number of REMOTESPO stations permitted are active, the
display header contains the phrase AT LIMIT.
To authorize the station, use the REMOTESPO :OK form of the command.
REMOTESPO
Removes supervisory control from all active stations and terminates the REMOTESPO
independent runner.
REMOTESPO :OK
Displays a list of the stations authorized to become remote ODTs.
Examples
Example 1
In this example, the REMOTESPO command is used first to designate data comm
station M333 as an ODT station, and then used alone to confirm that the station has
been designated as an ODT station and has become active.
REMOTESPO M333
REMOTESPO
Example 2
In this example, the AT LIMIT phrase indicates that the maximum number of
REMOTESPO stations are active.
REMOTESPO
Syntax
Explanation
REPLACE PK <unit number> ONTO PK <unit number>
Transfers a bit-image copy of all data on the pack with the first unit number to the
pack with the second unit number.
Both the source and destination volumes must be reserved before a pack volume can
be replaced. These volumes can be reserved with the UR (Unit Reserved) command.
Before the pack volume is replaced, messages are displayed describing both the
source and destination volumes, and you are asked to indicate whether to proceed
by entering either an OK (Reactivate) or DS (Discontinue) command.
The data on the source pack volume are copied to the destination volume. At
intervals during the copy phase, messages show how much of the data was
transferred and how much was transferred successfully. Errors are not logged, but
bad areas are recorded in the SECTORSINERROR report file.
When copying is complete, the system analyzes the effect of any damage on files
stored on the source volume. Lists of damaged files are generated, and affected
areas are marked to prevent their use. This information is stored in the
DAMAGEDFILES and DAMAGEREPORT files.
The label information is transferred to the destination volume and the source volume
is marked unlabeled. The destination volume can then be brought online and used.
Examples
Example 1
In this example, the operator requests that the contents of pack 241 be copied onto
pack 240. Note that both packs must be reserved with a UR command before the
REPLACE is started. The system asks for confirmation before doing the replacement,
and the operator enters OK. During the replacement process, the system sends
periodic messages stating how much of the pack was read so far. When the replace
operation is completed, the operator restores the packs to the system with a UR
command and then uses a PER PK command to list the status of the packs on the
system. Pack 240 has inherited the label that was attached to pack 241 previously,
and pack 241 is unlabeled.
PER PK
CLOSE PK 240,241
UR PK 240,241
PK240 RESERVED
PK241 RESERVED
5231 OK
UR - PK 240,241
PK240 AVAILABLE
PK241 AVAILABLE
5232 PK241 [000000] PARTS1 NO VOL1
5233 FAMILY REBUILDING:PK240 PARTS1
5233 FAMILY REBUILDING(50%):PK240 PARTS1
PER PK
Example 2
This example shows the REPLACE command responses on systems that support the
Mirrored Disk Pooling Facility (MDPF) when the destination pack is assigned as a free
spare disk in the spare disk pool. Before the command begins copying data from the
source pack to the destination pack, it displays one of the following two messages:
If you respond OK, the command completes the replacement and removes the free
spare attribute on the destination pack. A status change message is issued if the free
spare attribute of a disk is removed. The status change message is defined in the
MCP System Interfaces Programming Reference Manual.
In the damage analysis phase, if REPLACEPACK terminates for any reason (such as a
halt/load), the source volume is still labeled and the destination volume is unlabeled.
Changes already made to the directoryareas locked out or marked destroyed
remain in effect. REPLACEPACK ignores DS (Discontinue) commands in the damage
analysis phase.
Three output files contain the results of the operation. These files are named
SECTORSINERROR, DAMAGEDFILES, and DAMAGEREPORT, and reside on the
halt/load family. Their FILEKIND attribute is set to DATA and their MAXRECSIZE
attribute is 15 words. These files can be processed by CANDE or used as input to
user-written programs. The files are named according to the following convention:
SECTORSINERROR File
This file lists regions that were not successfully copied. Each record describes a
region. A region is a contiguous set of sectors that all failed to copy for the same
reason. Possible reasons are as follows:
Included in the description is the physical result descriptor obtained while the system
attempted to transfer the first sector of the region. If no bad sectors are found, a
null SECTORSINERROR file is created. A SECTORSINERROR file might look like this:
REPLACE/TESTPK/FAMILYINDEX2/SECTORSINERROR ON HLDISK
... RD=0001E9E60581
SCAN/REPLACE ERROR @ ADDRESS: 34009 FOR 6 DESTINATION WRITE ...
... ERROR RD=0001E9EA0901
SCAN/REPLACE ERROR @ ADDRESS: 59067 FOR 1 SOURCE READ ERROR ...
... RD=0001E9E60581
Both the start sector and the number of sectors are in decimal characters.
DAMAGEDFILES File
This file contains a list of files for which one or more areas were not successfully
copied. The titles are separated by commas. The file can be used to make a WFL
deck containing a COPY, ADD, or REMOVE statement. If no bad sectors are found,
this file is not created. A DAMAGEDFILES file might look like this:
REPLACE/TESTPK/FAMILYINDEX2/DAMAGEDFILES ON HLDISK
(XYZ)SYMBOL/GREEN
,*TESTDB/PARTS/DATA
DAMAGEREPORT File
This file contains a more detailed description of the damage to those files for which
one or more areas were not successfully copied. For each file, the title and a list of
affected areas are included. If the file is a DMSII file (its FILEKIND is DBDATA), the
phrase DMS ROW LOCKOUT OF is included. If a JOBDESC file was affected, messages
describing the problem appear at the end of the DAMAGEREPORT file. If no bad
sectors are found, this file is not created.
REPLACE/TESTPK/FAMILYINDEX2/DAMAGEREPORT ON HLDISK
Directories
In general, the directories for a family must be available to REPLACEPACK when a
member of that family is the subject of a pack volume replacement operation.
Consider the following cases:
The volume contains the only directory for the family. In this case, the family
is already offline, and REPLACEPACK implicitly has access to the directory.
The volume does not contain a directory. In this case, the family must be
online; that is, the directory volumes must be online and the directory must
have been complemented. REPLACEPACK ensures that this is the case and
then locks the directory volumes online (by incrementing their open counts)
until the operation completes.
The volume contains one of several directories for the family, and the family
is not online. In this case, REPLACEPACK terminates if it cannot find all other
directories for the family. REPLACEPACK locks the other directory volumes
online and marks them in a way that prevents the family from coming online
(being complemented) until the pack volume replacement is completed.
The family is in a marked state if it was online when one of its directory
volumes was closed. A family is also left in this state if some of its directory
volumes are brought online, but at least one is left offline, and VERIFYFAMILY
is discontinued when it requests the offline volume.
The volume contains one of several directories for the family, and the family
is online. In this case, REPLACEPACK uses the online directories, just as if the
subject of the pack volume replacement did not have a directory. If any
damage is found, the directory timestamps in the online directories are
updated, making the directory on the destination volume obsolete.
The only way to get a family into this state is for you to respond OF to
VERIFYFAMILY when it requests the volume that is to be the subject of the
pack volume replacement. This action should be taken only as a last resort.
The suggested approach for dealing with multimember families is to close only the
volume that is to be the subject of the pack volume replacement. All other members
of the family that have directories should be left online.
Duplicate directories are referenced, if possible, when records in the directory on the
source volume are bad. Messages inform you that this replacement has occurred.
If there is no duplicate directory, then messages appear describing the problem, and
REPLACEPACK waits with the following RSVP:
general description of VSS disks, refer to the Peripherals Information File on the
Product Documentation CD-ROM.
Only those 180-byte disks that were configured with VSS = VSS2 can be replaced by
a
VSS-2 disk. The VSS = VSS2 option ensures that file areas are allocated properly for
optimal VSS-2 performance. This option is described in the topics INITIALIZE
(Initialize Disk) and RC (Reconfigure Disk).
The following chart shows the various combinations of disks, and indicates whether a
REPLACE command can copy the data from the source disk to the target disk.
Notes:
If you enter a REPLACE command with a VSS-1 disk or a 180-byte disk that lacks the
VSS = VSS2 option as the source, and a VSS-2 disk as the destination, the system
responds with the following message:
Additionally, you cannot replace a VSS-2 disk with a VSS-1 disk. And if a 180-byte
disk has the VSS = VSS2 attribute, you cannot replace the disk with a VSS-1 disk. If
you attempt either of these operations, the system displays the following message:
Syntax
Explanation
REPLACECARD automatically identifies all the ports connected to the same CSBUS as
the specified port (the one identified for replacement) and reserves those that are
not currently reserved. An RSVP message is posted to indicate that it is safe to
remove or insert the specified channel card or any other card attached to the same
CSBUS.
Caution
Before you remove or insert any channel cards, consult the appropriate channel
servicing guide for information about hardware requirements, ESD protection,
and the use of the LED indicator found on each card.
Examples
Example 1
This example aborts the reserving of port 18101.
Example 2
This example reserves port 18101 so that it can be replaced, and then makes port
18101 available again.
Example 3
This example reserves port 18111 so that it can be replaced, and then makes port
18111 available again.
RSVP: CSBUS FOR PORT 18111 IS THE LAST PATH TO THE FOLLOWING
IN-USE UNITS: PK100, PK101, PK102, PK103
RSVP->OK
CSBUS FOR PORT 18111 RESERVED
PORT 18111 CAN NOW BE REPLACED
RSVP: PORT 18111: REPLY OK AFTER REPLACING OR DS TO ABORT.
RSVP->OK
CSBUS FOR PORT 18111 AVAILABLE
If any of the ports affected by the command serve as the last path or paths to
all available ODTs, the command will be aborted.
If any of the ports affected by the command serve as the last path or paths to
any critical units, the command will be aborted.
Non-critical last path conditions are reported and you are given the
opportunity to abort the command. If the command is not aborted, units
affected by the path loss will be periodically displayed to indicate that I/O
PROCESSING STOPPED DUE TO LOSS OF LAST PATH. Several
READTHISMESSAGE RSVPs might also occur.
If you discontinue I/O processing on special purpose ports (such as ICPs that
provide network services), the services provided by those ports are
interrupted. Once the REPLACECARD command completes, I/O processing
continues and lost services can be automatically restarted when the host
resident portion of the service detects that the affected port is available
again. The REPLACECARD command does not provide special recovery of
these services. The net effect on the special ports is the same as if they were
manually reserved by using the UR command and then unreserved with the
UR command.
Ports that were reserved prior to the use of the REPLACECARD command
remain reserved. Previously OUT OF SERVICE ports can be made available
following the completion of the REPLACECARD command.
RES (Reserve)
The RES (Reserve) command enables an area of a disk to be cleared of all files and
the spaces marked as unusable.
Syntax
<reserve options>
<segment range>
The number value specifies the following range of sectors to be reserved: the
starting address number, the ending address number, and the length.
The hex number value specifies the range of the hex starting address and the hex
ending address sectors to be reserved in hexadecimal form.
If the request is directed to the base unit of an online family, a segment range must
be specified. You cannot reserve an entire base unit.
Explanation
RES DK <unit number> <reserve options>
RES PK <unit number> <reserve options>
Start an independent runner named RESERVEDISK that reserves the unit according
to the reserve options. If insufficient target disk area exists when a RES request
requiring copying is entered, then a message is displayed, and the RES action can be
terminated by the DS (Discontinue) command. A RES request cannot be directed to
the following:
COPY ERRORS
Enables copying to continue despite errors if a RES request causes a file to be copied
from the area to be reserved and I/O errors occur during copying. Code files,
however, are removed.
REMOVE
Automatically removes all files except BADDISK files and special system files such as
active directories, the active MCP code file, and the active JOBDESC file that occupy
any space in the area being reserved.
Caution
These files are not copied or saved; therefore, great care should be exercised in
the use of this option.
System files such as the MCP code file, the JOBDESC file, and so forth are moved if
encountered.
Active or queued WFL jobs can prevent job files from being successfully moved.
<reserve options>
The following table explains the reserve options.
Option Explanation
Option Explanation
AS DELETED Valid for continuation packs but not for base packs in a
family. The AS DELETED option causes all files to be moved
from the specified continuation pack to the other packs in the
same family. The reserve process marks the reserved disk as
a SCRATCH disk, and deletes the entry for that family index
from the list on the base pack. The next time you use an RC
(Reconfigure Disk) command to add a continuation pack to
the same family (with a base pack specification that omits a
FAMILYINDEX number), the system assigns the family index
of the deleted member to the reconfigured disk.
Segment range If the SEGMENT clause is present in the RES command, the
specified segment range is covered by a BADDISK file.
<segment range>
Specifies an area of disk to be covered by a BADDISK file. This parameter is required
when reserving the base unit of an online family.
The PHYSICAL option has meaning only for VSS disks. Refer to Considerations for
VSS Disks later in this topic.
If you specify SEGMENT <starting address number> FOR <length number>, the area
to be reserved begins at <starting address number> and is <length number>
sectors long.
If you use the command SEGMENT <starting address number> THRU <ending
address number>, the area to be reserved begins at <starting address number> and
ends at <ending address number>.
If you do not specify either FOR or THRU, the system assumes THRU 1. To specify
these numbers in hexadecimal form, use <hex starting address> or <hex ending
address>. SEGMENT and ADDRESS are synonyms. The starting address must be
greater than or equal to 28 (HEX 1C).
Example
This example removes an area from the tables of usable space for disk pack unit 96:
MSG
Note that all addresses in BADDISK file names are in hexadecimal format.
Command Result
Command Result
If the RES command uses the physical segment address, the system converts the
address into a range of logical segment addresses before processing the command.
The range of logical segment addresses starts with the first logical segment address
that is located within the first physical segment address to be reserved, through the
last logical segment address located within the last physical segment address to be
reserved.
Thus, any BADDISK files created by the RES command have boundaries
corresponding to logical segments, regardless of whether the PHYSICAL option was
used.
The following examples illustrate the effects of logical or physical segments specified
in the RES command.
Note: For the sake of simplicity, the following examples reference segments at the
start of the disk. Actually, segments 0 through 27 are the label area and cannot be
reserved. Nonetheless, the concepts illustrated by these examples are valid.
In this case, the system creates a BADDISK file that reserves logical segments 0
through 3. The BADDISK file name is BADDISK/FMLYINX1/UNIT96/AD0H.
Because two BADDISK files can not reserve the same logical segment, the system
alters the BADDISK file from example 1 so that it no longer reserves logical
segments 2 and 3. The file reserves only logical segments 0 and 1. The BADDISK file
name remains unchanged: (BADDISK/FMLYINX1/UNIT96/AD0H).
At the conclusion of this example, two BADDISK files exist. The file names and
segments reserved by each file are as follows:
This action reserves a little more than physical segment 1. The part of logical
segment 2 that overlaps with physical segment 0 is also reserved, as is the part of
logical segment 5 that overlaps with physical segment 2.
Suppose that the BADDISK file from example 3 already exists, and you enter the
following command:
As you can see from the following figure, physical segment 2 maps to logical
segments 5, 6, 7, and 8:
Note, however, that the BADDISK file created by example 3 also reserved logical
segment 5. Because two BADDISK files can not reserve the same logical segment,
the system alters the BADDISK file from example 3 so that the file no longer
reserves logical segment 5. The file reserves only logical segments 2, 3, and 4. The
BADDISK file name remains unchanged (BADDISK/FMLYINX1/UNIT96/AD2H).
Syntax
Explanation
Each mix number included in the command must be for a valid active job that is not
in the process of being restarted. All jobs included in the RESTART command are
terminated and then requeued as ready for job selection. When they are selected,
the jobs restart in accordance with WFL capabilities. Refer to information about
restart capabilities in the Task Management Programming Guide.
If a mix number is not the number of a valid active job, the following message is
displayed:
INVALID NUMBER
If the job has already been restarted, the following message is displayed:
IMPROPER STATE
Examples
Example 1
The following example restarts the specified jobs:
8964,7700 RESTART
Example 2
The following example restarts all the jobs within the specified range of mix
numbers.
If you enter the RESTART command when tasks are running that have the
discontinued program option set, those tasks take program dumps. If a job starts a
task that applies transactions to a database, and you restart the job, the
transactions might be reapplied to the database.
The COMMAND option enables the security administrator to set or reset security
restrictions on system commands. Restricting the use of certain commands can help
to prevent changes to the system configuration. Command restrictions are in effect
only when security administrator status is authorized by the ??SECAD (Security
Administrator Authorization) command.
Users or programs must have security administrator privileges if they want to use
more than the inquiry forms of the RESTRICT command.
Syntax
<file list>
Explanation
RESTRICT MT <unit number list>
Marks the specified tape units as restricted. The RESTRICT MT <unit number list>
command removes the restrictions from the units.
RESTRICT COMMAND
Displays a list of the restricted commands.
ACCOUNTING DL MOVE SF
AD DN MQ SHARE
AI DQ MP SI
AR DR NET SQUASH
ASD GC OP SUPPRESSWARNING
BNAVERSION HN PQ TERM
CM HS RB TL
COMPILERTARGET ID RECONFIGURE TR
GROUP
COPYCAT IK RES UQ
CS LC RP XD
ACCOUNTING DL MOVE SF
DD MAX SB
DF MDT SBP
DL ML SEGARRAYSTART
Note: For specific restrictions associated with the IK system command, refer to the
Security Administration Guide.
Note: Because <option> can be any valid reserved word, an invalid combination of
words is not rejected. For example, DL CM is accepted but does not cause any
command to be restricted.
restrict a data file causes an error message to be displayed. The RESTRICT FILE
<file list> command removes the restrictions from the files.
The maximum number of ODTs that can be restricted is 15. An attempt to restrict
more than 15 ODTs produces the following error message:
The security key specification is invalid with the RESTRICT SC <unit number list>
form of the command. The security key option enables you to remove the restriction
from the ODT later with the primitive command ??RESTRICT as long as you know the
security key. If you do not specify security key information in the RESTRICT
command, you must have privileged system access (or access to an unrestricted
ODT) to remove the restriction.
Examples
Example 1
The following are examples of how security-related restrictions on peripherals, tape
volumes, or files can be set or reset through the RESTRICT command.
Command Action
RESTRICT MT 113, Marks tape unit 113 and packs 208 through 211 as
PK 208-211 unrestricted.
RESTRICT VOLUME Marks the volume directory entry for the tape volume
123456 with the serial number 123456 as restricted.
Example 2
The following examples show how security-related restrictions on an ODT can be set
or reset through the RESTRICT SC <unit number list> command.
Command Action
Example 3
The following examples show how security-related restrictions on a command can be
set or reset through the RESTRICT COMMAND <command> <option> command.
Command Action
RESTRICT COMMAND MAX Restricts the use of all options of the MAX
command.
Example 4
Suppose a family consists of two packs numbered 61 and 62, both unrestricted. The
command RESTRICT PK 61 causes pack 61 to be marked as restricted and pack 62
to be treated as restricted even though it is not so marked. The command RESTRICT
PK 61, which removes the restriction on pack 61, also stops the restricted
treatment of pack 62. By contrast, if both packs had been marked as restricted, the
command RESTRICT PK 61-62 would have been needed to remove the
restrictions from the family.
Restricting Commands
The RESTRICT COMMAND enables the site to specify that some system commands
can be used only by a Security Administrator.
Only the Security Administrator can use the RESTRICT COMMAND system command.
When security administrator status is enabled on the system, some commands, for
example the SL (Support Library) command, are automatically restricted.
either the source or destination are changed while copying is in progress. These
restrictions should not be changed during copying of any file that might be affected.
A nondata file to which access is restricted can be copied on the local system by a
security administrator or, if security administrator status is not authorized, by a
privileged user.
If access to a unit is restricted, access to any volume mounted on the unit is also
restricted. If a volume is restricted, access to all files on that volume is also
restricted. Access to a file is unrestricted only if access to the unit and volume where
it resides, as well as to the file itself, is unrestricted. Removing the restriction from a
file on a restricted unit without also removing the restriction from the unit results in
a warning that access to the file remains restricted.
When library maintenance copies a file from one volume to another, the access
restriction imposed on the copy depends on the access restrictions at the source and
at the destination. Copying a restricted file to any unit produces a restricted file.
Copying an unrestricted file from a restricted unit to an unrestricted one produces a
restricted copy. Copying an unrestricted file from an unrestricted volume on an
unrestricted unit produces an unrestricted file, unless the destination volume or unit
is restricted, in which case the copy is restricted.
Restricting an ODT
The command to restrict an ODT can be entered at that ODT, at any other ODT, at
any terminal that has privileged system access through MARC, or by a privileged
user.
You can restrict an ODT is scratch, labeled, or saved. You can restrict an ODT that is
the target of the PS (Print System) ASSOCIATE or UQ (Unit Queue) command. You
cannot restrict an ODT if it is reserved, freed, or assigned to a file. However, you can
reserve a restricted ODT with a UR (Unit Reserved) command or a FREE (Free
Resource) command if the ODT is not in use; its restricted status is preserved.
You can remove the restriction from an ODT by entering ??RESTRICT <key> or, if
you have privileged system access, from a MARC session by entering RESTRICT
SC <unit number list>.
Syntax
Explanation
RF <device type> <unit number list>
Displays the reliability factor of the devices in the unit number list.
Examples
Example 1
This example displays the reliability factor for tape drive 144:
RF MT 144
Example 2
This example displays the reliability factor for CTL 10013:
RF CTL 10013
Example 3
This example displays the reliability factor for port 1120:
RF PORT 1120
RM (Remove)
The RM (Remove) command removes, in response to the RSVP message DUPLICATE
FILE, the disk file specified in the message and retains the new file.
Syntax
Explanation
<mix number> RM
Removes the duplicate disk file identified by the mix number and retains the new
one.
Note: DUPLICATE FILE messages are displayed only when the MCP run-time option
AUTORM is reset.
Example
In this example, the W (Waiting Mix Entries) command displays a DUPLICATE FILE
message showing that the disk file called AE5/1 is a duplicate. The RM command
removes the original file and retains the new one.
2577 RM
RP (Resident Program)
The RP (Resident Program) command displays a list of resident programs or marks a
code file as resident.
Syntax
Explanation
The resident program designation improves the performance of a program that is run
repeatedly. After a resident program has been run once, the segment dictionary
stack for its code file remains in memory, even when no tasks are using this stack.
Declaring a program as resident increases the amount of memory used in the system
when no tasks are using the program; on the other hand, doing so decreases
processor and I/O time when the program is reused.
RP
Lists the file titles of all resident programs currently in memory.
RP <file title>
Marks the code file with the specified file title as a resident program.
RP <file title>
Cancels the resident status of the code file with the specified file title.
Examples
Example 1
This example lists the file titles of all resident programs currently in memory. The
number in parentheses indicates the number of tasks running that program.
RP
Example 2
This example marks the file SYSTEM/ALGOL as a resident program.
RP SYSTEM/ALGOL
Example 3
This example releases the file SYSTEM/DCALGOL from being a resident program.
RP - SYSTEM/DCALGOL
Example 4
This example attempts to mark the file SYSTEM/ALGOL as a resident program, but
the file is not a code file.
RP SYMBOL/ALGOL
WRONG FILEKIND
Example 5
This example attempts to mark the file OBJECT/MISSINGFILE as a resident program,
but the system could not find the file.
RP OBJECT/MISSINGFILE
The RSS system must be active for some of these commands to be processed. The
RSS system is automatically initiated after a halt/load, if an RSS section appears in
the system configuration file. The current version of the host TCP/IP software must
be running. If the RSS system is inactive, the CONFIG, QUIT, and TRACE options are
not processed.
Syntax
<K value>
A number in the range 1 to 255.
<Boolean>
A Boolean value: TRUE, FALSE, YES, or NO.
Explanation
RSS CONFIG
Displays information about the RSS configuration at the local host.
RSS QUIT
Causes the RSSUPPORT library to begin a thaw and termination sequence. If no
users are linked to the library, RSSUPPORT terminates. If users are linked, new users
are prevented from linking, but the library does not terminate until the currently
linked users have delinked. If library termination does not happen as quickly as you
like, you can discontinue the user programs with DS (Discontinue) commands.
The RSS QUIT NOW command cannot be processed if you have already entered RSS
QUIT.
RSS RESTART
If RSS is not active, initiates the RSS system at the local host. The current version of
the host TCP/IP software must be running.
If RSS is already active, displays a message asking the operator to confirm that a
quit/restart sequence is wanted. If the response is No, then the RSS RESTART
command is ignored. If the response is Yes, then the system performs an RSS QUIT
action, followed by an RSS RESTART action.
If RSS is active, then the system immediately performs an RSS QUIT action, followed
by an RSS restart action. The system does not ask for operator confirmation before
performing these actions.
RSS USERDATA
Displays the current status of CSP Userdata services. CSP Userdata provides the
capability to synchronize the contents of the USERDATAFILE between multiple nexus
connected through the Reliable Session Service (RSS). For further information about
CSP Userdata, refer to the Continuous Service Platform (CSP) Installation and
Operations Guide.
To enable all inquiries to be performed on the local nexus, you must set the K
parameter to a value at least as large as the maximum number of nexus that
participate in the CSP Userdata service group.
This parameter has no effect until the CSP Userdata service group is reestablished.
Examples
Example 1
This example shows the format of the response to RSS CONFIG on a system on
which RSS is active.
RSS CONFIG
LOCAL NEXUS
The local host name and its number within the plexus. Within RSS, a nexus is a
host system running the RSS software. A nexus name is always the same as the
host name of the system.
PLEXUS CONFIGURATION
A list of every host declared to RSS, including the local host, the nexus number of
each, and an indication of the current state of each nexus. Possible nexus states
include the following.
As a nexus enters the plexus, the state changes from OUT to JOINING to IN. As a
nexus leaves the plexus, the state changes from IN to LEAVING to OUT. The
JOINING and LEAVING states are usually of brief duration.
FILE DIRECTORY
The directory under which RSS files are created.
CURRENT TRACE/FILE
The name of the trace file currently being maintained by RSS on this host.
NEXUS TIMEOUT
A user-specified value, used by RSS and the underlying network provider to
determine the minimum time to wait before deciding that a non-communicating
remote nexus is no longer in the plexus. The range of values is 2 to 1440
minutes.
Due to the nature of the two network provider-based timers used internally, the
actual time to detect a non-communicating nexus generally exceeds the NEXUS
TIMEOUT value. The first timer, the dialog check interval, is reset every minute,
as long as any activity has occurred within that minute. The second timer, the
blocked timeout, runs for the NEXUS TIMEOUT period, minus one minute. This
timer begins only when no activity has occurred during the dialog check timer's
one minute interval. Following are two situations that can cause detection of a
non-communicating nexus to be delayed for longer than the NEXUS TIMEOUT
period:
Activity ceases during the current one-minute interval. In this case, the
remainder of that minute, and the next, must elapse before the blocked
timeout timer is initiated. This can extend the effective timeout period by up
to one minute.
A remote nexus has ceased activity without acknowledging a transmission
from the local nexus. In this case, the network provider retries the
transmission every few seconds, for 15 minutes. Because these retries count
as activity on the connection, the blocked timeout timer is not invoked.
Example 2
If you enter the RSS USERDATA command, and CSP Userdata is not active, the
following response might be given:
RSS USERDATA
RSS USERDATA
RW (Rewind)
The RW (Rewind) command rewinds and unloads tape units, and unloads CD-ROM
drives.
UNIT IN USE
Syntax
Explanation
RW CD <unit number list>
You can use the RW CD <unit number list> command to unload CD-ROM drives.
Notes:
The RW CD <unit number list> command only works with CD-ROM drives
connected via SCSI channels. It does not work for CD-ROM drives connected
via SCSI DLPs.
You cannot execute the RW CD <unit number list> command when the CD-
ROM drive is in use.
RW MT <unit number list>
The RW MT <unit number list> command rewinds and unloads tape units in the unit
number list.
Note: For tape devices that cannot unload their media, the drive is left in an
unloaded state and must be reloaded in order for the MCP to attempt to read the
label of the tape. The drive can be logically loaded with an RY (Ready) command,
for example. Or it can be physically loaded by placing the media in the drive
manually.
Example
RW MT114
RY (Ready)
The RY (Ready) command makes devices ready for system use if they were made
inaccessible by an SV (Save) or CLOSE (Close Pack) command, or were locked by a
program or by an SNL (Serial Number Lock) or a PGL (Purge and Lock) command.
The RY command puts modules into use. This operation requires a time period of
from 1 to 7 minutes during which the system is not available. The ODT updates the
system status during this period so that the modules can be used. You must respond
to an RSVP message before this command can take effect.
Note: CPM and IOM are only allowed on IOM systems. IOP is only allowed on IOP
systems.
Syntax
<MSM specification>
<MSU specification>
<QUAD specification>
Explanation
READY <device type> <unit number list>
Readies the device for use. The unit number can be an integer from 1 through
32767.
Examples
Example 1
This example readies a tape unit:
RY MT 113
Example 2
This example readies an MSM and an MSU:
RY MSM 0, MSU 1
Example 3
This example readies a Telephony Services Platform (TSP) unit:
RY TSP 200
TSP200 READY
VC Units
To ready all 26 voice channel (VC) units outboard of a voice interface module (VIM)
DLP, you need enter only the following command syntax:
TSP Units
You must explicitly ready each unit that makes up a Telephony Services Platform
(TSP). You can enter either a separate READY TSP <unit number> command for
each unit or explicitly list each unit in one command as follows:
Refer to the FS (Force Schedule) system command for information about starting
scheduled jobs.
Refer also to the FACTOR option in the SF (Set Factor) system command for
information about the rate at which tasks come out of the scheduled entries.
Syntax
<wild card>
<delim>
Use one of the following characters:
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters.
Character Description
You can include lowercase characters and space characters by prefixing the wild-card
string with LIT and enclosing the wild-card string in delimiters.
For example, if you enter the following syntax, the system returns entries that
contain the string "PACK":
S NAME =pack=
If you enter the following syntax, the system returns entries that contain the string
"pack":
Explanation
S
Displays any scheduled jobs or tasks that have not been suppressed by the
SUPPRESS (Suppress Display) command. The S command does not display jobs in
the job queues; the SQ (Show Queue) command serves that purpose.
S ALL
Displays all scheduled jobs or tasks, including any that were suppressed.
S QUEUE
SQ
Display scheduled WFL jobs or tasks originating from a job queue. This form of the
command does not show jobs still in the queue. To display jobs still in the queue,
use the SQ (Show Queue) command.
S USER <usercode>
Displays only scheduled jobs or tasks with the specified usercode.
Examples
Example 1
This example shows a typical response to the S command:
The heading line appears on the first page of the Scheduled Entries display and
before the Scheduled Entries in automatic display mode (ADM).
The Mix field shows the mix number of the scheduled job or task. The Pri field
contains the priority of the job or task. The Elapsed field shows the length of time
the task has been scheduled. The time is expressed in hours, minutes, and seconds.
The WordsReq field provides an estimate of the number of words required to initiate
the job. The suffix K indicates a multiplier of 1000.
The word JOB precedes each job name. The usercode of the originator appears
before the job or task name. Some tasks and jobs can have two usercodes shown for
the following reasons:
Tasks other than compiler tasks display with the following format:
Example 2
This example shows a response to the S command after an HS (Hold Schedule)
command has been entered:
The asterisk (*) in the first column designates the first time that this task has
appeared in this state on this ODT.
Example 3
This example shows a response to the S command after a CM (Change MCP)
command has been entered:
Example 4
This example shows a response to the S USER command with no usercode specified,
and assumes the same conditions as in Example 1:
S USER= ""
The display eliminates the entries with a specific usercode (NORM) but shows the
entry with no usercode.
SB (Substitute Backup)
The SB (Substitute Backup) command enables you to substitute one backup medium
for another. The SB specification affects only nondirect print files. The setting of the
LPBDONLY MCP option and the BACKUP bit of the OPTION attribute of a task can
affect the value of the BACKUPKIND file attribute before the SB substitution. For a
description of the BACKUPKIND and FAMILYNAME file attributes, refer to the File
Attributes Programming Reference Manual. For a description of the BACKUPFAMILY
and OPTION task attributes, refer to the Task Management Programming Guide.
Syntax
Setting Synonyms
DISK DK
PACK PK
TAPE MT
Explanation
SB
Displays the current backup settings.
SB TAPE = DLBACKUP
Makes the substitute backup medium for tape the family specified as the DLBACKUP
family. The DLBACKUP family is set with the DL (Disk Location) command. Thus, if
the conditions SB TAPE = DLBACKUP and DL BACKUP ON ALLBACKUP are TRUE, all
backup tape output is diverted to a disk family named ALLBACKUP.
SB DISK = PACK
Overrides all programmer selection of backup disk. This command sends all backup
disk files to the family named PACK. The result can be a better balance between disk
and disk pack channel use.
The SB command is not recursive. Thus, the following command diverts backup disk
to backup disk pack and diverts backup disk pack to backup disk in a simple
crossover:
SB DISK=PACK, PACK=DISK
Example
SB
SB
DISK = DISK
PACK = PACK
TAPE = TAPE
REDUNDANT SUBSTITUTION
Tasks that are running under WFL jobs have their BACKUPFAMILY task attribute set
to the family that was specified for the DLBACKUP family when the job began, unless
BACKUPFAMILY was specified in the job attribute list. For more information, refer to
the DL (Disk Location) system command.
Syntax
Explanation
SBP
Displays the current setting (in seconds) of the INTERVAL option, which is used to
change the system utilization time interval. The command also displays the current
setting of SLICERATE in slices per second.
The CPURATE can be displayed by the A (Active Mix Entries) and the ADM (Automatic
Display Mode) commands. For example if the SBP CPURATE is set to 15 seconds, the
operating system computes processor rates every 15 seconds. The displayed
processor rate is then the processor time used over the last 15 seconds shown as a
percentage of 15 seconds; a task that used 3 seconds of processor time in the last
15 seconds would have a CPURATE of 20 percent.
Example
SBP
You can use the U (Utilization) command to obtain current system utilization
statistics.
For the systems that support SLICERATE adjustment, the lower the slice ratethat
is, the fewer the number of process switches per second for a given prioritythe
better a compute-bound task can run. Up to a point, the higher the SLICERATE, the
better I/O-bound tasks can run. For a general mix, the slice rate should be in the
range of 30 to 90 slices per second. The most efficient tuning usually comes from
using a moderate SLICERATE and tiered job priorities, where compute-bound jobs
are relegated to relatively lower priorities, while I/O-bound jobs are given relatively
higher priorities. If you set the slice rate too low, you risk poor I/O service. If you set
the slice rate too high, you risk poor processor utilization, because the processor
must switch between stacks at a much higher rate, thereby making poorer use of
processor memory caching.
SC (System Configuration)
The SC (System Configuration) command displays the current system configuration.
Syntax
Explanation
SC
Displays all requestor IDs and MSMs or MEMs.
SC
In addition to the information displayed by an SC command, SC displays the status
of various system components and devices. On IOM systems, this includes the MSM
status and the device status of MLIs, bases, DLPs, and peripherals. On IOP systems,
this includes IP status and the device status of IOPs, ports, controls, and
peripherals.
Examples
Example 1
The following are portions of the SC- display for an MCPvm server:
SC-
PK 502
CTL 10403: PK1SCSI [0000] VIA PORT 10400
PK 501
CTL 10402: PK1SCSI [0000] VIA PORT 10400
PK 500
CTL 10401: PK1SCSI [0000] VIA PORT 10400
CD 51
CTL 10301: CD1SCSI [1.0C] VIA PORT 10300
CD 50
CTL 10201: CD1SCSI [LP12] VIA PORT 10200
NP 210
CTL 210: ICP1 [91010101] VIA PORT 10100
LP 20
CTL 10101: TP2 VIA PORT 10100
SC 1-2,(3-8),16
CTL 10001: CON1 VIA PORT 10000
Example 2
The following are portions of the SC display for an IOP system:
SC-
MEM STATUS:
UNIT SIZE STATE START ADDRESS
EXCLUSIVE-MEM-0 388 MWords UP 00000000
IP STATUS:
SUBPOD-1-0:
IP-1-0-0 STATE: UP
IP INFORMATION
IP-3-0-0 [ PL=100 FEATURES=0,02/04/2003]
IP RANGE REGISTERS:
LOW EMODE MEMORY LIMIT: 183FFFFF
PCI-BRIDGE-1-0
PCI-BUS-1-0-1
IOPS: 1,129
PCI-BUS-1-0-2
IOPS: 9
I/O CONFIGURATION:
IOP 1 (1-0-1-2): FC-1 [ERL=55.535,SLL=00.014]
FP 1,4'1': C4FT [ERL=01.101,SLL=00.014]
PORT 1001: SCSI [ERL=02.000,SLL=93.645, SCL=4,FEATURES=0,02/07/2003]
PORT 1003: SCSI [ERL=02.001,SLL=93.645, SCL=4,FEATURES=1,02/07/2003]
FP 2,4'0': CNA [ERL=55.535,SLL=00.014]
PORT 8001: ABI
IOP 129: NT
IOP 9 (1-0-2-2): FC-1 [ERL=55.535,SLL=00.014]
FP 1,4'1': C4FT [ERL=01.102,SLL=00.014]
PORT 90- 91: SCSI [ERL=02.000,SLL=93.645,SCL=4,FEATURES=0,02/07/2003]
IOP 129 (1-0-1-2,FP,2,4'0'): NT [ERL=55.535,SLL=00.014]
PORT 1290: ODT [ERL=01.201,SLL=00.006,SCL=0,FEATURES=0,02/06/2003]
MT 34
CTL 103: MT1SCSCI [ 7 M] VIA PORT 1003
PK 51
CTL 100: PK1SCSI [B603] VIA PORT 1001
PK 53
CTL 253: PK1SCSI [0657] VIA PORT 1001
PK 54
CTL 254: PK1SCSI [0609] VIA PORT 1001
SC 1,2,3,4,(5),(6),(7),(8),(9),(10),(11),(12),(13),(14),(15)
CTL 1291: CON3 VIA PORT 1290
PK 9000,9001,9002,9003,9004,9005,9006,9007,9008,9009,9010,9011
CTL 900: PK1EMC [5568] VIA PORT 90
CTL 902: PK1EMC [5568] VIA PORT 91
PK 9016,9017,9018,9019,9020,9021,9022,9023,9024,9025,9026,9027,9028
CTL 901: PK1EMC [5568] VIA PORT 90
CTL 903: PK1EMC [5568] VIA PORT 91
Example 3
The following are portions of the SC display for an NX5800 system:
SC-
MEMORY USAGE:
SYSTEM 136 Mwords
MEMORY DISK 8 Mwords
DISK CACHE 16 Mwords
TOTAL ONLINE 160 Mwords
MSM STATUS:
MSU QUAD SIZE QUADS ONLINE SAVED TO BE SAVED
MSM 0 0 16M 0-3 0-3 NONE NONE
1 16M 0-1 0-1 NONE NONE
MSM 1 0 16M 0-1 0-1 NONE NONE
1 16M 0-1 0-1 NONE NONE
MODULE STATUS:
SYSTEM MODULE DOMAIN STATE
0 IOM 0 [0] IN USE
0 CPM 4 [0] IN USE
0 CPM 6 [0] IN USE
0 MSM 0 [0] IN USE
1 IOM 1 [1] IN USE
1 CPM 5 [1] IN USE
1 CPM 7 [1] IN USE
1 MSM 1 [1] IN USE
CPM STATUS:
CPM 4-7: [ERL=01.009,SLL=71.504,SCL=0,FEATURES=5,01/07/1998]
I/O CONFIGURATION:
IOM 0:
TCU 0: <UNAVAILABLE>
TCU 1: <UNAVAILABLE>
IOU 0-1: [ERL=01.943,SLL=01.999,SCL=0,FEATURES=1,10/25/1997]
DTU 10000-10001: [ERL=01.943,SLL=01.999,SCL=0,FEATURES=0,10/25/1997]
PORT 22001-22002: [ERL=07.001,SLL=07.518,SCL=3,FEATURES=0,02/16/1996]
PORT 22033: <RESERVED>
.
IOM 1:
.
TCU 0: DIST [ERL=01.943,SLL=01.999,SCL=0,FEATURES=1,10/25/1997]
TCU 1: <UNAVAILABLE>
IOU 1: <RESERVED>
IOU 0: DIST [ERL=01.943,SLL=01.999,SCL=0,FEATURES=1,10/25/1997]
DTU 10100: [ERL=01.943,SLL=01.999,SCL=0,FEATURES=0,10/25/1997]
PORT 22101 [ERL=07.001,SLL=07.518,SCL=3,FEATURES=0,02/16/1996]
PORT 22102: <RESERVED>
.
.
.
Example 4
The following are portions of the SC display for a CS585 system:
SC-
MEM STATUS:
SIZE STATE START ADDRESS
EXCLUSIVE-MEM-0 388 MWords UP 00000000
EXCLUSIVE-MEM-1 1660 Mwords UP 20000000
IP STATUS:
SUBPOD-1-0:
IP-0-0-0 (UP,PL=40)
IP-0-0-1 (UP,PL=40)
IP-0-0-2 (UP, Java)
IP-0-0-3 (UP, Java)
IP EMULATION CODE:
[VERSION=01.0008,FEATURES=0,06/16/2004]
IP RANGE REGISTERS:
LOW EMODE MEMORY LIMIT: 183FFFFF
LOW NON-COHERENT BYTE MEMORY BASE: 18400000
LOW NON-COHERENT BYPE MEMORY LIMIT: 1FFFFFFF
HIGH EMODE MEMORY BASE: 20000000
HIGH EMODE MEMORY LIMIT: 87BFFFFF
Example 5
This example shows a portion of an SC display for an IOM system that is configured
with Telephony Services Platform (TSP) units:
SC-
MT 15,16,17
CTL 2077: MT1SCSI VIA 10001
SC 6, 7
CTL 2077: ODT1 VIA 10001
FR 29,30,31,(32),(33),34,(35)
CTL 2047: SCSIPK1 VIA 10001,20001
TSP 200,201
CTL 1001: TSPSCSI VIA 10000
TSP 202,203
Example 6
The following example shows a portion of an SC display for a Libra Model 680
system:
SC-
MEM STATUS:
SIZE STATE START ADDRESS
EXCLUSIVE-MEM-0 388 Mwords UP 00000000
EXCLUSIVE-MEM-1 1660 Mwords UP 20000000
IP STATUS:
SUBPOD-0-0:
IP-0-0-0 (UP, PL= 40)
IP-0-0-1 (UP, PL= 40)
IP-0-0-2 (UP, Java)
IP-0-0-3 (UP, Java)
IP EMULATION CODE:
[VERSION=01.0008,FEATURES=0,06/16/2005]
IP RANGE REGISTERS:
LOW EMODE MEMORY LIMIT: 183FFFFF
LOW NON-COHERENT BYTE MEMORY BASE: 18400000
LOW NON-COHERENT BYTE MEMORY LIMIT: 1FFFFFFF
HIGH EMODE MEMORY BASE: 20000000
HIGH EMODE MEMORY LIMIT: 87BFFFFF
Syntax
Explanation
SCAN
Starts a scan pack independent runner process that reads data from the volume on
the specified disk unit and produces a SECTORSINERROR report file. Damage
analysis is performed if read errors are found, and DAMAGEDFILES and
DAMAGEREPORT report files are generated. These report files are discussed in the
REPLACE (Replace Pack Volume) system command.
You must reserve the volume (unit) with a UR (Unit Reserved) command before you
can enter the SCAN command. The UR command requires that the volume be closed
(not in use). When SCAN is completed, you must enter a UR command to make the
volume available for use again.
Example
In this example, the operator inquires about the status of the packs on the system,
then closes and reserves two of them. It is then possible to scan either of the two
packs. In this case, the operator scans pack 241.
PER PK
CLOSE PK 240,241
UR PK 240,241
PK240 RESERVED
PK241 RESERVED
SCAN PK 241
On systems that do not have Secure Access Control Module software, the SECOPT
command can be used only for the following purposes:
Note: The terms paged and segmented are synonyms. However, paged is the
preferred term.
You can change the value of SEGARRAYSTART at any time. Any array row that the
system subsequently allocates becomes paged or not paged according to the new
value. If the size of the array row is greater than SEGARRAYSTART and the array row
has not been marked as LONG or DIRECT, the array becomes a paged array.
You can use this command to slightly improve system performance by causing more
arrays to be unpaged. Accesses to unpaged arrays are faster and need less
interaction with the operating system than accesses to paged arrays.
On the other hand, a system whose memory is overloaded and is thrashing could be
adversely affected if unpaged array sizes are set too large. For best results, this
command must be used in a way that is appropriate to the particular system.
Caution:
If you increase the value of SEGARRAYSTART, some programs that worked
correctly with the smaller value might fail with the larger value. The system might
discontinue a program that uses the RESIZE intrinsic with the message
OVERLAYABLE ARRAY TOO LARGE.
For more information about array row sizes and how they affect the overlay
mechanism, refer to the OVERLAY option in the DL (Disk Location) command.
Syntax
The array size is any number from 1024 to 65535. The default is the page size of the
system or 4096, whichever is larger. The MAXIMUM LONG ARRAY SIZE sets the
largest unpaged (LONG) array permitted. The MAXIMUM LONG ARRAY SIZE is fixed
for all machines at 16 bits (2**16-1=65535).
Explanation
SEGARRAYSTART
Displays the current SEGARRAYSTART settings. The page size used for paged arrays
is also displayed. The page size is determined by the processor microcode and is
fixed during system initialization.
Examples
Example 1
This example shows the response given to a SEGARRAYSTART inquiry:
SEGARRAYSTART
Example 2
This example causes a syntax error, because the array size is set too small:
SEGARRAYSTART = 200
Example 3
This example allows an unpaged array size of a minimum of 1,500 words:
SEGARRAYSTART 1500
Syntax
<blockval>
An integer in the range of 10 through 2000.
<bufsize>
An integer in the range of 480 through 64000.
<dasname>
INTRASYSTEM/BNAV2ICPINITIALIZATION for BNA Version 2 network processors
(NPs).
<freeval>
An integer in the range of 1 through 63.
<initval>
An integer in the range of 1 through 63.
<maxval>
An integer in the range of 10 through 127.
<wbufsize>
An integer in the range of 128 through 64000.
<wresize>
An integer in the range of 0 through 64000.
<repbufsize>
A construct specifies an integer in the range of 1 through 64000.
<option>
Explanation
SEND NP <unit number>: <NP unit-related command>
Specifies that the NP unit-related command is to be sent to the network processor
identified by the unit number. The semantics of the NP unit-related command, as
well as the responses to these NP unit-related commands, are defined by the
NPSUPPORT library; the text of the NP unit-related command is not inspected by the
CONTROLLER or the MCP. The NPSUPPORT library must be initialized before the
SEND NP command can be used.
If the unit is saved, you must ready it with the RY (Ready) command before the
NPSUPPORT library can access and control that unit. Before you can use any NP unit,
you must equate the SL NPSUPPORT function to the proper library code file.
Otherwise, if a ready NP exists, the system issues an RSVP message saying that the
NPSUPPORT library is not usable and the system waits for an SL (Support Library) or
a DS (Discontinue) command.
ANALYZE
DIAGNOSTICS
PROGRAMDUMP
RELEASE
TANKING
The following are the nondiagnostic options:
AUTOLOAD
BLOCKING
BLOCKTIMEOUT
BUFFERSIZE
DASNAME
DUMP
FREEINPUTS
ID
INITIALREADS
LOAD
MAXINPUTS
QUIT
WRITEBUFFER options
It is recommended that you use the following default options.
Option Value
MAXINPUTS 45
FREEINPUTS 5
INITIALREADS 10
WRITEBUFFERSIZE 90 (bytes)
Note: NPSUPPORT establishes these default values only when it creates the file
NP/SUPPORT/RECOVERY for the first time.
The system creates the file NP/SUPPORT/RECOVERY, if it does not already exist, on
the family specified by the DL OVERLAY pack specification when the NP support
library first initializes. However, if the file NP/SUPPORT/RECOVERY already exists on
the DL OVERLAY pack, NPSUPPORT uses the values of the NP options that are
already present in the file.
You can determine the values of NP options that are currently present by entering
the following command:
If you want to modify the values of the NP options, you must enter a command that
is structured in the following manner:
Changed values do not take effect until the system creates a new
NP/CONTROLLER/<unit number> stack or until you reinitialize the NPSUPPORT
library. To establish the new values, use the following procedure:
1. Issue the command SAVE N <unit number> to make the network processor
inaccessible to the system.
2. Issue the command CLEAR NP <unit number> to clear the network processor.
3. Wait for the NP/CONTROLLER/<unit number> stack to go to EOJ.
4. Issue the command READY NP <unit number> to ready the network
processor for use.
If multiple overlay families exist, NPSUPPORT places the recovery files on the first
overlay pack in the overlay family list. If you remove the file, or if you issue a DL
OVERLAY command that specifies a family that does not contain an
*NP/SUPPORT/RECOVERY file, the MCP creates a new file with the default options the
next time it initializes the NPSUPPORT library. In the following explanations,
NP/CONTROLLER/<unit number> is an invisible independent runner for the
corresponding NP unit. You cannot verify its existence by entering an AA (Active Mix
Entries All) command, but you can determine its presence by entering OL NP.
You can control the size of the host-to-NP message buffers at system initialization, or
when a host-to-NP request is being processed, or when the subport closes. You can
also report statistics about the use of these buffers.
ANALYZE
ANALYZE <file name>
Analyze the tank file and print the analyzed file. If a file name is not specified, the
active tank file is closed and renamed NP/TANKED/INPUT/<unit
number>/<date>/<time>, it is analyzed and printed, and a new tank file is created.
If a file name is specified, that file is analyzed.
AUTOLOAD
Causes the driver stack to try to load firmware as soon as the driver stack is
initialized. To turn the option on or off, precede the keyword AUTOLOAD with SET or
RESET. The default is SET.
BLOCKING
Causes the network processor to block all incoming messages to the host. If the
value of the BLOCKING option is SET, incoming messages are sent to the buffer of
the network processor. When this buffer is full, the contents of the buffer are sent to
the host as one set of messages. If the value of the BLOCKING option is RESET, then
every incoming message is immediately sent to the host.
You can set or reset the BLOCKING option at any time. To turn the option on or off,
precede the keyword, BLOCKING, with SET or RESET. (The default value is SET.) The
new setting does not take effect until the system either creates a new
NP/CONTROLLER/<unit number> independent runner for the unit (refer to
Considerations for Use later in this subsection) or reinitializes the NPSUPPORT
library.
Reset blocking is not supported for ICP DLPs. If you attempt to reset blocking for an
ICP DLP, then a message indicating an NPSUPPORT protocol error is displayed. If this
message appears, do the following to regain communication with the ICP DLP:
BUFFERSIZE
BUFFERSIZE <bufsize>
Display or set the size of the input buffers for messages from the network processor
to the host. The minimum value for BUFFERSIZE is 4032 bytes, the maximum size is
65520 bytes, and the default size is 9024 bytes. The new buffer size takes effect
immediately. The size of the largest input buffer required since the last time the NP
was initialized is shown in the response to the SEND NP <number> ID command as
LARGEST INPUT BUFFER.
DASNAME <dasname>
DASNAME = <dasname>
DASNAME is valid only for network processors (NPs). Use DASNAME to specify the
name of the device application supervisor. The MCP uses DASNAME to determine the
correct supervisor for the device.
Processor DASNAME
Type
Workstation INTRASYSTEM/NTS_TWINAX_INITIALIZATION
DLPs
If the supervisor for the device is not initialized, the operating system displays the
following message on the ODT:
DIAGNOSTICS
Displays diagnostic messages about the network processor system. To turn this
option on or off, precede the keyword, DIAGNOSTICS, with SET or RESET. The
default value is RESET.
DUMP
Causes a dump of the network processor. The internal memory state of the network
processor is dumped into a file with the following name:
DUMP/<hostname>/NP/<unit number>/MMDDYYYY/HHMMSS
The value MMDDYYYY is the date, and the value HHMMSS is the time that the DUMP
request was made. A DUMP request is fatal to the network processor, because it
clears the network processor. If you enter the command SEND NP <unit
number>:DUMP, the system creates a dump file on the overlay pack when the
NPSUPPORT library initializes. If you change the overlay pack, successive NP dump
files continue to be created on the previous overlay pack until the NPSUPPORT library
is initialized or until the next halt/load.
It is recommended that you take NP dumps by using the BNA Version 2 command
NW DUMP NP <unit number> <family name>. For details on how to use this
command, refer to the Networking Commands and Inquiries Help.
FREEINPUTS
FREEINPUTS <freeval>
Display or set the minimum number of available input buffers. If the number of
available input buffers falls below this value, the NPSUPPORT library starts a task to
overlay the buffers being used by the host (not the buffers in use by the network
processor). Setting this number too high causes frequent overlays and reduces
throughput. Setting it too low could force the network processor to wait for an
available buffer, thus reducing throughput. The minimum value of <freeval> is 1, the
maximum is 63, and the default value is 5.
You can change the value of FREEINPUTS at any time, but the new value does not
take effect until the system either starts a new NP/CONTROLLER/<unit number>
independent runner for the unit (see Considerations for Use), or reinitializes the
NPSUPPORT library. You cannot verify the existence of the NP/CONTROLLER/<unit
number> invisible independent runner by entering an AA command, but you can
determine its presence by entering the OL NP command.
ID
Displays compiler and run-time information about the network processor. See the
example for a sample display resulting from the ID message.
INITIALREADS
INITIALREADS <initval>
Display or set the number of initial read operations that the NPSUPPORT library is to
issue to the network processor. The default value is 10. With more than one read
operation outstanding, the network processor can complete one I/O operation and
begin transferring data with the next I/O operation while the system processes the
first. This option maximizes the throughput of the network processor. You can
change the value of INITIALREADS at any time, but the new value does not take
effect until the system starts a new NP/CONTROLLER/<unit number>independent
runner for the unit (see Considerations for Use) or initializes the NPSUPPORT library.
You cannot verify the existence of the NP/CONTROLLER/<unit number> invisible
independent runner by entering an AA command, but you can determine its presence
by entering the OL NP command.
LOAD
Requests that the driver stack load firmware into the network processor. This
message is used when AUTOLOAD has the value RESET.
MAXINPUTS
MAXINPUTS <maxval>
Display or set the number of input buffers to be used by the NPSUPPORT library for a
particular network processor. The minimum value is 10 buffers, the maximum is 63
buffers, and the default value is 45 buffers. You can change the value of MAXINPUTS
at any time, but the new value does not take effect until the system either creates a
new NP/CONTROLLER/<unit number> independent runner for the unit (see
Considerations for Use) or reinitializes the NPSUPPORT library. You cannot verify the
existence of the NP/CONTROLLER/<unit number> invisible independent runner by
entering an AA command, but you can determine its presence by entering the OL NP
command.
PROGRAMDUMP
Causes a dump of the driver stack to a printer backup file (a backup disk, or BD,
file). This file is labeled with the mix number of the frozen NP support library, for
identification. PROGRAMDUMP is not fatal. The unit continues its scheduled activities
after the dump.
QUIT
Requests that the independent runner NP/CONTROLLER/<unit number> terminate.
After you specify QUIT, the system does not allow any more connections to the
driver stack. The driver stack waits for the active count to go to 0 (zero) before
terminating.
RELEASE
When the system is in diagnostics mode, performs the following actions:
TANKING
Causes all incoming messages to be stored in a tank file. The tank file is named
NP/TANKED/INPUT/<ICP unit number>. The tank file is created on the family
specified in the DL OVERLAY command. To turn this option on and off, precede the
keyword, TANKING, with SET or RESET. The default value is RESET.
WRITEBUFFER Options
Controls the number of requests to expand the Host-to-NP buffers and the buffer
sizes.
Any option value not explicitly set at your site has a value of zero. If no options are
set or changed, the default write buffer size values are used. No change is made to
the value in the *NP/SUPPORT/RECOVERY file. The default processing is as follows:
Option Setting
WRITEBUFFERSIZE 128
WRITENORESIZE RESET
WRITERESIZEVALUE 1
WRITEGRANULARITY. Specifies the size range of the buffer size slot for
reporting. Specifying a new value removes (zeroes) any accumulated report
values. If no value is specified, a value of 50 is the default. Each buffer size
slot then corresponds to a write request range of 50 bytes (049, 5099, and
so on).
WRITEBUFFERSTATS. Sets or resets the reporting capability. When SET,
buffer use statistics are accumulated and reported automatically when
NPSUPPORT terminates. When RESET, no buffer statistics overhead
processing is done (neither counting RESIZES nor recording buffer size
counts).
WRITEONEFILE. Sets or resets the reporting into a single file. When SET, all
accumulated data about an NP are routed to the same print file. When RESET,
each write buffer report is directed to a separate print file. Reports for
different NPs are always routed to different print files.
WRITECUMULATIVESTATS. Sets or resets the reporting into a cumulative file.
When SET, the reported counts are retained after a report is produced. When
RESET, the report counts are zeroed after a report is produced.
REPORTWRITESTATS. Requests the write buffer statistics report from the
counts present in the recovery file. If write buffer statistics are being
accumulated when the NP/CONTROLLER stack terminates, a report request is
automatically issued by the software.
When WRITEBUFFERSTATS is SET and you request the REPORTWRITESTATS option,
a printer report is produced.
Statistics are not updated for the report until a port closes, so the report is more
accurate if few buffers are currently open. The RESIZE counts are updated when a
buffer is stretched and when it is resized.
Examples
Example 1
This example shows the terminal display resulting from a SEND NP <number> ID
message:
SEND NP 158: ID
Example 2
This example shows a sample write buffer statistics report:
3. To make the network processor ready for use, enter the following syntax:
RY NP <unit number>
Inactive
Linking
Initializing
Active
Terminating
Waiting to delink
SEND TAPESERVER <text>
SEND TS <text>
Pass text to the TAPESERVER.
Examples
Example 1
This example initiates the TAPESERVER library:
SEND TS START
Example 2
This example stops the TAPEMANAGER library:
SEND TM QUIT
Example 3
This example asks for the status of the TAPESERVER library:
SEND TS STATUS
Example 4
This example passes the text HELLO to the TAPEMANAGER library:
SEND TM HELLO
SF (Set Factor)
The SF (Set Factor) command displays or sets the memory management parameters
for the entire system. You can use the O (Overlay) command to display relevant
information about the overlay factors which are set in the SF command.
Syntax
<factor list>
<number>
The following are the valid ranges of values for <number> for each factor.
1 0 through 99 %
2 0 through 99 %
3 0 through 999 %
6 0 through 100 %
7 0 through 100 %
Explanation
SF
Displays the current memory management parameters:
Factor 1, OLAYGOAL
Factor 2, AVAILMIN
Factor 3, FACTOR
Factor 5, BUFFERGOAL
Factor 6, OLAYSATURATION
Factor 7, OLAYCHANGE
SF <number>
Sets the value of factor 3, FACTOR, to <number>. FACTOR is the default; it is
assumed when the command does not specify a factor to be set.
SF <factor list>
If the numbers in an SF command are preceded by 1, 2, 3, 5, 6, or 7, the value is
assigned to the first, second, third, fifth, sixth, or seventh parameter, respectively.
The factors are described in the paragraphs that follow.
Factor 1: OLAYGOAL
Together with Factor 2 (AVAILMIN), the OLAYGOAL factor controls the rate at which
overlayable memory is to be overlaid on a per-minute basis. The independent runner
WS_SHERIFF does the overlaying.
If both OLAYGOAL and AVAILMIN are 0 (zero), WS_SHERIFF is disabled, but not
terminated. Otherwise, the rate at which WS_SHERIFF runs is determined by
OLAYGOAL as follows, where the calculation gives the total percentage of processor
resource used by WS_SHERIFF:
If OLAYGOAL and AVAILMIN are not both 0, WS_SHERIFF performs the following
tasks:
If less than AVAILMIN percent of system memory is available and less than 25
percent of overlayable memory is in the least-recently-used (LRU) list,
approximately OLAYGOAL percent of overlayable memory is placed in the
Least-Recently-Used (LRU) list per minute. Otherwise, OLAYGOAL percent
squared of overlayable memory is placed in the LRU list per minute. For
example, if OLAYGOAL is 1 percent, then 0.01 percent of overlayable memory
will be placed in the LRU list. The memory is not overlayed at this point.
OLAYGOAL is used to determine the rate at which the LRU list is overlaid to
disk:
If the amount of available memory is less than AVAILMIN percent of system
memory, the LRU list is overlaid at a rate of OLAYGOAL percent per minute.
Otherwise, if available memory is less than 2*AVAILMIN percent of system
memory, the LRU list is processed at OLAYGOAL percent squared per minute.
Otherwise, if there is anything in the LRU list, 1 area is written to disk every
few seconds.
Setting OLAYGOAL to a value greater than 0 (zero) also causes the system to use a
different algorithm in determining whether enough memory is available to start a job
or task. Refer to the System Operations Guide for further information.
Factor 2: AVAILMIN
AVAILMIN interacts with OLAYGOAL to determine the rate at which WS_SHERIFF
overlays memory to disk and reshuffles memory. See the preceding description of
OLAYGOAL for an explanation of the relationship. If AVAILMIN and OLAYGOAL are
both 0 (zero), WS_SHERIFF is disabled (but not terminated).
Factor 3: FACTOR
This factor is used only for scheduling.
If the task is not "scheduled" according to the rules for STRICTSCHED (option 39), or
if STRICTSCHED is not set, a memory estimate of a task is divided by value of
FACTOR to determine if enough memory is available for the task to be started.
Suppose a memory estimate of a task is 10,000 and FACTOR is set to 200 percent.
The scheduling algorithm uses a memory estimate of 5,000 (10,000 divided by 2.00)
to see whether enough memory is available to start the task.
Factor 5: BUFFERGOAL
This factor specifies the minimum value, in words, that can be used for the default
buffer size for files with a FILESTRUCTURE attribute value of BLOCKED or STREAM.
In general you should not specify a value for this factor. The system default value
should provide an adequate buffer size. To restore the system default value, set
factor 5 to 0 (zero). Determine the system default value by multiplying the Mwords
of system memory shown in the MM (Memory Module) command display by 1024. If
this value is less than 2000, then 2000 words is the default value. If this value is
greater than 5000, then 5000 words is the default value. If the value is between
these two values, it is the default value. Refer to the description of the BUFFERSIZE
attribute in the File Attributes Programming Reference Manual more information.
Factor 6: OLAYSATURATION
OLAYSATURATION determines the level of processor usage that can be used for
overlay activity. If the processor usage exceeds the value of OLAYSATURATION and
OLAYGOAL is 0 (zero), new tasks are scheduled. The default setting is 15%.
Factor 7: OLAYCHANGE
OLAYCHANGE provides control over the smoothing of system overlay activity. The
calculated overlay activity is used to determine if the OVERLAYSATURATION (SF 6)
threshold has been exceeded. This smoothing factor is used in the calculation only
when the amount of overlay activity is decreasing. If overlay activity is increasing,
the actual level of overlay activity is used to determine overlay saturation. The
default setting is 10%.
Examples
Example 1
This example shows an SF display:
SF
Example 2
This example sets factor 2 (AVAILMIN) to 10 percent and factor 1 (OLAYGOAL) to 5
percent:
SF 2 10 1 5
Example 3
This example sets factor 5 (BUFFERGOAL) to its default value:
SF BUFFERGOAL 0
Programs on all hosts sharing a disk family can perform the following actions:
Read data from files on the disk family and rewrite data in existing files on
the disk family.
Initiate programs on the shared disk family or invoke procedures in libraries
on the shared disk family.
Read the attributes of files on the shared disk family.
Programs running on the master host can perform the following additional actions:
To be shared, a disk family must have a local system access directory. Refer to the
FAMILYACCESS (Directory Location) command.
Syntax
<number>
Currently, the only supported level number is 1.
Other share levels can be used by system software. Their use is documented in the
appropriate product documentation and should be used only as described in that
documentation.
Explanation
SHARE + <family name> LEVEL = <number>
Marks the labels of all the disk volumes in a family as shared disks and also
establishes the host where this command was entered as the master host for the
shared disk family.
Caution
Before using the SHARE + command, verify that all disks within the family are
freed from all connected hosts. If you issue a SHARE + command, and one or
more of the disks were already in the acquired state on any other host, you run
the risk of data corruption and system failures. To remedy the situation, you must
perform one of the following actions:
To process the SHARE + system command, the system starts an independent runner
named SHARE + <family name>. This process performs the following actions:
Checks whether the disk family is already shared and, if so, rejects the
request with a corresponding error message.
Checks the disk family for the presence of a local system access directory and
rejects the request with a corresponding error message if one is not found.
For information about local system access directories, refer to the
FAMILYACCESS (Directory Location) command.
Checks the disk family for CM (Change MCP), DN (Dump Name), DL (Disk
Location), memory disk, mirrored or cached status and rejects the request
with a corresponding error message if the family has such a status.
If there are no errors, the process proceeds as follows:
Updates the disk label of each disk family member with the host name and
system serial number of the host that the command was executed from, thus
designating that host as the master host for the family. The date and time the
shared disk family was created and the specified share level is written to each
family member's label. This action makes the current host the master host for
the disk family.
The system generates a message to indicate that the disk family is now
shared.
Note: Use the SHARE + command only on the master host. After a disk has been
marked as shared, any other host that executes an ACQUIRE (Acquire Resource)
command for that disk automatically becomes a nonmaster host. The host that
executes the ACQUIRE command must have the same LONGFILENAMES setting as
the master host, otherwise the system returns the following error message: 'FAST'
BLOCK SIZE OR VERSION MISMATCH. For further information and restrictions on
using LONGFILENAMES, refer to the SYSOPS (System Options) command.
To process this command, the system starts an independent runner named SHARE
<family name>. If the disk family is not shared, the process generates an error
message. If there are no errors, the process issues an RSVP asking you to free all
the disk family members from all other hosts. You can make either of the following
replies.
Reply Action
OK Erases the shared status in the disk label and the in-memory unit
information for each member in the specified disk family. The
disk family no longer has a master host assigned to it.
If there are no errors, the process issues an RSVP requesting that you free all the
disk family members from the current master host before proceeding. If you reply
with DS, the SHARE TAKEOVER <family name> process is aborted. If you reply with
OK, the process performs the following actions:
Updates the disk label of each family member with the host name and system
serial number of the host that the command was executed from. This action
designates the host as the master host for the family. The process writes the
date and time of when the shared disk family was created and the specified
share level to the label of each family member. These actions make the
current host the master host for the disk family.
Marks any open file headers on the disk family as being open on the master
host..
Recovers the system access directory of the disk family or rebuilds the
system access directory if necessary.
Performs a directory complement to determine the available space on the disk
family.
Generates a message to indicate that the host is now the master host.
Examples
Example 1
This example marks the disk family named WORK as a shared family with level 1
sharing capabilities:
Example 2
This example erases the shared status of a disk family named WORK:
SHARE - WORK
Example 3
This example changes the master host for the disk family named WORK to the host
that the command was executed from:
Use certain GETSTATUS calls that make copies of disk directories (if the copy
would be made to a shared disk family).
Take checkpoints to a shared disk family. Do not use families with the name
DISK or PACK as shared families.
Open files with any of the following file attribute values:
EXCLUSIVE = TRUE
BUFFERSHARING = SHARED or EXCLUSIVELYSHARED
Note: Although programs can use Direct I/O recording locking, the locking applies
only to processes that are accessing a file from the same MCP host.
RUN and PROCESS statements to run code files resident on a shared disk
family and the COMPILE statement to run compilers resident on a shared disk
family.
COPY, ARCHIVE, and other library maintenance statements to copy files from
a shared disk family to tape or other disks. If these statements are executed
on the master host, they can also copy files to a shared disk family.
CHANGE and SECURITY statements (but only if they are executed on the
master host).
Do not use the following WFL statements:
Caution
If one of the hosts sharing a disk family is halt loaded to an MCP that does not
support shared disk families, that host does not recognize the shared status of the
family. Therefore, programs and operators on that host can perform actions that
are not allowed in a shared environment, and that can compromise the integrity
of the shared disk family. This caution applies also to the use of the LOADER
utility.
Before you create a shared disk family, make sure it has a family name that does not
conflict with the names of any families on any of the hosts that will have access to it.
Also, ensure the serial numbers of all the members of the disk family do not conflict
with the serial numbers of any of the disks on hosts that will be sharing the disk
family.
If it is necessary later to remove existing files on a shared disk family, and proceed
as follows:
1. Use the following system command to release all the members of the shared
disk family from all hosts except the master host:
FREE PK <unit number>
Note that the system rejects a FREE command for a disk if a program on that host
is using that disk when you enter the command.
2. Use the following system command to cancel the shared status of the disk
family:
SHARE - <family name>
5. Use the following system command on all the members of the shared disk
family on all the hosts that need to share the disk family:
ACQUIRE PK <unit number>
When a program or job that is not running on the master host opens, updates,
executes, or copies a file from a shared disk family, the system does not update the
ALTERDATE, COPYSOURCEDATE, EXECUTEDATE, ACCESSDATE, and READDATE
dates, or the times or timezone values of the file.
The in use counts displayed by the PER PK and PD system commands show only
the usage counts for the host on which the command is executed. They do not show
the usage by other hosts sharing the disks. Similarly, the display for the SHOWOPEN
system command shows only the usage for the host on which the command is
executed.
The system does not use any form of structure caching for shared disk families. None
of the following are cached: directories, headers, or code stacks. However, the
system continues to use the structure caching specifications for other, non-shared
disk families. For information on structure caching, refer to the STRUCTURECACHE
(Cache Maintenance) command.
SHOW
The SHOW command lists a collection of attributes associated with the mix or with
the disk subsystem or tape subsystem. The command selects the items being
reported by specifying the attribute selection.
Syntax
<object type>
<attribute list>
<attribute selection>
<wild card>
<delim>
Use one of the following characters
/ \ I ~ ! @ # $ % ^ & * ' .
<date value>
Explanation
SHOW MIX <attribute list>
Displays the selected attributes for all mix entries (including libraries).
Each line of the output begins with the mix number, followed by the attribute values
and then the task name.
QUEUE Integer The job queue, if any, that is the source of the
process
Each line of the output begins with the mix number, followed by the attribute values
and then the library name.
The library attributes that can be specified are the same as the mix attributes that
were listed previously.
Each line of the output begins with the unit number, followed by the attribute values,
and then followed by the disk name.
SPARE Boolean TRUE if unit has been entered in the spare disk
pool (as either a free spare or an in-use spare)
Each line of the output begins with the unit number, followed by the attribute values,
and then followed by the tape name.
The following attributes can be used when mounted tapes are the target of a SHOW
command.
The sort attribute can be the same as one of the attributes in the attribute list, but it
does not have to be.
A value of FALSE selects objects for which the attribute has a value of FALSE.
If neither TRUE nor FALSE is specified, the value is assumed to be TRUE. For
example, SELECT MIX PU selects all the privileged programs in the mix.
Relation Meaning
= Equal to
Character Description
For example, if you enter the following syntax, the system returns entries that
contain the string "SYSTEM":
If you enter the following syntax, the system returns entries that contain the string
"system":
ALL
If information in the right-hand column of a SHOW display is truncated to fit your
screen, you can specify the ALL parameter to use a display format that displays one
attribute name and value per line.
Examples
Example 1
The following example displays several attributes for each mix entry:
MixNo-Control-Locked-PU-Name--------------------------------
8461 LOTSATASKS
8465 (PHIL) NOTHING
8439 X X *511/SYSTEM/DSSSUPPORT
8441 X X *SYSTEM/STATION/TRANSFER
8433 X *SYSTEM/NEWP ON SYS511
8429 X X *511/SYSTEM/HELP
8428 X *SYSTEM/MARC/AGENDA
8426 X *SYSTEM/MARC/COMMANDER
8422 X X X *SYSTEM/NPSCS/SUPPORT
8410 X *511/SYSTEM/FAULTLOGGER
Example 2
The following example displays various attributes for each mix entry, and also sorts
the entries into descending order based on their CPUTIME attribute:
MixNo-CPUTime---IOTime----ReadyQTime-InitPBit---Name------------------
8465 14:32 :00 1:17 :00 NOTHING ON DISK
8411 2:35 :04 :45 :06 SYSTEM/TESTIT
8438 1:14 :01 :24 :09 SYSTEM/LCF
8441 1:05 :00 :24 :02 *SYSTEM/COMS
8419 :37 :31 :39 :02 PRINT/WORKER
8409 :23 :00 :09 :00 *SYSTEM/CANDE
Example 3
The following example displays only library entries that include the string COM. For
each entry, this example lists the RELEASEID attribute:
Example 4
The following example displays various attributes for each disk unit:
UnitNo---AvailSects-LargestSZSects-TotalReads-TotalWrites--Name---------
44 250,827 38,682 1,420 363 PACK
45 437,220 167,983 3,840 1,150 DISK
47 1,112,719 662,691 110 168 DMSIITEST
Example 5
The following example lists the SCRATCH attribute for all tape units:
SHOW MT SCRATCH
UnitNo-Scratch-Name----------------------
35 DLTDUMPS/FILE000
36 X
37 HLCNSAVEDPS/FILE000
38 HLCNSAVEDPS/FILE003
Example 6
The following example uses the ALL option to display attribute values that match the
string =CAN= without truncation.
------------------------------------------------
MixNo: 5609
ReleaseID:
Name: CIA_INDICANT003/FOR/5608
------------------------------------------------
MixNo: 6832
ReleaseID: MCP 09.0 [50.150.000] (50.150.0024)
Name: *SYSTEM/CANDE
------------------------------------------------
MixNo: 8758
ReleaseID: MCP 09.0 [50.150.000] (50.150.0024)
Name: *CANDE/SERVANT01
Example 7
The following example reports the certified status for mirrored packs.
SHOW PK CERTIFIED
UnitNo-Certified-Name
180 X T180
Example 8
The following example reports the certification timestamp for all certified mirrors
which were certified today.
When you are trying to use the CLOSE (Close Pack) or RES (Reserve) commands on
a disk,you can use the SHOWOPEN command to determine what tasks are using files
on the family. When using the RES system command, you can use the <range>
specification to determine what tasks are using files in the target area of a RES
command. When you are trying to determine what tasks are using a particular file or
set of files, you can use the SHOWOPEN file and directory variants to display that
information.
Syntax
<CD info>
<disk info>
<range>
Explanation
The SHOWOPEN command generates information about open files. You can use this
information, for example, when you are trying to close a pack with the CLOSE (Close
Pack) command, but open files prevent the pack from being closed.
The maximum number of users displayed for a single file is approximately 200.
Examples
Example 1
The following example displays information about all open files on the specified
family:
SHOWOPEN ON RFAM
Example 2
The following example displays information about the users of the
SYSTEM/CARDLINE program on PACK:
Example 3
The following example displays information about all open files with usercodes on the
family DISK:
Syntax
Explanation
The spare disk pool is a collection of packs which have been assigned by the
customer as spare disks for automatic replacement of failed mirror disks. The pool
contains two types of spare disks: free spares and in-use spares.
Free spare disks contain no data and are not actively being used by any system or
application software. The entry for each free spare pack displays the unit number,
the serial number in brackets, and the word S P A R E.
In-use spare disks are actively being used as members of an online mirrored set. A
display entry is shown for all members of online mirrored sets. The entry for each in-
use spare pack shows the unit number, the serial number in brackets, and the family
name. These fields are identical to the fields displayed in the PER (Peripheral Status)
command.
At any given time, some packs in the spare disk pool might not be available for
selection as replacements for failed mirrors. Packs which are excluded are closed
(the entry displays the word C L O S E D) or reserved (the entry displays the word
R E S E R V E D), or are mirrored sets with less than three online members. Packs
not currently available for selection are displayed with the unit numbers enclosed in
parentheses.
Example
The following example displays information about a system that has free spare disks
in the spare disk pool. The display groups spare disks by capacity and logical sector
size. For each group of packs, the group heading includes all subtypes for which the
packs are compatible mirrors.
SHOWSPARES
SI (System Intrinsics)
The SI (System Intrinsics) command changes the file used for the system intrinsics
or displays the current title of that file.
When the system intrinsics file is changed, currently active tasks continue to use the
old intrinsics stack; new jobs use the new intrinsics stack.
Syntax
Explanation
SI
Displays the title of the file containing the current system intrinsics.
SI +
Causes the default file, SYSTEM/INTRINSICS, to be used for the system intrinsics.
SI <file title>
Causes <file title> to become the file used for the system intrinsics.
Examples
Example 1
SI SYSTEM/X
MSG
Example 2
SI +
MSG
Example 3
SI
INTRINSICS: SYSTEM/INTRINSICS
SL (Support Library)
The SL (Support Library) command maps function names to library code files.
Syntax
<attributes>
Explanation
SL
Displays the current libraries associated with the various function names. See the
CHECKFILE SL command for related information.
SL*
Displays the function names and their attributes.
SL <function name>
Displays the current library associated with the function name.
SL <function name>
Does one of the following:
If the library for the function is running and is not a ONEONLY function, the
system does the following:
Changes the library to a temporary library
Removes all information for the function from the system tables
If the library for the function is running and is a ONEONLY function, the
system rejects the SL command with the following response:
CAN'T BE MODIFIED WHILE IN USE
1. Enter the command LIBS to find out the mix number of the library.
2. Enter one of the following commands and wait for the library to terminate:
<mix no> THAW
<mix no> DS
library with either a THAW (Thaw Frozen Library) command (so that the
library will resume when it has no more users) or a DS (Discontinue)
command.
If the code file is TADS-compatible and the system is running with the security
option TADSWARN set, the system displays a warning message immediately after the
response to the command. If the code file title is placed in a pending state, the
system displays the warning message again when the code file replaces the current
one and becomes the library file.
System libraries which are defined in the MCP have some security attribute values,
such as ONEONLY and MCPINIT, that are internally set by the system. For Boolean
attributes, such as ONEONLY, MCPINIT, TRUSTED, and SYSTEMFILE, if the attribute
is set by the system, it cannot be reset. The linkage class attribute is an integer
value in the range 1 through 15, and can be changed only if a new class is able to
link to the system-defined linkage class. If an attribute specification violates these
rules, the system displays the error message LIBRARY ATTRIBUTES NOT
CHANGEABLE.
The library attributes assigned by the SL command are used only if the library is
initiated BYFUNCTION. Otherwise, they are not used.
LINKCLASS
An integer value from 0 to 15 that indicates the linkage class to be assigned to
the library code file. If the TRUSTED attribute is set, the system determines
whether a user can access a procedure exported from a library code file by
comparing the linkage class of the user program with the linkage class of the
requested library procedure.
If the TRUSTED attribute is reset, the system compares the linkage class of the
user program with the linkage class of the entire library code file. Linkage class
values for a library code file are as follows.
2 MCS 0, 2, 3, 4
3 Environment 0, 3, 4
Libraries
4 Privileged 0, 4
Programs
5 Compilers 0, 5
Examples
Example 1
SL
SL GENERALSUPPORT = *SYSTEM/GENERALSUPPORT
SL PLISUPPORT = *SYSTEM/PLISUPPORT
SL PRINTSUPPORT = *SYSTEM/PRINT/SUPPORT
*SYSTEM/PRINT/SUPPORT/2 (PENDING)
SL USERFUNCTION = (USER)SYSTEM/USERLIBRARY
Example 2
SL GENERALSUPPORT
SL GENERALSUPPORT = *SYSTEM/GENERALSUPPORT
Example 3
SL USERFUNCTION = (USER)SYSTEM/USERLIBRARY
Example 4
SL * PRINTSUPPORT
SL PRINTSUPPORT = *SYSTEM/PRINT/SUPPORT
MCPINIT, TRUSTED, ONEONLY, LINKCLASS=1
Example 5
SL PRINTSUPPORT = *SYSTEM/PRINT/SUPPORT/V2
SL PRINTSUPPORT
SL PRINTSUPPORT = *SYSTEM/PRINT/SUPPORT
*SYSTEM/PRINT/SUPPORT/V2 (PENDING)
Example 6
SL - USERFUNCTION
Example 7
SL - PRINTSUPPORT
Example 8
SL USERFUNCTION = SYSTEM/TADSFILE
Example 9
SL COMSSUPPORT: -MCPINIT, LINKCLASS=2
Example 10
SL NEWFUNCTION = SYSTEM/NEWFUNCTION : TRUSTED, LINKCLASS = 1
If you want to copy a new version of a support library to disk and give it the same
file nameor otherwise replace the current library with a new library code file with
the same nameyou must enter an SL command after the new version of the code
file has been copied. Whenever a support library is initiated, or whenever the
command SL <function name> = <file title> has been successfully executed, the
system establishes a link between the library code file currently resident on the disk
and the function name. This linkage remains intact even if the code file is
subsequently removed or replaced, or if the library is terminated with a THAW (Thaw
Frozen Library) or a DS (Discontinue) command. The linkage is broken only under
the following circumstances:
Several function names and associated libraries are provided in the system software.
For example, many intrinsics reside in the SYSTEM/GENERALSUPPORT library, which
has the function name GENERALSUPPORT. All function names suffixed with SUPPORT
are reserved for current and future system use. However, the titles of the support
libraries can be altered or function names can be created through the SL command.
For ONEONLY support libraries, such as PRINTSUPPORT, the title cannot be changed
while the library is running or frozen. Instead, the new title is marked as pending
under the function name in the SL function mapping table, and the following
response is displayed:
The new library is not used until the current library terminates (for example, as a
result of a THAW or a DS command) or until a halt/load takes place. You can remove
the pending title with the SL command.
When you use the SL command to assign a code file to a function, the MCP records
the function name and the associated code file in its function mapping tables. The
MCP becomes a user of the code file until a halt/load or until another SL command
maps a new code file to the function name.
If someone replaces the code filesuch as by copying in a file with the same name
with another code file of the same name, the change does not become effective until
a halt/load or an explicit SL command establishes the new code file as the
replacement library.
A program that was previously not executable becomes executable when it has been
associated with a function by the SL command and is then initiated by that function.
If security administrator status is authorized for the system, you must have a
security administrator usercode to execute this command.
Syntax
Explanation
<mix number list> SM <user text>
Sends the user text to the MCS or data base in the mix number list. You can use the
MCS (Message Control System) command to determine the active mix numbers of
the MCS.
The user text sent to an MCS can be any control command implemented for that
MCS. The command is placed in the primary queue of the MCS.
The user text sent to a data base can be any VISIBLE DBS command. These
commands are described in the Utilities Operations Guide.
If the MCS or data base sends any messages in response to the user text it received,
you can use the MSG (Display Messages) command to display these messages.
Examples
Example 1
In this example, the system sends the user text SS ALL HELLO to the MCS with the
mix number 5268. The operator then enters the MSG (Display Message) command to
display the response sent by the MCS.
MSG
Example 2
In this example, the operator wants to send a message to a database named
PARTSDB. First, he or she uses the DBS command to list all active database stacks.
The display shows that the mix number of the database named PARTSDB is 8239.
The operator uses this mix number in the SM command to send a status request to
that database. The operator then uses the MSG command to list the response to the
status request. The relevant messages in the MSG list are those that begin with that
mix number.
DBS
30679 SM STATUS
SN (Serial Number)
The SN (Serial Number) command purges and assigns serial numbers to tape
volumes and specifies their recording density, scratch pool, and whether they are to
be compressed.
The tape drive unit where the tape volume is mounted must be ready, not in use,
and write-enabled.
If you created the tape with the LOCKEDFILE file attribute set to TRUE, the system
displays the following message before it performs the purge operation:
If you respond to this message by using <mix number> OK, the tape is purged. To
cancel the purge operation, enter DS.
If you try to purge a library maintenance tape for which there is a LIBMAINTDIR disk
file resident on the DL LIBMAINTDIR disk family, the system displays the following
message and RSVP message and then waits for your response:
Decide if you want the system to remove the LIBMAINTDIR file and continue to
purge the tape or not. To locate the LIBMAINTDIR file, use the OL MT <unit
number> system command to find the name of the LIBMAINTDIR disk file. If you
respond to this message by using <mix number> OK, the system removes the
LIBMAINTDIR file and purges the tape. To cancel the purge operation, enter <mix
number> DS.
Syntax
<density>
<scratch pool>
Explanation
SN MT <SN option list>
Purges and assigns a serial number to the tapes mounted on the designated tape
units. The serial number consists of up to six alphanumeric characters. If a number
is used, it is right-justified with leading zeros added. Any serial number containing
alphabetic characters or any quoted alphanumeric string is left-justified with trailing
blanks.
If you attempt to assign a serial number to a locked tape, the following response
appears:
UNIT LOCKED
Note: If a tape has only one allowable output density, no density specification is
necessary and any SN command that specifies density is rejected with the error
INVALID DENSITY SPECIFIED.
For more information about this option, refer to Considerations for Use later in this
topic.
Examples
Example 1
In this example, the tape on unit 115 is purged and is assigned the serial number
X232. The density of the tape is identified as being 1600 bits per inch (bpi).
PER MT
Example 2
In this example, the tape on unit 116 is purged and is assigned a serial number of
000565. The density is identified as being 1600 bpi. The tape is then locked.
PER MT
Example 3
In this example, the tape on unit 116 is purged, assigned a serial number of 000565,
and assigned to a scratch pool named XYZ.
Example 4
In this example, the tape on unit 55 is purged, assigned a serial number of 000444,
and has a tape label written to indicate that compression was requested.
Example 5
In this example, the tape on unit 45 is purged, assigned a serial number of 000875,
and has a tape label written to indicate that compression was not requested.
Example 6
In this example, the tape on unit 55 is purged, assigned a serial number of 000334,
assigned to a scratch pool named ABC, and has a tape label written to indicate that
compression was not requested.
Expired tapes are treated as though they were scratch tapes from the pool specified
in the nonscratch label.
Tape Compression
If you enter a simple SN (Serial Number) command, which does not include a
compression keyword, to a device that does not support compression, and the
original label on the tape indicates compression requested, the system processes the
command with the following results:
The system writes the label to tape as if you had specified the
NONCOMPRESSED option.
The system issues the following messages to serve as an operator warning:
MT<unit number> [<serial number>] UNABLE TO SET COMPRESSION
MT<unit number> [<serial number>] PURGED
SQ (Show Queue)
The SQ (Show Queue) command displays information about the jobs in one or all job
queues.
Syntax
Explanation
SQ
Displays the queue number, fetch status, mix number, priority, usercode, queue
entry time, start time (if it has one and the start time is in the future), and job name
of the job at the head of each queue.
If a job name is specified after the BEGIN JOB, the job name is displayed.
If the job has parameters, the name displayed is the job name followed by
the parameters.
If no job name is specified, the string displayed is BEGIN JOB followed by the
first 30 characters from the next WFL statement or declaration in the job.
If a job contains a FETCH specification, the job number is preceded by an F.
SQ <number>
Displays the fetch status, mix number, priority, usercode, queue entry time, start
time (if it has one), and job name of every job in the queue denoted by <number>.
If the SQ <number> command is used and the system has no previously defined
queues, the system returns the following response:
SQ <number> <number>
Displays all entries in the queue indicated by the first number whose priority is equal
to the second number.
Examples
Example 1
SQ
QUEUE 1
NO ENTRIES
QUEUE 0 (FIRST OF 2 ENTRIES):
8391 50 BEGIN JOB DIRDUMP(BOOLEAN HARDCOPY);
QUEUED: 09/13/2002 AT 0:01:20 STARTTIME = 20:00:00
Example 2
SQ50
QUEUE 50
6630 50 JOB B;
QUEUED: 10/21/2002 AT 19:01:21
6631 50 ADDOUT
QUEUED: 10/21/2002 AT 19:04:22 STARTTIME = 20:00:00 ON 11/10/2002
6633 50 RUNNERS;
QUEUED: 10/21/2002 AT 19:05:25 STARTTIME = 20:00:00
6635 50 (SITE)RUNNERS
QUEUED: 10/21/2002 AT 19:06:00 STARTTIME = 20:00:00
6637 50 PRINT/A/JOB (1600)
QUEUED: 10/21/2002 AT 19:08:11 STARTTIME = 22:00:00
Syntax
Explanation
SQUASH <family name>
Starts the system process SQUASH/<family name>, which tries to compact the
allocated space on the family. If the family has more than one member, the process
compacts each online member. If a pack is mirrored, changes made to it are made
also to the other members of its mirrored set.
Examples
This example starts a process to compact the allocated space on the family named
DMSIITEST.
SQUASH DMSIITEST
When the SQUASH command is used, the system attempts to consolidate available
disk areas by moving from a specific area of the disk all disk areas that are in use.
The system selects the starting address of the area to be cleared based on the size
of the rows, the status, and the kind of files located in the area, and the amount of
available space already available in that area. The size of this area is 95 percent of
the total available space on the disk. Rows that are in use within this area are not
moved if they are larger than any contiguous available space elsewhere on the disk.
Therefore, you should consider the following when using the SQUASH command:
The SQUASH command can specify a family name that is in use. During the
execution of the SQUASH process, the available space on the disk decreases
progressively until the squash area is released at the end of the process. If a
program requires space that is not available on disk, it can go into a waiting state.
This condition is indicated in the waiting entry as SECTORS REQUIRED ON <family
name>.
Only one RES (Reserve) or SQUASH command can be active on a given disk family
at any given time. You cannot enter a SQUASH command while a RES or an XD (Bad
Disk) command is active on the same family, and you cannot enter a RES command
while a SQUASH command is active on the same family.
SS (Send to Station)
The SS (Send to Station) command sends a message from the ODT to data comm
stations identified either by station name or logical station number (LSN).
Syntax
Explanation
SS <station name> <user text>
SS <LSN> <user text
Send the message appearing as user text to the specified data comm stations. The
LSN is a number. The maximum length of <user text> is approximately 9000
characters.
Examples
SS M601: YOU HAVE A STOPPED JOB
SS M333: HELLO
ST (Stop)
The ST (Stop) command temporarily suspends jobs or tasks. The jobs or tasks can
be reactivated by the OK (Reactivate) command. This command sometimes has no
effect on an MCP independent runner, but you can usually terminate such a task with
the DS (Discontinue) command.
Syntax
Explanation
<mix number list> ST
Temporarily suspends the jobs or tasks in the mix number list.
Example
1024 ST
When you enter either an ST system command or a CANDE ?ST command, the task
does not become suspended until it attempts to use a processor. Stopped WFL jobs
do not become suspended until after the task started by that job terminates.
Syntax
Explanation
<mix number list> STARTTIME = <time>
Causes the jobs in the mix number list to start at the specified time. The time is the
time of day on a 24-hour clock in the form hh:mm. The number of hours must be
less than 24, and the number of minutes must be less than 60.
ON <date>
Causes the jobs to start at the given time on this date. The date can be either in the
form MM/DD/YY or MM/DD/YYYY.
Example
7132 STARTTIME = 21:12 ON 03/22/2002
Jobs that are given start times do not have any special status in the queuing
mechanism. They are subject to the same controls, such as mix limits, as other jobs
in the queues. If the JOBDESC file is removed, all queued jobs, including those with
start times, are also removed.
The start time of a job, if any, is displayed in response to the SQ (Show Queue)
command.
STORESAFE
The STORESAFE command is used to configure and monitor the StoreSafe feature.
Syntax
The <site ID> is the user-specified disk site name. The disk site name can be up to
17 alphanumeric characters in length.
Explanation
STORESAFE + PK <number> SITENAME <site ID>
This command assigns the <site ID> to PK <number>.
STORESAFE - PK <number>
This command removes the disk site name from PK <number> only if the command
does not create a StoreSafe alert condition.
an online mirror. The REMOVE variant is designed for situations such as this where
the subject disk is no longer online to the system. If a volume was in a StoreSafe
alert because there were no accessible members at the specified disk site name, use
of this command resolves the StoreSafe alert.
STORESAFE + ENFORCE
This command requests initiation of system-wide enforcement of StoreSafe alerts.
System-wide enforcement also requires that a valid feature key be installed in the
system keys file. When system-wide enforcement is in effect, the loss of the last
online copy of data at a disk site name causes a StoreSafe alert.
STORESAFE ENFORCE
This command requests termination of system-wide enforcement of StoreSafe alerts.
If the last online copy of data at a disk site name is lost when system-wide
enforcement is turned off, the alert is automatically overridden. Informational
messages are provided at the ODT to reflect the automatic StoreSafe override, but
I/O processing is not interrupted.
Examples
Example 1
The following message displays after installing the STORESAFE feature, but before
using it:
Example 2
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV +RUNNING
100B M DISK # 1 TR +RUNNING
PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and
PK 200 located at disk site name MV. The mirrored set is functioning normally.
Example 3
STORESAFE ALERTS NOT BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV -RUNNING
100B M DISK # 1 TR -RUNNING
PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR and
PK 200 located at disk site name MV. The mirrored set is functioning normally.
Example 4
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV +ALERT(AUDITING)
100B M DISK # 1 TR +SUSPENDED
name MV. The volume is in a STORESAFE alert because PK 200 was decommitted to
auditing.
Example 5
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: MV
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV(O) +OVERRIDDEN(AUDITING)
100B M DISK # 1 TR +RUNNING
A STORESAFE alert for this volume has been globally overridden after PK 200 was
decommitted to auditing. I/O activity is proceeding to the volume. PK 200 is not
synchronized.
Example 6
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
B DISK # 1 MV +ALERT(MISSING)
100B DISK # 1 TR +SUSPENDED
Example 7
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
300B M DISK # 1 MV +ALERT(PENDING)
100B M DISK # 1 TR +SUSPENDED
The volume is in a STORESAFE alert because PK 200 was decommitted out of the
set. PK 300 is being created at disk site name MV to resolve the alert, but has not
yet completed.
Example 8
Following is an example of the response that you receive if you enter a STORESAFE
ENFORCE command when the mirrored set is in the state described by the preceding
example.
Example 9
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV +SUSPENDED(AUDITING)
300B M DISK # 1 MV +RUNNING
100B M DISK # 1 TR +RUNNING
Since there is still an online copy of the data at MV on PK 300, I/O activity is
proceeding to the volume even though PK 200 was decommitted to auditing.
Example 10
Starting from the situation in the preceding example, PK 300 is now decommitted to
auditing and is not synchronized. This causes a STORESAFE alert.
Example 11
Starting from the situation in the preceding example, if you respond to the
STORESAFE_ALERT waiting entry for disk site name MV with an AX IGNORE PK 100
command, the response is as follows.
Example 12
Starting from the situation in Example 10, if you turn off system-wide enforcement
of STORESAFE alerts with a STORESAFE-ENFORCE command, the response is as
follows.
Example 13
Starting from the situation in the preceding example, both PK 200 and PK 300 have
their audits applied and they both come back online.
Example 14
Continuing with the preceding example, PK 100 proceeds even though it is not
ready. Since there is no system-wide enforcement of STORESAFE alerts, the alert is
automatically overridden.
Example 15
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV +SUSPENDED(AUDITING)
B M DISK # 1 RS +ALERT(MISSING)
100B M DISK # 1 TR +SUSPENDED
PK 100, PK 200, and PK 300 are a mirrored set, with PK 100 located at disk site
name TR, PK 200 at disk site name MV, and PK 300 located at disk site name RS.
PK 200 proceeds though it is not ready, causing an alert. You can override the alert
with an AX IGNORE PK 100 command and I/O activity resumes.
PK 300 is decommitted out of the set, causing a new alert. I/O activity is suspended
again.
Example 16
Continuing with Example 15, the operator responds with a STORESAFE REMOVE
SITENAME RS FROM PK 100 command. This command resolves the alert because a
copy at RV is no longer required. I/O activity resumes with the data at MV being out-
of-sync.
Example 17
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV -OVERRIDDEN(AUDITING)
100B M DISK # 1 TR -RUNNING
PK 200 proceeds even though it is not ready. There is no alert because STORESAFE
handling for critical disks is bypassed (note the minus (-) signs).
Example 18
STORESAFE ALERTS BEING ENFORCED
OVERRIDDEN SITES ARE: (NONE)
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
100B M DISK # 1 TR +RUNNING
200B M DISK # 1 +SUSPENDED(AUDITING)
PK 100 and PK 200 are a mirrored set with PK 100 located at disk site name TR; PK
200 is not STORESAFE named. PK 200 proceeds even though it is not ready. There is
no alert because members that are not STORESAFE-named have no effect on
STORESAFE handling.
Example 19
Continuing with the preceding example, PK 100 is decommitted out of the set. This
causes a STORESAFE alert because there is a requirement for a copy of the data at
disk site name TR.
Example 20
Following is an example of a display that includes multiple families, with multiple
family members and different volume compositions.
Syntax
Explanation
All forms of the STRUCTURECACHE command generate a display of the current
parameter settings and current data statistics for all four types of cache.
Note: You can use the RP (Resident Program) command to retain code stacks with
no users.
Examples
Example 1
The following example sets a new value for the size of the code stack cache and uses
the default value for the time limit:
Example 2
The following example displays all the information for the caches maintained by the
system for the data structures. The information displayed when the command is
executed is included in this example.
STRUCTURECACHE
SYSTEM/USERDATAFILE Cache
Size = 200 entries (18000 words in use)
current rate (per sec) since last H/L
reads hits/reads 3.87/3.87 = 100% 14092/14621 = 96%
reads hits/reads+writes 3.87/3.87 = 100% 14092/14798 = 95%
reads/reads+writes 3.87/3.87 = 100% 14621/14798 = 99%
Syntax
Explanation
<mix number list> SUPPRESS
Suppresses the display of the jobs or tasks in the mix number list.
Only mix display commands that contain an ALL qualifier display the suppressed jobs
or tasks.
Example
In this example, the A (Active Mix Entries) command displays the job MARC
identified by the mix number 6765. The SUPPRESS command causes this job not to
appear in the mix display. Another A command shows that the display was
suppressed.
6765 SUPPRESS
Syntax
Explanation
SUPPRESSWARNING
SPRWARN
Display the values currently stored in the warning suppression list of the system. If
the list is long, the display might cover several pages; enter the NS (Next Screen)
command to view succeeding pages.
SPRWARN ALL
Specifies that every warning message is to be suppressed.
SPRWARN NONE
Cancels the entire warning suppression list.
SPRWARN <number>
SPRWARN <number> <number>
SPRWARN + <number>
SPRWARN + <number> <number>
Add the specified value or values to the warning suppression list. The command can
specify a value, a range of values, or a list containing values, ranges, or both,
separated by commas. The value of <number> is the value associated with a system
warning message; it must be in the range 1 through 29999.
SPRWARN <number>
SPRWARN <number> <number>
Delete the specified value or values from the warning suppression list. The command
can specify a value, a range of values, or a list containing values, ranges, or both,
separated by commas. The value of <number> is the value associated with a system
warning message; it must be in the range 1 through 29999.
Examples
Example 1
This command results in a display indicating that the warning suppression list is
empty:
SPRWARN
SUPPRESSWARNING = NONE
Example 2
This command creates a list in which the range 1 through 4 is stored:
SPRWARN 4,2,1,3
Example 3
This command updates the list, with the result that the stored values are the range
1 through 9, and the number 21:
SPRWARN 5 - 9,21
Example 4
This command deletes the values 4 and 8 from the list, with the result that the
stored values are the ranges 1 through 3 and 5 through 7, and the numbers 9 and
21:
SPRWARN - 4,8
SV (Save)
The SV (Save) command makes units inaccessible to the system. Saved units can be
returned to the system with the RY (READY) command.
The SV command is not valid for online, mirrored packs. Before the SV can be
performed, the pack must be released with the MIRROR RELEASE command.
Note: CPM, IOM, and MSM are only allowed on IOM systems. IOP is only allowed on
IOP systems.
Syntax
<quad list>
Explanation
SV <device type> <unit number list>
Makes the devices in the unit number list inaccessible to the system. You can return
saved units to the system by using the RY (Ready) command. The device and unit
number list can be integers from 1 through 32767. The system does not accept any
new requestors of the resource provided by the device, but it does not interrupt
current users. If programs are using files on the device, those files continue to be
available until the programs close them.
SV MSM <number>
SV CPM <CPM list>
SV IOM <number>
Make the specified module unavailable for use if it is not the only one of its kind in
the system. The modules are kept in the partition and are marked saved/user saved.
MSM numbers can be either 0 or 1. CPM and IOM numbers must be integers in the
range 0 through 11. QUAD numbers can be from 0 through 3.
SV IOP <number>
The specified IOP is made unavailable for I/O operations unless it serves as the last
path to critical units. If the specified IOP serves as the last path to noncritical units,
an RSVP is posted to list the devices that will be lost, in which case, the user has the
option to abort the request. Once completed, the IOP is marked as SAVED in the
PCD. The specified IOP remains SAVED through subsequent halt/loads until the user
readies it by means of the RY command.
Examples
Example 1
This example saves a tape unit:
SV MT 114
MT 114 SAVED
Example 2
This example saves a memory subsystem module:
SV MSM 1
MSM 1 SAVED
Example 3
This example saves a central processing module:
SV CPM 6
CPM 6 SAVED
Example 4
This example saves an IOM system:
SV IOM 0
IOM 0 SAVED
Example 5
This example saves a critical pack, which is a pack that has been specified in a DL
(Disk Location) command:
SV PK 160
PER PK
-------------------------PK STATUS--------------------------------
160*B [000851] (TO BE SAVED)
Saving Memory
To obtain a successful release of a memory module (that is, an MSM, an MSU, or a
QUAD), consider some or all of the following options:
If disk caching is active, either terminate the system caching or downsize the
cache area.
Assure that adequate overlayable disk space is available.
Possibly reschedule the freeing of the memory resource to a time when the
system is idle or is not highly active.
Wait for the next system halt/load.
Issue the SF (Set Factor) system command with the OLAYGOAL option (Factor
1). OLAYGOAL is the percentage of overlayable memory that is to be overlaid
on a per-minute basis.
Use the CU (Core Usage) system command to monitor memory usage.
Issue the HS (Halt Schedule) system command to stop the initiation of any
new jobs or tasks.
Wait until the tasks terminate to perform the memory save specification.
If necessary, terminate tasks with the DS (Discontinue) system command
before you perform the memory save operation.
SW (Switches)
The SW (Switches) command enables you to dynamically control the Boolean setting
of any of the eight SW task attributes (SW1 through SW8). For detailed information
about these task attributes, refer to the Task Attribute Programming Reference
Manual.
Syntax
<switch no list>
<switch number>
An integer with a range from 1 through 8. If you enter a SW number less than 1, an
error message is displayed.
Explanation
<mix number> SW
<mix number> SW<n>
Displays the current value of all eight switches for the specified task.
Examples
Example 1
This example interrogates the value of the switches for task 4857.
4857 SW
Example 2
This example changes the value of switch 6 to TRUE for task 4857.
4857 SW 6 = TRUE
FALSE
TRUE
SYSADMIN COMMAND
Use the SYSADMIN COMMAND system command to control operator access to
system commands that are considered to be sensitive and that can change the
system state. Such commands are considered to be sensitive and are restricted to
use by a system administrator.
You must have special privileges to use certain forms of this command. Refer to
Considerations for Use for more details.
Syntax
Explanation
SYSADMIN COMMAND
Displays a list of the commands restricted to system administrator use. Use of this
form of the command does not require special privileges. You can enter this form of
the command from any source.
AD DL ML SEGARRAYSTART
AI DN MOVE SF
AR DQ MQ SHARE
ARCCOPY DR MP SI
ARCREPLACE GC NETEX SS
BNAVERSION HS RB SYSOPS
CM ID RECONFIGURE TERM
GROUP
COMPILERTARGET IK RES TL
COPYCAT LC RP TR
CS MAX SB UQ
DD
ACCOUNTING
DF
DL with the following options:
LOG
USERDATA
HU
ID with the following options:
<file name>
LG
LOGGING
MP with the following options:
COMPILER
EXECUTABLE
IDENTITY
KERBEROS
PU
SECADMIN
SERVICE
TASKING
All granulated privileges
MU
REMOTESPO :OK
RESTRICT
SECOPT
SL
SYSADMIN
SYSADMIN COMMAND <command> <option>
Restricts the use of the specified command option to a system administrator. The
value of <option> can be any valid reserved word. You can use options to restrict a
variation of the command rather than to restrict all uses of the command. For
example, you might want to restrict only usage of the LANGUAGE option of the
SYSOPS command.
Note: Because <option> can be any valid reserved word, an invalid combination of
words is not rejected. For example, DL CM is accepted but does not cause any
command to be restricted.
Examples
Example 1
This example restricts the use of the MERGE option of the IK system command.
Example 2
This example removes the usage restriction on the IK system command.
SYSADMIN - COMMAND IK
Example 3
This example sets usage restrictions on the TL system command and the LANGUAGE
option of the SYSOPS system command.
Example 4
After a security administrator issues the following two commands, both security
administrators and system administrators can use the SYSOPS system command.
Example 5
After a security administrator issues the following command, the system
administrator can issue a SQUASH system command, but the security administrator
cannot.
Example 6
After a security administrator issues the following command sequence, only the
security administrator can issue a SQUASH system command.
Example 7
After a security administrator issues the following request, only the security
administrator can issue a TL system command.
RESTRICT COMMAND TL
Syntax
<blocksize>
A positive integer. See "SYSOPS LMBLOCKSIZE <blocksize>" later in this section for
more information.
<catalog level>
An integer between 1 and 6, inclusive.
<chain length>
<rowsize>
The number 2000 or the number 4000.
<switch>
Explanation
SYSTEMOPTIONS
SYSOPS
Display the current values for each of the system options.
SYSOPS ALL
Display the current values for the system options and the possible values for these
options. If any values were changed in the same command input, the changes are
not displayed until after the next inquiry.
SYSOPS ABCDIAG
SYSOPS ABCDIAG MINIMUM
SYSOPS ABCDIAG MAXIMUM
SYSOPS ABCDIAG ON
SYSOPS ABCDIAG OFF
Displays or sets the value for ABCDIAG. This option should be performed only at the
request of Unisys support personnel to help diagnose an ABC channel problem. It is
valid only on an MCP compiled with the DIAGNOSTICS compile-time option. It
specifies how much diagnostic tracing information to gather for ABC channel activity.
Note: Setting the ABCDIAG option might seriously degrade system performance. It
should remain off except for relatively brief periods of time.
SYSOPS BACKUPFSDEFAULT
SYSOPS BACKUPFSDEFAULT ALIGNED180
SYSOPS BACKUPFSDEFAULT BLOCKED
SYSOPS BACKUPFSDEFAULT STREAM
Display or set the value for the BACKUPFSDEFAULT option. This option assigns the
default FILESTRUCTURE value for printer backup disk files. By default, the value is
ALIGNED180.
SYSOPS BCVRSVPS
SYSOPS BCVRSVPS <switch>
Display or set the value for the BCVRSVPS option. By default, the value is TRUE. If
the BCVRSVPS option is TRUE, a warning displays whenever the operator attempts to
acquire a BCV. If the option is FALSE, the warnings are suppressed and the BCVs are
acquired without operator intervention. If there are any BCV RSVPS waiting for the
operator when the BCVRSVPS option is set to FALSE, all the waiting entries are
acknowledged and the BCVs imported.
SYSOPS CATALOGLEVELSET
SYSOPS CATALOGLEVELSET <number>
Display or set the value for the CATALOGLEVELSET system option. Valid values for
CATALOGLEVELSET are the integers 1 through 6.
At sites that run with the OP + CATALOGING option set, the system uses this
number to determine the CATALOGLEVEL. That is, this value determines the number
of generations of a cataloged disk file or cataloged tape file that the system will keep
track of. A value of 1 means the system will allow two generations, 0 and 1; a value
of 2 means the system will allow three generations, 0, 1, and 2; and so forth. The
default value for CATALOGLEVELSET is 3.
When you change the value of CATALOGLEVELSET the new value applies to new
files. Existing resident disk files and existing nonresident disk and tape files will
continue to use the value under which they were originally created. To apply the new
value of CATALOGLEVELSET to an existing file, you can either remove or change the
name of that file, then use the WFL "CATALOG PURGE <file name> (PACK,
FAMILYNAME=<family>)" statement to delete all catalog information for the file, and
then restore the file or change the name of the file back to its original name.
SYSOPS CCSVERSION
SYSOPS CCSVERSION <ccsversion name>
SYSOPS CCSVERSION <ccsversion number>
Display or set the value for the CCSVERSION system option. If a new character set is
specified, it is implemented after the next halt/load. For more information about
what a ccsversion is and how to use it, refer to the MultiLingual System
Administration, Operations, and Programming Guide.
SYSOPS CIADIAG
SYSOPS CIADIAG MINIMUM
SYSOPS CIADIAG MAXIMUM
SYSOPS CIADIAG ON
SYSOPS CIADIAG OFF
Displays or sets the value for CIADIAG. This option should be performed only at the
request of Unisys support personnel to help diagnose a CIA problem. It is valid only
on an MCP compiled with the DIAGNOSTICS compile-time option set. It specifies how
much diagnostic tracing information to gather for FastPath CIA activity.
Note: Setting this option might seriously degrade system performance. It should
remain off except for relatively brief periods of time.
SYSOPS CONVENTION
SYSOPS CONVENTION <convention name>
Display or set the value for the CONVENTION system option. For more information
about what a convention is and how to use it, refer to the MultiLingual System
Administration, Operations, and Programming Guide.
SYSOPS COUNTRY
SYSOPS COUNTRY <country name>
COUNTRY is an alphanumeric string from 1 to 17 characters in length. The COUNTRY
string is not compared with any predefined values. The default system option
COUNTRY is UNITEDSTATES.
SYSOPS CREDENTIALS
SYSOPS CREDENTIALS DISABLED
SYSOPS CREDENTIALS MIGRATION
SYSOPS CREDENTIALS ENABLED
Display or set the value for the CREDENTIALS system option. This option controls
whether NX/Services uses password encryption for Windows workstations connecting
to the MCP environment. The effects of the possible values are as follows:
DISABLED
Client Access Services negotiates for plain text passwords when establishing
sessions with clients. When new passwords are created, and when passwords are
changed, they are not stored using the one-way encryption used by Windows
Networking.
MIGRATION
Client Access Services negotiates for plain text passwords when establishing
sessions with clients. When new passwords are created, and when passwords are
changed, they are stored using the one-way encryption used by Windows
Networking.
ENABLED
Client Access Services negotiates for credentials when establishing sessions with
clients. Credentials are derived from the clear text password using the one-way
encryption algorithm used by Windows Networking. When new passwords are
created, and when passwords are changed, they are stored using the one-way
encryption used by Windows Networking.
For more information about the CREDENTIALS option, refer to the Client Access
Services User Guide.
SYSOPS DIRECTPRINTER
SYSOPS DIRECTPRINTER = DIRECTDLP
SYSOPS DIRECTPRINTER = DIRECTPS
Display or set the value of the DIRECTPRINTER option. This option affects the
printing of printer backup files declared as DIRECT files or having a
PRINTDISPOSITION file attribute value of DIRECT. The DIRECTPRINTER option
values have the following effects:
DIRECTDLP specifies that DIRECT files can be printed only to devices attached
to printer DLPs.
DIRECTPS specifies that DIRECT files can be printed to any device controlled
by the Print System, except for virtual servers.
In addition, for any files declared with KIND = PRINTER and PRINTDISPOSITION =
DIRECT, the PRINTDISPOSITION value is changed to match that of the
DIRECTPRINTER system option.
SYSOPS ENABLEPOSIX
SYSOPS ENABLEPOSIX <switch>
Display or set the value for the ENABLEPOSIX option. Formerly, it was necessary to
set this option before using certain kinds of POSIX functionality, such as the
SECURITYMODE file attribute. However, these features are now available regardless
of whether this option is set or reset.
Although the ENABLEPOSIX option no longer controls any functionality, you can still
set or reset it. The feature enables you to control the option when you switch back to
earlier releases of the MCP.
SYSOPS ESR
Displays the current setting of the Electronic Service Request (ESR) option to control
the disposition of an ESR event.
Note: For information about ESRs, refer to the System Assistant Operations and
Programming Guide.
SYSOPS HOSTCCS
Displays the current status of the HOSTCCS option.
The <CCS Name> must be a member of the following approved CCS list:
ASERIESEBCDIC (4)
LATIN1EBCDIC (12)
LATIN5EBCDIC (14)
CANSUPPLEBCDIC (16)
LATINGREEKEBCDIC (19)
LATIN2EBCDIC (26)
LATINCYRILLICEBC (29)
ARABIC20EBCDIC (34)
LATIN9EBCDIC (47)
LOCALEBCDIC (50)
IBMSWEDENEBCDIC (51)
JAPANEBCDICJBIS8 (100)
EBCDICKSC5601 (105)
EBCDICGB2312 (111)
JAPANV24JBIS8 (114)
SYSOPS LABELFORMAT
Displays the ANSI standard being used to format tape labels when you create tapes.
The default is ANSI69DEFAULT.
If SECURITYLABELS attribute is set for the tape volume, the ANSI87 standard is used
to format the tape labels regardless of the setting of the LABELFORMAT option.
SYSOPS LANGUAGE
SYSOPS LANGUAGE <language name>
Display or set the value for the LANGUAGE system option. If a new system language
is specified, it is implemented after the next halt/load. For more information about
what a language is and how to use it, refer to the MultiLingual System
Administration, Operations, and Programming Guide.
SYSOPS LMBLOCKSIZE
Displays the current default block size (in words) that library maintenance uses for
disk sources, disk destinations, and tape destinations.
SYSOPS LMBLOCKSIZE = 0
Clears the value specified for LMBLOCKSIZE to zero, which directs library
maintenance to use its standard internal default values. These values depend on the
kind of disk or tape volume being used, as shown in the following table.
Depending on the kind of tape your installation uses, you can increase the default
block size to improve the performance of library maintenance tasks, and to increase
the amount of data that can be stored on library maintenance tapes. If you specify a
value of 5400 or more, the following benefits occur:
Processing time used for library maintenance runs is reduced by at least half.
Maximum Library
Tape Drive Name Density Maintenance Blocksize
When writing to tape volumes on tape units with special limits, library maintenance
automatically limits the block size it uses to conform to the allowable maximums
even if you specify a value that exceeds their limits. However, if you are copying files
to a tape volume that does not have limits, and that tape might later be read on a
tape unit that does have limits, you need to make sure that library maintenance
writes the tape with a block size that can be read on the target tape unit.
Second, the type of connection to a tape unit might also impose a limit on the
maximum block size that can be used. The soft or emulated controls (either a SCSI
DLP or Native SCSI Channel) limit the maximum block size of any tape connected to
it to 65535 bytes, which corresponds to a maximum library maintenance block size
of 10800 words. You can use the LOG CONFIG or LOG C CONFIG forms of the LOG
(Analyze Log) command to determine whether or not a given tape unit is attached to
an emulated SCSI. In the Unit Configuration section of the LOG CONFIG report,
tapes listed as SCSI with a firmware level of D101 or higher are emulated SCSI
DLPs.
SYSOPS LMENCRYPT
SYSOPS LMENCRYPT NO
SYSOPS LMENCRYPT TDES
SYSOPS LMENCRYPT AES256
Display or set the value of the LMENCRYPT system option. Library maintenance uses
the option to determine the default encryption option when copying data to tape. Use
NO (the default) to prevent library maintenance from encrypting the data that it
copies to tape. Use TDES to request that library maintenance use the triple DES
algorithm for encrypting all data being copied to tape. Use AES256 to request that
library maintenance use the AES256 algorithm for encrypting all data being copied to
tape. If you specify the ENCRYPT file attribute for a destination tape volume in a WFL
COPY statement, the value of the file attribute overrides the SYSOPS LMENCRYPT
option..
SYSOPS LMSINGLESPACE
SYSOPS LMSINGLESPACE <switch>
Display or set the value of the LMSINGLESPACE system option. This option can be
changed at any time and is reset by default. You can use this option to avoid file
sequence errors when copying files from an 18-track tape volume with a density of
BPI_38000 that is loaded on a 36-track OST5136 or CTS5236 tape unit. If you
specify the LIBMAINTSINGLESPACE file attribute for a source volume in a COPY
statement, the value of the file attribute overrides the SYSOPS LMSINGLESPACE
option.
SYSOPS LONGFILENAMES
SYSOPS LONGFILENAMES +
SYSOPS LONGFILENAMES SET
SYSOPS LONGFILENAMES TRUE
SYSOPS LONGFILENAMES YES
Display or set the value for the LONGFILENAMES system option. This feature makes
it easier for you to copy files with long names between Windows environments and
the MCP environment.
Setting LONGFILENAMES results in an RSVP message. The change does not take
place until you reply OK to the RSVP message and halt/load the system. After the
halt/load, the system migrates to a new file system that supports long file names.
For further information, refer to the System Administration Guide and the System
Operations Guide.
Note: Not all MCP environment utilities recognize long file names.
Caution
Both the sending and destination hosts must have the SYSOPS LONGFILENAMES
option set when a file transfer involves a file or files with node names exceeding
17 characters.
Migration to the new file system should be viewed as a one-time migration and
is not intended to be reversed. Once the system has migrated to the new file
system, you cannot use the SYSOPS command to return to the old file system.
Returning to the old file system results in the loss of all files with long names. If
you must return to the old file system, you need to use LOADER to cold start the
system on a new halt/load family.
SYSOPS NODATEOFFSET
SYSOPS NODATEOFFSET <switch>
Display or set the value for the NODATEOFFSET system option. The default value is
RESET. When you set this option, assignments to the DATEOFFSET task attribute are
not allowed. If a process tries to set this attribute, a warning message is displayed.
SYSOPS OPENTIMESTAMP
SYSOPS OPENTIMESTAMP <switch>
Display or set the value of the OPENTIMESTAMP system option. You can change this
option at any time. If OPENTIMESTAMP is set, the system stores a time stamp value
in the header of a disk file whenever that file is opened.
The OPENTIMESTAMP option is reset by default, because storing the time stamp
information at file open time incurs the extra overhead of a write action to the
system directory or system directories for the disk family on which the file resides.
You can display the open timestamp value of a disk file with the PD and PDRES
system commands or the CANDE LFILES command, or with the FILEDATA
ATTRIBUTES request.
You can programmatically retrieve the open timestamp information with the
GETSTATUS procedure or GETHEADERATTRIBUTE procedure, or with the new file
attributes OPENTIME, OPENDATE, OPENTIMEZONE, OPENTIMEUT, and OPENDATEUT.
SYSOPS PERMDIRECTORIES
SYSOPS PERMDIRECTORIES <switch>
Display, set, or reset the value for the PERMDIRECTORIES system option. When
PERMDIRECTORIES is set, privileged users can use the MKDIR command in WFL to
create the root permanent directory *DIR on specific disk families. Thereafter, users
can create permanent directories on those families. Permanent directories are similar
to the directories supported in Novell Netware and Windows environments. You can
use permanent directories to help control access to files that are shared among
groups of users. For further information, refer to the System Administration Guide
and the System Operations Guide.
SYSOPS PRESERVELH
SYSOPS PRESERVELH <switch>
Display, set, or reset the value for the PRESERVELH option. Changes to the
PRESERVELH option take effect immediately.
This option is meaningful only on IOP systems. On these systems, it controls I/O
firmware handling for local IOPs and channel adapter ports on ClearPath MCP
Release 8.0 and earlier software. It also controls I/O firmware handling for local IOPs
and channel adapter ports on ClearPath MCP Release 9.0 software levels older than
IC level MCP-050.1A.56. The older software levels do not support the enhanced LH
(Load Host) command syntax. Their behavior is described here for completeness, but
such behavior has been superseded on current software.
The default value of PRESERVELH is SET on old software levels that support
PRESERVELH to control firmware handling. On current software, the default value is
RESET.
On IOP systems, local IOP and channel adapter port devices can be loaded with new
operational firmware during initialization. Alternatively, they can be initialized to
continue using the last firmware that was loaded to them. Server Control puts a
complete set of I/O firmware images into high-end memory (HEM) when a partition
is started. These are the default firmware images used to initialize IOPs and ports
unless you specify otherwise.
On old software, the duration of an LH action to an IOP or port depends on both the
PRESERVELH setting and the HEM firmware level for the device. If PRESERVELH is
RESET, a device reverts to HEM firmware on any initialization. As long as
PRESERVELH is SET when a device is initializing, the current firmware remains.
However, the device reverts to the current HEM firmware if the HEM firmware is a
newer level than that currently loaded to a device. Regardless of the PRESERVELH
setting, a firmware older than the current HEM firmware for a device is never used.
Thus, the LH command cannot be used to load such firmware to devices when you
are using outdated software that supports firmware management based on
PRESERVELH.
whether this is the first initialization for a partition on software that uses enhanced
firmware handling. If it is, and PRESERVELH is SET, an implicit LH ALL :KEEP action
is performed, which forces all PCD firmware state toggles to the PERMANENT setting
and prevents the loss of any specially loaded firmware. Thereafter, current software
ignores the setting of PRESERVELH, except that it is explicitly RESET during system
initialization, with the following message being displayed for the operator to
acknowledge:
PRESERVELH OF SYSOPS HAS BEEN EXPLICITLY RESET. ON CURRENT MCP LEVELS, THIS
OPTION
HAS NO EFFECT ON IO FIRMWARE MANAGEMENT. YOU NEED TO CONSIDER SETTING THIS
OPTION
ONLY IF RETURNING TO OUTDATED SOFTWARE THAT DEPENDS ON THE PRESERVELH SETTING.
SYSOPS QUEUEDAX
SYSOPS QUEUEDAX <switch>
Display or set the value for the QUEUEDAX option. When you turn on the option, the
system can queue as many as 250 AX (Accept) messages for a task. If you turn off
the option, the system queues only one AX message for each task; subsequent
messages overwrite previous messages.
If you enter SYSOPS QUEUEDAX and the system has already queued some
messages, subsequent ACCEPT messages issued by the task continue to take
response messages from the front of the queue until the queue becomes empty.
However, the next AX command directed to a task produces the following results:
SYSOPS RSVPONTAPEERROR
SYSOPS RSVPONTAPEERROR <switch>
Display or modify the value for the RSVPONTAPEERROR system option. The default
value is RESET. This option, if SET, causes a tape drive to be saved automatically
and an RSVP message issued when an irrecoverable tape I/O error results in the
abnormal termination of a task.
SYSOPS SUPPRESSACTIVE
SYSOPS SUPPRESSACTIVE NONE
SYSOPS SUPPRESSACTIVE ALL
SYSOPS SUPPRESSACTIVE JOBS, LIBS, DBS
Display or set the value for the SUPPRESSACTIVE system option. The
SUPPRESSACTIVE system option controls whether jobs, freeze-control libraries, and
database task stacks are displayed in an Active Entries response. For the purpose of
this option, jobs include active jobs and tasks with no parent.
Note: The values JOBS, LIBS, and DBS can be listed in any order, as long as the
values are separated by commas.
SYSOPS SYSTEMDIRECTORY
SYSOPS SYSTEMDIRECTORY 2000
SYSOPS SYSTEMDIRECTORY 4000
The size limit for a SYSTEMDIRECTORY is 1000 AREAS. When you use the RC
PK<unit number> system command to create a new disk family, the size of the
AREAS depends upon the kind of disk and the SYSOPS SYSTEMDIRECTORY setting. If
the disk is a VSS2 disk or if the SYSOPS SYSTEMDIRECTORY value is 4000, the size
of the SYSTEMDIRECTORY AREAS for the new family is 4000 sectors. Otherwise, the
size is 2000 sectors.
To make space available in a SYSTEMDIRECTORY, you have to remove files from the
disk family.
SYSOPS TAPEMANAGER
SYSOPS TAPEMANAGER <switch>
Display or modify the value for the TAPEMANAGER system option. The default value
is RESET.
SYSOPS TAPESERVER
SYSOPS TAPESERVER <switch>
Display or modify the value for the TAPESERVER system option. The default value is
RESET.
SYSOPS TAPEEXPIRATION
SYSOPS TAPEEXPIRATION <switch>
Display or set the value for the TAPEEXPIRATION system option. The default is TRUE.
When the MCP reads the labels on a tape and this option is FALSE, the MCP ignores
the expiration date of the tape. When the MCP reads the labels on a tape and this
option is TRUE, the MCP treats the tape as a scratch tape if the current date is past
the expiration date, the tape is write-enabled, and the tape is labeled an ordinary
data tape. Library maintenance tapes and printer backup tapes are never treated as
scratch tapes.
SYSOPS TAPEOVERWRITE
SYSOPS TAPEOVERWRITE <switch>
Display or set the value for the TAPEOVERWRITE system option. This option
determines whether the system assigns an output tape file to a given tape volume in
cases where all the following conditions are true:
The tape file has a non-null SERIALNO value matching the serial number of
the tape volume.
The tape volume is write enabled.
The tape volume is not a scratch tape.
In this situation, if TAPEOVERWRITE is TRUE, then the system assigns the output file
to the tape volume. If TAPEOVERWRITE is FALSE, then the system does not assign
the output file to the tape volume. The default value of TAPEOVERWRITE is TRUE.
SYSOPS UDCHAINLENGTH
SYSOPS UDCHAINLENGTH <chain length>
Display or set the value for the UDCHAINLENGTH system option. The
UDCHAINLENGTH system option controls the generation of a warning message when
the number of index overflow blocks in the USERDATAFILE becomes too large. A
value of 0 inhibits the warning message. The warning is generated only once every
halt/load; however, the warning status is reset whenever the option is assigned
(assigning the existing value is sufficient to reset the status).
SYSOPS WARNFACTOR
Displays the current value for the WARNFACTOR option and the approximate System
Software Release (SSR) at which the code files will expire.
The WARNFACTOR option determines which code files receive recompilation warning
messages when they are executed. The warning message indicates that the code file
must be recompiled in order to run when the system is upgraded. The system
displays the warning message each time it executes a code file that requires
recompilation to run on the SSR level subsequent to the displayed SSR.
software within the near future, but does expect to upgrade before the end of the life
cycle of the current software level.
SYSOPS WFLPERIODS
SYSOPS WFLPERIODS ALLOWED
SYSOPS WFLPERIODS WARNING
SYSOPS WFLPERIODS ERROR
Display or set the value of the WFLPERIODS option. This option determines how a
period in an unquoted node of a file title is handled when the file title is in a string
variable assigned to a file, task, or library attribute that is file title-valued. By
default, the value is ALLOWED.
A value of ALLOWED means that the period is treated as part of the file title. A value
of WARNING means that the period is treated as a terminator, and a warning is
generated. A value of ERROR means that file title will be treated as invalid, and the
job will terminate with a run-time error.
SYSOPS WRAPNOWAIT
SYSOPS WRAPNOWAIT <switch>
Display or modify the value for the WRAPNOWAIT system option. The default value is
RESET. This option, if set, prevents processes from waiting for an RSVP when a wrap
is attempted without the presence of the wrap license key. If the wrap license key is
not present, the files are wrapped for Unisys support use only.
Examples
Example 1
The following example sets a new value for the CCSVERSION system option:
----------------------------SYSTEM OPTIONS---------------------------
Example 2
Use the following example when you want to indicate that all subsequent tapes are
to be created with the ANSI87 standard format. Note that a LABELFORMAT task
attribute can override the SYSOPS LABELFORMAT specification.
------------------------SYSTEM OPTIONS-------------------------------
LABELFORMAT is ANSI87DEFAULT
Example 3
Use the following example when you want the system to call a TAPEMANAGER library
for tape file requests:
Example 4
Use the following example to indicate that the MCP is to ignore the expiration dates
on tapes when it reads tape labels:
Example 5
SYSOPS QUEUEDAX TRUE
Example 6
SYSOPS ESR UNCONDITIONAL
Syntax
Explanation
The TD command displays the time, day, date, and time zone being used by the
system. The date is displayed both as a calendar date and a Julian date. The form
yyyyddd is used for the Julian date, indicating the year yyyy and day of the year
ddd. The time is displayed in 24-hour format in digits denoting hours, minutes, and
seconds, respectively. The time zone is set using the TR (Time Reset) command.
<timezone>
This optional entry enables you to display the time and date when your location is in
a different timezone than the host. The <timezone> is any of the character string
entries described in the TIMEZONE handling portion of the TR (Time Reset)
command.
Example
TD
Syntax
Explanation
TDIR <unit number>
TDIR <volume name>
List the directory of the tape volume that is mounted on the specified unit or that has
the specified volume name.
You can intermix volume names and unit numbers. You must use the unit number
instead of the volume name if you are specifying the n th reel of a multireel library
dump.
If you do not specify any of the output options, such as SCREEN or SPO, the system
sends the output to the printer.
The system does not send the directory display to the originating ODT if one of the
following circumstances exists:
In such a case, the system performs a search to find the first available ODT. If it
does not find an available ODT, SYSTEM/FILEDATA becomes a waiting entry with an
RSVP message that says FILEDATA REQUIRES SC.
Examples
Example 1
The following example shows a TDIR command for a library maintenance tape
named DAILYLOGMPA15AB and the directory listing that FILEDATA produces.
*SUMLOG/503/041105/007933 ON DISKB,
*SUMLOG/503/041105/007934 ON DISKB,
*SUMLOG/503/041105/007935 ON DISKB,
*SUMLOG/503/041105/007936 ON DISKB,
*SUMLOG/503/041105/007937 ON DISKB,
Example 2
The following example shows a TDIR command for a CD-ROM named SYSTEM_49150
and the report that FILEDATA produces.
TAPE DIRECTORY
TERM (Terminal)
The TERM (Terminal) command controls the format of all displays appearing on the
ODT at which the command is entered.
Syntax
Explanation
TERM
Displays the current terminal settings.
The default value is FALSE. Unless this option is explicitly set, terminals are not
affected.
FALSE is the default value and specifies that messages coming from the system are
not to be displayed when they are first received. However, these messages appear in
the messages portion of the ADM display or in response to the MSG command.
TRUE specifies that system messages, when first displayed, are to be truncated on
the right if their length exceeds the value specified in the WIDTH clause. TRUE is the
default value.
FALSE specifies that any incoming message that is longer than the value given in the
WIDTH is to be continued on subsequent lines.
TERM USER
Dissociates a usercode from that ODT.
Examples
Example 1
This example shows a normal response from a TERM inquiry.
TERM
Example 2
This example changes the language in which responses are to be displayed at the
terminal to French.
Example 3
This example attempts to change the language in which responses are to be
displayed at the terminal to Hindi. The system responds that Hindi is not a language
that can be displayed by the MCP.
Syntax
Explanation
The THAW command changes the state of the specified permanently frozen and
freeze-control libraries. Permanently frozen libraries are changed to temporary
libraries. For freeze-control libraries, bit [27:1] in the LIBRARYSTATE task attribute
of the library is reset and the EXECEPTIONEVENT task attribute results.
A permanently frozen library remains in the mix regardless of whether any users are
attached to it.
A freeze-control library remains in the mix until it exits its control procedure when it
becomes a temporary library.
A temporary library stays in the mix only as long as a user is attached to it.
Use the LIBS (Library Task Entries) command to display libraries and their mix
numbers.
Example
2340 THAW
TI (Times)
The TI (Times) command displays the current values of the time accumulators and
any limits on processor time, I/O time, and elapsed time for tasks.
Syntax
Explanation
<mix number list> TI
Displays the current values of the time accumulators and any limits on processor
time, I/O time, elapsed time for tasks, and task start time.
Example
5285 TI
PROCESS = 0:00:37
IO = 0:00:01
READYQ = 0:00:56
INITPBIT = 0:00:06 3,217 OPERATIONS
OTHERPBIT = 0:00:02 1,521 OPERATIONS
ELAPSED = 0:11:40
BOT = Thursday, May 10, 2001 (2001130) AT 14:06:30
TL (Transfer Log)
The TL (Transfer Log) command releases the current system log file and starts a new
one. The space allocation factors for the new file (the number of rows and the
number of records per row) can be changed if so desired. The space allocation
factors for the current system log can also be displayed.
Syntax
Explanation
TL
Releases the current SUMLOG and SECURITYLOG files, and starts new ones with the
same space allocation factors as the released files. The current files reside on the DL
LOG family. The space allocation factors are the AREAS and AREASIZE file attributes,
as described in the File Attributes Programming Reference Manual.
When a TL command results in new log files, the previous log files are named as
follows:
SUMLOG/<system number>/<mmddyy>/<number>
SECURITYLOG/<system number>/<mmddyy>/<number>
In these file names, <number> is a log serial number from 000001 through 065535.
A cold-start resets the log serial number back to 000001. To relate the two log files
as unambiguously as possible, the number used for the current SUMLOG is also used
for the current SECURITYLOG. The number is not computed independently for the
two files.
The security-related file attributes of the old files are automatically transferred to the
corresponding new files.
TL *
Displays the values of the space allocation factors of the current SUMLOG and
SECURITYLOG. The display includes:
TL ROWS <number>
TL RECORDS <number>
TL ROWS <number> RECORDS <number>
Releases the current SUMLOG and SECURITYLOG files and starts new ones with the
specified space allocation factors, where
The ROWS parameter corresponds to the AREAS file attribute, and can range
from 100 to 1023. For IOP systems the ROWS parameter can range from 25
to 1023.
The RECORDS parameter corresponds to the AREASIZE file attribute, and can
range from 1000 to 64000, in multiples of 1000. For IOP systems, the
RECORDS parameter can range from 4000 to 64000.
The new SUMLOG and SECURITYLOG files receive a titles and security-related
attributes as previously described for the simple TL form of the command.
Examples
Example 1
This example releases the current SUMLOG and SECURITYLOG files and creates new
ones:
TL
Example 2
This example displays the values space allocation factors of the current SUMLOG and
SECURITYLOG files:
TL *
Example 3
This example releases the current SUMLOG and SECURITYLOG files and creates new
ones with 650 rows and 7000 records per row:
TR (Time Reset)
The TR (Time Reset) command changes the system time used by the MCP. It can
also change the date and set the time zone.
If the Time Synchronization product is active, the operator should avoid manual time
changes using the TR command. For further information, refer to "Time
Synchronization" in the TCP/IP DSS Operations Guide.
Note: If the DRTRRESTRICT system option is set, you cannot change the system
date or time. However, you can still use the TR command to change the time zone.
The DRTRRESTRICT option is set through the OP (Options) command.
Syntax
<time>
<number>
Integers that represent hours and minutes in the range from 0000 through 2359.
<hours>
An integer in the range from 0 through 23. If AM or PM follows the <time>
specification, the range is from 1 through 12.
<minutes>
An integer in the range from 0 through 59.
<seconds>
An integer in the range 0 through 59.
<date>
<day of week>
<day of month>
The day of month is an integer in the range 1 through 31.
<month>
<year>
Year is a 4-digit integer.
<time zone>
Note: The use of custom time zones is not recommended because they cannot be
converted to internal time zone numbers. If a custom time zone is specified, a
warning message appears when the system is halt/loaded.
<offset>
<abbrev>
A string of from 1 to 6 letters.
Each site can specify its own time zone using the following guidelines:
The value for the <hours> parameter must be within the range of 0 through
23.
The value for the <minutes> parameter must be within the range of 0
through 59.
The value for the <name> parameter is the name of the time zone. This
value can be a maximum of 35 characters. The name can be up to 35
characters enclosed within quotation marks (" "). The name value can not
include quotation marks.
The value for the <abbr> parameter is the abbreviation of the time zone
name and can be a maximum of 6 characters enclosed within parentheses.
Parentheses cannot be specified as part of the time zone abbreviation.
<universal time zone>
No spaces can be entered between the quotation marks ("). The first number
indicates the hours of offset from universal time to local time. The hours can be in
the range 11 through +13. The second number in the syntax diagram indicates the
minutes of offset from universal time to local time. The minutes can be 00, 30, and
in four cases, 45. Only certain combinations of hours and minutes are valid. Refer to
the following table for a list of valid universal times and the predefined time zones
with which they correspond, if any.
UT - 11:30
UT - 11:00
UT - 10:30
UT - 9:30
UT - 8:30
UT - 7:30
UT - 6:30
UT - 5:30
UT - 4:30
UT - 1:30
UT - 1:00
UT - 0:30
UT + 0:30
UT + 1:30
UT + 2:30
UT + 3:30
UT + 4:00
UT + 4:30
UT + 5:00
UT + 5:45
UT + 6:00
UT + 6:30
UT + 6:45
UT + 7:00
UT + 7:00
UT + 7:30
UT + 8:30
UT + 11:30
UT + 12:30
UT + 12:45
UT + 13:45
Explanation
The TR command must contain one or more of the time, date, and time zone
options. You cannot enter TR by itself.
TR <number>
Changes the system time to the time specified by <number>, which must be a 3-
digit (hmm) or 4-digit (hhmm) integer. The last 2 digits specify the minute (00
through 59), and the first 2 (or 1) specify the hour (00 through 23).
TR <number>:<number>
Changes the system time to the specified time. The first number specifies the hour
(00 through 23), and the second number specifies the minute (00 through 59).
TR <number>:<number>:<number>
Changes the system time to the specified time. The first number specifies the hour
(00 through 23), the second number specifies the minute (00 through 59), and the
third number specifies the second (00 through 59).
However, you cannot change the time if it will cause a date change. For example, if
the time is 23:00, you can use the relative time change mechanism to set the clock
back 22 hours to 01:00 the same day, but you cannot use the relative time change
mechanism to set the clock ahead 2 hours to 01:00 the next day. You must specify
both a time change and a date change together. For example, you must set the clock
back 22 hours and the date to the next day simultaneously, thus setting the clock to
01:00 and the date to the next day.
You should avoid using custom time zones. The system stores time and date
information for disk files with the time zone number. Custom time zones do not have
a time zone number. When you copy or transfer disk files from a site that uses a
custom time zone to other sites, the time and date information for those files might
become confused.
Examples
Example 1
This example shows the way to correct the time of day kept by the system. A TD
(Time and Date) command has shown that the system is using a time of 6:04, but
the correct time is 7:15.
TR 0715
The operator enters OK and uses the TD (Time and Date) command to display the
time. (Thirty seconds elapse between the TR and TD commands.)
2345 OK
TD
Example 2
This example shows the way to correct the data and the time of day kept by the
system. A TD command has shown that the system is using a time of 7:10 and a
date of September 11. However, the correct time is 00:15, and the correct date is
September 10.
3456 OK
Because the change involves more than 15 minutes' difference, the system creates
another waiting entry:
The operator confirms the request and uses the TD (Time and Date) command to
display the new time and date:
3456 OK
TD
Example 3
In this example the operator enters a TR command to change the time of day kept
by the system from 12:24 PM to 12:33 PM. The system indicates that a response
might be needed, and the operator displays the waiting messages:
TR 12:33 PM
There are no waiting messages, which indicates that the time change was made. The
operator uses a TD (Time and Date) command to display the time.
The display shows that the time was changed and that four seconds have elapsed
since the change.
TD
Example 4
In this example, the operator sets the local time zone used by the system to Pacific
Daylight Time.
TR TIMEZONE PDT
There are no waiting messages, which indicates that the time zone change was
made. The operator uses a TD (Time and Date) command to display the time. The
display shows that the time zone was changed.
TD
A forward time change of more than 15 minutes results in a waiting entry with the
following form:
If you enter OK and the difference is more than 15 minutes, a second waiting
message is created. This message indicates the difference, as shown in the following
example:
MCP Environment
In the MCP environment, use the TR command.
Windows Environment
In the Windows environment, from the Start menu, point to Settings, choose Control
Panel, and then Choose Date and Time.
When the Date and Time Properties dialog box appears, make your time changes.
Note: Do not use the Time Zone tab option labeled Automatically adjust time for
daylight savings changes.
TV (Type Volume)
The TV (Type Volume) command displays the volume name, status, ownership, and
security attributes of any tape volume listed in the volume directory. This command
is valid only for installations that run with the security option SECOPT TAPECHECK
equal to AUTOMATIC.
Syntax
Explanation
TV MT <serial number>
Displays information for the tape volume specified by <serial number>.
Examples
Example 1
TV MT 001002
Example 2
TV MT MYTAPE
U (Utilization)
The U (Utilization) command displays the current system utilization statistics.
For systems that support SLICERATE adjustment, the lower the SLICERATEthat is,
the fewer the number of process switches per second for a given prioritythe better
compute-bound tasks run. Up to a point, the higher the SLICERATE, the better I/O-
bound tasks run. For a general mix, the SLICERATE should be in the range from 30
to 90 slices per second. The most efficient tuning usually comes from using a
moderate SLICERATE and tiered job priorities, where the system gives compute-
bound jobs relatively lower priorities and I/O-bound jobs relatively higher priorities.
The risk of setting a SLICERATE too low is poor I/O service. The risk of setting a
SLICERATE too high is poor processor utilization, because the processor must switch
between stacks at a much higher rate, which makes poorer use of processor memory
caching.
The U command can be a parameter for time-driven automatic display mode (ADM).
For information, refer to ADM (Automatic Display Mode).
The U command displays the number of standard and special purpose processors. A
nonzero value for the special purpose processors implies that a number of active
Java processors are on the system.
Syntax
Explanation
U
UTIL
UTILIZATION
Display the current system utilization statistics, including percentages of central
processor unit (CPU), I/O, master control program (MCP), and total system use. The
statistics display is always divided into two parts: processing utilization statistics and
I/O utilization statistics. It includes disk cache and memory disk utilization statistics
if the system is using these features.
U ALL
UTIL ALL
UTILIZATION ALL
Display only the processing utilization statistics for all active processor sets on the
system. I/O, disk cache, and memory disk statistics are not included in the display
when the ALL option is used.
Examples
Example 1
The following example shows the response to the basic U command:
Example 2
The following example shows the response to the U ALL command:
U ALL
Example 3
The following example shows the response to the U ALL command for a system that
supports custom processor sets:
U ALL
Component Description
Component Description
Initial Pbit The percentage of processor time spent making arrays and
code present initially.
The displayed value does not include time spent overlaying
existing data to make room for new data. (Overlay time is
charged to the OTHERPBIT and SEARCHLEAD accounts.)
A presence bit (p-bit) on a read-write array is considered
initial if it has not been used previously (it is not overlaid). A
p-bit on a read-only array or a code segment is initial if it has
not been used during the current instance of the code stack.
(When two stacks run the same code file at the same time,
they often share a single code stack.)
Other Pbit The percentage of processor time spent making arrays and
code present again after they were overlaid, and time spent
overlaying existing data to make room for new data. (Time
spent searching stacks during the overlay process is not
included.)
When other pbit times are being collected during demand
overlay, the pbit is charged against a global pbit account,
rather than against any task. The U command display and
FIND MIX are both accurate, but FIND MIX does not find
globally charged times.
Component Description
SEARCHFOLLOW
Processor time spent during an interrupt by another
processor doing an overlay search. One or more
processors are running stacks having visibility to the
subject of an overlay search.
True Idle The percentage of processor time spent idle that is not
considered to be false idle time.
False Idle The percentage of processor time spent idle while overlaid
data is being transferred by the I/O subsystem.
The term false idle is used because during this time the
processor might have been working on tasks waiting for
overlay I/O operations if overlays were not needed. The false
idle percentage indicates that overlay is causing some tasks
to experience increased turnaround time. It is not necessarily
a measure of how much work exists that would be performed
if overlay were not a factor.
Using OLAYGOAL for algorithms can force overlay, and lead to
false idle time. If the number of idle processors exceeds the
number of tasks that are waiting for overlay I/Os and other
PBIT I/Os to complete, the number of processors whose time
is charged to false idle is equal to the latter number.
I/O Utilization
The I/O utilization statistics are divided into five components. Each component is
described in rates calculated over the last time interval. The time interval can vary,
and is set by the SBP command.
Component Description
User The average number of user I/O operations per second and the
number of kilobytes of data transferred per second by user I/Os.
MCP The average number of MCP I/O operations per second and the
number of kilobytes of data transferred per second by MCP I/O
operations. MCP I/O operations include such functions as overlay
and logging.
DC The average number of data comm I/Os per second and the
number of kilobytes of data transferred per second by the data
comm I/O operations. Data comm I/O operations transfer
messages between EDCDLPs, DCHAs, or ICPs.
Total The total system I/O activity made up of user I/O operations and
MCP I/O operations (plus or minus 1).
I/O The average number of I/O interrupts per second during the time
Interrupts interval.
These components are repeated if memory disk is used, with the exception of data
comm I/O. The memory disk utilization data includes I/O for memory disk units only.
UL (Unlabeled)
The UL (Unlabeled) command, which is used in response to a NO FILE message,
assigns an unlabeled file on an indicated unit to a task.
Syntax
Explanation
<mix number> UL <device type> <unit number>
Assigns the unlabeled file located on the specified device to the task with the
specified mix number:
Example
This example shows a UL command that is entered in response to a NO FILE
message in the waiting entries queue. The system assigns an unlabeled file on
MT113 to the task with the mix number 4363.
-----WAITING ENTRIES-----
4361/4363 50 SYSTEM/DUMPALL
NO FILE DUMPALLDMPMT
4363 UL MT113
UP (Up Resource)
The UP (Up Resource) command enables an active group to acquire additional
resources, or to change the TEMPORARY status of already acquired units and
controls.
Note: UP is a synonym for ACQUIRE. Use UP on IOP systems. Use ACQUIRE on IOM
systems.
Syntax
<CTL specification>
<unit specification>
Note: For Libra Model systems, you can separate the variables with either hyphens (-) or
underscores (_).
<pod>
An integer from 0 through 3 that identifies a particular pod on an IOP system.
<subpod>
An integer (either 0 or 1) that identifies a particular pod on an IOP system.
<IP unit>
An integer from 0 through 3 that identifies an instruction processor within a subpod
on an IOP system.
<mio>
An integer (0 or 1).
<bus>
An integer identifying a PCI bus within a PCI bridge or IONODE on an IOP system.
Valid numbers are 1 through 3 for a Libra Model 185 or 500 Series system and 0
through 7 for a Libra Model 680 or 690 system.
<cell>
An integer from 0 through 3 that identifies a particular cell on a Libra Model 680 or
690 system.
<unit>
An integer from 0 through 7 that identifies a processor within the cell.
Explanation
UP CTL <CTL number list>
Acquires the CTLs identified by the device numbers in the device number list and
brings those CTLs online. This syntax can be used to permanently add to the running
group CTLs that were previously acquired with the :TEMPORARY or :TEMP option.
This form of the command might also be a necessary step in recovering from certain
CTL or PORT failures. You might need to perform the following steps to recover CTLs
that are involved in such failures:
UP IP-<pod>-<subpod>-<IP unit>
Acquires the specified IP (instruction processor) into the partition.
UP PCI-BUS-<pod>-<mio>-<bus>
UP PCI_BUS_<cell>_<bus>
Acquires the specified PCI bus or buses into the partition. The associated IONODE is
also acquired if it is detached (down). Server Sentinel must be available to perform
the request. Multiple PCI buses can be specified in a single request.
The operator must enter the RY IOP command to use any IOPs served by buses after
they have acquired additional resources by means of the UP command.
Special Considerations for Libra Model 185 and 500 Series Systems
The request must conform to the platform rules enforced by Server Sentinel. An UP
command cannot be performed on PCI-BRIDGE-x-y or PCI-BUS-x-y-z if any of the
following are acquired (up) in another partition:
SUBPOD-x-0
SUBPOD-x-1
IP-x-0-0 through IP-x-0-3
IP-x-1-0 through IP-x-1-3
PCI-BRIDGE-x-0
PCI-BRIDGE-x-1
PCI-BUS-x-0-1 through PCI-BUS-x-0-3
PCI-BUS-x-1-1 through PCI-BUS-x-1-2
Special Considerations for Libra Model 600 Series Systems
The request must conform to the platform rules enforced by Server Sentinel. For
example, PCI_BUS_<cell>_<bus> cannot be acquired in a partition if
PROCNODE_<cell> is acquired in another partition.
UP IONODE_<cell>
Acquire the specified IONODE into the partition. The IONODE must be down (see
DOWN command) and be defined in the PCD for the partition requesting the
acquisition. Server Sentinel must be available to perform the request. The request
must conform to the platform rules enforced by Server Sentinel. For example,
All I/O activity is automatically suspended as part of the UP request, causing a pause
that can last from several seconds to a few minutes. I/O activity resumes upon
completion of the request. The UP request allows multiple IONODEs to be specified
in a single request so several IONODEs can be acquired with only one pause in I/O
activity.
The operator can specify multiple PCI_BUS entries to also acquire PCI buses served
by the bridge. If no PCI_BUS entries are in the list, the command automatically
acquires all PCI buses associated with the IONODE. If any PCI bus connected to the
IONODE is specified, the remaining unspecified buses connected to the IONODE are
left in their original state.
The operator can use the RY (Ready) command to use any IOPs served by the bridge
or bridges and buses after they are acquired.
UP PCI-BRIDGE-<pod>-<mio>
Acquire the specified PCI bridge into the partition. The bridge must be down (see
DOWN command) and be defined in the PCD for the partition requesting the
acquisition. Server Sentinel must be available to perform the request. The request
must conform to the platform rules enforced by Server Sentinel. For example, a
bridge cannot be acquired in a partition if another component of the module is
acquired in another partition.
All I/O activity is automatically suspended as part of the UP request, causing a pause
that can last from several seconds to a few minutes. I/O activity resumes upon
completion of the request. The UP request allows multiple PCI bridges to be specified
in a single request so several bridges can be acquired with only one pause in I/O
activity.
The operator can specify multiple PCI-BUS entries to also acquire PCI buses served
by the bridge. If no PCI-BUS entries are in the list, the command automatically
acquires all PCI buses associated with the bridge. If any PCI Bus connected to the
bridge is specified, the remaining unspecified buses connected to the bridge are left
in their original state.
The operator can use the RY (Ready) command to use any IOPs served by the bridge
or bridges and buses after they are acquired.
UP SUBPOD-<pod>-<subpod>
Acquires all IP units corresponding to the specified subpod into the partition.
UP IP_<cell>_<unit>
Acquires the specified IP (instruction processor) into the partition.
UP PROCNODE_<cell>
Acquires all IP units in the specified cell into the partition.
Examples
Example 1
This example acquires multiple PCI buses.
UP PCI-BUS-3-1-2 PCI-BUS-2-0-1
PCI-BUS-3-1-2 WILL BE UP
PCI-BUS-2-0-1 WILL BE UP
Example 2
This example acquires a PCI bridge and all associated PCI buses.
UP PCI-BRIDGE-2-0
PCI-BRIDGE-2-0 WILL BE UP
Example 3
This example acquires a PCI bridge and only one of its associated buses.
UP PCI-BRIDGE-2-0 PCI-BUS-2-0-1
PCI-BRIDGE-2-0 WILL BE UP
PCI-BUS-2-0-1 WILL BE UP
Example 4
This example acquires an IONODE and all associated PCI buses.
UP IONODE_1
IONODE_1 WILL BE UP
Example 5
These two examples acquire IONODE_2 and only one of its associated buses,
PCI_BUS_2_3.
UP IONODE_2 PCI_BUS_2_3
UP PCI_BUS_2_3
IONODE_2 WILL BE UP
PCI_BUS_2_3 WILL BE UP
UQ (Unit Queue)
The UQ (Unit Queue) command displays unit queue assignments and assigns jobs
from input units to a job queue. The UQ command is only meaningful when <device
type> is SC.
All jobs started at a unit that has a queue assignment pass through the assigned
queue. If the job control card contains a class assignment, the system checks the
class of the job against the class of the unit. If the classes are not the same, the job
is discontinued.
If the queue for a unit that has a class assignment was eliminated with an MQ
command, all jobs subsequently entered through that unit are discontinued. Refer to
MQ (Make or Modify Queue).
Syntax
Explanation
UQ
Displays the current unit queue assignments.
Examples
Example 1
This example shows a query and response about unit queue assignments.
UQ
Example 2
This example requests that the system display the default unit queue for device SC
2.
UQ SC 2
QUEUE FOR SC 2 IS 7
Example 3
This example deletes a default unit queue for device SC2.
UQ-SC2
NO DEFAULT FOR SC 2
UR (Unit Reserved)
The UR (Unit Reserved) command reserves units so that maintenance can be
performed, or it makes previously reserved units available for normal use.
The UR command with the MAINT option enables or disables maintenance access to
peripherals, controls (CTLs), or ports.
Note: A pack must be closed before it is reserved. You can use the CLOSE (Close
Pack) command to ensure that the pack is closed prior to using the UR command.
The UR command is not valid for online mirrored packs. You must release a pack that
is part of a mirrored set by using the MIRROR RELEASE command before you can use
the UR command.
If the command is rejected, wait for the current command to complete and enter the
command again.
Syntax
Explanation
UR <device type> <unit number list>
UR <device type> <unit number list> MAINT
Reserve the units identified by the device type and the unit number list. If you
specify MAINT, the system enables maintenance access to the device. MAINT is valid
only for packs.
Examples
Example 1
This example makes the designated port an unavailable path for I/O operations:
UR PORT 1002
Example 2
This example causes the system to resume I/O operations for the designated port:
UR - PORT 1000
Example 3
This command reserves a Telephony Services Platform (TSP) unit:
UR TSP 200
TSP200 RESERVED
Example 4
This example makes a previously reserved TSP unit available for use:
UR - TSP 200
TSP200 AVAILABLE
Example 5
This example takes an active IOU out of service:
UR IOM 1 IOU 1
Example 6
This example shows an attempt to take a distinguished IOU out of service:
UR IOM 0 IOU 1
Reserving a Peripheral
The UR command can reserve a peripheral only if all the following conditions are
true:
The peripheral has previously been acquired by the executing partition and is
not already reserved.
The peripheral is not in use. Packs must be closed and must not be part of a
mirrored set.
There is an available path from the executing partition to the peripheral. This
condition is required only when the MAINT option is used.
The peripheral is not critical. Critical peripherals are packs the system needs,
such as the halt/load family, the OVERLAY family, the JOBS family, the
CATALOG family, and the LOG family.
Reserving a Port
The UR command can reserve a control or a port only if the following conditions are
true:
The device has previously been acquired by the executing partition and is not
already reserved.
There is an available path from the executing partition to the device. This
condition is required only when the MAINT option is used.
The device is not in the last available path to any critical peripheral.
Reserving a DTU
The UR command can reserve a DTU only if the device is not already reserved.
In this message, mix number is the mix number of the UNITHANDLER and unit
number is the physical unit number of the ODT being reserved.
If you enter <mix number> OK, the ODT is reserved and the system does not have
ODT access until the next halt/load. If you enter <mix number> DS, the ODT is not
reserved.
During a halt/load, if there are no ready ODTs, the system tries to ready an existing
ODT. If there are no ODTs on the system and the run-time operating system option
AUTORUNNING (15) is reset, the system performs a nonfatal dump. System
initialization completes without a ready ODT; however, communication with the
system operator is not possible.
UR TSP 200,201,202,203
UR - TSP 200,201,202,203
You must enter a separate UR or UR CTL <device number> command to affect the
TSP CTL.
USERLICENSE
The USERLICENSE command assigns or displays user license information.
The RSVP goes away if the number of concurrent users falls 5 percent below the
warning percentage. The warning percentage can be changed, and defaults to
90%.
This first time the number of concurrent users exceeds the number of licensed
users, the following RSVP message is displayed, and the logon is allowed:
Warning! User Licenses for <product> (<release>) have been exceeded,
grace period will expire in 60 days
This event initiates a 60-day grace period during which the number of licensed
users can exceed the licensed amount. The purpose of this grace period is to give
you time to purchase additional licenses. Once the 60 day grace period is
initiated, the following reminder is generated everyday at midnight:
Reminder: <product> (<release>) exceeded the number of licenses on <date>.
The grace period will expire in <number> days. After the grace period has
expired, only <licensed users> users may use the product simultaneously.
To suppress these daily warnings, use 'USERLICENSE NOWARN <product> <release>'.
When the number of concurrent users exceeds the number of licensed users
and the grace period has expired, the system displays the following RSVP
message and denies the log on:
Warning! User Licenses for <product> (<release>) have been exceeded,
grace period has expired
On systems other than LX systems, user licenses are enforced only for the SOMS
product; for all other products, you can use the USERLICENSE command to display
the number of users.
For further information about user licensing, refer to the User Licensing Installation
and Operations Guide.
Syntax
<product>
One of the following values:
CLIENTACCESS
DATAACCESS
SOMS
TRANSSERVER
<percent>
An integer between 0 and 100
<release>
A release level, where 51.1 and 10.0 refer to products released with ClearPath MCP
Release 10.0.
Explanation
USERLICENSE
Displays the current state of user license information for all products. The display
includes the product name, the release level, the number of active users, the peak
number of concurrent users, the warning percentage, the number of licenses
available, and the grace period date. Attempts to use more licenses than are
available after the grace period date are denied.
A display of "[None]" for the number of licenses available signifies that user licensing
is not enforced for this product; whereas a display of "None" signifies that an
unlimited user license has been found.
If there are no active users and the grace period is not active, this command deletes
the entry for the specified level of the product. If there are active users, the entry is
not deleted, but the peak user count is set to 0. If the grace period is active, the
command is rejected.
Examples
Example 1
Following is a display from an LX Series system:
USERLICENSE
An asterisk (*) appears in the Warn column if the number of active users has
reached the specified percentage of available licenses.
The Grace Period column contains the date when active users will no longer be able
to exceed the number of available licenses. If the date has passed, and an attempt is
made to exceed the number of available licenses, the date appears in parentheses.
Example 2
The following display is from a system other than an LX system:
USERLICENSE
Example 3
The following command sets the warning percentage:
USERLICENSE TRANSSERVER 85
Example 4
The following command removes user license information for Transaction Server
(formerly COMS):
User License information for TRANSSERVER (release 50.1) has been deleted
Example 5
The following command suppresses the daily warnings for the ClearPath MCP Release
10.0 version of Client Access Services (formerly NX/Services):
Syntax
<wild card>
<delim>
Use one of the following characters
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters:
Character Description
You can include lowercase characters and space characters by prefixing the wild-card
string with LIT and enclosing the wild-card string in delimiters.
For example, if you enter the following syntax, the system returns entries that
contain the string "PACK":
W NAME =pack=,
If you enter the following syntax, the system returns entries that contain the string
"pack":
Explanation
W
Displays all waiting jobs or tasks.
W QUEUE
WQ
Display waiting jobs and tasks from all queues.
W USER <usercode>
Displays only waiting jobs and tasks running with the specified usercode.
Examples
Example 1
This example shows a display for a typical W command:
The heading line appears on the first page of the Waiting Entries display and before
the Waiting Entries in automatic display mode (ADM).
The job number of the waiting task is displayed in the Job field. The mix number of
the job or associated task is displayed in the Task field. The Pri field contains the
priority of the task. The Elapsed field shows the length of time the task has been
waiting. The time is expressed in hours, minutes, and seconds.
The word Job precedes each job name. The usercode of the originator appears before
the job or task name. Some tasks and jobs can have two usercodes shown for the
following reasons:
Tasks other than compiler tasks display with the following format:
Example 2
This example shows waiting jobs and tasks from all queues:
W QUEUE
Example 3
This example displays only the waiting job that has no usercode associated with it:
W USER=""
WM (What MCP)
The WM (What MCP) command displays information about the current operating
system.
Syntax
Explanation
WM
Displays information about the current operating system. This information includes
the title of the MCP code file, the release level, whether the MCP is temporary or
permanent, and a list of the compiler options (standard and user options) that were
set when the code file was compiled. If the system is using the automatic pack
controlware load feature, the display shows the controlware types that have been
saved on the halt/load disk.
Information
Component Description
MCP Displays the MCP code file name and release level.
H/L unit Displays the unit number on which the current MCP code
file resides.
Compiled Displays the date and time the current operating system
was compiled and the NEWP compiler level.
Compile time options Displays the options that were set when the system was
are compiled. For more information on compile-time options,
refer to the Simple Installation Operations Guide.
Haltload reason Displays the reason for the most recent halt/load.
Haltload time Displays the date and time at which the most recent
halt/load occurred.
Information
Component Description
System type Displays the basic system type and number of CPUs.
Processor type Displays the system processor type. The system type
(displayed only on value for MCPvm systems is for a specific model (such as
Virtual MCP (MCPvm) CS523-006), but the processor type value for MCPvm
systems) systems is a general number (such as CS520). The
processor type value is the same as the TIME(24)
intrinsic value and the Simple Installation target
processor value.
Controlware types Displays the disk controller types for which controlware
saved can be loaded automatically, if necessary. Refer to the
appropriate capabilities manual for your system for more
information on automatic loading of controlware.
Examples
Example 1
This example shows a typical display generated by a WM command:
WM
Example 2
This example shows a display generated by a WM command when the system is
running on a temporary MCP:
WM
The X25MCS command also activates the Network Services library when the X.25
MCS is started if the Network Services is not active.
Syntax
Explanation
X25MCS
X25
Inquire on the status of the network and provides the network initialization file (NIF)
name currently in use.
X25MCS <command>
Directs system commands to the X.25 MCS operator interface.
X25 = *NULL
Specifies that no X.25 MCS initialization file is used.
X25 = *DEFAULT
Specifies that the X.25 MCS initialization file is used.
X25 + *NULL
Starts X.25 MCS initialization without using the initialization file.
X25 + *DEFAULT
Start X.25 MCS initialization using the initialization file.
X25MCS +
Starts the X.25 MCS and the Network Services library if Network Services is not
running.
X25MCS
Causes the X.25 MCS to terminate normally. No calls can start after this form of the
command is entered. The termination routine waits until all active calls are
completed before it finally stops the X.25 MCS.
X25MCS NOW
Causes the X.25 MCS to terminate immediately. No new calls are permitted, all
active calls are cleared, and the X.25 MCS is stopped when this form of the
command is used.
Example
X25MCS +
XD (Bad Disk)
The XD (Bad Disk) command eliminates defective sectors on disk from the available
disk table.
If the disk is mirrored, any changes are made to the other members of its mirrored
set also.
Syntax
Explanation
XD DK <unit number> ADDRESS <starting address number> <length number>
XD DK <unit number> SEGMENT <starting address number> <length number>
XD PK <unit number> ADDRESS <starting address number> <length number>
XD PK <unit number> SEGMENT <starting address number> <length number>
Eliminate the specified sectors from the available disk table. The unit number
specifies the unit affected. ADDRESS <starting address number> or SEGMENT
<starting address number> specifies the absolute decimal address of the first
segment to be marked. The <length number> or FOR <length number> specification
indicates the total number of sectors to be eliminated.
The eliminated area is recorded in the disk directory with the file name
BADDISK/<disk address>, where <disk address> is an address consisting of the
family index, the unit number, and the starting sector number.
Example
XD PK33 ADDRESS 62345 FOR 20
MSG
If any part of the area to be marked as bad disk is in use by a file, this procedure
fails and the following message is displayed:
If this occurs, use the RES (Reserve) command, which moves the files and removes
the sectors from the available disk table.
Y (Status Interrogate)
The Y (Status Interrogate) command displays the status of jobs or tasks. For a
scheduled task, the system displays the number of words required for the task.
Syntax
Explanation
Y
Returns a list of the programs that are linked to the specified mix number when the
mix number refers to a library stack. The program name is displayed immediately
after the first line that reports Status of Task. For a scheduled task, the display
shows the number of words required for the task.
If a task is using the MCP sort routine or is executing a program dump at the time
that you enter a <mix number> Y command, the Stack State display indicates
Sorting or Program dumping.
Status time
Job name
Start time
Fetch statements
Limits
Originating job number
Job class
MPID
Priority
Target and actual processor set
0 = Standard processor set (systems that do not support custom processor
sets) or STD:0 (Systems that support custom processor sets)
1 through n = Custom processor sets STD:1 through STD:n, where n is the
maximum number of custom processor sets as specified in the performance
key.
n+1 = Java
Origination
Originating MCS
Usercode
Stack state. For an explanation of stack states, refer to the Task Management
Programming Guide.
Program name
DISPLAY messages
RSVP messages
Valid replies to RSVP messages
CHARGECODE and ACCESSCODE attributes of the task or job identified by the
mix number if it is active
Checkpoint status. The checkpoint status is shown if it is not null. For
example:
CHECKPOINT STATUS = REQUESTED/RUNNING/RESTARTING
For information about checkpoint status, refer to the Task Management
Programming Guide.
PDUMPTITLE attribute of the task identified by the mix number
Code file title
Displayed for noncompiler tasks when the process name and the code file title
differ. If the code file is the current MCP, then the title is displayed as *MCP
Independent Runner*.
Code file created
This is the creation date and time of the code file or compiler in use.
Examples
Example 1
This example shows the response for a job that is waiting on an event:
656 Y
Example 2
This example shows a response for a job that has a fetch statement:
1555 Y
Example 3
This example shows a response for a library. It lists the programs that are linked to
the library:
1446 Y
Example 4
This example shows the response for a job that has a specified start time:
9325 Y
Example 5
This example shows the response for a job that has completed:
9122 Y
Example 6
This example shows the response for a job in which the process name and the code
file title differ:
9442 Y
Example 7
This example shows the response for a task with a non-zero CPURATEBIAS:
4218 Y
The ??CD command is available only if the MCP was compiled with the TRACE
compile-time option set.
For additional information, refer to the ??TRACE (Trace Table) primitive command.
Syntax
Explanation
??CD
Displays the state of all the conditional stop flags. The display is in 16 areas
numbered 0 (zero) through F (15). The row number corresponds to the first digit of
the stop number. Each row has three columns, labeled DUMP, STOP, and TRACE. The
entry in each column is a mask of the stops for which the various functions are
armed.
??CD +
Enables all CONDITIONALDUMP stops to generate trace entries.
??CD
Disables the TRACE function for all stops.
??CD STOP
??CD STOP77
The keywords STOP and STOP77 are synonymous; both enable the STOP function.
The only way the STOP function can be disabled is through the ODT. Enabling the
STOP function also arms the TRACE function for a CONDITIONALDUMP stop.
??CD DUMP
If the DUMP function is enabled for a CONDITIONALDUMP stop, then the next time
the stop is executed, the system takes a memory dump. The reason for the dump is
given as CNDTNL DUMP 000nn, where nn is the stop number. When the dump is
complete, the DUMP function is disabled for the CONDITIONALDUMP stop. Arming
the DUMP function also enables the TRACE function for a CONDITIONALDUMP stop.
??CL (Clear)
The ??CL (Clear) command clears all exception flags maintained by the MCP for the
specified peripheral units and terminates any task using those units.
Syntax
Explanation
??CL <device type> <unit number>
Clears the devices in the specified unit number list. Clearing a device assigned to a
task results in the immediate discontinuation of that task.
If the response to this command requires more than one screen, the screens are
displayed at 8-second intervals.
This command is the same as the nonprimitive CL (Clear) command, except that it is
executed by a stack independent of the CONTROLLER stack. This command can
therefore be used even when the CONTROLLER stack is suspended.
Syntax
Explanation
??CM <file name>
Changes the MCP to the MCP specified by <file name> without waiting for a zero mix
count. The disk bootstrap is changed and the new MCP is loaded at subsequent
halt/loads.
A subsequent halt/load loads the previous MCP because the disk bootstrap still points
to it.
When CMP auditing is active, all messages are written to the CMP trace file on the
halt/load unit. The trace file has a title of the form
CMPAUDIT/<MMDDhhmm>
In this title, <MMDDhhmm> is the month, day, hour and minute when the file was
opened.
The CMP trace file has a proprietary format and is intended for use by Unisys.
Syntax
Explanation
??CMPAUDIT
Reports the status of CMP auditing.
??CMPAUDIT +
Starts CMP auditing.
??CMPAUDIT
Closes the CMP trace file when the next message is sent or received.
??CMPAUDIT RESTART
Closes the CMP trace file and starts a new file when the next message is sent or
received.
Syntax
Note: The SERIALNO attribute can be specified only for a source or destination that
is a tape.
Explanation
<source>
<destination>
A family name or tape name of up to 17 letters and digits.
<serial>
From 1 to 6 letters and digits.
Note: The ??DIALT command is intended for use by Unisys engineers. This
command is not supported for use by customers.
Syntax
Explanation
The first time any ??DIALT command is entered, the MCP allocates the
DIALTRBUFFER array to hold the statistics. The + and options turn the statistics-
collecting operation on and off. When the data array is full, all statistical data
gathering is automatically stopped, as if a ??DIALT command had been entered.
??DIALT
Reports the current status of the DIAL trace (on or off).
??DIALT RESET
Reinitializes the data array, discarding any currently stored data and stopping all
statistical data gathering.
??DS (Discontinue)
The ??DS (Discontinue) command discontinues the task identified by the given mix
number. If the command is entered without a mix number, all ordinary tasks are
discontinued.
Syntax
Explanation
??DS
Discontinues all ordinary tasks.
?? <mix number> DS
Discontinues the task identified by the mix number.
Syntax
Explanation
??DUMP
Invokes a nonfatal memory dump.
??DUMP <text>
Invokes a nonfatal memory dump. The first 18 characters of the text appear in the
memory dump as the reason for the dump.
Syntax
Explanation
??FS
Causes the execution of all scheduled jobs and tasks.
??<mix number> FS
Causes the execution of the scheduled job or task identified by the mix number.
This command is designed primarily for debugging stand-alone system hardware and
software. This command stops all system operations and is not intended for normal
system use.
Syntax
Explanation
??HALT
Immediately stops the system. Note that the system cannot continue from this state.
All peripherals and control devices can now be acquired by another partition.
??HALT AT
??HALT IN
Set the system level debugging capability. These options can be used to enable
special processor hardware that freezes the processor state when a specified point is
reached in the code stream of the operating system or of a user program.
??HALT AT <SDI>
Causes an unconditional halt in the operating system code segment at the specified
segment dictionary index (SDI). The SDI is the offset in the segment dictionary
where the segment descriptor for the code is located.
Enter AX <SDI> to cause an unconditional halt in the user program code segment at
the specified SDI. Enter AX NO to cause the task to execute with no halt.
This task becomes the halt-enabled task. Only one task can be halt-enabled at a
time.
??HALT
Disables any halts that have been set. This command does not unmark any
previously marked code files.
Syntax
Explanation
The ??HS command changes the state of job selection to the opposite state. For
example, the ??HS command can be used to inhibit task initiation immediately
following a halt/load. A second ??HS restarts task initiation.
The ??LH (Load Host) command loads the pack controlware file to a disk pack
controller. If the response to this command requires more than one screen, the
system displays the screens at 8-second intervals.
Syntax
Explanation
??LH CTL <CTL number> <file title>
??LH DLP <DLP number> <file title>
Loads the pack controlware from the file with the title <file title> to the disk pack
controller specified as the target CTL or DLP.
Example
??LH DLP 4007 CONTROLWARE/B9387 ON SYSPACK
This command is the same as the nonprimitive LH (Load Host) command, except
that it is executed by a stack independent of the CONTROLLER stack. This command
can therefore be used even when the CONTROLLER stack is suspended.
Syntax
Explanation
The ??MARC command directs control of the ODT to COMS/ODT/DRIVER. The
standard ODT operations become unavailable until ??ODT is entered. Refer to
??ODT (Return from Menu-Assisted Resource Control) in later in this section. After
??MARC is entered, the only primitive commands the system recognizes are ??ODT
(to resume standard ODT operations), ??MEMDP (to force a system dump), and
??RESTRICT (to restrict standard ODT operations).
COMS/ODT/DRIVER always releases the ODT into MARC through the SYSTEM/COMS
MCS. Refer to the Menu-Assisted Resource Control (MARC) Operations Guide for
information about MARC.
COMS/ODT/DRIVER allocates a pseudostation for each ODT under its control and
handles simulation of a data comm environment without the need for an active NSP.
A DATACOMINFO file must be available that defines SYSTEM/COMS,
COMS/ODT/DRIVER, and any other MCSs (such as SYSTEM/CANDE) that might be
used. The SYSTEM/COMS MCS must be the same code file title used to establish the
COMSSUPPORT system (function) library.
If the DATACOMINFO file tables have not already been loaded, some delay can occur
before the ??MARC command can begin a transfer. In this case, the following
message is issued:
One of the following messages is issued if the ??MARC primitive command fails:
The following messages are issued when an ODT transfer is started because a delay
can occur if the COMS/ODT/DRIVER or SYSTEM/COMS (or <MCS name>) is not
running when the ??MARC primitive command is entered:
PRIMITIVE EXECUTED.
SC <unit number> TRANSFER UNDERWAY.
The following messages are issued by COMS/ODT/DRIVER and appear only on the
ODT for which they are intended. These messages are not seen by the CONTROLLER.
The controlling MCS of the station has terminated or the station was returned to the
control of COMS/ODT/DRIVER by a log-off or direct-transfer operation. The message
also appears if COMS/ODT/DRIVER accepts a <mix number> SM : CLEAR <ODT
unit>.
The number of pseudostations defined for the system is less than the number of ODT
units, and transferring the ODT would exceed the defined number of pseudostations.
Command Description
Command Description
Syntax
Explanation
??MEMDP
Invokes a nonfatal memory dump.
??MEMDP <text>
Invokes a nonfatal memory dump. The first 18 characters of the text appear in the
memory dump as the reason for the dump.
Syntax
Explanation
The ??ODT command forces an ODT to leave the control of COMS/ODT/DRIVER and
return to the control of the CONTROLLER and the system. Commands that begin with
two question marks (??) (primitive commands) are then recognized by the system,
and nonprimitive inputs are handled directly by the CONTROLLER.
??OK (Reactivate)
The ??OK (Reactivate) command reactivates suspended tasks.
Syntax
Explanation
??OK
Reactivates all waiting tasks.
?? <mix number> OK
Reactivates the waiting task identified by the mix number.
Syntax
Explanation
??OL <device type> <unit number list>
Displays the label and path information for the devices.
Syntax
Explanation
??PD <file name>
Displays information about the presence of the named file on the default family, and
other information about the file. The default family name is always DISK. If the file is
not present, the system displays the NO FILE message.
If file name ends in a minus sign (), you must enclose the file name in quotation
marks ("").
??PD <directory>
Displays the directory name (if the directory exists) and confirms that it is a
directory. The system lists no files under that directory. To obtain a list of these files,
enter the following command:
??PD <directory>/=
??PD =
??PD
List the first level of all names in the disk directory.
??PD <directory> =
??PD <directory>
??PD <directory>/=
??PD <directory>/
Display a list of all file names in the directory that have the specified directory name
as their prefix.
<number>
A positive integer used after an equal sign (=) or minus sign () that specifies the
maximum number of levels of the file names in that directory to be displayed.
ON <family name>
Specifies the family directory to be searched. The default is always DISK.
Syntax
Explanation
The ??PHL command causes a programmatic halt/load.
Syntax
Syntax
<security key>
A string from 1 to 17 alphanumeric characters.
Explanation
??RESTRICT + (<security key>)
The security key provides a means by which the system can validate the use of this
command to release the ODT and can disregard the restriction on the ODT. If a
security key was specified when the ODT was restricted and that security key is
supplied in the ??RESTRICT command, the ODT is returned to nonrestricted use.
An ODT that was restricted without a security key by a nonprimitive RESTRICT
command cannot be released by a ??RESTRICT command, which requires a
security key specification.
The ??RESTRICT command restricts or releases the ODT from which the command
originates; therefore, no unit number is required.
Syntax
Explanation
Caution
This command causes all job queue, ADM and TERM specifications and all queued
and active jobs to be lost when the next halt/load occurs.
The ??RJ command changes the FILEKIND attribute of the JOBDESC file to that of a
removable file so that the next halt/load will cause it to be discarded as the JOBDESC
file and renamed for diagnostic purposes according to the following format:
OLDJOBDESC/<date>/<time>
The <date> file title node is in the form MMDDYYYY, where MM is the two digit
month (01 through 12), DD is the two-digit day of the month (01 through 31), and
YYYY is the four-digit year (1995, 2010, etc.).The <time> file title node is in the
form HHMM, where HH is the hour of the day (00 through 23) and MM is the minute
of the hour (00 through 59). For example, a JOBDESC file removed on October 9,
1996 at 2:06 p.m. would be renamed
OLDJOBDESC/10091996/1406
The capabilities of the ??RUN command are also available through the PRIMITIVE
RUN system command.
Syntax
Explanation
The ??RUN <file title> command initiates the specified code file as an independent
process.
Syntax
Explanation
The ??RV command tells the system to start a new volume directory after the next
halt/load.
The following are the restricted system commands and related SETSTATUS calls.
CF LG RESTRICT
DL MP SL
USERDATA
HU MU ??SECAD
ID REMOTESPO
If security administrator status is not authorized for the system, any operator or
privileged user can change security options and the USERDATAFILE or invoke the
restricted system commands and SETSTATUS calls.
Syntax
Explanation
??SECAD
??SECAD +
Sets the SECADMIN option. The system indicates whether a USERDATAFILE exists
and, if so, how many security administrators are defined in it. It then waits for you
to confirm that a security administrator is to be authorized. If you confirm the action,
the SECADMIN option is set. If you deny the action, the option is not changed.
??SECAD
??SECAD <usercode>/<password>
Resets the SECADMIN option. If the security administrator is defined in the
USERDATAFILE, then the usercode and password of the administrator must be
supplied to verify that the person resetting the option is an administrator. If no
security administrator is defined in the USERDATAFILE, no administrator usercode or
password is needed to reset the option.
??ST (Stop)
The ??ST (Stop) command suspends tasks. If no mix number is specified, all
ordinary tasks are temporarily suspended.
Syntax
Explanation
??ST
Suspends all ordinary tasks.
??<mix number> ST
Suspends the task identified by the mix number.
The ??TRACE command is available only if the MCP was compiled with the TRACE
compile-time option set.
Syntax
Explanation
??TRACE
Displays the current trace setting.
DPFULL
Causes the system to generate a memory dump after the last entry has been placed
in the trace table. If this option is set, a series of memory dumps is taken, one each
time the table is full. If it is reset, the dumps are not taken. In either case, when the
table becomes full, the pointer for the next entry is reset to the beginning of the
table, and trace table entries continue to be made.
This option is set by the plus sign (+) or reset by the minus sign ().
CLEAR
Causes the next CONDITIONALDUMP stop that has the TRACE function armed to fill
all trace table entries with zeros, sets the pointer for the next entry to the beginning
of the table, and resets the CLEAR option.
This option is set by the plus sign (+) or reset by the minus sign ().
A container is a file containing other files in an encoded form, suitable for transport
across an open network to another host. You can use the WRAP statement in WFL to
create single wrapped files or wrapped containers containing multiple files. You can
later use the UNWRAP statement in WFL to recreate original files from single
wrapped files or wrapped containers on the destination host.
The ??UNWRAP primitive command supports only a subset of the syntax of the WFL
UNWRAP statement. The ??UNWRAP primitive is intended for use when the WFL
compiler is missing or fails to freeze.
Syntax
<source>
<destination>
<container name>
<wrapped file name>
These elements follow the <file name> syntax.
Explanation
??UNWRAP <wrapped file name> . . .
Creates an unwrapped file based on the specified wrapped file. By default, the file is
created under the same usercode as the wrapped file upon which it is based. (Note
that containers can include files with a variety of different usercodes.)
AS <file name>
Creates the unwrapped file using the specified file name, instead of the original file
name.
If the specified file name includes a usercode, the file is created under that usercode.
Otherwise, the file is created under the same usercode as the wrapped file.
If the AS <file name> clause is omitted, the file is recreated under the same name
as the wrapped file.
If the OUTOF <container name> clause is omitted, the system treats <wrapped file
name> as a reference to a single wrapped file instead of a file within a wrapped
container. If the AS <file name> clause is also omitted, the recreated file has the
same file name as the wrapped file, and overwrites the wrapped file.
FROM <source>
Specifies the disk or CD-ROM where the single wrapped file or container resides. The
FROM <source> clause is required. The default <source> is DISK.
TO <destination>
Specifies the disk family where the file is to be created.
If the TO <destination> clause is omitted, the system creates the file on the family
named DISK.
Examples
Example 1
The following command creates the file (THP)RECIPTS/INCOMING ON LFPACK, based
on the single wrapped file (THIEN)RECEIPTS/FILE ON DISK:
Example 2
The following command creates the file (THIEN)RECEIPTS/MONDAY ON DISK from
the wrapped file of the same name in the container (THIEN)RECEIPTS/FEBRUARY ON
LFPACK:
Example 3
The following command creates the file (THP)ACCTS/MONDAY ON LFPACK from the
wrapped file (THIEN)RECEIPTS/MONDAY in the container
(THIEN)RECEIPTS/FEBRUARY ON DISK:
Syntax
Explanation
This command is the same as the nonprimitive UR (Unit Reserved) command, except
that it is executed by a stack independent of the CONTROLLER stack.
You can use this command even when the CONTROLLER stack is suspended.
Syntax
Explanation
The ??W command displays all waiting jobs or tasks.
Syntax
Explanation
??ZFA
Clears all error counts for all modules.
Command Explanation
Command Explanation
HS, HS + Halt the starting of new jobs or tasks after the dump.
MT <unit Sends the dump to a tape unit. The tape on the unit is
number> purged before it is used.
Note: If the tape is not at load point, the memory dump
asks you to enter this command a second time. Before you
enter the command again, verify that it is permissible to
overwrite the contents of the tape.
NODUMP, Set the system run-time option NODUMP to TRUE after the
NODUMP + dump.
Note: The OP NODUMP option reverts to its original setting
after the next halt/load unless you enter an OP + NODUMP
command after the memory dump finishes.
PG MT <unit Sends the dump to the specified tape unit. The tape on that
number> unit is purged before being used.
Note: If the tape is not at load point, memory dump asks
you to enter this command a second time. Before you enter
the command again, verify that it is permissible to overwrite
the contents of the tape.
Command Explanation
SN MT <unit Sends the dump to the specified tape unit. The tape on that
number> <serial unit is purged and assigned the specified serial number
number> before being used. The serial number can be a number from
one to six digits long or an alphanumeric string from one to
six characters long and enclosed in quotation marks ("").
Note: If the tape is not at load point, the memory dump
asks you to enter this command a second time. Before you
enter the command again, verify that it is permissible to
overwrite the contents of the tape.
Note: The system does not perform automatic memory dumps if the OP + NODUMP
option is set. For more information about memory dumps, refer to the MDT (Memory
Dump Type) command.
The memory dump procedure can write memory dumps to disk, tape, or CD-R. When
a memory dump is to be written to a dump disk file, the memory dump procedure
automatically writes the dump to disk. When a memory dump is to be written to
tape, the memory dump procedure stops and asks you to specify the tape unit
number holding the tape volume on which the memory dump is to be written.
Notes:
For a dump to tape, the memory dump procedure automatically selects and uses
any write-enabled online scratch tape with the serial number DUMMMP without
waiting for you to reply.
The media used for memory dump to CD-ROM must be scratch: If CD-R media is
used it must be new; if CD-RW media is used it must be new or newly erased.
Note that no read to verify written data is performed. Do not use media that is
known to be unreliable.
All tape and CD-ROM media are rewound and unloaded when the memory dump
process completes or the media is full. These actions are required because the
state of the device from an MCP perspective remains as it was preceding the
dump. If the dump media is not unloaded, it can be rendered unusable by a user
program or MCP process that attempts to use the device when the system
resumes following the dump. Ensure that any doors that might inhibit the
unloading of the tape or CD-ROM device are open when the dump is directed to
such a device.
If the system attempts to take a memory dump to tape or CD-ROM, it waits for
an operator to specify the unit number to be used. If the dump waits beyond
2100 on the following day, the system date and time are incorrect after the
dump completes. The operator must reset the date and time as soon as possible
after the dump completes. You can avoid this situation by using either the DN or
CM + HLDUMPDISK commands so that system dumps are taken to disk.
DP_071900_1213
DP_071900_1213_2
DP_071900_1213_3
CD-ROMs containing memory dumps are in a nonstandard format, and will not be
able to be read by standard software on other systems such as PCs. The PER CD
display distinguishes CD-ROMs that contain memory dumps by appending the
phrase, Memory Dump. Certain commands such as FILES and PD do not work on CD-
ROMs containing memory dumps.
Memory dump to 650 MB CD-R media, 700 MB CD-R media, DVD-R media, and
DVD+R media is supported. MEMDUMP uses the full capacity of whichever media is
used. There is no need for the user to specify DENSITY (and no way for the user to
specify DENSITY) during MEMDUMP. Continuation media need not be the same
capacity as earlier media. SDASUPPORT handles mixed capacity sets while reading
MEMDUMPs.
Command Description
Command Description
However, in current releases, additional implementation has been added that might
provide performance improvements for all systems using the MDT NONCOMPRESSED
option. These improvements are based on creating the dump name (DN) file on a
multiunit family. When multiple units are utilized for the DN file, simultaneous I/O
operations (I/Os) can be performed in parallel, decreasing the elapsed time required
to take a complete dump. Because the dump time is not dependent upon the
contents of memory, tests can be performed on various configurations to determine
the expected time for a given memory dump. In most situations, when the dump is
noncompressed, dedicating two units to the DN family results in dumps completing
faster. Performance improvements are greatly enhanced by locating the various units
on independent paths.
The memory dump process has a limited number of internal I/O structures for
performing parallel I/Os. These internal I/O structures include READ/WRITE
operations to active ODT units and to the dump disk file.
For multiunit families, a minimum of two I/Os and a maximum of 16 I/Os can be
performed in parallel. The actual number of parallel I/Os is constrained by the
smaller of the number of members in the DN family, a value dependent on the
number of ODT units and the maximum value of 16. The second value is
calculated by the equation 29(2X), where X is the number of ODT units. The
multiple of two derives from the fact that READ and WRITE operations to ODT
units need separate I/O structures. For example, if the DN file resides on a four-
unit family, a maximum of four I/Os can be performed in parallel. Similarly, if 13
ODT units are in the partition, the equation 29(2*13) limits the maximum to
three.
The number of ODT units is based on the current configuration. Therefore, if ODT
units are acquired in a partition, but do not really exist, they should be freed from
the partition. Refer to the FREE and DOWN commands in this manual.
If none of these options are specified, DUMPDISKMASTER prompts the operator for
input, by displaying the dump time and reason, with the choices OK, SAVE,
PURGE, and SKIP. For an explanation of how to respond to the
DUMPDISKMASTER choices, refer to the DF (Empty Dumpdisk File) and DN (Dump
Name) commands.
time the system performed the dump, as well as the dump reason, in the following
format:
DP (or SAVEDUMP)/mmddyy/hhmmss/<reason>
You can check these files with the PD (Print Directory) system command. For
example, if DMSIITEST is the name of the DL DPFILES family and the dump was not
unloaded with SAVEDUMP action, enter the following syntax to view the dump file:
PD DP/= ON DMSIITEST
DP (DIRECTORY)
. 081892 (DIRECTORY)
.. 165801(DIRECTORY)
... SC_1 (DATA)
. 081992 (DIRECTORY)
.. 163532(DIRECTORY)
... SC_1 (DATA)
When DUMPDISKMASTER creates a memory dump tape, it names the tape file
MEMORY/DUMP.
To analyze a dump stored on the DL DPFILES family, run DUMPANALYZER and label
equate the TAPEIN file to the dump to be analyzed. The following is an example RUN
statement:
RUN *SYSTEM/DUMPANALYZER;
FILE TAPEIN = DP/mmddyy/hhmmss/<reason> ON <dpfiles family>;
RUN *SYSTEM/DUMPANALYZER;
FILE TAPEIN (SERIALNO = <serialno>);
When you run DUMPANALYZER, you can use the DUMPANALYZER SAVE command to
produce a disk file that contains the memory dump along with line information and
MCP identifier names. This is the form of the memory dump file you can send to your
customer service representative for evaluation when problems occur. You can copy
this saved file to tape with library maintenance. For more information about
DUMPANALYZER, refer to the System Software Utilities Operations Reference Manual.
Refer to the FREE (Free Resource) and DOWN (Down Resource) commands.
General Categories
This appendix contains the following tables that group system commands by
function. This appendix also includes a table listing old and new mnemonics for
system commands that have changed names.
BNA Commands
Dump Commands
Log Commands
Maintenance Commands
MCP Commands
Peripheral Commands
Printer Commands
Tape Commands
CQ (Clear Queue)
CU (Core Usage)
FIND
MAX (Maximums)
ML (Mix Limit)
MX (Mix Entries)
NS (Next Screen)
O (Overlay)
SHOW
TERM (Terminal)
U (Utilization)
BNA Commands
Refer to the following commands:
BNA
BNAVERSION
CA (Candidate)
HOSTNAME (Hostname)
HU (Host Usercode)
NET (Network)
NW (Network Prefix)
SS (Send to Station)
AD (Access Duplicate)
AR (Archive Release)
DD (Directory Duplicate)
DIR (Directory)
DIRECTORY ONLY
DL (Disk Location)
DU (Disk Utilization)
FI (File Information)
PV (Print Volume)
RB (Rebuild Access)
RC (Reconfigure Disk)
RES (Reserve)
RM (Remove)
TL (Transfer Log)
XD (Bad Disk)
DIRECTORY ONLY
FIND
LH (Load Host)
PARTIALSETS
PG (Purge)
RC (Reconfigure Disk)
REMOTEDISK
RES (Reserve)
SHOW
STORESAFE
XD (Bad Disk)
Dump Commands
Refer to the following commands:
DA (Dump Analyzer)
DN (Dump Name)
IK (Install Keys)
LICENSESTATUS
USERLICENSE
DQ (Default Queue)
DS (Discontinue)
??DS (Discontinue)
FS (Force Schedule)
HS (Hold Schedule)
IB (Instruction Block)
ML (Mix Limit)
OK (Reactivate)
??OK (Reactivate)
PF (Print Fetch)
PQ (Purge Queue)
PR (Priority)
QF (Queue Factors)
SQ (Show Queue)
UQ (Unit Queue)
Y (Status Interrogate)
Log Commands
Refer to the following commands:
LC (Log Comment)
LJ (Log to Job)
TL (Transfer Log)
Maintenance Commands
Refer to the following commands:
PG (Purge)
RC (Reconfigure Disk)
RES (Reserve)
RF (Reliability Factor)
RY (Ready)
SC (System Configuration)
SV (Save)
UP (Up Resource)
UR (Unit Reserved)
XD (Bad Disk)
MCP Commands
Refer to the following commands:
AI (Automatic Initiation)
CM (Change MCP)
CO (CONTROLLER Options)
CS (Change Supervisor)
DA (Dump Analyzer)
DL (Disk Location)
DN (Dump Name)
DR (Date Reset)
HS (Hold Schedule)
ML (Mix Limit)
MP (Mark Program)
OP (Options)
OPLOCKTIMEOUT
PRIMITIVE RUN
RA (Register Application)
RP (Resident Program)
SI (System Intrinsics)
SL (Support Library)
TR (Time Reset)
U (Utilization)
WM (What MCP)
CU (Core Usage)
FIND
FREE
FS (Force Schedule)
HS (Hold Schedule)
ML (Mix Limit)
MM (Memory Module)
O (Overlay)
RP (Resident Program)
RY (Ready)
SC (System Configuration)
SF (Set Factor)
SHOW
ST (Stop)
??ST (Stop)
SV (Save)
U (Utilization)
Peripheral Commands
Refer to the following commands:
CL (Clear)
??CL (Clear)
FIND
IL (Ignore Label)
NAMEMAP
OU (Output Unit)
PG (Purge)
REMOTEDISK
RF (Reliability Factor)
RY (Ready)
SB (Substitute Backup)
SHOW
SN (Serial Number)
SV (Save)
UL (Unlabeled)
UP (Up Resource)
UQ (Unit Queue)
UR (Unit Reserved)
Printer Commands
Refer to the following commands:
FM (Form Message)
OU (Output Unit)
PB (Print Backup)
PS ACTIVE
PS ADDFILES
PS ASSOCIATE
PS BANNER
PS BDIR
PS CONFIGURE
PS DEFAULT
PS DELETE
PS DESTINATION
PS DEVICES
PS DIAGNOSTICS
PS DUMP
PS FONTLIB
PS FORCE
PS GROUP
PS HEADER
PS LOAD
PS MODIFY
PS NOTOK
PS OK
PS PAPERSIZE
PS QUIT
PS READY
PS REQUEUE
PS RESTART
PS SAMPLE
PS SAVE
PS SELECTION
PS SHOWREQUESTS
PS SKIP
PS STATUS
PS STOP
PS TRAILER
PV (Print Volume)
QT (Quit)
SB (Substitute Backup)
FIND
ML (Mix Limit)
O (Overlay)
PR (Priority)
SC (System Configuration)
SHOW
TI (Times)
U (Utilization)
UP (Up Resource)
Y (Status Interrogate)
AX (Accept)
BR (Breakout)
CU (Core Usage)
DS (Discontinue)
??DS (Discontinue)
FA (File Attribute)
FM (Form Message)
FR (Final Reel)
FS (Force Schedule)
IB (Instruction Block)
IL (Ignore Label)
LJ (Log to Job)
LP (Lock Program)
NF (No File)
OF (Optional File)
OK (Reactivate)
??OK (Reactivate)
OU (Output Unit)
PF (Print Fetch)
PR (Priority)
QT (Quit)
RM (Remove)
ST (Stop)
??ST (Stop)
SW (Switches)
TI (Times)
UL (Unlabeled)
Y (Status Interrogate)
CF (Configuration File)
GC (Group Configuration)
MM (Memory Module)
NAMEMAP
RY (Ready)
SC (System Configuration)
SV (Save)
UP (Up Resource)
UR (Unit Reserved)
HU (Host Usercode)
MP (Mark Program)
MU (Make User)
SYSADMIN COMMAND
Tape Commands
Refer to the following commands:
FI (File Information)
FIND
FR (Final Reel)
IL (Ignore Label)
OF (Optional File)
OU (Output Unit)
PG (Purge)
PV (Print Volume)
RW (Rewind)
SHOW
SN (Serial Number)
TV (Type Volume)
UL (Unlabeled)
Old New
M MX (Mix Entries)
?ABORT ?MAXSTATIONS
?ADD ?MAXSTACKS
?ATTACH ?MOVE
?AUTOANSWER ?NEWS
?BUG ?NOAUTOANSWER
?CLEAR ?OP
?COMPILESPERCENT ?QUIT
?CONTROL ?READY
?DEPTH ?RELEASE
?DISABLE ?SAVE
?DSLGSTA ?SCHEDULE
?ENABLE ?SS
?FACTOR ?STUP
?GRINDLIMIT ?SUBTRACT
?INFO ?SWAP
?LAISSEZFILE ?TANKING
?ABORT ?MAXSTATIONS
?LGOP ?TRANSFER
?LGSTA ?WHERE
?MAXGRINDS ?WHO
The following commands are described in the CANDE Operations Reference Manual:
?COUNTS ?STATUS
?RO ?TIME
?SO ?TO
Jobs entered at an ODT must not contain data specifications. Any WFL compiler
options must be followed by a semicolon (;) to separate them from the rest of the
job.
A number of WFL statements are recognized by the CONTROLLER and are passed to
the WFL compiler automatically, even if they are not preceded by the CC, ?, or
BEGIN JOB constructs. The following list shows the valid WFL statements:
CLASS REMOVE
COMPILE RERUN
A WFL job started at an ODT runs without a usercode unless the job contains a
USERCODE job attribute specification. A job without a usercode (and any tasks it
initiates) cannot access files residing under usercodes unless their security attribute
is PUBLIC. If the job has no usercode or FAMILY specification, the FAMILY of the job
queue is used, if present. Otherwise, the FAMILY attribute defaults to a null string,
which has the same effect as
The statements ALTER, CHANGE, MKDIR, REMOVE, RERUN, SECURITY, and START
are executed interpretively if entered individually at an ODT rather than as part of a
job. In these cases, the WFL compiler produces no code file; instead, it executes the
statements directly. These statements, if entered at an ODT, are treated as
privileged and can access files residing under usercodes.
The Default column of the table shows the system command that reestablishes the
default setting. For some options, such as OP and PLI, you must use two or more
system commands to establish the default setting. For some options, the phrase
(Dependent on code) appears, where code is one of the following values:
(blank)
The default value listed in the Default column is established by a LOADER cold-
start run.
LOADER
The default value listed in the Default column is established by a LOADER cold-
start run unless you give the LOADER a command to set the option to a specific
value.
JOBDESC
The default value listed in the Default column is established every time that the
CONTROLLER (at halt/load time) creates a new JOBDESC file on the DL JOBS
family. The CONTROLLER creates a new JOBDESC file for any of the following
reasons:
Either the system or LOADER changed the DL JOBS setting to reference a
disk family that does not have a JOBDESC file.
The system executed a ??RJ primitive command for the old JOBDESC file.
An error occurred when the old JOBDESC file was set up.
CONFIGURATION
The values for these options are established either by the configuration file used
by a RECONFIGURE GROUP command or by LOADER.
PRINTERINFO
PRINTSUPPORT establishes these default values whenever the PRINTSUPPORT
library starts. This library creates a new SYSTEM/PRINTERINFO file.
Option Default
ASD ASD 50
Refer to ASD (Actual Segment Descriptor)
AUTORESTORE DONTCARE
Refer to AUTORESTORE (Archiving AUTORESTORE Option)
BNAVERSION BNAV2
Refer to BNAVERSION
CF CF
(Dependent on LOADER)
Refer to CF (Configuration File)
CS CS
Refer to CS (Change Supervisor)
Option Default
DN DN
Refer to DN (Dump Name)
DQ DQ 0
(Dependent on JOBDESC)
Refer to DQ (Default Queue)
DRC DRC
Refer to DRC (Disk Resource Control)
FILELOCKTLIMIT FILELOCKTLIMIT 0
Refer to FILELOCKTLIMIT (File Lock Time Limit)
HLUNIT The disk from which the system was most recently
halt/loaded
(Dependent on LOADER, CONFIGURATION)
Refer to HLUNIT (Specify Halt/Load Unit)
HOSTNAME HN
(Dependent on CONFIGURATION)
Refer to HOSTNAME (Hostname)
HS HS
Refer to HS (Hold Schedule)
HU HU
Refer to HU (Host Usercode)
ID ID SYSTEM: MAXPSEUDO 0
Refer to ID (Initialize Data Comm)
Option Default
MIXLIMIT MIXLIMIT
(Dependent on JOBDESC)
Refer to ML (Mix Limit)
MQ MQ 0, MIXLIMIT 10,
DEFAULTS (PRIORITY = 50),
LIMITS (PRIORITY = 99)
(Dependent on JOBDESC)
Refer to MQ (Make or Modify Queue)
PLI PLI 60
PLI
Refer to PLI (Periodic Logging Interval)
Option Default
PS HEADER PS HEADER
(Dependent on PRINTERINFO)
Refer to PS HEADER
Option Default
PS TRAILER PS TRAILER
(Dependent on PRINTERINFO)
Refer to PS TRAILER
Option Default
Option Default
SYSOPS SYSOPS
CATALOGLEVELSET = RESET
CCSVERSION = ASERIESNATIVE
CONVENTION = ASERIESNATIVE
CREDENTIALS = DISABLED
DATEWARN = RESET
DIRECTPRINTER = RESET
ENABLEPOSIX = RESET
ESR = CONDITIONAL
LABELFORMAT = ANSI69DEFAULT
LANGUAGE = ENGLISH
LMBLOCKSIZE = 0
LONGFILENAMES = RESET*
PERMDIRECTORIES = RESET
QUEUEDAX = RESET
RCBP = RESET
RSVPONTAPEERROR = RESET
SYSTEMDIRECTORY = RESET
TAPEOVERWRITE = RESET
TAPESERVER = RESET
TAPEMANAGER = RESET
TAPEEXPIRATION = TRUE
WARNFACTOR = STANDARD
WRAPNOWAIT = RESET
*This option is unique because LOADER always prompts
the operator for the desired value of the parameter during
a cold-start. If during a halt/load the DL CATALOG family
is determined to contain a usable file access structure that
is in the long file name format, the MCP unconditionally
sets the LONGFILENAMES option.
Refer to SYSOPS (System Options)
??SECAD ??SECAD
Refer to ??SECAD (Security Administrator Authorization)
Status Default
RY RY <unit>
UR UR <unit>
(Dependent on LOADER)
Basic Constructs
This topic defines technical constructs that appear in the syntax diagrams in this
manual. The constructs are listed in alphabetical order.
<alphanumeric character>
Any of the characters A through Z or 0 (zero) through 9.
<base number>
<bus>
A number identifying a PCI bus within a PCI bridge or IONODE on an IOP system.
Valid numbers are 1 through 3 for a Libra Model 185 or 500 Series system and 0
through 7 for a Libra Model 680 or 690 system.
<CCS name>
A valid CCS name contains from 1 to 17 alphanumeric characters and must begin
with a letter.
<ccsversion name>
A valid ccsversion name contains from 1 to 17 alphanumeric characters and must
begin with a letter.
<ccsversion number>
A positive integer that represents the library coded character set number. For more
information, refer to the MCP/AS Multilingual System (MLS) Administration,
Operations, and Programming Guide.
<CD name>
A valid name is from 1 to 17 characters. The characters can be letters, and digits,
underscores (_), and hyphens (-).
<convention name>
A valid convention name contains from 1 to 17 alphanumeric characters and must
begin with a letter.
<country name>
A valid country name contains from 1 to 17 alphanumeric characters and must begin
with a letter.
<CPM list>
<CPM number>
An integer in the range 0 through 11. On LX systems, the number must be in the
range 4 through 11.
<CTL number>
For IOM systems, a number that identifies a particular control device on a system. It
can be any number in the range 1 through 32767. See also <DLP number>.
<day of week>
The value used to indicate the days of the week.
<device ID>
A device type concatenated with an integer that identifies a specific I/O device.
<device number>
The device number is used to identify a particular unit, control, or port. A device
number can be any number within the range 1 through 32767 for IOM systems or 1
through 65535 for IOP systems.
<device type>
Device mnemonics are defined as follows.
Device Meaning
Type
CD CD-ROM device
DC Data comm
HY HYPERchannel unit
LP Line printer
NP Network processor
PK Pack
Device Meaning
Type
VC Voice channel
<digit>
Any character in the range 0 through 9.
<directory name>
As an alternate syntax for indicating a directory associated with a usercode, instead
of preceding the directory name with the usercode in parentheses, you can precede
the directory name with *USERCODE/<usercode>. You can use this alternate form
when you refer to either a file or to a directory of files under the specified usercode.
The # <string primary> syntax can be used to dynamically build directory names
and directory titles. The run-time result must form a valid directory name constant
or directory title constant, respectively; otherwise, a run-time error occurs.
A string primary can contain an entire individual directory name or directory title. A
string primary can also take the place of any part of the name and title, as long as
the result is of the correct form.
<directory title>
A directory title containing the suffix ON <family name> specifies a family other than
the default family (DISK).
<DLP address>
A number that indicates the relative location of a data link processor (DLP) within a
base. It can be any number in the range 0 through 7.
<DLP number>
A number that identifies a particular data link processor (DLP) on a system. For IOM
systems, <DLP number> is identical with <CTL number>. A nonpreferred synonym,
DLP instead of CTL is often used when referring to a control device that is an MLI-
protocol data link processor.
<DTU number>
Any number in the range 1 through 32767. For resource management module (RMM)
systems, this number is used to identify a data transfer unit (DTU) used for disk
caching.
<EBCDIC character>
Any letter, number, or special character that is in the character set of enterprise
server systems.
<family index>
An integer in the range 1 through 255 that is used to specify a member of a
multimember family.
<family name>
A family is a group of mass storage devices that function as one logical unit.
Specification of a nonquote identifier as the family name refers to a named disk pack
(with any continuation packs) whose name is the family name. A file whose KIND
attribute is set to DISK or PACK refers, by default, to the DISK family.
<file directory>
As an alternate syntax for indicating a directory associated with a usercode, instead
of preceding the directory name with the usercode in parentheses, you can precede
the directory name with *USERCODE/<usercode>. You can use this alternate form
when you refer to either a file or to a directory of files under the specified usercode.
The # <string primary> syntax can be used to dynamically build file names, file
titles, directory names, and directory titles. The run-time result must form a valid file
name constant, file title constant, directory name constant, or directory title
constant, respectively; otherwise, a run-time error occurs.
A string primary can contain an entire individual file name, file title, directory name,
or directory title. A string primary can also take the place of any part of these names
and titles, as long as the result is of the correct form.
<file name>
A file name is a sequence of 1 to 12 names separated by slashes (/) and optionally
preceded by a usercode (enclosed in parentheses) or by an asterisk (*) in the case
of a file that has no usercode.
<file title>
A file title containing the suffix ON <family name> specifies a family other than the
default family (DISK).
<hex digit>
Any character in the range 0 through 9 or A through F.
<hex number>
From 1 to 6 hexadecimal digits.
<hostname>
A valid hostname contains from 1 to 17 alphanumeric characters and must begin
with a letter.
<hour>
An integer from 0 through 23.
<hyphen>
The character used as a hyphen ().
<identifier>
A string of from 1 to 17 alphanumeric characters. Or a string of from 1 to 17
nonquote EBCDIC characters enclosed in quotation marks.
<IOM number>
A number representing an IOM.
<IOP number>
On IOP systems, a number representing an IOP. Valid numbers are 1 through 255.
<IOU number>
A number representing an IOU. An IOU is a component of the I/O module that
provides input/output support functions for the master control program (MCP).
<IP unit>
A number identifying an instruction processor within a subpod on an IOP system.
Valid numbers are 0 through 3.
<kilosector>
1,000 sectors.
<language name>
A valid language name contains from 1 to 17 alphanumeric characters and must
begin with a letter.
<letter>
Any one of the 26 uppercase characters A through Z.
<MCS name>
The name of the Message Control System (MCS).
<MEM unit>
A number identifying an exclusive MEM unit on an IOP system. Valid numbers are 0
through 127.
<minute>
An integer from 0 through 59.
<MIObus>
A number identifying a particular MIO bus of a PCI bridge on an IOP system. Valid
numbers are 0 and 1.
<mix number>
The number by which a task or job is referenced while it is executing. An integer in
the range of 1 through 65535.
<mod range>
The numbers in the mod range must be in the range 0 through 63.
<MSU list>
Two or more MSU numbers (or ranges of MSU numbers), separated by commas.
<MSU number>
Memory storage unit (MSU) numbers can have the following values.
MCPvm 0
<name>
A name is a string of characters used to identify an entity such as a file, a usercode,
or a device group. Starting with a letter or digit, followed by from 0 to 16 letters,
digits, hyphens, or underscores, or a string of from 1 to 17 nonquote EBCDIC
characters enclosed in quotes.
<nonquote identifier>
A nonquote identifier can have from 1 to 17 alphanumeric characters.
<number>
From 1 to 11 digits, optionally followed by a decimal point and one or two digits. Any
more than two decimal digits are ignored.
<pod>
A number identifying a particular pod on an IOP system. Valid numbers are 0
through 3.
<port number>
Any number in the range 1 through 32767 for IOM systems or 1 through 65535 for
IOM systems.
<queue number>
Any number in the range 0 through 1023.
<security key>
A string of from 1 to 17 alphanumeric characters.
<serial number>
A string of from 1 to 6 alphanumeric characters. A serial number is a six-character
identifier that an installation assigns to a disk or magnetic tape to uniquely identify
it.
<set number>
On systems that support custom processor sets, a value of 0 designates the standard
processor set and a value of 1 designates a custom processor set.
<station name>
A unique identifier of a particular station. A station name can have a maximum of 12
identifiers.
<subpod>
A number identifying a particular subpod within a pod on an IOP system. Valid
numbers are 0 and 1.
<text>
One or more EBCDIC characters. The length of the text permitted depends on the
context in which the item is used. Any limits are discussed in the explanation of the
command.
<underscore>
The character used as an underscore (__).
<unit number>
The unit number identifies a particular peripheral device. Valid values are
<user text>
The user text starts with the first nonblank character; that is, the leading blanks are
removed. If this first character is a colon (:), it is discarded. If this first character is a
comma (,), a syntax error is reported. If the first nonblank character is intended to
be a comma, a colon must precede it.
<usercode>
An identification code used to establish user identity, to control security, and to
provide for segregation of files.
Paths
Paths show the order in which the command or statement is constructed and are
represented by horizontal and vertical lines. Many commands and statements have a
number of options so the railroad diagram has a number of different paths you can
take.
The three paths in the previous example show the following three possible
commands:
REMOVE
REMOVE SOURCE
REMOVE OBJECT
A railroad diagram is as complex as a command or statement requires. Regardless of
the level of complexity, all railroad diagrams are visual representations of commands
and statements.
Mandatory items
User-selected items
Order in which the items must appear
Number of times an item can be repeated
Necessary punctuation
Follow the railroad diagrams to understand the correct syntax for commands and
statements. The diagrams serve as quick references to the commands and
statements.
Constants are never enclosed in angle brackets (< >) and are in uppercase letters.
A variable is an item that represents data. You can replace the variable with data
that meets the requirements of the particular command or statement. When
replacing a variable with data, you must follow the rules defined for the particular
command or statement.
In the following example, BEGIN and END are constants, whereas <statement list>
is a variable. The constant BEGIN can be abbreviated, since part of it appears in
boldface.
BE
BEG
BEGI
Constraints
Constraints are used in a railroad diagram to control progression through the
diagram. Constraints consist of symbols and unique railroad diagram line paths. They
include
Vertical bars
Percent signs
Right arrows
Required items
User-selected items
Loops
Bridges
A description of each item follows.
Vertical Bar
The vertical bar symbol (|) represents the end of a railroad diagram and indicates
the command or statement can be followed by another command or statement.
Percent Sign
The percent sign (%) represents the end of a railroad diagram and indicates the
command or statement must be on a line by itself.
Right Arrow
The right arrow symbol (>)
Is used when the railroad diagram is too long to fit on one line and must
continue on the next
Appears at the end of the first line, and again at the beginning of the next line
Required Item
A required item can be
A constant
A variable
Punctuation
If the path you are following contains a required item, you must enter the item in the
command or statement; the required item cannot be omitted.
A required item appears on a horizontal line as a single entry or with other items.
Required items can also exist on horizontal lines within alternate paths, or nested
(lower-level) diagrams.
In the following example, the word EVENT is a required constant and <identifier> is
a required variable:
User-Selected Item
A user-selected item can be
A constant
A variable
Punctuation
User-selected items appear one below the other in a vertical list. You can choose any
one of the items from the list. If the list also contains an empty path (solid line)
above the other items, none of the choices are required.
In the following railroad diagram, either the plus sign (+) or the minus sign () can
be entered before the required variable <arithmetic expression>, or the symbols can
be disregarded because the diagram also contains an empty path.
Loop
A loop represents an item or a group of items that you can repeat. A loop can span
all or part of a railroad diagram. It always consists of at least two horizontal lines,
one below the other, connected on both sides by vertical lines. The top line is a right-
to-left path that contains information about repeating the loop.
Bridge
A loop can also include a bridge. A bridge is an integer enclosed in sloping lines (/ \)
that
Not all loops have bridges. Those that do not can be repeated any number of times
until all valid entries have been used.
In the first bridge example, you can enter LINKAGE or RUNTIME no more than two
times. In the second bridge example, you can enter LINKAGE or RUNTIME no more
than three times.
In some bridges an asterisk (*) follows the number. The asterisk means that you
must cross that point in the diagram at least once. The maximum number of times
that you can cross that point is indicated by the number in the bridge.
In the previous bridge example, you must enter LINKAGE at least once but no more
than twice, and you can enter RUNTIME any number of times.
The following railroad diagram indicates only one path that requires the constant
LINKAGE and the variable <linkage mnemonic>:
Loops
User-selected items
A combination of loops and user-selected items
More complex railroad diagrams can consist of many alternate paths, or nested
(lower-level) diagrams, that show a further level of detail.
For example, the following railroad diagram consists of a top path and two alternate
paths. The top path includes
An ampersand (&)
Constants that are user-selected items
These constants are within a loop that can be repeated any number of times until
all options have been selected.
The first alternative path requires the ampersand and the required constant
ADDRESS. The second alternative path requires the ampersand followed by the
required constant ALTER and the required variable <new value>.
Example 1
<lock statement>
Example 2
<open statement>
Example 3
<generate statement>
Example 4
<entity reference declaration>
Example 5
<PS MODIFY command>
attaching a file name to the ODT, 259 CD-RW media, erasing, 456
attributes CF (Configuration File), 71
disk, 595 CHANGE (FTAM command), 43
job queues, 479 changing the MCP, 83, 744
mix, 595 CHECKFILE (Check for Nonresident
tape, 595 Files), 73
attributes, 595 checkpoint for task, initiating, 60
automatic display of current system CIADIAG system option, 656
status information, 23 CL (Clear), 75
automatically initiating programs, 32 clearing
AUTORESTORE (Archiving disk areas, 520
AUTORESTORE Option), 53 peripheral units, 75
available sectors of disk space, 156 queued system messages, 104
AVAILMIN, 584 clearing, 520
AX (Accept), 54 CLOSE (Close Pack), 79
CM (Change MCP), 83
backup files, terminating printing, 481 CMP (console multiplexing protocol),
backup media, substituting, 554 745
backup tape files, printing, 441 CMPLINK ODT, 745
BACKUPFSDEFAULT system option, CO (CONTROLLER Options), 94
656 code files, running as independent
BADFILE (Bad File), 56 processes, 768
basic constructs, 835 cold-start, default options after, 825
BCVRSVPS system option, 656 commands
BNA hosts memory dumps, 781
assigning names, 207 restricting security, 529, 651
BNA hosts, 207 commands, 529
BNA Version 2 initialization and communicating with media library, 569
termination, 57 communicating with NPSUPPORT
BNA, candidates for subports, 65 library, 569
BNAVERSION, 59 COMPILE STATUS (Information for
BR (Breakout), 60 Compiler Task), 102
bridges in railroad diagrams, 850 compiler
BUFFERGOAL, 584 setting default value for TARGET
option, 98
C (Completed Mix Entries), 62 status, 102
CA (Candidate), 65 compiler, 102
CACHE (Disk Cache), 67 COMPILERTARGET (Set Default Target
cache memory status, 67 Value), 98
cache values of data structures, completed mix entries, listing, 62
displaying, 640 CONDITIONALDUMP stop, 741
CANDE, entering control commands at configuration file, creating, 71, 198
an ODT, 821 configuration, system, 558
candidates for BNA Version 2 subports, configuring StoreSafe, 632
65 connection libraries, 277
capacity licensing information, 221 console multiplexing protocol (CMP),
catalog, system, 103 745
cataloging systems, 171, 477, 769 constants in railroad diagrams, 849
CATALOGLEVELSET system option, constraints in railroad diagrams, 850
656 constructs for railroad diagrams, 835
CC (Control Card), 70 control commands, sending to MCS or
CCSVERSION system option, 656 database, 618
CD-ROM drives, unloading, 546 CONTROLLER options, 94