Unisys MCP Commands 86000395-514

ClearPath Enterprise
Servers
System Commands
Operations Reference Manual
ClearPath MCP Release 11.0 or Later
Printed in USA
April 2006 8600 0395514
.
ClearPath Enterprise
Servers
System Commands
Operations Reference Manual
UNISYS
2006 Unisys Corporation.

All rights reserved.
ClearPath MCP Release 11.0 or Later
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
COMPILERTARGET (Set Default Target Value) ..................... 98

COMPILE STATUS (Information for Compiler Task) .............102
COPYCAT (Copy Catalog) ................................................103
CQ (Clear Queue)...........................................................104
CS (Change Supervisor) ..................................................105
CU (Core Usage) ............................................................107
DA (Dump Analyzer).......................................................109
DBS (Database Stack Entries)..........................................110
DD (Directory Duplicate) .................................................112
DIRECTORY ONLY...........................................................113
DF (Empty Dumpdisk File)...............................................114
DIR (Directory) ..............................................................116
DL (Disk Location)..........................................................117
DN (Dump Name) ..........................................................132
DN (Dump Name) ..........................................................132
DO (Diagnostic Options)..................................................136
DOWN (Down Resource) .................................................139
DQ (Default Queue)........................................................144
DR (Date Reset).............................................................146
DRC (Disk Resource Control) ...........................................149
DS (Discontinue)............................................................152
DU (Disk Utilization) .......................................................156
DUMP (Dump Memory) ...................................................160
EXPAND (Expand Directory).............................................165
FA (File Attribute) ..........................................................168
FAMILYACCESS (Directory Location) .................................171
FAS (Failure Analysis Summary) ......................................173
FI (File Information) .......................................................174
FILELOCKTLIMIT (File Lock Time Limit) .............................177
FIND.............................................................................178
FM (Form Message) ........................................................188
FR (Final Reel) ...............................................................189
FS (Force Schedule) .......................................................190
FREE (Free Resource) .....................................................192
GC (Group Configuration)................................................198
HI (Cause Exception Event) .............................................201
HLUNIT (Specify Halt/Load Unit) ......................................202
HOLD (Hold Unit for Operator Use) ...................................205
HOSTNAME (Hostname) ..................................................207
HS (Hold Schedule) ........................................................209
HU (Host Usercode) ........................................................210
IB (Instruction Block) .....................................................212
ii 8600 0395-514
Contents
ID (Initialize Data Comm) ...............................................213

IK (Install Keys).............................................................221
IL (Ignore Label) ............................................................241
INITIALIZE (Initialize Disk)..............................................242
INSTALL (Install Software) ..............................................245
IOTIMER (Specify Time-out Value) ...................................251
J (Job and Task Display) .................................................255
LABEL (LABEL ODT)........................................................259
LB (Relabel Pack or Host Control Unit) ..............................261
LC (Log Comment) .........................................................267
LG (Log for Mix Number).................................................268
LH (Load HostIOP Systems) ...........................................270
LH (Load HostIOM Systems) ..........................................274
LIBS (Library Task Entries)..............................................277
LIBTRACE (Library Trace) ................................................280
LICENSESTATUS ............................................................284
LJ (Log to Job) ...............................................................285
LOADMICROCODE (Load MicrocodeIOM Systems) ............286
LOG (Analyze Log) .........................................................288
LOGGING (Logging Options) ............................................289
LP (Lock Program)..........................................................292
MAX (Maximums) ...........................................................293
MCS (Message Control System) .......................................297
MDT (Memory Dump Type)..............................................299
MEMORYCEILING (Set Memory Ceiling).............................310
MIRROR (Mirror Disk) .....................................................312
ML (Mix Limit)................................................................332
MM (Memory Module) .....................................................333
MODE (Unit Mode)..........................................................335
MOVE (Move Job or Pack)................................................339
MP (Mark Program) ........................................................342
MQ (Make or Modify Queue) ............................................352
MSC (Message Control) ...................................................358
MSG (Display Messages) .................................................372
MU (Make User) .............................................................375
MX (Mix Entries) ............................................................377
NAMEMAP......................................................................381
NET (Network) ...............................................................385
NETEX (Support NETEX Software) ....................................386
NEW SYSTEMDIRECTORY (Replace an Existing
SYSTEMDIRECTORY) ......................................................388
NF (No File) ...................................................................392
NOTOK (Do Not Reactivate).............................................393
8600 0395-514 iii

Contents
NS (Next Screen) ...........................................................394

NW (Network Prefix).......................................................395
NX (NETEX Software Input) .............................................396
O (Overlay) ...................................................................397
OF (Optional File) ...........................................................399
OK (Reactivate) .............................................................400
OL (Display Label and Paths) ...........................................401
OP (Options) .................................................................422
OPLOCKTIMEOUT ...........................................................434
OT (Inspect Stack Cell) ...................................................436
OU (Output Unit)............................................................437
PARTIALSETS ................................................................440
PB (Print Backup) ...........................................................441
PDIR (Process Directory) .................................................442
PER (Peripheral Status)...................................................443
PF (Print Fetch)..............................................................454
PG (Purge) ....................................................................456
PLI (Periodic Logging Interval) .........................................465
PMIX (Process Mix).........................................................466
POWER (Power Up/Down) ...............................................467
PQ (Purge Queue) ..........................................................469
PR (Priority) ..................................................................470
PRIMITIVE RUN..............................................................471
Print System (PS) Introduction ........................................472
PV (Print Volume)...........................................................477
QF (Queue Factors) ........................................................479
QT (Quit) ......................................................................481
RA (Register Application) ................................................483
RB (Rebuild Access)........................................................486
RC (Reconfigure Disk).....................................................488
RECONFIGURE GROUP (Reconfigure System).....................500
RECOVER (Recover I/O Module) .......................................503
REMOTEDISK.................................................................505
REMOTESPO (Activate REMOTESPO) .................................506
REPLACE (Replace Pack Volume) ......................................509
REPLACECARD (Replace Card) .........................................517
RES (Reserve) ...............................................................520
RESTART (Restart Jobs) ..................................................528
RESTRICT (Set Restrictions) ............................................529
RF (Reliability FactorIOM Systems) ................................536
RM (Remove) ................................................................538
RP (Resident Program)....................................................539
iv 8600 0395-514
Contents
RSS (Reliable Session Service Prefix)................................541

RW (Rewind) .................................................................546
RY (Ready) ....................................................................547
S (Scheduled Mix Entries) ...............................................550
SB (Substitute Backup) ...................................................554
SBP (System Balancing Parameters) .................................556
SC (System Configuration) ..............................................558
SCAN (Scan Pack Volume)...............................................564
SECOPT (Security Options)..............................................566
SEGARRAYSTART (Array Segmentation Start Size) .............567
SEND (Send Message) ....................................................569
SF (Set Factor) ..............................................................584
SHARE (Shared Family) ..................................................588
SHOW...........................................................................595
SHOWOPEN (Show Open Disk Files) .................................605
SHOWSPARES (Show Spare Disks) ...................................607
SI (System Intrinsics).....................................................609
SL (Support Library) .......................................................611
SM (Send to MCS or Database) ........................................618
SN (Serial Number) ........................................................620
SQ (Show Queue) ..........................................................625
SQUASH (Consolidate Disk Allocation) ..............................627
SS (Send to Station) ......................................................629
ST (Stop) ......................................................................630
STARTTIME (Start Time) .................................................631
STORESAFE ...................................................................632
STRUCTURECACHE (Cache Maintenance) ..........................640
SUPPRESS (Suppress Display) .........................................642
SUPPRESSWARNING (Suppress Warning)..........................644
SV (Save) .....................................................................646
SW (Switches) ...............................................................649
SYSADMIN COMMAND ....................................................651
SYSOPS (System Options)...............................................656
TD (Time and Date)........................................................676
TDIR (Tape Directory).....................................................677
TERM (Terminal) ............................................................680
THAW (Thaw Frozen Library) ...........................................684
TI (Times) .....................................................................685
TL (Transfer Log) ...........................................................686
TR (Time Reset) .............................................................689
TV (Type Volume) ..........................................................701
U (Utilization) ................................................................703
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
Section 2 Memory Dump Processing and

Commands
Memory Dump Commands ..............................................781
Memory Dump Processing ...............................................784
Appendix A Functional Command Groupings

General Categories .........................................................791
Automatic Display Mode (ADM) and ODT Control Commands792
BNA Commands .............................................................794
Data Comm Commands ..................................................795
Directory and Disk File Management Commands ................796
Disk Pack Commands .....................................................798
Dump Commands...........................................................800
Installation and Licensing Commands ...............................801
Job Queue Commands ....................................................802
Log Commands ..............................................................803
Maintenance Commands .................................................804
MCP Commands .............................................................806
Memory Management Commands.....................................808
Peripheral Commands .....................................................810
Printer Commands..........................................................812
Processor Management Commands ..................................814
Program Communication Commands ................................815
System Configuration Commands.....................................817
System Security Commands ............................................818
Tape Commands ............................................................819
Old and New Command Mnemonics ..................................820
Appendix B Using CANDE and WFL at an ODT

Entering CANDE Control Commands at an ODT ..................821
Starting Work Flow Language (WFL) Jobs at an ODT...........823
Appendix C Cold-Start Default Values

Default Options after a Cold-Start ....................................825
Default Status of Units ....................................................833
8600 0395-514 vii

Contents
Appendix D Basic Constructs

Basic Constructs ............................................................835
Appendix E Understanding Railroad Diagrams

Understanding Railroad Diagrams.....................................847
Paths ............................................................................848
Constants and Variables..................................................849
Constraints....................................................................850
Following the Paths of a Railroad Diagram .........................853
Railroad Diagram Examples with Sample Input ..................854
Index ........................................................ 859
viii 8600 0395-514

Section 1
Commands
System Commands Overview

Purpose and Audience
This document is written for system operators. It describes the commands an
operator uses to display system information, start a utility, get a printout,
communicate with the CONTROLLER and the operating system, initialize the data
communications subsystem, take dumps, and perform similar tasks.
This document provides complete descriptions of all system commands. It presents

these commands in alphabetical order for convenient reference. The syntax and
functions of each command are explained, along with suggestions for using the
command most effectively.
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.
Unit and Mix Number Ranges

The number of units and mix numbers that can be specified in a single command is
limited. If you specify too many numbers, the MCP generates the error TOO MANY
NUMBERS. When you include unit and mix number ranges in a command (for
example, RY PK 500 - 509), the range is expanded as if each individual usint or mix
number was explicitly specified. If a command generates the error TOO MANY
NUMBERS, reduce the size of any unit or mix number range.
Network Support Processors (NSPs)

The type of data comm device called the network support processor (NSP) has been
deimplemented. However, the term NSP continues to be used in this manual to refer
to a class of data comm devices, including enhanced data communications data link
processors (EDCDLPs) and data communications host adapters (DCHAs).
Arithmetic operators
The following symbols are the standard arithmetic operators used in this document.
8600 039-514 1
Arithmetic Meaning
Operator
+ Addition
Subtraction
* Multiplication
/ Division
** Exponentiation
Sources for Entering System Commands

This manual describes all the available system commands. These are commands that
you can use to perform general system operations. You can enter the system
commands described in this manual through any of the following interfaces:
Operator display terminals (ODTs).
Operations Center. This utility provides a graphical interface to selected system

commands. Refer to the Operations Center Help.
Menu-Assisted Resource Control (MARC). For further information, refer to the

MARC Operations Guide.
The DCKEYIN function in a privileged Data Communications ALGOL (DCALGOL)

program. For further information, refer to the DCALGOL Programming Reference
Manual.
Using CANDE and WFL at an ODT

If you are using an ODT, you can enter system commands, CANDE commands, or
Work Flow Language (WFL) statements. This manual is concerned primarily with
system commands. However, refer to the following for information about using
CANDE or WFL at an ODT:
CANDE Control Commands
Work Flow Language (WFL)
System Command Descriptions

Each of the system command descriptions in this manual includes the following four
topics:
A brief description of the functions of the command.
A syntax diagram outlining the various options of the command.
2 8600 0395-514
An explanation of each option of the command.
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.
The command descriptions are presented in alphabetical order according to the

preferred mnemonic assigned to each command.
Learning Which Commands to Use

For an introduction to system operations, refer to the System Operations Guide.
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.
TERM Convention Numeric Separator Example
BELGIUM (.) Period 1.234.567
NORWAY ( ) Blank 1 234 567
SWITZERLAND (') Prime 1'234'567
JORDAN No Separator 1234567
ASERIESNATIVE (,) Comma 1,234,567
8600 0395-514 3
The following system commands are affected by internationalization:
ASD (Actual Segment Descriptor)
ASDU (ASD Usage for specified mix numbers)
CU (Core usage)
DU (Disk usage)
O (Overlay)
OL (Display label and path information of a unit)
OT (Show Stack Cell- decimal values only)
PD (and PDRES single instance only)
SHOWOPEN (Show the open files of a disk family)
TI (Times - operations counts only)
For more information, refer to the MultiLingual System Administration, Operations,

and Programming Guide and the TERM (Terminal) command.
4 8600 0395-514
A (Active Mix Entries)

The A (Active Mix Entries) command lists all or selected active jobs, tasks, database
stacks, and freeze control libraries in the mix.
Syntax
<wild card>
<delim>
One of the following characters:
/ \ I ~ ! @ # $ % ^ & * '
The first delimiter must be the same as the second delimiter.
<wild-card string>
A string of characters used to search for a task name. The string can include the
following special characters.
Character Description
Equal sign (=) Matches any sequence of characters
Question mark (?) Matches any single character
Tilde (~) Matches any sequence of characters except a slash (/)
The wild-card string is automatically uppercased, except for characters enclosed in

quotation marks, and the system stops processing the string when it encounters a
space character.
8600 0395-514 5
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":
A NAME LIT ^=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 NAME <wild-card string>

Displays all active tasks with names that match the designated wild-card string,
including any that were suppressed. You can use this option with other options such
as A NAME <wild-card string> SORT CPU.
A MCSNAME = <MCS name>

A MCS = <MCS name>
Display only active jobs or tasks that originated from the specified message control
system (MCS).
A QUEUE
AQ
Display all active jobs or tasks initiated from any queue.
A QUEUE <queue number>

A Q <queue number>
Display only active jobs or tasks initiated from the specified queue.
A CPU
A CPURATE
6 8600 0395-514
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
---Mix-Pri--CPU Time------------ 93 ACTIVE ENTRIES -----------------

12828 50 :00 Job FROMQUEUE3
5456 50 :00 Job J
19149 80 :05 Lib *SYSTEM/NXSERVICES/SERVER
19148 80 :03 Job *SYSTEM/CANDE
19241 80 :00 *CANDE/STACK02
19221 50 :00 COMS/DTP/MONITOR
19218 80 :03 Lib *SYSTEM/COMS/PSH/TTP
19217 80 :01 Lib COMS/PA/FACILITY
19197 50 :00 *SYSTEM/MCPSERVER/COMSTP
E 5510 80 14:17 (NORM) *DCALGOL (NORM)OBJECT/SYMBOL/NED
* 5483 50 :05 (NORM) *DCALGOL (NORM)OBJECT/SYMBOL/XPD
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
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 Pri field shows the priority of the job or task.
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:
One usercode indicates the USERCODE attribute of the task or job.

The other usercode is part of the NAME attribute of the task or job. This
usercode is one of the following:
The usercode that the code file is stored under (an external procedure).
The usercode that the parent of the task or job had when the system initiated
the task or job (an internal procedure).
Compiler tasks display with the following format:
<task usercode> <compiler name> <code file name>
Tasks other than compiler tasks display with the following format:
<task usercode> <task name>
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
--Mix-Pri--CPU Time--------- 8 ACTIVE ENTRIES QUE=5 -------------------

6524 50 :00 Job (SPI) (SPI)RUNMONITOR
6525 50 :00 LIB (SPI) (SPI)OBJECT/SPIMON/PROGRAM/TASKMASTER ON DISKB
6533 50 :02 (SPI) (SPI)OBJECT/SPIMON/PROGRAM/SYSTEMINFO ON DISKB
6528 50 1:14 (SPI) (SPI)OBJECT/SPIMON/PROGRAM/LOGEXTRACTOR ON DISKB
6527 50 :07 (SPI) (SPI)OBJECT/SPIMON/PROGRAM/UTILIZATION ON DISKB
6526 50 :00 (SPI) (SPI)OBJECT/SPIMON/PROGRAM/FILESHIPPER ON DISKB
6459 50 :01 (OPS) *OBJECT/AUTOLABEL
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=""
---Mix--Pri--CPU Time------16 ACTIVE ENTRIES USER= ----------------
5989 80 :07 Job *SYSTEM/CANDE3 ON CANDE

6297 80 :01 *CANDE3/SERVANT01
5993 80 :03 *CANDE3/STACK01
5992 80 :04 *CANDE3/STACK02
5991 80 :10 *CANDE3/STACK03
6701 50 :05 Lib *SYSTEM/MSNET/SUPPORT
6683 50 :00 Lib *SYSTEM/DTS/SUPPORT
6702 50 :00 *DTS/PIPEHANDLER
6644 50 :08 Lib *SYSTEM/MARC/COMMANDER
6638 50 :56 Lib *SYSTEM/DTP/TM ON DISKB
6624 50 :51 Lib *SYSTEM/DSSSUPPORT/DIAGNOSTICS
3674 75 :00 STATUS/CHANGE/MP051
3617 75 :00 STATUS/CHANGE/ECCSA
3209 50 :18 ODT/HANDLER
8600 0395-514 9
Example 4
This example shows the command and response for the SORT CPURATE option:
A SORT CPURATE
---Mix--Pri--CPU Rate------18 ACTIVE ENTRIES (ALL) SORT CPURATE-----

6647 50 2.21% *SYSTEM/MCPSERVER/COMSTP
6664 75 0.59% TCPIP/IP/7000/1
3590 80 0.14% (SILVA) *SYSTEM/NXSERVICES/FILESERVER
6666 75 0.12% TCPIP/BUFFER/7000/1
6458 50 0.09% (SITE) (SITE)OBJECT/UCF/MONITOR
2823 55 0.09% (X) (SITE)OBJECT/UTIL/RUNPM ON PACK
6669 75 0.08% TCPIP/MSS/DATA/7000
6456 80 0.6% Job GRAPHDEBUG_LOGGER
6614 52 0.5% CCF/LOGON/PORT_IN_HANDLER
6668 75 0.3% TCPIP/MSS/CONTROL/7000
6665 75 0.2% TCPIP/ARP/700/1
6451 50 0.1% Lib *SYSTEM/ASSISTANT
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)

The ACCOUNTING command sets and displays task and file resource use selections
for the system, users, and tasks. If the system uses the Secure Access Control
Module software, only security administrators can use this command. For more
information about the ACCOUNTING command, refer to the Security Administration
Guide.
Syntax
Explanation
ACCOUNTING
Displays the current settings for the task and file resource use selections.
ACCOUNTING DEPENDENTTASK IDENTIFIED

Sets the default value for system resource accounting. This value enables the
maximum accounting of resource utilization and provides a complete record of all
task starts and terminations.
ACCOUNTING DEPENDENTTASK ANONYMOUS

Sets the minimum accounting of resource utilization and does not provide
information about task starts and terminations or completed tasks.
ACCOUNTING DEPENDENTTASK UNSPECIFIED

Sets the default value for user and task resource accounting. This value permits
accounting to be specified at the user and task level.
ACCOUNTING FILE IDENTIFIED

Sets the default value for file resource accounting. This value enables the maximum
accounting of resource utilization and provides a complete record of all file openings
and closings.
ACCOUNTING FILE ANONYMOUS

Sets the minimum amount of file resource accounting. No SUMLOG entries are made
for file openings and closings.
ACCOUNTING FILE UNSPECIFIED

Sets the default value for user and task file resource accounting. This value permits
accounting to be specified at the user and task level.
8600 0395-514 11
Examples
Example 1
This example sets the highest priority of system resource utilization accounting:
ACCOUNTING DEPENDENTTASK IDENTIFIED
Example 2
This example sets the minimum level of file resource accounting:
ACCOUNTING FILE ANONYMOUS
12 8600 0395-514
ACQUIRE (Acquire Resource)

The ACQUIRE (Acquire Resource) command enables an active group to acquire
additional resources or to change the TEMPORARY status of already acquired units
and controls. For example, you can use this command to dynamically acquire and
free domains or to enable and disable requestors from memory.
Many of the forms of the ACQUIRE command cause a brief system pause.
A locking mechanism prevents multiple copies of programs from attempting to use

the ACQUIRE (Acquire Resource), CLOSE (Close Pack), FREE (Free Resource),
INITIALIZE (Initialize Disk) , LB (Relabel Pack or Host Control Unit), PG (Purge), RC
(Reconfigure Disk), and UR (Unit Reserved) commands to access the same device
simultaneously. If one of these operations is already in progress when another
command is issued to the same device, the command is rejected and the following
message is displayed:
PK <unit> <command entered> COMMAND REJECTED BECAUSE ANOTHER COMMAND IS USING

THIS UNIT.
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
<CTL specification>
For other syntax elements, refer to Basic Constructs.
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.
The DOMAIN number can be 0 or 1. DOMAIN and SYSTEM are synonyms.
ACQUIRE DOMAIN <number> :SAVE

ACQUIRE SYSTEM <number> :SAVE
Acquire the specified domain and mark all the modules in the domain as saved.
ACQUIRE DOMAIN <number> :READY

ACQUIRE SYSTEM <number> :READY
Acquire the specified domain and ready all the modules whether or not they are
saved.
ACQUIRE DOMAIN <number> :POWERUP

ACQUIRE SYSTEM <number> :POWERUP
Power up, initialize, and acquire the specified domain. These commands do not cause
the system to ready any MSMs.
ACQUIRE MSM <number>

Acquires the domain containing the MSM. The MSM number can be either 0 or 1. The
system marks the remaining modules as saved. The system also marks the
remaining memory storage units (MSUs) in the MSM as saved; you must use the RY
(Ready) command before the system can make them available.
ACQUIRE MSM <number> :READY

ACQUIRE MSM <number> :READY :POWERUP
Acquire the domain containing the MSM. The MSM number can be either 0 or 1. The
system readies the requestor and puts it into use.
14 8600 0395-514
ACQUIRE MSM <number> :SAVE

ACQUIRE MSM <number> :SAVE :POWERUP
Acquire the domain containing the MSM. The MSM number can be either 0 or 1. The
system marks the requestor as user-saved.
ACQUIRE CPM <CPM list>

ACQUIRE IOM <number>
Acquire the domain that contains the specified CPM or IOM. The numbers specified to
identify CPMs or IOMs can be integers in the range 0 through 11. On VM systems,
the range of CPM numbers is 4 through 11. The system then readies the requestor if
the saved state is NOT-IN-USE.
ACQUIRE CPM <CPM list> :READY

ACQUIRE IOM <number> :READY
Acquire the domain that contains the specified CPM or IOM. The numbers specified to
identify CPMs or IOMs can be integers in the range 0 through 11. On VM systems,
the range of CPM numbers is 4 through 11. The system then readies the requestor
and puts it into use.
ACQUIRE CPM <CPM list> :SAVE

ACQUIRE IOM <number> :SAVE
Acquire the domain that contains the specified CPM or IOM. 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. The system marks the requestor as user-saved.
ACQUIRE CPM <CPM list> :READY :POWERUP

ACQUIRE IOM <number> :READY :POWERUP
Acquire, power up, and initialize the domain that contains the specified CPM or IOM.
The system then readies the requestor and puts it into use.
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.
ACQUIRE CPM <CPM list> :SAVE :POWERUP

ACQUIRE IOM <number> :SAVE :POWERUP
Acquire, power up, and initialize the domain that contains the specified CPM or IOM.
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. The system marks the
requestor as user-saved.
ACQUIRE <device type> <unit number list>

Acquires the unit or units identified by the device and unit number list. The system
automatically readies the units unless you use the SAVE option.
ACQUIRE <device type> <unit number list> :SAVE

ACQUIRE <device type> <unit number list> :SA
Acquire the units in the saved statethat is, the units are acquired and saved in one
step.
8600 0395-514 15
ACQUIRE <device type> <unit number list> :TEMPORARY

ACQUIRE <device type> <unit number list> :TEMP
Acquire the designated units until the next halt/load of the system. If group
reconfiguration does not occur when the system is halt/loaded, each unit reverts to a
logically unowned status as a freed device of its partition. In the case of intelligent
peripheral interface (IPI) units, physical ownership is relinquished as long as a usable
physical path remains to the subsystem.
ACQUIRE DLP <device number> OVERRIDE

ACQUIRE DLP <device number> OVERRIDE :TEMPORARY
OVERRIDE specifies that the system is to takeor stealthe specified units from
another system. Because the subsystem enforces ownership of intelligent peripheral
interface (IPI) units, this action might be necessary to acquire such devices when the
partition that owns the devices can not cooperate in physically freeing them.
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.
ACQUIRE CTL <device number list>

Acquires the CTLs identified by the device numbers in the device number list and
brings the 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 and PORT failures. You might need to perform the following steps to recover
CTLs that are involved in such failures:
1. Remedy the hardware problem causing the failure.

2. Enter FREE CTL <device number>.
3. Enter ACQUIRE CTL <device number>.
For example, a BCC-clear or a base power loss requires that you perform this
procedure for each CTL in the affected base.
16 8600 0395-514
ACQUIRE CTL <device number list> :RESERVED

Acquires the CTLs specified by the device numbers in the device number list and
leaves them in the reserved state. If you do not specify the RESERVED option, the
system acquires the CTLs and makes them available for use.
ACQUIRE CTL <device number list> :TEMPORARY

ACQUIRE CTL <device number list> :TEMP
Acquires the CTLs identified by the device numbers in the device number list until
the next halt/load of the system. If group reconfiguration does not occur when the
system is halt/loaded, the CTL reverts to a logically unowned status as a freed device
of its partition. Physical ownership of DLP controls is relinquished as long as there is
still a usable port path to the CTL.
ACQUIRE CTL <device number list> OVERRIDE

ACQUIRE CTL <device number list> OVERRIDE :TEMPORARY
OVERRIDE specifies that the system is to takeor steala CTL from another
partition. Use OVERRIDE only when the partition that owns the CTL cannot be made
to cooperate in giving up physical ownership of the CTL. The rules for stealing a CTL
currently apply only to DLP controls, and are as follows:
The CTL cannot already be owned by the stealing host.

The CTL must be owned by another host.
The base in which the CTL resides must be shared between the stealing host
and the host that currently owns the CTL.
Specifying :TEMPORARY or :TEMP steals the CTL until the next halt/load of
the system. If group reconfiguration does not occur when the system is
halt/loaded, the CTL reverts to a logically unowned status as a freed device of
its partition. Physical ownership of DLP controls is relinquished as long as
there is a usable port path to the CTL.
ACQUIRE NETPORT <device number> LINEID <number>
Acquires the LINEID <number> that is associated with the internal networking port
that is identified by the device number. The LINEID number is either 1 or 2,
depending on the position of the Ethernet port on which the LINEID depends. This
form of the command enables the Ethernet port to be used by networking protocols.
If the LINEID is designated as NEVER ACQUIRE in the Peripheral Configuration

Description, the system responds with the following message:
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
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 =
------------------------ MT STATUS --------------------------------

81*P [000048] 1600 #1 1:0 <07/16/1994> MEMORY/DUMP
82 NOT AVAILABLE TO GROUP
ACQUIRE MT 82
MT82 WILL BE ACQUIRED
This PER display shows that unit 82 was acquired and automatically readied. The
operator then acquires MT 83 in the saved state.
PER MT =
------------------------ MT STATUS --------------------------

81*P [000048] 1600 #1 1:0 <07/16/2005> MEMORY/DUMP
82*P [MIKE ] 1600 S C R A T C H
ACQUIRE MT 83:SAVE
MT 83 WILL BE ACQUIRED
This PER display shows that unit 83 was acquired but not readied:
PER MT
------------------------ MT STATUS -----------------------------

81*P [000048] 1600 #1 1:0 <07/16/2005> MEMORY/DUMP
82*P [MIKE ] 1600 S C R A T C H
83*P SAVED
Example 2
This example acquires the designated control units:
ACQUIRE CTL 4001,4002,4003
CTL 4001 WILL BE ACQUIRED

18 8600 0395-514
Example 3
This example acquires a Telephony Services Platform (TSP) unit:
ACQUIRE TSP 200
TSP200 WILL BE ACQUIRED
TSP200 SUCCESSFULLY ACQUIRED
Considerations for Use

Releasing a Resource
To release a resource from an active group, refer to the FREE (Free Resource)
command.
Ready and Saved States

Each module has either a ready or a saved state as described in the following table.
State Description
Ready Module is available to run or is currently running.
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.
Saveduser Module was saved by an operator request and cannot be

saved readied without another operator request.
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.
Acquiring Units with a Single Command

For units that can be referenced either by device, unit number, or CTL device
number, you need to enter the ACQUIRE command only once. You can use the same
number to reference an NSP either as a CTL or as a unit. For example, you can
acquire NSP 108 by entering either ACQUIRE CTL 108 or ACQUIRE DC 108. It is not
necessary to enter both.
You can acquire the following units by entering a single number:
NSPs, such as enhanced data communications data link processors (EDCDLPs)

or data communications host adapters (DCHAs)
8600 0395-514 19
HYPERchannel (HY) units

Host control (HC) units
Understanding IEA-1 IOPs
The IEA-1 IOP provides two Ethernet connections and supports one internal port for
connectivity between distributed networking software such as TCPIPSUPPORT in the
MCP environment and NNS implementation within the IOP.
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:
ACQUIRE VC <unit number>
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 TSP Units

You must explicitly acquire each unit that makes up a Telephony Services Platform
(TSP) through a separate ACQUIRE TSP <unit number list> command, or you must
list each unit number separately in one ACQUIRE command as follows:
ACQUIRE TSP 200, 201, 202, 203
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)
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.
While a duplicate directory is not required to be on the family member that is to

receive the duplicate access structure, it is recommended that a duplicate directory
be present. Such a practice provides for a reduced probability of losing the access
structure. For additional information, refer to the DD (Directory Duplicate)
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.
AD ON <family name> (<family index>)

Removes a previous and currently unused access structure on the pack specified by
<family name> and <family index>.
Examples
Example 1
AD (2)
8600 0395-514 21
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:

C (Completed Mix Entries)
S (Scheduled Mix Entries)
W (Waiting Mix Entries)
The following shows a typical display for the A command:
*608 80 :01 Job AD (002)
Example 2
AD - ON DISK (2)
7268 PK97 SYSTEM/ACCESS/002 REMOVED ON DISK
22 8600 0395-514
ADM (Automatic Display Mode)

The ADM (Automatic Display Mode) command lets you start or stop automatic
display of current system status information on the same ODT at which the ADM
command is entered. ADM settings can be changed at any time from the ODT.
Automatic display is useful for monitoring the status of scheduled and completed
entries, jobs in the mix, libraries, database stacks, peripheral units such as line
printers, queue settings, messages from the operating system, and other automatic
display information.
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
<mix display command>
<mix display option>
<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:
ADM (A7, W3, S2, C5, MSG) DELAY 4.
24 8600 0395-514
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.
ADM (<timed options>)

If the first item following ADM is a left parenthesis, ADM unconditionally displays the
described pages after the specified time interval. In the time-driven mode, each
group of timed options enclosed in parentheses specifies one page of an ADM
display. Each page is automatically updated and displayed after the interval specified
by DELAY.
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.
Information for the MSG (Display Messages) option is restricted to a maximum of 42

lines of messages, regardless of the number of lines specified.
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
ASD ASD table usage information
C Completed mix entries
CU System memory usage entry (core usage)
DBS Active database stacks
JOBS Job structure
LIBRARIES Frozen library stacks
LIBS Synonymous with LIBRARIES
8600 0395-514 25
Option Meaning
MESSAGES Most recent messages from the system. If the NW option is

MESSAGES specified, only networking messages are displayed. If the NW
NW option is not specified, only non-networking messages are
displayed.
Note: The setting of the CONTROLLER option
SEPARATEMSGS at the time that the message is received
determines whether the messages appear in the MSG or MSG
NW list. Refer to the CO (CONTROLLER Options) command.
MIX Mix entries by job structure (also includes RSVP and DISPLAY
messages)
ML Summary of all queues
MSG Synonymous with MESSAGES
MX Synonymous with MIX
O System overlay utilization
PER Peripheral entries (must be specified by device)
PS Print System status (same as PS STATUS)
S Scheduled entries
U System utilization
W Waiting entries
ADM + (<timed options>)

Adds the new ADM instruction to the current ADM specification, which must be a
time-driven ADM.
<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 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
C Completed mix entries
DBS Active database stacks
JOBS Job structure
LIBRARIES Frozen library stacks
LIBS Synonymous with LIBRARIES
MESSAGES Most recent messages from the system. If the NW option is

MESSAGES specified, only networking messages are displayed. If the NW
NW option is not specified, only non-networking messages are
displayed.
Note: The setting of the CONTROLLER option SEPARATEMSGS
at the time that the message is received determines whether
the messages will appear in the MSG or MSG NW list. Refer to
the CO (CONTROLLER Options) command.
MSG Synonymous with MESSAGES
MIX Mix entries by job structure (also includes RSVP and DISPLAY
messages)
MX Synonymous with MIX
PER Peripheral entries (must be specified by device)
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
<mix display option>

Specifies the entries that are eligible for inclusion in the ADM display. The possible
options are as follows.
Option Description
ALL Displays all entries, including any that were suppressed
SORT CPU Displays entries according to decreasing CPU time used

SORT CPURATE or decreasing CPU processor rate
MCSNAME = <MCS Displays only entries that originated from the specified
name> message control system (MCS)
ADM EVENT PRINTLABEL

This form of the ADM command applies to ODTs that have a hard-copy output device
attached. It produces tape labels in any desired format. The text can be printed
directly on the gummed labels. The quoted string is a literal that identifies the
various data items. The slash (/) causes a carriage return. The number following the
named data items specifies the maximum size that can be used to contain the data.
If the field width of an alpha type item is too short for the data, the rightmost
characters are truncated. If the field width of a numeric item is too short for the
data, the field is filled with asterisks (*). If the field width of a DATE type item is less
than 11 characters, the last two digits of the year are used, as in 08/22/05.
Otherwise, a four-digit date is used, as in 08/22/2005.
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:
PRINTLABEL "TITLE: " TITLE 28/

"TASK: " TASKID 28/
"SERIAL: " SERIALNO 10/
"CYCLE: " CYCLE 4/
"UNIT: " UNITNO 5/
"DENSITY: " DENSITY 4/
DATE 14 TIME 8/
/////
ADM + EVENT PRINTLABEL

Adds the specified items to the PRINTLABEL formatting specifications and displays
the new settings. The PRINTLABEL specifications are retained across halt/loads.
28 8600 0395-514
Examples
Example 1
This example shows the current ADM settings:
ADM
---Mix-Pri-CPU Time------- 5 ACTIVE ENTRIES ---------------------

E 7226 80 14:17 (NORM) *DCALGOL (NORM)OBJECT/SYMBOL/NED
7259 80 6:03 Job *SYSTEM/CANDE ON PACK
7262 80 1:07 *CANDE/STACK01
7248 80 15:08 *SYSTEM/COMS ON PACK
7253 50 14:12 MARC
---Mix-Pri---Elapsed----------- 1 WAITING ENTRY --------------------
* 5663 50 11:14 (ROBY) (ROBY)OBJECT/SYMBOL/GOODUTIL ON TOP
NO FILE OBJECT/SCREENDESIGN/USA ON TOP
---Mix-Pri---Elapsed------------- 1 SCHEDULED ENTRY ----------------
5655 50 7:22 (SMITH) *DCALGOL (SMITH)OBJECT/PATCH/X
---Job-Task-Time--Hist----------- COMPLETED ENTRIES ----------------
* 5653\5655 08:43 EOT (DON) *OBJECT/SPO/II
* 5653\5654 08:42 EOT (DON) *OBJECT/NOSUM
5637\5652 08:40 EOT (GEORGE) (GEORGE)OBJECT/SD ON FIRE
5637\5651 08:40 O-DS (MACS) (GEORGE)OBJECT/TAB ON FIRE
---Mix--Time------------------- MESSAGES -----------------------------
* 5633 08:42 PK51 (KAY)CANDE/TEXT640 CHANGED TO (KAY)PORTFILE ON FIRE
5633 08:41 PK51 (KAY)PORTFILE REMOVED ON FIRE
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.
Type of Entry Refer to
Active Entries A (Active Mix Entries)
Completed Entries C (Completed Mix Entries)
Messages MSG (Display Messages)
Scheduled Entries S (Scheduled Mix Entries)
Waiting Entries W (Waiting Mix Entries)
8600 0395-514 29
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:
ADM EVENT A SORT CPURATE
-Mix--Pri--CPU Rate------18 ACTIVE ENTRIES (ALL) SORT CPURATE-----

6647 50 2.21% *SYSTEM/MCPSERVER/COMSTP
6664 75 0.59% TCPIP/IP/7000/1
3590 80 0.14% (SILVA) *SYSTEM/NXSERVICES/FILESERVER
6666 75 0.12% TCPIP/BUFFER/7000/1
6458 50 0.09% (SITE) (SITE)OBJECT/UCF/MONITOR
2823 55 0.09% (X) (SITE)OBJECT/UTIL/RUNPM ON PACK
6669 75 0.08% TCPIP/MSS/DATA/7000
6456 80 0.6% Job GRAPHDEBUG_LOGGER
6614 52 0.5% CCF/LOGON/PORT_IN_HANDLER
6668 75 0.3% TCPIP/MSS/CONTROL/7000
6665 75 0.2% TCPIP/ARP/700/1
6451 50 0.1% Lib *SYSTEM/ASSISTANT
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 Overhead
The ADM command provides a useful periodic updating of system information for
operators. However, excessive use of ADM can result in visibly larger operating
system overhead, as reported, for instance, by the U (Utilization) system command.
Larger time interval values, fewer ADM specifications, and fewer ODTs using the ADM
command can reduce this overhead.
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:
ADM STORAGE EXCEEDED.
ADM CANCELED DUE TO INSUFFICIENT STORAGE.
30 8600 0395-514
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)
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").
A waiting entry with a NO FILE RSVP message results if a program specified by an

AI command is not present at the time of a halt/load.
Note: The AI command is intended as a replacement for the CS (Change

Supervisor) command, which will be deimplemented in a future release.
Syntax
<AI name>
An AI name is an identifier.
Explanation
AI
Displays the list of programs previously specified by AI commands.
AI <AI name> = <file title>

Updates the name of the code file for an existing entry identified by the AI name.
AI + <AI name> = <file title>

Adds an entry for the code file identified by the AI name.
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 + <file title>
Adds a new entry for the specified code file.
Note: This form of the command will be deimplemented in a future software

release.
AI - <file title>
Deletes the entry for the specified code file.
Note: This form of the command will be deimplemented in a future software

release.
Example
AI
AI HARDCOPY = *SYSTEM/HARDCOPY
AI SUPER = *SYSTEM/SUPERVISOR
8600 0395-514 33
ARCCOPY (Copy Archive Directory)

The ARCCOPY command creates an offline copy of an archive directory for a family.
You can then use this copy to make a backup for the archive directory in case the
directory ever becomes corrupted. Use the ARCREPLACE command to restore the
backup directory. When you enter the ARCCOPY command, if it is free of syntax
errors, the system starts a visible independent runner named ARCCOPY. Use the C
(Completed Mix Entries) command to find out if the ARCCOPY command has
completed.
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.
ARCCOPY <family name> <file title> (<family index>)

The family index specifies the member of the family to which the archive directory is
to be copied.
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.
ARCCOPY PACK BACKUPARCHIVE/PACK ON WORKPACK (1)
34 8600 0395-514
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
--Mix--Time------------------- MESSAGES --------------------

*4080 16:26 A NEW ARCHIVELOG HAS BEEN CREATED
4080 16:25 THE ARCHIVELOG WAS RELEASED
8600 0395-514 35
ARCDUPLICATE (Duplicate Archive Directory)

The ARCDUPLICATE command creates or deletes a duplicate copy of an active
archive directory for a disk family.
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.
ARCDUPLICATE ON <family name> (<family index>)

Creates a duplicate archive directory for the specified catalog family on the family
member specified in the value for <family index>. An archive directory for the
catalog family should not be active when this command is entered.
ARCDUPLICATE - ON <family name> (<family index>)

Removes the duplicate archive directory for the specified catalog family from the
family member specified in the value for <family index>.
Examples
Example 1
This example creates a duplicate archive directory for the family named WORKPACK
on family member 2:
ARCDUPLICATE ON WORKPACK (2)
Example 2
This example deletes the duplicate archive directory for the family named
WORKPACK on family member 2:
ARCDUPLICATE - ON WORKPACK (2)
36 8600 0395-514
ARCREPLACE (Replace Archive Directory)

The ARCREPLACE command replaces an archive directory with a backup archive
directory that was previously saved. You can use this command when a disk family is
recovered or moved by first creating a new family with the same name, then copying
files to that new family. In this case, after the original disk family is closed, this
command is used to instruct the MCP to associate the original disk family archive
directory with the new disk family.
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.
ARCREPLACE PACK BACKUPARCHIVE/PACK ON DMSIITEST
8600 0395-514 37
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.
LB PK92 NAME=XPACK OLDNAME=WORK

ARCREPLACE XPACK SYSTEM/ARCHIVE/WORK/001 ON CATPACK
REMOVE OLD/ARCHIVE/XPACK/001 FROM CATPACK
38 8600 0395-514

The ASD (Actual Segment Descriptor) command displays information about the ASD
table and how it is being used, and (if previously specified) the amount of memory to
be used to calculate the size of the ASD table. You can also use this command to
change the parameters used to calculate the target size of the ASD table for any
future halt/loads.
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:
ASD table size = (total memory/<factor>)
The total memory is the total physical memory (in words) available online to the
system.
ASD <factor> <memory size> MEGAWORDS

Specifies the factor and the amount of memory used to calculate the size of the ASD
table at the next and all subsequent halt/loads. The memory size value is an integer
that specifies the number of megawords that are to be available for the calculation
8600 0395-514 39
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
---------------------- ACTUAL SEGMENT DESCRIPTORS ----------

CURRENT FACTOR : 40 WORDS/ASD
TOTAL ASDS : 419,439
CURRENTLY IN-USE : 67 %
MAXIMUM IN-USE : 78 %
ASDTABLE ENTRY SIZE: 4 WORDS/ASD
Example 2
ASD 60
---------------------- ACTUAL SEGMENT DESCRIPTORS ----------

NEW FACTOR : 60 WORDS/ASD (EFFECTIVE NEXT H/L)
Example 3
ASD
----------------------- ACTUAL SEGMENT DESCRIPTORS ------------

CURRENT FACTOR : 60 WORDS/ASD BASED ON MEMORY OF : 29,360,128 WORDS
40 8600 0395-514

Example 4
ASD 50 28 MEGAWORDS
----------------------- ACTUAL SEGMENT DESCRIPTORS -----------

NEW FACTOR : 50 WORDS/ASD BASED ON MEMORY OF:
29,360,128 WORDS (EFFECTIVE NEXT H/L)

For best results, the number of ASDs on a system should be slightly more than the
expected (or previously used) maximum number of ASDs in use. The system
automatically begins taking action to curb ASD usage when utilization reaches 95
percent. The ASD table size should be set after careful analysis of the site
requirements. If the factor is set too high, the system might run out of ASDs,
resulting in possible system failure. If the factor is set too low, use of system
memory is not optimized.
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)
ASDU (ASD Usage)

The ASDU (ASD Usage) command indicates, for a given job or task, the number of
actual segment descriptors (ASDs) currently in use and the maximum number of
ASDs used by the job or task since it began.
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
ASD USAGE BY TASK

0007 ASD USAGE:
CURRENTLY IN-USE: 69 ASDS
MAXIMUM IN-USE: 90 ASDS
1234 ASD USAGE:
CURRENTLY IN-USE: 80 ASDS
MAXIMUM IN-USE: 169 ASDS
5449 ASD USAGE:
CURRENTLY IN-USE: 5,522 ASDS
MAXIMUM IN-USE: 7,079 ASDS
42 8600 0395-514
AT (At Remote Host)
AT (At Remote Host)

The AT (At Remote Host) command directs a system command to another host in the
network. Any response to the command appears at the ODT at which the command
was entered.
Syntax
Explanation
The software determines which service to use for the AT command according to the
following order:
1. The command specifies the service.

Either the HOSTSERVICES (or HS) option or the FTAM option is specified as the
service option in the command.
2. The type of command indicates the service.

Either a remote system command, which is supported by Host Services, or a File
Transfer, Access, and Management (FTAM) command is included in the AT
command. The software determines the type of command that was entered and
routes the command to the appropriate host using that service.
3. Default selection.
The software determines the service most likely able to support the command
and then automatically routes the command to that service.
If HOSTSERVICES or FTAM is specified in the AT command but the service is not

available, then the entire AT command is rejected.
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.
The remote host response to the AT command is restricted to a maximum of 255

lines. The remaining output is truncated without any warning.
Examples
Example 1
AT BLUE W
***********REPLY FROM BLUE****************
-Job-Task-Pri---Elapsed---- 1 WAITING ENTRY ---------------------

1566/1568 50 1:10 *SYSTEM/DUMPANALYZER ON HLDISK
NO FILE MEMORY DUMP (MT) #1
Example 2
AT BLUE J
***********REPLY FROM BLUE*****************
-Mix-Pri----------------- JOB ENTRIES -----------------------------

1566 50 JOB BEGIN JOB;RUN *SY
1568 50 *SYSTEM/DUMPANALYZER ON HLDISK
Example 3
AT BLUE 1568 FA TITLE=(USER)A ON DISK
**********REPLY FROM BLUE*****************
NO RESPONSE GENERATED

Host Services permits access to systems that are part of either a BNA or an OSI
network.
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.
With each system command sent to another host, HOSTSERVICES provides a

usercode that the host can use to satisfy its security or access control restrictions. If
the command is entered at an ODT to which a terminal usercode was assigned (refer
to TERM (Terminal)), that usercode is used. If the command is entered through the
DCKEYIN interface, the usercode of the program is used. Otherwise, the host
44 8600 0395-514
usercode is used. If there is no terminal usercode or host usercode, an error occurs

and the AT command cannot be used. Refer to the HU (Host Usercode) command.
When a system receives a system command from a remote host, it determines

whether the command came from a usercode defined as a SYSTEMUSER. A remote
user whose usercode is marked with the SYSTEMUSER attribute has the same ODT
capabilities as the ODT operator on the local system.
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
BADFILE Bad File
C Completed Mix Entries
CU Core Usage
DBS Database Stack Entries
DS Discontinue
DUMP Dump Memory
FA File Attribute
FR Final Reel
HI Cause EXCEPTIONEVENT
J Job and Task Display
LIBS Library Task Entries
MSG Display Messages
MX Mix Entries
NF No File
OF Optional File
OK Reactivate
8600 0395-514 45
Command Meaning
OT Inspect Stack Cell
RM Remove
SQ Show Queue
ST Stop
THAW Thaw Frozen Library
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
HOSTNAME Host Name
ID Initialize Data Comm
MM Memory Module
SC System Configuration
SI System Intrinsics
SL Support Library
TD Time and Date
WM What MCP
A task named ODT/HANDLER handles the transfer of system commands and

responses between hosts. HOSTSERVICES automatically starts ODT/HANDLER after
receiving an AT command on the local host or an ODT request from a remote HS
host. The ODT/HANDLER is an independent runner that terminates automatically
when Host Service operations are terminated or when no system commands are sent
to or received from other hosts for five minutes.
46 8600 0395-514
AT (At Remote Host): Use with FTAM
AT (At Remote Host): Use with FTAM

FTAM permits access to MCP and non-MCP systems. File names and directory names
included as part of the AT command must use the syntax required by the remote
host. This syntax is called the universal file name, which is described in the WFL
Programming Reference Manual.
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>
The USERCODE attribute consists of three componentsusercode, password, and

account numbereach separated from the others by a slash (/). The total length of
the three components and any slashes or quotation marks (' or ") cannot exceed
255 characters.
To prevent lowercase usercode data from being translated to uppercase prior to

transmission, enclose the data string in apostrophes (') or in quotation marks ("). For
a full discussion of the USERCODE attribute, refer to the WFL Programming
Reference Manual.
After all the delimiters are stripped out, the three components are interpreted by
FTAM in the following way:
The usercode is converted to the FTAM Initiator-Identity parameter.

The password is converted to the FTAM Filestore-Password parameter.
The account number is converted to the FTAM account parameter.
When you specify the optional USER statement, you must enter it before the
command text and follow it with a semicolon (;) as shown in the following
example:
USER = <usercode>/<password>;<file command>
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>
USER = ""/<password>;<file command>
When the USER statement is not specified, a usercode is inherited and

converted to the FTAM Initiator-Identify parameter. The FTAM Filestore-
Password parameter and Account parameters are not sent to the remote host.
The usercode to be inherited depends on the source of the FTAM file
management command.
CHANGE (FTAM File Management Command)

This command is used to change the name of the specified files.
Syntax
Explanation
The first universal file name must specify an existing file at the remote host and
must also include a volume identification.
FILES (FTAM File Management Command)

This command is used to generate a list of the available files at the remote host. A
directory or a specific file can be defined in the command.
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.
LFILES (FTAM File Management Command)

This command is used to access detailed information about the available files. In
addition, a list of file attributes can be specified as part of the command to control
the amount of information that is displayed. The following attributes are available:
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.

This command is used to send a request to change attributes at the remote host.
The remote host returns a response indicating either complete rejection of the
request or general acceptance of the request. If the request is accepted, the remote
host changes only the attributes it supports prior to returning the response. The
remote host does not indicate which attributes, if any, are supported.
Syntax
8600 0395-514 49
<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:
***** NONE OF THE REQUESTED ATTRIBUTES IS SUPPORTED BY FTAM HOST

<remote host name>; NO MODIFICATION WAS ATTEMPTED.
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:
An LFILES command can be used to interrogate the new attribute value(s)
If the same attribute is specified more than once, the last specified value is used.
The remote host returns the following response:
DUPLICATE SPECIFICATION FOR <attribute name>;

WILL USE: <attribute value>
50 8600 0395-514
REMOVE (FTAM File Management Command)

This command is used to remove the specified files.
Syntax
FTAM Command Examples

The examples that follow show various FTAM command options. Be aware of the
constraints concerning the USER statement. Refer to AT (At Remote Host): Use with
FTAM in this section.
Example 1
This example inquires about all files on the specified host:
AT hostname [FTAM] USER = ""; FILES
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.
AT hostname [FTAM] USER = MYUC/MYPW;FILES
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.
AT hostname [FTAM] USER = "";LFILES
AT hostname [FTAM] LFILES:ALTERDATE
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 (' ').
AT hostname [FTAM] USER = "";FILES 'B:DESIGN.DOC'
Example 5
This example changes the name of a file on the remote host:
AT hostname [FTAM] USER = "";CHANGE old/file/name TO new/file/name
8600 0395-514 51
Example 6
This example removes the specified file:
AT hostname [FTAM] REMOVE scratch/file/name
Example 7
This example changes the file name attribute of a file that belongs to the $AB
usercode:
AT FTAMHOST [FTAM] USER = '$AB'; MODIFY 'X.Y' (FILEN = Z)
Example 8
This example changes three attributes of a file named X:
AT FTAMHOST [FTAM] USER = A/B; MODIFY X (FUTUREFILESIZE = 9876543,

FILEAVAILABILITY IMMEDIATE, STORAGEACCOUNT 1234)
52 8600 0395-514
AUTORESTORE (Archiving AUTORESTORE Option)

The AUTORESTORE command displays or sets the system archiving AUTORESTORE
option. This option, in conjunction with the AUTORESTORE task attribute, determines
whether or not the system automatically tries to reload a backup copy of a disk file
when a NO FILE condition occurs for a nonresident disk file.
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.
A task waiting on an ACCEPT message appears in the display requested in a W

(Waiting Mix Entries) command.
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:
---Mix-Pri-Elapsed----------- 1 WAITING ENTRY -----------------------

* 1528 50 :10 JOB (SITE)TEST
ACCEPT:WHAT TO DO
1528 AX COMPLETE THE SQUARE

Queuing AX Messages
The capabilities of the AX command are controlled by the QUEUEDAX system option.
If you set QUEUEDAX by entering SYSOPS QUEUEDAX SET or one of its variants, the
system can queue a maximum of 250 AX messages per task provided that the total
length of the messages in bytes does not exceed (65532 (4 * <message count>)).
If you reset the option with the SYSOPS QUEUEDAX RESET command or one of its
variants, the system queues only one AX message per task, and subsequent
messages overwrite previous messages.
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:
Flushes the entire AX queue

Maintains from that point a queue depth of one
No warning messages are displayed if AX messages are discarded because
the limit of 250 messages was exceeded or the maximum message length
was exceeded or a recent SYSOPS QUEUEDAX RESET action discarded all
previously queued messages.
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)
BADFILE (Bad File)

You can use the BADFILE (Bad File) command in response to certain MT <unit
number> RECOPY REQUIRED <file name> RSVP messages.
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 MT114 RECOPY DATA/FILE
1970 BADFILE
MSG
1970 PK47 DATA/FILE COPIED AS BADFILE/DATA/FILE
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 +
BNA will be initiated
Example 3
BNA -
BNA shutting down
The message BNAV2 IS UNAVAILABLE appears only after BNA shuts down. This
process might be lengthy.
8600 0395-514 57
BNA

The SL (Support Library) command specifies the file title of the required libraries for
BNA Version 2. These libraries are
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.
Note: BNA Version 1 has been deimplemented.
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
The display returned by a BR command depends on the value of the

CHECKPOINTABLE and BRCLASS attributes of the task and its job. Task 1234 has
several possible responses.
If you are not allowed to use the BR command to initiate a checkpoint for this task:
TASK 1234 IS NOT CHECKPOINTABLE BY THE OPERATOR
If you can use the BR command for this task:
TASK 1234 IS CHECKPOINTABLE
If the task is not allowed to continue at the end of the checkpoint:
TASK 1234 IS CHECKPOINTABLE (CANNOT CONTINUE AFTER BR)
60 8600 0395-514
BR (Breakout)
Example 2
2345 BR +
Either of the following responses might appear:
TASK 2345 : CHECKPOINT REQUESTED

TASK 2345 : CHECKPOINT REQUESTED (CANNOT CONTINUE AFTER 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
Either of the following responses might appear:
TASK 5678 : CHECKPOINT RUNNING

TASK 5678 : CHECKPOINT RUNNING (CANNOT CONTINUE AFTER 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
Any of the following responses might appear:
TASK 6789 : RESTARTING

TASK 6789 : RESTARTING (PROGRAM)
TASK 6789 : RESTARTING (ONCEONLY)
TASK 6789 : RESTARTING (MULTIPLE)
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

The C (Completed Mix Entries) command lists recently completed jobs and tasks and
specifies the reasons for their termination.
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:
-Job-Task-Time--Hist------ 10 COMPLETED ENTRIES -------------------

1886\1928 12:22 SNTX (PRIYU) *ALGOL (PRIYU)CANDE/CODE590 ON FIRE
1925\1925 12:22 EOJ (NORM) JOB *SYSTEM/XREFANALYZER
1923\1923 12:21 EOJ (NORM) JOB NEDCOMPILE
1923\1924 12:21 EOT (NORM) *DCALGOL OBJECT/SYMBOL/NED
1517\1922 12:20 EOT (FARZIN) (FARZIN)CANDE STARTER
1855\1918 12:19 EOT (ROBY) (ROBY)WFLCODE ON PACK
1855\1919 12:19 EOT (FARZIN) *LIBRARY/MAINTENANCE
1855\1916 12:17 EOT (ROBY) *LIBRARY/MAINTENANCE
62 8600 0395-514
The heading line appears on the first page of the Completed Entries display and on
the ADM display of completed mix entries.
The completion time of the task or job is shown in 24-hour format.
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
?-DS Discontinued. The reason is not known because

the history was not set.
A-DS Discontinued because of invalid job attributes.
D-DS Data comm was discontinued.
E-DS Discontinued because of a database error.
EOJ End of job.
EOT End of task.
F-DS Discontinued because of a fault (for example, a

divide by zero or segmented array error).
I-DS Discontinued because of an I/O error.
N-DS Discontinued because of a networking error.
O-DS Discontinued by the operator.
P-DS Programmatically discontinued.
Q-DS Discontinued because the job failed queue

insertion.
R-DS Discontinued because of a resource limitation

(for example, a print limit exceeded or stack
overflow).
S-DS Discontinued by the system.
SNTX Syntax error.
U-DS Discontinued for an unknown reason.
The name of the task or job is shown, prefixed by the usercode of the originator.
8600 0395-514 63
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
---Job--Task--Time--Hist--------5 COMPLETED ENTRIES USER= PDW--------

* 4118/4118 14:18 EOJ (PDW) JOB COPY/MCP511
* 4118/4119 14:18 EOT (PDW) *LIBRARY/MAINTENANCE
* 2286/4117 14:16 EOT (PDW) (PDW)CANDE STARTER
* 2286/4035 14:06 EOT (PDW) *OBJECT/ED ON SYS511
* 3457/3457 14:04 EOJ (PDW) JOB (MAIL)SYSTEM/RUNMAIL ON PACK
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.
FILENAME SECURITY TYPE
MY HOST MY HOST GROUP
APPLICATION GROUP MY USERCODE
REQUESTED CHAR SET TRANSLATE
OFFER TYPE MATCHING STATUS
MY NAME YOUR NAME
MY CODEFILE INTNAME
USING PROCESS YOUR HOST
SUBPORT INDEX IGNORE DIRECTORY
REQUESTED YOUR YOUR HOST GROUP

USERCODE
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)
CACHE (Disk Cache)

The CACHE (Disk Cache) system command controls the cache memory status of
disks, displays cache statistics for the entire system, and dynamically resizes the
amount of memory allocated to the disk cache.
Note: This command is not supported on MCPvm systems.
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
Disk cache memory size
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
CACHE + PK <unit list>

Starts caching for the specified units.
8600 0395-514 67
CACHE (Disk Cache)
CACHE PK <unit list>

Stops caching for the specified units. This command also stops maintaining the disk
cache statistics for the specified units.
CACHE MEMORY <cache size>

Dynamically resizes cache memory. If <cache size> is less than the current size of the memory
allocated to the disk caching subsystem, the amount of memory allocated to the disk caching
subsystem is decreased to <cache size>. Setting the <cache size> to zero suspends disk
caching.
If <cache size> is greater than the current size of memory allocated to the disk caching
subsystem, the amount of memory allocated to the disk c aching subsystem is increased to
<cache size>.
Examples
Example 1
CACHE
Disk Caching Statistics:

Caching Packs = 35
Overall ReadHits/Requests: 76% Cache Size: 10 Mwords
Cache: 70 Reqs/Sec 336 Kbytes/Sec
% % %
Reqs/ Rhit/ Read/ Rhit/ Kbytes/
PK Sec Read All All Sec
165 SYSTEM #1 2 75 23 17 5
166 CAE #1 1 100 44 44 1
176 DISK #1 6 100 49 49 5
184 PACK #1 3 23 96 22 38
185 X3 #1 3 94 72 67 7
187 BDRIVE #1 55 97 100 97 280
The CACHE command displays the following items:
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
PK 149 CACHING STARTED
Example 3
This example turns off caching for disk pack 149:
CACHE - PK149
PK 149 CACHING STOPPED
Example 4
This example resizes cache memory to 16 megawords:
CACHE MEMORY 16 MWORDS
CACHE MEMORY WILL BE RESIZED
CACHE MEMORY RESIZED TO 16 MWORDS
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:
CC MOVE XYZFILE TO NEWFAMILY
Example 2
The following command passes the WFL statement RESTORE XYZFILE ORIGIN
NEWFAMILY FROM ATAPE; to the WFL compiler for processing:
?RESTORE XYZFILE ORIGIN NEWFAMILY FROM ATAPE;

The BEGIN JOB construct can be used as an alternative to the CC or ? system
commands to pass a WFL statement to the WFL compiler.
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)
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 CF command verifies that the designated file exists on either
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.
Before you can use a RECONFIGURE GROUP (Reconfigure System) command to

reconfigure the system to any configuration other than DEFAULT or MINIMAL, you
must specify a configuration file.
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:
NO CONFIGURATION FILERECONFIGURATION ABORTED.
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 <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
SYSTEM CONFIGURATION FILE: XYZ ON DISK ESTABLISHED
Example 2
CF
CONFIGURATION FILE: XYZ ON DISK
Example 3
CF NEW/CONFIG ON MYFAMILY
SYSTEM CONFIGURATION FILE: NEW/CONFIG ON MYFAMILY ESTABLISHED
Example 4
CF+
SYSTEM/CONFIGURATION IS THE CONFIG. FILE

If security administrator status is authorized for the system, a security administrator
usercode is required to execute this command.
72 8600 0395-514
CHECKFILE (Check for Nonresident Files)

The CHECKFILE system command displays information for support library function
names that point to code files that are not resident.
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.
CHECKFILE SL <function name>

Displays the file name associated with the given function and whether that file is
resident on disk.
CHECKFILE SL * <function name>

Displays the file name and attributes of the given function and indicates if the file is
not resident on disk.
Examples
Example 1
CHECKFILE SL
ALL FILES REFERENCED BY 'SL' ARE RESIDENT
8600 0395-514 73
Example 2
CHECKFILE SL *
SL INSTALLSUPPORT = (KONA)SYSTEM/ISUPPORT ON PACK

*** NOT RESIDENT ***
TRUSTED, LINKCLASS = 1
SL INSTALLSUPPORT3 = (KONA)501IC/SYSTEM/ISUPPORT ON UPS
*** NOT RESIDENT ***
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
TSP200 HAS BEEN SUCCESSFULLY CLEARED AND REINITIALIZED

The action of the CL command depends on the system type and on the status of the
unit. The following text shows how the system handles the CL command for units in
various states.
CL Actions for Disk Packs

When you enter the command CL PK or CL DK, use the following table to interpret
the information that the system reports.
Suspended, No In Use by Action Code

Path, or Not Ready? MCP?
Yes Don't Care CANCEL
No Yes CANCEL
No No None
CL Actions for Units Other Than Disk Packs

When you enter the command CL followed by a device mnemonic other than PK or
DK, use the following table to interpret the information that the system reports.
Suspended In Use by User Action Code

Unit? Task?
Yes Yes DS*
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.
None No operations are canceled, and no tasks are discontinued.
Effects of the CL Command on Selected Unit Types

In general, the CL command does not work on disk or pack units unless the unit is
assigned to an operating system procedure such as RECONFIGURE GROUP. For
example, CL works only if a mix number appears in the OL (Display Label and Paths)
command display for the unit.
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
DC For Network Support Processors (NSPs), discontinues the associated

DCCONTROL stack and discontinues any associated NSP data comm
stations.
HC Discontinues the associated intersystem control (ISC) stack.
HY Discontinues the associated NETEX (Network Executive) stack and any

dialogs that it was conducting through the HYPERchannel DLP.
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.
NP Discontinues the associated NP/CONTROLLER/nnn stack and

disconnects any associated BNA V2 stations. This process happens only
if the NP is already in a saved state.
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.
VC The CL VC command never causes user tasks to be discontinued; they

are always canceled.
The system needs to execute only one CL VC <unit number> command
to clear all 26 VC units outboard of the same VIM DLP.
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)
CLOSE (Close Pack)

The CLOSE (Close Pack) command releases the label information for a disk or disk
pack unit and logically detaches the unit from the system.
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.


THIS UNIT.
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.
If a code file has been the subject of an SL (Support Library) or an RP (Resident

Program) system command, the code file might appear as being in-use and be listed
in response to a SHOWOPEN (Show Open Disk Files) system command. If no other
files than these cause the pack to appear in-use, the pack is closed.
CLOSE PK <unit number> :DS

CLOSE CD <unit number> :DS
For use in emergency situations, clear all users from a pack and close the pack. The
command attempts to discontinue (DS) all tasks that have files open to the pack or
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:
DS INITIATED BUT NOT COMPLETE
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
PKO65 WILL BE CLOSED

PKO65 UNIT CLOSED
PER PK
-----PK STATUS-----
65*U C L O S E D
RY PKO65
PK065 WILL BE READY
Example 2
This example closes PK066 and cancels all queued I/O operations on that pack:
CLOSE PKO66:DS
PKO66 WILL BE FORCIBLY CLOSED

PKO66 UNIT CLOSED
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
CD 1302 WILL BE READY

If any files are open on the specified disk pack, the CLOSE command without the DS
option terminates with a UNIT IN USE message. The CLOSE command has no time
limit for computing the number of open files; therefore, the system might seem
unresponsive until the CLOSE command finishes or is terminated.
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.
On cataloging systems, if you close a member of a nonvolumed family that is either

a base pack or contains a duplicate directory, the time that the system takes to
delete all the cataloging information for that family can be lengthy. In addition, the
following message appears at intervals during the process:
DELETING CATALOG INFORMATION nn% <family name> [<serial number>]
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>
<fam index list>
<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:
A heading that specifies the number of families in the display.

The family base pack unit number.
CM # <file name>
CM <file name>
Change the operating MCP code file on the current halt/load family to the specified
file name. For these commands, the target family is always the current halt/load
pack. A halt/load to the new operating system follows.
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:
1. Enter the command OP + OKTIMEANDDATE.

2. Enter the ??PHL command to halt/load the system.
3. When STARTSYSTEM stops and asks you to verify the time and date, do the
following:
1. Enter the command HS so that no jobs or tasks can be initiated.
2. Enter TIMEOK so that STARTSYSTEM can proceed.
3. If your installation normally runs with OP OKTIMEANDDATE reset, enter the
command OP OKTIMEANDDATE.
4. When the halt/load disk is initialized, enter the CM command with the options
you need.
CM
Cancels a pending MCP change.
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)
CM ON <family name> :DELAY

Removes the reference to the delayed MCP from the specified family.
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.
CM <file name> ON <family name>

Creates a family with halt/load capability with the indicated code file. The target
family is specified by the family name. The current halt/load pack cannot be specified
in this command.
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 <file name> : DELAY

Sets the specified code file as a delayed MCP. The code file is used whenever the
system is forced to halt/load. The code file is loaded as a temporary MCP and can
become the permanent MCP after the system is running.
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 #).
<family index list>

Specifies duplicate MCPs on the specified members of a multipack family. One
advantage of using duplicate MCPs is that read operations to the MCP code file are
rotated between the duplicate files, which reduces the I/O activity on the base pack
of the halt/load family.
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:
1. Enter the following command:

CM <file name> <family index list>
The system displays the following message:
CM PENDING, WAITING FOR NULL MIX
2. Enter the following primitive command to force the process to proceed

without waiting for the null mix:
??CM <file name>
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:
The list cannot contain duplicate numbers.

If you specify a list and direct the CM command to the current halt/load pack,
you must include in the list the family index of the current halt/load pack.
Each unit referenced in the command must be suitable for use as a base
pack. That is, the unit must be either a base pack or a continuation pack with
a duplicate directory. Refer to the DD (Directory Duplicate) command.
Otherwise, the message CM INVALID OR MISSING DISK appears.
When you specify a family index list, the system cancels the delayed MCP on
that family.
When the system is running with duplicate MCPs, it adds to the file name a suffix of
the form FMLYINXnnn, where nnn represents the three-digit family index number of
the member on which the code file resides.
<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)
The CM + HLDUMPDISK command cannot direct a dumpdisk file to a mirrored set

or to a family containing a mirrored set. If you make such an attempt, the
system returns an error message.
HLDUMPDISK
Immediately removes the SYSTEM/HLDUMPDISK/<nnn> file from use.
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)
NO MCP FOUND ON STANDBY H/L UNIT <family name>.

IT WILL NOT BE UPDATED.
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
SYSTEM/DELTA/MCP511 NEXT MCP, MEMONLY
Example 3
This example changes the MCP code file on the current halt/load family to the
specified file name
CM SYSTEM/DELTA/MCP511
SYSTEM/DELTA/MCP4511 WILL BE THE NEXT MCP
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)
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
CM STATUS : (2 CM'ED FAMILIE

MCP : *SYSTEM/MCP/501 ON BACKPACK
BASE PACK : (PK418)
CREATION DATE : Friday January 21, 2005 2005021)
HLDUMPDISK : RESET
STANDBY H/L UNITS:
A18HL (PK431) (CURRENT H/L UNIT)
MCP : *SYSTEM/MCP/501 ON A18H
BASE PACK : (PK431) (CURRENT H/L FAMILY)
CREATION DATE : Friday January 21, 2005 2005021)
HLDUMPDISK : RESET
STANDBY H/L UNITS:
A18HL (PK418) (ON-LINE)
Example 7
This example creates a halt/load DUMPDISK file on the halt/load family.
CM + HLDUMPDISK
CM OPTIONS WILL BE CHANGED
90 8600 0395-514
CM (Change MCP)

Using Duplicated or Triplicated MCPs
If you want to use duplicated or triplicated MCPs on your system, the CM procedure
needs two or three copies of the MCP code file each time you change MCPs. You can
use either of the following methods to create duplicated or triplicated copies of the
MCP code file:
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:

CM <file name> <family index list>
The system displays the following message:
CM PENDING, WAITING FOR NULL MIX
2. Enter the following primitive command to force the process to proceed

without waiting for the null mix:
??CM <file name>
Allowing the CM Procedure to Copy the MCP Code File

To let the CM procedure generate the extra copies of the MCP code file, perform the
following 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:
CM <file name> (<family index list>)
The command syntax for the standby families is as follows:
CM <file name> ON <family name> (<family index list>)
Copying the MCP Code File Yourself

To make the extra copies of the MCP code file yourself, perform the following steps:
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:
CM <file name>/FMLYINX<nnn> (<family index list>)
The command syntax for the standby families is as follows:
CM <file name>/FMLYINX<nnn> ON <family name> (<family index list>)
Using CM? to Find Out if a Pack Can No Longer Be Halt/Loaded

If a REPLACE (Replace Pack Volume) command finds bad sectors or if you perform a
DD command on a halt/load capable pack, the pack is no longer halt/load capable.
The REPLACE and DD commands do not result in any warnings, but you can use
the CM? command to find out if the family is no longer halt/load capable.
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?
[[[ ERROR ]]]
Input/output (I/O) errors or data structure inconsistencies on the specified family

can cause this situation. Also, there is a sequence of DD and CM commands that
produces a family with halt/load capability with no MCP.
ERROR IN STRUCTURES ON STANDBY H/L UNIT <family name>. IT WILL NOT
BE UPDATED.
Input/output (I/O) errors or data structure inconsistencies were encountered
while the preserved structures were being located on the specified family, or I/O
errors were encountered while these structures were being preserved. The
specified family remains in the list of standby halt/load families for the current
halt/load family, but its structures are not updated. In the response to the CM?
[[[ ERROR ]]]
STANDBY H/L UNIT <family name> NOT FOUND.

The specified family was not found during the system initialization following the
most recent halt/load. The specified family remains in the list of standby
halt/load families for the current halt/load family. In response to the CM?
[[[ OFF-LINE ]]]
WARNING: <family name> IS NO LONGER AN ONLINE STANDBY H/L UNIT.

The specified family has been deleted from the list of standby halt/load families
for the current halt/load family as the result of a CM, PG, or RC command, or was
taken offline by the CLOSE command. In the latter case, the specified family
remains in the list of standby halt/load families for the current halt/load family,
but its structures are not updated. In the response to the CM? command, the
specified family is flagged with the following phrase:
[[[ OFFLINE ]]]
PK<unit number> IS NOT A STANDBY H/L UNIT.

The command CM STANDBY ON <family name> was entered, but the specified
family does not contain a list of standby halt/load families.
PK<unit number> IS NOT CMED.
The command CM + STANDBY ON <family name> was entered, but the specified
family is not halt/load capable.
8600 0395-514 93
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
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:
Unable to obtain memory for TRACE - Request Aborted
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
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
Examples
Example 1
The following CO command example displays the current option settings:
CO
--------------------------CONTROLLER OPTIONS-------------------------
Compile time options are:

Diagnostics
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

Diagnostics
Errordp is SET.
Input is RESET.
Monitor is RESET.
Suppresswarning is SET.
Trace is RESET.
96 8600 0395-514
Example 3
The following example resets the ERRORDP option and sets the SUPPRESSWARNING
option:
CO - ERRORDP, + SUPPRESSWARNING

Diagnostics
Errordp is RESET.
Input is RESET.
Monitor is RESET.
Suppresswarning is SET.
Trace is RESET.
8600 0395-514 97
COMPILERTARGET (Set Default Target Value)

The COMPILERTARGET (Set Default Target Value) command sets the default value
for the compiler option TARGET.
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.
THIS CS520 CS7101 LX6000
ALL CS580 CS7201 LX7000
LEVEL5 CS585 FS1100 NX6820
LEVEL6 CS590 FS1300 NX6830
CS180 CS595 FS1400 VSE500
CS185 CS680 FS1600
CS300 CS690 LX100
98 8600 0395-514
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.
LEVEL5 currently includes the following systems.
CS180 CS595 LX100
CS185 CS7101 LX6000
CS300 CS7201 LX7000
CS520 FS1100 NX6820
CS580 FS1300 NX6830
CS585 FS1400 VSE500
CS590 FS1600
LEVEL6 currently includes the following systems.
CS680 CS690
COMPILERTARGET
Displays the current default value of the TARGET compiler option.
COMPILERTARGET = <primary target>

Assigns the specified target value as the default value for the TARGET compiler
option.
8600 0395-514 99
COMPILERTARGET = <primary target> (<secondary target>)

Assigns the specified primary target value as the default value and also assigns the
secondary target value.
Examples
Example 1
This example shows the COMPILERTARGET command set to LEVEL5 and the
response that appears:
COMPILERTARGET LEVEL5
BY DEFAULT THE COMPILERS ON THIS MACHINE GENERATE
CODE TAILORED FOR THESE MACHINES:

CS180 CS185
CS300 CS520
CS580 CS585
CS590 CS595
CS7101 CS7201
FS1100 FS1300
FS1400 FS1600
LX100 LX6000
LX7000 NX6920
NX6830 VSE500
CODE COMPATIBLE WITH THESE MACHINES:

CS680
CS690
100 8600 0395-514

Example 2
This example shows the COMPILERTARGET command set to LEVEL6 and the
response that appears:
COMPILERTARGET LEVEL6
BY DEFAULT THE COMPILERS ON THIS MACHINE GENERATE
CODE TAILORED FOR THESE MACHINES:

CS680
CS690
CODE COMPATIBLE WITH THESE MACHINES:
CS180 CS185
CS300 CS520
CS580 CS585
CS590 CS595
CS7101 CS7201
FS1100 FS1300
FS1400 FS1600
LX100 LX6000
LX7000 NX6920
NX6830 VSE500
8600 0395-514 101

COMPILE STATUS (Information for Compiler Task)

The COMPILE STATUS command displays the sequence number and number of errors
detected for a compiler task.
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
SEQ = 98942000, NO ERRORS
Example 2
This example shows the sequence number and reports that three errors were
detected:
3621
SEQ = 606140, ERRORCOUNT = 3
102 8600 0395-514

COPYCAT (Copy Catalog)

The COPYCAT (Copy Catalog) command creates an inactive disk copy of the active
system catalog. Use this command to make a backup copy of the catalog while the
catalog is in use. Do not use library maintenance to create backup copies of the
active catalog directly, because the catalog might have internal records changed
during the copy operation.
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.
COPYCAT <file title> (<family index>)

Directs the copy of the active system catalog or access file to a particular pack.
Example
The following example creates a copy named BACKUP/CATALOG/002 on family
member number 2 of the family named PACK:
COPYCAT BACKUP/CATALOG/002 ON PACK (2)

Use the COPYCAT command to make a safety or backup copy of the active catalog.
After you create the backup copy, use the library maintenance procedure to copy the
backup to tape, and store the tape offline.
8600 0395-514 103

CQ (Clear Queue)
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
104 8600 0395-514

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.
Note: The CS command is to be deimplemented in a future release and will be

replaced by the AI (Automatic Initiation) command.
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-
SUPERVISOR: SUPERVISOR CANCELED
Example 3
CS
SUPERVISOR: NOT SPECIFIED
8600 0395-514 105

Example 4
CS SYSTEM/HARDCOPY
SUPERVISOR: SYSTEM/HARDCOPY
106 8600 0395-514

CU (Core Usage)
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.
8600 0395-514 107

CU (Core Usage)
Examples
Example 1
The following example of a CU display shows all memory used by the process and
main memory usage:
CU
--------SYSTEM MEMORY USAGE----------------------------
---Memory Summary-- ---ASD Information---- ----Buffer Statistics---

Available 5,309,139 Total ASDs 41,942 Size source Number Memory
Non save 2,090,869 In use 25% Buffergoal 0 0
Save 988,600 Maximum in use 26% Buffersize 0 0
Total 8,388,608 Factor 50 Words/ASD Blocksize 5 2,420
Overlaid 158,712
Example 2
The following shows a <mix number> CU command and the resulting display:
9508 CU
9508 Memory: Total Save

Stack 8,592 4,782
Code 23,075 2,949
Total 31,667 7,731
Example 3
The following shows a CU AVAIL command and the resulting display that shows
individual available memory totals:
CU AVAIL
-----------------------------SYSTEM MEMORY USAGE-------------------------
-- Memory Summary -- - ASD Information - --- Buffer Statistics ---

Available 560911202 Total ASDs 16777215 Size source Number Memory
Non save 4370696 In use 1% Buffergoal 0 0
Save 110000918 Maximum in use 1% Buffersize 0 0
Total 675282816 Factor 20 Words/ASD Blocksize 37 59336
Overlaid 0
- Avail Mem Totals -

Non save 560869941
Save 293267005
Total 31679
108 8600 0395-514

DA (Dump Analyzer)
DA (Dump Analyzer)
The DA (Dump Analyzer) command executes the utility SYSTEM/DUMPANALYZER to
analyze a memory dump.
For more information, refer to Memory Dump Processing.
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).
If entered from a REMOTESPO station, the DUMPANALYZER session is initiated at an

ODT. A REMOTESPO station cannot run a DUMPANALYZER session interactively.
DA <unit number>
Specifies a tape drive where a memory dump tape has been mounted.
DA " <file title> "

Specifies a disk file containing a saved or unsaved memory dump.
Example
DA

You can check on the progress of SYSTEM/DUMPANALYZER by entering one of the
following monitoring commands:

8600 0395-514 109

DBS (Database Stack Entries)

The DBS (Database Stack Entries) command provides listings of all active database
stacks.
Syntax
<wild card>
<delim>
Use one of the following characters:
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
Equal sign (=) Matches any sequence of

characters
Tilde (~) Matches any sequence of

characters except a slash (/)

space character.
110 8600 0395-514

DBS NAME =pack=
"pack":
DBS NAME LIT ^=pack=^
Explanation
DBS
Displays all unsuppressed database stacks.
DBS ALL
Displays suppressed and unsuppressed database stacks.
DBS NAME <wild-card string>

Displays all database stacks that match the name specified in the wild-card string,
including any that were suppressed.
DBS USER <usercode>

Display only database stacks with the specified usercode.
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
---Mix-Pri-Usr------- 3 ACTIVE DATABASES --------------------------

8379 80 1 STADB
8329 80 5 STBDB
8335 50 1 STCDB
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).
8600 0395-514 111

DD (Directory Duplicate)
The DD (Directory Duplicate) command creates or deletes a backup copy of the flat
directory of a pack family.
Each pack family can contain a maximum of three directories.
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.
DD ON <family name> (<family index>)

Removes the duplicate directory. This form of the command cannot be used unless
the pack indicated by the specified family index is online.
Example
DD ON MASTERPACK (2)
---Mix-Pri-CPU Time-------- 1 ACTIVE ENTRY ----------------------

* 9303 80 14:17 Job DD MASTERPACK (002)

If you enter a DD command for a halt/load capable member that is not in use, the
member is no longer halt/load capable. You cannot perform a DD command on a
member that is the active base pack.
112 8600 0395-514

DIRECTORY ONLY
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.
DIRECTORY ONLY - ON <family name> (<family index>)

Cancels the DIRECTORY ONLY status of the given disk volume.
Example
The following example shows the DIRECTORY ONLY command:
DIRECTORY ONLY ON DMDATA (1)

When you use the DIRECTORY ONLY command, the system does not move AREAS of
nondirectory files off the specified disk. After the DIRECTORY ONLY command
completes, you can move those AREAS off the unit by
Using the RES (Reserve) command:

RES PK <unit number> SECTOR <number> FOR <number> AS BADDISK
REMOVE <new baddisk file> FROM <the family>
Using library maintenance:
COPY files FROM <the family> (PACK) TO <the family>(PACK);
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.
8600 0395-514 113

DF (Empty Dumpdisk File)

The DF (Empty Dumpdisk File) command empties dumps from dumpdisk files.
DF initiates an independent runner to empty the dumpdisk files.
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.
If a family name is not specified, it is assumed to be the halt/load family. The

specified dumpdisk file might be the currently loaded dumpdisk file or an
HLDUMPDISK file. Refer to DN (Dump Name) for more information about the
dumpdisk files; refer to CM (Change MCP)for more information about the
HLDUMPDISK file.
114 8600 0395-514

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
---Mix-Pri-Elapsed----------- 2 WAITING ENTRIES -----------------------

* 3971 99 10:11 Job DUMPDISKMASTER
ACCEPT: "OK"/"SAVE"/"PURGE"/"SKIP", DUMP BY "SC1 REQUEST " -
01/20/90 @ 15:53
3971AX OK

All forms of the DF command behave identically. If the file is empty, the process
terminates immediately. If any of the settings of AUTORUNNING (option 15 of the OP
(Options) command), MDT AUTOSAVE, or MDT AUTOUNLOAD are enabled, the
system automatically unloads any dumps in the dumpdisk file. Otherwise, the system
waits for a reply to the RSVP message before emptying each dump found in the
dumpdisk file. For more information about the unloading of dump files, refer to the
DN (Dump Name) command; for more information on AUTORUNNING, refer to the
OP (Options) command; for more information on the AUTOUNLOAD and AUTOSAVE
options, refer to the MDT (Memory Dump Type) command.
To force the file to a particular pack, enter the following command:
<mix number> AX OK <familyname>
To force the file to a tape, enter the following command:
<mix number> AX OK *TAPE
8600 0395-514 115

DIR (Directory)
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 <parameter list>

Generates a report for the specified file parameters. The parameter list is explained
in the section on FILEDATA in the System Software Utilities Reference Manual.
DIR <numeric report request>

Generates the numeric report request. The numeric report request is explained in the
section on FILEDATA in the System Software Utilities Reference Manual.
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:
DIR F:DIR= A/B ON HLUNIT;S;CH
Example 2
The following DIR command requests a list of filenames on the family HLUNIT:
DIR F:FAMILY=HLUNIT
116 8600 0395-514

DL (Disk Location)
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.
8600 0395-514 117

DL (Disk Location)
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.
DL BACKUP ON <family name>

Enables a site to direct printer backup files to any desired family. The DL BACKUP
specification is effective only if the SB (Substitute Backup) command setting specifies
DLBACKUP as a substitute backup medium. In this case, printer backup files are
opened on the family specified by the task attribute BACKUPFAMILY. The default
value for the BACKUPFAMILY attribute of a process is the family name specified for
the DL BACKUP command. If the substitute backup setting does not link to DL
BACKUP, the system does not use the BACKUPFAMILY task attribute.
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.)
To change the DL BACKUP family, perform the following procedure:
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);
118 8600 0395-514

DL (Disk Location)
Note: If you have explicitly specified the location of SYSTEM/BACKUPFILELIST or

SYSTEM/PRINTERINFO by means of the appropriate PS DEFAULT commands, do
not include those files in the copy command.
4. When the COPY process successfully completes, issue the PS RESTART

command.
The CANDE command BACKUPPROCESS starts a process called
SYSTEM/PRINT/BACKUP/PROCESSOR, which interacts with PrintS to locate the
backup files of the session. The SYSTEM/BACKUP utility automatically finds files
on DISK, PACK, and the BACKUPFAMILY family of the job.
DL CATALOG ON <family name>

Specifies the family that contains the system catalog or access structure and the
archive directories for each disk family. On systems that run cataloging, the
structure contains catalog information as well as ordinary disk file information. When
you change the catalog family specification, the system does not move the catalog or
access structure to the new family. However, all future halt/loads search for the
catalog or access structure on the new family.
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:
COPYCAT SYSTEM/ACCESS/nnn ON newfamily (nnn)
COPYCAT SYSTEM/CATALOG/nnn ON newfamily (nnn)
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
8600 0395-514 119

DL (Disk Location)
in the form DP/mmddyyyy/hhmmss/<memory dump reason>, and referred to as a

DP file. When the file is unloaded in the analyzed format, the DP prefix is replaced
with SAVEDUMP, and the dump is correspondingly referred to as a SAVEDUMP file.
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.
DL DPFILES ON <family name> assigns <family name> as the DPFILES family.
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.
After taking a memory dump to a dumpdisk file, DUMPDISKMASTER proceeds as

follows:
If the OP AUTORUNNING option is set, DUMPDISKMASTER automatically

empties the dumpdisk file to a file on the DPFILES family. If DPFILES is null,
DUMPDISKMASTER automatically empties the dumpdisk file to the halt/load
family.
If the MDT AUTOSAVE option is set, DUMPDISKMASTER automatically empties
the dumpdisk file to a SAVEDUMP file on the DPFILES family. If DPFILES is
null, DUMPDISKMASTER automatically creates the SAVEDUMP file on the
halt/load family.
If the MDT AUTOUNLOAD option is set and neither of the previous two options
are set, DUMPDISKMASTER will unload the dumpdisk file to a file on the
DPFILES family. If DPFILES is null, the dump is unloaded to a TAPE file.
If the OP AUTORUNNING, MDT AUTOUNSAVE, and MDT AUTOUNLOAD options
are not set, DUMPDISKMASTER sends a message asking if it should empty,
purge, or skip the dump file.
You can empty the dumpdisk file by entering the following command:
<mix number> AX OK
If DPFILES is not null, DUMPDISKMASTER empties the dumpdisk file to the

DPFILES family. If DPFILES is null, DUMPDISKMASTER empties the file to a tape.
To force the file to a particular pack, enter the following command:
<mix number> AX OK <familyname>
To force the file to a tape, enter the following command:

<mix number> AX OK *TAPE
120 8600 0395-514

DL (Disk Location)
For more information about memory dump processing, refer to Memory Dump
Processing and Memory Dump Commands.
DL JOBS ON <family name>

Specifies the family on which the JOBDESC file is located. The JOBDESC file contains
job queue specifications and information about queued and running jobs. When the
DL JOBS command is entered, SETDLJOBS is initiated. If a file named JOBDESC is
not present on the destination family, SETDLJOBS creates a file named
NEWJOBDESC. This new file is renamed to JOBDESC when the system is halt loaded.
When you change the JOBDESC family specification, the system does not move the
JOBDESC file to the new family. However, all future halt/loads search for JOBDESC
on the new family. If the family is not present when you halt/load the system, you
can use either the IL (Ignore Label) command or the OF (Optional File) command.
(Refer to the explanation for the CATALOG option earlier in this subsection.)
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.
DL LIBMAINTDIR ON <family name>

Specifies the disk family that library maintenance uses for library maintenance tape
directory disk files. Users of library maintenance WFL statements ADD, COPY,
ARCHIVE, RESTORE, and RESTOREADD can optionally request that library
maintenance create a tape directory disk file for an output tape or access the tape
directory disk file previously created for an input tape. Library maintenance tape
directory disk files have file names in the following forms:
(usercode)LIBMAINTDIR/<tape name>/<date>/<tape serial>
*LIBMAINTDIR/<tape name>/<date>/<tape serial>
For additional information about these files, refer to the WFL Programming Reference
Manual.
DL LOG ON <family name>

Permits a site to maintain the SYSTEM/SUMLOG file on any desired family.
During system initialization, if the specified family is not present, the DL LOG
specification defaults to the halt/load family name.
8600 0395-514 121

DL (Disk Location)
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:
1. Performs a TL (Transfer Log) action on the SYSTEM/SUMLOG file that resides

on the previous family
2. If a SYSTEM/SUMLOG file already exists on the new family, performs a TL
(Transfer Log) action before opening the new SYSTEM/SUMLOG
If security administrator status is authorized for the system, then a security
administrator usercode is required to execute the LOG form of the DL command.
DL OVERLAY <olay request>

Initiates the visible independent runner CHANGEOLAYFAMILY that makes the
changes you request.
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.
This command can take one of the following forms:
DL OVERLAY <family list>

Specifies on which disk family or families the system is to store memory overlay
data. This form of the command completely replaces an existing family list with a
new family list. If you respecify an existing family, that family retains its former
overlay data. If you do not respecify an existing family, the system acts as
though you have used the DL OVERLAY command on the family. That is, the
system subtracts the family from the list of overlay families. If you specify a new
family, that family becomes a new candidate for the system to use as an overlay
family.
The DL command must acquire enough room on the new overlay family or
families before the system can start moving overlay data from the old families to
the new families. If not enough sectors are available on the new overlay family,
122 8600 0395-514

DL (Disk Location)
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.
8600 0395-514 123

DL (Disk Location)
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 PDUMPFILES ON <family name>

Assigns <family name> as the PDUMPFILES family.
DL ROOT .
DL ROOT ON <family name>
Establishes a family as the POSIX ROOT family. This family becomes the family that
the system uses to establish a file system environment that conforms to POSIX
requirements. The system creates a file named *dev/null on the specified family
when the ENABLEPOSIX system option is set. This family also becomes the default
family for directories and files that do not include a <family name> in the absolute
pathname when POSIX file name resolution rules are in effect. The operating system
checks for the presence of the specified DL ROOT family during system initialization
and whenever you enter a new DL ROOT ON <family name> command.
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
DL ROOT ON <family name>

Assigns <family name> as the ROOT family.
During system initialization, the following RSVP messages might be displayed:
DL ROOT REQUIRES FAMILY : <family name>

Cause: The system is initializing, and the specified family is not present.
Possible Responses:
Enter the DS (Discontinue) command to discard the request and set ROOT to
null.
Enter the OK (Reactivate) command after you make the family base unit
available.
DUP FILE: *dev/null ON <family name>
Cause: The system is initializing, and the following conditions are true:
The ENABLEPOSIX system option is set.
The specified family is present.
124 8600 0395-514

DL (Disk Location)
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:
DL ROOT REQUIRES FAMILY : <family name>
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.
DUP FILE: *dev/null ON <family name>

Cause:
The ENABLEPOSIX system option is set.
The specified family is present
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 retain the
previous DL ROOT specification.
Enter the OK (Reactivate) command after you dispose of the file in some
other way.
The DL ROOT setting is not changed until all RSVP messages are satisfied.
Note: Changing the DL ROOT setting to a different family or to null when POSIX
applications currently have open files on the existing DL ROOT family might cause
unexpected results because subsequent file opens will occur relative to the new
family.
DL SORT ON <family name>

Designates the default family for SORT work files and SORT statistics files. The
default family can be overridden by family substitution or file equation when a
program calls the SORT procedure.
8600 0395-514 125

DL (Disk Location)
DL USERDATA ON <family name>

Enables a site to maintain the SYSTEM/USERDATAFILE on any desired family. The
USERDATAFILE contains information about the usercodes that are allowed on the
system.
This form of the command changes the family whether or not a

SYSTEM/USERDATAFILE is present on the old USERDATA family. If a
SYSTEM/USERDATAFILE is present on the old USERDATA family, the system copies
the current SYSTEM/USERDATAFILE to the new USERDATA family. The
SYSTEM/USERDATAFILE on the old family is renamed USERDATAFILE/<date-time>.
If the copy operation fails, the system terminates the DL USERDATA change. Do not
remove the file on the old family until you are sure that the system has successfully
copied it to the new family as a result of the DL USERDATAFILE command.
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.
If a SYSTEM/USERDATAFILE already exists on the new family, an RSVP wait gives

you the following options:
Enter the DS (Discontinue) command to terminate the DL USERDATA

specification.
Enter the RM (Remove) command to remove the file.
Dispose of the file by changing its name on the new family or by removing it.
Then enter the OK (Reactivate) command.
Note: Because the system has not yet copied the old SYSTEM/USERDATAFILE, do
not remove it from the old family before you reply to the RSVP message.
If no SYSTEM/USERDATAFILE exists on the USERDATA family, or if that family is not

present, and a noninteractive request is made for USERDATA information, the MCP
action is as follows:
If no family is present, the system displays a REQUIRES PK message with OK,

DS, or OF options. OK causes repeated demand for the family. OF causes the
code to proceed without the family.
If the family is present but has no SYSTEM/USERDATAFILE, or if the
REQUIRES PK message is answered by the OF option, the system displays a
NO FILE message. If the IL option is used, the DL USERDATA family is set to
the family name of the resulting unit.
usercode is required to execute this form of the DL command.
126 8600 0395-514

DL (Disk Location)
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
DISK LOCATION FOR OVERLAY WILL BE CHANGED
---Mix-Pri-CPU Time --------------1 ACTIVE ENTRY --------------------

7240 80 :05 CHANGEOLAYFAMILY
MSG
--Mix--Time--------------------- MESSAGES ------------------------

------
7240 10:12 DL OVERLAY ROWSIZE = 504, DISK FAMILIES: PACK, DISK,
USERS
Example 3
DL OVERLAY 504 ON DISK
OVERLAY WILL BE CHANGED
---Mix-Pri-CPU Time --------------1 ACTIVE ENTRY -----------------------

7440 80 :05 CHANGEOLAYFAMILY
MSG
--Mix--Time-------------------- MESSAGES ------------------------------

7440 10:12 DL OVERLAY ROWSIZE = 504, DISK FAMILIES: DISK
7440 10:12 OVERLAY CHANGE IS COMPLETED.
8600 0395-514 127

DL (Disk Location)

Adding a Missing Family
You can enter DL commands during the delay caused by the OP + 24
(OKTIMEANDDATE) command. This ability can be useful if you know that a family
specified in one or more DL categories is in one of the following states when the
system is halt/loaded:
The family is offline.

The files on the unit are defective.
The unit is saved.
The unit is defective.
Actions You Can Take When DL Families Are Missing
The system issues an RSVP message or a message during the halt/load process if
any or all of the following families are missing at halt/load time:
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).
128 8600 0395-514

DL (Disk Location)
The following table lists actions to be taken when DL families are missing.
DL Family System Action Suggested Operator Action
BACKUP RSVP messages by Either locate and ready the requested

PRINT_ SUBSYSTEM_ family, or select a new family with the
INITIALIZATION and following steps:
SYSTEM/ PRINT/ 1. Shut down the Print System with
FONTSUPPORT the PS QUIT command.
2. Reply DS to the RSVP messages.
3. Specify a new family with the DL
BACKUP command.
4. Copy the following files to the new
family:
SYSTEM/PRINTERINFO,
SYSTEM/BACKUPFILELIST,
SYSTEM/PRINT/FONTSUPPORT/=
SYSTEM/PRINTSYSTEMCONFIG
5. Restart the Print System with the PS

RESTART command.
CATALOG RSVP message, To restore the original assignment:

IL or ??PHL 1. Locate the requested family.
2. Ready the family with the RY
command.
3. Halt/load the system.
To select a new family, issue the IL
command to the new family.
DPFILES RSVP message by To restore the original assignment,

DUMPDISKMASTER locate and ready the requested family.
To select a new family:
1. Issue the DL DPFILES command to
the new family.
2. Reply OU to the RSVP message.
JOBS RSVP message by To restore the original assignment,

STARTSYSTEM locate and ready the requested family.
To select a new family, issue an IL
command to the new JOBS family.
8600 0395-514 129

DL (Disk Location)
LIBMAINTDIR Defaults to the To restore the original assignment,

halt/load family locate and ready the missing family.
1. Select the new family.
2. Issue the DL LIBMAINTDIR
command to the new family.
LOG Defaults to the To restore the original assignment:

halt/load family 1. Locate and ready the proper family.
2. Issue the DL LOG command to the
family.
1. Select the new family.
2. Issue the DL LOG command to the
new family.
OVERLAY RSVP message by To restore the original assignment,

CHANGE- locate and ready the missing family or
OLAYFAMILY families.
1. Reply OF to the RSVP message,
select the new family or families.
2. Issue the DL OVERLAY command to
the new families.
PDUMPFILES Defaults to the To restore the original assignment,

standard method. locate and ready the requested family.
To select a new family, issue the DL
PDUMPFILES command to the new
family.
ROOT RSVP message by To restore the original assignment:

SETDLROOT 1. Locate and ready the requested
family.
2. Reply OK to the RSVP message.
1. Reply DS to the RSVP message.
2. Select the new family and issue the
DL ROOT command to the new
family.
130 8600 0395-514

DN (Dump Name)
SORT RSVP message when To restore the original assignment,

SORT runs locate and ready the requested family.
1. Issue the DL SORT command to the
new family.
2. Reply OU to the RSVP message.
USERDATA RSVP message by To restore the original assignment,

STARTSYSTEM locate and ready the requested family.
To select a new family, perform one of
the following actions:
If you have an existing
USERDATAFILE, select the new
family on which the file resides by
reissuing a DL USERDATA <family>
command.
If you do not have an existing
USERDATAFILE, you must re-create
it either by restoring the file from
tape or by creating a new one with
the SYSTEM/MAKEUSER utility.
Then select the family on which the
file resides by issuing a DL
USERDATA <family> command.
8600 0395-514 131

DN (Dump Name)
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.
An independent runner named DUMPDISKMASTER handles all dumpdisk file

processing.
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 file specification, converted to a standard-form name (including the

family), cannot be longer than 36 characters.
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:
Use the DN command to create a dumpdisk file.
Use the CM (Change MCP) command to create an HLDUMPDISK file.
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.
For more information, refer to Memory Dump Processing.
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.
132 8600 0395-514

DN (Dump Name)
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:
<mix number> DN FILE SPECIFICATION NULLED - INPUT REQUEST
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.
DN <file name> [ <kilosectors> ]

DN <file name> ON <family name> [ <kilosectors> ]
Function exactly as the information provided in the DN <file name> ON <family
name> explanation, with the exception that the [<kilosectors>] number is taken as
the initial response to the ACCEPT request.
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
3870 DUMPER ON DISK HAS BEEN LOADED
8600 0395-514 133

DN (Dump Name)
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
DN-ED FILE: NOT SPECIFIED

K SECTORS: TOTAL/FREE
HLDUMPDISK 100/100
DEFAULT DISKDUMP DISPOSAL (DL DPFILES)CREATE MEMORY/DUMP TAPES
Example 3
This example shows a request for the name of the dumpdisk file. The response
shows that DL DPFILES = PACK.
DN
DN-ED FILE: MY/DUMPDISK ON ABC

K SECTORS: TOTAL/FREE
HLDUMPDISK 100/100
DN-ED FILE 150/96
DEFAULT DISKDUMP DISPOSAL (DL DPFILES)CREATE DP FILES ON PACK

After a dumpdisk file is activated, the memory dump procedure automatically stores
dumps there. At any time during a dump, you can redirect the dump to tape by
entering the memory dump TAPE command; refer to Memory Dump Commands. If
the dumpdisk file reaches its capacity, the memory dump procedure redirects the file
to tape. During a dump to disk, you can use the PROG dump command or enter
<SPCFY> to display the number of free and in-use kilosectors.
After a dump to disk procedure completes, DUMPDISKMASTER immediately attempts

to unload the dump from the dumpdisk file in order to make space available in the
file for any subsequent dumps. If one of the automatic options is set,
DUMPDISKMASTER continues with actions based upon the setting of the DL DPFILES
option. The options and actions based upon the DPFILES specifications are listed in
the following table.
Option DL DPFILES Specified DL DPFILES Null
MDT AUTOSAVE SAVEDUMP on DPFILES SAVEDUMP on H/L Family

set
OP + Raw Dump on DPFILES Raw Dump on H/L Family

AUTORUNNING
MDT Raw Dump on DPFILES MEMORY/DUMP tape created

AUTOUNLOAD
set
134 8600 0395-514

DN (Dump Name)
In the absence of any of these automatic options, DUMPDISKMASTER requests

operator input regarding the disposition of the dump. A waiting entry identifies the
dump and requests a response. The following table explains the action for each valid
operator response.
Response Action
SAVE Creates SAVEDUMP file on the DL DPFILES or halt/load

family.
SAVE Creates SAVEDUMP file on the named family.

<familyname>
OK Empties the dump to the DL DPFILES family.
OK <familyname> Empties the dump to the named family.
OK *TAPE Empties the dump to tape.
SKIP Retains the dump and presents any other dumps that are
waiting for disposition.
PURGE Removes the dump from the file.
DS Makes no further requests 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.
At the completion of copying a dump to the DL DPFILES disk family or to tape,

DUMPDISKMASTER again presents any unprocessed dumps for disposition.
8600 0395-514 135

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.
136 8600 0395-514

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.
8600 0395-514 137

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: This operation is intended for internal use by Unisys.
138 8600 0395-514

DOWN (Down Resource)

The DOWN command detaches resources from the executing partition.
Many forms of the DOWN command cause a brief system pause.
Note: DOWN is a synonym for FREE. Use DOWN on IOP systems. Use FREE on
IOM systems.
Syntax
<CTL specification>
<resource> (Libra Model 185, 580, 585, 590, 595 systems)
<resource> (Libra Model 680, 690 systems)
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.
8600 0395-514 139

<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.

2. Enter the command DOWN CTL <CTL specification>.
3. Enter the command UP CTL <CTL specification>.
DOWN <unit specification>
Detaches the devices from their former group and makes them available to any
group. Unit numbers on IOP systems can be any integer from 1 to 65535.
DOWN IP-<pod>-<subpod>-<IP unit>

Detaches the specified IP (instruction processor) 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.
140 8600 0395-514

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:
DOWN not allowed, IOP <IOP Number> is active.
You can save in-use IOPs by using the SV (Save) command.
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.
Special Considerations for Libra 600 Series Systems

Detaching the last Up Bus of an IONODE automatically detaches the IONODE.
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 REJECTED BECAUSE DISABLED BUSES SPECIFIED. TO RECOVER, HALT/LOAD OR DOWN

IONODE_<cell>
The indication that a bus is disabled shows up in an SC- display
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:
DOWN not allowed, IOP <IOP number> is active.
A DOWN PCI-BRIDGE-x-y command is rejected if the specified PCI-BRIDGE is

currently marked as MASTER. The master PCI bridge is chosen at the time of a
START partition or RUN LOADER command. It is selected based on whichever bridge
has the lowest number (for example, pci-bridge-0-0 is lower than pci-bridge-0-1).
This is a hardware limitation; dynamic reconfiguration is restricted from performing a
DOWN operation on the PCI bridge. To perform a DOWN operation on the bridge, you
must enter an ST (Stop) system command so that the bridge can be brought down
by Server Sentinel.
In-use IOPs can be saved using the SV (Save) command.
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
8600 0395-514 141

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:
DOWN not allowed, IOP <IOP number> is active.
In-use IOPs can be saved using the SV (Save) command.
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.
DOWN CTL 4001
TL 4001 WILL BE FREED
142 8600 0395-514

Example 2
This example frees a tape unit.
DOWN MT 12
MT 12 WILL BE FREED
Example 3
This example detaches multiple PCI buses.
DOWN PCI-BUS-3-1-2 PCI-BUS-2-0-1
PCI-BUS-3-1-2 WILL BE DOWN

Example 4
This example detaches a PCI bridge and all associated PCI buses. Each of the
following has the same result.
DOWN PCI-BRIDGE 2-0

DOWN PCI-BRIDGE-2-0 PCI-BUS-2-0-1
DOWN PCI-BRIDGE-2-0 PCI-BUS-2-0-1 PCI-BUS-2-0-2 PCI-BUS-2-0-3
PCI-BRIDGE-2-0 WILL BE DOWN

Example 5
This example detaches multiple PCI buses.
DOWN PCI_BUS_3_1 PCI_BUS_2_1
PCI-BUS_3_1 WILL BE DOWN

PCI-BUS_2_1 WILL BE DOWN
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
IONODE_2 WILL BE DOWN

PCI_BUS_2_3 WILL BE DOWN
8600 0395-514 143

DQ (Default Queue)
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
THE DEFAULT QUEUE IS 999
Example 2
This example shows a query about the default queue number and the system
response.
DQ
THE DEFAULT QUEUE IS 999
144 8600 0395-514

DQ (Default Queue)
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
THE DEFAULT QUEUE HAS BEEN CHANGED FROM 999 TO 77
Example 4
This example cancels the default job queue specification that currently is queue 8.
DQ -
DEFAULT QUEUE CANCELED (8)
8600 0395-514 145

DR (Date Reset)
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.
This command will be deimplemented in a future release. For information on

changing the time and date simultaneously, refer to the TR (Time Reset) 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>.
146 8600 0395-514

DR (Date Reset)
Example
This example shows a command, entered on Wednesday, July14, 2004, that sets the
system date back 30 days:
DR WEDNESDAY 14 JULY 2004
DATE CHANGE REQUEST--OK OR DS MAY BE REQUIRED--SEE WAITING ENTRIES
The operator enters a W (Waiting Mix Entries) command to display the entries:
---Mix-Pri-Elapsed------------ 1 WAITING ENTRY ----------------------

1234 80 :01 JOB CHANGEDATE
CLOCK BEING SET BACKWARDS--CAN CAUSE LOG/AUDIT PROBLEMS--OK OR DS
The operator confirms that a backward change is required:
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:

1234 80 :04 JOB CHANGEDATE
VERIFY 30 DAYS BACKWARD
After confirming the change, use the TD (Time and Date) command to display the
system time and date:
1234 OK
TD
The date is Wednesday, July 14, 20044 (2004195)
The time is 17:32:05 Pacific Daylight Time (PDT)

Changing the Date Forward
The system immediately makes a forward date change of one to three days.
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.
8600 0395-514 147

DR (Date Reset)
Changing the Date Backward

Every request to set the date backward results in a waiting entry with the following
message:
CLOCK BEING SET BACKWARDS--CAN CAUSE LOG/AUDIT PROBLEMS--OK OR DS.
You must either cancel the request by entering a DS (Discontinue) command or

confirm it by entering an OK (Reactivate) command.
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,
VERIFY 7 DAYS BACKWARD
You must enter either an OK (Reactivate) command or a DS (Discontinue) command.
148 8600 0395-514

DRC (Disk Resource Control)

The DRC (Disk Resource Control) command provides information on the current state
of the disk resource control system.
Syntax
<old family name>
<new family name>
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.
8600 0395-514 149

DRC LB <old family name> <new family name>

Informs the DRC system that a family was relabeled when it was not visible to the
DRC system. The command causes a new FAMILYLIST entry to be created in the
USERDATAFILE for the new family name with the same FAMILYINUSE value as the
old family name. The FAMILYINUSE value for the old family name is set to zero. The
system performs this operation on all usercodes known to the DRC system to have
files on the old family name. You must enter the DRC LB command before the family
named by the new family name is brought online on the system that is running the
DRC system.
DRC PG <old family name>

Informs the DRC system that a family was purged or destroyed when it was not
visible to the DRC system. The command causes the FAMILYINUSE value to be set to
zero for all usercodes known to the DRC system to have files on the old family name.
Examples
Example 1
This example displays the current state of the disk resource control system:
DRC
THE DRC SYSTEM IS INACTIVE
Example 2
This example directs the MCP to start the disk resource control system after the next
halt/load:
DRC +
THE DRC SYSTEM WILL BE STARTED AFTER THE NEXT HALT/LOAD
Example 3
This example directs the MCP to terminate the disk resource control system after the
next halt/load:
DRC -
THE DRC SYSTEM IS TERMINATING
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:
DRC LB OLDNAME = ABC NAME = XYZ
<mix number> DRC LB OLDNAME = ABC NAME = XYZ OK TO CONTINUE
<mix number> OK
150 8600 0395-514

<mix number> DRC LB OLDNAME = ABC NAME=XYZ DONE
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?
DRC PG OLDNAME = ABC
<mix number> DRC PG OLDNAME = ABC OK TO CONTINUE
<mix number> OK
<mix number> DRC PG OLDNAME = ABC DONE

A family is not visible to the DRC system under the following circumstances:
1. The DRC system is inactivethat is, you entered DRC .

2. The family is using a local system access directory. Refer to the
FAMILYACCESS (Directory Location) command.
3. The family is on another system.
4. CSP Userdata services are established on the system.
When a family is visible to the DRC system, changes to disk space usage that occur
as the result of the system commands LB (Relabel Pack or Host Control Unit), PG
(Purge), and RC (Reconfigure Disk) are automatically propagated to the
USERDATAFILE entries of usercodes that have files on the affected families.
Consequently, the system does not execute DRC LB and DRC PG requests if the
families named by either the old family name or the new family name are online at
the time that you enter the request.
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:
DRC LB OLDNAME = <family name> NAME = <family name> OK TO CONTINUE
DRC PG OLDNAME = <family name> OK TO CONTINUE
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.
8600 0395-514 151

DS (Discontinue)
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
* (asterisk) Combines options already set by the task with options

specified in the command; the net result controls the
program dump.
ALL Causes a program dump with all options set.
NONE Resets all program dump options. If no other options

are specified in this command, no program dump is
performed.
152 8600 0395-514

DS (Discontinue)
Option Description
DSED Forces a program dump with options already set by the

task (if used with *) or with the default options (if used
without *) plus any other options set in this command.
BASE Dumps the base of the stack (used by the operating

system) and the process information block.
ARRAYS Dumps the arrays.
PRESENTARRAYS Dumps only present arrays. If the ARRAYS option and

the PRESENTARRAYS option are both specified, then all
arrays are dumped.
CODE Dumps all code segments.
CRITICALBLOCK Causes any program dumps to include the stack that

contains the critical block of the dumping stack. If the
stack is a job stack, it is not dumped. The stack is
dumped from the top of the environment that contains
the critical block or from the base of the frozen
environment of a library or database stack, whichever
is higher.
FILES Dumps all areas used by files.
DBS Dumps database stacks.
LIBRARIES Dumps library stacks.
PRIVATELIBRARIES Dumps only private library stacks. If LIBRARIES is also

set, the system dumps all libraries.
TODISK Causes any program dumps taken by the process to be

directed to a disk file. If TOPRINTER is also set, the
system directs the dump both to the printer and to
disk.
TOPRINTER Causes any program dumps taken by the process to be

directed to the task file. The INTNAME of this file is
TASKFILE, and the default KIND is PRINTER. If TODISK
is also set, the system directs the dump both to disk
and to the printer.
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.
8600 0395-514 153

DS (Discontinue)
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
3132 OPERATOR DSED @ 002:001D:1
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 NOT LOCKED
4532 DS
4532 OPERATOR DSED @ (01200300)

In rare cases, a discontinued task might not terminate. To resolve this situation,
halt/load the system.
A PROGRAMDUMP (caused by the DS command) might take a significant amount of

time to complete depending on the relevant dump options, how large the program is,
or other factors.
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
154 8600 0395-514

DS (Discontinue)
command was applied. These procedures might take time to complete, or they might
have a problem, preventing completion.
Note: In this case, a second DS command can cause the task to

terminate. Prematurely entering the second DS command could cause other tasks to
malfunction.
If a discontinued task does not terminate and the CONTROLLER is functioning

normally, subjecting the task to ??DS (the primitive form of the DS command) is no
more likely to result in task termination than a nonprimitive DS command.
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:
WAITING FOR n TASKS TO TERMINATE: <mix number list> RSVP.
8600 0395-514 155

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.
DU ON <family name> (<family index>)

Displays information only for that unit specified by the family index.
DU ON <family name> <size>

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 less than the specified size, the number of
available sectors in areas at least as large as the specified size, and the number of
disk areas in the specified size that can be allocated. The size is specified in sectors.
DU SYSTEMDIRECTORY ON <family name>

Displays the current capacity of the SYSTEMDIRECTORY for the family, the total
number of available sectors in the SYSTEMDIRECTORY for the family, the total
number of sectors in use in the SYSTEMDIRECTORY for the family, the largest
available area, the number of available sectors in areas of fewer than 3 sectors, the
number of available sectors in areas of 3 or more sectors, and the number of disk file
headers of 3 sectors long that can be allocated.
156 8600 0395-514

DU SYSTEMDIRECTORY ON <family name> <size>

Displays the current capacity of the SYSTEMDIRECTORY for the family, the total
number of available sectors in the SYSTEMDIRECTORY for the family, the total
number of sectors in use in the SYSTEMDIRECTORY for the family, the largest
available area, the number of available sectors in areas less than the specified size,
the number of available sectors in areas at least as large as the specified number,
and the number of disk file headers of the specified size that can be allocated. The
size is specified in sectors.
Examples
Example 1
DU ON DISK
Disk Utilization Report for DISK (Entire Family)
-- Sectors -- ---- Bytes ----- Percent

Available: 293,088 52,755,840 19 %
In Use : 1,262,412 227,234,160 81 %
Capacity : 1,555,500 279,990,000 100 %
Available Space Analysis
Areasize -- Sectors -- ---- Bytes ----- Percent

Largest: 28,536 5,136,480 2 %
< 504: 41,274 7,429,320 3 % (120 Areas)
> 503: 251,814 45,326,520 16 % (29 Areas)
490 areas of 504 sectors could be allocated.
Example 2
DU ON MCPMAST 1046
Disk Utilization Report for MCPMAST (Entire Family)
-- Sectors -- ---- Bytes ------ Percent

Available: 121,746 21,914,280 4 %
In Use : 2,891,054 520,398,720 96 %
Capacity : 3,012,800 542,304,000 100 %
Areasize -- Sectors -- ---- Bytes ------- Percent

Largest : 51,100 9,199,000 2 %
< 1,046: 52,962 9,533,160 2 % (3,203 Areas)
> 1,045: 68,784 12,381,120 2 % (5 Areas)
63 areas of 1046 sectors could be allocated.
8600 0395-514 157

Example 3
DU ON TEST_MEDIA_A (CD)
Disk Utilization Report for TEST_MEDIA_A (CD)
- Sectors - -- Bytes ----- Percent

Available: 201,010 205,834,240 20 %
In Use : 798,554 817,719,296 80 %
Capacity : 1,000,000 1,024,000,000 100 %
Example 4
Following is an example of the output for a large family:
DU ON BIGFAMILY
Disk Utilization Report for BIGFAMILY (Entire Family)
WARNING -- Sector and Byte Counts in K (1,000)
- K Sectors -- ----K Bytes ----- Percent

Available: 3,557,402 640,332,389 100 %
In Use : 6 1,123 0 %
Capacity : 3,557,408 640,333,512 100 %
Areasize -K Sectors -- ----K Bytes ----- Percent

Largest : 19,763 3,557,403 1 %
< 504: 0 0 0 % (0 Areas)
> 503: 3,557,402 640,332,389 100 % (180 Areas)
7058337 areas of 504 sectors could be allocated
158 8600 0395-514

Example 5
DU SYSTEMDIRECTORY ON MCPMAST
SYSTEMDIRECTORY Usage Report for MCPMAST
-- Sectors -- Percent
Available: 3,170 32 %
In Use : 6,830 68 %
Capacity : 10,000 100 %
Available SYSTEMDIRECTORY Space Analysis
Headersize -- Sectors -- Percent

Largest : 1,426 14 %
< 3: 122 1 %
> 2: 3,048 30 %
1004 headers of 3 sectors could be allocated
Maximum capacity 2,000,000 sectors
8600 0395-514 159

DUMP (Dump Memory)
DUMP (Dump Memory)

The DUMP (Dump Memory) command does the following tasks:
Performs a memory dump

Invokes the program dump procedure for specified programs
Sets up future program dump options
You can also perform a memory dump or a program dump with specified options.
Syntax
<memorydump option>
<programdump option list>
160 8600 0395-514

DUMP (Dump Memory)
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.
DUMP : <memorydump options>

Specifies an option for a memory dump. The following table describes the valid
values.
Memory Dump Description

Option
PARTIAL Captures a subset of the in-use areas of memory. A partial

dump includes the following areas:
The requested stack and all the areas owned by the
stack.
The area occupied by all the stacks in a running
system.
All the areas owned by the MCP.
Any stack and its associated areas that are linked into
the GRAPHHEADWORD, PROCESSFAMILYLINK, or both
of the requested stack.
ASD tables.
For systems that include task control processors
(TCPs), some relevant TCP state information such as
events and statistical data for each stack being
dumped.
If you do not supply a mix number with this option , the
MCP performs a dump of the CONTROLLER stack.
8600 0395-514 161

DUMP (Dump Memory)
Memory Dump Description

Option
MINIMAL Captures a subset of the information contained in the

dump. A minimal dump includes the following:
The ASD table.
The area occupied by all the stacks in a running
systemthe area from the bottom-of-the-stack
register (BOSR) to the limit-of-stack register (LOSR)
of each stack.
The structures owned by the MCP required for the
DUMPANALYSER SUMMARY and STACK commands,
including all PIBS, TABW, and JOBDATA information.
The LISTARRAY containing GRAPH information.
For DIAGNOSTIC MCPs, the TRACE BUFFER,
TBIT_RCWS, and ASD_LOCK_WORD arrays.
For systems that include task control processors
(TCPs), the event and process information maintained
by the TCP.
When a mix number is supplied, the off stack
information of the process family of the mix number is
also included in the dump.
ALLINUSE Captures only the in-use areas (those present in memory).
COMPLETE Captures the entire memory image.
<mix number list> DUMP

Invokes the program dump procedure for the programs in the mix number list.
<mix number list> DUMP <programdump option list>

Specifies options to control a program dump. These options are as follows.
Option Description
* (asterisk) Combines options already set by the task with options

specified in the command; the net result controls the
program dump.
ALL Sets all future dump options, including DSED and FAULT.
No program dump is taken at this time (when the command
is entered).
ARRAYS Dumps the arrays.
BASE Dumps the base of the stack (used by the operating

system) and the process information block.
162 8600 0395-514

DUMP (Dump Memory)
Option Description
CODE Dumps all code segments.
CRITICALBLOCK Causes any program dumps to include the stack that

contains the critical block of the dumping stack. If the stack
is a job stack, it is not dumped. The stack is dumped from
the top of the environment that contains the critical block
or from the base of the frozen environment of a library or
database stack, whichever is higher.
DBS Dumps database stacks.
DSED Requests a future program dump if the program is

discontinued (with a DS command) for any reason other
than a fault. No program dump is taken at this time (when
the command is entered).
FAULT Requests a future program dump if a fault (such as a

segmented array or a divide-by-zero operation) occurs in
the program. No program dump is taken at this time (when
the command is entered)
FILES Dumps all areas used by files.
LIBRARIES Dumps library stacks.
NONE Resets all future program dump options. If no other options

are specified in this command, a dump is taken with the
default options.
PRESENTARRAYS Dumps only present arrays. If the ARRAYS option and the
PRESENTARRAYS option are both specified, then all arrays
are dumped.
PRIVATELIBRARIES Dumps only private library stacks. If LIBRARIES is also set,

the system dumps all libraries.
TODISK Causes any program dumps taken by the process to be

directed to a disk file. If TOPRINTER is also set, the system
directs the dump both to the printer and to disk.
TOPRINTER Causes any program dumps taken by the process to be

directed to the task file. The INTNAME of this file is
TASKFILE, and the default KIND is PRINTER. If TODISK is
also set, the system directs the dump both to disk and to
the printer.
For details about the effects of the TODISK and TOPRINTER options, refer to the
Task Attributes Programming Reference Manual.
8600 0395-514 163

DUMP (Dump Memory)
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:
3132 DUMP ALL
Example 2
This example requests a partial memory dump for the program with the specified
mix number:
DUMP : PARTIAL 5402
Example 3
These two examples request minimal memory dumps by using the DUMP command
with the MINIMAL <memorydump option>:
DUMP LOW_MEMORY:MINIMAL
DUMP TASK_LOOPING:MINIMAL 1024

When the system is performing a memory dump, the MCP clock stops. As a result,
the processor and I/O times for various actions are not distorted by the time used to
take the dump.
164 8600 0395-514

EXPAND (Expand Directory)

The EXPAND (Expand Directory) command pre-expands a directory before it fills up.
Using the EXPAND command helps avoid delays that sometimes occur when a
directory is full and there is not enough disk space available for the system to
expand the full directory.
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:
EXPAND SYSTEMDIRECTORY/001 ON PACK AREAS = 400

If the system is waiting on an RSVP message for directory space, then an EXPAND
command for that directory or any of its duplicates waits until you resolve the
directory space required by the RSVP message before proceeding, such as the
following:
PK4101 2000 (FAMILYINDEX 1) SECTORS REQUIRED ON PACK: *SYSTEMDIRECTORY/001
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
8600 0395-514 165

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.
Changing the Size of the SYSTEMDIRECTORY for a Disk Family

The following three system commands enable you to change the size of the
SYSTEMDIRECTORY for a disk family.
EXPAND SYSTEMDIRECTORY/<number> ON <family name> AREAS

<number>
The primary purpose of this command is to preexpand the SYSTEMDIRECTORYs
for a given family.
Preexpanding the SYSTEMDIRECTORYs for a family helps to ensure that the
system is not delayed waiting for disk space on the base pack to expand the
SYSTEMDIRECTORY while you are adding files to the family.
NEW SYSTEMDIRECTORY ON <family name>
The primary purpose of this command is to change the AREASECTORS value of
the SYSTEMDIRECTORY on the indicated family.
You can change AREASECTORS from the old 600 sector value to 2000 sectors,
roughly tripling the total capacity of the directory. For single pack disk families,
you can change the value from 2000 sectors to 4000 sectors, roughly doubling
the total capacity of the directory.
SQUASH SYSTEMDIRECTORY ON <family name>
The primary purpose of this command is to reduce the size of the
SYSTEMDIRECTORY for the family and return unused AREAS to the available disk
space pool for use by normal files.
Use this command for disk families that at one time contained a large number of
files but no longer contain or need to contain so many files.
Note that this function is completely different from the function of the "SQUASH
<family name>" system command, which attempts to reduce the
checkerboarding of the available disk space pool.
Performance
The SQUASH SYSTEMDIRECTORY and NEW SYSTEMDIRECTORY commands both use
the same algorithm as follows:
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.
166 8600 0395-514

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.
Postpone using the SQUASH SYSTEMDIRECTORY and NEW SYSTEMDIRECTORY

commands until a time when critical programs are not running. Before using either of
these commands, consider using the ADM ST system command on any ODT that is
running the automatic display of system status with a the display of disk packs (PER
PK). Whenever a SQUASH SYSTEMDIRECTORY or NEW SYSTEMDIRECTORY process
is running, avoid issuing any commands that reference disks, such as PER PK
(Peripheral Status), PD (Print Directory), MP (Mark Program), and so forth.
The EXPAND SYSTEMDIRECTORY command uses a much simpler algorithm as

follows:
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.
8600 0395-514 167

FA (File Attribute)
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.
---Mix-Pri-Elapsed----------- 1 WAITING ENTRY ----------------------

* 7988 50 10:11 (ROBY)TEXTX ON PACK
NO FILE ABC (MT) #1
PER MT
114*P[000123] #1 13:12 ABCD
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.
168 8600 0395-514

FA (File Attribute)
---Job-Task Pri---Elapsed----------- 1 WAITING ENTRY ---------------

3944/3945 50 :36 (USERX)LIBRARY/TEST
NO LIBRARY MISSING/LIBRARY ON DMSIITEST
3945 FA LIBACCESS=BYFUNCTION, FUNCTIONNAME=SDASUPPORT

Tape Reel Switches
The FA response at tape-reel-switch time is limited to only the SERIALNO attribute.
Any attempt to set another attribute at tape-reel-switch time produces the following
message:
<mix no.> FA ERROR: ONLY SERIALNO MAY BE FA-ED DURING REELSWITCH
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):
<mix no.> <file name> REQUIRES MT # <file section>
<mix no.> NO FILE <file name> (MT) # <file section>
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:
<mix no.> FA SERIALNO = <serial number>
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:
<mix no.> FA SERIALNO = (<serial number>, <serial number>, . . .

<serial number>)
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.
Example RSVP Message

The system displays the following RSVP message when the second reel of an output
tape is required:
2230 T/FILE029 REQUIRES MT #2
8600 0395-514 169

FA (File Attribute)
Respond with the following command:
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.
Library Maintenance Restrictions

Using the FA command for any attribute other than SERIALNO or SCRATCHPOOL for
library maintenance produces this message:
<mix no.> FA ERROR: ONLY SERIALNO AND SCRATCHPOOL MAY BE

FA-ED FOR LIBRARY MAINTENANCE
170 8600 0395-514

FAMILYACCESS (Directory Location)

By default, the DL CATALOG family includes a SYSTEM/ACCESS or a
SYSTEM/CATALOG file, which is a central directory of all the files for all the disk
families on the system. You can use the FAMILYACCESS command to move the
directory information for any particular family to a local system access directory
stored on the family itself.
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.
To process the command, the system starts an independent runner named

COPYDIR. The name of this COPYDIR process then changes to FAMILYACCESS
LOCAL <family name>. The process checks the status of the specified disk family.
The system rejects the FAMILYACCESS request if any of the following are true:
The family is not online and write-enabled.

The family is listed in the volume library (cataloging sites only).
The family is already using a local system access directory.
If there are no errors, the process performs the following steps:
1. Creates a local system access directory named SYSTEM/ACCESS/<family

name>/<family index> on the base pack for the family
2. Performs a rebuild for the family, which fills the local
SYSTEM/ACCESS/<family name>/<family index> directory with the names
and locations of all resident disk files on the family
3. Erases all information for the disk from the central SYSTEM/ACCESS or
SYSTEM/CATALOG directory
8600 0395-514 171

FAMILYACCESS CENTRAL <family name>

Removes the local system access directory from the family and restores the
information to the central directory.
To process this command, the system starts an independent runner named

COPYDIR. The name of this process then changes to FAMILYACCESS CENTRAL
<family name>. If the specified disk family is using a local system access directory,
the process performs the following steps:
1. Removes instances of the local SYSTEM/ACCESS/<family name>/= directory

from the family
2. Initiates a family rebuild to build all necessary information in the central
SYSTEM/ACCESS or SYSTEM/CATALOG directory
FAMILYACCESS COPY <family name> TO <file title>
Copies the information from the local system access directory to a file with the
specified title. Use this command to make a backup copy of the local system access
directory while the directory is in use. Do not use library maintenance to create
backup copies of the directory, because internal records in the directory might
change during the copy operation.
To process the FAMILYACCESS COPY command, the system starts an independent

runner named COPYDIR. The name of this process then changes to FAMILYACCESS
COPY <family name>. If the specified disk family is using a local system access
directory, the process copies the active local SYSTEM/ACCESS/<family
name>/<family index> directory into the designated file.

A disk family with a local system access directory cannot be listed in the volume
library and cannot contain any cataloged files. Refer to the explanation of the
VOLUME ADD and CATALOG ADD statements in the WFL Programming Reference
Manual.
The Disk Resource Control (DRC) feature cannot be used on the system if any disk
families use local system access directories.
172 8600 0395-514

FAS (Failure Analysis Summary)

The FAS (Failure Analysis Summary) command provides a summary of recent error
counts and enables you to set the CPM threshold limit value that causes the
operating system to take special action in response to those errors.
Syntax
Explanation
FAS
Displays the error threshold and counts.
FAS LIMIT CPM <number>

Specifies the CPM error threshold limit. If the system has multiple CPMs, a CPM is
saved when it reaches the error limit. No action is taken if the threshold limit is
zero.
Examples
Example 1
FAS
CPM threshold : 10
CPM 5 : 2 errors
Example 2
FAS LIMIT CPM 5
CPM threshold : 5
No CPM errors
8600 0395-514 173

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.
<mix number list> FI

Use the minus sign () modifier to display large values of I/O time and to display
large values of read, write, and transaction counts. If the minus sign () modifier is
omitted, the details for each file are shown on a single line.
<mix number list> FI VSS2

Reports the following VSS-2 migration information for each disk 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.
174 8600 0395-514

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
4 files for mix 9886

Kind Use Reads Writes Trans Time File Title
Pack I/O 3 7 10 0:00:00 *SYSTEM/COMS/MARC/COMMAN
Pack I/O 0 0 0 0:00:00 *SYSTEM/COMS/MARC/COMMAN
Pack Out 0 28 28 0:00:01 *TANKFILE/COMMANDER ON D
Pack In 16 0 16 0:00:01 *SYSTEM/MARC/MENUGRAPH/E
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 -

Kind Use Reads Writes Trans Time
Pack Out 9,863 887,674 8,876,748 2:00:25
(ADM)FI/EXAMPLE ON USER.
Pack In 1,441,801 0 14,418,000 0:17:50
(ADM)FI/EXAMPLE ON USER.
8600 0395-514 175

Example 3
This example shows a report for one mix number, with VSS-2 information requested:
9886 FI VSS2

RMW Write Ratio File Frame Block File Title
Count Count Structure Size Size
0 100 0% ALIGNED180 48 720 FILE/1
File attributes support VSS-2 logical-physical alignment.
FAMILY: PERIPH is comprised of 180-byte and VSS-2 disks.
25 125 20% ALIGNED180 48 720 FILE/2

File opened for direct I/O - cannot analyze file attributes.
FAMILY: USERS is comprised of VSS-2 disks.
16 100 16% ALIGNED180 48 512 FILE/3

File attributes do not support VSS-2 logical-physical alignment.
FAMILY: DISK is comprised of VSS-2 disks.
FILE/4
Foreign file - cannot analyze file attributes.
176 8600 0395-514

FILELOCKTLIMIT (File Lock Time Limit)

The FILELOCKTLIMIT (File Lock Time Limit) command interrogates, establishes, and
modifies the system-wide time limit used by the record-locking protocols. The default
value is 0 (unlimited). For detailed information about the record-locking protocols,
refer to COBOL ANSI-85, Vol. 1 and the description of the RECORDLOCKER
procedure in the MCP System Interfaces Programming Reference Manual.
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
8600 0395-514 177

FIND
FIND
The FIND command searches the mix, disk, and tape subsystems to find items with
specific attributes and reports them.
You can use the FIND command to
Get a report on what is in the mix.

Identify disks or magnetic tapes.
Get reports about disk drives or magnetic tapes.
Syntax
<object type>
<selection attribute>
<wild card>
<delim>
One of the following characters
/ \ I ~ ! @ # $ % ^ & * '
178 8600 0395-514

FIND
<date value>
For <date value>
<month> is two digits representing the selected month.

<day> is two digits representing the day of the month.
<year> is four digits representing the year.
TODAY selects today's date.
<integer value> is used to adjust today's date by the number of specified
days. A minus sign must precede the 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.
Attribute Name Type Description
ACCESS String Process access code
ASDSINUSE Integer Number of ASDs in use
CHARGE String Process charge code
CODEFILE String Title of the object code file
CODEMEMORY Integer Memory used by the segment dictionary of the

process
COMPILER Boolean TRUE if the process is a compiler
CONTROL Boolean TRUE if the process is a control program
CPURATE Integer Recent processor usage of the process as a

percentage
CPUTIME Integer Process processor time
IDENTITY String Process identity (from MP <code file> +

IDENTITY)
INITPBITS Integer Count of initial presence bits
8600 0395-514 179

FIND
INITPBITTIME Integer Processor time used for initial presence bits
IOTIME Integer Process I/O time
JOBNO Integer Process job number
LOCKED Boolean TRUE if the process is a locked program
MEMORY Integer Process total memory
MIXNO Integer Process mix number
MPID String The MPID attribute of the process
NAME String Process name
ORGLSN Integer LSN of originating station
ORGSTATION String Station name where process originated
OTHERPBITS Integer Count of non-initial presence bits
OTHERPBITTIME Integer Processor time used for non-initial presence bits
PRIORITY Integer Process priority
PU Boolean TRUE if the process has PU privilege from the MP

+ PU command
QUEUE Integer The job queue, if any, that is the source of the
process
READYQTIME Integer Process ready queue time
RELEASEID String Release identity of process
SAVECODEMEMORY Integer Save memory used by the segment dictionary
SAVEMEMORY Integer Save memory in use by the process
SECADMIN Boolean TRUE if the process has SECADMIN privilege

from the MP + SECADMIN command
SUPPRESSED Boolean TRUE if the process is suppressed
TASKING Boolean TRUE if the process has TASKING privilege from

the MP + TASKING command
USER String Process user code
180 8600 0395-514

FIND
FIND MIX <selection attribute>

Finds all mix entries that match the selection attribute. This command searches mix
entries of all types, including library mix entries. For each mix entry, this command
returns the mix number, job number, and name as well as the selection attribute.
The mix attributes that can be specified are the same as the library attributes that
were listed previously.
FIND MT <selection attribute>

Finds all tape drives that match the selection attribute. For each tape drive, this
command returns the unit number, serial number, reel number, and name as well as
the selection attribute.
Use the FIND command and the following attributes to query mounted tapes.
Attribute Type Description

Name
MIX Integer Mix number of the program using the tape
NAME String Tape name
SCRATCH Boolean TRUE if the tape mounted is a scratch tape
SCRATCHPOOL String Scratch pool of the mounted tape
SERIAL String Serial number
TOTALREADS Integer Total number of reads of the tape on the drive
TOTALWRITES Integer Total number of writes to the tape on the drive
UNITNO Integer Unit number of the tape drive
FIND PK <selection attribute>

Finds all disks that match the selection attribute. All FIND PK commands return the
unit number, serial number, family index, and name in addition to the other selection
attribute that was specified. Use the FIND command and the following attributes to
query disk packs.
AVAILSECTS Integer Available sectors on a pack
BASEUNIT Integer Unit number of a base pack
CACHED Boolean TRUE if unit is being cached
8600 0395-514 181

FIND
CAPACITY Integer Capacity of a pack in sectors
CERTIFIED Boolean Certification status of a mirrored pack
CERTTIMESTAMP Date Timestamp of mirror certification
FAMILYINDEX Integer Index of family member
IOTIMER Integer Timeout value in effect for READ and WRITE

operations on a pack
LARGESTSZSECTS Integer Largest single area available on a pack
LOCALACCESS Boolean TRUE if unit uses local system access directory
MIRRORED Boolean TRUE if unit is a member of a mirrored set
NAME String Pack name
ONLINE Boolean TRUE if unit is on line
QUEUEDEPTH Integer Number of I/Os waiting for a pack
REMOTEDISK Boolean TRUE if unit is a remote disk device
SCRATCH Boolean Purged pack unit
SERIAL String Serial number of a pack
SHARED Boolean TRUE if unit is shared
SITENAME String StoreSafe site name of a StoreSafe named pack
SPARE Boolean TRUE if unit has been entered in the spare disk
pool (as either a free spare or an in-use spare)
STORESAFESTATUS String Status of StoreSafe named units and volumes
TOTALIOS Integer Total number of reads from a pack and writes to

a pack
TOTALREADS Integer Total number of reads from a pack
TOTALWRITES Integer Total number of writes to a pack
TYPE String Acceptable values:

B = base pack
C = continuation pack
UNITNO Integer Unit number
182 8600 0395-514

FIND
VSSTYPE Integer Acceptable values:

0=180-byte disk
1= VSS-1 disk
2 = VSS-2 disk
FIND <object type> <Boolean attribute> = TRUE

FIND <object type> <Boolean attribute> = FALSE
FIND <object type> <Boolean attribute>
A value of TRUE reports objects for which the attribute has a value of TRUE.
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.
FIND <object type> <integer attribute> <relation> <integer value>

Finds objects with a integer attribute that satisfies the relation. For example, FIND
MIX MEMORY > 5000 returns all mix entries using greater than 5000 words of
memory. Following are the possible relations.
Relation Meaning
= Equal to
<> Not equal to
> Greater than
>= Greater than or equal to
< Less than
<= Less than or equal to
FIND <object type> <string attribute> <wild-card string>

Finds objects with a string attribute matching the wild-card string. The string can
include the following special characters.
Equal sign ( = ) Matches any sequence of characters
8600 0395-514 183

FIND
Question mark ( ? ) Matches any single character
Tilde ( ~ ) Matches any sequence of characters except a slash ( /)

space character.
contain the string "SYSTEM":
FIND MIX NAME =system=
"system":
FIND MIX NAME LIT ^=system=^
FIND <object type> <selection attribute> SORT

FIND <object type> <selection attribute> SORT +
FIND <object type> <selection attribute> SORT
The SORT option causes the output to be sorted. SORT or SORT + sorts the output in
ascending order. SORT sorts the output in descending order.
The SORT option cannot be used with a Boolean selection attribute.
FIND <object type> <selection attribute> 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 its value per line.
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.
184 8600 0395-514

FIND
FIND MIX MEMORY > 60000
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:
FIND MIX MEMORY > 100000 SORT-
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
8600 0395-514 185

FIND
Example 3
This example reports all packs on the system with a name starting with the string
SYS:
FIND PK NAME 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:
FIND PK UNITNO <= 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:
FIND PK AVAILSECTS < 300000
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:
FIND MIX RELEASEID =DIAGNOSTICS= ALL
--------------------------------------------------------------
MixNo: 38018
JobNo: 38016
ReleaseID: CANDE-051.1A.4 (51.189.8015)<OPTIONAL DIAGNOSTICS>
Name: *SYSTEM/CANDE ON SUPPORT
--------------------------------------------------------------
186 8600 0395-514

FIND
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:
FIND PK CERTTIMESTAMP = TODAY
UnitNo-Serial-FamilyIndex-Type-Certification Date and TimeStamp-Name

180 000180 1 B Mon, May 13, 2002 @ 14:40:03 T180.
8600 0395-514 187

FM (Form Message)
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:
FM REJECTED, REQUIRES <device list>
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.
---Job-Task-Pri-Elapsed-------- 1 WAITING ENTRY --------------------

1126/1127 80 1:13 *SYSTEM/BACKUP
REQUIRES FM:"TWOPART", LP
1127 FM LP4
188 8600 0395-514

FR (Final Reel)
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
8600 0395-514 189

FS (Force Schedule)
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:
INSUFFICIENT MEMORY TO FULFILL FS REQUEST
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.
---Mix-Pri---Elapsed--WordsReq-- 2 SCHEDULED ENTRIES ----------------

6599 50 :03 2K (PDW) (PDW)OBJECT/TEST/MLS ON MCPMAST
6600 50 :03 2K (SPALDING) *CONTROLCARD
6599 FS
190 8600 0395-514

FS (Force Schedule)
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
8600 0395-514 191

FREE (Free Resource)

The FREE (Free Resource) command detaches resources from the executing
partition.


THIS UNIT.
command again.
Note: FREE is a synonym for DOWN. Use FREE on IOM systems. Use DOWN on
IOP systems.
Syntax
<device number list>

A list of numbers or number ranges separated by commas.
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
192 8600 0395-514

FREE IOM <number>

FREE IOM <number> :READY
FREE IOM <number> :SAVE
Save and then free the specified requestor from the system and then mark the CPM
or IOM as saved and not in use. The CPM and IOM numbers must be integers in the
range 0 through 11. For VM systems, the CPM number must be in the range 4
through 11. If the CPM or IOM is the last requestor of that type in the system, the
system displays an error message and does not free the requestor. If all the modules
in the domain that contains the specified requestor are saved, the system frees the
domain.
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:
MODULE CAN BE FREED AFTER RELATED MODULES ARE SAVED
FREE MSM <number>

FREE MSM <number> :READY
FREE MSM <number> :SAVE
Free the memory in the MSM from the operating system and free the MSM from the
partition. The MSM number can be either 0 or 1.
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:
MODULES CAN BE FREED AFTER RELATED MODULES ARE SAVED
This command might fail for the following reasons:
Requestors associated with the MSM belong to the partition.

Not all the memory in use in the MSM can be saved.
Not all the modules in the domain that contains the MSM are saved.
FREE <device type> <unit number list>
Detaches the devices from their former group and makes them available to any
group. Unit numbers and device numbers can be any integer from 1 to 32767.
FREE CTL <device number list>

Detaches the specified CTL units from their former group and makes them available
to any group. Device numbers can be any integer from 1 through 32767.
Remedy the hardware problem causing the failure.
8600 0395-514 193

Enter the command FREE CTL <device number list>.

Enter the command ACQUIRE CTL <device number list>.
For example, a BCC-clear or a base power loss requires that you perform this
procedure for each CTL in the affected base.
FREE NETPORT <device number> LINEID <number>

Frees the LINEID <number> that is associated with the internal networking port that
is identified by the device number. The LINEID number is either 1 or 2, depending on
the position of the Ethernet port on which the LINEID depends. This form of the
command disables the Ethernet port to be used by networking protocols.
If the LINEID is designated as NEVER ACQUIRE in the Peripheral Configuration

Description, the system responds with the following message:
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
CPM 6 WILL BE FREED
Example 2
This example frees a memory subsystem module:
FREE MSM 1
MSM 1 WILL BE FREED
Example 3
This example frees an I/O module:
FREE IOM 1
IOM 1 WILL BE FREED
Example 4
This example frees a CTL unit:
FREE CTL 4001
CTL 4001 WILL BE FREED
194 8600 0395-514

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:
FREE TSP 200
TSP200 WILL BE FREED
SUCCESSFULLY FREED TSP200

Attaching a Resource
To attach a resource to an active group, refer to the ACQUIRE (Acquire Resource)
command.
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.
Identifying Dependent Devices

When the system frees a control device, it marks the dependent devices as having
no path. Device x is dependent on device y if freeing y eliminates the only remaining
path from x to the executing partition.
Using Critical Units

The following units are critical. If any critical unit is dependent on a control, you
cannot free that control.
Halt/load family
OVERLAY family
JOBDESC family
CATALOG family
SYSTEM/SUMLOG family
8600 0395-514 195

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.
You can free the following units by entering a single number:

Use the READY option to change the state of the modules in the domain from free to
savednot in use. Use the SAVE option to change the state of the modules in the
domain from free to saveduser saved.
Understanding IEA-1 IOPs

The IEA-1 IOP provides two Ethernet connections and supports one internal port for
connectivity between distributed networking software such as TCPIPSUPPORT in the
MCP environment and NNS implementation within the IOP.
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
196 8600 0395-514

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:
FREE VC <unit number>
On IOM systems, all 26 VC units outboard of a CTL have the same unit number.
Freeing TSP Units

You must explicitly free each unit that makes up a Telephony Services Platform
(TSP). You can enter either a separate FREE TSP <unit number> command for each
unit or explicitly list each unit in one command as follows:
FREE TSP 200,201,202,203
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.
8600 0395-514 197

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
198 8600 0395-514

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
8600 0395-514 199

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
200 8600 0395-514

HI (Cause Exception Event)

The HI (Cause Exception Event) command causes the exception event of a process
and, optionally, assigns a number to the VALUE task attribute of the process. If a
noninteger number is entered, it is rounded to the nearest integer before it is
assigned to the VALUE task attribute.
For a definition of exception event and an explanation of the EXCEPTIONEVENT task

attribute, refer to the Task Attributes Reference Manual.
Syntax
Explanation
<mix number list> HI
Causes the exception event of the processes in the mix number list.
<mix number list> HI <number>

Stores this value in the VALUE task attribute of the processes in the mix number list
and causes their exception event. The maximum value for the number variable is
(10**111).
Example
The following example sets the VALUE task attribute for mix 4312 to 5:
4312 HI 5

When you direct the <mix number> HI command to a library maintenance task or
archive process, the task or process responds with a message that describes the
status of the requested operation. Refer to the System Messages Manual for detailed
information about the message syntax.
8600 0395-514 201

HLUNIT (Specify Halt/Load Unit)

The HLUNIT (Specify Halt/Load Unit) command displays or specifies the halt/load
unit information. This command can specify or display the following halt/load
devices:
Primary halt/load pack

Primary halt/load pack control
Alternate halt/load pack
Alternate halt/load pack control
Halt/load ODT
CD-ROM or CD-RW drive
Tape unit
This information is maintained by the console. The halt/load pack is the pack
containing such information as the operating system and structure tables. The
alternate halt/load pack is used if problems occur with the primary halt/load pack.
The halt/load ODT is available to primitive software (LOADER and SATAPEDUMP).
The alternate halt/load pack specification can be deleted by this command.
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 CD <unit number>

When this command is specified, a Force Dump is able to automatically initiate when
a CD-R is mounted on the CD-ROM or CD-RW drive. This allows automatic force
dumps to proceed when requested from the MCP on an unattended system.
HLUNIT PK <unit number>

Designates the pack identified by the unit number as the new halt/load pack.
202 8600 0395-514

HLUNIT PK <unit number> VIA CTL <CTL number>

Designates the pack identified by the unit number as the new primary halt/load unit.
The CTL identified by the device number is used for access to the halt/load unit.
HLUNIT PK (BACKUP) <unit number>

Designates the pack identified by the unit number as the new alternate halt/load
unit.
HLUNIT PK (BACKUP) <unit number> VIA CTL <device number>

Designates the pack identified by the unit number as the new alternate halt/load
unit. The specified control is used for access to the halt/load unit.
HLUNIT PK (BACKUP)
Designates the alternate halt/load unit parameter to be cleared.
HLUNIT SC <unit number>

Designates the ODT (also known as the system console) identified by the unit
number as the new halt/load ODT.
HLUNIT TAPE <unit number>

When this command is specified, a Force Dump is able to automatically initiate when
a "DUMMMP" scratch tape is mounted on the tape unit. This allows automatic force
dumps to proceed when requested from the MCP on an unattended system. The
syntax for the command allows either TAPE or MT to be specified as the device (that
is, HLUNIT MT <unit number> or HLUNIT TAPE <unit number>).
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
8600 0395-514 203

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

When you halt/load the system, the MCP automatically places mirrors of critical
diskssuch as the halt/load family, the log family, and the catalog familyinto the
auditing state so that write operations can complete before the mirrored copies come
online. If the OP 24 (OKTIMEANDDATE) is set, the MCP waits for you to answer the
message PLEASE VERIFY TIME AND DATE. You must enter either TIMEOK or <mix
number> OK. During this delay, if the audit trail, which is maintained in memory, is
lost, the mirrored copies of the critical disks are also lost.
HLUNIT TAPE and HLUNIT CD are allowed only on IOP systems.
204 8600 0395-514

HOLD (Hold Unit for Operator Use)

The HOLD command either prevents the system from assigning files to a tape on a
tape unit or allows the system to assign files to a tape on a tape unit that was
previously restricted by a HOLD command.
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
MT 10 FILE ASSIGNMENT HOLD IN EFFECT
Example 2
HOLD - MT 10
MT 10 FILE ASSIGNMENT HOLD NOT IN EFFECT
Example 3
HOLD SC 1
SC 1 FILE ASSIGNMENT HOLD IN EFFECT
PER SC
1 S C R A T C H (HOLD)
8600 0395-514 205


If you want to acquire a tape unit and prevent file assignment so that you can
examine a tape label, perform the following steps:
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
If you have an IOP system, enter the following syntax:

UP 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.
206 8600 0395-514

HOSTNAME (Hostname)
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:
HOSTNAME WILL BE UNSPECIFIED AFTER NEXT HALT/LOAD.
If BNA is running, the system displays the following message:
HOSTNAME CANNOT BE REMOVED WHEN BNAV2 IS AVAILABLE
8600 0395-514 207

HOSTNAME (Hostname)
Examples
Example 1
HOSTNAME
HOSTNAME: BLUE
Example 2
HN = HOST
LOCAL HOSTNAME IS: TRPROGD

HOSTNAME WILL BE >>HOSTC<< AFTER NEXT HALT/LOAD
208 8600 0395-514

HS (Hold Schedule)
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
JOB SELECTION STOPPED
Example 2
HS-
JOB SELECTION RESUMED
Example 3
HS?
SCHEDULE IS NOT HELD
8600 0395-514 209

HU (Host Usercode)
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 DSS requests are the following:
System commands sent to a remote host with the AT <host name>

command.
File transfer, initiated by the WFL COPY statement.
Job transfer, initiated by the WFL statement START or ?AT <hostname>. (If
the local alias of the usercode used to transfer the job is marked as having a
SYSTEMUSER status, the job runs at the remote host without a usercode;
otherwise, it runs under the local alias usercode. If the job contains a
usercode, it runs under that usercode.)
If a host usercode has not been set through the HU command and if any of the
preceding DSS requests are made from an ODT without a terminal usercode, an
error message is generated at the initiating host.
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
210 8600 0395-514

HU (Host Usercode)
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
HOST USERCODE: SDSYSTEM
Example 2
HU LASYSTEM
HOST USERCODE: LASYSTEM

administrator usercode is required to execute this command.
8600 0395-514 211

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.
<mix number> IB <number>

Specifies the instruction block indicated by <number>, which can have a value from
1 through 63.
Examples
Example 1
3178 IB
INSTRUCTION 07 : MOUNT TAPE SYS/TEST AND START AGAIN.
Example 2
2657 IB 1
INSTRUCTION 01 :PLEASE DS MY JOB IF NO FILE A/B IS PRESENT.
212 8600 0395-514

ID (Initialize Data Comm)

The ID (Initialize Data Comm) command is used for the following purposes:
To initialize an enhanced data communications data link processor (EDCDLP)

or a data communications host adapter (DCHA).
To initialize, change, or display data-comm-related items, such as the prefix
for the DATACOMINFO file, and various options.
To direct commands to the DCCONTROL process in control of a device.
To modify options in the data comm subsystem that control system-wide
auditing of data comm message traffic.
To allow any program that is listed in the DATACOMINFO file as a MCS to
initialize its primary queue and thereby become recognized by the MCP as an
MCS.
On BNA V2 systems, to initiate the DATACOMSUPPORT library that is
necessary to support pseudostations. Refer also to AUTODC (Option 12) in
the OP (Options) command.
usercode is required to execute the form of this command that alters the data comm
prefix. If security administrator status is not authorized for the system, any operator,
SYSTEMUSER, or privileged user can execute the command.
Syntax
8600 0395-514 213

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:
NSP <unit number> NOT DECLARED IN NDL
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:
A task opens a remote file.

An MCS attempts to initialize its primary queue.
BNAV2 initialization makes a request to initialize COMS.
A user transfers an ODT to MARC by using the ??MARC command.
Before initialization of the NSP, the system can dump its memory contents if the data
comm information tables are marked with an indication to dump this NSP. This action
occurs if the previous activation of the NSP terminated with an error and if the dump
request made by the system in response to the error failed. Such a failure results in
the data comm information tables being marked with an indication to dump the NSP.
If you want to avoid the dump action, enter ID <unit number> :CLEAR.
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:
214 8600 0395-514

NAME TOO LONG
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:
NO FILES WITH SPECIFIED NIF PREFIX FOUND
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.
ID <file name> ON <family name>

Designates the family name on which the specified DATACOMINFO file resides. If the
sequence <file name> ON <family name> exceeds 24 characters, the system
responds with the following message:
NAME TOO LONG
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:
NO FILES WITH SPECIFIED NIF PREFIX FOUND
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.
A pending change to a new DATACOMINFOFILE now becomes effective. The

existence of a pending change is identified by the NIF TO BE value response returned
in response to an ID command. Any subsequent system initialization uses the new
DATACOMINFOFILE.
ID <unit number> :QUIT

Causes the NSP specified by the unit number to terminate. Any active sessions or
open remote files to stations associated with the NSP close. No other data comm
services are affected, even if the specified NSP is the only active NSP. The system
preserves the MCS status of each MCS.
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
8600 0395-514 215

use this option to terminate all NSP tasks without terminating MARC dialogs that are
active at ODTs.
ID <unit number> :DUMP

Directs the device specified by the unit number to dump its memory into a file titled
DUMP/NSP/<number 1>/YYMMDDHHMMSS on the halt/load disk unit. If you do not
specify the unit number, the system directs all running NSPs to dump their
memories. Dumping an NSP can be useful in debugging data comm problems. The
DCDLPDUMPANALYZER and NDLIIANALYZER utilities can be used to analyze the
dump resulting from this operation.
ID <unit number> :CLEAR

Causes the system to clear and initialize the NSP, rather than to resume
communication with the NSP if it is running. If the specified unit is not running, the
system initializes the NSP task for the unit. However, the system also resets any
indication to dump the NSP and does not attempt to dump it before reinitialization.
ID :OPTION = ALL, <option number>, <option number>, . . .

Sets the option byte to all 1s (ones) and sets any following options to 0 (zero). The
equal sign (=) is optional.
ID :OPTION = NONE, <option number>, <option number>, . . .

Sets the option byte to all 0s (zeros) and sets any following options to 1 (one). The
equal sign (=) is optional.
ID <unit number> :OPTION = <option number>

ID <unit number> :OPTION = + <option number>
ID <unit number> :OPTION = <option number>
Specify that the requested activities be audited by causing the system to write to a
file on the halt/load unit. The audit options apply to all active NSPs. The option
number value must be an integer in the range 0 through 7. If you specify +
<option number>, you set the option and any following options. If you specify
<option number>, you reset the option and any following options. If you specify the
optional unit number and if that NSP is not running, the system initializes the NSP.
The specified audit activity is performed for the NSP and all other active NSPs.
Activity initiated by DCINITIAL (value 0) is written to a file titled

NSPAUDIT/DCINITIAL/<NSP unit number>. All other audit activity is written to a file
titled NSPAUDIT/DCCONTROL/<NSP unit number>.
Valid option number values and their meanings are as follows.
Value Meaning
0 Audit all I/O activity initiated by DCINITIAL to the NSP.
1 Audit all I/O activity initiated by DCCONTROL to the NSP.
2 Audit all DCCONTROL-formatted requests in DCCONTROL.
216 8600 0395-514

Value Meaning
3 Audit all DCWRITE-formatted requests and results in DCCONTROL.
4 Reserved.
5 Audit all NSP trace results.
6 If the DIAGNOSTICS option (OP 6) of the OP system command is also

set, perform an NSP dump after any severe error.
7 Audit all NSP error conditions.
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.
The MAXPSEUDO variant of the ID command controls only pseudostations associated

with the DATACOMINFO file, that is, those that are numbered from 2 through
16383. Thus, the maximum value that you can specify is 16383. If you specify a
nonzero value, the system allocates that many pseudostations in the data comm
information tables the next time that the data comm subsystem is initialized.
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.
8600 0395-514 217

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 <unit number> :DCTRACE

Displays the current setting either for the unit specified by the unit number value or
for all active NSPs.
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.
After an ID DCTRACE command is entered, one of the following messages (the

contents of which depend on the prior setting of the DCTRACE option) appears on
the ODT:
<NSP identification> TRACE STARTED

<NSP identification> TRACE ALREADY STARTED
<NSP identification> TRACE STOPPED
<NSP identification> TRACE ALREADY STOPPED
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.
218 8600 0395-514

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
5435 NSP 108 INITIALIZED
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
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.
ID 110 SYS231: OPTION NONE 0 7
8600 0395-514 219

Example 6
This example directs device 110 to dump its memory to a file named
DUMP/NSP/110/YYMMDDHHMMSS:
ID 110: DUMP
220 8600 0395-514

IK (Install Keys)
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 partition processor image consists of a processor count, the processor performance

level, and constraints on how the processors must be configured (nonredundant or
redundant power domains). For example, a partition processor image of 4@9N
indicates that this partition is licensed to use 4 processors at performance level 9,
where all processors reside in a single nonredundant power domain.
Each processor license key contains embedded processor-performance

characteristics for all licensed partitions in the system; each active partition shares in
the system-wide pool of partition images. Therefore, only one processor license key
is active on the entire system at any time.
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.
8600 0395-514 221

IK (Install Keys)
Syntax
222 8600 0395-514

IK (Install Keys)
<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>
<subpod>
8600 0395-514 223

IK (Install Keys)
<IP unit>
An integer from 0 through 3 that identifies an instruction processor within a subpod
on an IOP system.
<cell>
690 system.
<unit>
An integer from 0 through 7 that identifies a particular unit within the cell.
<custom processor set number>

On systems that support custom processor sets, a value of 0 designates the standard
processor set and a value of 1 through n (where n is the maximum number of
custom processor sets as specified in the performance key) designates a custom
processor set.
Explanation
IK
Displays the syntax diagram for the IK command.
IK ADD <key> : <password>

Adds the specified key to the system keys file *SYSTEM/KEYSFILE on the halt/load
family. This process creates a new version of the file and removes the old version.
The total length of the key, the colon (:), and the password must not exceed 150
characters.
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.
IK DELETE ALL <string>

Deletes any keys that begin with the specified string from the keys file on the
Halt/Load unit, creates a new version, 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:
Copy your active keys file to disk or tape.

Ensure that your active keys file is secure.
224 8600 0395-514

IK (Install Keys)
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:
Your string must contain at least three characters.

You cannot specify the current SSR release level, the two preceding SSR
levels, or a future SSR level. The first two characters in a numeric string are
taken as the SSR level.
For example, if the current SSR level is 51.1, levels 52.1, 51.1, 50.1, and 49.1
are protected.
You cannot specify a string that begins with the characters "UL-" or "00-".
When any of these conditions are detected, the system terminates your request with
an UNRECOGNIZED REQUEST message.
IK DELETE ALL <string> KEYSFILE = <file title>

Deletes the specified key or keys matching <string> from the specified alternate
keys file. In the case of a DELETE ALL request, restrictions described above do not
apply.
IK DELETE ALL EXCEPT <string> KEYSFILE = <file title>

Deletes any key from the alternate file that does not match the specified string.
Following are restrictions for deleting multiple key alternate files:
The string must contain at least one character.

You must specify an alternate keys file with a DELETE ALL EXCEPT request.
On a DELETE ALL EXCEPT request, the <string> that you enter must match at
least one key; otherwise, it is terminated with a KEY NOT FOUND message.
The primary purpose behind the alternate keys file delete capability is to provide an
environment in which you can perform keys file maintenance without the risk of
impacting site production.
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.
8600 0395-514 225

IK (Install Keys)
IK SHOW KEYSFILE = <file name>

IK SHOW <string> KEYSFILE = <file name>
Display keys in the specified keys file. If you omit the string parameter, the system
displays all keys. If you specify a string parameter, the system displays only keys
that begin with the parameter.
IK SHOW <string> KEYSFILE = <file name> :PRINTER

IK SHOW <string> KEYSFILE = <file name> :FILE <file name>
List the specified keys in a file. Use PRINTER to specify a line printer file and FILE to
specify a disk file. If a disk file with the specified name already exists, the command
generates an error message.
IK DSADELETE <DSA key set ID>

This command deletes the specified DSA key set from the system DSA keys file,
creates a new version of the file, and removes the old version.
IK DSAMERGE <file name>

This command merges the DSA key sets from the specified DSA keys file into the
system DSA keys file, creates a new version of the file, and removes the old version.
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 DSASHOW KEYSFILE = <file name>

IK DSASHOW <string> KEYSFILE = <file name>
These commands display DSA key set IDs and their corresponding software levels in
the specified DSA keys file. If you omit the string parameter, the system displays all
IDs. If you specify a string parameter, the system displays only key set IDs that
begin with the parameter.
IK DSASHOW : KEYSFILE <file name>

IK DSASHOW <string> : KEYSFILE <file name>
IK DSASHOW KEYSFILE = <file name> : KEYSFILE <file name>
IK DSASHOW <string> KEYSFILE = <file name> : KEYSFILE <file name>
These commands extract the specified DSA key sets and store them in another DSA
keys file indicated by <file name> of the option : KEYSFILE. If this file does not
exist, a new one is created.
IK IOACTIVATE <key ID>

Activates a specific I/O capacity key. Note that only one I/O capacity performance
key can be active system wide for all partitions. Use the IK IOSHOW system
command to list the available valid key IDs.
226 8600 0395-514

IK (Install Keys)
IK IOADD <key string>:<password>

On systems that support I/O capacity on demand (COD), installs a single I/O
capacity key into Server Control.
IK IODELETE <key ID>

On systems that support I/O capacity on demand (COD), deletes a single I/O
capacity key previously installed into Server Control.
IK IOMERGE <keys file>

On systems that support I/O capacity on demand (COD), installs I/O capacity keys
from a keys file into Server Control.
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.
IK IOSHOW <key ID>

On systems that support I/O capacity on demand (COD), displays detailed key
information for a specific key installed into Server Control. Key IDs can range from 1
to 999. If the key ID is that of the currently active key, detailed I/O licensing and
utilization information for the system is also displayed.
IK IPACTIVATE <key ID>

Activates a specific processor license key for the system. Use the IK IPSHOW system
command to list the available valid key IDs. Changing the system processor license
key transforms the respective partition processor images for each active partition. If
the new key is the alternate processor license key or a change from a temporary key
to the previously active permanent key, each partition automatically acquires its
previous partition processor image. If the new key was not the alternate processor
license key, each partition is automatically assigned the default partition processor
image (the lowest-performance processor image licensed by that key). If this is not
the desired image, use IK IPACTIVATE <partition image> to select the desired
image. Verify the respective partition processor image licenses for all running
partitions after the activation of a new processor license key.
IK IPACTIVATE <partition image>

Activates a specific partition processor image license for a specific partition using the
current active processor license key. A partition processor image license consists of
8600 0395-514 227

IK (Install Keys)
three items: the number of licensed processors, the associated processor

performance level, and the constraints on how the processors must be configured
(nonredundant or redundant power domains). Examples include 1@4N, 4@5R,
8@9N, and so forth. The IK IPSHOW ACTIVE system command displays a list of
available and stealable images from which to choose. Activation of an available
image license does not affect image licenses of any other partition. Activation of a
stealable image license resets the respective images for non-local partitions to the
default image license. Verify the respective partition processor image licenses for all
running partitions after the activation of a stealable image license.
IK IPACTIVATE <key ID>:<partition image>

Activates a specific processor license key for the system and a specific processor
image license for a partition. Valid key IDs and images are available using the IK
IPSHOW system command. You can activate any of the displayed images. Choosing
a new processor license key might reset partition processor image licenses for all
active partitions. Verify the respective partition processor image licenses for all
running partitions.
IK IPACTIVATE <key ID>:<image ID>

Activates a specific processor license key for the system and a specific processor
image license identified by the ordinal image identifier. The ordinal image identifier is
available using the IK IPSHOW command.
IK IPADD <key string>:<password>

Adds a single processor performance key into Server Control or the Console. Keys
added from any partition are visible to all partitions.
IK IPDELETE <key ID>

Deletes one or more processor performance keys from a keys file into Server Control
or the Console.
IK IPJAVA + IP <IP identifier>

IK IPJAVA IP <IP identifier>
On systems that support Java capacity on demand (COD), enables the reassignment
of the Java processors. The plus (+) option assigns a processor to the Java processor
set. The minus () option removes a processor from the Java processor set.
IK IPLIMIT <RPM limit>

Sets the maximum performance level of the partition to a value between the
contracted baseline and ceiling. This takes effect immediately, and system meters
account for the new ceiling value in recorded workload delivery. Note that, although
<limit> is a specific RPM value, the system can set the limit only to a restricted set
of RPM values, based upon the supported performance level settings of the CPUs. As
a result, if the selected <limit> value is not supported by the CPUs, the RPM value
that is closest (and less than) the requested <limit> value is selected. System
displays show the requested <limit> as TARGET LIMIT, and the selected <limit> as
ACTUAL LIMIT.
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
228 8600 0395-514

IK (Install Keys)
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 IPLIMIT STD: <custom processor set number> <percentage> %

On systems that support custom processor sets, redistributes standard processor
performance to the standard processor set or a custom processor set.
If there are no custom processor sets defined, the IK IPLIMIT <percentage>%

command can be used, in place of the IK IPLIMIT STD:0 <percentage>% command,
to redistribute performance to the standard processor set.
IK IPMERGE <keys file>

Merges one or more processor performance keys from a keys file into Server Control
or the Console. Keys merged from any partition are visible to all partitions.
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:
E-mail report: *METERDATA/<yyyymmdd>/<hhmm>/EMAIL
Report attachment: *METERDATA/<yyyymmdd>/<hhmm>/ATTACH
Command Subject Description
ACTIVATION Activation Meter Used by Unisys to identify the "begin

Report billing" characteristics of the system.
CONFIG COD license key and Used for upgrade processing.

hardware
configuration Interim
Meter Report
8600 0395-514 229

IK (Install Keys)
Command Subject Description
LOCAL Interim Meter Report Sent to local addresses only. It can be

used for tracking purposes.
METER Interim Meter Report Sent to all addresses. It can be used to

test the e-mail connection to Unisys or
when Unisys requests an interim meter
report.
DATE Monthly Meter Manually forces the resending of a

<yyyymmdd> Report previously generated monthly report to
the currently configured e-mail
destinations.
You can use this form when the report
can be found in the standard location.
FILE <file Monthly Meter Manually forces the resending of a

name> on Report previously generated monthly report to
<family> the currently configured e-mail
destinations.
You can use this form if the report has
been saved using a different name or
has been moved off the halt/load family.
See also Sending a Missing Monthly Metering E-Mail Report to Unisys.
IK IPSET JAVA + <IP unit>

On systems that support JOLT capacity on demand (COD), assigns the specified
processor to the JAVA processor set.
IK IPSET JAVA - <IP unit>

On systems that support JOLT capacity on demand (COD), removes the specified
processor from the JAVA processor set and returns it to the standard processor set.
IK IPSET STD: <custom processor set number> + <IP identifier>

On systems that support custom processor sets, assigns a processor to the custom
processor set.
IK IPSET STD: <custom processor set number> - <IP identifier>

On systems that support custom processor sets, removes a processor from the
custom processor set. A custom processor set number of 0 designates the standard
processor set, and a custom processor set number of 1 through n (where n is the
maximum number of custom processor sets as specified in the performance key)
designates a custom processor set.
230 8600 0395-514

IK (Install Keys)
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 <key ID>

Displays detailed key information for a specific key installed into Server Control or
the Console. Key IDs can range from 1 to 999. If the key ID is that of the currently
active key, then detailed active licensing information is also displayed.
IK IPSHOW METER
Displays an interim system processing power metering report on the ODT.
IK MEMACTIVATE <key ID>

Activates the specified memory key. Note that only one memory capacity
performance key can be active system wide for all partitions. Use the IK MEMSHOW
system command to list the available valid key IDs.
IK MEMADD <key string>:<password>

Installs the specified memory licensing key into Server Control.
IK MEMDELETE <key ID>

Deletes the specified memory key previously installed into Server Control.
IK MEMMERGE <keys file>

Installs all memory licensing keys contained in the specified keys file into Server
Control.
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.
8600 0395-514 231

IK (Install Keys)
IK MEMSHOW <key ID>

Displays detailed memory licensing information for the specified memory licensing
key. Key IDs can range from 1 to 999. If the key ID is that of the currently active
key, detailed memory licensing information for the system is displayed.
Example 1
This example adds the key 511-CANDE-CDE-S with the password
AHQWOMNWEFUMDQE:
IK ADD 511-CANDE-CDE-S:AHQWOMNWEFUMDQE
GOOD KEYSFILE ACTION
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"
--- KEY -------------------- EXPIRES --- LICENSE ID -----------
511-ALGOL-ALG
Example 5
This example displays the keys in the specified keys file, SYSTEM/KEYS/511ON
TEST:
IK SHOW KEYSFILE = SYSTEM/KEYS/511 ON TEST
--- KEY -------------------- EXPIRES --- LICENSE ID -----------
511-ADDSPROPERTIES-SAP
511-ADDSPROPERTIES-SAP-S
511-ALGOL-ALG
511-ALGOL-ALG-S
232 8600 0395-514

IK (Install Keys)
.
.
.
Example 6
This example displays maintenance license keys:
IK SHOW "MAINTKEY"
--- KEY --------------EXPIRES --- LICENSE ID------
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
---- Software Release -- ------ DSA Key Set ID ------

511 SSR511DSAKEYID
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:
IK DSASHOW "SSR51" : KEYSFILE 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.
8600 0395-514 233

IK (Install Keys)
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.
COPY *SYSTEM/KEYSFILE FROM HLUNIT(PACK)TO TAPE(SERIALNO="KYS")
IK SHOW "511"
---KEY --------------------EXPIRES ---LICENSE ID -----------

511-ADDSPROPERTIES-SAP
511-ADDSPROPERTIES-SAP-S
511-ALGOL-ALG
511-ALGOL-ALG-S
.
.
.
IK DELETE ALL "511"
IK DELETE:GOOD KEYSFILE ACTION
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
IK IPSEND: METERING INFORMATION SENT
Example 13
This example illustrates the display of metering information on a prepaid metering
system:
IK IPSHOW METER
Report Type Interim

Version 2
Interval Nov 18, 2004 15:28:38 to
(UTC) Nov 24, 2004 20:11:47
Key 41A38DC3[1] Projected Utilization Avg Workload Current Utilization

Image 2@27R/4
Time 534,508 seconds 2,415 seconds
Total Used 46,801,875 RPM sec 88 RPM 211,459 RPM sec
--> Metered 18 RPM month (standard)
==> 1 MIPS month (standard) ID=012000ABE41A38DC301
Image 4@57N/2 (Most recent inter-partition update)
234 8600 0395-514

IK (Install Keys)

--> Metered 16 RPM month (standard)
==> 1 MIPS month (standard) ID=012000ABE41A38DC302
Example 14
This example illustrates the display of metering information on a base-plus-use
metering system:
IK IPSHOW METER
Report Type Interim

Version 2
Interval Nov 18, 2004 15:28:38 to
(UTC) Nov 24, 2004 17:00:38
Key 41A3560E[0] Projected Utilization Avg Workload Current Utilization

Image 8@57R/1

Base 21,816,400,000 RPM sec 40,000 RPM
Maximum 48,381 RPM
Metered 0 RPM sec
--> Billable 0 RPM month (standard)
==> 0 MIPS month (standard) ID=012000ABE41A3560E01
Image 8@45N Non-Metering Partition Image
Image 4@57N/2
Base 0 RPM sec 0 RPM
Maximum 33,680 RPM
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
SYSTEM MCN/HACH C2462/0620 PARTITION 7 ACTIVE KEY 1 ALT KEY NONE

IMAGES: CURRENT 1@35N, 1 Java IP (IPs UNDER-CONFIGURED)
PARTITION [7]2@35R(100%), 2 Java IPs
AVAILABLE 2@35R(100%), 2 Java IPs
ID TYPE STATUS DAYS/LEFT EXPIRES IMAGES
1 PERM ACTIVE A) 2@35R(100%), 2 Java IPs
8600 0395-514 235

IK (Install Keys)
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
IK IPJAVA: JAVA PROCESSOR ASSIGNED
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
IK IPJAVA: JAVA PROCESSOR UNASSIGNED
Example 18
This example shows a response to an IK IOSHOW command entered on a Libra 585
system:
IK IOSHOW
PARTITION 7 ACTIVE KEY 71 SYSTEM I/O 3 IOP Cards, 1 NW IOP Cards

ID TYPE STATUS DAYS/LEFT EXPIRES I/O
1 PERM ACTIVE 2 IOP Cards, 0 NW-IOP Cards
2 ADD INUSE 1 IOP Cards
3 ADD INUSE 1 NW IOP Cards
Example 19
This example shows a response to an IK IOSHOW ALL command entered on a Libra
585 system:
IK IOSHOW ALL
SYSTEM MCN/MACH 49625/0620 PARTITION 7 ACTIVE KEY 1 ALT KEY NONE

LICENSED I/O 3 IOP Cards, 1 NW-IOP Cards
PARTITION [6] 2 IOP Cards, 1 NW-IOP Cards
[7] 1 IOP Cards, 0 NW-IOP Cards
ID TYPE STATUS DAYS/LEFT EXPIRES I/O
1 PERM ACTIVE 2 IOP Cards, 0 NW-IOP Cards

IO1-6NTCQCTUY66BZ49J5WBEPBFM07ZZU9NHENCEN9FWR9X7AAUZP7J8
2 ADD INUSE 1 IOP Cards

IO1-E7U3T7SXZCPYCPT15WNHUN7YE7K44JB3AG4P5RQKDJFJHPZ6J580
236 8600 0395-514

IK (Install Keys)
3 ADD INUSE 1 NW IOP Cards

IO1-8YTDWE5T9Y9H30AUH0C03P9RGFU5KZZTX9TYMGJBSWC07ZPDSCS5
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
SYSTEM USN/MACH 123456789/0129 PARTITION 7 ACTIVE KEY 9 ALT KEY NONE

CURRENT IMAGE STD (ACTUAL 62% CONFIGURABLE 62%)
STD:0 1@126N (ACTUAL 42%)
ADAPTIVE PRODUCTION PARTITION
PARTITION [7] STD 2@120N/1 (TARGET 62%)

STD:0 (TARGET 42%)
STD:1 (TARGET 20%)
[6] STD 2@72N/1 (TARGET 38%)
ID TYPE STATUS IMAGES

9 PERM ACTIVE A) STD 2@120N/1 (62%)
B) STD 2@72N/1 (38%)
IP1-CSM7N7WHKBYSQT9H2C69XMZ2DQYYHHZJQJ3U4S9DQ2CMR1TENPTF
B) STD 2@72N/1 (33%)
IP1-EPN1NW10BDP5J0RDYSS61E2BK3Q5BHDBP3D3XFJ1FZKU6D0JTP0D
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:
IK IPSEND *METERDTA/JUNE/2005 ON ADMIN
Example 23
For systems that support custom processor sets, this example shows how to assign a
processor to STD:1, the custom processor set:
IK IPSET STD:1 + IP_0_0
IK IPSET: STD: 1 PROCESSOR ASSIGNED
8600 0395-514 237

IK (Install Keys)
Example 24
For systems that support custom processor sets, this example shows how to remove
a processor from STD:1, the custom processor set:
IK IPSET STD:1 - IP_0_0
IK IPSET: STD: 1 PROCESSOR UNASSIGNED
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
SYSTEM MCN/MACH 123456789/012B PARTITION 4 ACTIVE KEY 2 ALT KEY NONE

CURRENT IMAGE STD (ACTUAL 66% CONFIGURABLE 66%)
Java 1 (CONFIGURABLE 2)
STANDARD PRODUCTION PARTITION
PARTITION [4] STD 1@40N/1 (TARGET 66%)
Java 2
[5] STD 1@24N/1 (TARGET 34%)

Java 2
B) STD 1@24N/1 (34%)
IP1-ZWUADDPSHNG86SNE6670MJUMKKWBBTXT06QH5MHBPPSUXJZUC1M
3 TEMP AVAIL A) STD 2@40N/1 (66%)

Java 2
B) STD 2@24N/1 (34%)
IP1-JKLJLKLKLKADSJLKGJLBMI4MLKM575M6LKM8SMLK342452NDNMD
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
SYSTEM MCN/MACH 123456789/022B PARTITION 7 ACTIVE KEY 9 ALT KEY NONE

METERING MODE 0, REPORT DAY 1
CURRENT IMAGE STD (RPM ACTUAL 34830)
STD:0 4@86N (RPM ACTUAL 34830)
Java 3 (CONFIGURABLE 4)
PARTITION [7] STD 4@120N/2 (RPM MAX 48600 BASE 12150 TARGET 35000)
Java 4
[6] STD 2@80R/2 (RPM MAX 18225 BASE 4860 TARGET 10000)
238 8600 0395-514

IK (Install Keys)
9 PERM ACTIVE A) STD 4@120R/2 (RPM MAX 48600 BASE 12150)

Java 4
B) STD 2@80R/2 (RPM MAX 18225 BASE 4860)
METERING MODE 0, REPORT DAY 1, ID 42794838
IP1-CSM7N7WHKBYSQT9H2C69XMZ2DQYYHHZJQJ3U4S9DQ2CMR1TENPTF

Retaining the *SYSTEM/KEYSFILE on the Halt/Load Family
For some products to be fully functional after their installation, it might be necessary
for a particular key to be present. Therefore, it is recommended that you retain the
*SYSTEM/KEYSFILE on the halt/load family after the product is installed. Moreover,
you should back up this file after you install a software release and after you use the
IK MERGE command to install keys for a particular product or feature. Then, if your
*SYSTEM/KEYSFILE is ever accidentally deleted or destroyed, you can easily restore
the backed up version to your halt/load family.
Timeout Limitations
The system closes the KEYSFILE after 15 seconds of no activity.
Maintenance License Keys

Maintenance license keys control the use of peripheral test drivers (PTDs) and
SYSTEM/FAULTLOG/ANALYZER, independently of any peripheral. Customer service
representatives obtain a maintenance license key in the field as part of a
maintenance contract. Without a maintenance license key, PTDs and
SYSTEM/FAULTLOG/ANALYZER cannot run.
Sending a Missing Monthly Metering E-Mail Report to Unisys

Metering reports are automatically sent by e-mail from the server to Unisys on a
monthly basis. Occasionally, network problems or some other circumstance might
prevent the report from being received at the Unisys mailbox. In that event, Unisys
will contact you and provide instructions about how to locate the files that contain
the saved e-mail and the related attachment.
To resend a missing monthly metering e-mail report to Unisys, select one of the
following commands:
IK IPSEND DATE <date>

The variable <date> is in the format YYYYMMDD and represents the second node
in the standard title of the saved e-mail message
(*METERDATA/YYYYMMDD/HHSS/EMAIL).
IK IPSEND FILE <file title>
The variable <file title> is the title of the saved e-mail file. It is either the
standard title or a nonstandard title if the file has been renamed.
8600 0395-514 239

IK (Install Keys)
One of the following three responses appears on the ODT after you send the
command:
METER REPORT RESENT

This message indicates that the specified meter report and corresponding
attachment were located and sent.
METER REPORT NOT RESENT
This message indicates that there was a problem in either accessing the specified
meter report file or verifying it as a metering report.
METER REPORT RESENT WITH NO ATTACHMENT
This message indicates that the specified metering report was located and sent.
However, the attachment file was either not located or there was a problem
accessing the file or verifying it as a metering attachment,
The system log also receives an entry to indicate that a RESEND function was issued.
240 8600 0395-514

IL (Ignore Label)
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.
The device can be any device except a line printer (LP).
Family substitution is ignored when the IL command is used.
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.
---Job-Task-Pri-Elapsed--------- 1 WAITING ENTRY --------------------

1108/1109 50 :08 *LIBRARY/MAINTENANCE
NO FILE TBACKUP/FILE000 (MT) #1
1109 IL MT 162
8600 0395-514 241

INITIALIZE (Initialize Disk)

The INITIALIZE (Initialize Disk) command initializes variable-sector-size disks that
were preformatted by the manufacturer or that were previously configured with the
RC (Reconfigure Disk) command.


THIS UNIT.
command again.
Syntax
<oldname list>
<sector format>
VSS1 or VSS2.
Explanation
This command
Applies a Unisys label to the disks.

Writes a master available table (MAT) on the disks.
Initializes the disks to a capacity based on the physical capacity of the device
and MCP environment capacity calculation algorithms.
242 8600 0395-514

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.
VSS = <sector format>

Controls the sector format used for variable sector size (VSS) disks. For information
about VSS disks, refer to the Peripherals Information File on the Product
Documentation CD-ROM.
Possible values for the VSS sector format are
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:
MUST SPECIFY VSS FORMAT FOR INITIALIZE

ACCEPT: VSS = VSS1/VSS2
The RSVP accepts an AX or DS response.
OLDNAME = <oldname list>

For disks previously labeled by the RC system command, you can specify the current
family names of the disks that are to be initialized. Otherwise, you must respond to
an ACCEPT OLDNAME = <FAMILY NAME> request for each disk. Note that the order
of the family names in the oldname list does not matter.
Examples
Example 1
This example initializes disk 43 to VSS2 mode:
INIT PK 43 VSS = VSS2
8600 0395-514 243

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.
INIT PK 80 - 81, 836 OLDNAME = (ALPHA, TEXT) VSS = VSS2

This command can be used only if all the following conditions are true:
The I/O subsystem supports variable sector size disks.

The disk units are self identifying disks with variable sector size.
The disk units are write-enabled but are not in use.
If the disk units are mirrored disks, they must be closed.
To initialize a mirrored disk, you must first release the mirrored disk with the
MIRROR RELEASE command. The INITIALIZE command is allowed for closed
mirrored disks and disks assigned to the spare disk pool for the mirrored disk pool
facility (MDPF).
Following are messages that can be displayed in response to this command:
PK <unit number> INITIALIZED TO <180-byte-sectors> SECTORS (<total-bytes> BYTES)
The disk was successfully initialized.
PK <unit number> CANNOT INITIALIZE A MIRRORED UNIT
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.
PK <unit number> HAS BEEN INITIALIZED TO THE MAXIMUM SUPPORTED CAPACITY
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.
PK <unit number> INVALID CAPACITY - DISK CANNOT BE INITIALIZED
The disk capacity is less than 64 megabytes, which is the minimum capacity required
for a self identifying disk with variable sector size.
244 8600 0395-514

INSTALL (Install Software)

The INSTALL (Install Software) command copies and installs system software from
the system release media. It performs the following steps:
1. Copies a keys file from CD-ROM to the halt/load family.

2. Copies the GENERALSUPPORT library file, the Simple Installation (SI)
program, the WFLSUPPORT library file, the CENTRALSUPPORT library file, and
the related data files from CD-ROM to the DISK family. If the DATAONLY
option is specified, the support libraries and the installation program are not
copied.
3. If step 2 is successful, runs the Simple Installation (SI) program in batch
mode, using the parameters specified in the system command. The program
copies the remaining software CD-ROM to the DISK family and, optionally,
installs it.
Note: If you do not use the INSTALL = <FALSE> option, the command installs
that is, sets all SLs and runs all installation librariesas well as copies the indicated
software.
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.
8600 0395-514 245

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.
SYSTEMSOFTWARE copies all system software files, except Enterprise Database

Server files, that are needed for a running system.
246 8600 0395-514

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/=
None of the support libraries are copied.
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.
INSTALL KEYSFILE = <release ID>

INSTALL KEYSFILE = <release ID> CDROM <cdrom name>
Merge information into the system keys file *SYSTEM/KEYSFILE from the file
SYSTEM/<release ID>/KEYSFILE for the release specified by <release ID>. These
commands also copy the optional keys file SYSTEM/DSAKEYSFILE from the media to
the halt/load family if the file is on the media.
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.
INSTALL KEYSFILE = <file name>

Merge information for the current software release into the system keys file
*SYSTEM/KEYSFILE from the file specified by <file name>. These commands also
copy the optional keys file SYSTEM/DSAKEYSFILE from the media to the halt/load
family if the file is on the media.
The default value for <file name> is SYSTEM/<release ID>/KEYSFILE.
8600 0395-514 247

INSTALL RELEASEID = "<version ID>"

Specifies the name of the release being installed. If this specification is omitted, the
release that created the Simple Installation (SI) program is assumed. The release
name is used to form the name of the file that contains all the information needed to
install the software. The file name is constructed as follows:
INSTALLDATAFILE/SYSTEM/<compressed release ID>
In the file name, <compressed release ID> is the <version ID> with all
nonalphanumeric characters removed.
INSTALL DISK = <family name>

Copies software that does not need to be on the halt/load family to the specified
family. If this specification is omitted, the software is copied to the DISK family. If
there is no family named DISK on the system, the software is copied to the halt/load
family.
INSTALL HLDISK = <family name>

Copies software that must be on the halt/load pack to the specified family. If this
specification is omitted, that software is installed on the current halt/load family. If
the INSTALL = <Boolean> option is not set to FALSE, any SL mappings are applied
to the current halt/load family rather than to the new halt/load family.
INSTALL INSTALL = <Boolean>

Specifies whether to install the software after copying. TRUE (the default value)
indicates it should be installed. FALSE indicates it should not be installed. FALSE is
useful for preparing new release families when the software is to be installed later.
INSTALL CDROM <cdrom name suffix>

Specifies that all files are copied from CD-ROM. The <cdrom name suffix> is the 5-
digit release ID on the label of the CD-ROM and is prefixed with SYSTEM_ to form
the CD-ROM name.
248 8600 0395-514

Examples
The following table contains examples of the INSTALL command and an explanation
of each example.
This command . . . Performs this action . . .
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
Copies and installs the following software from a

CDROM named SYSTEM_51150:
INSTALLDATAFILE
SI code files
WFLSUPPORT library
INSTALL SUPPORT CDROM Copies and installs the following software from a
51150 CD-ROM named SYSTEM_51150:
Updated files
INSTALLDATAFILE
SI code files
WFLSUPPORT library
8600 0395-514 249

This command . . . Performs this action . . .
INSTALL HLDISK = Copies the following software from a CD-ROM

MYHLPACK, DISK = named SYSTEM_51150:
MYDISK, INSTALL =
FALSE, CDROM 51150 Files needed for a minimal running system
Software necessary for the halt/load disk to the
family MYHLPACK
INSTALLDATAFILE
SI code files
WFLSUPPORT library
INSTALL Copies the following files from the CDROM named

SYSTEMSOFTWARE, SYSTEM_KEYS (if the system is running on MCP
KEYSFILE, INSTALL = software release 51.1):
FALSE,
CDROM 51150 SYSTEM/511/KEYSFILE
SYSTEM/DSAKEYSFILE
Copies the following software from a CDROM

named SYSTEM_51150:
All the system software files

INSTALLDATAFILE
SI code files
WFLSUPPORT library
250 8600 0395-514

IOTIMER (Specify Time-out Value)

The IOTIMER command displays or specifies the time-out value in effect for disk
READ and WRITE operations. Refer to the I/O Subsystem Programming Guide for an
explanation of the I/O timer handling feature.
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
4243 Reserved for internal use
44 SCSI/286 pack
8600 0395-514 251

Subtype Description
45 SCSI/546 pack
4648 Reserved for internal use
49 IPI/M2671P pack
50 SCSI/1367 pack, SCSI/1367-1
52 SCSI/805, SCSI/805-n packs
53 SCSI/1545, SCSI/1545-1, or
SCSI/1545-n packs
54 SCSI/419-1, SCSI/419-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.
252 8600 0395-514

IOTIMER
IOTIMER PK
IOTIMER PK ALL
Displays the I/O time-out value status of all disk units in the system.
IOTIMER PK <unit list>

Displays the I/O time-out value status of the specified disk unit or units.
IOTIMER PK <unit list> VALUE <time-out value>

Assigns the specified time-out value for all READ and WRITE operations issued to the
disks identified by the unit list. If a disk is a member of a mirrored set, all disks in
that set are given the specified time-out value. If the value is DEFAULT, the default
value of 80 seconds is used. If the value is a valid time-out value, the specified
number of seconds is used.
IOTIMER PK SUBTYPE <subtype number>

Displays the I/O time-out value status of disk units with the specified subtype
number.
IOTIMER PK SUBTYPE <subtype number> VALUE <time-out value>

Assigns the specified time-out value for all READ and WRITE operations issued to the
disks identified as having the specified subtype number. If a disk is a member of a
mirrored set, all disks in that set are given the specified time-out value. If the value
is DEFAULT, the default value of 80 seconds is used. If the value is a valid time-out
value, the specified number of seconds is used.
IOTIMER PK ALL VALUE <time-out value>

Assigns the specified time-out value for all READ and WRITE operations issued to all
disks defined on the system, including disks which are currently freed from the
system. If the value is DEFAULT, the default value of 80 seconds is used. If the value
is a valid time-out value, the specified number of seconds is used.
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
-- PK ----------------- TIMEOUT --------- DESCRIPTION (SUBTYPE) ---

100 HLPACK #1 80 (DEFAULT) SCSI/1545 (53)
101 TIMERPK #2 40 SCSI/1545 (53)
200 TIMERPK #1 40 SCSI/805 (52)
201 SUPPORT #2 80 SCSI/805 (52)
300 TEST #1 20 SCSI/419 (54)
301 TESTHOLD #1 20 SCSI/419 (54)
302 DBPACK #1 80 (DEFAULT) SCSI/805 (52)
8600 0395-514 253

Example 2
This example shows the response to
IOTIMER PK ALL VALUE DEFAULT
IOTIMER FOR ALL PACKS SET TO MCP DEFAULT
Example 3
IOTIMER PK 201 VALUE 80
IOTIMER FOR PK 201 SET TO 80 SECONDS
Example 4
IOTIMER PK 101 200 VALUE 40
IOTIMER FOR PK 101 200 SET TO 40 SECONDS
Example 5
IOTIMER PK SUBTYPE 54 VALUE 20
IOTIMER FOR PACKS OF SUBTYPE 54 SET TO 20 SECONDS
254 8600 0395-514

J (Job and Task Display)

The J (Job and Task Display) command lists active jobs, tasks, database stacks, and
freeze control libraries by job structure.
Syntax
<wild card>
<delim>
Use one of the following characters
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>

space character.
8600 0395-514 255

J NAME =pack=
"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 NAME <wild-card string>

Displays the job or all jobs with a name designated by the wild-card string, including
any that were suppressed. You can also use all other options with this form of the
command.
J MCSNAME = <MCS name>

J MCS = <MCS name>
Display only jobs or tasks originating from the specified MCS. The equal sign (=) is
optional.
J QUEUE
JQ
Display active jobs or tasks in all queues.
J QUEUE <queue number>

J Q <queue number>
Display only jobs or tasks from the specified queue.
J USER <usercode>
Displays only jobs or tasks running with the specified usercode.
256 8600 0395-514

Examples
Example 1
This example shows the response to a simple inquiry:
---Mix-Pri----------------- JOB ENTRIES ----------------------------

* 4591 50 (MACS) JOB BIND/CTLR36
E 4592 50 ..(MACS) *BINDER (MACS)SYSTEM/MCP/CTLR
4579 5 (KAY) JOB TEST/PORTFILE
4581 50 W ..(KAY) *ALGOL (KAY)OBJECT/TEST/PORTFILE
4473 80 Job *SYSTEM/CANDE
4538 50 ..(GEORGE) *OBJECT/ED
4507 50 S ..(NORM)OBJECT/PATCH/NED ON ODESY
4477 80 ..*CANDE/STACK01
4462 80 ..*SYSTEM/COMS
4468 50 ....MARC
4460 80 ..COMS/TANK
4459 80 ..COMS/INPUT
4457 80 Job NSP108/00
4452 50 Job *SYSTEM/PRINT/ROUTER
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).
first time.
The job or task number is shown in the Mix field.
The Pri field shows the priority of the job or task; the priority can be followed by a
waiting (W) or scheduled (S) flag.
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.
8600 0395-514 257


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=""
---Mix--Pri----------------JOB ENTRIES USER= ----------------

3936 50 Job *SYSTEM/PRINT/ROUTER ON DMSIITEST
3935 50 ...KEYEDIOII/STRUCTURES00
3937 50 ..*SYSTEM/PRINT/BNAROUTER ON DMSIITEST
3932 80 ..PRINT/WORKER
3904 75 ..SYSTEM/STATION/TRANSFER
3875 80 ..SYSTEM/DSS/ROUTER
3862 75 ..SYSTEM/NETWORK/SERVICES/MANAGER
3901 75 ....SYSTEM/LCF
3850 80 Job *SYSTEM/CANDE ON DMSIITEST
3889 80 ..*SYSTEM/COMS ON DMSIITEST
3893 50 ....MARC
3892 50 ....MARC
3887 80 ..COMS/TANK
3886 80 ..COMS/INPUT
3938 75 *REMOTESPO
258 8600 0395-514

LABEL (LABEL ODT)
LABEL (LABEL ODT)

The LABEL (LABEL ODT) command attaches a file name to the ODT from which you
enter the command. You cannot use this command at a remote ODT.
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:
You enter an ADM (Automatic Display Mode) command.

You close the program.
You enter the command CL SC <unit number>.
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
8600 0395-514 259

LABEL (LABEL ODT)

You can clear label assignment by using one of the following commands:
CL
RESTRICT
??MARC
A halt/load also clears label assignment.
260 8600 0395-514


The LB (Relabel Pack or Host Control Unit) command changes the family name, the
volume serial number, the capacity, or the name of the owner of a pack, but does
not affect any files on the pack. It can also change a host control (HC) unit from
scratch to labeled. However, changing the volume serial number of a member of a
multipack family is not permitted.
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.


THIS UNIT.
command again.
Syntax
<relabel pack>
<relabel host control unit>
8600 0395-514 261

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:
PKnn IS A SCRATCH PACK, PACK MUST BE RC'ED
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
<integer> MB and <integer> GB specify the capacity in megabytes or

gigabytes. The minimum value that can be specified is 64 megabytes. The
maximum value that can be specified is the original formatted capacity of the
disk.
The system converts the integer to a value, expressed in logical sectors, that
conforms to the MCP's internal implementation requirements. The result can be a
reduction to the requested value, by as much as 32 kilobytes.
LIKE PK <unit number> requests the same capacity that is in use for the pack
with the specified unit number.
FULL specifies the capacity the disk had when it was first initialized.
Notes:
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:
PK <number> RESIZED TO <number> SECTORS (<number> BYTES)
When the CAPACITY parameter is used, the only other parameter that can be
specified is OLDNAME. Any other combinations are rejected.
262 8600 0395-514

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
INVALID DISK TYPE
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.
NAME = <family name>

Assigns the family name to the pack. TAPE and DISKPACK are illegal values for
<family name> and are rejected. If no NAME option is specified, the original family
name is assigned by default. The NAME = <family name> option and the SR option
are mutually exclusive. The equal sign (=) is optional.
OLDNAME = <family name>

Specifies the family name of the pack to be changed or relabeled. If the command
does not specify OLDNAME, an RSVP message asks you to confirm that this is the
right pack. The waiting entry message is
<mix number> PK <pack number> is [<serial number>] <pack name>
<mix number> ACCEPT: OLDNAME = <pack name>
The reply must be
<mix number> AX OLDNAME = <pack name>
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:
PKnn INCORRECT OLDNAME ENTERED - RC/PG/LB NOT DONE
The OWNER identification is verified before the OLDNAME.
8600 0395-514 263

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:
PKnn [<number>] DUPLICATE SERIALNO
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:
LB SERIAL NO OF MULTI-PACK FAMILY IS DISALLOWED.
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.
LB HC <unit number> NAME = <hubname>

Labels the specified host control unit with the hubname. If the hub to which a host
control unit is being attached has a name, the hubname specified for the host control
unit must match it. If the hub does not have a name, the hubname specified for the
host control unit is also assigned in the HUBMAP as the name of the hub. If the hub
is not named and the hubname cannot be entered in the HUBMAP because space
limitations in the configuration description for this group have been exceeded, the LB
264 8600 0395-514

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:
LB PK66 NAME = JD, OWNER = 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 you enter a W (Waiting Mix Entries) command, or have previously requested

automatic display of current system status information with an ADM (Automatic
Display Mode) command, the system displays the waiting entries, as shown in this
example:

2273 50 17:02 JOB LB PK66
ACCEPT: OLDNAME = JOHN
If the reply is 2273DS, the job terminates.
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:
LB PK 3104 OLDNAME=DISK1 CAPACITY=5 GB
Example 3
This example shows how to change the NAME of all the disks in a family with one
command.
LB PK 80 OLDNAME = X, NAME = Y, FAMILY
Example 4
This example assigns a hubname of ISC03 to the host control unit with the number
123:
LB HC123 NAME ISC03
8600 0395-514 265


When you attempt to relabel a disk assigned to the spare disk pool for the Mirrored
Disk Pooling Facility (MDPF), the following RSVP message appears:
<mix number> PK<pack number> IS CURRENTLY DESIGNATED AS A SPARE FOR

MIRROR REPLACEMENT. ENTER OK TO CONTINUE WITH LABEL,
DS TO QUIT. OK WILL REMOVE THE PACK FROM THE SPARE DISK
POOL.
<mix number> REPLY: OK,DS
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:
<mix number> PK <pack number> IS A SPARE FOR MIRROR REPLACEMENT.

RC/LB/PG NOT DONE
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:

MIRROR REPLACEMENT, A FEATURE NOT ENABLED ON THIS
MACHINE. ENTER OK TO CONTINUE WITH LB, DS TO QUIT.
OK WILL REMOVE THE PACK FROM THE SPARE DISK POOL.
<mix number> REPLY: OK, DS
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:
<mix number> PK <pack number> IS A SPARE FOR MIRROR REPLACEMENT.

RC/LB/PG NOT DONE
If your system does not support MDPF, relabeling a disk removes the disk from the
spare disk pool and no message appears.
266 8600 0395-514

LC (Log Comment)
LC (Log Comment)
The LC (Log Comment) command enters a comment in the system log file
SYSTEM/SUMLOG.
Logged comments can be printed by running SYSTEM/LOGANALYZER and specifying

the OPERATOR option. Refer to the section on LOGANALYZER in the System Software
Utilities Manual for a more detailed description of SYSTEM/LOGANALYZER.
Syntax
Explanation
LC <text>
Enters the specified text in the SYSTEM/SUMLOG file.
Example
LC BEGIN COMPILER TESTS
COMMENT LOGGED
8600 0395-514 267

LG (Log for Mix Number)

The LG (Log for Mix Number) command controls selective logging of specified tasks.
This command is available only as part of Secure Access Control Module security-
enhancement software or if the Security Accountability Facility is available.

Syntax
Explanation
<mix number list> LG
Starts logging all events for the tasks in the specified mix number list.
<mix number list> LG <action>

Selectively logs events for the specified tasks, depending on the specified action
value. The <action> value is an integer in the range 0 through 15. Its significance is
as follows.
Value Significance
0 Stops all logging of events
1 Logs all successful actions
2 Logs all actions that are attempted but fail
4 Logs all security-relevant actions
8 Logs all actions that result in security violations
15 Logs all events (same as not specifying

<action>)
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.
268 8600 0395-514

Examples
Example 1
4872 LG
Example 2
3298,3367 LG 0
8600 0395-514 269

LH (Load HostIOP Systems)

The LH (Load Host) command loads firmware to a designated local IOP card or PORT
device of an IOP system. You can also use this command to specify how long a
device is to remain on its current firmware, with or without changing it immediately
See Considerations for Use for an explanation of default high-end memory (HEM)
firmware and for instructions on copying firmware files.
Syntax
<source>

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.
270 8600 0395-514

LH FCIOP FOR IOP <IOP number>

Loads default HEM firmware to the Fibre Channel IOP (FCIOP) card associated with
<IOP number> and to all attached C4FT (CS_Bus-4 feed through) card connections
to legacy channel adapter ports of a local FC-1 IOP. All IOPs served by the card must
be in the SAVED state. The specified IOP is initialized after the load.
LH IOP <IOP number> <source>

Loads the specified firmware to the FCIOP card for which <IOP number> is the local
IOP and to all attached C4FT cards if the IOP is an FC-1 IOP. The IOP must be in the
SAVED state. The specified IOP is initialized after the load. If .<cycle> is
specified, the MCP attempts to load firmware from the following files, depending on
the IOP type.
For an FC-1 IOP, the following files are loaded:
FIRMWARE/<mark2>_<cycle3>/FCIOP ON <family>
FIRMWARE/<mark2>_<cycle3>/C4FT ON <family>
For an FC-2 IOP, the following file is loaded:
FIRMWARE/<mark2>_<cycle3>/FC2IOP ON <family>
The <mark2> variable is a two-digit representation of and the <cycle3>

variable is a three-digit representation of <cycle>, both with leading zeros as
required.
LH PORT <port number>

Loads default HEM firmware to port <port number>. The port can be in the READY or
RESERVED state. The specified port is initialized, resetting the RESERVED state, if
necessary, after the load.
LH PORT <port number> <source>

Loads the specified firmware file to port <port number>. The port can be in the
READY or RESERVED state. If .<cycle> is specified, the MCP attempts to
load firmware from the following file:
FIRMWARE/<mark2>_<cycle3>/CA/<component> ON <family>
The <component> variable is either SCSI or FCHP, the <mark2> variable is a two-
digit representation of , 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.
8600 0395-514 271

LH FCIOP FOR IOP 1
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.
LH 1OP 2 TESTFW ON TESTPACK :TEMP
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.
LH PORT 31001 1.15 ON MYFAMILY
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.
LH PORT 31001 DIRECTORY MY/FIRMWARE ON THEFAMILY :TEMP
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.)
LH PORT 31001 :KEEP

HEM Firmware
On IOP systems, server control places a complete set of I/O firmware into high-end
memory (HEM) when every partition is started. The source of the firmware comes
either from
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.
272 8600 0395-514

Copying Firmware Files

Before you use the LH command to load firmware from a file, you must copy the
required firmware files to a disk family on your MCP system and rename them to
match the required command syntax.
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
These files must be renamed as follows to be compatible with the LH command:
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/_<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.
To use the <version ID> form of LH <source>, a somewhat different directory

structure is required. For example, the IOFIRMWARE share could be defined as
*FIRMWARE on the family HL, and the firmware files would be stored in subdirectory
0l_034 of this share.
8600 0395-514 273

LH (Load HostIOM Systems)

The LH (Load Host) command loads a controlware file to a disk pack drive controller
or downloads microcode to a Maintenance LAN Channel Adapter.
Syntax
Notes:
This command is not available on MCPvm systems.

The port option is available only on systems that support Maintenance LAN
Channel Adapters. Currently, these adapters are available only on NX5600,
NX5800, NX6820, and NX6830 systems.
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.
LH CTL <CTL number>

LH DLP <DLP number>
Loads the pack controlware file with the default title on the halt/load family to the
disk pack controller specified as the target CTL or DLP. If no such file exists on the
halt/load family, a waiting entry appears with a NO FILE RSVP message.
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.
Controller File Title

Type
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.
274 8600 0395-514

LH CTL <CTL number> <file title>

LH DLP <DLP number> <file title>
Loads the pack controlware file whose title is <file title> to the disk pack controller
specified as the target CTL or DLP.
The DLP or control must have been reserved previously.
LH PORT <CON2 port number>

Loads the CON2 CTL firmware from the default file to the Maintenance LAN Channel
Adapter flash PROM specified by the <CON2 port number>. The default CON2 CTL
firmware file title is
*SYSTEM/CON2/FIRMWARE ON <halt/load unit>
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
OK The traffic is stopped. Once the firmware load

process is complete, traffic to the outboard
devices resumes.
DS The system abandons the attempt to download

the firmware file, and traffic to the ODT and
Maintenance LAN devices continues without
interruption.
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.
LH PORT <CON2 port number> <file title>

Loads the CON2 CTL firmware to the Maintenance LAN Channel Adapter flash PROM
specified by the <CON2 port number>. The effect is the same as that of the LH PORT
<CON2 port number> command, except that the firmware is downloaded from the
file specified by <file title> instead of from the default file.
LH PORT <FC port number> <file title>

Loads the Host Bus Adapter (HBA) microcode for the Fibre Channel port from the
<file title>. A <file title> is required for this command.
8600 0395-514 275

Examples
Example 1
The following commands load the specified pack controlware files to the specified
CTL or DLP:
LH DLP 4007 CONTROLWARE/B9387 ON SYSPACK
DLP 4007 WILL BE LOADED
LH CTL 4007 CONTROLWARE/90387 ON SYSPACK
CTL 4007 WILL BE LOADED
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:
LH PORT 18101 SYSTEM/CON2/FIRMWARE/0322B ON HLUNIT451
As a result of the preceding command, a waiting entry with the following RSVP
message appears:
FIRMWARE LOAD WILL CAUSE LOSS OF CONSOLE SPOS - OK OR DS?
If you enter an OK response, the following message is displayed:
PORT 18101 WILL BE LOADED
276 8600 0395-514

LIBS (Library Task Entries)

The LIBS (Library Task Entries) command lists all frozen libraries, including both
server libraries and connection libraries.
Syntax
<wild card>
<delim>
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>

space character.
8600 0395-514 277

LIBS NAME =pack=
"pack":
LIBS NAME LIT^=pack=^
Explanation
LIBS
LIBRARIES
Display all unsuppressed frozen library stack entries.
LIBS ALL
Displays all frozen library stack entries, including suppressed ones.
LIBS NAME <wild-card string>

Displays one or all library names that contain the specified wild-card string, including
any that were suppressed.
LIBS MCSNAME = <MCS name>

LIBS MCS = <MCS name>
Display only libraries initiated from the specified MCS.
LIBS Q
Shows all libraries that were originally initiated from a job through a job queue.
LIBS Q <job queue number>

Shows all libraries that were originally initiated from a job through the specified job
queue number.
LIBS USER <usercode>

Displays only libraries running with the specified usercode.
Examples
Example 1
This example shows output from the LIBS command:
LIBS
---Mix--Frz---Shr---Usr--- 10 FROZEN LIBRARIES ---------------------

* 1908 Temp All 1 SL *SYSTEM/TADSSUPPORT ON PACK
* 1626 Perm Run 2 SL *SYSTEM/COMS/UTILITY/FORMATS ON PACK
* 1595 Perm Priv 1 Job *SYSTEM/SCREENDESIGN/INTERFACE ON PACK
* 1593 Temp All 2 Job *SYSTEM/SCREENDESIGN/FORMATS ON PACK
278 8600 0395-514

* 1921 Perm All 1 SL Job *SYSTEM/SCREENDESIGN/MANAGER ON PACK

1490 Temp All 1 Job *SYSTEM/MARC/AGENDA/TDXXX
1482 Perm All 8 SL Job *SYSTEM/COMS ON PACK
1493 Conn Priv Job *SYSTEM/NXSERVICES/SERVER
1489 Perm All 2 SL *SYSTEM/MARC/COMMANDER
1485 Ctrl All 5 (MACS)TEST/FREEZE/CONTROL
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
All Shared by All
Run Shared by Run Unit
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=
---Mix--Frz---Shr---Usr--------- 5 FROZEN LIBRARIES (ALL) =SERV=----

19287 Temp All 2 SL Job *SYSTEM/TCPHOSTSERVICES
19243 Ctrl All 0 Job *SYSTEM/MCPSERVER/SUPPORT
19222 Ctrl All 1 SL Job *SYSTEM/NXSERVICES/NAMESERVER
19170 Ctrl All 0 SL Job *SYSTEM/NXSERVICES/ADMINCENTER
19144 Perm All 1 SL Job *SYSTEM/NXSERVICES/CREDENTIALSUPPORT
8600 0395-514 279

LIBTRACE (Library Trace)

The LIBTRACE (Library Trace) command sets a trace for all libraries. This command
is valid only on diagnostic versions of the MCP. A number of options can be set or
reset. The option list contains three categories of options: functional, modifier, and
destination.
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.
Option Category Purpose When Set
CLDIRECTORIES Functional To trace connection library directories.

(*)
DELINKING (*) Functional To trace delinking code.
DISPLAY Destination To display trace output as system messages.
LINENUMBERS (*) Modifier To include line numbers in trace output.
LINKING (*) Functional To trace linking code.
LOCKING (*) Functional To trace locking code.
LOGIC (*) Modifier To trace decision logic.
PROCEDURES (*) Modifier To trace MCP procedure calls on entry and

exit.
STANDARD or STD Not To set or reset the standard options.

applicable
280 8600 0395-514

Option Category Purpose When Set
SUPER Modifier To trace an extra level of detail.
TEMPLATES (*) Functional To trace library templates.
TEMPORARY or Functional To trace temporary trapping code.

TEMP
TOLOG (*) Destination To write trace output to SYSTEM/SUMLOG,

job summary, or both. You can analyze
entries in the SYSTEM/SUMLOG by using
LOGANALYZER with the DIAG (LIB) option.
USERPROCS (*) Functional To trace user procedures.
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 SET ALL

LIBTRACE ALL
Set all functional and modifier options and the TOLOG destination option.
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.
8600 0395-514 281

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.
LIBTRACE + LINKING LOCKING TOLOG LOGIC
LIBTRACE OPTIONS SET

- Linking Locking With: Logic To: ToLog
LIBTRACE OPTIONS RESET
- Delinking UsrProcs Templates Headers CLDirectories Temporary
Attributes With: Linenumbers Procedures Superset To: Display ToDisk
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.
LIBTRACE - DELINKING, TEMP, LINENUMBERS

Example 4
Based on Example 3, this example shows an inquiry concerning options that have
been reset and its response.

282 8600 0395-514

Example 5
This example shows a command that resets all options.
LIBTRACE NONE

- NONE To: NONE
- Linking Delinking UserProcs Templates Headers CLDirectories
Temporary Attributes With: Linenumbers Procedures Logic Superset
To: Display ToDisk
Example 6
This example shows the command and response for the standard set of options.
LIBTRACE SET STANDARD

- Linking Delinking UserProcs Templates Headers CLDirectories
locking Attributes
With: Linenumbers Procedures Logic To: ToLog
LIBRARY OPTIONS RESET
- Temporary With: Superset To: Display ToDisk
8600 0395-514 283

LICENSESTATUS
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
Master keys: MASTERKEY-YYYYMMDD-HHMMSS

SCN: S0199999 (Valid MCN)
MASTERKEY-YYYYMMDD-HHMMSS
SCN: S0299999 (Invalid MCN, MCN 123456789)
Library is running, mix number is nnnnn
Example 2
LS RESTART
Restarting LicenseSupport Library
284 8600 0395-514

LJ (Log to Job)
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.
The text specified in the LJ command appears in the JOBSUMMARY printout.
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:
3335 LJ GREAT JOB
8600 0395-514 285

LOADMICROCODE (Load MicrocodeIOM Systems)
LOADMICROCODE (Load MicrocodeIOM

Systems)
The LOADMICROCODE (Load Microcode) command directs the console to load a
specific microcode version into all central processing modules (CPMs) or I/O modules
(IOMs) in the partition.
Note: This command is not supported on MCPvm servers.
Syntax
<version>
The value for is a 2-digit integer.
The value for <cycle> is a 3-digit integer.
Explanation
LOADMICROCODE CPM .<cycle>
LOADMICROCODE IOM .<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.
LOADMICROCODE CPM 08.012
MICROCODE LOAD REQUEST COMPLETED FOR CPM4

Acknowledging the RSVP Message
When you use the LOADMICROCODE command, you must acknowledge the following
RSVP message:
SYSTEM MAY PAUSE WHILE LOADING MICROCODE (OK OR DS)
286 8600 0395-514

LOADMICROCODE (Load MicrocodeIOM Systems)
Scheduling the Activity

You should use this command during a low workload period to minimize system
unavailability and elapsed time. Verify that the microcode being requested is
installed on the console. The system will pause if the requestor is IOM, or if the
requestor type is CPM and only one CPM is in use. No pause is required to load CPM
microcode on a multiprocessor system.
Error Conditions
If the console determines that the specified microcode version is not installed, the
system displays the following error message:
CPM <number>: SPECIFIED MICROCODE IS NOT INSTALLED ON THE CONSOLE
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:
MICROCODE COMPATIBILITY CANNOT BE DETERMINED FOR CPM 5
If microcode fails to load or if a requestor fails to initialize, the requestor remains

logically saved. Processing continues if there is another requestor of the same type.
The system displays an error message similar to the following:
MICROCODE LOAD REQUEST FAILED FOR IOM 1
8600 0395-514 287

LOG (Analyze Log)
LOG (Analyze Log)

The LOG (Analyze Log) command starts the utility SYSTEM/LOGANALYZER.
Refer to the information on LOGANALYZER in the System Software Utilities Manual

for a detailed description of SYSTEM/LOGANALYZER and its parameters.
Syntax
Explanation
LOG
Performs a complete analysis of the current system log if no log parameters are
specified.
LOG <log parameters>

Starts SYSTEM/LOGANALYZER with the specified parameters.
Examples
LOG 1700 BOT EOT MAINT MSG
LOG MAINT MT 48
LOG JOB 4811
288 8600 0395-514

LOGGING (Logging Options)

The LOGGING (Logging Options) command displays or changes the system logging
options, which suppress the logging of certain log records. This command has no
effect on any log entries generated during a halt/load of the system.
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.
Although the LOGGING command is completely functional, it is designed for

programmatic interface rather than as an operator interface. The intended operator
interface is through Menu-Assisted Resource Control (MARC) menus.
For more information about logging options, refer to the System Log Programming
Reference Manual.
Syntax
<major>
<minor>
<log option list>
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.
8600 0395-514 289

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 <major> <log option list>

Sets the logging options for all minor types under the specified major type as
specified in the log option list. After setting the options, the system displays them.
For further information and restrictions on logging, refer to the Security
Administration Guide.
LOGGING <major>,<minor> <log option list>

Sets the logging option for the specified minor type under the major type as
specified in the log option list. After setting the options, the system displays them.
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.
290 8600 0395-514

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,7 All;4,8 None;
Logging 4,9 None;4,10 All;
Logging 4,11 All
No Minor Type 7,5. Logging 7 All;
8600 0395-514 291

LP (Lock Program)
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.
<mix number list> LP

Removes the LP restriction from the processes in the specified mix number list.
Examples
Example 1
4872 LP
4872 PROGRAM LOCKED.
Example 1
3298 LP
3298 NOT LOCKED.
292 8600 0395-514

MAX (Maximums)
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.
MAX MESSAGES <number>

MAX MESSAGES = <number>
MAX MSG <number>
MAX MSG=<number>
Specify the number of messages to be stored by the system for retrieval with the
MSG FULL system command.
Note: The values of the variables apply to both network and non-network
messages.
MAX COMPLETED <number>

MAX COMPLETED = <number>
Specify the number of completed entries that are to be stored by the system for
retrieval with the COMPLETED FULL system command.
MAX SESSION <number>

MAX SESSION = <number>
Specify the maximum session number that is allocated by the system.
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
8600 0395-514 293

MAX (Maximums)
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.
MAX MIX <number>

MAX MIX = <number>
Specify the maximum mix number that is allocated by the system. This maximum is
constrained by the currently effective value of the MORETASKS system option. (Note
that changes to the MORETASKS value do not take effect until the next halt/load.)
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.
MAX STACK <number>

MAX STACK = <number>
Specify the maximum stack number that is allocated by the system. This maximum
is constrained by the currently effective value of the MORETASKS system option.
(Note that changes to the MORETASKS value do not take effect until the next
halt/load.)
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.
294 8600 0395-514

MAX (Maximums)
Examples
Example :
This example displays the current settings.
MAX
Maximum Settings are as follows

Messages Saved : 100
Completed Entries : 500
Session Number : 9999 (65535 supported)
Stack Number : 4095 ( 4095 supported)
Mix Number : 9999 ( 9999 supported)
MoreTasks State : INACTIVE
Example 2
This example updates the number of messages to be saved by the system.
MAX MESSAGES 120
Maximum Settings are as follows:

Stack Number : 4095 (16383 supported)
Mix Number : 9999 (65535 supported)
MoreTasks State : INACTIVE
Example 3
This example updates the number of completed messages to be stored by the
system.
MAX COMPLETED 400

Stack Number : 16383 (16383 supported)
Mix Number : 32000 (65535 supported)
MoreTasks State : ACTIVE
8600 0395-514 295

MAX (Maximums)
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.
MAX MIX=32000 STACK=16383

Stack Number : 16383 ( 4095 supported)
Mix Number : 32000 ( 9999 supported)
MoreTasks State : ACTIVE
296 8600 0395-514

MCS (Message Control System)

The MCS (Message Control System) command displays the summary and status
information about each of the message control systems (MCSs) that are supported
by the system at the time you issue the command. You define an MCS to the system
by declaring it in the current DATACOMINFO file, as specified by the ID (Initialize
Data Comm) command.
Syntax
Explanation
The MCS command provides the following summary and status information.
Display Meaning
MIX Mix number of the MCS if active.
STATUS The MCS can be in one of four states:

ACTIVE: The MCS is running.
INACTIVE: The MCS is not running. The previous
execution of the MCS either terminated normally or
an attempt to execute the MCS has not been made.
DSED: The MCS has been terminated abnormally.
REQUIRED: An unsuccessful attempt was made to
initiate the MCS. The MCS could not be initiated
because it had previously terminated abnormally or
the code file of the MCS was not found. This failed
attempt at initiating the MCS causes an MCS
REQUIRED message to be displayed at the ODT.
TASKS The number of currently active tasks that were initiated

from the MCS.
STATIONS The number of logical stations owned by the MCS.
NUM The number of the MCS.
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.
8600 0395-514 297

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
298 8600 0395-514

MDT (Memory Dump Type)

The MDT (Memory Dump Type) command either sets or interrogates the current
system-wide memory dump type options. The MDT command enables you to do the
following:
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.
Syntax for MDT Command
8600 0395-514 299

Syntax for MDT SHOW Command
<suppressed dump list>
<dump number list>
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.
<autosuppress entry list>
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.
300 8600 0395-514

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.
MDT AUTOSUPPRESS <autosuppress entry>

MDT AUTOSUPPRESS <autosuppress entry> <autosuppress entry>
Sets the AUTOSUPPRESS flag for the specified autosuppress entry or entries. An
autosuppress entry is a record number in the dump history file. If an entry is marked
for automatic suppression using this syntax, and the same dump occurs again, the
system logs the new dump request but suppresses the actual dumping of memory.
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 <autosuppress entry>

MDT AUTOSUPPRESS <autosuppress entry> <autosuppress entry>
Reset the AUTOSUPPRESS flag for the specified autosuppress entry or entries. If any
of the corresponding dumps occurs again, the system performs a new memory
dump.
MDT AUTOSUPPRESS ALL

Sets the AUTOSUPPRESS flag for each entry in the dump history file.
MDT AUTOSUPPRESS ALL

Resets the AUTOSUPPRESS flag for all dump entries in the dump history file.
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 AUTOSUPPRESS OVERRIDE <autosuppress entry>

MDT AUTOSUPPRESS OVERRIDE <autosuppress entry> <autosuppress entry>
Sets the OVERRIDE flag for the specified autosuppress entry or entries. If a
particular dump occurs again, the OVERRIDE option causes the system to perform a
memory dump and then reset the OVERRIDE flag for that dump. If the same dump
occurs again after that, the system logs the dump request but does not dump
memory.
8600 0395-514 301

MDT AUTOSUPPRESS OVERRIDE <autosuppress entry>

MDT AUTOSUPPRESS OVERRIDE <autosuppress entry> <autosuppress entry>
Resets the OVERRIDE flag for the specified autosuppress entry or entries.
MDT AUTOSUPPRESS OVERRIDE ALL

Sets the OVERRIDE flag for each of the autosuppress entries in the dump history file.
MDT AUTOSUPPRESS OVERRIDE ALL

Resets the OVERRIDE flag for each of the autosuppress entries in the dump history
file.
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 <dump history file name>

Creates a dump history file name with the name that you designate. This file can be
copied to tape for backup while serving as the history file.
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.
302 8600 0395-514

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 NONCOMPRESSED (NONC, NONCOMP, NONCOMPRESS)

Specifies that data compression is to be postponed until the memory dump has
finished by writing the memory dump to disk without compression.
MDT NONCOMPRESS
Resets the NONCOMPRESS option.
MDT SHOW
Is synonymous to the MDT SHOW ALL request.
MDT SHOW ALL

Displays a list of memory dumps. The list includes the unique dump number, the
reason, the action (for example, fatal or nonfatal), the type (for example, complete),
and a description.
MDT SHOW NONFATAL

Displays a list of memory dumps that are nonfatal.
MDT SHOW <dump number>

MDT SHOW <dump number>, <dump number>
MDT SHOW <dump number> - <dump number>
Displays a list of memory dumps. The list includes the dumps with the requested
dump numbers.
MDT SHOW OPERATOR

MDT SHOW SETSTATUS
Displays the selected memory dump, including the reason, the action, the type, and
the description.
MDT SHOW HISTORY

MDT SHOW HISTORY <dump number list>
Displays the current list of dump entries in the history file. If a <dump number list>
is specified, only the requested dumps are displayed.
MDT SHOW SUPPRESS

Displays the current list of manually suppressed dumps.
8600 0395-514 303

MDT SHOW AUTOSUPPRESS

MDT SHOW AUTOSUPPRESS <autosuppress entry list>
Displays the currently selected candidates for automatic suppression. The
<autosuppress entry list> restricts the display to the requested entries.
MDT SHOW AUTOSUPPRESS OVERRIDE

MDT SHOW AUTOSUPPRESS OVERRIDE <autosuppress entry list>
Displays the currently selected candidates for automatic suppression that also have
the OVERRIDE flag set. The <autosuppress entry list> restricts the display to the
requested entries.
MDT SUPPRESS <dump number list>

Adds the dump numbers to the list of suppressed dumps.
MDT SUPPRESS <dump number list>

Deletes the dump numbers from the list of suppressed dumps.
MDT SUPPRESS NONFATAL

Sets the option to suppress all nonfatal memory dumps.
MDT SUPPRESS OPERATOR

Sets the option to suppress all operator requested memory dumps. Primitive dumps
using ??DUMP or ??MEMDP are to be taken.
MDT SUPPRESS SETSTATUS

Suppresses all dumps that use the SETSTATUS intrinsic.
MDT SUPPRESS ALL

Sets the option to suppress all memory dumps. Primitive dumps using ??DUMP or
??MEMDP are to be taken.
MDT SUPPRESS ALL

Resets the option to suppress all memory dumps.
Examples
Example 1
This example displays the memory dump options.
MDT
----------------------------- MEMORY DUMP OPTIONS --------------
The settings for Memory Dump options are as follows:
The dump type is DEFAULT

The NONCOMPRESSED option is RESET
The AUTOSUPPRESS option is RESET
304 8600 0395-514

The SUPPRESS ALL option is RESET

The SUPPRESS NONFATAL option is RESET
The AUTOSAVE option is RESET
The AUTOUNLOAD option is RESET
The dump HISTORY file is *DUMP/HISTORY ON DISK

There is 6 dumps in the HISTORY file
There are no dumps marked for automatic suppression
There are no dumps marked to override automatic suppression
There are no dumps manually suppressed
Example 2
This example suppresses all SETSTATUS dumps.
MDT SUPPRESS SETSTATUS
-------------------------MEMORY DUMP OPTIONS---------------------
The settings for Memory Dump options have been changed as follows:
DUMP 8000003 SUPPRESSED
Example 3
This example shows suppressed dumps.
MDT SHOW SUPPRESS
--- Dump Number -- Dump Reason --------- Dump Action & Type ----
8000003 SETSTATUS REQUEST By Request, By Request

Memory dump requested from a program using the SETSTATUS
intrinsic - Type = Miscellaneous, Subtype = DUMP. The action
and type for the dump request is determined by the parameters
to the SETSTATUS call
Example 4
This example shows the current dump history.
MDT SHOW HISTORY
----------------------- MEMORY DUMP HISTORY-----------------------
The dump HISTORY file is *SYSTEM/DUMPHIST ON DN
Autosuppress Entry #: 263

--------------------
Autosuppress Flag: Off
Autosuppress Count: 62, Last Suppressed: 6/19/1995 @ 9:34:30
Dump 8680002 by "LOST EVENT(S) ", Nonfatal, Partial
8600 0395-514 305

Stack History : 1007:0312:3, 10D2:1542:5, 10D2:0A76:1

1048:078A:4, 1048:079A:0, 1048:0905:1
--- Dump Timestamp ------ MCP Level ------ Result ------------
06/01/1995 @ 14:40:20 42.320.1637 Completed to Disk
Example 5
This example shows the history for SETSTATUS dumps.
MDT SHOW HISTORY SETSTATUS
----------------------- MEMORY DUMP HISTORY-----------------------
The dump HISTORY file is *SYSTEM/DUMPHIST ON DN
Autosuppress Entry #: 23
--------------------
Autosuppress Flag: Off
Autosuppress Count: 3, Last Suppressed: 12/13/1995 @ 11:28
Dump 8000003 by "SETSTATUS DUMP # 1", Nonfatal, Partial
Stack History : 178B:047A:0 1781:0FB3:5 1781:0004:0
--- Dump Timestamp ------ MCP Level ------ Result ------------

Example 6
This example marks dump entry 23 for automatic suppression.
MDT AUTOSUPPRESS 23
----------------------MEMORY DUMP OPTIONS-------------------------
The settings for Memory Dump options have been changed as follows:
Autosuppress Entry 23 marked for autosuppression

Changing Memory Dump Types
The MDT command is designed to provide you with the ability to set a system-wide
memory dump type to override any dump call that the system initiates with more,
not less, information. For example, if the MDT value is set to COMPLETE, any type of
memory dump calls that the system initiates are overridden. A complete memory
dump is the most comprehensive; it is a snapshot of the entire memory on the
system. The following paragraphs describe various memory dump types.
306 8600 0395-514

Using ALLINUSE Memory Dump

If the MDT value is set to ALLINUSE, only partial memory dump calls are overridden.
ALLINUSE memory dumps comprise all areas of memory that are in use, have been
touched, and have been made present.
Using Partial Memory Dumps

Partial memory dumps comprise any area owned by the system, the stack that has
initiated the memory dump, and any stack linked to the stack that has initiated the
memory dump.
Using DEFAULT Memory Dumps

If the MDT value is set to DEFAULT, any type of dump that the system generates
takes priority. The MCP dump call is not affected.
Using the NONCOMPRESSED Option

The MDT NONCOMPRESSED option affects only COMPLETE memory dumps that are
written to a disk. A COMPLETE memory dump requires more space in the dump disk
file than a compressed dump because the complete memory image is written to the
dump disk file, including tags. When the dump finishes, the DUMPDISKMASTER
utility compresses the memory image that resides on the disk when uploading the
dump.
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.
Performance Improvements When Using the NONCOMPRESSED Option

When there are multiple units in the DN family, concurrent I/Os are performed to
improve performance. However, because memory dumps are performed using a
primitive I/O interface, there is a limit to the number of I/Os that can be performed
at one time. For uncompressed dumps, the dump process recognizes that additional
I/Os can be performed by using slots normally reserved for ODT units. To take
advantage of this schema, it is recommended that ODT units be freed from the
partition if they do not exist. For more information, refer to the Free (Free Resource)
command for IOM systems and the DOWN (Down Resource) command for IOP
systems.
Considerations for Using Dump Suppression

The following two dump suppression options are available to selectively suppress
individual dump occurrences:
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
8600 0395-514 307

previously reported, but it also allows suppression of a dump that occurs under many
different circumstances for the same problem.
Using Automatic Suppression

Automatic suppression is based on matching a new dump request with a previous
one and comparing additional information concerning the memory dump. It
suppresses only memory dumps when the particular dump matches a previously
experienced dump request. This process allows another dump to the same dump
number, but for a different actual problem to be collected while still suppressing
another dump for a problem that was already reported.
Using the AUTOSUPPRESS Option

The MDT AUTOSUPPRESS option requests that all dumps in the dump history file be
considered for suppression by matching. MDT AUTOSUPPRESS resets the option,
and only individual entries in the history file previously marked are to be considered
for autosuppression.
Using the SETSTATUS Interface

All programmatically requested memory dumps use the MCP SETSTATUS interface,
which is currently assigned a single dump number. This practice allows you to
manually suppress all external dump requests. To suppress all program requested
memory dumps, you can use the MDT SUPPRESS SETSTATUS command. Automatic
suppression is also available for entries in the dump history for the SETSTATUS
dump number. This automatic suppression is based on the other parameters to the
dump request, such as the dump reason.
Using Operator Requested Dumps

Automatic suppression is not available for operator requested dumps, and these
dumps are not added to the dump history file. To suppress all operator requested
memory dumps, use the SUPPRESS OPERATOR variation of the MDT command. This
suppression applies to all requests made with the system command DUMP (Dump
Memory), MCS requests, and DCKEYINs. You can still request dumps at the ODT by
using the primitive forms of the command such as ??DUMP and ??MEMDP.
Using NODUMP (Option 13)

The system option NODUMP continues to override all memory dump requests with
the exception of primitive dump requests entered at the ODT. The setting or
resetting of the NODUMP option does not affect entries in the dump suppression list.
In contrast, setting or resetting the MDT SUPPRESS ALL option causes all entries to
be removed from the dump suppression list.
Using the AUTOSAVE Option

The MDT AUTOSAVE option causes memory dumps to disk to be automatically
unloaded and formatted as a DUMPANALYZER SAVEDUMP. The SAVEDUMP file is
created by DUMPDISKMASTER by linking to DUMPANALYZER. In order to link
successfully, you need to establish the system library (SL) definitions for
DPASUPPORT and SDASUPPORT during normal system installation.
308 8600 0395-514

Using AUTOSAVE to create a SAVEDUMP file requires additional resources at unload

time. The unloaded SAVEDUMP file can be submitted to Unisys through a UCF
without any further processing or corresponding resource utilization.
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 the AUTOSAVE option is set, DUMPDISKMASTER ignores the AUTOUNLOAD

option.
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.
Using the AUTOUNLOAD Option

The MDT AUTOUNLOAD option instructs DUMPDISKMASTER to automatically unload a
memory dump from a dumpdisk file without requiring operator input. When the DL
DPFILES family is specified, the AUTOSAVE option has the same effect on
DUMPDISKMASTER as the AUTORUNNING option; the dump is automatically
unloaded with a DP file name. For more information, refer to AUTORUNNING (option
15 of the OP (Options) command) and the DL DPFILES command. When the DL
DPFILES family is not specified, DUMPDISKMASTER unloads the dump to a TAPE file.
In either case, the unloaded file is in the raw memory dump format, not the
SAVEDUMP format that results from setting the AUTOSAVE option.
The AUTOUNLOAD option is ignored when the AUTOSAVE option is set.
Using Dump History Files

To enable automatic dump suppression, you must create a dump history file with the
HISTORY option of the MDT command. This option enables you to specify a history
file name and location. If you use the command to specify an already existing file
and if the file is a valid dump history file, it becomes the new active dump history
file. This practice permits saving multiple dump history files for different MCPs. Dump
history files have the same restrictions as dumpdisk files. For details of these
restrictions, refer to the DN (Dump Name) command.
When you use the MDT HISTORY option, the system ignores the history file and
disables automatic dump suppression.
8600 0395-514 309

MEMORYCEILING (Set Memory Ceiling)

The MEMORYCEILING (Set Memory Ceiling) command enables you to display or set a
memory ceiling. The specified value is a memory address that represents the top
limit of memory as viewed by memory management software. When you declare a
memory ceiling, memory above the specified value is reserved by the MCP and
displayed as NOT IN USE by the MM (Memory Module) and SC (System
Configuration) commands. Note that the MEMORYCEILING command does not alter
the amount of memory owned by the partition.
The MEMORYCEILING command is valid on machines that support capacity on

demand (COD). It is primarily intended for systems that require memory licensing.
The MEMORYCEILING command is not supported on Virtual MCP (MCPvm) systems.
Syntax
Explanation
MEMORYCEILING
Displays the current and maximum memory ceiling values and indicates whether the
fast memory dump feature is enabled.
MEMORYCEILING <number> MWORDS

Establishes or resizes memory ceiling to the specified size.
MEMORYCEILING <number> MWORDS DEFER

Establishes or resizes memory ceiling on the next halt/load.
MEMORYCEILING
Removes the current memory ceiling.
MEMORYCEILING DEFER
Removes the current memory ceiling on the next halt/load.
310 8600 0395-514

Example
This command queries the memory ceiling size:
MEMORYCEILING
MEMORY CEILING ADDRESS
Current address : 1024 MWords

Next halt/load : 1024 MWords
Licensed maximum : 1536 MWords
Partition maximum : 1924 Mwords
Fast dump maximum : 1024 Mwords
Fast memory dump is enabled.

Licensed Memory Size
On systems that require memory licensing, the licensed memory size for a partition
is the system-wide limit minus the sum of all active partition memory sizes. During
initialization, the MCP enforces a memory ceiling if the partition memory size exceeds
the licensed memory size.
On systems that do not require memory licensing, the licensed memory size is
simply the partition memory size.
Reducing Memory Ceiling

A request to establish a memory ceiling or to reduce an existing memory ceiling can
fail depending on the requested size and current memory usage. In this case, the
MCP reduces the memory ceiling as low as it can until an immovable area prevents
further reduction. The requested size is preserved for the next halt/load.
Increasing Memory Ceiling

A request to remove or increase a memory ceiling succeeds as long as the requested
size does not exceed the maximum licensed size.
Memory Disk or Disk Cache Considerations

If memory disk or disk cache is declared, it resides below the requested memory
ceiling value.
Fast Memory Dumps

The area above a memory ceiling can be available for a fast memory dump if the
area size is large enough to capture a dump image. Fast memory dump is a feature
that minimizes down time when the user or MCP requests a memory dump. You
might require a key to enable this feature. Note that the MEMORYCEILING response
indicates the maximum memory ceiling value that enables the use of fast memory
dump.
8600 0395-514 311

MIRROR (Mirror Disk)

The MIRROR (Mirror Disk) command controls the use of disk mirroring on the
system. The command initiates an independent runner named MIRROR_CREATE. For
a description of disk mirroring, refer to the System Operations Guide.
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
312 8600 0395-514

<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.
This command is particularly useful when a member of a mirrored set is experiencing

repeated, recoverable errors that degrade the I/O throughput to that set.
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.
8600 0395-514 313

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
MIRROR ACTION NOT DONE (NOT AN ONLINE MIRRORED DISK).
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:
MIRROR ACTION NOT DONE (LAST ONLINE MIRROR IN SET).
MIRROR AUDIT OFFLINE COPIES OF PK <unit number>

Tells the system to bring the mirrored set online and audit its unavailable member or
members.
MIRROR AUDIT OFFLINE COPIES OF ALL SETS

Provides a shorter version of the preceding command. The system is instructed to
bring online all mirrored sets waiting to be brought online because of unavailable
members.
MIRROR CERTIFY PK <unit number>

Verifies that the data contained in each online member of a mirrored set is identical.
Every sector, except those that are identified as defective in the BADDISK file, is
read and compared for each online member. Any data discrepancy is reported on the
ODT. A report file is generated that logs any data discrepancies as well as the
success of the certify process. When mirror certification completes, a certification
timestamp is written on the disk label. The mirror certify timestamp for each certified
member of the set is displayed as part of the OL (Display Label and Paths)
command.
MIRROR CERTIFY generates a report for any data discrepancies encountered. If a

data mismatch occurs on an unused sector, that sector is identified as AVAILABLE
space. If the data mismatch occurs on an area used by the MCP, that sector is
identified as IN USE BY MCP. Otherwise, the file name that contains the bad sector is
reported. A block of consecutive mismatched sectors is reported as a single
mismatch. The length of the mismatched block is reported.
MIRROR CREATE PK <unit number> FROM PK <unit number>

Creates a mirror copy of an existing pack. The source and destination packs must be
identically formatted. For example, both packs could be 207 interlaced packs, or both
could be 659 sequential packs. The existing pack can be a member of a mirrored set.
314 8600 0395-514

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.
MIRROR IGNORE PK <unit number>

If an attempt is made to bring a mirrored set online and one or more of its members
are unavailable, this command causes the system to treat those members as if it had
not yet encountered them. Do not confuse this command with the CLOSE (Close
Pack) command. Unlike CLOSE, this command does not necessarily leave the set in a
state in which all members are known to be identical, with their labels showing a
closed state. Rather, it returns the packs to whatever state they were in before the
attempt to bring them online. Members that have been ignored can be made ready
later with the RY (Ready) command if you wish to bring up the set.
MIRROR IMPORT PK <unit number>

Once you have marked all of the family members to be imported, use the
MIRROR IMPORT command to assign unique identification to the family to which the
PK <unit number> belongs.
Importing a MIRROR SNAPSHOT COPY

When you are ready to separate the snapshot candidate from its original, any
application software that is performing write operations to the mirrored sets
representing the family must be quiesced by the user. The MIRROR IMPORT
command is then entered to separate the snapshot candidate from its original and
provide it with unique serial numbers and optional family name.
MIRROR IMPORT PK <unit number> NAME = <new family name>

The following message is displayed when a MIRROR IMPORT command is issued. Its
purpose is to verify that the user has quiesced all I/O to the family being imported:
PK<unit number> MIRROR IMPORT REQUESTED. OPERATOR IS RESPONSIBLE FOR

QUIESCING I/O TO THE FAMILY TO ENSURE DATA CONSISTENCY. REPLY 'OK' WHEN
READY TO PROCEED. 'DS' TO ABORT.
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:
SAN MIRROR DISK MANAGER KEY NOT INSTALLED
A check is made to verify that all family members are present. If not, the
operation is aborted and the following message is displayed:
8600 0395-514 315

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
PK <unit number> MIRROR IMPORT COMMAND INITIATED. I/O ACTIVITY CAN BE RESUMED.
Upon successful completion of the command, the following message is displayed:
FAMILY CONTAINING PK <unit number> SUCCESSFULLY IMPORTED
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:
PK<unit number> IMPORT OPERATION FAILED. THE FAILING MEMBER

HAS BEEN RELEASED. RECREATE A MIRROR TO REPLACE THE FAILING
MIRROR, MIRROR MARK THE REPLACEMENT, AND REPEAT THE MIRROR
IMPORT PROCESS.
Importing a BCV Device

MIRROR IMPORT PK <unit number> NAME=<familyname>
This command checks the following:
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:
HOST COMPONENT FOR EMC TIMEFINDER KEY NOT INSTALLED
316 8600 0395-514

PK<unit number> UNIT NOT AVAILABLE. MIRROR IMPORT ABORTED.
A check is made to verify that all family members have been marked. If not, the
PK<unmarked unit number> UNIT NOT MARKED. MIRROR IMPORT OF PK<unit number>
ABORTED.
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.
FAMILY CONTAINING PK<unit number> SUCCESSFULLY IMPORTED
MIRROR IMPORT PK <unit number> RETAIN

This option of the MIRROR IMPORT command enables a user to bring a BCV device
online while retaining the original family name and serial number. When the RETAIN
option is used, the MIRROR MARK command does not have to be used because the
serial number remains unchanged.
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.
In this command, PK<unit number> specifies the member of the family to be

retained. This command checks the following:
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:
PK <unit number> UNIT NOT AVAILABLE. MIRROR IMPORT ABORTED.
A check is made to verify that no family member has been marked. If so, the
PK <unit number> FAMILY MEMBER MARKED. MIRROR IMPORT ABORTED.
8600 0395-514 317

FAMILY CONTAINING PK <unit number> SUCCESSFULLY IMPORTED
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.
Marking a MIRROR SNAPSHOT COPY

MIRROR MARK + PK <unit number> SERIAL = <serial number>
Once a copy has been made for all members of a family, the MIRROR MARK
command enables the user to specify the serial number to be used for the snapshot
candidate when it is subsequently imported. This option also permits the operator to
unmark a device and to display the MARK status of a family.
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.
The serial number must be unique. If it is not, the operation is aborted.
The unit must be eligible and a member of a mirrored set to be marked as a

snapshot candidate.
If a member that has been marked in the mirror set already exists , the
operation is aborted.
If the unit specified to be marked is not available, the operation is aborted.
MIRROR MARK PK <unit number>

Unmarks a snapshot candidate. The unmarked unit is no longer a candidate to be
imported.
318 8600 0395-514


The query form of the MIRROR MARK command displays the mark status of all the
family members to which the PK <unit number> belongs. This status consists of the
unit number, assigned serial number, family name, family index, and the pending
serial numbers.
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-------------------
100 [045678] #1 PERIPH MARKED (PENDING [12345])

150 [023456] #2 PERIPH UNMARKED
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.
Marking a BCV Device

MIRROR MARK + PK <unit number> SERIAL = <serial number>
Once a BCV device has been acquired into the MCP environment, an option to the
MIRROR MARK command enables you to specify the serial number to be used for the
BCV when it is subsequently imported. This option also permits the operator to
unmark a device and display the MARK status of a family.
This command provides unique identification for a BCV. This enables it to be

imported from its original. This command checks the following:
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
Pk <unit number> SERIAL NUMBER IS NOT UNIQUE. MIRROR MARK ABORTED.
The unit must be eligible to be marked. It must be a nonimported BCV. If it is

not eligible, the operation is aborted and the following message is displayed:
DISK IS NOT ELIGIBLE TO BE MARKED
8600 0395-514 319

PK <unit number> SUCCESSFULLY MARKED TO BE IMPORTED.

This command unmarks a BCV device. The unmarked unit is no longer a candidate to
be imported. Upon successful completion of the command, the following message is
displayed:
PK <unit number> SUCCESSFULLY UNMARKED.

The query form of the MIRROR MARK command displays the mark status of all the
family members to which the PK <unit number> belongs. This status consists of the
unit number, assigned serial number, family name, family index, and the pending
serial numbers.
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-----------------
100 [045678] #1 PERIPH MARKED (PENDING [12345])

150 [023456] #2 PERIPH UNMARKED
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:
PK <unit number> MARK OPERATION FAILED. SEE THE SYSTEM MESSAGES

MANUAL FOR RECOVERY INSTRUCTIONS.
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.
MIRROR OPTION DELAY

The query form of the MIRROR OPTION DELAY command reports the current setting
of the global delay option.
MIRROR OPTION DELAY = <value>

Sets a delay value that can be used by any MIRROR CREATE initiated to apply an
audit to a returning off-line member.
320 8600 0395-514

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.
MIRROR OPTION DELAY 3
MIRROR OPTION QUICKAUDIT

Reports the current setting of the QUICKAUDIT global option.
MIRROR OPTION QUICKAUDIT ON

MIRROR OPTION QUICKAUDIT OFF
Set the global QUICKAUDIT option to the specified value and force the QUICKAUDIT
error recovery option of all current mirrored sets to this value. The global
QUICKAUDIT setting determines the initial QUICKAUDIT error recovery option setting
for new mirrored sets.
MIRROR OPTION PARTIALSETS

MIRROR OPTION PSETS
Reports the current setting of the PARTIALSETS option: HLAUDIT or WAIT.
MIRROR OPTION PARTIALSETS HLAUDIT

MIRROR OPTION PSETS HLAUDIT
The HLAUDIT setting prevents the need for operator intervention if a partial set
condition arises during halt/load initiation (for example, because a hardware failure
caused a mirrored member to go offline). The HLAUDIT setting causes the system to
force the logical volume online by performing one of the following actions:
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:
MIRRORED SET(S) PK <number,[number,[ ... ]]> WERE

FORCED ONLINE BY AUDITING OFFLINE MEMBER(S).
ACKNOWLEDGE WITH <mix#> OK
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:
MIRRORED SET(S) PK <number,[number,[ ... ]]> WERE

FORCED ONLINE BY INVALIDATING ALL OTHER SET MEMBER(S)
ACKNOWLEDGE WITH <mix#> OK
8600 0395-514 321

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.
MIRROR OPTION PARTIALSETS WAIT

MIRROR OPTION PSETS WAIT
Specifies that the system should wait for operator intervention after a halt/load
before making partial mirrored sets available for use. The system creates a
PARTIALSETS waiting entry for any partial mirrored set. The data on these partial
mirrored set volumes is not available for use by applications until either the missing
members are brought online or the operator forces the volumes to come online by
using the MIRROR AUDIT system commands.
WAIT is the default setting of PARTIALSETS.
MIRROR OPTION PK <unit number>

If no options are specified, the current recovery option settings for the specified
mirrored set are displayed. QUICKAUDIT is included in the response only if enabled
for the set. The setting of MANUALSYNC is included only if it is currently enabled.
MIRROR OPTION PK <unit number> DONTREAD = YES

MIRROR OPTION PK <unit number> DONTREAD = NO
Specify whether or not to exclude the specified disk unit from read operations
distributed among mirrored disks. The DONTREAD feature is useful if you determine
that read performance might improve when issuing mirrored reads to some members
versus others.
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 following example causes PK 1673 to be excluded from mirrored read

distribution algorithms:
MIRROR OPTION PK 1673 DONTREAD = YES
MIRROR OPTION PK <unit number> QUICKAUDIT ON

MIRROR OPTION PK <unit number> QUICKAUDIT OFF
The QUICKAUDIT error recovery option for the specified mirrored set is changed to
the specified value. If QUICKAUDIT is enabled for a mirrored set on an IOM system,
improved real-time performance during I/O error recovery is achieved by temporarily
decommitting a mirrored set member to audit, if possible, during recovery from
certain slow transient errors.
322 8600 0395-514

MIRROR OPTION PK <unit number> READDISTRIBUTION . . .

MIRROR OPTION PK <unit number> RD . . .
Specify the method that the system uses to distribute read operations among
mirrored disk units. The specific values for this option are described under their own
headings later in this discussion. The following considerations apply to the
READDISTRIBUTION option in general:
When the READDISTRIBUTION option is specified for a member of a mirrored

set, it affects all members of the mirrored set.
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.
MIRROR OPTION PK <unit number> READDISTRIBUTION DEFAULT

MIRROR OPTION PK <unit number> RD DEFAULT
A READDISTRIBUTION value of DEFAULT restores the system default read
distribution algorithm. The effect depends on whether the mirrored set is caching,
that is, using the Memory Accelerated Caching System (or MACS).
If the mirrored set is not caching, read operations are rotated evenly among the
online members of the mirrored set.
f the mirrored set is caching, a static partitioning algorithm is used. This

algorithm divides the address space of the mirrored set evenly among the online
members of the set. The read operation is sent to the member whose portion of
the address space includes the starting disk address of the read request.
At fixed intervals of approximately four minutes, the system reassigns the

mapping of the address space. Thus, if member 1 was previously assigned the
low disk addresses, member 1 is now assigned the high disk addresses, and the
reverse is done for member 2. In this way, the system refreshes the cache pages
and ensures consistent access to all members of the set over time. This method
ensures the cache contents are backed by a working device and also ensures that
all devices of the mirrored set are exercised periodically.
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.
MIRROR OPTION PK 45 READISTRIBUTION = DEFAULT
MIRROR OPTION PK <unit number> READDISTRIBUTION BYADDRESS

MIRROR OPTION PK <unit number> RD BA
A READDISTRIBUTION value of BYADDRESS causes the system to divide the disk
address space evenly among the online members of the mirrored set. The effect is
much like the default static partitioning used with cached mirrors, except that the
8600 0395-514 323

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.
If a member is lost or removed, the address space is automatically divided

among the remaining members equally.
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:
MIRROR OPTION PK 101 RD = BYADDRESS
The address space is assigned as follows:
PK 100 is assigned addresses 0 through 999,999
PK 101 is assigned addresses 1,000,000 through 1,999,999
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.
MIRROR OPTION PK <unit number> READDISTRIBUTION BYADDRESS

STRIPESIZE = <number> SECTORS
MIRROR OPTION PK <unit number> RD BA SS = <number> SECTORS
The STRIPESIZE specification instructs the system to logically divide the address
space for the mirrored set into sections (or stripes) of the specified size and then
assign the stripes to the online members. For example, a stripe size of 1 million
means that the first million sectors of the address space are assigned to the first
member of the set, the second million sectors are assigned to the second member,
and so on.
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
324 8600 0395-514

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:
MIRROR OPTION PK 600 RD = BA SS = 2000000 SECTORS
The preceding command assigns address ranges as follows:
PK 500 is assigned addresses 0 through 1,999,999
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:
MIRROR OPTION PK 900 RD = BA SS = 3000000 SECTORS
The address space is assigned as follows:
MIRROR OPTION PK <unit number> MANUALSYNC ON

MIRROR OPTION PK <unit number> MANUALSYNC +
Both of these commands turn on the MANUALSYNC option for PK <unit number>.
Operator acknowledgement is required before a mirror audit is applied to PK <unit
number>.
8600 0395-514 325

MIRROR OPTION PK <unit number> MANUALSYNC OFF

MIRROR OPTION PK <unit number> MANUALSYNC -
Both of these commands turn off the MANUALSYNC option for PK <unit number>.
The MCP automatically applies mirror audits when PK <unit number> becomes
useable again.
MIRROR OPTION PK <unit number> MANUALSYNC

This command displays the current setting of MANUALSYNC for PK <unit number>.
MIRROR OPTION PK <unit number> RECOVERY = DMS

The DMS value enables faster recovery for packs used solely by DMSII or a program
with a similar audit mechanism. In the event of a halt/load, such an audit
mechanism reissues outstanding write operations to ensure that the mirrored packs
are updated to an identical state.
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.
MIRROR OPTION PK <unit number> RECOVERY = DISCARD

Setting the DISCARD option breaks the mirrored set; only one pack is brought online
if the OWL is lost. RECOVERY = DISCARD is the default setting.
MIRROR OPTION PK <unit number> SPARE ON

MIRROR OPTION PK <unit number> SPARE OFF
Establishes a spare disk pool of disk packs for the Mirrored Disk Pooling Facility
(MDPF). 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). SPARE ON (or SPARE +) sets the in-use spare attribute in the label of the
specified pack. SPARE OFF (or SPARE ) resets the in-use spare attribute.
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
326 8600 0395-514

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:
PK <unit number> ADDED TO THE SPARE DISK POOL
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:
PK <unit number> REMOVED FROM THE SPARE DISK POOL
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.
MIRROR RELEASE PK <unit number>

Eliminates one or more packs from a mirrored set. When mirrors are released, they
are automatically taken offline and their labels are invalidated, with one exception: if
only one pack remains, it is left online. When all but one member are released, the
remaining member is modified to indicate that it is no longer mirrored, and the set is
eliminated from the system mirror structures.
Note: The MIRROR RELEASE command has no effect on the time limit assigned to
either the released or remaining members of a mirrored set.
MIRROR RELEASE ALL COPIES OF PK <unit number>

Releases all mirrors in a set, except the unit specified, from the mirrored set and
takes them offline. The remaining member remains online, and its label is updated to
show that it is no longer mirrored.
MIRROR RELEASE OFFLINE COPIES OF PK <unit number>

Releases only offline members of the mirrored set. (An offline member is one in the
process of being audited.)

Mirrored disks that had write operations in progress when the system underwent a
halt/load are placed into a pending state during system initialization to synchronize
the data of the mirrored copies. If the system undergoes a halt/load while a mirror is
8600 0395-514 327

in the pending state, the mirror is removed from its set during the subsequent
system initialization.
Note: If OP + OKTIMEANDDATE was specified before a halt/load, system

initialization pauses while it waits for the operator to reply to the RSVP message
PLEASE VERIFY TIME AND DATE. Mirrors of critical unitssuch as the halt/load family,
the log family, and the catalog family that had write operations in progress when the
system underwent a halt/load are in the pending state described previously until the
operator responds to the RSVP message. Therefore, if the system undergoes a
halt/load during the RSVP process, the mirrors of critical units are lost.
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.
Disk Mirroring With VSS-2 Disks

Some restrictions apply to the use of mirrored sets containing various combinations
of VSS-1, VSS-2, or 180-byte disks. For a general description of VSS disks, refer to
the Peripherals Information File on the Product Documentation CD-ROM.
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:
NOT ALLOWED: Destination must be INITIALIZED as VSS-1 and RCED

with CAPACITY option to mirror this source.
To convert the selected disk to a compatible destination for this source
1. If the disk is labeled, enter the following command:
INITIALIZE PK <destination disk> OLDNAME = <name> VSS = VSS1
If the disk is not labeled, enter the following command:
INITIALIZE PK <destination disk> VSS = VSS1
RC PK <destination disk> NAME = <temp name> SERIAL = <temp serial>

CAPACITY LIKE PK <source disk>
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
328 8600 0395-514

MIRROR CREATE command that violates one of these restrictions, the system
displays the following message:

with CAPACITY option to mirror this source.
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.
Source Target Allowed
180-byte VSS-1 Yes
180-byte VSS-2 No (3)
180-byte 180-byte (1) Yes (2)
VSS-1 180-byte Yes
VSS-1 VSS-2 No (3)
VSS-1 180-byte (1) Yes (2)
VSS-2 180-byte Yes (5)
VSS-2 VSS-1 No (4)
VSS-2 180-byte (1) Yes (5)
180-byte (1) VSS-1 No (4)
180-byte (1) VSS-2 Yes
VSS-2 180-byte (1) Yes (5)
180-byte (1) VSS-1 No (4)
8600 0395-514 329

Source Target Allowed
180-byte (1) 180-byte Yes (5)
Notes:
1. The 180-byte disk is reconfigured with VSS = VSS2.
2. The target 180-byte disk no longer uses VSS-2 file allocation after this mirror
create operation is started.
3. The VSS-2 target must be initialized to VSS-1 and reconfigured with

CAPACITY LIKE PK <source> to mirror this source.

CAPACITY LIKE PK <source> to mirror this source.
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.
Released Mirror Spare Disk Eligible

Candidate
(1)
180-byte 180-byte Yes
180-byte 180-byte with VSS Yes (2)

= VSS2
180-byte VSS-1 Yes
180-byte VSS-2 No
180-byte with VSS 180-byte Yes (3)

= VSS2
180-byte with VSS 180-byte with VSS Yes

= VSS2 = VSS2
180-byte with VSS VSS-1 No

= VSS2
180-byte with VSS VSS-2 Yes

= VSS2
330 8600 0395-514

Released Mirror Spare Disk Eligible

Candidate
(1)
VSS-1 180-byte Yes
VSS-1 180-byte with VSS Yes (2)

= VSS2
VSS-1 VSS-1 Yes
VSS-1 VSS-2 No
VSS-2 180-byte with VSS Yes

= VSS2
VSS-2 VSS-1 No
VSS-2 VSS-2 Yes
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.
8600 0395-514 331

ML (Mix Limit)
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.
ML QUEUE <queue number list>

For each job queue specified, the queue number, the active count, the mix limit, and
the number of jobs queued are displayed. The queues are displayed in the order
specified in the <queue number list>.
Example
ML
QUEUED ACTIVE LIMIT QUEUED

0 2 10 0
3 0 2 0
5 4 4 1
TOTAL 6 NONE
332 8600 0395-514

MM (Memory Module)
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
8600 0395-514 333

MM (Memory Module)
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
SYSTEM TYPE: CS7101-1007

MEMORY USAGE:
SYSTEM 128 Mwords
TOTAL ONLINE 128 Mwords
334 8600 0395-514

MODE (Unit Mode)
MODE (Unit Mode)

The MODE (Unit Mode) command tells the system that the write-enable status of a
unit has been changed. The command also sets the automatic unload status of a
magnetic tape unit. The system preserves these status settings of a unit across
halt/loads.
Syntax
<iopartner specifications>
The hubindex is an integer in the range 0 through 15.
Explanation
MODE DK <unit number> IO
MODE PK <unit number> IO
MODE MT <unit number> IO
Allow the device to revert to normal operation.
MODE DK <unit number> IN

MODE PK <unit number> IN
Prevent new files from being created on the specified unit. This prohibition extends
to new RESERVEDISK and BADDISK files, so that most RESERVE functions are
effectively blocked. These commands also prevent the allocation of new file areas to
existing files, and file removal through the WFL statement REMOVE A/B, C/= FROM
D. However, user programs can still write to existing file areas, and can remove
individual files through the CLOSE with PURGE statement.
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.
8600 0395-514 335

MODE (Unit Mode)
ACCESSDATE BACKUPTIMEUT COPYSOURCETZ
ACCESSTIME BACKUPTZ READDATE
ACCESSTZ COPYSOURCEDATE READDATEUT
BACKUPDATE COPYSOURCEDATEUT READTIME
BACKUPDATEUT COPYSOURCETIME READTIMEUT
BACKUPTIME COPYSOURCETIMEUT READTIMETZ
MODE MT <unit number> IN

Prevent new files from being created on the specified unit.
MODE DK <unit number> OUT

MODE MT <unit number> OUT
MODE PK <unit number> OUT
Allow the device to revert to normal operation.
MODE HC <unit number> IO

Allows the specified host control (HC) unit to be opened for input/output (I/O) use.
MODE HC <unit number> IN

Allows the specified HC unit to be opened for input (read operations) only.
MODE HC <unit number> OUT

Allows the specified HC unit to be opened for output (write operations) only.
MODE HC <unit number> CLOSED

Disallows HCFILE use of the specified HC unit.
MODE MT <unit number> AUTOUNLOAD ON

Instructs the MCP to unload a tape on the device when the unit is closed and
released or when the MCP performs a reel switch from the unit.
MODE MT <unit number> AUTOUNLOAD OFF

Instructs the MCP to unload a tape on the device only when specifically directed by a
programmatic close or by the RW (Rewind) system command.
MODE HC <unit number> WRITEPARTNER = <hubindex>

MODE HC <unit number> WP = <hubindex>
Cause all HCFILE write operations on the specified HC unit to be directed to the
specified hubindex.
336 8600 0395-514

MODE (Unit Mode)
MODE HC <unit number> READPARTNER = <hubindex>

MODE HC <unit number> RP = <hubindex>
Cause HCFILE read operations from the specified HC unit to expect input only from
the hubindex.
MODE HC <unit number> WRITEPARTNER

MODE HC <unit number> WP
MODE HC <unit number> READPARTNER
MODE HC <unit number> RP
Remove WRITEPARTNER or READPARTNER specifications from the specified HC unit.
Examples
Example 1
MODE HC 096 OUT
HC096 MODE IS OUT
Example 2
MODE MT 48 AUTOUNLOAD OFF
MT 48 MODE IS AUTOUNLOAD OFF

If applied to HC units, the MODE command controls the direction of the I/O as well
as specifying partner HC units to which I/O is permitted.
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.
The effect of the AUTOUNLOAD MODE option on programmatic file closes is

summarized in the following table.
Option Value Effect on File CLOSE Result
ON CLOSE(F) Rewound/unloaded
CLOSE(F,REWIND) Just rewound
CLOSE(F,REEL) Rewound/unloaded
CLOSE(F,PURGE) Rewound/unloaded
8600 0395-514 337

MODE (Unit Mode)
Option Value Effect on File CLOSE Result
CLOSE(F,*) Position retained
CLOSE(F,LOCK) Rewound/unloaded
REWIND(F) Just rewound
F.OPEN:=FALSE Just rewound
Block exit close Rewound/unloaded
Implicit close on reel Rewound/unloaded

switch
OFF (default) CLOSE(F) Just rewound
CLOSE(F,REWIND) Just rewound
CLOSE(F,REEL) Just rewound
CLOSE(F,PURGE) Just rewound
CLOSE(F,*) Position retained
CLOSE(F,LOCK) Rewound/unloaded
REWIND(F) Just rewound
F.OPEN:=FALSE Just rewound
Block exit close Just rewound
Implicit close on reel Just rewound

switch
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.
338 8600 0395-514

MOVE (Move Job or Pack)

The MOVE (Move Job or Pack) command changes the order of jobs in job queues or
moves a pack from one drive to another. The changes made to a job in a queue are
temporary. If a halt/load occurs, the changes are lost.
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.
MOVE PK <unit number> TO PK <unit number>

Moves a disk pack to another drive, even if the pack is in use. Units in the halt/load
family, the OVERLAY families, the JOBDESC family, and the family that contains the
SYSTEM/SUMLOG file are critical units. A critical unit cannot be moved, except on
LX5400, CS7101, and CS7201 machines. On these systems, critical units can be
moved unless the halt/load pack has already failed, making it impossible to bring the
needed MCP algorithms into memory.
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:
MOVE <family name> FROM PK <unit number> TO PK <unit number>
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.
8600 0395-514 339

The recommended procedure for moving a pack is as follows:
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.
MOVE 7419 7421
7419 HAS BEEN MOVED AFTER 7421
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);
7423 50 ?BEGIN JOB STCEDITOR;
340 8600 0395-514

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.
MOVE 6627, 6629, 6631 : 6630

SQ50
QUEUE 50:
6630 50 ?JOB B;
6631 50 ?BEGIN JOB PAYROLL;
6629 50 ?BEGIN JOB SCHEDULEA;
6627 50 ?BEGIN JOB DUMPTAPETODISK(BOOLEAN HISTORY);
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:
MOVE PK67 TO PK69
A MSG (Display Messages) command shows that the MOVE is being initiated:
MSG
--Mix-Time-------------------- MESSAGES ----------------------------

*1387 16:26 MOVE BKRUNNERS FROM PK67 TO PK69
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:
-Job-Task-Time-Hist------- COMPLETED ENTRIES ------------------------

1387\1387 16:30 EOT MOVE PK67 TO PK69
8600 0395-514 341

MP (Mark Program)
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:
Certain options of the MP system command require security administrator

status. The MP system commands are available to users assigned the
SECADMIN option or are privileged.
Each code file option can be selected only once.
Syntax
<code file option assignment>
342 8600 0395-514

MP (Mark Program)
<code file option deletion>
<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
8600 0395-514 343

MP (Mark Program)
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.
<file title> + <code file option assignment>

Sets the specified option of the object code file.
<file title> <code file option deletion>

Resets the specified option of the object code file.
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,
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.
Note: The definition of <identifier> requires that it must be enclosed in quotation

marks if it includes any special characters.
344 8600 0395-514

MP (Mark Program)
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,
8600 0395-514 345

MP (Mark Program)
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.
If a given process becomes suspended, it appears in the W (Waiting Mix Entries)

system command display, regardless of whether the SUPPRESSED option of the
object code file is set.
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.
346 8600 0395-514

MP (Mark Program)
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.
For example, if you enter
MP MYCODEFILE + WORKLOADGROUP *BATCH
and then
RUN MYCODEFILE; WORKLOADGROUP = INTERACTIVE
the task runs with a WORKLOADGROUP of BATCH.
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.
8600 0395-514 347

MP (Mark Program)
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.
GSDIRECTORY A process with this privilege can access GETSTATUS directory

and volume requests that are normally restricted to a privileged
process.
The GSDIRECTORY privilege also provides users with the
capability to use the FILEDATA TAPEDIR request.
IDC A process with this privilege can update the current

DatacomInfo file through DATACOMSUPPORT entry points.
LOCALCOPY A process with this privilege can copy files and directories
belonging to other users on the local host through library
maintenance.
LOGINSTALL A process with this privilege can access the MCSLOGGER

intrinsic to create log installation records.
LOGOTHERS A process with this privilege can access the MCSLOGGER

intrinsic to create other log records for which privilege is
currently required. Refer to the Events Logged by MCP_LOGGER
table in the System Log Programming Reference Manual for
information on the log types affected.
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.
SYSTEMUSER A process with this privilege can be specified as a code file

privilege using the MP system command.
348 8600 0395-514

MP (Mark Program)
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
FILE SYSTEM/GENERALSUPPORT ON DISK (NEWPCODE) IN USE

PRIVILEGES:
PU TRANSPARENT
GRANULATED PRIVILEGES:
NONE SET
OTHER ATTRIBUTES:
CONTROL
8600 0395-514 349

MP (Mark Program)
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.
MP OBJECT/DELTA + CONTROL, + COMPILER, + SUPPRESSED, + IDENTITY = PROG
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.
MP OBJECT/DELTA + PU TRANSPARENT, + SECADMIN TRANSPARENT, - CONTROL
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.
MP MY/CODE/FILE + SERVICE MyService
FILE *MY/CODE/FILE ON DISK (CCCODE)

PRIVILEGES:
PU
NONE SET
SERVICES:
HADTHISALREADY
MYSERVICE
OTHER ATTRIBUTES:
NONE SET
Example 5
The following example removes the association between the program named
SYSTEM/PAYROLL and the service named Payroll.
MP SYSTEM/PAYROLL - SERVICE "Payroll"
FILE *SYSTEM/PAYROLL ON DISK (COBOL85CODE)

PRIVILEGES:
PU
NONE SET
OTHER ATTRIBUTES:
350 8600 0395-514

MP (Mark Program)
NONE SET
IDENTITY: PAYROLL
Example 6
The following example assigns the code file (MYUC)OBJECT/MYCODE with several
granulated privileges.
MP (MYUC)OBJECT/MYCODE + READ, + WRITE TRANSPARENT, + USERDATA
FILE (MYUC)OBJECT/MYCODE ON DISK (ALGOLCODE)

PRIVILEGES:
NONE SET
WRITE TRANSPARENT
READ
USERDATA
OTHER ATTRIBUTES:
NONE SET

If the security administrator option has been specified by using the ??SECAD +
version of the ??SECAD (Security Administrator Authorization) command, only those
users with the security administrator privilege can use the following MP command
options:
COMPILER
EXECUTABLE
IDENTITY
<granulated privilege> TRANSPARENT
PU
PU TRANSPARENT
SECADMIN
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.
8600 0395-514 351

MQ (Make or Modify Queue)

The MQ (Make or Modify Queue) command creates a job queue, changes the
attributes of a job queue, or deletes a job queue.
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>
352 8600 0395-514

<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.
MQ <queue number> <queue attributes>

Specifies new values for attributes of the specified queue. Attributes can be deleted
from the queue, which returns them to the value they would have had if they had
never been specified. For example, to delete the FAMILY attribute, specify FAMILY.
(you must include the period). To delete the tape resource attributes, specify TAPE0.
To delete all other attributes, specify <attribute> .
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
8600 0395-514 353

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.
TURNAROUND = <real number>

Assigns <real number> as the value of the TURNAROUND attribute, where <real
number> is an unsigned real constant indicating minutes. This value is used by the
CONTROLLER when selecting jobs from the queues. Turnaround time is the time
since the selection of the previous job from a queue. If that time is greater than the
value of the TURNAROUND attribute of the queue, the CONTROLLER favors the
queueunless the value of the TURNAROUND attribute of another queue is exceeded
by a greater amount. If no TURNAROUND value is assigned, turnaround time for the
queue is assumed not to be a concern and is not computed.
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.
FAMILY <family name> = <family name> ONLY

FAMILY <family name> = <family name> OTHERWISE <family name>
Associate family specifications with a job queue so that default specifications are
provided for jobs in that queue. If a queue has a family specification, the family
statement is used for any job or user that runs through the queue. If a job has a
family statement that does not exactly match the family statement of the queue, the
job is rejected by the following message:
QUEUE FAMILY MISMATCH
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
354 8600 0395-514

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.
8600 0395-514 355

<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
356 8600 0395-514

Example 2
This example creates a queue, numbered 4, with the specified attributes:
MQ 4 MIXLIMIT=3, TURNAROUND=2.5, DEFAULTS(PRIORITY=60,

IOTIME=20,PROCESSTIME=3,LINES=50),LIMITS
(PRIORITY=80,IOTIME=60,PROCESSTIME=20,LINES=200,
TAPE=14)
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.
MQ 5 FAMILY DISK = STUDENTFILES OTHERWISE DISK
8600 0395-514 357

MSC (Message Control)

The MSC command enables you to activate the message suppression feature. You
can control the display of system messages at the system ODT and at remote
terminals. This command is especially useful if your site runs jobs that produce
repetitive ODT or terminal messages. You can, for example, simplify ODT and remote
terminal display by suppressing announcements of each successful completion of a
library maintenance file copy operation.
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:
A type of message, such as warning messages

A unique message characteristic, such as a specific mix number, task name,
or usercode that identifies the job or jobs producing the messages to be
suppressed or displayed
Note: Do not specify a chargecode as the characteristic to be identified. While other
message characteristics are single names of up to 17 characters, charge codes can
be multilevel names.
In addition to controlling which messages are displayed or suppressed, an MSC

command can control where the suppression or display action occurs:
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:
Display the currently active MSC commands.

Suppress the display of messages either on the ODT or on the remote
terminal, or on both.
Reactivate the display of some or all previously suppressed messages.
Dynamically suppress or reactivate the display of messages based on
specified message characteristics such as the usercode under which the job or
jobs producing the messages are running or the message ID of a specific
message type.
Temporarily suspend all active MSC commands and later reactivate those
commands to resume message suppression.
Clear all active MSC commands.
358 8600 0395-514

Store one or more MSC commands as an MSC command file.

Save the current active list of MSC commands as an MSC command file.
Define an MSC command file as the file to be loaded automatically after a
halt/load.
Load MSC command files manually as needed.
The System Operations Guide also provides information on the message suppression
feature.
Syntax
<type>
<source>
<destination>
<file title>
8600 0395-514 359

<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.
Wild-card characters are valid in the following MSC command variables:
Variables used to identify a message type: chargecode, task name, identity,

usercode, message ID
Variables used to identify the source of a message ID: chargecode, task
name, identity, usercode
You can use the following wild-card characters in MSC commands.
Character Meaning
Equal sign (=) Match any sequence of characters.
Tilde (~) Match any sequence of characters excluding the slash (/) file
node separator.
Question mark Match any individual character.

(?)
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:
MSC SUPPRESS CHARGE ???9= AT ALL
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:
MSC SUPPRESS REMOTE MSRWARNG= AT ODT
Explanation
The MSC command enables you to control the display or suppression of system
messages.
360 8600 0395-514

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 SUPPRESS <type> AT <destination>

Suppresses the display of selected messages from jobs initiated at the ODT or a
remote terminal. Messages are selected for suppression if they are of the specified
type and intended for the specified destination.
MSC SUPPRESS REMOTE <type> AT <destination>

Suppresses the display of selected messages from jobs initiated at remote terminals.
Messages are selected for suppression if they are of the specified type and intended
for the specified destination.
MSC SHOW <type> AT <destination>

Reactivates the display (cancels the suppression) of selected messages from jobs
initiated at either the ODT or a remote terminal. Messages are selected for resumed
display if they are of the specified type and are intended for the specified
destination.
MSC SHOW REMOTE <type> AT <destination>

Reactivates the display (cancels the suppression) of selected messages from jobs
initiated at remote terminals. Messages are selected for suppression if they are of
the specified type and intended for the specified destination.
MSC LOAD <file title>

Appends a file of MSC commands to the currently active MSC commands on the
system.
MSC SAVE <file title>

Saves the current list of MSC commands in the designated file. The current list
consists of all MSC commands that are currently active on the system. To display the
current list, enter MSC with no parameters as described earlier in this discussion.
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.
8600 0395-514 361

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:
MSC SUPPRESS REMOTE USER OPS AT MCS
The messages still appear at the ODT.
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:
MSC SUPPRESS TASK OBJECT/ED= AT ODT
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:
MSC SUPPRESS MSG MSRDIR4 FROM USER STAT AT ALL
Example 4
The following command suppresses from display at the ODT all occurrences of
message MSRDIR3 stemming from jobs initiated at remote terminals:
MSC SUPPRESS REMOTE MSRDIR3 AT ODT
Messages with the message ID value of MSRDIR3 are of the following form:
FILE COPIED FROM DISK1 TO DISK2
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.
362 8600 0395-514

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:
MSC SUPPRESS REMOTE CHARGE XXXX AT ODT
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:
MSC SUPPRESS IDENTITY MYPROG AT ODT
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:
MSC SUPPRESS MSG MSRWAR= FROM IDENTITY TEST AT ODT

Understanding How the System Uses MSC Commands
When the operating system is prompted to display a message, it reads the current
list of message control commands. It then suppresses or displays the message
according to the most recent applicable message directive it encounters.
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
8600 0395-514 363

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.
Entering MSC Commands

You can enter MSC commands directly, or by loading one or more MSC command
files. See Creating and Using MSC Command Files for more information on this
method.
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:
A halt/load occurs. When the operating system is halt/loaded, the part of

system memory storing the MSC commands is erased.
An MSC CLEAR command is entered. The MSC CLEAR command erases all
current message suppression commands.
An MSC SUSPEND command is entered. The MSC SUSPEND command
suspends all MSC suppression. The suspension continues until either an MSC
RESUME command is entered or a halt/load occurs.
Displaying Current MSC Commands
To display the MSC commands that are currently active on your system, enter the
following command:
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.
Suppressing and Showing Messages

The SUPPRESS and SHOW options of the MSC command enable you to control
message display as follows:
The SUPPRESS option suppresses selected messages at designated locations.

The SHOW option cancels the suppression of designated messages at
designated locations (it reactivates the display of selected messages). The
SHOW option only reactivates the display of messages that were suppressed;
if no messages were suppressed, the option has no effect.
An MSC command with either of these options must include a message type
specification to identify the messages to be controlled and a destination specification
to indicate the location or locations to be affected by the command. The command
can also include the REMOTE qualifier.
A maximum of 9999 MSC SUPPRESS and SHOW commands can be active

simultaneously. If you specify more than 9999 commands, an error is displayed.
364 8600 0395-514

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:
MSC SUPPRESS USER OPS AT ODT
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:
MSC SUPPRESS REMOTE USER OPS AT ODT
The messages still appear on the terminal from which the job was initiated.
Message Type Specifications

The following table outlines the message type specifications you can specify in an
MSC SUPPRESS or MSC SHOW command.
Type Messages Referenced
CHARGE All messages from programs with the designated

chargecode
MIXNO All messages from programs with the designated mix

number
JOBNO All messages from programs with the designated job

number
TASK All messages from programs with the designated task

name
8600 0395-514 365

Type Messages Referenced
IDENTITY All messages prefixed with the designated identity, as

assigned with the MP (Mark Program) system command
USER All messages from programs with the designated

usercode
ALL All types of messages
MSG All messages having the designated message ID
Note: An MSC command that specifies a task name takes effect only when that
name matches the task name in a current mix entry.
The following table presents selected message IDs.
Message ID Corresponding Message
MSRDIR3 <file name> COPIED FROM <source> TO

<destination>
MSRDIR4 <file name> REMOVED ON <family name>
MSRDIR7 <file name> CHANGED TO <file name>
MSRDIR10 <file name> NOT ON <family name>
MSRDIR54 <number> FILES REMOVED IN <directory name>
MSRDIR85 <file name> REPLACED ON <family name>
MSRDISP3 DISPLAY: <text>
MSRDPC97 <device> PURGED
MSRFIN9 NO FILE <file name>
MSRHI13 SEG ARRAY ERROR @ <line number>
MSRIPC1 MISSING CODE FILE @ <line number>
MSRWARNG<number> WARNING <number> <text of warning>
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
366 8600 0395-514

specify one of the following options to specify the destination where messages are
displayed.
Entry Destination of Message Display
ODT Operator display terminal (ODT)
PRINTER System printer
REMOTE MSG Your terminal
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.
Value Characteristic Common to Selected Messages
CHARGE <chargecode> Specified chargecode value
MIXNO <mix number> Specified mix number
JOBNO <job number> Specified job number
TASK <task name> Specified task name
IDENTITY <identity> Specified identity value
USER <usercode> Specified usercode
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:
8600 0395-514 367

MSC SUPPRESS MSG MSRDPC97 FROM CHARGE 8179 AT ODT
Message Destination Specifications

The following table outlines the available destination specifications.
Destination Meaning
ODT Operator display terminal (ODT)
MCS Remote terminal from which job

originated
ALL Both the ODT and the remote terminal
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:
MSC SUPPRESS USER HDS AT ODT
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:
MSC SUPPRESS USER HDS AT MCS
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.
To suppress the display at both locations, enter
MSC SUPPRESS USER HDS AT ALL
Combining Commands for Unique Message Control

By entering MSC SUPPRESS and MSC SHOW commands in the proper order, you can
suppress a class of messages but show a subset of that class.
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:
MSC SUPPRESS USER OPS AT ODT

MSC SHOW JOBNO 7683 AT ODT
368 8600 0395-514

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:
MSC SUPPRESS REMOTE MSG MSRDIR54 AT ODT
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:
MSC SHOW REMOTE USER OPS AT ODT
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:
MSC SUPPRESS REMOTE USER XYZ AT ODT

MSC SHOW TASK MY/PROGRAM AT ODT
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.
Creating and Using MSC Command Files

The message suppression feature enables you to perform the following operations:
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.
8600 0395-514 369

Before using this feature, make the following decisions:
Do you want to establish a default file of MSC commands to be used after a

halt/load has occurred? If you do not establish such a file, your operator must
enter MSC commands manually.
Do you need to establish several files that might be used during different
times of the day? If you establish multiple files, you can load a specific file
using the LOAD option of the MSC command or the LOAD selection on the
MSC screen.
Do you just want to add or override MSC commands dynamically as your
needs become apparent? You can use this approach even if you load files that
perform basic message suppression operations.
All MSC commands not specifically saved in separate files are erased when a
halt/load occurs. If you decide to create an MSC command file, you have several
methods of creating that file:
Create a file of MSC commands using a editor such as CANDE.

Create a file programmatically.
Enter MSC system commands and save them using the SAVE option.
Entering MSC commands and then saving them with the SAVE option adds to the
already existing list of active commands. To create a completely new file, you first
must use the CLEAR option.
If you choose to create the file with an editor or a program, follow these guidelines:
The file must be either a text file or a symbol file.

Continuation records can be included in the LOAD file commands. Create a
continuation record by entering an ampersand (&) in the first column for each
following text line in order to concatenate that text line with the previous
record.
Comments, if included, must be preceded by a percent sign (%). Any input
following the percent sign on the same line is ignored.
The file should contain no MSC command that identifies a mix or job number.
Any such command is ignored.
Omit the keyword MSC from the MSC commands. The MESSAGESUPPORT
function, which processes an MSC command file, does not require this
keyword and rejects any command that contains it, resulting in a syntax
error.
When you create an MSC command file by entering MSC commands and saving
them by using the SAVE option, the system automatically removes the MSC
keywords before storing the commands on the file.
370 8600 0395-514

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:
SUPPRESS REMOTE MSG MSRDIR3 AT ODT

SHOW USER TOM AT ODT
SHOW USER DICK AT ODT
SHOW USER MARY AT ODT
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.
To define DEFAULT/MESSAGES as the default message suppression command file on

your system, enter the following command:
COPY DEFAULT/MESSAGES AS *MESSAGES/STARTUP TO SYSTEM(PACK)
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.
8600 0395-514 371

MSG (Display Messages)

The MSG (Display Messages) command displays the most recent messages from the
system. The response includes network messages and other system messages. The
types of messages in the response are determined by the command modifier and the
setting of the CONTROLLER option SEPARATEMSGS. The display shows the mix
numbers of the tasks that generated messages, the times of the messages, and the
text of the messages.
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.
372 8600 0395-514

MSG USER <usercode>

Displays unsuppressed, non-network messages that originated from programs
running with the specified usercode. Although the number of messages displayed is a
function of the TERM LINES and TERM FIRST values for the ODT, the system
searches the entire list of saved messages, up to the number specified by the value
of MAX MESSAGES.
MSG ALL USER <usercode>

Displays non-network messages, including suppressed messages, that originated
from programs running with the specified usercode. Although the number of
messages displayed is a function of the TERM LINES and TERM FIRST values for the
ODT, the system searches the entire list of saved messages, up to the number
specified by the value of MAX MESSAGES.
MSG FULL USER <usercode>

Displays non-network messages, including suppressed messages that originated
from programs running with the specified usercode. The system searches the entire
list of saved messages, up to the number specified by the value of MAX MESSAGES.
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
--Mix--Time----------- MESSAGES --------------------------------------

*4080 16:26 LP4: *BD/0004078/0004079/000LINE ON DISK PRINTED & REMOVED
4078 16:25 DISPLAY:BIND FINISHED.
4078 16:21 PK51 (BIGMACS)SYSTEM/MCP/CCONTROLLER/PATCHES/WEDNESDAY/FINA
L NOT REMOVED (NOT PRESENT)
4076 16:20 PK51 (MACS)OBJECT/CONTROLLER REMOVED ON FIRE
8600 0395-514 373

Example 2
This example shows all messages displayed by programs running with the usercode
PDW:
MSG FULL USER PDW
--Mix--Time------------------ 7 MESSAGES (FULL) USER = PDW -------------

4119 14:18 (PDW)MCP/MM10 COPIED FROM MCPS TO MCP511
4119 14:18 (PDW)OBJECT/TEST/MKSC COPIED FROM MCPMAST TO MCP511
4119 14:18 (PDW)TEST/MSC COPIED FROM MCPMAST TO MCP511
4119 14:18 (PDW)OBJECT/S/UTILIB COPIED FROM MCPMAST TO MCP511
4119 14:18 (PDW)OBJECT/S/DPPRINT COPIED FROM MCPMAST TO MCP511
4119 14:18 (PDW)OBJECT/S/EASE/STATUS COPIED FROM MCPMAST TO MCP511
4119 14:18 (PDW)S/EASE/STATUS COPIED FROM MCPMAST TO MCP511
Example 3
The following example shows all unsuppressed network messages:
MSG NW
---Mix-Time--------------------- 15 NETWORK MESSAGES -----------------

* NW 11:38 PHASE CHANGED FOR TCPIP FROM INITIALIZED TO NETWORKING
* NW 11:38 CNS NETWORK INITIALIZING
* NW 11:37 CONNECTIONGROUP ADDED: CG_ICP_2101
* NW 11:37 CONNECTIONGROUP ADDED: CG_ICP_2100
* NW 11:37 SG_ICP_2100 ADDED AS STATIONGROUP
374 8600 0395-514

MU (Make User)
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
JOHN IS NOT PRIVILEGED
Example 3
MU JOE/JOE
JOE USERCODE CREATED
8600 0395-514 375

MU (Make User)

The MU command is not allowed on a password-generating system.
A valid USERDATAFILE must be present; otherwise, the system responds with a

REQUEST DENIED message. The MU action is subject to regulation by the MU
model entry in SYSTEM/USERDATAFILE. This entry can disallow either the entire MU
command or the PRIVILEGED option of the command. Refer to the explanation of
MAKEUSER in the Security Administration Guide for more information about the
USERDATAFILE.
376 8600 0395-514

MX (Mix Entries)
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>
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>

space character.
8600 0395-514 377

MX (Mix Entries)
MX NAME =pack=
"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 NAME <wild-card string>

Displays one or all mix entries that contain the specified wild-card string, including
any that were suppressed. You can also use all other options with this form of the
command.
MX MCSNAME = <MCS name>

MX MCS = <MCS name>
Display only jobs or tasks originating from the specified message control system
(MCS). The equal sign (=) is optional.
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 QUEUE <queue number>

Displays jobs that were initiated from a job queue and tasks that are descendants of
jobs initiated from a job in the specified queue.
MX USER <usercode>
Displays only jobs or tasks running with the specified usercode.
378 8600 0395-514

MX (Mix Entries)
Examples
Example 1
This example shows RSVP and DISPLAY messages for all unsuppressed jobs or tasks
in the mix:
MX
---Mix-Pri----------------- JOB ENTRIES ----------------------------

* 7275 50 (NORM) JOB NEDCOMPILE
E 7276 50 ..(NORM) *DCALGOL (NORM)OBJECT/SYMBOL/NED
7259 80 Job *SYSTEM/CANDE ON PACK
7277 50 W ..*SYSTEM/DUMPANALYZER
R:NO FILE MEMORY/DUMP (MT) #1
D:PK65 (GEORGE)CANDE/RECV600 REMOVED ON FIRE
7248 80 ..*SYSTEM/COMS ON PACK
D:DISPLAY: OUTPUT ROUTER SELECTED TO MIX NUM 724
The heading line appears on the first page of the Job Entries display and before the
mix entries in automatic display mode (ADM).
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.
blank.

8600 0395-514 379

MX (Mix Entries)
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
---Mix--Que-Pri------------ JOB ENTRIES (ALL) ALL QUEUES -----------------

* 9661 0 50 Job (USER1) J1
9662 0 50 ..(USER1) (USER1)OBJECT/PROG1
* 9658 5 50 Job (USER2) J2
9659 5 50 ..(USER2) (USER2)OBJECT/PROG2
Example 3
This example displays jobs that were initiated without a specified usercode.
MX USER=""
--Mix-Pri---------------------- JOB ENTRIES USER= --------------------------

9618 50 Lib *SYSTEM/DSSSUPPORT
D: DSS:50016440 OPENING CONFIG FILE: *CONFIGURATION/DSSSUPPORT ON DISK.
9623 75 ..SYSTEM/STATION/TRANSFER
D: DSS: 1195970 GSSAPI Library is not enabled on the system.
9617 75 Lib *SYSTEM/CNSOBJMGR/51004
D: DISPLAY:CNSOBJMGR: Version = 51.2.1.
9615 75 Lib *SYSTEM/SNMPAGENT/51004
D: DISPLAY:Maximum number of TCP connections is now set to 65535.
9613 99 Job PRINTS_COMMAND_HANDLER
9612 50 Job *SYSTEM/PRINT/ROUTER
D: DISPLAY:PrintS has no requests to process.
9604 50 Lib *SYSTEM/PRINT/UTILITY
D: PRINT_UTILITY:PrintUtility Version 51.126.0001
9603 50 Lib *SYSTEM/TCPIPSECURITY/51004
D: DISPLAY:-- TCP/IP Security Version = 51.002.0001 (Std).
.
.
.
9479 80 Lib *SYSTEM/NXSERVICES/SERVER
D: NXSERVICES: TCP/IP available
380 8600 0395-514

NAMEMAP
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.
NAMEMAP TO <file title>

Creates a disk file of FILEKIND SEQDATA that contains a list of all controls that have
an associated port name. This file is in the form recognized by both
SYSTEM/CONFIGURATOR and the NAMEMAP command. This functionality enables
you to insert the NAMEMAP file into configuration files without any editing. You can
also use the file to move the known control to port name associations from one
partition to another.
NAMEMAP CTL <CTL number> = <Port Name>

NAMEMAP CTL <CTL number> = 0
Associates a Fibre Channel port name with the designated control. The <port name>
must contain exactly 16 hex digits or be a zero. A <port name> value of zero
removes any Fibre Channel port name associated with the control. The control must
have a status of FREE before you can associate a port name with the control. The
port name association established by this command is not used until the control is
acquired.
8600 0395-514 381

NAMEMAP
NAMEMAP FROM <file title>

Provides the same function as NAMEMAP CTL except that the list of port names is in
a disk file of FILEKIND SEQDATA. This option enables you to take the output of a
NAMEMAP TO <file title> to another partition or to update a new system
configuration. You can edit the file. It is in the form of the <NAMEMAP section> of a
configuration file. If an error occurs while updating one control, processing continues
with the next control. The result, success or error indication, of the action taken for
each control entry in the list is in the SUMLOG; you can view it with
SYSTEM/LOGANALYZER.
NAMEMAP PORT <port number>

NAMEMAP PORT <port number> TO <file title>
Provides a display or disk file of all Fibre Channel port names known to the specified
port. The port must be online because the command requires a port I/O operation to
obtain the name information. Because of the dynamic nature of Fibre Channel fabric,
the information obtained can change each time that you use this command. The
display has no particular order. Two port s connected to the same Fibre Channel
fabric can return the same information but in different orders. Port names returned
by the channel adapter that are not in the NAMEMAP of the MCP have a <CTL
number> of 0.. You can edit the output file, if required, and can use it as input to a
NAMEMAP FROM <file title> command, or insert it inserted into a GROUP statement
of a configuration file.
NAMEMAP PORT <port number> :UNSPECIFIED

NAMEMAP PORT <port number> TO <filename> :UNSPECIFIED
Causes the output of a NAMEMAP PORT command to be altered so that only port
names that are not associated with a control are displayed. This option can be useful
when you add new devices to a Fibre Channel fabric or a port name has changed
within the Fibre Channel fabric as a result of a hardware replacement action (such as
replacing a JBOD disk drive). The port names of the controls of the new disk are not
the same as the port names associated with the controls of the disk that was
removed.
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
CTL 1000 = 21:00:20:78:90:AB:CD:EF

CTL 2000 = 22:00:20:78:90:AB:CD:EF
382 8600 0395-514

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
NAMEMAP: % Friday, November 15 2002 11:23:11
CTL 2000 = 21.00.20.44:55:66:77:88;

CTL 2001 = 22:00:20:44:AA:BB:CC:DD;
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:
NAMEMAP CTL 2001=21:00:20:78:90:AB:CD:EF; CTL 1000=0
Example 4
This example edits a file called XYZ to change or insert entries in the file.
NAMEMAP FROM XYZ
NAMEMAP: % Friday, November 15 2002 11:23:11
CTL 1000 = 10:00:56:78:90:AB:CD:EF;

CTL 2000 = 21.00.33.44:55:66:77:88;
CTL 2001 = 22:00:33:44:AA:BB:CC:DD;
Example 5
This example provides a display of all Fibre Channel port names known to port
31107.
NAMEMAP PORT 31107
NAMEMAP:
CTL 7540 = 21:00:00:20:37:32:91:C3;

CTL 7541 = 21:00:00:20:37:32:93:21;
CTL 7542 = 21:00:00:20:37:32:95:44;
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;
8600 0395-514 383

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.
NAMEMAP PORT 31107 TO XYZ
NAMEMAP: % FOR PORT 31107 Wednesday, February 26, 2003 10:32:10
CTL 7540 = 21:00:00:20:37:32:91:C3; % FABRIC ADDRESS 03:15:A7

CTL 7541 = 21:00:00:20:37:32:93:21; % FABRIC ADDRESS 03:15:A6
CTL 7542 = 21:00:00:20:37:32:95:44; % FABRIC ADDRESS 03:15:A5
CTL 0 = 21:00:00:20:37:32:82:A2; % FABRIC ADDRESS 03:15:90
CTL 0 = 21:00:00:20:37:32:82:DB; % FABRIC ADDRESS 03:15:8F
CTL 0 = 21:00:00:20:37:32:7B:6E; % FABRIC ADDRESS 03:15:88
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 PORT 31107:UNSPECIFIED
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.
NAMEMAP PORT 31107 TO XYZ :UNSPECIFIED
NAMEMAP: % FOR PORT 31107 Wednesday, February 26, 2003 10:32:10
CTL 0 = 21:00:00:20:37:32:82:A2; % FABRIC ADDRESS 03:15:90

CTL 0 = 21:00:00:20:37:32:82:DB; % FABRIC ADDRESS 03:15:8F
CTL 0 = 21:00:00:20:37:32:7B:6E; % FABRIC ADDRESS 03:15:88
384 8600 0395-514

NET (Network)
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.
8600 0395-514 385

NETEX (Support NETEX Software)

The NETEX command initiates and terminates the NETEX (Network Executive)
software and specifies the NETEX initialization file. It also displays the running status
of NETEX software and the title of the current and next NETEX initialization files. For
more information about NETEX, refer to vendor software documentation.
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 = <file title>

Specifies the title of the NETEX initialization file 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.
386 8600 0395-514

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 + <file title>

Starts NETEX software and specifies the title of the initialization file to be used. Any
subsequent initiation of NETEX software also uses the file title 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
NETEX IS NOT RUNNING

NEXT NETEX INITFILE: (UTIL) SYSTEM/NETEX/INIT ON COMM
Example 2
This example shows how to set the NETEX initialization file for a subsequent initiation
of NETEX software.
NETEX = (JBFAL) NETEX/WDB/JN ON RPC
NEXT NETEX INITFILE: (JBFAL) NETEX/WDB/JN ON RPC
8600 0395-514 387

NEW SYSTEMDIRECTORY (Replace an Existing SYSTEMDIRECTORY)
NEW SYSTEMDIRECTORY (Replace an Existing

SYSTEMDIRECTORY)
The NEW SYSTEMDIRECTORY command expands the area sectors of the
SYSTEMDIRECTORY for a disk family from 600 sectors to 2000 sectors.
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.
NEW SYSTEMDIRECTORY ON <family name> AREAS <number>

You can use this form of the command to ensure that the SYSTEMDIRECTORY for the
disk is large enough to hold a given number of files. By pre-expanding a
SYSTEMDIRECTORY with a large enough number of AREAS, you can ensure that the
system will not stop and wait for the operator to remove some files when you are
adding files to the family.
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.
388 8600 0395-514

NEW SYSTEMDIRECTORY (Replace an Existing SYSTEMDI
NEW SYSTEMDIRECTORY ON <family name> AREASECTORS 2000 AREAS

<number>
You can use this form of the command to convert a SYSTEMDIRECTORY with an
AREASECTORS value of 600 to 2000 and to pre-expand the directory so that the
system will not stop and wait for directory space when you add files to the family.
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.
NEW SYSTEMDIRECTORY ON PACK AREASECTORS = 2000

Restrictions
You cannot use the NEW SYSTEMDIRECTORY command on the active halt/load
family.
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.
8600 0395-514 389

Changing the Size of the SYSTEMDIRECTORY for a Disk Family

The following three system commands enable you to change the size of the
SYSTEMDIRECTORY for a disk family.
EXPAND SYSTEMDIRECTORY/<number> ON <family name> AREAS

<number>
The primary purpose of this command is to preexpand the SYSTEMDIRECTORYs
for a given family.
Preexpanding the SYSTEMDIRECTORYs for a family helps to ensure that the
system is not delayed waiting for disk space on the base pack to expand the
SYSTEMDIRECTORY while you are adding files to the family.
NEW SYSTEMDIRECTORY ON <family name>
The primary purpose of this command is to change the AREASECTORS value of
the SYSTEMDIRECTORY on the indicated family.
You can change AREASECTORS from the old 600 sector value to 2000 sectors,
roughly tripling the total capacity of the directory. For single pack disk families,
you can change the value from 2000 sectors to 4000 sectors, roughly doubling
the total capacity of the directory.
SQUASH SYSTEMDIRECTORY ON <family name>
The primary purpose of this command is to reduce the size of the
SYSTEMDIRECTORY for the family and return unused AREAS to the available disk
space pool for use by normal files.
Use this command for disk families that at one time contained a large number of
files but no longer contain or need to contain so many files.
Note that this function is completely different from the function of the "SQUASH
<family name>" system command, which attempts to reduce the
checkerboarding of the available disk space pool.
Performance
The SQUASH SYSTEMDIRECTORY and NEW SYSTEMDIRECTORY commands both use
the same algorithm as follows:
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
390 8600 0395-514

NEW SYSTEMDIRECTORY (Replace an Existing SYSTEMDI
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.
Postpone using the SQUASH SYSTEMDIRECTORY and NEW SYSTEMDIRECTORY

commands until a time when critical programs are not running. Before using either of
these commands, consider using the ADM ST system command on any ODT that is
running the automatic display of system status with a the display of disk packs (PER
PK). Whenever a SQUASH SYSTEMDIRECTORY or NEW SYSTEMDIRECTORY process
is running, avoid issuing any commands that reference disks, such as PER PK
(Peripheral Status), PD (Print Directory), MP (Mark Program), and so forth.
The EXPAND SYSTEMDIRECTORY command uses a much simpler algorithm as

follows:
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.
8600 0395-514 391

NF (No File)
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.
---Mix--Pri-Elapsed------------ 2 WAITING ENTRIES ------------------

* 7777 50 10:11 (ROBY)TEST/ON/PACK
NO FILE XYZ (DK)
7777 NF
392 8600 0395-514

NOTOK (Do Not Reactivate)

The NOTOK command is used to answer NO to certain RSVP messages such as SORT
FILE FULL and OK TO EXPAND.
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.
8600 0395-514 393

NS (Next Screen)
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:
NO MORE ENTRIES FOR THIS REQUEST

NO MORE VIEWABLE ENTRIES FOR THIS REQUEST
The second message indicates that more entries would have been shown if ALL had
been specified with the previously entered system command.
394 8600 0395-514

NW (Network Prefix)
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.
NW NS START NETWORK BNA
NW NS STOP NETWORK BNA
NW NS SHOW NETWORK BNA
For more information about NW NS command input, refer to the Distributed Systems
Services (DSS) Operations Guide.
8600 0395-514 395

NX (NETEX Software Input)

The NX command directs operator input to the NETEX library.
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:
NETEX IS NOT RUNNING
Syntax
Explanation
For the format of NETEX software operator commands, refer to vendor software
documentation.
396 8600 0395-514

O (Overlay)
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.
Processor Overlay Utilization

There are three overlay components: the first is the overlay processor statistic, and
the remaining two are the overlay system parameters. These overlay components
are described in the following table.
Component Description
System Usage The percentage of processor time that could not be

used because of overlay activity.
Threshold If the system parameter OLAYGOAL is 0 (zero) and the

System Usage value is larger than the Threshold value,
any new tasks are scheduled. You can change the
Threshold value by setting the OLAYSATURATION factor
in the SF (Set Factor) system command.
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.
8600 0395-514 397

O (Overlay)
Overlay Disk Utilization

The following table explains the remaining factors in the Overlay Utilization report.
Allocated Overlays on The percentage of Overlay Disk Allocated sectors that

Disk are currently holding data.
Overlay Disk Allocated The percentage of Total Overlay Sectors that are
allocated for use by overlayable arrays.
Total Overlay Sectors The number of sectors reserved by the overlay

subsystem.
Example
OVERLAY
------------------------ OVERLAY UTILIZATION ------------------------
System Usage = 8% Allocated Overlays on Disk = 62%

Threshold = 15% Overlay Disk Allocated = 74%
Change per Second = 10% Total Overlay Sectors = 246,389
398 8600 0395-514

OF (Optional File)
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.
The OF command is useful for responding to a DUPLICATE FILE message. It causes

the new file to be discarded and the old file to be retained.
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:
If the program tried to open an existing file, a NO FILE message is displayed.

If the program tried to create a new file, another REQUIRES DK message is
displayed.
If the file was already opened, the program could be terminated, or the
necessary function might not be performed.
If library maintenance was waiting for the disk, it might continue without
copying any files. If the missing disk was a continuation pack, library
maintenance might not copy the file or it might terminate.
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).
---Mix-Pri-Elapsed------------ 1 WAITING ENTRY ----------------------

* 3968 50 10:11 (ROBY)TEST/ON/PACK
NO FILE XYZ (DK)
3968 OF
8600 0395-514 399

OK (Reactivate)
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.
---Job-Task-Pri---Elapsed----- 1 WAITING ENTRY ----------------------

9079/9080 50 :07 *LIBRARY/MAINTENANCE
LOGTAPE/FILE000 REQUIRES MT #1
9080 OK
400 8600 0395-514

OL (Display Label and Paths)

The OL (Display Label and Paths) command displays the label and path information
for peripheral devices.
Syntax
Note: IOP syntax is valid only on IOP systems.
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.
Path Information Description
CTL The device number of the control that services the unit.
FIRMWARE A number representing the firmware level of a path. If

path firmware level does not apply to the unit, the
column is omitted. For group-coded recording (GCR)
controls, the information describes the task control unit
(TCU) firmware. The control firmware is described on
the top line.
STATUS The status of the CTL. The following list shows the
possible status conditions:
FREED means that the CTL is not attached to the

executing group.
RES MAINT means that the CTL is reserved for
offline maintenance (IOM systems only).
RESERVED means that the CTL is reserved for
maintenance.
HUNG means that the CTL has not completed an
outstanding I/O operation in a reasonable amount
of time for that device type and will not be used for
8600 0395-514 401

further I/O operations.

OUT OF SERVICE means that the CTL is not
available for use.
NO PATH means that there is no available CTL to
this unit.
ONLINE means that the CTL is online.
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.
OL CTL <CTL number list>

Displays the inboard and outboard information for the control unit. The OL control
display is divided into three parts: an upper area composed of one or more lines
describing information specific to the control, an area describing the port the control
services, and an area describing the outboard devices. The following information is
provided for CTLs outboard of a port.
CTL Information Description
CTL The device number of the CTL.
TYPE The type of the CTL.
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.
Port Information Description
PORT The device number of the port the CTL is servicing.
STATUS The status of the port the CTL is servicing. The following
list shows the possible port status conditions:
RESERVED the port is reserved for maintenance (IOM

systems only).
OUT OF SERVICE means that the port is not available
for use.
IN USE means that the port has been selected and can
be used for all I/Os to the CTL.
402 8600 0395-514

ONLINE means that the port is online.

STANDBY means that the port is reserved for use in
the event that another port fails.
Unit Information Description
Outboard The device numbers of units configured to this control.

Devices that are not available to the group appear in
parenthesis.
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 Port: <port number on the storage processor>
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.
OL IOP <IOP number list>

Displays the outboard information for the IOP.
IOP Information Description
IOP The device number of the IOP.
Resource Location <pod>-<mio>-<bus>-<slot>

(Libra Model 185
and 500 Series <pod>
systems) The particular pod on an IOP system
<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
Resource Location <cell>-<remote>-<bus>-<slot>

(Libra Model 600 <cell>
Series systems) The particular cell on an IOP system
<remote>
Identifies the IOP as being in an Integrated (0) or Remote
(1) I/O node
8600 0395-514 403

<bus>
The PCI bus within an IO node on an IOP system
<slot>
The slot in the PCI bus occupied by the IOP
<type> Values The values for <type> can be

(Libra Model 185 FC-1
and 500 Series FC-2
systems) IEA-1
NT

(Libra Model 600 FC-3
Series systems) NT
Microcode This information is hardware specific and provides internal

Identification levels and compile dates.
If the IOP is not online, the microcode identification
variable is replaced with a state value indicating why it is
offline. The IOP state can be SAVED, STANDBY, BROKEN,
or NO PATH.
SAVED means the IOP is offline for maintenance.

BROKEN means that the port is not available for use.
A qualifier specifies the manner in which the IOP is
broken.
STANDBY means that the port is reserved for use in
the event another port fails.
NO PATH means the IOP is listed in the configuration
but is not present in the partition.
In addition to the static states above, there are transitional

states that exist while an IOP is either recovering from an
exception or first coming online. These states are FAILING,
RECOVERING, and INITIALIZING.
PORT The device number of the PORT outboard of the IOP.
TYPE The type of PORT
PORT Description
Information

Identification levels and compile dates.
If the PORT is not online, the microcode identification
variable is replaced with a state value indicating why it is
offline. The IOP state can be RESERVED, OUT OF
SERVICE, or STANDBY.
404 8600 0395-514

RESERVED means that the port is reserved for

maintenance (IOM systems only).
OUT OF SERVICE means that the port is not available for
use.
STANDBY means that the port is reserved for use in the
event that another port fails.
IOP Examples
These examples show an OL command display for an IOP SCSI port.
OL IOP 7
IOP 7 (0-1-7-1): FC-1 <STANDBY>

Last Known FW Info: [ current/last FW indeterminate ] {FW Status: TEMP}
FP 1: C4FT
PORT 6001- 6002: SCSI <NO PATH>
PORT 6004: SCSI <NO PATH>
OL IOP 10
IOP 10 (0-1-2-1): FC-2 <SAVED>

Last Known FW Info: [ current/last FW indeterminate ] {FW Status: TEMP}
FP 1
PORT 5001: FIBER <RESERVED>
PORT 15001: FIBER <STANDBY>
OL PORT <port number list>

Displays the inboard and outboard information for the port. The OL port display is
divided into two parts: an upper area composed of one or more lines describing
information specific to the port, and a lower area describing the control or controls
outboard of the port. The following information is displayed for ports.
Port
Information Description
PORT The device number of the Port.
SMB (IOM systems only)

MLI (IOM systems only)
IPI (IOM systems only)
SCSI
PCCA (IOM systems only)
DAC
8600 0395-514 405

Port

Identification levels and compile dates. If the port is not online, the port
state will be either: RESERVED, OUT OF SERVICE, or IN
USE.
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:
Port does not support Maximum Blocksizes.

Port supports Maximum Blocksizes.
CTL The device number of the CTL that services the port.
TYPE The type of CTL that services the port.
CTL Information
Description
406 8600 0395-514

Port
STATUS The status of the CTL that services the port. The following
list shows the possible CTL status conditions:
FREED means that the CTL is not attached to the

executing group.
RES MAINT means that the CTL is reserved for offline
maintenance (IOM systems only).
RESERVED means that the CTL is reserved for
maintenance.
HUNG means that the CTL has not completed an
outstanding I/O operation in a reasonable amount of
time for that device type and will not be used for further
I/O operations.
OUT OF SERVICE means that the CTL is not available for
use.
NO PATH means that no available port to this CTL
exists.
ONLINE means that the CTL is online.
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
PORT 28145: SCSI [ERL=02.000,SLL=01.499,SCL=4,FEATURES=0,04/05/2001]

Download Capable: No
State: Initialized
Port supports Maximum Blocksizes.
CTL TYPE STATUS VIA PORT
1450 MT1SCSI ONLINE 28145, (28245)
1451 MT1SCSI ONLINE 28145, (28245)
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
8600 0395-514 407

OL PORT 31031
PORT 31031: SCSI [ERL=03.204,SLL=03.029,SCL=5,FEATURES=7,02/28/2003]

DOWNLOAD (LH) CAPABLE: YES
SUB PROTOCOL: FIBRE CHANNEL, STATE: INITIALIZED
PORT SUPPORTS MAXIMUM BLOCKSIZES.
Port_Name: F0:00:08:00:0B:16:00:1C
Node_Name: 10:00:08:00:0B:16:00:1C
5440 FCSCSII ONLINE 31031
5541 FCSCSII RESERVED 31031
5542 FCSCSII RESERVED 31031
5543 FCSCSII FREED 31031
5549 FCSCSII ONLINE 31031
OL PORT 5001
PORT 5001: FIBER <RESERVED>

Serving IOP: 10 Download (LH) Capable: No
Last Known Firmware Level: [ current/last FW indeterminate ]
Sub Protocol: Fibre Channel, State: Offline/Unknown
11500 FCSCSI1 NO PATH (5001)
OL PORT 15001
PORT 15001: FIBER <STANDBY>

Serving IOP: 19 Download (LH) Capable: No
Last Known Firmware Level: [ current/last FW indeterminate ]
Sub Protocol: Fibre Channel, State: Offline/Unknown
408 8600 0395-514


CTL Examples
This example shows an OL command display for a SCSI tape CTL:
OL CTL 1451
CTL 1451: MT1SCSI [ 7 B]

PORT STATUS
28145 ONLINE
OUTBOARD: 53
OL CTL 7541
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
CTL 7541: FCSCSII <FREED>

Port_Name: 21:00:00:20:37:32:93:21
PORT STATUS
31107 RESERVED
OUTBOARD: (541)
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
CTL 16001: OSR CTL [0207]

CLARiiON Multipath Manager
SP-A Port: 0
Port_Name: 50:06:01:60:10:60:27:45
PORTSTATUS
10021 ONLINE
10061 ONLINE
OUTBOARD: PK 6001-6024, (6025-6224)
8600 0395-514 409

Tape Unit Example

This example shows a command and display for a tape unit:
OL MT 52
MT52*H[000052] 36TRKC #1 1:0 <11/18/2004> XYZ/FILE000

CREATION DATE: Thursday, November 18, 2004EXPIRATION DATE: Saturday,
December 18, 2004
CREATION SITE 1
LABELKIND: A SERIES LIBRARY MAINTENANCE.
AUTOUNLOAD OFF
UNIT IS NOT READ-REVERSE CAPABLE
UNIT IS ODD BLOCKSIZE CAPABLE
UNIT HAS LOCATE FAST ACCESS CAPABILITIES
UNIT IS BUFFERING DATA
MAXIMUM BLOCKSIZE 262144 BYTES
UNIT COMPRESSION AVAILABLE
VOLUME COMPRESSION SETTING: ON
DEVICE FIRMWARE LEVEL =7 N
CTL FIRMWARESTATUS
5320 7 NONLINE
The Tape Unit Example shows the following information:
The unit type

The unit number
An asterisk (*) indicates the tape is write-enabled
The type of tape
Values can include the number 8, indicating an 8-millimeter cartridge tape; the
letter P, indicating a 9-track phase-encoded (PE) or group-coded recording (GCR)
tape; the letter Q, indicating a quarter-inch cartridge tape; the letter H,
indicating a half-inch cartridge or similar cartridge tape; the letter D, indicating
digital linear tape (DLT); the number 4, indicating a 4-millimeter cartridge tape;
the letter A, indicating advanced intelligent tape (AIT).
The serial number in brackets ([ ])
The mix number in parentheses, showing that the tape is in use by the
program with that mix number
The tape density
The letter C if compression is being used
The file section number
The volume sequence number preceded by a slash (/), if the tape has ANSI87
tape labels
The cycle number and version number separated by a colon (:)
The creation date in angle brackets (<>)
The title of the tape, and, if applicable, the scratch pool into which the tape
will be placed if it is subsequently purged
410 8600 0395-514

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
\ Designates a tape entered in a volume library.
D Indicates that the mounted volume is listed in the Volume Directory.
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.
Display Name Description
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.
LABELKIND Indicates whether the tape is a special system tape such as

library maintenance or is a user data tape.
LIBMAINTDIR File name of the tape directory disk file for library
maintenance tape. This file should reside on the DL
LIBMAINTDIR disk family.
8600 0395-514 411

AUTOUNLOAD AUTOUNLOAD indicates whether or not the MCP is to unload

a tape on the device when the unit is released by a close
operation or when the MCP performs a reel switch from the
unit. You can override this option by using the AUTOUNLOAD
file attribute.
UNIT IS <NOT> An indication of whether the tape drive is capable of reading

READ-REVERSE in both forward and reverse directions. This information
CAPABLE pertains to the physical drive only. It does not take into
account the attributes of the volume that might be mounted
on the drive.
UNIT IS ODD An indication of whether the tape drive is capable of writing

BLOCKSIZE blocks containing an odd number of bytes. If the unit is not
CAPABLE ODD BLOCKSIZE CAPABLE, no display is shown.
UNIT HAS The tape drive supports LOCATE and READLOCK commands.
LOCATE FAST
ACCESS
CAPABILITIES
UNIT IS <NOT> An indication of whether a buffer-capable unit is buffering

BUFFERING DATA data.
MAXIMUM A number that represents the maximum block size (in bytes,
BLOCKSIZE not words) that can be handled by the unit.
UNIT Valid values are AVAILABLE, UNAVAILABLE, AVAILABLE

COMPRESSION (CONFIGURED OFF), or DETECTED (UNRECOGNIZED).
AVAILABLE means the unit is capable of using an industry
standard data compression and compaction algorithm.
UNAVAILABLE means that, at this time, the unit cannot
perform standard compression algorithms. AVAILABLE
(CONFIGURED OFF) supports compression, but has been
manually configured to be OFF. DETECTED (UNRECOGNIZED)
means that the unit is compression capable, but the MCP is
currently unable to determine what type of compression the
unit supports.
VOLUME Valid values are ON, ON (INCOMPATIBLE), or OFF. ON means

COMPRESSION compression has been applied to the volume. ON
SETTING (INCOMPATIBLE) means compression has been applied to the
volume, but the unit is not capable. OFF means that no
compression has been applied to the volume.
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)
412 8600 0395-514

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
Disk Unit Examples

This example shows a command and display for a disk pack:
OL PK 101
PK 101*C c t [182182:682177:208] #2 TIMERPK (3)(TO BE SAVED)

FAMILY HEADER VERSION 7
FAMILY CREATED ON: 12/14/1994 AT 00:06:29
FAMILY CREATION SITE 102
SCSI/1545-81 PACK
READ/WRITE TIME-OUT = 40 SECONDS
CAPACITY: 8,588,125 SECTORS (1,545,862,500 BYTES)
CTL FIRMWARE STATUS
1100 1439 ONLINE
6100 1439 ONLINE
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
1 The unit number.
2 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; an at
sign (@) if the tape is write-enabled but has been locked by the
LOCKEDFILE file attribute.
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.
5 A backslash (\) designates a disk entered in the volume library. This

display does not show such an example.
6 The letter D indicates that the disk pack is listed in the Volume Directory.
8600 0395-514 413

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.
8 This field is blank.
9 The letter M indicates if the pack is mirrored. If a mirrored set is in the

process of coming online but is waiting for another previously online
member, it is considered a partial mirrored set. These packs are marked
with a lowercase m instead of an uppercase M. This display does not
show such an example.
10 A letter t indicates that a user-specified I/O time limit value is assigned

to the disk. Otherwise the column is blank.
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.
414 8600 0395-514

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.
14 The family index number, from 1 through 255.
15 The family name.
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.
Disk Unit: Unit Served by a Control Unit (CTL)

This example shows a disk pack that is served by a PK1SBC CTL. The DEVICE
FIRMWARE LEVEL line specifies the firmware level of the disk pack itself.
OL PK 800
PK 800*B [800805] #1 SBC800 (0)

SCSI 805 PACK
CAPACITY: 4,475,653 SECTORS (805,617,540 BYTES)
DEVICE FIRMWARE LEVEL = 0D07
CTL FIRMWARE STATUS
8000 A151 ONLINE
8100 A141 ONLINE
8600 0395-514 415

Disk Unit: Continuation Pack for Family Missing Base Pack

This example shows the device status line for a continuation pack in a multipack
family if the base pack is absent. The warning indication NO BP is displayed. 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
if the continuation packs are usable from another backup directory.
OL PK 245
PK 245*C [000240:000245:NO BP] #2 SYSX
Disk Unit: Mirrored Member

This example can appear on all systems that support the Mirrored Disk Pooling
Facility (MDPF). The display indicates that the pack has been assigned to the spare
disk pool for a mirrored disk set.
OL PK 408
PK 408*B [123456:000000] #1 S P A R E
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.
Disk Unit: Mirrored Member with BY ADDRESS Read Distribution

This example with a two member mirrored set illustrates a BY ADDRESS read
distribution setting with a Stripe Size equal to 1,234,567 sectors:
OL PK 1673
PK 1673*B M c [161200] #1 MYDISK (6)

MIRRORS: OFFLINE: 00 ONLINE 02 ON 803,1673, PENDING 00
READ DISTRIBUTION = BY ADDRESS (STRIPE SIZE = 1234567 SECTORS)
SCSI/805 SCSI PACK
READ/WRITE IOTIMER = 80 SECONDS (MCP DEFAULT)
CAPACITY: 4,475,653 SECTORS
SECTOR SIZE: 180 BYTES
CTL FIRMWARE STATUS
1673 2441 ONLINE
416 8600 0395-514

Disk Unit: Mirrored Member with DONTREAD and REMOTEDISK

This example shows a mirrored member. The statement beginning with BIASED
AWAY indicates that the disk is a remote disk for which DONTREAD is set:
OL PK 19100
PK 19100*B M c t [200100] #1 DMPACK (102)

FAMILY CREATED ON: Tuesday, June 7, 2005 AT 21:33:47
SCSI/2001E-81 PACK
READ/WRITE IOTIMER = 5 SECONDS
SECTOR SIZE: 512 BYTES (180-BYTE SECTORS BEING EMULATED)
BIASED AWAY FROM MIRRORED READ DISTRIBUTION DUE TO:
DONTREAD AND REMOTEDISK SPECIFICATIONS
CTL FIRMWARE STATUS
1100 1439 ONLINE
6100 1439 ONLINE
Disk Unit: Non-Mirrored Disk with REMOTEDISK

This example shows a unit that is not mirrored. The UNIT IS REMOTE line indicates
that the unit is designated as a remote disk. (For local disks, this line does not
appear. There is no corresponding UNIT IS LOCAL line.)
OL PK 19100
PK 19100*B c t [200100] #1 DMPACK (102)

FAMILY CREATED ON: Tuesday, May 11, 2004 AT 21:33:47
SCSI/2001E-81 PACK
SECTOR SIZE: 512 BYTES (180-BYTE SECTORS BEING EMULATED)
UNIT IS REMOTE
CTL FIRMWARE STATUS
1100 1439 ONLINE
6100 1439 ONLINE
Disk Unit: Memory Disk

The following example shows a command and display for a memory disk:
OL DK 255
DK 255*B [000255] #1 MEMORYDISK (2)

CAPACITY: 34,952 SECTORS (6,291,360 BYTES)
8600 0395-514 417

Disk Unit: Resized Disk Unit

The following example shows a command and display for a 3557 disk pack that has
been resized to the capacity of a 3019 disk pack:
OL PK 701
PK 701*B cr [161200] #1 MYDISK (35)

SCSI/3019 RESIZED (3557 SCSI PACK)
READ/WRITE IOTIMER = 80 SECONDS (MCP DEFAULT)
RESIZED CAPACITY: 16,777,215 SECTORS (3,019,898,700 BYTES)
NATIVE CAPACITY: 19,761,195 SECTORS (3,557,015,100 BYTES)
SECTOR SIZE: 180 BYTES
CTL FIRMWARE STATUS
10161 1439 ONLINE
6161 1439 ONLINE
Disk Unit: USS 5100 Disk Pack

The following example shows a command and display for a USS 5100 disk pack:
OL PK 15182
PK 15182*B M [200182] #1 HLPK (9)

MIRRORS: OFFLINE: 00, ONLINE: 02 ON 15182,15184, PENDING: 00
HALT/LOAD FAMILY
SCSI/1545-192 PACK
CABINET ID: 752 (DECIMAL), LOGICAL VOLUME ID: 10 (HEX)
CTL FIRMWARE STATUS
2506 0027 ONLINE
2516 0027 ONLINE
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:
CABINET ID: UNKNOWN, LOGICAL VOLUME ID: UNKNOWN
Disk Unit: Non-180-Byte Disk

For packs whose sector size is not 180 bytes, the OL display indicates whether the
180-byte emulation in effect for that pack is VSS-1 or VSS-2. The display also
identifies a pack that has a VSS-2 format directory or has file space allocated on
418 8600 0395-514

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 non-180-byte disk using VSS-2 emulation:
PK 19281*B c t [000281] #1 KEYSTONE (1)

FAMILY CREATED ON: Monday, February 7, 2005 AT 19:37:01
SCSI/4003 PACK
CAPACITY: 22,239,490 LOGICAL SECTORS (4,003,018,200 BYTES)
PHYSICAL SECTOR SIZE: 512 BYTES
LOGICAL SECTOR SIZE: 180 BYTES IN VSS-2 FORMAT
DIRECTORY FORMAT: VSS-2
Disk Space Allocated On VSS-2 Boundaries
CTL FIRMWARE STATUS
1281 5514 ONLINE
6281 5514 ONLINE
Following is a display for a non-180-byte disk using VSS-1 emulation:
PK 19282*B c t [000282] #1 DBBACKUP (1)

SCSI/6004 PACK
CAPACITY: 33,359,235 LOGICAL SECTORS (6,004,662,300 BYTES)
PHYSICAL SECTOR SIZE: 512 BYTES
LOGICAL SECTOR SIZE: 180 BYTES IN VSS-1 FORMAT
CTL FIRMWARE STATUS
1282 5514 ONLINE
6282 5514 ONLINE
Following is a display for a 180-byte disk that was reconfigured using the RC
(Reconfigure Disk) command with the VSS = VSS2 option:
PK 19283*B c t [000283] #1 BENCH (1)

SCSI/3565 PACK
DIRECTORY FORMAT: VSS-2
Disk Space Allocated On VSS-2 Boundaries
CTL FIRMWARE STATUS
1281 5514 ONLINE
6281 5514 ONLINE
8600 0395-514 419

ODT Examples: Restricted and Nonrestricted

These examples show commands displays for restricted and nonrestricted ODTs.
The following display is for a nonrestricted ODT:
OL SC 2
SC 2 S C R A T C H
CTL STATUS
2001 ONLINE
The next display is for a restricted ODT:
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
SC 3 (MCP) COMS/ODT/DRIVER RESTRICTED

CTL STATUS
2001 ONLINE
ODT Examples: IOP Machine

The ODT of an IOP machine is a Java application called Web Enabler. It
communicates with its control through a socket over TCP/IP. In a redundant
configuration, it communicates with two controls in two IOPs over two networks.
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.
420 8600 0395-514

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
Line Printer Example

This example shows a command and display for a line printer:
OL LP 11
LP 11 S C R A T C H EBCDIC96
MAXIMUM BLOCKSIZE 132 BYTES
B9246-12 PRINTER
CTL STATUS
1301 ONLINE
8600 0395-514 421

OP (Options)
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.
Num Option Num Option
1 OPEN 25 MOREBACKUPFILES
2 TERMINATE 26 LOGPOSITIONING
3 NOCHECK 27 SERIALNUMBER
4 LPBDONLY 28 ARCHIVING
5 AUTORM 29 CDRUNITNUMBER
6 DIAGNOSTICS 30 LIBRARYDEBUG
7 Not in use 31 IORANGECHECK
8 AUTORECOVERY 32 MORETASKS
9 DUPSUPERVISOR 33 KEYEDIOII
10 DUPINTRINSICS 34 MIRRORING
11 TRANSWARNINGS 35 DIAGNOSTICDUMP
12 AUTODC 36 AUDIT
13 NODUMP 37 FILESATURATION
14 Not in use 38 EOTSTATISTICS
422 8600 0395-514

OP (Options)
Num Option Num Option
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.
8600 0395-514 423

OP (Options)
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
424 8600 0395-514

OP (Options)
termination, unsuccessful I/O operation, rejected request, DISCONNECT (first error),

or DSR NOT PRESENT (first error).
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.
DUPINTRINSICS (option 10)

If a file titled <file name> is designated as the intrinsics file and this option is set, at
halt/load time the system uses the code file titled <file name>/FMLYINXnnn as the
intrinsics file. If the option is reset, the code file <file name> is used as the intrinsics
file at halt/load time. 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 intrinsics file on each halt/load pack and name the file with the
appropriate suffix.
For more information on the intrinsics file, refer to the SI (System Intrinsics)
command.
TRANSWARNINGS (option 11)

If this option is set and a program is given translation warnings, then the translation
warnings are displayed and the code file is marked as having been given translation
warnings. (Translation warnings are issued when a file is opened and there is a risk
of invalid data access and/or data corruption.)
8600 0395-514 425

OP (Options)
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.
AUTODC (option 12)

If this option is set, data comm is automatically initiated if it is not running when an
MCS performs a station attach DCWRITE operation. For additional information about
AUTODC, refer to the ID <unit number> explanation in the ID (Initialize Data
Comm) command.
The AUTODC option works as documented provided a station is defined in the

SYSTEM/DATACOMINFO file as belonging to an MCS.
NODUMP (option 13)

If this option is set, the system does not try to take memory dumps. However, this
option does not prevent the system from taking a memory dump if someone
requests the memory dump by using the ??DUMP system command, a SETSTATUS
DUMP call, or the MARC system software. Potential nonfatal dumps are denoted by a
display at the supervisory console and logged. The source of a fatal dump is listed in
a system display at halt/load time. If the option is reset, dumps are taken in the
normal fashion.
For more information about memory dump processing, refer to Memory Dump
Processing.
AUTORUNNING (option 15)

When this option is set, certain default actions are taken in response to some of the
RSVP conditions that can arise during initialization. For some of these default actions,
instead of waiting for you to reply, the RSVP message and the following message are
displayed:
'OP AUTORUNNING' IS SET, REPLY <reply> ASSUMED
The reply indicates the default action selected by the system.
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.
426 8600 0395-514

OP (Options)
All family complements proceed without RSVPs. If FLATREADER discovers bad

records in a directory, it rebuilds the directory. If a disk family with duplicated
directories is being complemented and one or more of the disks with duplicate
directories is missing, the family is readied for use without the missing
directories. If a site uses cataloging and a family is found to be missing from
the volume library, the RSVP is skipped with an assumed OF (Optional File)
response.
If the JOBDESC family cannot be found, the DL specification defaults to the
halt/load family.
Note: If the OKTIMEANDDATE option is set, time and date verification is still
required if AUTORUNNING is set.
System memory dumps take one of the following default actions when you set the
AUTORUNNING option:
If no dumpdisk files are specified, the dump is not taken.

If a dumpdisk file exists and is not full, the memory dump is automatically
captured in the file. When the dump is completed, the system initiates the
DUMPDISKMASTER independent runner to unload the dump to a memory
dump image disk file for analysis using the Dumpanalyzer utility. If DL
DPFILES is specified, the dump is unloaded to the specified family. If DPFILES
is not specified, the dump is unloaded to the halt/load family. If an error
occurs unloading the memory dump, a message is displayed and the dump is
skipped, leaving the dumpdisk file intact.
The memory dump is discontinued if it encounters problems such as when the
dumpdisk file has insufficient capacity for the dump, or a fatal I/O error
occurs while writing the dump.
For more information about creating and unloading dumpdisk files, refer to the CM
(Change MCP), DN (Dump Name), DF (Empty Dumpdisk File), DL (Disk Location),
and MDT (Memory Dump Type) commands. Also, refer to Memory Dump Processing.
For more information about the Dumpanalyzer utility, refer to the System Software
Utilities Manual.
CRUNCH (option 16)

If this option is set, code files and backup disk files are automatically crunched when
they are closed. Furthermore, when this option is set, you can crunch other files by
using the CRUNCH option in the CLOSE statement. If this option is reset, no file can
be crunched, even if a crunch is explicitly requested.
BACKUPBYJOBNR (option 17)

If this option is set, print requests are selected for printing by job number. If this
option is reset, print requests are selected for printing according to the criteria
specified in the PS SELECTION command.
PDTODISK (option 18)

This option is ignored whenever the program executing the dump has the TODISK or
TOPRINTER bit set in its OPTION task attribute. Otherwise, it operates as follows:
8600 0395-514 427

OP (Options)
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.
NOFETCH (option 19)

If this option is set, you need not enter an OK (Reactivate) command to reactivate a
WFL job containing a FETCH statement.
RESOURCECHECK (option 20)

If this option is set, resource limits established by queues are enforced (refer to the
tape specification parameter in the MQ (Make or Modify Queue) command. Before
jobs are admitted into queues, the RESOURCE task attributes are checked to ensure
they do not exceed the established limits. If the option is reset, the limits are
ignored. Refer to the Task Management Programming Guide for a detailed
explanation of this option.
DRTRRESTRICT (option 21)

If this option is set, the system time or date cannot be changed by the DR (Date
Reset) command, the TR (Time Reset) command, or the corresponding SETSTATUS
calls. However, the TR command or call is permitted to change the time zone.
DIRDEBUG (option 22)

Note: This option is intended for use as directed by Unisys support personnel only.
It is not intended for use by customers.
CATALOGING (option 23)

The CATALOGING option is tested during disk initialization after a halt/load. If this
option is set, the CATALOGLEVEL attribute is initialized to the value of the system
option CATALOGLEVELSET; if it is reset, CATALOGLEVEL is set to 0. Refer to the
SYSOPS (System Options) command for more information.
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.
OKTIMEANDDATE (option 24)

This option requires you to verify the system TIME and DATE values at halt/load
time.
Note: Setting OKTIMEANDDATE overrides the setting of AUTORUNNING.
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
428 8600 0395-514

OP (Options)
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.
MOREBACKUPFILES (option 25)

This option controls the maximum number of printer backup files that can be created
by any one task, and affects the format of printer backup filenames.
If MOREBACKUPFILES is set, a single task can create up to 549,755,813,887 printer

backup files. Printer backup filenames default to a format of
*BD/<7 digit job number>/<7 digit mix number>/...<12 digit file number>/<file
name>
If MOREBACKUPFILES is reset, a single task can create up to 1000 printer backup

files. Printer backup filenames default to a format of
*BD/<7 digit job number>/<7 digit mix number>/...<3 digit file number><file
name>
LOGPOSITIONING (option 26)

When a parity I/O error on a tape occurs, the system tries to recover from the error
by repositioning the tape and retrying the I/O process. If this option is set, the
system logs these I/Os. If an I/O error occurs during the repositioning of a tape, you
can use the log records that are written to analyze why the recovery was not
successful.
SERIALNUMBER (option 27)

If this option is set, scratch tapes are not assigned to output files unless the file
SERIALNO attribute matches the tape serial number, or the file SCRATCHPOOL
attribute matches the scratch pool of a scratch tape, or the tape is specified in an OU
(Output Unit) command.
ARCHIVING (option 28)

This option enables the archiving function of the catalog subsystem. If this option is
set and the catalog level of the system is greater than 0 (zero), an archive log is
created. The name of the archive log is ARCHIVELOG/<date>/<time>, where
<date> and <time> are the creation date and creation time of the file, respectively.
If the archive log cannot be set up, the system automatically resets the option.
8600 0395-514 429

OP (Options)
CDRUNITNUMBER (option 29)

If this option is set to true, assignment to a scratch CD-disk occurs only if the unit
number for a specific device is specified using the file attribute UNITNO or if the unit
number is specified in an OU (Output Unit) command.
LIBRARYDEBUG (option 30)

IORANGECHECK (option 31)

This option verifies that the disk address requested for an I/O is within the range of
one of the areas of the file. For IORANGECHECK to have any effect, the compile-time
option DIAGNOSTICS must be set when the system is being compiled.
MORETASKS (option 32)

This option specifies whether expanded mix numbers and stack numbers are
permitted. When MORETASKS is SET, you can use the MAX (Maximums) system
command to specify up to the maximum values for mix and stack numbers. When
MORETASKS is RESET, the mix number limit is 9999 and the tack number limit is
4095.
Note: Changes to the MORETASKS option to not take effect until the next halt/load.
For more information, refer to the MAX (Maximums) command.
KEYEDIOII (option 33)

Setting this option ensures that all new files created with FILEORGANIZATION =
VALUE (INDEXED), VALUE (INDEXEDNOTRESTRICTED), or VALUE (KEYEDIOII) are
linked to the SYSTEM/KEYEDIOII library and are created as KEYEDIOII files. Existing
files are correctly linked to either SYSTEM/KEYEDIO or SYSTEM/KEYEDIOII
depending on how they were created. Therefore, you can read and update both
KEYEDIO and KEYEDIOII files, but all new files are KEYEDIOII.
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.
MIRRORING (option 34)

This option allows disk mirroring to occur after the next halt/load. At that time, a
mirror information table (MIT) and other structures needed for disk mirroring are
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.
430 8600 0395-514

OP (Options)
The option can be changed, subject to the following conditions:
An OP + MIRRORING command is ignored if mirroring is already in effect.

An OP MIRRORING command is rejected if any mirrored sets are currently
present in the system. All mirrored sets must first either be closed or be
reduced to single packs with the MIRROR RELEASE command.
DIAGNOSTICDUMP (option 35)
If set, this option enables certain other memory dump calls to be made for diagnostic
purposes. Also, the system provides maximum diagnostic information when an
exception condition occurs.
AUDIT (option 36)

FILESATURATION (option 37)

If set, this option causes the following warning message to be issued whenever the
system allocates the last area of a disk file:
WARNING, ALLOCATING LAST ROW OF FILE <file name>
The preceding message is subject to the following restrictions:
It applies to programmer files, including ordinary data files, printer backup

files, and compiler code files.
It does not apply to internal system files such as SYSTEM/SUMLOG or library
maintenance files.
It does not necessarily mean that the file is almost full. Some areas might
have been skipped if the file was written randomly.
For information about how the system determines the last possible area of a disk file,
refer to the LASTACCESSIBLEAREA description in the File Attributes Programming
Reference Manual.
EOTSTATISTICS (option 38)

If this option is set, end-of-task (EOT) statistics for each task are displayed on the
ODT in the following format:
<mix number> EOT TIMES: ET=hhh:mm:ss.s PT=hhh:mm:ss.s IO=hhh:mm:ss.s
In this display, hhh denotes the hours, mm denotes the minutes, and ss.s denotes
the seconds (rounded to the nearest tenth).
STRICTSCHED (option 39)

The STRICTSCHED option alters the behavior of SF 3 (FACTOR). Refer to the SF
(Set Factor) command for details.
Note: Because of the increased likelihood of the scheduling of new tasks, setting
STRICTSCHED is not recommended for most systems.
8600 0395-514 431

OP (Options)
NETRECOVERY (option 40)

If this option is set, during halt/load processing the system determines the last state
of the currently selected BNA. If the state was not running, BNA is not initiated. If
BNA was running before the halt/load, BNA libraries and stacks are initiated.
GRAPHDEBUG (option 41)

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.
ISCDEBUG (option 42)

IODIAGNOSTICS (option 43)

PORTDEBUG (option 44)

If this option is set on an operating system that was compiled with the compile-time
option INTERNAL set (a diagnostic system), port debug trace information is written
to the SYSTEM/SUMLOG file in BNA debug log records. You can examine this
information by running LOGANALYZER.
USECATDEFAULT (option 45)

The value of this option has meaning only on an operating system that is running
CATALOGING. If this option is set, the default value of the file attribute USECATALOG
is TRUE.
CATTEST (option 46)

MCPTEST (option 47)

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.
432 8600 0395-514

OP (Options)
OP
1 OPEN 2*TERMINATE 3 NOCHECK 4*LPBDONLY

5*AUTORM 6 DIAGNOSTICS 8*AUTORECOVERY 9 DUPSUPERVISOR
10 DUPINTRINSICS 11 TRANSWARNINGS 12*AUTODC 13 NODUMP
15 AUTORUNNING 16*CRUNCH 17 BACKUPBYJOBNR 18 PDTODISK
19*NOFETCH 20 RESOURCECHECK 21 DRTRRESTRICT 22 DIRDEBUG
23*CATALOGING 24*OKTIMEANDDATE 25 MOREBACKUPFILES 26*LOGPOSITIONING
27*SERIALNUMBER 28*ARCHIVING 29 CDRUNITNUMBER 31 IORANGECHECK
33*KEYEDIOII 34*MIRRORING 35*DIAGNOSTICDUMP 36 AUDIT
37 FILESATURATION 38 EOTSTATISTICS 39 STRICTSCHED 40*NETRECOVERY
41 GRAPHDEBUG 42 ISCDEBUG 43 IODIAGNOSTICS 44 PORTDEBUG
45 USECATDEFAULT 46 CATTEST 47 MCPTEST
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 -
------------------------------- RESET OPTIONS ------------------------------

1 OPEN 3 NOCHECK 6 DIAGNOSTICS
9 DUPSUPERVISOR 10 DUPINTRINSICS 11 TRANSWARNINGS
13 NODUMP 15 AUTORUNNING 17 BACKUPBYJOBNR
18 PDTODISK 20 RESOURCECHECK 22 DIRDEBUG
25 MOREBACKUPFILES 31 IORANGECHECK 36 AUDIT
37 FILESATURATION 38 EOTSTATISTICS 39 STRICTSCHED
41 GRAPHDEBUG 42 ISCDEBUG 43 IODIAGNOSTICS
44 PORTDEBUG 45 USECATDEFAULT 46 CATTEST
47 MCPTEST
Example 4
These commands set or reset particular options:
OP + 3
3 NOCHECK SET
OP - 3
3 NOCHECK RESET
8600 0395-514 433

OPLOCKTIMEOUT
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.)
434 8600 0395-514

OPLOCKTIMEOUT
The defaults are
OPLOCKTIMEOUT = 30, 10
The minimum values are
OPLOCKTIMEOUT = 10, 3
Note: Time-out values specified by OPLOCKTIMEOUT take effect immediately.
8600 0395-514 435

OT (Inspect Stack Cell)

The OT (Inspect Stack Cell) command displays the contents of the specified stack
cell for the task.
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
Stack 11B Offset 2 = 0 00000000002A (Hex) 42 (Decimal)
Example 2
8904 OT 5
Stack 11E Offset 5 = 1 C C00000000739 (Hex)
Note: The selected stack word in this example contains a nonzero extension (1).
Example 3
8904 OT 6
Stack 11F Offset 6 = 0 000000001000 (Hex) 4,096 (Decimal)
436 8600 0395-514

OU (Output Unit)
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.
<mix number list> OU MT

When you use this form of the command in response to a MT <unit number>
RECOPY REQUIRED <filename> RSVP message, library maintenance requests a new
tape volume and then recopies the file. When you use this form of the command in
response to a <filename> REQUIRES . . . BACKUP . . . RSVP message, it causes
the backup file opened by the specified task to be written to any available tape drive.
If a substitute backup medium was established for tape by the SB (Substitute
Backup) command, the output goes to the substitute medium instead.
<mix number list> OU PK

Has no effect on nonbackup files. Controls the destination for backup output files as
follows:
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.
8600 0395-514 437

OU (Output Unit)
<mix number list> OU DK

Has no effect on nonbackup files. Controls the destination for backup output files as
follows:
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.
<mix number list> OU LP <unit number>

Directs the output files to a specific line printer.
<mix number list> OU SC <unit number>

Directs the output files to a specific ODT.
<mix number list> OU CD <unit number>

Directs the output files to a specific scratch CD-disk.
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:
1985 FILEA REQUIRES MT
If the program requests a backup medium, backup information is appended to the

message. If the program requests a particular tape serial number or density, the
specified serial number or density is appended to the message.
The operator can enter an OU response; for example:
2121 OU MT 28
If the OU response specifies an inappropriate device, an error message is displayed.

Two possible messages are the following:
DIRECT FILE CANNOT BACKUP
NEED AN OUTPUT TAPE FOR OUMT
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
438 8600 0395-514

OU (Output Unit)
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.
In the second message, an OU MT response was unsuccessful because no suitable

tape is available.

Other messages that accept an OU response are as follows:
CATALOG FAMILY MISSING <family name>
<device ID> TYPE DISAGREES WITH KIND, REQUIRES <device list>
<device ID> UNABLE TO LOAD TRAIN, SELECT ANOTHER PRINTER
<device ID> REQUIRES FORMID <text>
<device ID> MUST BE UNFORMED <device list>
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:
OU REJECTED, REQUIRES <device list>
The RSVP message that requested the OU command is reissued.
8600 0395-514 439

PARTIALSETS
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.
PARTIALSETS <family name> <family name>

PSETS <family name> <family name>
This command displays a list of mirrored members from the specified mirror sets.
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.
PARTIALSETS DISK00 ZEBRA
DISK00
#1 ( 802) #2 ( 184) #3 ( 272)
ZEBRA
#7 ( 800)
440 8600 0395-514

PB (Print Backup)
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.
8600 0395-514 441

PDIR (Process Directory)

The PDIR (Process Directory) command initiates the SYSTEM/PDIR program and
enables you to search for files by using a wild-card string and file attributes. You can
also specify sort preferences, and direct the output to a printer file, disk file, or
remote file.
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.
PDIR *= SELECT SECTORS > 5000 SORT - SECTORS
Example 2
This example lists all usercoded files on PACK that have a FILEKIND of
MCPCODEFILE:
PDIR (=)= ON PACK SELECT FILEKIND = 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:
PDIR *= SORT - SECTORS SELECT SECTORS > 10000: FILE LARGE/FILES
Example 4
This example opens a remote file and routes it to a particular station:
PDIR MYFILES/=:REM MYSTATION/1
Example 5
This example opens a remote file at a station at host MP456:
PDIR MYFILES/=:REM MYSTATION/1 AT MP456
442 8600 0395-514

PER (Peripheral Status)

The PER (Peripheral Status) command displays the status of peripheral units.
Syntax
<unit number range>
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 <unit number range>

The PER display shows only units in the range from the first unit number to the
second unit number, inclusive. The second unit number must be greater than the
first unit number. If you specify only one unit number, the system displays
information only for units whose unit number is equal to or greater than the specified
unit number.
PER <device type>

Displays the status of all peripheral units of the specified device type.
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).
PER <device type> =

PER <device type>
Displays the status of all peripheral units of the specified device type, including
unlabeled and unready devices.
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.
8600 0395-514 443

Message Explanation
BLASTED Indicates that the pack or CD-ROM was cleared and

must be closed and readied before being used or
indicates that the pack was released from a mirrored
set. In either case, you can reconfigure disk packs
without having to close and ready them again.
CLOSED Indicates that the pack or CD-ROM was closed with

the CLOSE (Close Pack) command.
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.
NOT READY Indicates that the unit is physically not ready.
RESERVED Indicates that the pack has been taken offline with
the UR (Unit Reserved) command.
SAVED Indicates that the pack or CD-ROM has been marked

with the SV (Save) command.
SCRATCH Indicates that the pack has been purged with the PG
(Purge) command.
UNINITIALIZED Indicates that the pack has not been reconfigured

with an RC (Reconfigure Disk) command.
UNLABELED, LABEL Indicates that no label information exists in memory

ERROR for the pack. One of the following actions has
occurred:
The pack has not been initialized.
The directory complementor failed while it was
reading the directories on the pack.
An error occurred in one of the following
commands: LB (Relabel Pack), PG (Purge), or RC
(Reconfigure Disk).
444 8600 0395-514

Examples
Example 1
This example shows a response for a PER MT command:
PER MT
44*C [DMTAPE] ST9940 C #1/1 1:1 <11/23/2004> DMSIITAPETEST2/TAPESET

50*H D [005050] 36TRK C #1 1:0 <11/18/2004> ABC/FILE000
51*\ [DDSDDS] DDS3 #1 1:0 <11/24/2004> DMSIIFILES/FILE000
52*H [000052] 36TRK C #1 1:0 <11/18/2004> XYZ/FILE000
56*H 38000 UNLABELLED
59*H R [UNISYS] 38000 C #1 1:0 <01/20/2001> MYTAPE/FILE000
91*D [007248] DLT40 C S C R A T C H POOL: DLTTAPES
97*H [MT57 ] 38000 C #1 1:0 COMPRESSION MISMATCH, CAN'T READ (SEE OL)
116 P SAVED
180*H [DMTAPE] ST9840CC #1/1 1:1 <11/23/2004> DMSIITAPETEST2/TAPESET
240@H [JJTAPE] ST9840 C #1 1:0 <11/19/2004> DMSSTUFF/FILE000
300*8 K[123456] 11000 #1/1 1:0 <08/17/2000> FILEA
302*H [234567] 38000 S C R A T C H POOL: ROOM
303*H [345678] 38000 #1 1:0 <11/04/2000> DCW (FROM POOL TWH)
The example shows the following information:
The unit number
A write-enabled flag
Symbol Description
* Indicates that the tape is write enabled.
@ Indicates that the tape is write enabled but has been locked by the
LOCKEDFILE file attribute.
A media-type flag
Symbol Description
8 Indicates an 8-millimeter cartridge tape.
9 Indicates undefined media.
H Indicates a half-inch cartridge tape and similar cartridge tape.
P Indicates a 9-track, phase-encoded (PE) or group-coded recording

(GCR) tape.
8600 0395-514 445

Symbol Description
Q Indicates a quarter-inch cartridge tape.
D Indicates a digital linear tape (DLT).
4 Indicates a 4-millimeter cartridge tape.
A Indicates an advanced intelligent tape (AIT).
Optional flags
Value Description
\ Indicates that the mounted volume is listed in the Volume Library.
D Indicates that the mounted volume is listed in the Volume Directory.
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.
The serial number in brackets ([ ])

The mix number in parentheses, showing that the tape is in use by the
program with that mix number
The tape density
The letter C if compression is being used
The file section number
The volume sequence number preceded by a slash (/), if the tape has ANSI87
tape labels
The cycle number and version number separated by a colon (:)
The creation date in angle brackets (<>)
The file name of a file on the tape or the following designation
Name Description
SAVED Indicates that the tape unit is saved.
SCRATCH Indicates that the tape has been purged or contains an

ordinary data file that is expired.
UNLABELLED Indicates that the tape does not have a recognizable label.
446 8600 0395-514

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, is the block size in the label:
BLOCKSIZE TOO LARGE, CAN'T READ
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
-------------------------------- PK STATUS -----------------------------

96*B [000097] (MCP) #1 DAMISDB (1) (TO BE SAVED)
97*B\ c [000096] #1 SSDMASTER (11)
98*C [000098:000097:096] #2 DAMISDB (0)
99 U C L O S E D
100*U U N I N I T I A L I Z E D
103 B t [000099] #1 TRIAL (1)
112 B R [002112] #1 HAZARD (0)
160*B c [682180] #1 DMPACK (418)
200*B (c) [000200] #1 CACHE1 (1)
201*B c [000201] #1 CACHE2 (1)
202*B c- [000202] #1 CACHE3 (1)
203*B Mc [659003] #1 DISK (17)
210*B [123456:000000] #1 S P A R E
211*B [659009:000000] #1 S C R A T C H
245*C [000245:000240: NO BP] #2 GOOD240
701*C ctr[161200] #1 DK7434 (0)
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.
8600 0395-514 447

Field Description
1 This field displays the unit number.
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).
5 A backslash (\) designates a disk entered in the volume library.
6 The letter R if security restrictions were imposed on the pack. For more
information, refer to RESTRICT (Set Restrictions).
7 This field is blank.
8 The letter M indicates if the pack is mirrored. If a mirrored set is in the

process of coming online but is waiting for another previously online
member, it is considered a partial mirrored set. These packs are marked
with a lowercase m instead of an uppercase M. This display does not
show such an example.
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.
10 The letter t indicates that a user-specified I/O time limit is assigned to

the disk.
448 8600 0395-514

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.
13 The family index number, from 1 through 255.
14 The family name.
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
--------------------------- DK STATUS -------------------------------

255*B [000255] #1 MEMDISK (27)
8600 0395-514 449

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 -
141 DC NOT AVAILABLE TO GROUP
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
150*B [207150] #1 DISK (27)

151*B [206151] #1 TESTPACK (0)
153*B [207153] #1 PACK (*)
162*B [207162] #1 DBUNIT (*)
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
450 8600 0395-514

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
1 Indicates the external unit number of the printer.
2 Optional field that shows special I/O status enclosed in angle

brackets (<>).
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.
4 Indicates the status of the printer or who is controlling the printer.

Terms used in this field include TO BE SAVED, SAVED, LOCKED, S C
R A T C H, NOT READY, the file title, and the name of the print server
if a file is printing.
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
8600 0395-514 451

156 (ICP10-A, LEVEL: 7.1) ACTIVE, COMMUNICATING

161 (ICPII, LEVEL: 0.2) ACTIVE, COMMUNICATING
210 (CNP, LEVEL: 5.1) ACTIVE, COMMUNICATING
The following table describes the display.
Entry Description
1 NP number.
2 The ICP type and its firmware level.

The first number of the firmware level describes its DLP type, and the
second number describes the functional level. If the system cannot
determine the ICP type, the display is presented as ICP, LEVEL: NOT
AVAILABLE.
On NX5600, NX5800, NX6820, and NX6830 systems, a type of CNP
designates a PCI-Bridge.
3 The actual status of the NP.
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
------------------------ VC STATUS ----------------------------------

200 (1100) VC_FILE
201 (1105) VC_FILE
202 (1105) VC_FILE
203 (1105) VC_FILE
204 (1105) VC_FILE
205 (1105) VC_FILE
206 (1105) VC_FILE
207 (1105) VC_FILE
208 (1105) VC_FILE
209 (1105) VC_FILE
210 (1105) VC_FILE
211 (1105) VC_FILE
212 (1105) VC_FILE
213 (1105) VC_FILE
214 (1105) VC_FILE
215 (1105) VC_FILE
216 (1105) VC_FILE
217 (1105) VC_FILE
218 (1105) VC_FILE
452 8600 0395-514

219 (1105) VC_FILE

220 (1105) VC_FILE
221 (1105) VC_FILE
222 (1105) VC_FILE
223 (1105) VC_FILE
224 (1105) VC_FILE
225 (1105) VC_FILE
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
---------------------------- TSP STATUS -----------------------------

200 (1100) TSPFILE
201 (1101) TSPFILE
300 S C R A T C H
301 S C R A T C H
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 -
----------------------- TSP STATUS -------------------------------

200 (1234) TSP_FILE
201 (1234) TSP_FILE
100 RESERVED
101 RESERVED
Example 13
This example shows the response for a PER command with a unit range:
PER 100-199 PK
---------------------------------- PK STATUS -------------------------------

100 C c [008556:400103:14103] #3 NI00 (9)
101*C c [000226:191232:19132] #2 PCBACKUP (0)
102*B [008370] #1 TOMSDISK (0)
103*B c [000659] #1 Z103Z1971 (0)
8600 0395-514 453

PF (Print Fetch)
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:
REQUIRES FETCH, QUEUE = <queue number>
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
<mix number> DS Terminates the job
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.
See OP (Options) for more information about the NOFETCH option.
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.
454 8600 0395-514

PF (Print Fetch)
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 50 10:11 X
REQUIRES FETCH, QUEUE = 0
3738 PF
REMOVE TAPE 36451 AND MOUNT ON MT34, BACKUP TO PK173

If a fetch job is started from a queue with an FS (Force Schedule) command, the
system ignores the fetch statement
8600 0395-514 455

PG (Purge)
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.


THIS UNIT.
command again.
Syntax
456 8600 0395-514

PG (Purge)
<density>
<scratch pool>
<scratch pool name>
<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.
8600 0395-514 457

PG (Purge)
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.
PG MT <unit number list> (<density>)

Specifies the density of the tape in bytes per inch (a numeric value) or as a density
mnemonic abbreviation (an alphanumeric string). If the density is specified, it
applies to all tapes mounted on the units in the unit number list. Only certain tape
drives permit you to change tape density. Refer to the documentation for your tape
drive to see if it fits into this category.
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.
PG MT <unit number list> <scratch pool>

Purges the volume or volumes mounted on the specified tape unit or units and
assigns it or them to the designated scratch pool. Refer to the File Attributes
Programming Reference Manual for more information.
PG MT <unit number list> COMPRESSED

Specifies that the system is to write a label that indicates compression was
requested. If the tape is mounted on a device that does not support compression,
the system displays the following message:
MTnnn UNIT DOES NOT SUPPORT COMPRESSION
For more information about this option, refer to Considerations for Use.
PG MT <unit number list> NONCOMPRESSED

Specifies that the system is to write a tape label that indicates compression was not
requested.
PGL MT <unit number list>

PGL MT <unit number list> ( <density> )
PGL MT <unit number list> SCRATCHPOOL = <scratch pool name>
PGL MT <unit number list> COMPRESSED
PGL MT <unit number list> NONCOMPRESSED
Have the same effect as the PG command except that they lock the tape units after
purging them so that no job can automatically acquire them as scratch tapes. To
unlock the units, you must ready them by using the RY (Ready) command. The
locked status of a tape unit is not preserved over a halt/load operation.
458 8600 0395-514

PG (Purge)
PG PK <unit number list>

Labels the disk packs identified by the unit numbers as scratch packs that are
available only to maintenance programs.
If the disk packs have OWNER identification, you must verify purge permission
through an OK response to an RSVP message.

automatic display of current system status information by entering an ADM
(Automatic Display Mode) command, the system displays the waiting entries. For
example:
<mix number> PK <pack number> IS [<serial number>] , OWNER=<owner>; OK TO RC
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:
<mix number> AX OLDNAME = <family name>

automatic display of current system status information by entering an ADM
(Automatic Display Mode) command, the system displays the waiting entries. For
example:
<mix number> PK <pack number> IS : SERIAL=[<serial number>] PACKNAME=<pack name>
<mix number> ACCEPT: OLDNAME = <pack name>
Reply as follows:
<mix number> AX OLDNAME = <pack name>
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:
PKnn INCORRECT OLDNAME ENTERED - COMMAND NOT DONE
PG PK <unit number list> OLDNAME = <oldname list>

Labels the disks identified by the unit number list as scratch disks after checking that
the old names of the disk match one of the names in the oldname list.
PG PK <unit number> OWNER = <name>

Labels the disk pack identified by the unit as a scratch pack and sets the OWNER
identification to the specified name.
8600 0395-514 459

PG (Purge)
PG PK <unit number list> SERIAL = <serial number list>

Labels the disks identified by the unit number list as scratch disks and gives them
the serial numbers specified in the serial number list. Each serial number in the list
must be in the range from 1 through 999999. If any of the serial numbers are left
out (if there is a double comma or if there are fewer serial numbers than unit
numbers), the PG process leaves the serial number of the corresponding disks as
they are.
PG PK <unit number list> INIT VSS = VSS1

PG PK <unit number list> INIT VSS = VSS2
Initializes the disks identified by the unit number list in the format specified by the
VSS option and marks the disk volumes as scratch.
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
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
MT 55 WILL BE PURGED COMPRESSED
460 8600 0395-514

PG (Purge)
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
MT 55 WILL BE PURGED 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:
PG MT 55 (38000) POOL = ABC COMP
MT 55 WILL BE PURGED COMPRESSED
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
----------------------------PK STATUS -------------------------------

44*B [000444] #1 PACK (10)
45*B [380003] #1 DISK (94)
47*B [380047:000000] #1 S C R A T C H
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.
PG PK 80-81, 836-837 OLDNAME = (ALPHA, TEST)

SERIAL = (,818181, 836836)
8600 0395-514 461

PG (Purge)
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:
PG PK 100-107 INIT VSS = VSS1 SERIAL = (555100-555107)

CONFIRM PURGE Message for Locked Files
If the first file written to a tape has the LOCKEDFILE attribute set to TRUE, when you
try to purge that tape, the system displays the following message before it performs
the purge operation:
MT nn CONFIRM PURGE <tape name> [<serialno>] OK OR DS
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.
LIBMAINTDIR Tape Directory Disk Files and Associated Disk Files

If you try to purge a library maintenance tape for which a LIBMAINTDIR disk file (or
associated disk file) resides on the DL LIBMAINTDIR disk family, the system displays
the following message and RSVP message and then waits for your response:
MT<unit number> THIS TAPE VOLUME HAS A RESIDENT 'LIBMAINTDIR' TAPE

DIRECTORY DISK FILE: <file name>
MT<unit number> TO LEAVE THIS TAPE AS IS REPLY 'DS'; TO PURGE IT

REMOVE THE 'LIBMAINTDIR' FILE OR REPLY 'OK'
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.
Scratch Pool Considerations

Unlabeled tapes are treated as though they were from the default (no name) pool.
Expired tapes are treated as though they were scratch tapes from the pool specified
in the nonscratch label.
462 8600 0395-514

PG (Purge)
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
If you do not specify a compression keyword and the drive is compression-capable,

the system retains the original compression specification.
Disk Packs and Labels

For disk packs, the PG command does not actually purge any data from the unit.
Instead, the PG command simply changes the name to S C R A T C H, which is a
special name that cannot be used by programs.
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:
PK 526*C L [000526:000000: NO BP] #2 S C R A T C H
Online Mirrored Packs

The PG command is not valid for use with online mirrored packs. Before using the PG
command, you must release the pack with the MIRROR RELEASE command. The PG
command is valid for closed mirrored packs, and packs assigned to the spare disk
pool for the Mirrored Disk Pooling Facility (MDPF), provided you respond OK to the
RSVP message that appears.
Bad Disk Information

The PG command deletes any bad disk information by removing the BADDISK files.
Spare Disk Pool Considerations

If you attempt to purge a disk assigned as a free spare in the spare disk pool for the
Mirrored Disk Pooling Facility (MDPF), the following RSVP message appears:
<mix number> PK<pack number> IS CURRENTLY DESIGNATED AS A SPARE

FOR MIRROR REPLACEMENT. ENTER OK TO CONTINUE WITH
PG,DS TO QUIT. OK WILL REMOVE THE PACK FROM THE
SPARE DISK POOL.
8600 0395-514 463

PG (Purge)
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
<mix number> PK<pack number> IS A SPARE FOR MIRROR REPLACEMENT,

RC/LB/PG NOT DONE
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:
<mix number> PK<pack number> IS CURRENTLY DESIGNATED AS A SPARE

FOR MIRROR REPLACEMENT, A FEATURE NOT ENABLED ON THIS
MACHINE. ENTER OK TO CONTINUE WITH PG, DS TO QUIT.
<mix number> ACCEPT: OK, DS
If you respond OK, the pack is purged, the pack label remains SCRATCH, a system
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.
that does not support MDPF, the PG command clears the FREE SPARE attribute from
the pack label with no operator notification.
464 8600 0395-514

PLI (Periodic Logging Interval)

The PLI (Periodic Logging Interval) command enables logging of usage information
for open files at specified time intervals. The time interval is approximate because
logging actually takes place when the file is next accessed. Interval logging does not
take place for
Direct I/O files

Files with the DUMMYFILE file attribute set to TRUE
Programs running with anonymous file accounting
After a cold-start, the default state of interval logging is disabled.
Syntax
Explanation
PLI
Displays the current logging parameters.
PLI +
Enables interval logging.
PLI
Disables interval logging.
PLI = <time interval>

Sets the interval to the specified number of minutes. The default is 60; the range is
1 through 1440.
Example
PLI
LOG INTERVAL = 100 MINUTES

INTERVAL LOGGING IS DISABLED
8600 0395-514 465

PMIX (Process Mix)
PMIX (Process Mix)

The PMIX (Process Mix) command initiates the SYSTEM/PMIX program and enables
you to search for mix entries with a set of specified characteristics. You can also
specify sort preferences, and direct the output to a printer file, disk file, or remote
file.
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.
PMIX SELECT NAME=""=PRINT="",TYPE <> 8 SHOW MIXNO,NAME,TYPE
Example 2
This example selects all mix entries that have a non-empty usercode. It displays the
name, usercode, and mix number.
PMIX SELECT USERCODE <> """" SHOW NAME, USERCODE, MIXNO
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.
PMIX SELECT NAME=""*SYSTEM=""

SHOW MIXNO, NAME, TASKTYPE, READYQTIME
SORT DESCENDING READYQTIME
466 8600 0395-514

POWER (Power Up/Down)

On systems where the MCP environment is supplied through emulation, the POWER
(Power Up/Down) command causes the MCP environment of the system to be shut
down. This command does not actually affect the system power. Similarly, this
command does not affect any peripherals whose power supplies are connected to the
system.
This command is for MCPvm systems only.
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.
POWER DOWN SYSTEM DELAYOFF

POWER OFF SYSTEM DELAYOFF
POWER DOWN SYSTEM DELAYOFF <delay time>
POWER OFF SYSTEM DELAYOFF <delay time>
Power the system off after the specified number of minutes listed in the delay time
parameter. If you omit the delay time value, the system uses the default delay time
of 20 minutes.
At intervals, the system broadcasts a message to warn users about the impending
loss of power. Messages are sent at the following intervals:
If delay time is greater than 10 minutes, a message is sent every 10 minutes.

If delay time is less than 10 minutes, but greater than 5 minutes, a message
is sent twice with a 5-minute interval between messages.
If delay time is less than 5 minutes, a message is sent twice, with the last
message 1 minute before power loss.
A delay time of zero is not allowed.
8600 0395-514 467

POWER DOWN SYSTEM CANCEL

POWER OFF SYSTEM CANCEL
Cancel a pending shutdown that was requested by the POWER DOWN SYSTEM
DELAYOFF command.
468 8600 0395-514

PQ (Purge Queue)
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
8600 0395-514 469

PR (Priority)
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.
If a task discontinued by the DS command has a priority of 0, the system ignores

any special priority category that the task might have, such as control program
status. As a result, the system gives the task the lowest priority. For more
information about task priorities, refer to the Task Management Programming Guide.
Examples
Example 1
4972,4980 PR 90
Example 2
4975 PR 30
470 8600 0395-514

PRIMITIVE RUN
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
Remote ODT stations enabled through the REMOTESPO (Activate

REMOTESPO) command.
DCKEYIN functions in DCALGOL programs.
Syntax
Explanation
When this command is successful, the operating system responds with the following
message:
<file title> WILL BE INITIATED
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:
The program is initiated without going through job queues.

The program is run without a usercode.
There is no WFL job associated with the program.
Task and file equation are not supported.
8600 0395-514 471

Print System (PS) Introduction

The PS (Print System) commands control the configuration and use of the Print
System (PrintS). Each command deals with a particular aspect of Print System
control, as shown in the following table.
Command Purpose
PS Display the versions of all the Print System softwares,

followed by a list of the Print System commands.
PS ACTIVE Enable or disable printing of site requests, remote

requests, or BNA requests. Also, specify the maximum
number of servers allowed for site, remote, or virtual
requests, or the maximum number of simultaneous
outbound BNA port request file transfers.
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.
PS ASSOCIATE Associate input devices or usercodes with output devices

or device groups, or display all of the existing associations.
The association affects the selection of devices for printing
output.
PS BANNER Display or set the contents and format of the banner

pages that separate the individual files within a print
request.
PS BDIR Displays the directory of printer backup files.
472 8600 0395-514

Command Purpose
PS CONFIGURE Display, assign, modify, or cancel the following

characteristics of output devices and device groups:
The block size the system uses when writing output to
the device.
The use of checkpoints, to reduce the amount of
reprinting needed after a print request is interrupted.
The assignment of a descriptive comment that appears
in PS DEVICE displays.
The assignment of control stations and control users,
to prevent other users at other stations from issuing
PS commands that affect the output device or device
group.
The assignment of fonts available on the device.
The assignment of font sets available on the device.
The assignment of a value for the FORMID file
attribute, to indicate whether or not an output device
or device group has a special form required for tasks
such as printing paychecks or invoices.
The printing of header pages and trailer pages, to
indicate the start and end of a print request.
The creation of I/O handlers, or the assignment of the
I/O handler functions to be used by a I/O handler.
The assignment of size limits and time limits, to
restrict the size of print requests that can be accepted
during a certain time.
The assignment of the estimated lines per page, to
enable you to skip a printer (usually one with a special
form) to another page instead of another line.
The assignment of limits for the maximum number of
fonts that can be downloaded to a printer and the
maximum memory available for use with
downloadable fonts.
The specification of the PAGECOMP file attribute, to
use certain printer capabilities and control the
formatting of output.
The assignment of PRINTERKIND values, which
indicate the page description languages supported by
the selected output device.
The assignment of the virtual server that processes
the print requests routed to a virtual device, to create
a virtual device or to change its virtual server.
The assignment of the device driver that processes the
print requests routed to a device, to control certain
printing capabilities. A device driver can be used in
conjunction with the PAGECOMP file attribute to
8600 0395-514 control the formatting of output. 473
The manner in which channel-skipping operations are
to be performed.
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
Command Purpose
PS DELETE Delete print requests from the print queue, or delete a file
within a print request.
PS DESTINATION Provide information about valid non-BNA destinations.
PS DEVICES Provide information about the configuration of a device or

device group.
PS DIAGNOSTICS Provide diagnostic options for Unisys personnel.
PS DUMP Display Print System information in a human-readable,

CANDE-editable text file.
PS FONTLIB Manage the font library.
PS FORCE Mark one or more print requests as candidates for

immediate printing.
PS GROUP Define a group of printers that can be referred to by a

single logical name, or display information about the
existing device groups.
PS HEADER Display or set the contents and format of the header page
which marks the start of each print request.
PS LOAD Execute a text file containing Print System commands.
PS MODIFY Retry a print request, or alter one or more file attribute or

print modifier values of a print request and retry it.
PS NOTOK Indicate that the paper alignment on a printer needs to be

checked again, so the alignment test pattern should be
printed another time.
PS OK Start a printing device or a print request from a stopped

state that resulted either from a PS STOP command or
from the forms alignment process.
PS PAPERSIZE Enable creation, modification, and deletion of site-defined

custom paper sizes.
PS QUIT Close down the Print System, to install a different version

of the PrintS software or to fall back to an earlier version
of the MCP.
PS READY Ready a printing device from a saved state resulting from

a PS SAVE command.
PS REQUEUE Stop a currently printing request, print a trailer page, and

return the request to the print request list.
8600 0395-514 475

Command Purpose
PS RESTART Restart the Print System after it has been closed down by
a PS QUIT command.
PS SAMPLE Preview the output of a print request with this command.
PS SAVE Prevent the Print System from considering the specified

device as the destination for any further print requests.
PS SELECTION Display or change the print request selection criteria that

decide the order in which print requests are printed.
PS SHOWREQUESTS Show information about the print requests in the system.
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 STATUS Display the status summary of all current print requests.
PS STOP Stop a device or a print request. The device remains

stopped until a PS OK command is entered to resume
printing.
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.
476 8600 0395-514

PV (Print Volume)
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
-----VOLUME LIBRARY ENTRY FOR (MT) [223344]-----
SERIALNO 223344, #0002, PETAPE, ONSITE

FAMILY NAME: TEST
FAMILY CREATION DATE: 1/29/2004

FAMILY EXPIRATION DATE: 3/1/2004
FAMILY CREATION SITE: 281
FAMILY STRUCTURE #1 THRU 4
SERIALNO 334658 #0001, TAPE, ONSITE
SERIALNO 223344 #0002, TAPE, ONSITE
SERIALNO 430023 #0003, TAPE, ONSITE, DESTROYED
SERIALNO 321567 #0004, TAPE, OFFSITE
8600 0395-514 477

PV (Print Volume)
Example 2
PV PK 000096
-----VOLUME LIBRARY ENTRY FOR (PK) [000096]-----
SERIALNO 000096, #0001, PACK, BASE, OFFSITE

FAMILY NAME: MASTERPACK
FAMILY CREATION DATE: 01/24/2004
FAMILY STRUCTURE #1 ONLY
478 8600 0395-514

QF (Queue Factors)
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.
The active mix count is displayed if it is not equal to zero.
If the queue number has not been previously defined, the following message is
issued:
SPECIFIED QUEUE(S) NOT DEFINED
If the system has no previously defined queues, the following message is issued:
SYSTEM HAS NO QUEUES DEFINED
QF <queue number list>

Displays the value of all attributes of the job queues specified. Also, active mix
counts are displayed for any queues with active jobs. The queues are displayed in
the order specified in the queue number list.
8600 0395-514 479

QF (Queue Factors)
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
.
.
.
480 8600 0395-514

QT (Quit)
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:
PK <unit number> RESERVE INCOMPLETE: OK TO PROCEED, QT FOR RESDISK
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
If the mix number you specify is for a SYSTEM/BACKUP process, SYSTEM/BACKUP

skips over the file that is currently printing and continues printing with the next file
in the list. If the terminated file is on tape, SYSTEM/BACKUP spaces the tape
forward. If the terminated file is a backup disk file, SYSTEM/BACKUP does not
remove the file from the disk directory.
The QT command has no effect on a process that has been locked by the LP (Lock
Program) command.
8600 0395-514 481

QT (Quit)
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 NOT LOCKED
2420 QT
(The system does not respond this time.)
482 8600 0395-514

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
Running The application program is running and being monitored.
Not Running The application is not running.
DS on Timeout The application has specified the option to discontinue the

program if it successfully checks in within the specified time
period.
8600 0395-514 483

Response Meaning
Halt Load on The application has requested that the system be

Failed Recovery halt/loaded if the application times out and the recovery
code file fails to call the REGISTER_APPLICATION procedure
to check-in within a specified time period. (If the automatic
recovery fails, the system is to be halt/loaded.)
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.
484 8600 0395-514

Examples
Example 1
This example adds an application to the list of applications being monitored and
shows the system response:
RA + PAYROLL USER = MONEY RECOVERY = (MONEY)OBJECT/BANK
Application PAYROLL has been registered
Application Name Usercode Code File

PAYROLL MONEY (MONEY)OBJECT/BANK
Example 2
This example shows the command to list the application that was added in Example
1 and the system response:
RA PAYROLL
Application Name Usercode Code File

PAYROLL MONEY (MONEY)OBJECT/BANK
Example 3
This example deletes the application PAYROLL from the list of applications being
monitored and shows the system response:
RA - PAYROLL
Application PAYROLL has been deleted from registered applications
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:
RA + TEST USER = USER1 RECOVERY = OBJECT/PROG RESTART = TRUE

If you do not have a license key present on the system for the product A Series
Availability Plus, SETSTATUS refuses to process RA + and RA commands and
returns the following message:
UNABLE TO PERFORM REQUEST
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.
8600 0395-514 485

RB (Rebuild Access)
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.
Note: The system treats the command form RB ON VOLUMEDIRECTORY as RB ON

VOLUME DIRECTORY.
486 8600 0395-514

RB (Rebuild Access)
Example
RB ON PARTS
MSG
--Mix--Time------------------- MESSAGES ----------------------------

*4784 16:26 FAMILY REBUILDING:PK73 PARTS
8600 0395-514 487

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.

488 8600 0395-514


THIS UNIT.
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
8600 0395-514 489

<base pack specification>
<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
490 8600 0395-514

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:
PKnn SERIAL NO. ALREADY IN FAMILY AS FAMILYINDEX <number>
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
<integer> MB and <integer> GB specify the capacity in megabytes or

gigabytes. The minimum value that can be specified is 64 megabytes. The
maximum value that can be specified is the original formatted capacity of the
disk.
The system converts the integer to a value, expressed in logical sectors, that
conforms to the MCP's internal implementation requirements. The result may be
a reduction to the requested value, by as much as 32 kilobytes.
LIKE PK <unit number> requests the same capacity that is in use for the pack
with the specified unit number.
FULL specifies the capacity the disk had when it was first initialized.
At the completion of the command, the following message is displayed at the
ODT to tell the user that the capacity of the specified unit was changed:
PK <number> RESIZED TO <number> SECTORS (<number> BYTES)
If you use the CAPACITY option on a system that does not support this feature,
the following message is displayed:
INVALID MACHINE TYPE
8600 0395-514 491

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:
492 8600 0395-514

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:
ILLEGAL OR CONFLICTING FAMILYINDEX
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 member to be replaced is currently online, the following error message

appears:
FAMILYINDEX MUST BE CLOSED
If the family is the active DL JOBS family, the following error message appears:
FAMILYINDEX CANNOT BE USED ON JOBDESC FAMILY
If directory processing fails, the reconfiguration terminates with the following

message:
ERROR PROCESSING BASEPACK FLAT DIR
NAME = <family name>

Specifies the family name to be assigned. TAPE and DISKPACK are invalid values for
<family name> and are rejected. If NAME is not specified, the old family name is
used.
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:
8600 0395-514 493


MIRROR REPLACEMENT. ENTER OK TO CONTINUE WITH RC, DS TO QUIT.
If you respond OK, the designated family name is assigned to the pack, a system
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:
<mix number> PK<unit number> IS A SPARE FOR MIRROR REPLACEMENT.

RC/LB/PG NOT DONE
If your system does not have MDPF installed, the following RSVP message appears:

MIRROR REPLACEMENT, A FEATURE NOT ENABLED ON THIS MACHINE.
ENTER OK TO CONTINUE WITH RC, DS TO QUIT. OK WILL REMOVE
THE PACK FROM THE SPARE DISK POOL.
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.
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.
OLDNAME = <oldname list>

For disks previously labeled by the RC system command, you can specify the current
family names of the disks that are to be reconfigured. Otherwise, you must respond
to an ACCEPT OLDNAME = <family name> request for each disk. Note that the
order of the family names in the oldname list does not matter.
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.
494 8600 0395-514

To remove the owner identification, reconfigure or relabel the disk pack with the
following null string:
OWNER=""
SERIAL = <serial number list>

Specifies the serial numbers to be used. Each serial number in the list must be in the
range from 1 through 999999. The first unit in the unit number list receives the first
serial number in the serial number list, and so forth. If a serial number is left out of
the list (if there is a double comma or if there are fewer serial numbers than number
of units), those units retain their original serial numbers.
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
8600 0395-514 495

NAME AND SPARE MAY NOT APPEAR IN THE SAME COMMAND
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
If the free spare attribute of the disk was already set, no status change message is
issued and the following system message appears:
PK <unit number> RC'ED. PACK WAS ALREADY A SPARE.
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:
PK <unit number> UNIT RC'ED. PACK WAS NOT A SPARE.
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
INIT VSS = VSS1

INIT VSS = VSS2
For each disk in the <unit number list>, the RC process first initializes that disk with
the specified format and then reconfigures the disk.
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.
496 8600 0395-514

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:
RC PK066 NAME=JD, OWNER=JOHNDOE
If the disk already has a name, the system displays a message and creates a waiting
entry.
Following is an example message:
2566 PK66 IS: SERIAL = [206147] PACKNAME = JOHN
Following is an example waiting entry:
---Job--Task-Pri---Elapsed------ 1 WAITING ENTRY -------------

2566/ 2566 99 1:26 JOB "RC PK66 "
ACCEPT: OLDNAME = JOHN
If the operator replies 2566DS, the job terminates.
If the operator replies 2566AX OLDNAME = JOHN, the reconfiguration proceeds.
Example 2
This example assigns PK 3104 the same capacity as PK 1372, removes the data files,
and assigns a new family name:
RC PK 3104 NAME=DISK2 OLDNAME=DISK1 CAPACITY=LIKE PK 1372
Example 3
This example assigns PK 3104 the same capacity as PK 1372, removes the data files,
and retains the old family name:
RC PK 3104 OLDNAME=DISK1 CAPACITY=LIKE PK 1372
8600 0395-514 497

Example 4
This example changes the capacity of PK 3104 to be 4 gigabytes, removes the data
files, and assigns a new family name:
RC PK 3104 NAME=DISK2 OLDNAME=DISK1 CAPACITY=4 GB
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.:
RC PK 80 INIT VSS = VSS1 NAME = DATAPACK SPARE = OFF

SERIAL = 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.
RC PK 100, 200-204 NAME = TEST SPARE = OFF

OLDNAME = (XPACK, TEST)
SERIAL = (555100, , 555201-555202)
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).
RC PK 300-304 NAME=TEST BP = 555100 SPARE = OFF
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)
498 8600 0395-514


Multidisk Reconfigurations
When you are performing a multidisk reconfiguration (using the RC command with
more than one unit number in the unit number list), it is best to specify the family
name with the NAME option. Otherwise, each disk inherits its original name, and the
RC process cannot link all the disks into the same family.
When you are performing a multidisk reconfiguration, it is best to specify SPARE =

OFF if any of the existing disks might be spare mirror disks.
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:
PD BADDISK/= ON <family name>
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.
RCBP System Option

You can set the system option RCBP to activate a checking feature for base packs in
a multipack family. When the SYSOPS RCBP option is set, the system displays a
warning message when an attempt is made to reconfigure base packs in a multipack
family. Respond OK to continue the reconfiguration or DS to discontinue the
command.
8600 0395-514 499

RECONFIGURE GROUP (Reconfigure System)

The RECONFIGURE GROUP (Reconfigure System) command changes the hardware
resources to be used by a partition; you can specify either a user-defined group or
the special MINIMAL or DEFAULT groups.
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.
A halt/load is always required to complete RECONFIGURE GROUP action.
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
500 8600 0395-514

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
RECONFIGURE GROUP AS DEFAULT
RECONFIGURE GROUP AS MINIMAL NOW
RECONFIGURE GROUP AS RED
RECONFIGURE GROUP AS RED NOW HALT

The resources available to a group are determined by the hardware PCD list, the
permanent device tables that the Server Control loads during initialization. Unit and
control devices are reconfigurable between partitions.
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
8600 0395-514 501

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.
GROUP AS DEFAULT Option

In response to RECONFIGURE GROUP AS DEFAULT, the system attempts to acquire
all controls and units specified in the PCD list as accessible to the executing partition.
If the executing partition has a path to a unit, that unit is acquired even if another
partition has access to it. Except for instances where sharing of disks is desired,
avoid reconfiguring as DEFAULT when two partitions have access to the same
peripherals.
For Further Reading

For detailed information about system configuration, see the System Configuration
Guide.
502 8600 0395-514

RECOVER (Recover I/O Module)

The RECOVER (Recover I/O Module) command initiates the recovery, from the
system console (SYCON) environment, of I/O module (IOM) units that have failed.
You can use the command in conjunction with the IOM Interrupt Halt switch of the
console to control the timing of the console recovery attempt.
Note: This command is not supported on MCPvm servers.
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:
NO IOM RECOVERY REQUIRED
IOM RECOVERY IS INITIATED

The RECOVER command is processed in conjunction with the SYCON IOM Interrupt
Halt switch and the DO (Diagnostic Options) DRP, DRI, DRD command. By using
these commands with the RECOVER command, you can specify the way the system
responds to a failing non-distinguished I/O unit (IOU), data transfer unit (DTU), or
channel manager unit (CMU). Depending on the way the interrupt halt switch and
the diagnostic options are set, recovery can be attempted immediately or postponed
to another scheduled time.
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.
8600 0395-514 503

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.
2. The operating system does not take MCP

corrective action.
3. If the RECOVER command is issued, the system

pauses to perform state dumps and to perform
console corrective action. The operating system
then takes MCP corrective action.
504 8600 0395-514

REMOTEDISK
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.
This REMOTEDISK specification takes effect immediately and is preserved across

halt/loads.
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.
REMOTEDISK + PK <unit numbers>

Marks the specified units as remote disks.
REMOTEDISK - PK <unit numbers>

Marks the specified units as local disks. This is the default setting.
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
8600 0395-514 505

REMOTESPO (Activate REMOTESPO)

The REMOTESPO (Activate REMOTESPO) command controls the authorization and
activation of a data comm station as a remote ODT station. When the command
activates or deactivates a remote ODT, no response is displayed.
A maximum of 15 ODT and REMOTESPO STATIONS can run simultaneously.
If security administrator status is authorized for the system or the LIMITREMOTESPO

security option is set, an appropriately privileged user must authorize a station
before it can be activated as a remote ODT.
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.
REMOTESPO <station name>

Makes the designated data comm station an ODT station and gives it system
supervisory control. You can then enter all nonprimitive system commands from that
station except LABEL (Label ODT) and TERM DCSTATION. The CQ (Clear Queue)
command is not effective on remote ODTs; use the CANDE command ?BRK instead.
If security administrator status is authorized on the system or if the

LIMITREMOTESPO security option is set, the station name must have been previously
authorized. Otherwise, the following error message appears:
STATION <station name> WAS NOT FOUND IN THE LIST OF AUTHORIZED

REMOTESPO STATIONS
To authorize the station, use the REMOTESPO :OK form of the command.
REMOTESPO <station name>

Removes system supervisory control from the station. To return control of the
terminal to an MCS, enter BYE, END or ?END at that terminal.
506 8600 0395-514

REMOTESPO
Removes supervisory control from all active stations and terminates the REMOTESPO
independent runner.
REMOTESPO :OK <station name>

Authorizes the designated data comm station as a remote ODT station but does not
activate it. The authorization is preserved across halt/loads.
If security administrator status is authorized on the system, only the security

administrator usercode can issue this command. If security administrator status is
not authorized but the security option LIMITREMOTESPO is set, any operator,
SYSTEMUSER, or privileged user can issue this command. If the system is not
running in either of these two security modes, the REMOTESPO :OK command is
invalid.
A maximum of 255 station names can be concurrently authorized as remote ODT

stations.
REMOTESPO :OK <station name>

Removes the authorization for the data comm station to be a remote ODT but does
not deactivate any current use of it as a remote ODT.
REMOTESPO :OK
Displays a list of the stations authorized to become remote ODTs.
8600 0395-514 507

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
---------------- 1 ACTIVE REMOTESPO STATION --------

M333
Example 2
In this example, the AT LIMIT phrase indicates that the maximum number of
REMOTESPO stations are active.
REMOTESPO
-------9 ACTIVE REMOTESPO STATIONS (AT LIMIT)-------

M333
CCFPIPE22/CANDE/1
CCFPIPE22/CANDE/2
CCFPIPE22/CANDE/3
CCFPIPE22/CANDE/4
CCFPIPE11/CANDE/1
CCFPIPE11/CANDE/2
CCFPIPE11/CANDE/3
CCFPIPE11/CANDE/4
508 8600 0395-514

REPLACE (Replace Pack Volume)

The REPLACE (Replace Pack Volume) command initiates a pack volume replacement
operation.
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.
REPLACE & COMPARE PK <unit number> ONTO PK <unit number>

The COMPARE option causes each successful transfer operation to be followed by a
pair of read operationsone of the source and one of the destination. The resulting
data are compared. If either read operation fails or if the comparison fails, the same
action takes place as if the original transfer had failed. The COMPARE option helps to
ensure the accuracy of the transfer but it doubles the time required for a pack
volume replacement.
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
8600 0395-514 509

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
240*B [206000] #1 PARTS2 (0)

241*B [123123] #1 PARTS1 (0)
CLOSE PK 240,241
PK240 WILL BE CLOSED

PK240 UNIT CLOSED
PK241 UNIT CLOSED
UR PK 240,241
PK240 RESERVED
PK241 RESERVED
REPLACE PK 241 ONTO PK 240
5231 PK240 IS PARTS2 #1 [206000]

5231 OK TO REPLACE PK241 ONTO PK240 ? (PK240 WILL BE OVERWRITTEN.)
5231 OK
5231 PK241 10 % READ. 100 % SUCCESSFULLY.

5231 PK241 REPLACED ONTO PK240. 0 FAILURES. (0 SECTORS OUT OF 362230)
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
510 8600 0395-514

PER PK
----- PK STATUS -----

240*B [123123] #1 PARTS1 (0)
241*B [000000] #1 L A B E L E R R O R
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 MDPF is installed on your system, the message is similar to the following:

<mix number> PK64 IS DBDATA #1 [<serial #>]

<mix number> PK65 IS DESIGNATED A SPARE FOR MIRROR REPLACEMENT
<mix number> OK TO REPLACE PK 64 ONTO PK 65? (PK 65 WILL BE OVERWRITTEN)
If MDPF is not installed on your system, the message is similar to the

following:
<mix number> PK64 IS DBDATA #1 [<serial #>]

<mix number> PK65 IS DESIGNATED A SPARE FOR MIRROR REPLACEMENT,
A FEATURE NOT ENABLED ON THIS SYSTEM.
<mix number> OK TO REPLACE PK 64 ONTO PK 65? (PK 65 WILL BE OVERWRITTEN)
Note: The OK TO REPLACE message is displayed by the REPLACE command

regardless of the presence or absence of MDPF.
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.
If you respond DS, the command is rejected and no replacement occurs.

You can use the SCAN (Scan Pack Volume) command before the REPLACE command
to determine in advance the probable results of using the REPLACE command. For
more information, refer to the SCAN (Scan Pack Volume) command.
A visible independent runner, REPLACEPACK, performs the pack volume

replacement. It controls both volumes until it finishes, preventing any other use of
them. Because REPLACEPACK leaves both volumes reserved, you must enter UR
to make them available. Refer to the UR (Unit Reserved) command. REPLACEPACK
displays an error message and terminates if any of the following conditions occurs:
8600 0395-514 511

The units do not exist.

The source pack is larger than the destination pack.
The units are not reserved.
The units are not available; for example, if they are being used by
maintenance or by another REPLACEPACK.
The directories for the source volume are not available.
The source volume is not a labeled pack.
If REPLACEPACK is discontinued with a DS command or terminates for any other
reason during the copy phase, the source volume is not modified and the destination
volume is unlabeled.
If errors occur on the destination volume, REPLACEPACK displays a message

summarizing the errors and then displays the following RSVP message before
proceeding to the damage analysis phase:
OK TO CONTINUE OR DS AND TRY ANOTHER DESTINATION.
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:
REPLACE/<family name>/FAMILYINDEX<integer>/<report file name>
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:
SOURCE READ ERROR

DESTINATION WRITE ERROR
SOURCE COMPARE READ ERROR
DESTINATION COMPARE READ ERROR
COMPARE ERROR
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
SCAN/REPLACE ERROR @ ADDRESS: 8090 FOR 1 SOURCE READ ERROR ...
512 8600 0395-514

... 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.
A DAMAGEREPORT file might look like this:
REPLACE/TESTPK/FAMILYINDEX2/DAMAGEREPORT ON HLDISK
DAMAGED FILE: (XYZ)SYMBOL/GREEN

ROW(S): 17,24
DAMAGED FILE: *TESTDB/PARTS/DATA
DMS ROW LOCKOUT OF
ROW(S): 7
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.
8600 0395-514 513

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.
It is possible to perform pack volume replacement operations on several

nondirectory volumes of the same family at the same time. However, you should first
consider how such actions will reduce the rate of I/O subsystem throughput and
increase the system workload.
If the subject volume of a pack volume replacement operation contains a directory,

then parts of the directory might not transfer correctly to the destination volume. All
records in a directory contain a checksum, which detects any such errors.
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:
OK TO ERASE BAD RECORDS?
Enter one of the following system commands to reply to this message:
DS terminates the pack volume replacement.

OK lets pack volume replacement continue, but might cause files to be lost
from the directory.
If there is no duplicate directory and the portion of the directory describing the
directory itself is corrupted, the pack volume replacement is terminated.
Replacing Disks with Varying Sector Sizes

Some restrictions apply to the replacement of a disk with another disk that uses a
different sector size or sector size emulation method (either VSS-1 or VSS-2). For a
514 8600 0395-514

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.
Source Target Allowed?
180-byte VSS-1 Yes
180-byte VSS-2 No (3)
180-byte 180-byte (1) Yes (2)
VSS-1 180-byte Yes
VSS-1 VSS-2 No (3)
VSS-1 180-byte (1) Yes (2)
VSS-2 VSS-1 No (4)
VSS-2 180-byte (1) Yes (5)
180-byte (1) VSS-1 No (4)
180-byte (1) 180-byte Yes (5)
Notes:
1. The 180-byte disk is reconfigured with VSS = VSS2.

2. The target 180-byte disk no longer uses VSS-2 file allocation after this replace
CAPACITY LIKE PK <source> to replace this source.
CAPACITY LIKE PK <source> to replace this source.
5. The target 180-byte disk uses VSS-2 file allocation after this replace
8600 0395-514 515

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:

with CAPACITY option to replace this source.
To convert the selected disk to a compatible destination for this source,


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:

with CAPACITY option to replace this source.
To convert the selected disk to a compatible destination for this source,


516 8600 0395-514

REPLACECARD (Replace Card)

The REPLACECARD (Replace Card) command assists with the replacement of a
hardware channel card on IOM systems except MCPvm systems. Qualified field
service personnel must do replacement of channel cards. This command is not
intended for the user.
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.
REPLACECARD PORT <port number>

The specified port and all ports outboard of the same CSBUS as the specified port are
made unavailable for I/O operations. An RSVP message is posted to indicate when
I/O operations have ceased. Prior to responding to the RSVP, the channel card
(specified port) can be removed and replaced. After the channel card is replaced,
your response to the RSVP causes all the associated ports previously made
unavailable to become available for I/O operations.
Examples
Example 1
This example aborts the reserving of port 18101.
REPLACECARD PORT 18101
CSBUS FOR PORT 18101 RESERVED

PORT 18101 CAN NOW BE REPLACED
RSVP: PORT 18101: REPLY OK AFTER REPLACING OR DS TO ABORT.
RSVP->DS
PORT 18101: REPLACECARD ABORTED
8600 0395-514 517

Example 2
This example reserves port 18101 so that it can be replaced, and then makes port
18101 available again.

RSVP->OK
CSBUS FOR PORT 18101 AVAILABLE
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
RSVP->OK
CSBUS FOR PORT 18111 AVAILABLE
518 8600 0395-514


The following conditions for replacing a channel card (port) apply to all ports affected
by this command.
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.
8600 0395-514 519

RES (Reserve)
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:
Label areas (sectors 0 through 27)

Units whose base units are not online
520 8600 0395-514

RES (Reserve)
If a RES request is directed to any of these areas, the request is terminated.
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
AS BADDISK The AS BADDISK option causes the entire pack to be covered

by a BADDISK file.
AS MAINT The AS MAINT option results in the CLOSE and SV (Save)

operations being performed on the unit. It is the only option
that can be applied to units that have been closed using the
CLOSE (Close Pack) system command. For such units, its
function is to mark the unit as saved. If the unit is ready, all
files are either transferred from the unit before the CLOSE
and SV (Save) operations are performed, or they are
removed if the REMOVE option is specified.
8600 0395-514 521

RES (Reserve)
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).
522 8600 0395-514

RES (Reserve)
Example
This example removes an area from the tables of usable space for disk pack unit 96:
RES PK 96 SEGMENT 111111 FOR 25
---Mix-Pri-CPU Time-------- 1 ACTIVE ENTRY --------------------------

1281 99 14:17 JOB RESERVEDISK
MSG
--Mix--Time------------------- MESSAGES -----------------------------

1281 16:26 PK96 BADDISK/FMLYINX1/UNIT96/AD01B207H CREATED ON DISK
1281 16:25 DATA MOVED IN *SYSTEM/MCP117
Note that all addresses in BADDISK file names are in hexadecimal format.

Mirrored Disk Considerations
If the specified pack is mirrored, any changes made to it are also made to the other
members of its mirrored set. The AS DELETED and AS MAINT parameters are not
allowed for mirrored sets.
Using RES, SQUASH, and XD Requests

Only one RES, SQUASH, or XD request can be active on a disk family at any given
time.
Using the AS MAINT Option

For the AS MAINT option, the independent runner RESERVEDISK leaves the pack in
the saved state. You can reconfigure or relabel saved packs and return them to a
usable state by entering the RY (Ready) command. For more information, refer to
LB (Relabel Pack or Host Control Unit) in Section 5, RC (Reconfigure Disk) earlier
in this section, and RY (Ready) later in this section.
Handling Files that Cannot Be Moved

If the independent runner RESERVEDISK encounters files that could not be moved in
the area to be reserved, the system displays the following RSVP message:
PK <unit number> RESERVE INCOMPLETE: OK TO RETURN, QT FOR RESDISK
You can then enter one of the following commands.
Command Result
DS Releases all space reserved during this run of RESERVEDISK.

(Discontinue)
8600 0395-514 523

RES (Reserve)
Command Result
OK Causes another pass through the permanent intersecting files. If

(Reactivate) any file is still blocking the reserve, it is displayed. If no
blockage exists, RESERVEDISK then handles temporary files.
QT (Quit) Causes creation of RESDISK files out of areas that would

otherwise be released and then sends the RESERVE procedure
to end-of-job (EOJ). You can use this option to cut off the
RESERVEDISK overhead, while preventing the allocation to
areas that later might be required by a RESERVE procedure. (A
RESDISK file has the FILEKIND attribute set to XDISKFILE, and
is titled in the same way as BADDISK.)
If a RESDISK file is encountered by a subsequent RES
command, it is removed. Any part of the old RESDISK that
intersects with the new RESERVEDISK specification is then
absorbed into the new set of reserved disk, and the remainder
is released as available for system use.
Old BADDISK files remain in the directory even if the areas were
released by a later RESERVEDISK operation. In the display for a
PD command, the total sectors for BADDISK are reported as 0
(zero): "TOTAL SECTORS 0."
Considerations for VSS Disks

VSS disks have 180-byte logical segments and 512-byte physical segments. By
default, the <segment range> for a VSS disks refers to logical segments. However, if
you include the PHYSICAL option at the start of the <segment range>, then the
<segment range> refers to physical segments.
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.
524 8600 0395-514

RES (Reserve)
Example 1: VSS-2 Disk

Suppose you enter the following command:
RES PK 96 SEGMENT 0 THRU 3
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.

Suppose that the BADDISK file that was created in example 1 already exists, and
you enter the command
RES PK 96 PHYSICAL SEGMENT 1 THRU 2
The system creates a second BADDISK file, with the name

BADDISK/FMLYINX1/UNIT96/AD2H. The file reserves logical segments 2 through 5,
because these correspond to physical segments 1 and 2, as shown in the following
figure:
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:
BADDISK/FMLYINX1/UNIT96/AD0H corresponds to physical segment 0 and

reserves logical segments 0 and 1.
BADDISK/FMLYINX1/UNIT96/AD2H corresponds to physical segment 1 and 2,
reserving logical segments 2 through 5.
8600 0395-514 525

RES (Reserve)

Suppose you enter the following command:
RES PK 96 PHYSICAL SEGMENT 1
In this case, the system creates a file named BADDISK/FMLYINX1/UNIT96/AD2H that

reserves logical segments 2 through 5. These are all the logical segments that are
wholly or partly contained in physical segment 1, as the following figure shows:
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.

It is possible for two seemingly unrelated REServe commands to affect the same
logical segment. This is possible because a RES command can specify physical
segments, but the system translates these physical segments into logical segments
that might overlap adjoining physical segments.
Suppose that the BADDISK file from example 3 already exists, and you enter the
following command:
As a result of this command, the system creates a file named

BADDISK/FMLYINX1/UNIT96/AD5H. This file reserves logical segments 5, 6, 7, and
8, because these all correspond to physical segment 2, as shown in the following
figure:
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).
526 8600 0395-514

RES (Reserve)

Suppose that the two BADDISK files from example 4 already exist, and you enter the
following command:
Where physical segment 0 maps to logical segments 0, 1, and 2 as shown in the

following figure:
In this case, the system
Creates a third BADDISK file, named BADDISK/FMLYINX1/UNIT96/AD0H. The

file reserves logical segments 0 through 2.
Alters the previously created BADDISK file that reserves logical segments 2
through 4. The system removes logical segment 2 from this file, so it now
reserves only logical segments 3 and 4.
Note that the system also renames the BADDISK file in this case, because the file
name is based in part on the first segment that the file reserves, and this file now
starts at logical segment 3 instead of logical segment 2. The resulting BADDISK file
name is BADDISK/FMLYINX1/UNIT96/AD3H.
At the conclusion of this example, the following BADDISK files exist.
File Name Description
BADDISK/FMLYINX1/UNIT96/AD0H Corresponds to physical segment 0 and

reserves logical segments 0 through 2.

reserves logical segments 3 and 4.

reserves logical segments 5 through 8.
If you remove BADDISK/FMLYINX1/UNIT96/AD0H, the system makes logical

segments 0 through 2 available for use. This means that all of logical segment 2
becomes available even though it overlaps into physical segment 1 (previously
reserved). Later, when a program attempts to read or write logical segment 2, the
system attempts to access all of physical segment 1. An error can result if physical
segment 1 is defective.
8600 0395-514 527

RESTART (Restart Jobs)

The RESTART command restarts a job or group of jobs. The command has no effect
on a process that has been locked by the LP (Lock Program) command.
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.
6660 - 6670 RESTART

You can use the RESTART command to achieve the effects of a halt/load without
interrupting the system. For example, the RESTART command enables pack
maintenance to be performed so that jobs using those packs can be discontinued,
held in job queues, and restarted from the last point at which tasks were not active.
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.
528 8600 0395-514

RESTRICT (Set Restrictions)

The RESTRICT (Set Restrictions) command sets or resets security-related restrictions
on peripherals, volumes, commands, or files. The system preserves the restricted
status of a unit and its security key through a halt/load. This command initiates an
independent runner named RESTRICT <device type> <unit number>.
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 PK <unit number list>

RESTRICT DK <unit number list>
Mark the specified packs or memory disk units as restricted. If the command
specifies one pack in a multipack family, all packs in the family are treated as
restricted even if they are not so marked.
8600 0395-514 529

The RESTRICT PK <unit number list> or RESTRICT DK <unit number list>

command removes the restrictions from the packs. To remove the restrictions from a
family, the RESTRICT command must specify all members of the family that are
marked as restricted.
RESTRICT CD <unit number list>

Marks the specified CD-ROM units as restricted. You can use the RESTRICT CD
<unit number list> form of the command to remove the restrictions from the
specified units.
RESTRICT COMMAND
Displays a list of the restricted commands.
Note that many commands are automatically restricted when a security

administrator is authorized. For a complete list of these automatically restricted
commands, refer to the ??SECAD (Security Administrator Authorization) primitive
command.
RESTRICT COMMAND <command>

Restricts the use of the specified command. The following commands can be
specified in the RESTRICT command.
ACCOUNTING DL MOVE SF
AD DN MQ SHARE
AI DQ MP SI
AR DR NET SQUASH
ARCCOPY DRC NETEX SS
ARCDUPLICATE EXPAND NEW STC

SYSTEMDIRECTORY (STRUCTURECACHE)
ARCREPLACE FAMILYACCESS NW SUPPRESS
ASD GC OP SUPPRESSWARNING
BNA HLUNIT PB SYSOPS
BNAVERSION HN PQ TERM
CM HS RB TL
COMPILERTARGET ID RECONFIGURE TR
GROUP
COPYCAT IK RES UQ
CS LC RP XD
530 8600 0395-514

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.
If security administrator status is authorized for the system, restricted commands

can be entered only from a source with SECADMIN status. Such sources include
A MARC session with a security administrator usercode.

A program using SETSTATUS that is running under a usercode with
SECADMIN status.
A program using DCKEYIN that is marked with SECADMIN status by the MP
(Mark Program) command.
Note: Setting the TERM USER attribute to a security administrator usercode at an
ODT does not permit the use of restricted system commands from that ODT.
RESTRICT COMMAND <command> <option>

Restricts the use of the specified command option. 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, if you restrict SYSOPS, you restrict all
uses of the command. If you restrict SYSOPS LANGUAGE, you restrict only 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.
RESTRICT COMMAND <command>

Removes any restrictions previously applied on the specified command.
RESTRICT VOLUME <serial number list>

Marks the volume directory entries for the specified tape volumes as restricted.
RESTRICT VOLUME <serial number list> removes the restrictions from the tape
volumes. This command is available only if you are using Secure Access Control
Module security enhancement software and if you have set the TAPECHECK security
option.
RESTRICT FILE <file list>

Marks the specified nondata files as restricted. Nondata files are system files,
compilers, backup files, and code files. For a definition of these files, refer to the
discussion of FILEKIND in the I/O Subsystem Programming Guide. An attempt to
8600 0395-514 531

restrict a data file causes an error message to be displayed. The RESTRICT FILE
<file list> command removes the restrictions from the files.
RESTRICT SC <unit number>

Suspends automatic display mode (ADM) on the specified ODTs and restricts those
ODTs to using MARC and being assigned to files. The execution of this command
leaves the specified ODTs under the control of COMS/ODT/DRIVER. If a unit has
been reserved with a UR (Unit Reserved) command, it cannot be restricted, and the
following message appears:
SC <unit number> NOT RESTRICTED
If a unit is already restricted, the following response appears:
SC <unit number> RESTRICTED AGAIN
The maximum number of ODTs that can be restricted is 15. An attempt to restrict
more than 15 ODTs produces the following error message:
SC <unit number> NOT RESTRICTED, TOO MANY RESTRICTED ODTS
You can use the following system commands on a restricted ODT:
In ODT mode, the following commands are valid:

??MARC
??RESTRICT (<security key>)
LABEL
In MARC mode, you can use only ??ODT.
RESTRICT SC <unit number list> (<security key>)
Restricts the specified ODTs to using only MARC and being assigned to files, and
associates a security key with them.
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.
RESTRICT SC <unit number list>

Removes the restriction on the use of the specified ODTs, whether or not they have a
security key. The system places the ODT in ODT mode (rather than MARC mode).
When the system releases an ODT, automatic display mode (ADM) becomes enabled.
If an ODT is not restricted, the following message appears:
SC <unit number> RELEASED AGAIN
532 8600 0395-514

If an ODT is reserved (with a UR command), it cannot be released and the message

is
SC <unit number> NOT RELEASED
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-115 Marks tape units 113 through 115 as restricted.
RESTRICT PK 201 Marks pack 201 as restricted.
RESTRICT PK 201- Marks packs 201 through 203 as unrestricted.

203
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.
RESTRICT FILE X Marks the file named X on DISK as restricted if it is a

non-data file.
RESTRICT FILE X ON Marks the file X ON PACK as unrestricted.

PACK
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
RESTRICT SC 1 Restricts the ODT whose unit number is 1.
RESTRICT SC 1 Removes the restriction on the ODT whose unit number is 1.
8600 0395-514 533

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 Restricts the use of the LANGUAGE option of the

SYSOPS LANGUAGE SYSOPS command.
RESTRICT COMMAND Removes any restrictions on the SYSOPS

SYSOPS command.
RESTRICT COMMAND MAX Restricts the use of all options of the MAX
command.
RESTRICT COMMAND Removes the restriction on the MAX MESSAGES

MAX MESSAGES 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.

If security administrator status is authorized on the system the RESTRICT command
can be issued only by a security administrator usercode. If security administrator
status is not authorized on the system, then any operator, SYSTEMUSER, or
privileged user can issue RESTRICT commands. For information about setting
security administrator status, refer to the ??SECAD (Security Administrator
Authorization) primitive command.
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.
Restricting Files, Units, and Volumes

Access restrictions might affect file copying by library maintenance. The access
restriction for the new file is unpredictable if the file, volume, or unit restrictions of
534 8600 0395-514

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.
Access to a nondata file is restricted if one or more of the following conditions is

true:
The file is explicitly restricted.

The volume containing the file is restricted.
The unit on which the volume is mounted is restricted.
The file is on a pack or memory disk family with one or more members
located on a restricted unit.
Code files to which access is restricted cannot be executed. Such files can be opened
only by a security administrator (or, if security administrator status is not authorized,
by a privileged user). These files can be altered if they can be opened and if system
criteria for altering them are met.
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>.
If all ODTs become restricted, you must perform a cold-start.
8600 0395-514 535

RF (Reliability FactorIOM Systems)

The RF (Reliability Factor) command displays the current reliability factor for
peripheral units, controls (CTLs) or ports.
Syntax
Explanation
RF <device type> <unit number list>
Displays the reliability factor of the devices in the unit number list.
RF CTL <device number>

Displays the reliability factor of a control.
RF PORT <port number>

Displays the reliability factor of a port.
Examples
Example 1
This example displays the reliability factor for tape drive 144:
RF MT 144
MT 144 RELIABILITY FACTOR = 99%
Example 2
This example displays the reliability factor for CTL 10013:
RF CTL 10013
CTL 10013 TOTAL I/O = 45723 ERROR = 2 PERCENT = 0%
Example 3
This example displays the reliability factor for port 1120:
RF PORT 1120
PORT 1120 TOTAL I/O = 1693 ERROR = 5 PERCENT = 0%
536 8600 0395-514


You can clear the reliability factor by using an RW (Rewind) command or UR (Unit
Reserved) command. Halt/loading the system also clears the reliability factor.
8600 0395-514 537

RM (Remove)
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.
In response to the RSVP message DIRECTORY NOT CURRENT, the command

removes the outdated backup directory and marks the disk as online for ordinary use
to programs.
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 50 10:11 JOB CONTROLCARD
PK500 *AE5/1 DUPLICATE FILE ON DISK
2577 RM
2577 PK500 *AE5/1 REPLACED ON DISK

2577 PK500 *AE5/2 CHANGED TO *AE5/1 ON DISK
538 8600 0395-514

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.
The default status of programs is nonresident.
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
----- 3 RESIDENT PROGRAMS -----

(1) *SYSTEM/NEWP ON NI34
(0) *OBJECT/TEST ON PACK
(3) *SYSTEM/ALGOL ON DISK
8600 0395-514 539

Example 2
This example marks the file SYSTEM/ALGOL as a resident program.
RP SYSTEM/ALGOL
SYSTEM/ALGOL IS A RESIDENT PROGRAM
Example 3
This example releases the file SYSTEM/DCALGOL from being a resident program.
RP - SYSTEM/DCALGOL
SYSTEM/DCALGOL NOT A RESIDENT PROGRAM
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
FILE NOT ON DISK
540 8600 0395-514

RSS (Reliable Session Service Prefix)

The RSS (Reliable Session Service Prefix) command directs RSS operator input
commands to the RSS system.
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.
8600 0395-514 541

RSS QUIT NOW

Causes the RSSUPPORT library to terminate itself and any linked users. The linked
programs are discontinued.
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.
RSS RESTART NOW

If RSS is not active, initiates the RSS system at the local host. The effect is the same
as an RSS RESTART command.
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 TRACE DUMP

Causes the in-memory trace buffer of the local nexus to be written to disk. The
command is acknowledged, and the name of the trace file is displayed at the ODT.
RSS TRACE RELEASE

Causes the in-memory trace buffer of the local nexus to be written to disk. The
current trace file is closed, and a new file is opened. The command is acknowledged,
and the name of the released trace file is displayed at the ODT.
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.
RSS USERDATA K = <K Value>

Sets the value of the K parameter on all nexus to the new value. If the value of the K
parameter is increased, the current USERDATAFILE is replicated to sufficient nexus
to ensure that enough replicated copies are available (assuming that sufficient nexus
exist).
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.
542 8600 0395-514

RSS USERDATA INITIAL = <Boolean>

Sets the value of the INITIAL parameter on this nexus. The INITIAL parameter
specifies whether a nexus can supply the master USERDATAFILE.
This parameter has no effect until the CSP Userdata service group is reestablished.
RSS USERDATA ENABLED

Enables the CSP Userdata service. The CSP Userdata service will not initialize unless
it is enabled. If the CSP Userdata service is enabled, the service starts whenever RSS
initializes and the CSP run-time key is installed.
RSS USERDATA DISABLED

Disables the CSP Userdata service. The CSP Userdata service will not be initiated
either automatically when RSS initializes, or after an RSS USERDATA RESTART
command.
RSS USERDATA QUIT

Terminates the CSP Userdata service.
RSS USERDATA RESTART

Restarts the CSP Userdata service if the Reliable Session Service is available.
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 IS: HOSTA # 1

PLEXUS CONFIGURATION:
HOSTA # 1, (IN)
HOSTB # 2, (OUT)
HOSTC # 3, (IN)
FILE DIRECTORY: *RSS ON RSPACK

CURRENT TRACE/FILE: *RSS/TRACE/HOSTA/050515/183530 ON RSPACK
NEXUS TIMEOUT: 2 MINUTES
Following are explanations of various portions of this output:
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
8600 0395-514 543

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.
State Code Meaning
IN Nexus is in the plexus.
OUT Nexus is not in the plexus.
JOINING Nexus is in the process of joining the plexus.
LEAVING Nexus is in the process of leaving the plexus.
FAULTY Failure has been detected.
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.
544 8600 0395-514

Example 2
If you enter the RSS USERDATA command, and CSP Userdata is not active, the
following response might be given:
RSS USERDATA
---- CSP Userdata Status ----

Initial is set
CSP Userdata is disabled
K redundancy is 127
UserData Services are not in use
If CSP Userdata is active, the following response might be given:
RSS USERDATA
---- CSP Userdata Status ----

Initial is reset
CSP Userdata is enabled
K redundancy is 127
UserData Services are active
2 peers
Rank is 1
Chrone address is C2/1/3
UserDataFile is replicated on this nexus
2 messages in use
8600 0395-514 545

RW (Rewind)
RW (Rewind)
The RW (Rewind) command rewinds and unloads tape units, and unloads CD-ROM
drives.
If a unit is in use, the following message is displayed:
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
MT114 REWOUND & UNLOADED
546 8600 0395-514

RY (Ready)
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.
8600 0395-514 547

RY (Ready)
READY CPM <CPM list>

Readies the specified CPM for use by the system. The CPM numbers in the list can be
integers from 0 through 11.
READY IOM <number>

Readies the specified unit for use by the system. The task control unit (TCU) and the
I/O unit (IOU) are made available on a standby basis. The data transfer unit (DTU) is
available for cache operations. All ports that have not been reserved are made
available. The IOM number can be an integer from 0 through 7.
READY MSM <number>

READY MSM <number> MSU <number>
READY MSM <number> MSU <number> QUAD <number>
Ready the specified memory subsystem modules and memory storage units for use
by the system. MSM numbers can be either 0 or 1. MSU numbers can be integers
from 0 to 5. QUAD numbers can be integers from 0 to 3.
Examples
Example 1
This example readies a tape unit:
RY MT 113
MT 113 WILL BE READY
Example 2
This example readies an MSM and an MSU:
RY MSM 0, MSU 1
MSM 0 WILL BE READY
MSU 1 WILL BE READY
Example 3
This example readies a Telephony Services Platform (TSP) unit:
RY TSP 200
TSP200 WILL BE READY
TSP200 READY
548 8600 0395-514

RY (Ready)

System Initialization Restrictions
A pack that is readied during system initialization is made available to the system
only after initialization is completed. During initialization, if it is determined that an
unavailable pack is needed, such as the CATALOG pack, you must halt/load the
system again after you enter the RY PKnn command.
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:
READY VC <unit number>
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:
READY TSP 200,201,202,203
8600 0395-514 549


The S (Scheduled Mix Entries) command displays scheduled tasks. A schedule is a
queue of tasks that are attempting to initiate, but cannot yet do so because one of
the following situations exists:
Available memory is insufficient.

Processor usage for overlay activity has exceeded the value of
OLAYSATURATION. Refer to Factor 6: OLAYSATURATION in the SF (Set
Factor) system command.
Fewer than five per cent of the ASDs are available.
Pack space for the system log is insufficient (LOGHANDLER would be in the
waiting entries).
Pack space for overlaying memory is insufficient (OLAYSCOUT would be in the
waiting entries).
An HS (Hold Schedule) command was entered.
A CM (Change MCP) operation is in progress.
A RECONFIGURE GROUP (Reconfigure System) operation is in progress.
Exceptions to these conditionsthat is, jobs might have these conditions but are not
scheduledare control programs that have either insufficient memory, fewer than
five percent of the ASDs available, or have overlay saturation and visible
independent runners that have insufficient pack space for overlaying memory.
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>
550 8600 0395-514

<delim>
Use one of the following characters:
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
Question mark Matches any single character

(?)
Tilde (~) Matches any sequence of characters except a slash

(/)

space character.
S NAME =pack=
"pack":
S NAME LIT ^=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.
8600 0395-514 551

S NAME <wild-card string>

S ALL NAME <wild-card string>
Display one or all scheduled jobs or tasks with names that contain the specified wild-
card string.
S MCSNAME = <MCS name>

S MCS = <MCS name>
Display only scheduled jobs or tasks originating from the specified MCS.
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 QUEUE <queue number>

S Q <queue number>
Display any scheduled WFL jobs or tasks originating from the specified queue.
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:
--Mix-Pri-Elapsed--WordsReq--- 3 SCHEDULED ENTRIES ------------------

270 50 09:07 2K Job (NORM) NEDCOMPILE
274 50 10:11 34K (ROBY)OBJECT/SYMBOL/GOODUTIL ON TOP
280 50 14:22 21K (NORM) *DCALGOL (NORM)OBJECT/PATCH/NED
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:
552 8600 0395-514


Example 2
This example shows a response to the S command after an HS (Hold Schedule)
command has been entered:
--Mix-Pri-Elapsed--WordsReq--- 3 SCHEDULED ENTRIES HS ---------------

3203 50 2:21 21K *ALGOL ON DISK XPROG
*3208 50 :02 31K *SYSTEM/DUMPALL ON DISK
3205 50 1:27 921 Job DREF
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:
--Mix-Pri-Elapsed--WordsReq--- 1 SCHEDULED ENTRY CM -----------------

*3321 50 :04 1K *LIBRARY MAINTENANCE
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= ""
--Mix-Pri-Elapsed--WordsReq--- 3 SCHEDULED ENTRIES USER= ------------

3274 50 10:11 34K (ROBY)OBJECT/SYMBOL/GOODUTIL ON TOP
The display eliminates the entries with a specific usercode (NORM) but shows the
entry with no usercode.
8600 0395-514 553

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
You can use the following synonyms.
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.
554 8600 0395-514

SB TAPE = PACK, DISK = PACK, PACK = PACK

Causes PACK to be the only backup medium.
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

If an entry is duplicated in an SB command, such as the following, then an error
SB DISK = PACK TAPE PACK
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.
8600 0395-514 555

SBP (System Balancing Parameters)

The SBP (System Balancing Parameters) command displays and sets the time
interval used for computing system utilization information.
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.
SBP CPURATE = <number>

Sets the time interval (in seconds) for computing CPU processor rate information for
processes. The number must be in the range 10 to 60. The default is 20.
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.
SBP INTERVAL = <number>

Sets the time interval (in seconds) for computing system utilization information. The
information can be displayed by the U (Utilization) command. The default interval is
10 seconds.
SBP SLICERATE = <number>

Sets the rate, in slices per second, at which processes of the same priority are sliced.
The slice rate value is a number between 10 and 200 that indicates the number of
slices (process stack switches) per second that the system is to make for processes
that have the same priority level. All processes at the same priority level are treated
in a round-robin manner. Processes at a higher priority always immediately preempt
processes at a lower priority regardless of the setting of SLICERATE. The default is
50.
556 8600 0395-514

Example
SBP
SYSTEM BALANCING PARAMETERS

INTERVAL = 10 SECONDS
SLICERATE = 60 SLICES PER SECOND
CPURATE = 20 SECONDS

Setting the Slice Rate Value
A short SBP INTERVAL value provides an immediate picture of system utilization, and
a long interval gives a better average picture. With a short interval, sudden changes
are accurately reflected. With a longer interval, changes are smoothed out. The
default interval is 10 seconds, which can be termed short. An interval shorter than
10 seconds is not advisable because the statistics tend to fluctuate too much.
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.
8600 0395-514 557

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-
SYSTEM TYPE: CS7101-1007

1 DATA PROCESSOR 4
1 I/O PROCESSOR 1
MEMORY USAGE:
SYSTEM 16 MWords
TOTAL ONLINE 16 MWords
MODULE STATUS:
MODULE STATE
IOM 1 IN USE
CPM 4 IN USE
CPM STATUS:
CPM 4: [MAC=01.000,SLL=06.871,SCL=0,FEATURES=5,06/21/2004]
I/O CONFIGURATION:
IOM 1:
TCU 0: DIST [ERL=06.871,SLL=06.000,SCL=0,FEATURES=1,06/21/2004]
IOU 0: DIST [ERL=06.839,SLL=01.051,SCL=0,FEATURES=0,05/20/2004]
PORT 10400: [ERL=06.839,SLL=00.105,SCL=3,FEATURES=1,05/20/2004]
558 8600 0395-514


PK 502
CTL 10403: PK1SCSI [0000] VIA PORT 10400
PK 501
PK 500
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-
SYSTEM TYPE: CS580

PROFILE NAME: J2D1-0210
SDS NAME: P11SDS22
PLATEAU: 1.1Z
1 INSTRUCTION PROCESSOR
1 PCI-BRIDGE
1 MEM
MEMORY USAGE:
SYSTEM 138 MWords
MEMORY DISC 20 MWords
DISC CACHE 230 MWords
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
8600 0395-514 559

HIGH EMODE MEMORY BASE: 20000000

HIGH EMODE MEMORY LIMIT: 2FFFFFFF
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
PK 54
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
PK 9016,9017,9018,9019,9020,9021,9022,9023,9024,9025,9026,9027,9028
Example 3
The following are portions of the SC display for an NX5800 system:
SC-
Response returned at 16:01:26
SYSTEM TYPE: NX5800

4 DATA PROCESSORS 4-7
2 I/O PROCESSORS 0-1
2 MSMS 0-1
560 8600 0395-514

MEMORY USAGE:
SYSTEM 136 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>
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]
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-
8600 0395-514 561

SYSTEM TYPE: CS585

PROFILE NAME: TRPROGD
SDS NAME: F13SDS3
PLATEAU: 1.3C
2 STANDARD PROCESSORS
2 SPECIAL PURPOSE PROCESSORS
2 PCI-BRIDGES
2 MEMS
MEMORY USAGE:
SYSTEM 500 MWords
MEMORY DISK 500 MWords
DISC CACHE 500 Mwords
NOT IN USE 548 Mwords (MEMORYCEILING 1624 Mwords)
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 NON-COHERENT BYTE MEMORY BASE: 18400000
LOW NON-COHERENT BYPE MEMORY LIMIT: 1FFFFFFF
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
562 8600 0395-514

CTL 2001: TSPSCSI VIA 20000

.
.
.
Example 6
The following example shows a portion of an SC display for a Libra Model 680
system:
SC-
SYSTEM TYPE: CS680

PROFILE NAME: TRPROGD
SDS NAME: F13SDS3
PLATEAU: 1.3C
2 STANDARD PROCESSORS
2 SPECIAL PURPOSE PROCESSORS
2 PCI-BRIDGES
2 MEMS
MEMORY USAGE:
SYSTEM 500 MWords
NOT IN USE 548 Mwords (MEMORYCEILING 1624 Mwords)
MEM STATUS:
SIZE STATE START ADDRESS
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 NON-COHERENT BYTE MEMORY BASE: 18400000
LOW NON-COHERENT BYTE MEMORY LIMIT: 1FFFFFFF
HIGH EMODE MEMORY LIMIT: 87BFFFFF
8600 0395-514 563

SCAN (Scan Pack Volume)

The SCAN (Scan Pack Volume) command reads a pack volume to analyze and record
any read errors. It enables you to determine, in advance, the results of issuing a
REPLACE (Replace Pack Volume) command that specifies the given device as a
source. The SCAN command initiates an independent runner named REPLACEPACK.
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
------- PK STATUS -----

240*B [206000] #1 PARTS2 (0)
241*B [123123] #1 PARTS1 (0)
242*B [550066] #1 DISK (53)
CLOSE PK 240,241

PK240 UNIT CLOSED
PK241 UNIT CLOSED
UR PK 240,241
PK240 RESERVED
PK241 RESERVED
564 8600 0395-514

SCAN PK 241
5228 PK241 PK241 IS PARTS1 #1 [123123]

5228 SCANNING PK241.
5228 PK241 SCANNED. 0 FAILURES. (0 SECTORS OUT OF 362230)

The SCAN command does not lock out defective areas or mark them as destroyed.
The volume need not be labeled. If it is an unlabeled or scratch pack, no damage

analysis is performed and only a SECTORSINERROR report file is generated.
8600 0395-514 565

SECOPT (Security Options)

On systems that have Secure Access Control Module security-enhancement software,
the SECOPT (Security Options) command displays or sets system security options.
On systems that do not have Secure Access Control Module software, the SECOPT
command can be used only for the following purposes:
Assign a value to the AUTHENTICATION option

Assign a value to the ENCRYPTION option
Assign a value to the GSSAPI option
Assign a value to the HOSTSRESTRICTED option
Assign a value to the LOGONATTEMPTS option
Assign a value to the OLDBKUPSECURITY option
Assign a value to the OLDDMSSECURITY option
Assign a value to the RESTRICTUNWRAP option
Change the security class from U to MINIMAL or vice versa
Interrogate the settings of the system security options
The SECOPT command is to be used only by the system security administrator or by
those acting for the security administrator. A description of the syntax and action of
the SECOPT command appears in the Security Administration Guide.
566 8600 0395-514

SEGARRAYSTART (Array Segmentation Start Size)

The SEGARRAYSTART (Array Segmentation Start Size) command displays or sets the
array size (in words) that the system uses to determine whether or not an array is to
be paged. The SEGARRAYSTART command also displays the page size for paged
arrays and the overlay row size. The maximum long array size and page size for
paged arrays cannot be changed. The overlay row size is changed using the
OVERLAY option of the DL (Disk Location) command.
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).
8600 0395-514 567

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.
SEGARRAYSTART <array size>

Changes the value that the system uses to determine whether new arrays are to be
paged.
Examples
Example 1
This example shows the response given to a SEGARRAYSTART inquiry:
SEGARRAYSTART
ARRAY SEGMENTATION START SIZE: 1024
MAXIMUM LONG ARRAY SIZE: 65535
PAGED ARRAY PAGE SIZE: 256
OVERLAY AREA SIZE IN SEGMENTS: 504
Example 2
This example causes a syntax error, because the array size is set too small:
SEGARRAYSTART = 200
SEGARRAYSTART VALUE TOO SMALL
Example 3
This example allows an unpaged array size of a minimum of 1,500 words:
SEGARRAYSTART 1500
ARRAY SEGMENTATION START SIZE: 1500
MAXIMUM LONG ARRAY SIZE: 65535
PAGED ARRAY PAGE SIZE: 256
OVERLAY AREA SIZE IN SEGMENTS: 504
568 8600 0395-514

SEND (Send Message)
SEND (Send Message)

Use the SEND (Send Message) command to communicate with the NPSUPPORT
library and the media library.
Syntax
8600 0395-514 569

SEND (Send Message)
<NP unit-related command>
<blockval>
An integer in the range of 10 through 2000.
<bufsize>
<dasname>
INTRASYSTEM/BNAV2ICPINITIALIZATION for BNA Version 2 network processors
(NPs).
570 8600 0395-514

SEND (Send Message)
<freeval>
<initval>
<maxval>
<wbufsize>
<wresize>
<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.
There are two types of NP unit-related command options: diagnostic and

nondiagnostic. You can enter diagnostic options only when a diagnostic NPSUPPORT
library is being used. In other words, the SEND NP diagnostic options cannot be
used unless the NPSUPPORT library is compiled with the DIAGNOSTICS option.
8600 0395-514 571

SEND (Send Message)
Otherwise, an INVALID OPERATOR INPUT message is returned. You can enter

nondiagnostic options any time that the NPSUPPORT library is active. The following
are the diagnostic options:
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
BUFFERSIZE 9000 (bytes)
MAXINPUTS 45
BLOCKTIMEOUT 100 (milliseconds)
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.
572 8600 0395-514

SEND (Send Message)
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.
Note: Starting with ClearPath MCP Release10.0 , the NP/SUPPORT/RECOVERY file is

locked to avoid inadvertent deletion. The system administrator must explicitly unlock
the file before it can be removed.
You can determine the values of NP options that are currently present by entering
the following command:
SEND NP <unit number> :ID
If you want to modify the values of the NP options, you must enter a command that
is structured in the following manner:
SEND NP <unit number> <option> = <value>
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.
8600 0395-514 573

SEND (Send Message)
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:
Set the blocking option for the DLP.

Reinitialize the ICP DLP.
BLOCKTIMEOUT
BLOCKTIMEOUT <blockval>
Display or set the amount of time (in milliseconds) the ICP is to wait before sending
a set of blocked messages to the host. You can change the value of <blockval> at
any time. 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. The default value is
100 milliseconds.
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.
Refer to Example 1 for an example of a terminal display resulting from a

SEND NP <number> ID message.
574 8600 0395-514

SEND (Send Message)
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.
Possible DASNAME values are shown in the following table.
Processor DASNAME
Type
BNAV2 NPs INTRASYSTEM/BNAV2ICPINITIALIZATION
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:
WAITING FOR <dasname>
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
8600 0395-514 575

SEND (Send Message)
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.
576 8600 0395-514

SEND (Send Message)
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:
Closes the current tank file.

Changes the file name to NP/TANKED/INPUT/xxx/<date>/<time>.
Opens a new tank file.
SET <option>
RESET <option>
Sets or resets any of the following options: AUTOLOAD, BLOCKING, DIAGNOSTICS,
and TANKING. For more information, see the description of the individual options.
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:
When an NP is initialized, the size of each host-to-NP write buffer is 90 bytes.

(No value is specified for WRITEBUFFERSIZE).
When a host-to-NP request is processed, a write buffer is expanded to the
exact size requested. (No value is specified for WRITERESIZEINCREMENT and
WRITERESIZETOMAX is RESET.)
When a subport file is closed, the write buffer is resized down to 1 byte. (No
value is specified for WRITERESIZEVALUE and WRITENORESIZE is RESET.)
To avoid adverse processor usage when writing to a port file or when port files are
closed, you can change this default processing. The following options are available
for use by each NP:
WRITEBUFFERSIZE. Specifies the initial size of each host-to-NP buffer in

bytes. If this option is not specified or zero, the write buffer size defaults to
90 bytes when the NP/CONTROLLER stack initializes. Setting
WRITEBUFFERSIZE to its current minimum value (128) includes the 30 bytes
needed for control headers in addition to the default size.
8600 0395-514 577

SEND (Send Message)
WRITERESIZEINCREMENT. Specifies the increment value to use when a new

host-to-NP request requires a buffer that is larger than the current buffer
size. If this option is not specified or zero and the WRITERESIZETOMAX option
is RESET, the write buffer size defaults to the exact size requested. If this
option is non-zero, WRITERESIZETOMAX is ignored and the
WRITERESIZEINCREMENT value is the number of extra bytes added to the
actual request size when a write buffer is too small. If the write request sizes
for a port are clumped, then the RESIZE overhead can be reduced.
WRITERESIZETOMAX. Specifies whether or not to use the MAXRECSIZE value
for the port when a new host-to-NP request requires a buffer that is larger
than the current buffer size. If this option is RESET (the default), the
MAXRECSIZE is not used. If this option is SET and the
WRITERESIZEINCREMENT is not specified or zero, the write buffer is
immediately resized to the value of the MAXRECSIZE. Setting this option
reduces the number of RESIZE requests but uses more memory.
WRITENORESIZE. Specifies whether or not to use the WRITEMAXBUFFERSIZE
and WRITERESIZEVALUE options to control resizing the write buffer. If this
option is RESET (the default), the WRITERESIZEVALUE controls the resizing.
If this option is SET, the write buffer is not resized unless the largest request
size is larger than the WRITEMAXBUFFERSIZE. If so, the WRITERESIZEVALUE
controls the resizing. Setting this option reduces the number of RESIZE
requests.
WRITERESIZEVALUE. Specifies the new size of the write buffer after it has
been resized when a subport file is closed. If this option is not specified or
zero and the WRITENORESIZE option is RESET, the buffer size defaults to 1
byte. If the WRITENORESIZE option is SET, the WRITERESIZEVALUE is used
only if the WRITEMAXBUFFERSIZE has been exceeded in a request.
WRITEMAXBUFFERSIZE. Valid only when the WRITENORESIZE option is set. If
this option is non-zero, the value specifies the threshold to determine if a
buffer needs to be resized when a subport file is closed. The buffer is resized
only if the largest request size was larger than the WRITEMAXBUFFERSIZE. If
this option is not specified or zero, it has no effect.
Use the following option settings to ensure that the new WRITEBUFFER options result
in the same operations as in previous releases.
Option Setting
WRITEBUFFERSIZE 128
WRITERESIZEINCREMENT 0 (the default)
WRITENORESIZE RESET
WRITERESIZEVALUE 1
WRITEBUFFER Reporting Options

You can use reporting options to determine the actual buffer sizes that need to be
requested at your site.
578 8600 0395-514

SEND (Send Message)
The following options can be specified for each NP independently to report

information about the host-to-NP message buffering operation:
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
NP7002 NPSUPPORT LIBRARY: *SYSTEM/BNAV2/NPSUPPORT.

VERSION: 52.104.1; COMPILED: 8/9/2004 @ 09:57:32
FIRMWARE LEVEL: 0800E1010400
DASNAME: INTRASYSTEM/BNAV2ICPINITIALIZATION
BUFFERSIZE: 65280 BYTES
LARGEST INPUT BUFFER: 65280 BYTES
BLOCKTIMEOUT: 100 MILLISECONDS
MAXINPUTS: 45
FREEINPUTS: 5
INITIALREADS: 10
ACTIVE UNITS: 2 ACTIVE USERS: 3 WAITING USERS: 0
8600 0395-514 579

SEND (Send Message)
OUTPUT FILES: ON PACK

WRITE (HOST-TO-NP) PARAMETERS
WRITEBUFFERSIZE: 90
WRITEMAXBUFFERSIZE: 0
WRITERESIZEINCREMENT: 0
WRITERESIZETOMAX: RESET
WRITENORESIZE : RESET
WRITERESIZEVALUE: 1
WRITEBUFFERSTATS: RESET
WRITEGRANULARITY: 0
WRITEONEFILE: RESET
WRITECUMULATIVESTATS: RESET
RUN TIME OPTIONS:
AUTOLOAD: SET
DIAGNOSTICS: RESET
TANKING: RESET
BLOCKING: SET
COMPILE TIME OPTIONS:
NO OPTIONS SET
QSP LEVEL: 2 PHYSICAL PIPES: 2 SIMULATED PIPES: 16
MAX MULTIAREA BUFFERS: 3
READS PER MIN: 434
Example 2
This example shows a sample write buffer statistics report:
SEND NP<unit number>: REPORTWRITESTATS
MP040 NP 159 5/12/2005 15:54:33

BUF SIZE 2000 RESIZE INCREMENT 400 NO RESIZE DOWN MAX BUF
SIZE 2000 RESIZE DOWN SIZE 2000
BUFFERS USED 16 RESIZES(UP 34 213% TOO LARGE 15 94% )
150-199(1) 2850-2899(5) 3050-3099(10) ** 100%
MP040. NP 159 5/12/2005 15:59:13

BUF SIZE 2004 RESIZE INCREMENT 400 NO RESIZE DOWN MAX BUF
SIZE 3090 RESIZE DOWN SIZE 2000
BUFFERS USED 15 RESIZES(UP 5 33% )
2850-2899(5) 3050-3099(10) ** 100%
MP040. NP 159 5/12/2005 16:02:27

BUF SIZE 2004 NO RESIZE DOWN MAX BUF SIZE 3090 RESIZE DOWN
SIZE 3054
BUFFERS USED 15 RESIZES( )
2850-2899(5) 3050-3099(10) ** 100%
580 8600 0395-514

SEND (Send Message)

Certain changes specified in the SEND NP command (BLOCKING, BLOCKTIMEOUT,
FREEINPUTS, INITIALREADS, and MAXINPUTS) do not take effect until the system
either creates a new NP/CONTROLLER/nnn stack for the unit or reinitializes the
NPSUPPORT library. The NP/CONTROLLER/nnn is an invisible independent runner.
You cannot verify its existence by entering an AA command, but you can determine
its presence by entering the OL NP command.
To create a new stack, perform the following steps:
1. To make the network processor inaccessible to the system, enter the

following syntax:
SV NP <unit number>
2. To clear the network processor, enter the following syntax:

CL NP <unit number>
3. To make the network processor ready for use, enter the following syntax:
RY NP <unit number>
Media Library System Commands

The following are valid media library system commands.
To send lowercase characters to TAPEMANAGER or TAPESERVER, enclose the <text>

in quotation marks. Both the quotation marks and the <text> are sent.
SEND TAPESERVER START

SEND TS START
Initiate the TAPESERVER library.
SEND TAPESERVER START <text>

SEND TS START <text>
Initiate the TAPESERVER library and pass text to its initiation routine.
SEND TAPESERVER QUIT

SEND TS QUIT
Terminate the TAPESERVER library.
SEND TAPESERVER QUIT <text>

SEND TS QUIT <text>
Terminate the TAPESERVER library and send text to its termination routine.
SEND TAPESERVER STATUS

SEND TS STATUS
Display the current status of the TAPESERVER library.
8600 0395-514 581

SEND (Send Message)
This version of the command can return the following states:
Inactive
Linking
Initializing
Active
Terminating
Waiting to delink
SEND TAPESERVER <text>
SEND TS <text>
Pass text to the TAPESERVER.
SEND TAPEMANAGER START

SEND TM START
Initiate the TAPEMANAGER library.
SEND TAPEMANAGER START <text>

SEND TM START <text>
Initiate the TAPEMANAGER library and pass text to its initiation routine.
SEND TAPEMANAGER QUIT

SEND TM QUIT
Terminate the TAPEMANAGER library.
SEND TAPEMANAGER QUIT <text>

SEND TM QUIT <text>
Terminate the TAPEMANAGER library and pass text to its termination routine.
SEND TAPEMANAGER STATUS

SEND TM STATUS
Display the current status of the TAPEMANAGER library.
SEND TAPEMANAGER <text>

SEND TM <text>
Pass text to the TAPEMANAGER.
Examples
Example 1
This example initiates the TAPESERVER library:
SEND TS START
TAPESERVER WILL START
582 8600 0395-514

SEND (Send Message)
Example 2
This example stops the TAPEMANAGER library:
SEND TM QUIT
TAPEMANAGER WILL QUIT
As an alternate reply, you might also see the following message:
TAPESERVER OPTION RESET, INACTIVE
Example 3
This example asks for the status of the TAPESERVER library:
SEND TS STATUS
TAPESERVER OPTION SET, ACTIVE, MIXNUMBER 892
Example 4
This example passes the text HELLO to the TAPEMANAGER library:
SEND TM HELLO
OPERATOR TEXT FORWARDED TO TAPEMANAGER
8600 0395-514 583

SF (Set Factor)
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.
Factor <number> Range Units
1 0 through 99 %
2 0 through 99 %
3 0 through 999 %
5 0 through 65535 words
6 0 through 100 %
7 0 through 100 %
Explanation
SF
Displays the current memory management parameters:
584 8600 0395-514

SF (Set Factor)
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:
0.1% + (OLAYGOAL * 0.05%)
If OLAYGOAL and AVAILMIN are not both 0, WS_SHERIFF performs the following
tasks:
1. Moves non-overlayable memory out of high memory.

2. Moves overlayable memory out of low memory.
3. Compacts non-overlayable memory.
4. Combines adjacent small available memory areas into larger available
memory areas.
When the value of OLAYGOAL is greater than 0, overlaying is enabled for
WS_SHERIFF, and OLAYGOAL is used as follows:
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.
8600 0395-514 585

SF (Set Factor)
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 STRICTSCHED option (option 39) is set:
The amount of physical memory is multiplied by FACTOR% and used as a limit in

determining if a task will run or will be entered into the "scheduled" state. If the in
use memory + overlaid memory + task memory estimate exceeds this number, the
task will be "scheduled". For example, if the total memory on the system is
100,000,000 words, and the FACTOR is set to 110, the amount of memory in use or
overlaid cannot exceed 110,000,000, regardless of how much memory is available.
This means that a task that requires 1,000,000 words to run, will be scheduled if the
in-use memory adds up to 100,000,000 and the overlaid memory is 9,100,000
words, i.e. (100,000,000 + 9,100,000 + 1,000,000) = 110,100,000 words, which is
greater than 110,000,000 words.
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
586 8600 0395-514

SF (Set Factor)
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
1) OLAYGOAL = 5% PER MINUTE

2) AVAILMIN = 10%
3) FACTOR = 110%
4) Not Used
5) BUFFERGOAL = 5000 (DEFAULT)
6) OLAYSATURATION = 15%
7) OLAYCHANGE = 10%
Example 2
This example sets factor 2 (AVAILMIN) to 10 percent and factor 1 (OLAYGOAL) to 5
percent:
SF 2 10 1 5
1) OLAYGOAL = 5% PER MINUTE

2) AVAILMIN = 10%
3) FACTOR = 110%
4) Not Used
5) BUFFERGOAL = 5000 (DEFAULT)
6) OLAYSATURATION = 15%
7) OLAYCHANGE = 10%
Example 3
This example sets factor 5 (BUFFERGOAL) to its default value:
SF BUFFERGOAL 0
8600 0395-514 587

SHARE (Shared Family)

The SHARE command specifies whether a disk family is to be shared between
multiple hosts, and specifies that the current host is the master host. The system
limits the actions that programs and operators can perform on shared disk families.
Programs running on the master host can perform more actions on the shared disk
family than programs running on other hosts.
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:
Create new files or copy files to the shared disk family.

Expand existing files by writing new data beyond the old end-of-file marker or
allocating new areas of the file.
Retitle or modify the attributes of files on the shared disk family.
Regardless of the host they are running on, programs are restricted from performing
the actions listed under Restrictions on Programs later in this topic.
To be shared, a disk family must have a local system access directory. Refer to the
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.
588 8600 0395-514

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:
Halt/load the other host.

Use the FREE PK <unit number> and ACQUIRE PK <unit number>
commands on the other host for each pack in the shared family.
Use the CLOSE PK <unit number> and READY PK <unit number>
commands on the other host for each pack in the shared family.
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
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.
SHARE <family name>

Removes the shared status of a disk family.
8600 0395-514 589

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
DS Aborts the SHARE <family name> process.
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.
SHARE TAKEOVER <family name>

Designates the host where the command is entered as the new master host for a
shared disk family.
To process the SHARE TAKEOVER system command, the system starts an

independent runner named SHARE TAKEOVER <family name>. If the disk family is
not shared or the host that the command was executed on is already the master
host, a corresponding error message is generated.
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.
590 8600 0395-514

Examples
Example 1
This example marks the disk family named WORK as a shared family with level 1
sharing capabilities:
SHARE + WORK LEVEL = 1
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:
SHARE TAKEOVER WORK

Prerequisites
The shared disk feature can be used for any type of disk unit, including
variable sector size disks using VSS-1 or VSS-2 180-byte emulation.
The shared disk must have a local system access directory. For information
about local system access directories, refer to the FAMILYACCESS (Directory
Location) command.
Shared disk functionality is packaged with the Continuous Service Platform
(CSP) product, so it requires the CSP license key.
All hosts must have the SYSOPS LONGFILENAMES option established to the
same value, either SET or RESET.
Restrictions on Disks
A disk of any of the following types cannot be marked as a level 1 shared disk
family:
A disk selected by the CM (Change MCP) system command

A disk selected by the DN (Dump Name) system command
A disk selected by the DL (Disk Location) system command
A memory disk, mirrored disk, or cached disk family
Restrictions on Programs
Programs cannot perform the following actions:
Remove or replace existing files on a shared disk family.

Use the row exchange intrinsic to swap rows of files residing on a shared disk
family.
8600 0395-514 591

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
Additionally, programs running on non-master hosts cannot create a new file

(temporary or permanent) on the shared disk family.
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.
Restrictions on WFL Statements

WFL jobs, operators, and users of MARC and CANDE can use various WFL statements
that affect disk files. Following are partial lists of the statements that are allowed and
disallowed on a shared disk family.
You can use the following WFL statements:
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:
MOVE or ARCHIVE ROLLOUT statements to copy files from a shared disk

family.
Certain library maintenance statements (such as MOVE, REPLACE, ARCHIVE
RESTORE, or ARCHIVE RESTOREADD) that attempt to copy files to a shared
disk family.
REMOVE or ARCHIVE RELEASE statements.
Statements related to cataloging: VOLUME ADD statements, CATALOG
statements, and COPY or ADD statements with the BACKUP option.
Restrictions on System Commands
Operators, users of MARC, and programs that call GETSTATUS, DCKEYIN, and
SETSTATUS can issue various commands that affect disks. The following are partial
lists of the system commands that are allowed and disallowed on shared families.
592 8600 0395-514

You can use the following system commands:
PER, OL, SV, RY, CLOSE, FREE, and ACQUIRE

PD, PDRES, and SHOWOPEN
SL, SI, and CS
MP, RP, and XD (allowed only on the master host for the disk family).
RC, LB, and PG. Note that the system does not proceed with the action until
the operator replies to an RSVP that the FREE system command has been
used to release the disk from use on all hosts sharing the disk family.
The RC PK <unit number> ... BP = <serial number> command, which adds
disks to a shared disk family (allowed only on the master host for the disk
family).
Do not use the following system commands:
REPLACE, if the source or destination disk family is shared

RES and SQUASH
DD and FAMILYACCESS CENTRAL
Other Considerations
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.
8600 0395-514 593

2. Use the following system command to cancel the shared status of the disk
family:
SHARE - <family name>
3. Make the necessary changes to the files on the disk family.

4. Use the following system command to restore shared status to the disk
family:
SHARE + <family name> LEVEL = 1
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.
594 8600 0395-514

SHOW
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.
You can use the SHOW command to
Get a report on what is in the mix.

Identify disk packs or magnetic tapes.
Get reports about disk drives or magnetic tapes.
Syntax
<object type>
<attribute list>
<attribute selection>
<wild card>
<delim>
/ \ I ~ ! @ # $ % ^ & * ' .
8600 0395-514 595

SHOW
<date value>
For <date value>
<month> is two digits representing the selected month.

<day> is two digits representing the day of the month.
<year> is four digits representing the year.
TODAY selects today's date.
<integer value> is used to adjust today's date by the number of specified
days. A minus sign must precede the 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.
You can specify the following attributes in the attribute list.
ACCESS String Process access code
ASDSINUSE Integer Number of ASDs in use
CHARGE String Process charge code
CODEFILE String Title of the object code file
CODEMEMORY Integer Memory used by the segment dictionary of the

process
COMPILER Boolean TRUE if the process is a compiler
CONTROL Boolean TRUE if the process is a control program
CPURATE Integer Recent processor usage of the process as a

percentage
CPUTIME Integer Process processor time
596 8600 0395-514

SHOW
IDENTITY String Process identity (from MP <code> + IDENTITY)
INITPBITS Integer Count of initial presence bits
INITPBITTIME Integer Processor time used for initial presence bits
IOTIME Integer Process I/O time
JOBNO Integer Process job number
LOCKED Boolean TRUE if the process is a locked program
MEMORY Integer Process total memory
MIXNO Integer Process mix number
MPID String The MPID attribute of the process
NAME String Process name
ORGLSN Integer LSN of originating station
ORGSTATION String Station name where process originated
OTHERPBITS Integer Count of non-initial presence bits
OTHERPBITTIME Integer Processor time used for non-initial presence bits
PRIORITY Integer Process priority
PU Boolean TRUE if the process is a privileged program
QUEUE Integer The job queue, if any, that is the source of the
process
READYQTIME Integer Process ready queue time
RELEASEID String Release identity of process
SAVEMEMORY Integer Save memory in use by the process
SAVECODEMEMORY Integer Save memory used by the segment
SECADMIN Boolean TRUE if the process has SECADMIN privilege

from the MP SECADMIN command
SUPPRESSED Boolean TRUE if the process is suppressed
TASKING Boolean TRUE if the process has tasking
8600 0395-514 597

SHOW
USER String Process user code
SHOW LIBS <attribute list>

Displays the selected attributes for all libraries.
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.
SHOW PK <attribute list>

Displays the selected attributes for all disks.
Each line of the output begins with the unit number, followed by the attribute values,
and then followed by the disk name.
You can use the following attributes in the attribute list.
AVAILSECTS Integer Available sectors on a pack
BASEUNIT Integer Unit number of a base pack
CACHED Boolean TRUE if unit is being cached
CAPACITY Integer Capacity of a pack in sectors
CERTIFIED Boolean Certification status of mirrored pack
CERTTIMESTAMP Date Timestamp of mirror certification
FAMILYINDEX Integer Index of family member
IOTIMER Integer Timeout value in effect for READ and WRITE

operations on a pack
LARGESTSZSECTS Integer Largest single area available on a pack
LOCALACCESS Boolean TRUE if unit uses local system access directory
MIRRORED Boolean TRUE if unit is a member of a mirrored set
NAME String Pack name
598 8600 0395-514

SHOW
ONLINE Boolean TRUE if unit is on line
QUEUEDEPTH Integer Number of I/Os waiting for a pack
REMOTEDISK Boolean TRUE if unit is a remote disk device
SCRATCH Boolean Purged pack unit
SERIAL String Serial number of a pack
SHARED Boolean TRUE if unit is shared
SITENAME String StoreSafe site name
SPARE Boolean TRUE if unit has been entered in the spare disk
pool (as either a free spare or an in-use spare)
STORESAFESTATUS String StoreSafe status
TOTALIOS Integer Total number of reads from a pack and writes

to a pack
TOTALREADS Integer Total number of reads from a pack
TOTALWRITES Integer Total number of writes to a pack
type String Acceptable values:

B = base pack
C = continuation pack
UNITNO Integer Unit number
VSSTYPE Integer Acceptable values:

0 =180-byte disk
1 =VSS-1 disk
2 =VSS-2 disk
SHOW MT <attribute list>

Displays the selected attributes for all tapes.
Each line of the output begins with the unit number, followed by the attribute values,
and then followed by the tape name.
8600 0395-514 599

SHOW
The following attributes can be used when mounted tapes are the target of a SHOW
command.
Attribute Type Description

Name
MIX Integer Mix number of the program using tape
NAME String Tape name
SCRATCH Boolean TRUE if tape mounted is a scratch tape
SCRATCHPOOL String Scratch pool of mounted tape
SERIAL String Serial number
TOTALREADS Integer Total number of reads of tape on the drive
TOTALWRITES Integer Total number of writes to the tape on the

drive
UNITNO Integer Unit number of tape drive
SORT + <sort attribute>

SORT <sort attribute>
Sorts the lines of output based on the value of the specified sort attribute. The
attributes must be appropriate for the object type (MIX, LIBS, PK, or MT). A plus sign
(+) requests a sort in ascending order. A minus sign () requests a sort in descending
order.
The sort attribute cannot be a Boolean attribute.
The sort attribute can be the same as one of the attributes in the attribute list, but it
does not have to be.
SELECT <object type> <Boolean attribute> = TRUE

SELECT <object type> <Boolean attribute> = FALSE
SELECT <object type> <Boolean attribute>
A value of TRUE selects objects for which the attribute has a value of TRUE.
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.
SELECT <integer> <relation> <integer value>

Selects objects with a integer attribute that satisfies the relation. For example,
SELECT MIX MEMORY > 5000 returns all mix entries using greater than 5000 words
of memory. Following are the possible relations.
600 8600 0395-514

SHOW
Relation Meaning
= Equal to
<> Mot equal to
> Greater than
>= Greater than or equal to
< Less than
<= Less than or equal to
SELECT <string attribute> <wild card string>

Shows objects with a string attribute matching the wild card string. The string can
include the following special characters.
Equal sign ( = ) Matches any sequence of characters
Question mark ( ? ) Matches any single character
Tilde ( ~ ) Matches any sequence of characters except a slash ( /)

space character.
contain the string "SYSTEM":
SHOW MIX MEMORY SELECT NAME =system=
"system":
SHOW MIX MEMORY SELECT NAME LIT ^=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.
8600 0395-514 601

SHOW
Examples
Example 1
The following example displays several attributes for each mix entry:
SHOW MIX NAME, CONTROL, LOCKED, PU
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:
SHOW MIX NAME, CPUTIME, IOTIME, READYQTIME, INITPBITTIME SORT - CPUTIME
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:
SHOW LIBS RELEASEID, SELECT NAME =COM=
7049 MCP 09.0 [50.150.000] (50.150.0027) *SYSTEM/MARC/COMMANDER

7044 MCP 09.0 [50.150.000] (50.150.0001) *SYSTEM/COMS/PROCESSING/ITEMS
6895 MCP 09.0 [50.150.000] (50.150.0088) *SYSTEM/COMS
7142 MCP 09.0 [50.150.000] (50.150.0010) *SYSTEM/COMS/PSH/TTP
7140 MCP 09.0 [50.150.000] (50.150.0088) COMS/PA/FACILITY
7034 MCP 09.0 [50.150.000] (50.150.0088) COMS/ROUTER
6808 MCP 09.0 [50.150.000] (50.150.0001) *SYSTEM/DATACOMSUPPORT
6826 MCP 09.0 [50.150.000] (50.150.0001) DATACOMSUPPORT/9
602 8600 0395-514

SHOW
Example 4
The following example displays various attributes for each disk unit:
SHOW PK AVAILSECTS, LARGESTSZSECTS, TOTALREADS, TOTALWRITES
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.
SHOW MIX RELEASEID NAME SELECT NAME =CAN= ALL
------------------------------------------------
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
8600 0395-514 603

SHOW
Example 8
The following example reports the certification timestamp for all certified mirrors
which were certified today.
SHOW PK SERIAL FAMILYINDEX TYPE NAME SELECT CERTTIMESTAMP = TODAY
UnitNo-Serial-FamilyIndex-Type-Certification Date and TimeStamp-Name

180 000180 1 B Mon, May 17, 2004 @ 14:40:03 T180
604 8600 0395-514

SHOWOPEN (Show Open Disk Files)

The SHOWOPEN command generates information on open disk files including the
owner of the file, the family, and family member information.
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.
8600 0395-514 605

Examples
Example 1
The following example displays information about all open files on the specified
family:
SHOWOPEN ON RFAM
*SYMBOL/PRINT/SUPPORT (NEWPSYMBOL) 66,528 Sectors

45856/7638 (GSTEIN) *OBJECT/ED
*XREFFILES/SYSTEM/PRINT/SUPPORT/REFS (DATA) 9,226 Sectors
45856/7638 (GSTEIN) *OBJECT/ED
(TQ)SYSTEM/TQ/SMFII/PROBE/LIBRARY (DCALGOLCODE) 1,998 Sectors
4957/4959 (TQ) (TQ)SYSTEM/TQ/SMFII/PROBE/LIBRARY/SCHEDULER ON DISKB
4957/4957 (TQ) (TQ)SYSTEM/TQ/SMFII/PROBE/LIBRARY ON DISKB
(RADU)SYSTEM/TCPPRTSUPPORT (DCALGOLCODE) SLed 4,698 Sectors
5030/5030 (RADU)SYSTEM/TCPPRTSUPPORT ON FIRE
(MP)LST/RECENT (DATA) 238 Sectors
7597/7597 (MP) (OPS)OBJECT/LST ON PACK
(CLIN)MAIL/INBOXINX (DATA) 80 Sectors
7617/7617 (CLIN) (MAIL)SYSTEM/RUNMAIL ON PACK
(RAID)OBJECT/SYMBOL/NED (DCALGOLCODE) 1,863 Sectors
8013/8013 (RAID) (RAID)OBJECT/SYMBOL/NED ON FIRE
(RAID)Q_FILE (DATA) Temporary File 0 Sectors
8013/8013 (RAID) (RAID)OBJECT/SYMBOL/NED ON FIRE
Example 2
The following example displays information about the users of the
SYSTEM/CARDLINE program on PACK:
SHOWOPEN SYSTEM/CARDLINE ON PACK
SYSTEM/CARDLINE (ALGOLCODE) 72 SECTORS

9269/4439 *SYSTEM/CARDLINE
0262/4435 *SYSTEM/CARDLINE
Example 3
The following example displays information about all open files with usercodes on the
family DISK:
SHOWOPEN USERCODE/= ON DISK
(DONP)SYSTEM/TIME/SUPPORT (NEWPCODE) Sled 2,340 Sectors

4490/4490 (DONP)SYSTEM/TIME/SUPPORT
606 8600 0395-514

SHOWSPARES (Show Spare Disks)

The SHOWSPARES command displays a list of disk packs which have been assigned
to the spare disk pool for the Mirrored Disk Pooling Facility (MDPF). For more
information about MDPF, see the System Administration Guide or the System
Operations Guide.
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.
8600 0395-514 607

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
------------------------- SPARE DISK POOL ---------------------------

226, 236-----------------------------------------------------------
100 *B [659002] #1 S P A R E
300 *B [659005] #1 S P A R E
3680 1440 FIPS-SEQ, 3680 1440 FIPS-INT-----------------------------
200 *B [659004] #1 S P A R E
3682---------------------------------------------------------------
71 *B [659006] #1 S P A R E
(1383)*B [659006] #1 R E S E R V E D
608 8600 0395-514

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
SYSTEM/X WILL BE LOADED
MSG
--Mix--Time--------------- MESSAGES ---------------------------------

6029 22:11 SYSTEM/X HAS BEEN LOADED
Example 2
SI +
SYSTEM/INTRINSICS WILL BE LOADED
MSG
--Mix--Time--------------- MESSAGES ---------------------------------

6039 22:13 SYSTEM/INTRINSICS HAS BEEN LOADED
8600 0395-514 609

Example 3
SI
INTRINSICS: SYSTEM/INTRINSICS
610 8600 0395-514

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>

Displays the current library associated with the function name and the attributes
associated with that library.
SL <function name>
Does one of the following:
If a change is pending for the function, SL cancels that change. A pending

change occurs when you enter the command SL <function name> = <file
title> for a ONEONLY function.
If the library for the function is not running, the system removes all
information for the function from the system tables.
8600 0395-514 611

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
To remove the ONEONLY function with a running library, proceed as follows:
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
3. Repeat the SL <function name> command.

When the system removes a function specification, all tasks already linked to the
library continue to use the old library. The system creates the following waiting entry
message for tasks that subsequently try to link to the function:
FUNCTION <function name> IS NOT DEFINED. DEFINE WITH SL OR DS.
SL <function name> = <file title>

Specifies the library code file that the system is to use for the designated function
name. If the function name is already defined, any library attributes associated with
the function name are retained. If the function name is not defined (not listed in an
SL display), but is defined in the MCP, the MCP automatically assigns attribute
values. The system responds as follows according to whether a library for the
function is already available (is frozen or has readied an interface) or has been
initiated by the library linking mechanism:
If a library for the designated function is not currently available or initiated,

the system changes the function association as requested.
If a library for the designated function is currently available or initiated and if
the function is not a ONEONLY function, the system changes the function
association as requested, and performs a thaw operation on the old library.
Tasks already linked to the old library continue to use it. Tasks that
subsequently attempt to link to the function use the new library. The old
library resumes and terminates automatically when all old users have
delinked, but you can also terminate it with a DS (Discontinue) command.
If a library for the designated function is currently available or initiated and if
the function is a ONEONLY function, the system changes the function
association to indicate that a new library code file is PENDING. If the <file
title> refers to the current active code file, and an assignment is already
pending, the pending assignment is removed (as if an SL - command had
been entered.) Tasks continue to use and link to the old library until the old
library resumes or a halt/load occurs. If required, you can terminate the old
612 8600 0395-514

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.
SL <function name> = <file title> : <attributes>

Specifies the library code file that the system must use for the designated function
name. Sets the attributes associated with the library, as specified. The library
attributes are described in the following syntax explanation.
SL <function name> : <attributes>

Sets the attributes associated with the library, as specified, and displays the library
associated with the function name.
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.
The library attributes have the following uses:
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.
Class Value Description
0 (default) Unprotected. Programs of any linkage class can link to the

library.
1 Only programs of linkage class 1 can link to the library.
2 to 7 Reserved for use by system software.
8600 0395-514 613

Class Value Description
8 to 15 Free for site-dependent definition and use.
Linkage classes of 2 to 5 have been defined as follows.
Class Type Classes Allowed to Link to
2 MCS 0, 2, 3, 4
3 Environment 0, 3, 4
Libraries
4 Privileged 0, 4
Programs
5 Compilers 0, 5
A code file is defined as a privileged program by the PU option of the MP (Mark

Program) system command.
The linkage class of a stack is determined at the time the stack is initiated. For a
library initiated BYFUNCTION, the linkage class is determined from the
LINKCLASS associated with the function name. Linkage classes 4 and 5 are
determined from the privileges of the code file.
MCPINIT
If set, the library can only be initiated BYFUNCTION by the MCP. The library code
file can still be initiated by a PROCESS or RUN construct, or it can be initiated by
title as long as the appropriate security considerations for access to the code file
are met.
ONEONLY
If set, this attribute indicates that only one version of the library code file is
permitted to be in use on the system at any one time.
SYSTEMFILE
If set, this attribute indicates that the library code file is to be made a
nonremovable system file when it is initiated or mapped to a library code file with
the SL command.
TRUSTED
If set, this attribute indicates that the code in the file is trusted code. This means
that the system uses the linkage class assigned to an individual library procedure
to determine whether a user program can access that procedure. If this attribute
is reset, the system uses the linkage class designated by LINKCLASS to
determine whether a user program can access a procedure in the library.
614 8600 0395-514

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
FUNCTION "USERFUNCTION = (USER)SYSTEM/USERLIBRARY" ESTABLISHED
Example 4
SL * PRINTSUPPORT
MCPINIT, TRUSTED, ONEONLY, LINKCLASS=1
Example 5
SL PRINTSUPPORT = *SYSTEM/PRINT/SUPPORT/V2
FUNCTION "PRINTSUPPORT = *SYSTEM/PRINT/SUPPORT/V2"

WILL BE ESTABLISHED
SL PRINTSUPPORT
*SYSTEM/PRINT/SUPPORT/V2 (PENDING)
Example 6
SL - USERFUNCTION
FUNCTION "USERFUNCTION" IS NO LONGER ESTABLISHED
Example 7
SL - PRINTSUPPORT
PENDING TITLE FOR "PRINTSUPPORT" IS REMOVED
8600 0395-514 615

Example 8
SL USERFUNCTION = SYSTEM/TADSFILE
FUNCTION "USERFUNCTION = SYSTEM/TADSFILE" ESTABLISHED

WARNING: FILE IS TADS-CAPABLE
Example 9
SL COMSSUPPORT: -MCPINIT, LINKCLASS=2
LIBRARY ATTRIBUTES NOT CHANGEABLE
Example 10
SL NEWFUNCTION = SYSTEM/NEWFUNCTION : TRUSTED, LINKCLASS = 1
FUNCTION "NEWFUNCTION=SYSTEM/NEWFUNCTION" ESTABLISHED,

ATTRIBUTES CHANGED

Because the system maintains the function-mapping tables for the library linkage
mechanism, a program can access a library through the appropriate function name.
The SL command provides the ability to change to new libraries without affecting any
running programs or requiring a new library name to be compiled into the calling
program.
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:
When the system halt/loads

When the disk that contains the code file is closed
When you enter a new SL <function name> = <file title> command for the
function
A program can access the mapping tables by using the LIBACCESS and
FUNCTIONNAME attributes available in ALGOL, Pascal, and NEWP.
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.
616 8600 0395-514

Access to a support library function can be controlled through the security

specifications of the code file for that function.
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:
FUNCTION "XXX = YYY" WILL BE ESTABLISHED
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.
8600 0395-514 617

SM (Send to MCS or Database)

The SM (Send to MCS or Database) command sends a control command to an MCS
or data base.
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.
5268 SM : SS ALL HELLO
MSG
--Mix--Time------------------ MESSAGES ----------------------------

*5268 16:26 DISPLAY: #.
618 8600 0395-514

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
---Mix-Pri--Usr----------------- 1 ACTIVE DATABASE -------

30679 50 1 Job (ADM) (ADM)TESTDB
30679 SM STATUS
---Mix-Time--------------------- 21 MESSAGES -------------------------

30679 16:46 DISPLAY:OPEN COUNTS: INQUIRY =0, UPDATE = 1.
30679 16:46 DISPLAY:FORCED OVERLAYS = 0.
30679 16:46 DISPLAY:SYNC WAIT IS 0 SECONDS.
30679 16:46 DISPLAY:OVERLAYGOAL = 1 % ALLOWEDCORE / MINUTE.
30679 16:46 DISPLAY:RESIDENT TOTAL:ALLOWED=100000,IN USE=0.
30679 16:46 DISPLAY:CORE TOTAL:ALLOWED=200000,IN USE=24,OLAYRATE= 0%.
30679 16:46 DISPLAY:CONTROL POINT AGING AFTER AUDIT SWITCHES = FORCE.
30679 16:46 DISPLAY:SYNCPOINT = 1, CONTROLPOINT = 1.
30679 16:46 DISPLAY:CURRENT AUDIT SECTIONS = 1, CF AUDIT SECTIONS = DEFAULT.
30679 16:46 DISPLAY:CURRENT AUDIT BUFFERS = 11, CF AUDIT BUFFERS = AUTOMATIC .
30679 16:46 DISPLAY:AUDIT BLOCKSIZE = 120, AREASIZE = 400, AREAS = 1.
30679 16:46 DISPLAY:AUDIT FILE# = 1,BLOCK SERIAL# = 73 (148/399=37%).
30679 16:46 DISPLAY:POPULATIONWARN IS NOT AVAILABLE FOR THIS DB.
30679 16:46 DISPLAY:POPULATIONINCR IS NOT AVAILABLE FOR THIS DB.
30679 16:46 DISPLAY:AUDIT PROCESSOR TIMES OFF.
30679 16:46 DISPLAY:PRINT STATISTICS = OFF.
30679 16:46 DISPLAY:TRACKERQPFACTOR = 1.
30679 16:46 DISPLAY:TRACKERFLUSHDB = 10.
30679 16:46 DISPLAY:(ADM)TESTDB: DMSII ACCESSROUTINES 46.141.0287.
8600 0395-514 619

SN (Serial Number)
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:
MT nn CONFIRM PURGE <tape name> [<serialno>] OK OR DS
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:
MT <unit number> THIS TAPE VOLUME HAS A RESIDENT 'LIBMAINTDIR' TAPE

DIRECTORY DISK FILE: <file name>
MT <unit number> TO LEAVE THIS TAPE AS IS REPLY 'DS'; TO PURGE IT

REMOVE THE 'LIBMAINTDIR' FILE OR REPLY 'OK'
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
<SN option list>
620 8600 0395-514

SN (Serial Number)
<density>
<scratch pool>
<scratch pool name>
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
SN MT <SN option list> (<density>)

Purges and assigns the specified serial number in bytes per inch (a numeric value) or
as a density mnemonic abbreviation (an alphanumeric string). If the density is
specified, it applies to all tapes mounted on the units in the unit number list. Only
certain tape drives permit you to change tape density. Refer to the documentation
for your tape drive to see if it fits into this category.
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.
8600 0395-514 621

SN (Serial Number)
SN MT <SN option list> <scratch pool>

Purges the tape and assigns the specified serial number and scratch pool name.
Refer to the File Attributes Programming Reference Manual for more information.
SN MT <SN option list> COMPRESSED

If the tape is mounted on a drive that supports compression, purges the tape,
assigns the specified serial number, and marks the label to indicate that compression
was requested. If the tape is mounted on a device that does not support
compression, the system does not perform the purge request and displays the
following message:
MTnnn UNIT DOES NOT SUPPORT COMPRESSION
For more information about this option, refer to Considerations for Use later in this
topic.
SN MT <SN option list> NONCOMPRESSED

Purges the tape mounted on the designated tape unit, assigns a serial number to the
tape, and marks the tape label to indicate that compression was not requested.
SNL MT <SN option list>

SNL MT <SN option list> (<density>)
SNL MT <SN option list> <scratch pool>
SNL MT <SN option list> COMPRESSED
SNL MT <SN option list> NONCOMPRESSED
Purge and lock the specified tape unit, so that no job can automatically acquire the
tapes as scratch tapes. You can assign the tape to a specific scratch pool and
designate that the tape be either compressed or noncompressed. To unlock the unit,
you ready the units with the RY (Ready) command. The locked status of a tape drive
is not preserved over a halt/load of the system.
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).
SN MT 115 X232 (1600)
MT 115 WILL BE SN-ED
PER MT
115*P [X232 ] 1600 #1:0 S C R A T C H
622 8600 0395-514

SN (Serial Number)
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.
SNL MT116 565 (1600)
PER MT
116*P [000565] 1600 LOCKED
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.
SN MT116 565 POOL = XYZ
Example 4
and has a tape label written to indicate that compression was requested.
SN MT55 444 COMPRESSED
MT 55 WILL BE SN-ED COMPRESSED
Example 5
and has a tape label written to indicate that compression was not requested.
SN MT45 875 NONCOMPRESSED
MT 45 WILL BE SN-ED NONCOMPRESSED
Example 6
assigned to a scratch pool named ABC, and has a tape label written to indicate that
compression was not requested.
SN MT55 334 NONCOMPRESSED SCRATCHPOOL = ABC
MT 55 WILL BE SN-ED NONCOMPRESSED
8600 0395-514 623

SN (Serial Number)

Scratch Pool Considerations
Unlabeled tapes are treated as though they were from the default (no name) pool.
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
If you do not specify a compression keyword and the drive is compression-capable,

the system retains the original compression specification on the tape. If the tape is
unlabeled, the system purges the tape with compression.
624 8600 0395-514

SQ (Show Queue)
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.
The job name field is constructed as follows:
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>.
The CONTROLLER returns the following response for the SQ <number> if

<number> is not defined:
SPECIFIED QUEUE(S) NOT DEFINED
If the SQ <number> command is used and the system has no previously defined
queues, the system returns the following response:
SYSTEM HAS NO QUEUES DEFINED
SQ <number> <number>
Displays all entries in the queue indicated by the first number whose priority is equal
to the second number.
SQ <queue number list>

Displays the fetch status, mix number, priority, usercode, queue entry time, start
time, and job name of every job in the specified queues. The queues are displayed in
the order specified in the queue number list.
8600 0395-514 625

SQ (Show Queue)
Examples
Example 1
SQ
QUEUE 45 (SINGLE ENTRY):

9533 50 BEGIN JOB;
QUEUED: 09/13/2002 AT 18:37:44
QUEUE 1
NO ENTRIES
QUEUE 0 (FIRST OF 2 ENTRIES):
8391 50 BEGIN JOB DIRDUMP(BOOLEAN HARDCOPY);
Example 2
SQ50
QUEUE 50
6630 50 JOB B;
QUEUED: 10/21/2002 AT 19:01:21
6631 50 ADDOUT
6633 50 RUNNERS;
6635 50 (SITE)RUNNERS
6637 50 PRINT/A/JOB (1600)
626 8600 0395-514


The SQUASH command tries to move allocated areas on disk so as to reduce
fragmented disk allocation and to create larger available areas.
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.
SQUASH <family name> (<family index>)

Only the family member specified by <family index> is compacted.
Examples
This example starts a process to compact the allocated space on the family named
DMSIITEST.
SQUASH DMSIITEST

The SQUASH procedure does not move areas of files from one pack in a family to
another pack in the family.
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:
If the fragmentation of available space is severe, a SQUASH command might

not be able to move any areas, or might result in making the largest available
area smaller.
A SQUASH operation is most successful if it is done before the available space
is severely fragmented. As a preventive measure for disks that are prone to
fragmentation, it is recommended that a SQUASH operation be performed
routinely during non-peak processing hours.
8600 0395-514 627

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.
628 8600 0395-514

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).
The response is determined by the controlling message control system (MCS).
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.
To send lowercase characters to a station, enclose the <user text> in quotation

marks. Both the quotation marks and the <user text> are sent to the station.
Examples
SS M601: YOU HAVE A STOPPED JOB
SS 42 PLEASE SIGN OFF
SS M333: HELLO
8600 0395-514 629

ST (Stop)
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
1024 OPERATOR STOPPED

You can use the OK (Reactivate) command to reactivate a task that you have
stopped with either an ST or a CANDE ?ST command. CANDE users can not
reactivate a task that is stopped by the operator with the ST command.
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.
630 8600 0395-514

STARTTIME (Start Time)

The STARTTIME (Start Time) command assigns a starting date and time to jobs in a
queue.
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

This command can be used whether or not the job already has a start time
associated with it. If the job reaches the front of the queue and its specified start
time is later than the current time, it stays at the head of the queue but is not
started. The CONTROLLER selects the first job in the queue whose start time is
earlier than or the same as the current time or that has no start time. That job is the
next job to be run from the queue. The changes made by this command to a job in a
queue are retained over a halt/load of the system.
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.
8600 0395-514 631

STORESAFE
STORESAFE
The STORESAFE command is used to configure and monitor the StoreSafe feature.
Syntax
<disk site name>
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.
STORESAFE - PK <number> FORCE

This command forces the removal of the disk site name from PK <number>. After
executing the command, if the mirrored set to which PK <number> belongs has
other members at the same disk site name, but none of them are accessible, the
remaining members are marked as being overridden.
STORESAFE REMOVE <disk site name> FROM PK <number>

The REMOVE variant is used to eliminate the requirement that members must be
present at a disk site name in a situation where none of the members at that disk
site name are online to the system. For example, consider a mirrored set consisting
of PK 100 and PK 200, with PK 100 having the disk site name PRIMARYSITE and PK
200 having the disk site name BACKUPSITE. If PK 200 is decommitted out of the set
due to an irrecoverable I/O error, all that remains is PK 100, un-mirrored, at
PRIMARYSITE, and it is in a StoreSafe alert. If the site administrator wishes to
remove the requirement that there be a mirror of PK 100 at BACKUPSITE, it is not
possible to do so with the STORESAFE - PK 200 command, since PK 200 is no longer
632 8600 0395-514

STORESAFE
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 REMOVE <disk site name>

This form of the REMOVE variant is used to eliminate the requirement that members
be present at the specified disk site name for all StoreSafe volumes currently on the
system. An operator acknowledgement is needed to ensure that the FROM PK xxx
part of the command was not inadvertently omitted.
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.
STORESAFE + OVERRIDE SITENAME <disk site name>

This command provides a way to globally override any existing StoreSafe alerts for
the specified disk site name and to prevent future such alerts from occurring. If a
volume is in a StoreSafe alert because it does not have an online member at the
specified disk site name, overriding the alert causes I/O activity to the volume to
resume without the MCP maintaining in-sync members at that disk site name.
STORESAFE OVERRIDE SITENAME <disk site name>

This command provides a way to discontinue a global site name override request.
This enables future StoreSafe alerts to take place as the result of the loss of the last
member at the specified disk site name.
Note: Out-of-sync volumes are unaffected by this command. Simply discontinuing a

global override does not cause a volume to be in-sync.
8600 0395-514 633

STORESAFE
Examples
Example 1
The following message displays after installing the STORESAFE feature, but before
using it:
STORESAFE ALERTS NOT BEING ENFORCED

OVERRIDDEN SITES ARE: (NONE)
NO STORESAFE DISKS FOUND
System-wide enforcement of STORESAFE alerts is not in effect because the operator

has not entered a STORESAFE+ENFORCE command. There are no STORESAFE
named disks on the system.
Example 2
STORESAFE ALERTS BEING ENFORCED
PK STATUS FAMILY MEMBER SITE NAME STORESAFE STATUS
200B M DISK # 1 MV +RUNNING
100B M DISK # 1 TR +RUNNING
System-wide enforcement of STORESAFE alerts is in effect.
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
200B M DISK # 1 MV -RUNNING
100B M DISK # 1 TR -RUNNING
System-wide enforcement of STORESAFE alerts is not in effect because the operator

has not entered a STORESAFE+ENFORCE command.
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
200B M DISK # 1 MV +ALERT(AUDITING)
100B M DISK # 1 TR +SUSPENDED
System-wide enforcement of STORESAFE alerts is in effect. 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
634 8600 0395-514

STORESAFE
name MV. The volume is in a STORESAFE alert because PK 200 was decommitted to
auditing.
Example 5
OVERRIDDEN SITES ARE: MV
200B M DISK # 1 MV(O) +OVERRIDDEN(AUDITING)

mirrored set with PK 100 located at disk site name TR and PK 200 located at disk
site name MV.
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
B DISK # 1 MV +ALERT(MISSING)
100B DISK # 1 TR +SUSPENDED

name MV. The volume is in a STORESAFE alert because PK 200 was decommitted out
of the set.
Example 7
300B M DISK # 1 MV +ALERT(PENDING)

name MV.
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.
8600 0395-514 635

STORESAFE

300B M DISK # 1 MV -OVERRIDDEN(PENDING)
Example 9
200B M DISK # 1 MV +SUSPENDED(AUDITING)
System-wide enforcement of STORESAFE alerts is in effect. PK 100, PK 200, and PK

300 are a mirrored set with PK 100 located at disk site name TR and PK 200 and 300
located at disk site name MV.
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.

200B M DISK # 1 MV +OVERRIDDEN(AUDITING)
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.
636 8600 0395-514

STORESAFE

200B M DISK # 1 MV -OVERRIDDEN(AUDITING)
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.

100B M DISK # 1 TR -OVERRIDDEN(AUDITING)
Example 15
200B M DISK # 1 MV +SUSPENDED(AUDITING)
B M DISK # 1 RS +ALERT(MISSING)
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.
8600 0395-514 637

STORESAFE
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

name MV. The mirrored set is a critical family.
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
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.

B M DISK # 1 TR +ALERT(MISSING)
200B M DISK # 1 +SUSPENDED(AUDITING)
638 8600 0395-514

STORESAFE
Example 20
Following is an example of a display that includes multiple families, with multiple
family members and different volume compositions.

200B M DISK # 1 RS +RUNNING
101C M DISK # 2 +RUNNING
201C M DISK # 2 MV +RUNNING
301C M DISK # 2 TR +RUNNING
102C M DISK # 3 MV +RUNNING
202C M DISK # 3 RS +RUNNING
303B PMDB # 1 TR +RUNNING

104C M PMDB # 2 MV +RUNNING
204C M PMDB # 2 RS +RUNNING
304C M PMDB # 2 TR +RUNNING
105B M ZETA # 1 MV +SUSPENDED

205B M ZETA # 1 RS +SUSPENDED
305B M ZETA # 1 TR +ALERT(AUDITING)
8600 0395-514 639

STRUCTURECACHE (Cache Maintenance)

The STRUCTURECACHE command is used to set and display values for caches
maintained by the system for a number of data structures.
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.
STRUCTURECACHE DIRECTORY <integer>

Sets the size of the disk directory cache. This cache holds blocks of the data
structure used by the system to locate disk files according to title. A value of zero (0)
disables this cache. The default value is 100 blocks, and the maximum value is 4095
blocks.
STRUCTURECACHE HEADERS <integer>

Sets the size of the disk file header cache. This cache retains the disk file headers of
files that have been recently used but that are currently not in use. A value of zero
(0) disables this cache. The default value is 30 headers, and the maximum value is
1000 headers.
STRUCTURECACHE CODESTACKS <integer>,<integer>

Sets values for the code stack cache. This cache retains a number of code stacks
that have been recently used but that are currently not in use. The first parameter
specifies the size of the cache, and the second parameter specifies the time limit for
the cache to retain a code stack. Setting either value to zero (0) disables the cache.
The size default value is 15 stacks, and the time default value is 60 seconds. The
maximum size is 100 stacks, and the maximum time limit is 100,000,000 seconds.
Note: You can use the RP (Resident Program) command to retain code stacks with
no users.
STRUCTURECACHE USERDATAFILE <integer>

Sets the size of the SYSTEM/USERDATAFILE cache. This cache contains entries of the
data structure used by the system to record usercodes and their associated
attributes. Setting the value to zero (0) disables the cache. The default value is 200
entries, and the maximum value is 4095 entries.
640 8600 0395-514

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:
STRUCTURECACHE CODESTACKS 20,60
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
Disk Directory Cache

Size = 120 blocks (28800 words in use)
current rate (per sec) since last H/L
reads hits/reads 1.25/3.12 = 40% 5678/12003 = 47%
reads hits/reads+writes 1.25/6.23 = 20% 5678/18349 = 31%
reads/reads+writes 3.12/6.23 = 50% 12003/18349 = 65%
Disk File Header Cache

Size = 30 headers (3570 words in use)
already open/requests 0.82/1.70 = 48% 256/1364 = 19%
cache hits/requests 0.46/1.70 = 27% 667/1364 = 49%
misses/requests 0.42/1.70 = 25% 441/1364 = 32%
Code Stack Cache

Size = 15 stacks (35164 words in use)
Time Limit = 30 seconds
already running requests 0.20/0.82 = 24% 100/759 = 13%
cache hits/requests 0.32/0.82 = 39% 231/759 = 30%
misses/requests 0/30/0.82 = 37% 428/759 = 56%
SYSTEM/USERDATAFILE Cache
Size = 200 entries (18000 words in use)
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%
8600 0395-514 641

SUPPRESS (Suppress Display)

The SUPPRESS (Suppress Display) command prevents jobs or tasks from appearing
in a mix display while they are active. The command can also end the suppression of
job or task displays.
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.
If an active suppressed job or task goes to a waiting state, it is displayed. When it

returns to an active state, it is suppressed again.
The suppressed status is not preserved over a halt/load.
<mix number list> SUPPRESS

Ends the suppression of display for the jobs or tasks in the mix number list.
642 8600 0395-514

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.
---Mix-Pri-CPU Time-------- 14 ACTIVE ENTRIES -----------------------

7019 80 :15 Job *SYSTEM/CANDE ON DISK
7020 80 :07 *CANDE/STACK01
6761 80 :41 *SYSTEM/COMS ON DISK
6765 50 :04 MARC
6759 80 :00 COMS/TANK
6758 80 :00 COMS/INPUT
6765 SUPPRESS
---Mix-Pri-CPU Time------- 14 ACTIVE ENTRIES ------------------------

7019 80 :15 Job *SYSTEM/CANDE ON DISK
7020 80 :07 *CANDE/STACK01
6761 80 :41 *SYSTEM/COMS ON DISK
6759 80 :00 COMS/TANK
6758 80 :00 COMS/INPUT
8600 0395-514 643

SUPPRESSWARNING (Suppress Warning)

The SUPPRESSWARNING command displays or modifies the list of warning messages
to be suppressed. If the value associated with a message is contained in the
suppression list, the text of that message is not displayed on the ODT or, in the case
of an interactive task, on the remote terminal. For detailed information about
warning numbers and messages, refer to the System Messages Manual. Message
suppression applies to all tasks.
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.
644 8600 0395-514

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

Warning suppression does not directly affect the creation of entries in the system log
file or a job summary file. However, any logging that would otherwise take place as a
result of warning message display is bypassed.
The warning suppression list is preserved across a halt/load.
To suppress warnings for an individual task, use the SUPPRESSWARNING task

attribute. This attribute is described in the Task Attributes Programming Reference
Manual.
8600 0395-514 645

SV (Save)
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.
646 8600 0395-514

SV (Save)
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.
SV IOP <number> : INHIBIT

Same as SV IOP except that the IOP is marked as INHIBITED in the PCD. Use
SAVE :INHIBIT if an IOP system is suspected to be bad so that attempts to READY
the IOP system requires a response to a warning RSVP.
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
8600 0395-514 647

SV (Save)
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
PK 160 WILL BE SAVED
PER PK
-------------------------PK STATUS--------------------------------
160*B [000851] (TO BE SAVED)

Saving a Pack
For pack devices, saving the unit prevents any new areas from being created on that
unit, but does not prevent existing areas from being read from and written to.
Saving the pack does not prevent the unit from being the object of LB (Relabel Pack
or Host Control Unit), PG (Purge), RC (Reconfigure Disk), or MIRROR CREATE
commands. Saving the base pack of a pack family makes the family inaccessible for
file open actions and directory inquiriessuch as the PD (Print Directory) command.
Saving a continuation pack of a pack family does not have this effect. Saving a
critical pack causes the pack to be saved after a halt/load.
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.
648 8600 0395-514

SW (Switches)
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.
<mix number> SW <switch number> = TRUE

<mix number> SW <switch number> = FALSE
Changes the Boolean value of the designated switch.
8600 0395-514 649

SW (Switches)
Examples
Example 1
This example interrogates the value of the switches for task 4857.
4857 SW
SWITCH VALUES FOR 4857:
SW 1 = FALSE (NOT VALID)

SW 2 = TRUE
SW 3 = FALSE
SW 4 = TRUE
SW 5 = FALSE
SW 7 = TRUE
SW 8 = FALSE
Example 2
This example changes the value of switch 6 to TRUE for task 4857.
4857 SW 6 = TRUE
SWITCH VALUES FOR 4857:

SW 2 = TRUE
SW 3 = FALSE
SW 4 = TRUE
SW 5 = FALSE
SW 6 = TRUE
SW 7 = TRUE
SW 8 = FALSE

The SW (Switches) system command shows the validity of each switch. Each switch
has a validity bit associated with it, indicating if the value of a switch has been
explicitly set. A switch that is not indicated as valid will return the value FALSE.
Each switch setting is reported as one of the following:
FALSE (NOT VALID)
FALSE
TRUE
650 8600 0395-514

SYSADMIN COMMAND
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.
A system administrator is a user with the usercode attribute SYSADMIN set.
Commands related to the mix are not restricted
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.
SYSADMIN COMMAND <command>

Restricts the use of the specified command to a system administrator. You can
restrict the use of the following system commands.
ACCOUNTING DF MDT SBP
AD DL ML SEGARRAYSTART
AI DN MOVE SF
AR DQ MQ SHARE
ARCCOPY DR MP SI
ARCDUPLICATE FAMILYACCESS NET SQUASH
ARCREPLACE GC NETEX SS
8600 0395-514 651

SYSADMIN COMMAND
ACCOUNTING DF MDT SBP
ASD HLUNIT OP STRUCTURECACHE
BNA HOSTNAME PB SUPPRESSWARNING
BNAVERSION HS RB SYSOPS
CM ID RECONFIGURE TERM
GROUP
COMPILERTARGET IK RES TL
COPYCAT LC RP TR
CS MAX SB UQ
DD
The following commands are automatically restricted when security administrator

status is enabled. If security administrator status is enabled, a system administrator
cannot use them even if they are added to the list of SYSADMIN COMMAND
commands.
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
652 8600 0395-514

SYSADMIN COMMAND
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.
SYSADMIN COMMAND <command>

Removes any restrictions previously applied to the specified command.
Examples
Example 1
This example restricts the use of the MERGE option of the IK system command.
SYSADMIN COMMAND IK MERGE
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.
SYSADMIN COMMAND TL, SYSOPS LANGUAGE
8600 0395-514 653

SYSADMIN COMMAND
Example 4
After a security administrator issues the following two commands, both security
administrators and system administrators can use the SYSOPS system command.
RESTRICT COMMAND SYSOPS
SYSADMIN COMMAND SYSOPS
Example 5
After a security administrator issues the following command, the system
administrator can issue a SQUASH system command, but the security administrator
cannot.
SYSADMIN COMMAND SQUASH
Example 6
After a security administrator issues the following command sequence, only the
security administrator can issue a SQUASH system command.
SYSADMIN COMMAND - SQUASH
RESTRICT COMMAND SQUASH
Example 7
After a security administrator issues the following request, only the security
administrator can issue a TL system command.
RESTRICT COMMAND TL

Levels of Security Required to Use This Command
A system administrator is a user with the SYSADMIN usercode attribute.
If security administrator status is authorized on the system, restrictions on system

commands can be set only by someone who has a security administrator usercode.
If security administrator status is not authorized on the system, restrictions on

system commands can be set only by a system administrator. For information about
setting security administrator status, refer to the ??SECAD (Security Administrator
Authorization) primitive command.
654 8600 0395-514

SYSADMIN COMMAND
Sources for Entering Restricted Commands

You can enter restricted commands only from a source that has SYSADMIN user
status. Such sources include
A MARC session with a system administrator usercode

A program using SETSTATUS that is running under a system administrator
usercode
A program using DCKEYIN that is running under a system administrator
usercode
Precedence for Using SYSADMIN COMMAND and RESTRICT COMMAND

Commands
When security administrator status is authorized, the following rules apply:
Only a security administrator is permitted to use the SYSADMIN COMMAND to

add or delete restricted commands. This usage permits the security
administrator to determine which commands the system administrator
usercode can control. The system administrator cannot change the set of
commands that has been delegated by the security administrator.
The security administrator can give the system administrator exclusive rights
to a particular command and options, or he can retain the rights to that
particular command and option for himself.
If a security administrator delegates the control of a command to a system
administrator, the security administrator is not permitted to use that
command until it has been removed from the control of the system
administrator with the SYSADMIN COMMAND system command.
A security administrator can permit a command to be used by both a system
administrator and a security administrator. You can accomplish this by
naming the command using both the RESTRICT COMMAND and SYSADMIN
COMMAND, shown in Example 4.
A user who has both security administrator and system administrator
privileges is not subject to command restrictions.
Examples 4 through 7 illustrate the precedence for use when security administrator
status is authorized.
8600 0395-514 655

SYSOPS (System Options)

The SYSOPS (System Options) command is used to display or set various system
options.
Syntax
656 8600 0395-514

<system options A - H>
8600 0395-514 657

<system options L-W>
658 8600 0395-514

8600 0395-514 659

<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>
A number in the range of 0 to 31.
<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.
660 8600 0395-514

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.
8600 0395-514 661

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
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.
662 8600 0395-514

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.
The default value is DIRECTDLP.
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.
Note: The ENABLEPOSIX option is scheduled to be deimplemented in a future

release.
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 ESR = UNCONDITIONAL

Generates Electronic Service Requests (ESRs) when an ESR event occurs.
SYSOPS ESR = CONDITIONAL

Generates an RSVP waiting entry when an Electronic Service Request (ESR) event
occurs.
8600 0395-514 663

SYSOPS ESR = SUPPRESSED

Stops the system from generating Electronic Service Requests (ESRs).
SYSOPS HOSTCCS
Displays the current status of the HOSTCCS option.
SYSOPS HOSTCCS = <CCS Name>

Use this command to set the HOSTCCS option. The HOSTCCS option can be set only
when the next default value of CCSVERSION is ASERIESNATIVE. Setting this option
changes the value of the HOSTCCS from the default CCSVERSION to the designated
<CCS Name>.
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.
SYSOPS LABELFORMAT = ANSI69

SYSOPS LABELFORMAT = ANSI69DEFAULT
If you choose this option, the ANSI69 standard is used to format tape labels when
you create tapes. For information about the ANSI69 tape labels, refer to the I/O
Subsystem Programming Guide.
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.
664 8600 0395-514

SYSOPS LABELFORMAT = ANSI87

If you choose this option, the ANSI87 standard is used to format tape labels when
you create tapes. For information about the ANSI87 tape labels, refer to the I/O
Subsystem Programming Guide.
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
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.
Kind Density Default Blocksize
PK/DK N/A 5400 words
MT 6250/1250 2700 words
MT 38000 10800 words
MT 11000 10800 words
MT 9840 10800 words
MT FMTLT03 64800 words
SYSOPS LMBLOCKSIZE <blocksize>

Sets the default block size (in words) that library maintenance is to use for copying
to and from disk and copying to tape. The maximum valid value is 64800. The
system automatically rounds the specified number up to an integer multiple of 900
words, which is the record size used by library maintenance.
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.
8600 0395-514 665

Performance of disk-to-disk and disk-to-tape copy operations is greatly

improved.
Performance of tape-to-tape copy operations is greatly improved if the input
tape has the same block size as the LMBLOCKSIZE value.
For tape units, there are two special limits on the block size that library maintenance
can use. In general, the special tape limits only affect the use of block sizes greater
than 10800.
First, certain tape drives have a built-in maximum block size.
Maximum Library
Tape Drive Name Density Maintenance Blocksize
QIC1000 1250 or 10800

FMTQIC1000
HS8500(C) (8mm) 11000 40500
USR5073 (half-inch 38000 42300

cartridge)
ALP440/TAL408012 FMTDDS 10800

(rmm) FMTDDS2
FMTDDS3
FMTDDS4
OST5136, CTS5236, FMT36TRK 42300

CTS4890,ALP8436
ALP920 (AIT) FMTAIT 64800

FMTAIT2
CTS9840, CTS9840B, FMT9840 42300

CTS9840C, CTS9940B FMT9840C
FMT9940
DLT7000, DLT8000, FMTDLT20 64800

SDLT320 FMTDLT35
FMTDLT40
FMTDLT160
LTO Gen 2 FMTLTO 64800
LTO Gen 3 FMTLTO3 64800
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
666 8600 0395-514

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.
When LONGFILENAMES is reset, file names are limited to 12 identifiers and 17

characters per identifier. When LONGFILENAMES is set, users can create file names
with up to 20 identifiers. Identifiers can exceed 17 characters, but the total file name
cannot exceed 216 characters.
8600 0395-514 667

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.
The DATEOFFSET task attribute is described in the Task Attributes Programming

Reference Manual.
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.
668 8600 0395-514

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.
On current software, the duration of an LH firmware load action to an IOP or port

depends solely on the setting of a firmware state toggle (either PERMANENT or
TEMPORARY) in the PCD entry for the device. The peripheral configuration diagram
profile, or PCD, is part of the information is maintained by Server Control, which can
modify it when a partition is halted. PRESERVELH is specially handled during
migration from old to current software. Current software takes special note of
8600 0395-514 669

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.
The PRESERVELH option continues to be settable, to enable the return to software

that supports the old firmware management scheme. When support for ClearPath
MCP Release 9.0 terminates, PRESERVELH will be deimplemented as a SYSOPS
option.
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:
Flushes the entire AX queue for that task

Maintains from that point a queue depth of one
SYSOPS RCBP
SYSOPS RCBP <switch>
Display or set the value for the RCBP system option. When you set this option, the
system activates a checking feature to prevent accidental reconfiguration of base
packs in a multipack family. If an RC (Reconfigure Disk) command is entered for a
directory-capable base pack, the system displays system warning and RSVP
messages. An operator must reply OK to continue the reconfigure operation if
another base pack for the family can be used or if the continuation packs are also to
be reconfigured. A reply of DS aborts the RC command and retains the multipack
family environment.
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.
670 8600 0395-514

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.
The maximum size of a SYSTEMDIRECTORY is 600,000, 2,000,000, or 4,000,000

sectors, depending on the size of the AREAS of that SYSTEMDIRECTORY.
You can use the DU SYSTEMDIRECTORY ON <family name> system command to

monitor the size and usage of a SYSTEMDIRECTORY.
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.
8600 0395-514 671

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.
SYSOPS WARNFACTOR MINIMUM

If you choose this option, the recompilation warning message is issued for only code
files that require recompilation to run on system software released after the next
year (approximately 12 months). For example, for SSR 50.1, the MINIMUM setting
results in warning messages for code files that expire on or before SSR 51.1. Code
files that expire after that period do not receive the warning message on the SSR
50.1 level of software. Use this option if your site expects to upgrade to a new
software level (SSR) within the next year.
SYSOPS WARNFACTOR STANDARD

files that require recompilation to run on system software released after the next 2
years (approximately 24 months). For example, for SSR 50.1, the STANDARD setting
50.1 level of software. Use this option if the site has no plans to upgrade the
672 8600 0395-514

software within the near future, but does expect to upgrade before the end of the life
cycle of the current software level.
SYSOPS WARNFACTOR MAXIMUM

files that require recompilation to run on system software released after the next 3
years (approximately 36 months). For example, for SSR 50.1, the MAXIMUM setting
50.1 level of software. Use this option if the site prefers to wait until the current level
of software is no longer supported before upgrading to the newest software level
available at the time of the upgrade.
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:
SYSOPS CCSVERSION = USEBCDIC
----------------------------SYSTEM OPTIONS---------------------------
SYSTEM OPTION(S) are changed as follows:
The current CCSVERSION is ASERIESNATIVE ( 0 ).

The CCSVERSION following the next HALTLOAD will be USEBCDIC ( 1 ).
8600 0395-514 673

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:
SYSOPS TAPEMANAGER = SET
----------------------- SYSTEM OPTIONS ------------------------------
TAPEMANAGER is being SET
Example 4
Use the following example to indicate that the MCP is to ignore the expiration dates
on tapes when it reads tape labels:
SYSOPS TAPEEXPIRATION = FALSE
----------------------- SYSTEM OPTIONS ------------------------------
TAPEEXPIRATION will be set to FALSE
Example 5
SYSOPS QUEUEDAX TRUE
----------------------- SYSTEM OPTIONS --------------------------------
QUEUEDAX will be set to TRUE
674 8600 0395-514

Example 6
SYSOPS ESR UNCONDITIONAL
----------------------- SYSTEM OPTIONS --------------------------------
The ESR Software Logging Option is UNCONDITIONAL
8600 0395-514 675

TD (Time and Date)
TD (Time and Date)

The TD (Time and Date) command displays the time, day, date, and time zone being
used by the system.
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.
Clock correction information is displayed if the system is running with Time

Synchronization software. For more information, refer to the TCP/IP DSS Operations
Guide.
<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
The date is Thursday, June 6, 2005 (2005157)

Clock correction 0.067 seconds per day
676 8600 0395-514

TDIR (Tape Directory)

The TDIR (Tape Directory) command initiates the utility SYSTEM/FILEDATA to list the
names of the files contained on a library maintenance tape or library maintenance
format CD-ROM directory. To list the names of the files contained on a CD-ROM
formatted according to ISO 9660 standards, use the PD (Print Directory) command.
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.
TDIR <volume name> (CDROM)

TDIR SPO <volume name> (CDROM)
Display the directory of the CD-ROM that is loaded on the specified unit or the CD-
ROM with the specified volume name.
TDIR SPO <unit number>

TDIR SPO <volume name>
TDIR SCREEN <unit number>
TDIR SCREEN <volume name>
Display the directory of the specified tape on the originating ODT. Specify the SPO
option if the ODT is configured with a visible end-of-text (ETX) character. Specify the
SCREEN option if the ODT is not configured with a visible ETX character.
The system does not send the directory display to the originating ODT if one of the
following circumstances exists:
The ODT is attached or assigned to a program.

The ODT is labeled.
The ODT is saved.
The command was entered from a remote ODT.
8600 0395-514 677

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.
TDIR SPO DAILYLOGMPA15AB
UNISYS FILEDATA 51.150.0026 REPORT MPA15C CS185 #8 04/20/2005 15:40:55
TAPE = DAILYLOGMPA15AB/FILE000 (MT31) [807130], CREATED 04/12/20055

DLT 160 GB TAPE (Super DLT 320)
*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,
TAPE DIRECTORY INPUT = "TDIR SPO DAILYLOGMPA15AB"
678 8600 0395-514

Example 2
The following example shows a TDIR command for a CD-ROM named SYSTEM_49150
and the report that FILEDATA produces.
TDIR SYSTEM_49150 (CD)
UNISYS FILEDATA 49.189.8007 REPORT MP150 CS180 #2334 06/30/2004 11:44:11
TAPE DIRECTORY
CDROM = SYSTEM_49150 (CD50), CREATED 01/16/2003
1 *NX/WEBSTATION/CONTAINER ON SSR491,[KEY=491-JSN-JSN, VALID

2 *FIRMWARE/NSP/050/BDLC_LINE_CONTROL ON SSR491,[KEY=491-BLC-BLC, VALID]
3 *FIRMWARE/NSP/050/BSC_56KB_CONTROL ON SSR491,[KEY=491-BYC-BYC, VALID]
4 *FIRMWARE/NSP/050/SDLC_LINE_CONTROL ON SSR491,[KEY=491-SDL-SDL, VALID]
5 *FIRMWARE/NSP/050/EXECUTIVE ON SSR491,[KEY=491-DCDLPFIRMWARE-DCD, VALID]
7 *FIRMWARE/NSP/076/DP_LINE_CONTROL ON SSR491,[KEY=491-BYC-BYC, VALID]
8 *FIRMWARE/NSP/076/SDLC_LINE_CONTROL ON SSR491,[KEY=491-SDL-SDL, VALID]
10 *ASSISTANT/PARAMETERS/EXAMPLE ON SSR491,[KEY=491-OCA-OCA, VALID]
11 *BOOK/SIMPLEINSTALL/ENGLISH ON SSR491,
17 *INSTALLDATAFILE/SYSTEM/491 ON SSR491,
18 *OBJECT/NXSERVICES ON SSR491,[KEY=491-HMP-HMN, VALID]
19 *OBJECT/RSTRACE ON SSR491,[KEY=491-RSS-RSS, VALID]
20 *SYSTEM/ASSISTANT ON SSR491,[KEY=491-OCA-OCA, VALID]
21 *SYSTEM/CENTRALSUPPORT ON SSR491,
22 *SYSTEM/COMS ON SSR491,[KEY=491-COMS16-C01, VALID]
23 *SYSTEM/DELTA/LOADER ON SSR491,
24 *SYSTEM/DELTA/MCP ON SSR491,
25 *SYSTEM/DELTA/MCP/DIAGNOSTICS ON SSR491,
26 *SYSTEM/EPSILON/MCP ON SSR491,
27 *SYSTEM/EPSILON/MCP/DIAGNOSTICS ON SSR491,
.
.
.
1503 *WEBCOMPONENTS/"DOCS.ZIP" ON SSR491,[KEY=491-WEC-WEC, VALID]
1504 *WEBCOMPONENTS/LASTFILE ON SSR491,[KEY=491-WEC-WEC, VALID]
1505 *WEBCOMPONENTS/CONTAINER ON SSR491,[KEY=491-WEC-WEC, VALID]
1506 *WEBCOMPONENTS/"INDEX.HTM" ON SSR491,[KEY=491-WEC-WEC, VALID]
1507 *WEBCOMPONENTS/"VSSVER.SCC" ON SSR491,[KEY=491-WEC-WEC, VALID]
1508 *WEBCOMPONENTS/"WEBENBLCOMPS.GIF" ON SSR491,[KEY=491-WEC-WEC, VALID]
1509 *WEB/COMPONENTS/CONTAINER ON SSR491,[KEY=491-WEC-WEC, VALID]
TAPE DIRECTORY INPUT = "TPDIR SYSTEM_49150 (CD)"
8600 0395-514 679

TERM (Terminal)
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.
TERM CONVENTION <convention name>

TERM CONVENTION *
Specify the name of the convention to be used for formatting times and dates in
responses to system commands. The convention name must be a valid convention.
If you specify an asterisk (*), the system default convention is used.
TERM DCSTATION TRUE

TERM DCSTATION FALSE
TERM DCSTATION YES
TERM DCSTATION NO
Can be specified at any ODT whose firmware lets it function as a remote terminal
through COMS/ODT/DRIVER. This option should be set to TRUE if the ODT is
configured to suppress the visible end-of-text character (ETX) on output and to no
longer interpret a DC1 as a line erase. The option causes the NS (next screen)
prompt to appear at the upper left corner of the terminal instead of the lower right
corner. DCSTATION is not valid from remote ODTs.
The default value is FALSE. Unless this option is explicitly set, terminals are not
affected.
680 8600 0395-514

TERM (Terminal)
For more information about COMS/ODT/DRIVER, refer to ??MARC (Transfer to

Menu-Assisted Resource Control).
TERM FIRST <number>

Specifies the number of screen lines to be skipped at the beginning of the display.
The value of <number> must be less than the current value specified by TERM
LINES. The default value is 2. The system always displays responses to primitive
commands on the second line, regardless of the setting of FIRST.
TERM LANGUAGE <language name>

TERM LANG <language name>
Specify the name of the language in which responses are to be displayed at the
terminal. If <language name> is not an MCP-bound language, a warning is displayed
along with the names of the system-bound languages. The language is changed,
even if the new language is not an MCP-bound language (a language in which MCP
responses can be displayed).
TERM LINES <number>

Specifies the number of display lines on the ODT device. The value of <number>
must be greater than the current value specified by TERM FIRST. The default value is
24. The maximum value is 63.
TERM MESSAGES TRUE

TERM MESSAGES FALSE
TERM MESSAGES YES
TERM MESSAGES NO
TRUE specifies that messages coming from the system are to be displayed when they
are first received. These messages include REMOVED messages, OPERATOR DS (DS
command) messages, and RSVP messages. The messages appear on the line after
the number of lines specified in the TERM FIRST command.
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.
TERM RESPONSE NONE

TERM RESPONSE CONCISE
TERM RESPONSE EXPANDED
Specify the form of any system response to certain system commands. NONE
indicates that no system response is to be displayed. CONCISE indicates that the
system is to respond only with a display of OK. EXPANDED indicates that a full
system response command is to be displayed. The default value is EXPANDED.
TERM TRUNCATE TRUE

TERM TRUNCATE FALSE
TERM TRUNCATE YES
TERM TRUNCATE NO
Affects only messages specified in the MSG command. In ADM mode, messages are
always truncated.
8600 0395-514 681

TERM (Terminal)
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 = <valid usercode/password>

Associates the usercode with any of the following requests initiated at the ODT where
the command is entered:
System commands sent to a remote host with the AT <host name>

command
File transfers initiated with the WFL COPY statement
Job transfers initiated with the WFL START or ?AT <host name> statement
File inquiries initiated with the Print Directory (PD) command.
Note: You cannot use the ODT to enter restricted ODT commands when TERM USER
is set as a security administrator user code.
TERM USER
Dissociates a usercode from that ODT.
TERM WIDTH <number>

Specifies the physical width, in characters, of the ODT device. The default value is
80. The maximum value is 132.
Examples
Example 1
This example shows a normal response from a TERM inquiry.
TERM
TERM LINES 24 WIDTH 80 FIRST 2 LANGUAGE ENGLISH

CONVENTION *(ASERIESNATIVE) TRUNCATE TRUE RESPONSE EXPANDED
MESSAGES FALSE
Example 2
This example changes the language in which responses are to be displayed at the
terminal to French.
TERM LANG FRANCAIS
LANGUAGE CHANGED FROM ENGLISH TO FRANCAIS
682 8600 0395-514

TERM (Terminal)
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.
TERM LANGUAGE HINDI
LANGUAGE CHANGED FROM FRANCAIS TO HINDI

WARNING : HINDI IS NOT AN MCP BOUND LANGUAGE
The MCP bound languages: ENGLISH FRANCAIS
8600 0395-514 683

THAW (Thaw Frozen Library)

The THAW (Thaw Frozen Library) command changes the state of permanently frozen
libraries and freeze-control libraries.
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
684 8600 0395-514

TI (Times)
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.
The information is returned in units of hours, minutes, and seconds.
Example
5285 TI
TIMES FOR 5285
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
For an explanation of INITPBIT and OTHERPBIT, refer to U (Utilization).
8600 0395-514 685

TL (Transfer Log)
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:
The number of rows (which corresponds to the AREAS file attribute)

The number of records per row (which corresponds to the AREASIZE file
attribute)
The maximum recommended size for a log record
The maximum supported size for a log record
686 8600 0395-514

TL (Transfer Log)
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
10207 10:51 PK353 *SYSTEM/SUMLOG CHANGED TO

*SUMLOG/227/030204/000011 ON DISK
10207 10:51 PK353 *SYSTEM/SECURITYLOG CHANGED TO
*SECURITYLOG/227/030204/000011 ON DISK
Example 2
This example displays the values space allocation factors of the current SUMLOG and
SECURITYLOG files:
TL *
SUMLOG and SECURITYLOG Factors are as follows:

Rows : 100
Records per row : 1,000
Maximum recommended record size : 29,001 words
Maximum supported record size : 1,048,554 words
8600 0395-514 687

TL (Transfer Log)
Example 3
This example releases the current SUMLOG and SECURITYLOG files and creates new
ones with 650 rows and 7000 records per row:
TL ROWS 650 RECORDS 7000
SUMLOG and SECURITYLOG Factors are as follows:

Rows : 650
Records per row : 7,000
Maximum recommended record size : 203,001 words
Maximum supported record size : 1,048,554 words
10252 10:55 PK353 *SYSTEM/SUMLOG CHANGED TO

*SUMLOG/227/030204/000012 ON DISK
10252 10:55 PK353 *SYSTEM/SECURITYLOG CHANGED TO
*SECURITYLOG/227/030204/000012 ON DISK
688 8600 0395-514

TR (Time Reset)
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.
If neither AM nor PM is specified, the time is assumed to be on the 24-hour clock. AM

indicates a time equal to or after midnight but before noon. PM indicates a time
equal to or after noon but before midnight.
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>
8600 0395-514 689

TR (Time Reset)
<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>
690 8600 0395-514

TR (Time Reset)
<predefined time zone>
8600 0395-514 691

TR (Time Reset)
<predefined time zone> (cont.)
<custom 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.
692 8600 0395-514

TR (Time Reset)
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.
Standard Time Predefined Time Zone

Zone
UT - 11:30
UT - 11:00
UT - 10:30
UT - 10:00 Hawaii-Aleutian Standard (HST)
UT - 9:30
UT - 9:00 Hawaii-Aleutian Daylight (HDT), Alaska Standard (AKST)
UT - 8:30
UT - 8:00 Alaskan Daylight (AKDT), Pacific Standard (PST)
UT - 7:30
UT - 7:00 Pacific Daylight (PDT), Mountain Standard (MST)
UT - 6:30
8600 0395-514 693

TR (Time Reset)

Zone
UT - 6:00 Mountain Daylight (MDT), Central Standard (CST)
UT - 5:30
UT - 5:00 Central Daylight (CDT), Eastern Standard (EST)
UT - 4:30
UT - 4:00 Eastern Daylight (EDT), Atlantic Standard (AST)
UT - 3:30 Newfoundland Standard (NST)
UT - 3:00 Atlantic Daylight (ADT), Greenland Standard (GST)
UT - 2:30 Newfoundland Daylight (NDT)
UT - 2:00 Greenland Daylight (GDT)
UT - 1:30
UT - 1:00
UT - 0:30
UT + 0:00 Greenwich Mean (GMT)
UT + 0:30
UT + 1:00 British Summer (BST), Central European Standard

(CEST)
UT + 1:30
UT + 2:00 Central European Daylight (CEDT), Eastern European

Standard (EEST)
UT + 2:30
UT + 3:00 Eastern European Daylight (EEDT)
UT + 3:30
UT + 4:00
UT + 4:30
UT + 5:00
UT + 5:30 Indian Standard (IST)
694 8600 0395-514

TR (Time Reset)

Zone
UT + 5:45
UT + 6:00
UT + 6:30
UT + 6:45
UT + 7:00
UT + 7:00
UT + 7:30
UT + 8:00 Hong Kong Standard (HKST), Chinese Standard (CHST),

Western Australian Standard (WAST)
UT + 8:30
UT + 9:00 Western Australian Daylight (WADT), Japanese Standard

(JST)
UT + 9:30 Central Australian Standard (CAST)
UT + 10:00 Eastern Australian Standard (EAST)
UT + 10:30 Central Australian Daylight (CADT)
UT + 11:00 Eastern Australian Daylight (EADT)
UT + 11:30
UT + 12:00 New Zealand Standard Time (NZST)
UT + 12:30
UT + 12:45
UT + 13:00 New Zealand Daylight Time (NZDT)
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.
8600 0395-514 695

TR (Time Reset)
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).
TR <number> <day of week> <month> <day of month> <year>

TR <number>:<number> <day of week> <month> <day of month> <year>
TR <number>:<number>:<number> <day of week> <month> <day of
month><year>
Change the system date and time. The new date is 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>.
Relative Time Change

Change the system time of day by a relative amount of time by placing a plus sign
(+) or a minus sign (-) before the amount of time to added or subtracted from the
current time.
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.
TR TIMEZONE <predefined time zone>

Uses a predefined time zone as the system time zone.
TR TIMEZONE <universal time zone>

Uses an offset of UT+0:00 (Greenwich Mean Time) to define the system time zone.
The valid universal time zone offsets are specified in the table under <universal time
zone> as standard time zones. You should use this syntax instead of the custom
time zone syntax whenever possible. The system stores system time and date
information for disk files based on time zone numbers, which are available only for
standard (universal) time zones.
696 8600 0395-514

TR (Time Reset)
TR TIMEZONE + <hour>:<minutes> <custom time zone name>(<abbr>)

TR TIMEZONE <hour>:<minutes> <custom time zone name> (<abbr>)
Specifies a local time zone. The system uses the specified hours and minutes
whenever it converts local time to universal time.
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
TIME CHANGE REQUEST--OK OR DS MAY BE REQUIRED--SEE WAITING ENTRIES
The Waiting Entries display shows the following information:
---MIX-PRI-ELAPSED------------ 1 WAITING ENTRY -------------------------

2345 80 :06 JOB CHANGETIME
VERIFY 1 HOUR 10 MINUTES 42 SECONDS FORWARD
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
The date is Wednesday February 2, 2005 (2005033)

The time is 07:15:30 Pacific Standard Time (PST)
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.
TR 00:15 FRIDAY SEPTEMBER 10, 2004
8600 0395-514 697

TR (Time Reset)
This is a backward change, so you must confirm the request:
---MIX-PRI-ELAPSED------------ 1 WAITING ENTRY -----------------------

CLOCK BEING SET BACKWARDS--CAN CAUSE LOG/AUDIT PROBLEMS--OK OR DS
3456 OK
Because the change involves more than 15 minutes' difference, the system creates
another waiting entry:
---MIX-PRI-ELAPSED------------ 1 WAITING ENTRY ----------------------

VERIFY 6 HOURS 55 MINUTES 14 SECONDS BACKWARD 1 DAYS BACKWARD
The operator confirms the request and uses the TD (Time and Date) command to
display the new time and date:
3456 OK
TD
The date is Friday September 10, 2004 (2004253)

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
---MIX-PRI-ELAPSED----------- NO WAITING ENTRIES --------------------
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
The date is Wednesday February 2, 2005 (2005033)

The time is 12:33:04 Pacific Standard Time (PST)
698 8600 0395-514

TR (Time Reset)
Example 4
In this example, the operator sets the local time zone used by the system to Pacific
Daylight Time.
TR TIMEZONE PDT
TIME ZONE CHANGE REQUEST--OK OR DS MAY BE REQUIRED--SEE WAITING ENTRIES
---MIX-PRI-ELAPSED------------ NO WAITING ENTRIES ----------------------
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
The date is Sunday June 6, 2004 (2004157)


Changing the Time Forward
A forward time change of fewer than 15 minutes is made immediately.
A forward time change of more than 15 minutes results in a waiting entry with the
following form:
VERIFY 1 HOURS 10 MINUTES 42 SECONDS FORWARD.
You must either confirm the request by entering an OK (Reactivate) command or

cancel it with a DS (Discontinue) command.
Changing the Time Backward

Any request for a backward time change results in the following waiting message:
CLOCK BEING SET BACKWARDS--CAN CAUSE LOG/AUDIT PROBLEMS--OK OR DS.
You must cancel the request by entering a DS (Discontinue) command or confirm it

with an OK (Reactivate) command.
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:
VERIFY 1 HOURS 10 MINUTES 42 SECONDS BACKWARD.
You must enter an OK (Reactivate) or a DS (Discontinue) command.
8600 0395-514 699

TR (Time Reset)
Setting the Time Zone

The TIMEZONE option enables you to display the current time zone, specify an
already defined time zone as the system time zone, or adjust the time zone for local
conditions. Setting, removing, or changing the time zone does not affect the system
time of day.
Synchronizing MCP and Windows Time on a Server

To synchronize the time on a server, you must separately update the time in the
MCP environment and in the Windows environment.
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.
700 8600 0395-514

TV (Type Volume)
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
-----VOLUME DIRECTORY ENTRY FOR (MT) [001002]-----

FAMILY NAME: TEST
FAMILY OWNER: *
TASK THAT WROTE TAPE STARTED ON: Tuesday December 17 (2002147) AT 12:23:33
FAMILY CREATION DATE: Tuesday, December 17, 2002
FAMILY EXPIRATION DATE: Thursday, January 16, 2003
LABELKIND: A SERIES LIBRARY MAINTENANCE
UPDATE TIMESTAMP: Tuesday, December 17, 2002 (2002152) AT 11:19:38
SECURITY: PUBLIC -- USAGE: READ/WRITE
GUARDFILE: NONE
FAMILY STRUCTURE #1 -- 0004
(MT) [001551] 36TRK #0001, DESTROYED, ONSITE
(MT) [001002] 36TRK #0002, TEMPORARY, RESTRICTED, ONSITE
(MT) [MT0923] 36TRK #0003, PERMANENT, NON-RESTRICTED, ONSITE
(MT) [MT11C4] 36TRK #0004, PERMANENT, RESTRICTED, DESTROYED, ONSITE
8600 0395-514 701

TV (Type Volume)
Example 2
TV MT MYTAPE
-----VOLUME DIRECTORY ENTRY FOR (MT) [MYTAPE]-----

FAMILY NAME: TEST2
FAMILY OWNER: USER
TASK THAT WROTE TAPE STARTED ON: Monday December 13 (2004147) AT 9:15:45
FAMILY CREATION DATE: Monday, December 13, 2004
FAMILY EXPIRATION DATE: Monday, February 14, 2005
LABELKIND: A SERIES LIBRARY MAINTENANCE
UPDATE TIMESTAMP: Monday December 13 (2004147) AT 10:20:30
MATCHONLYSERIALNO
SECURITY: PUBLIC -- USAGE: READ/WRITE
GUARDFILE: NONE
FAMILY STRUCTURE #1 ONLY
(MT) [MYTAPE] DDS2 #0001, TEMPORARY, RESTRICTED, ONSITE
702 8600 0395-514

U (Utilization)
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.
8600 0395-514 703

U (Utilization)
Examples
Example 1
The following example shows the response to the basic U command:
-------------------------- SYSTEM UTILIZATION -------------------------------
------ Standard IP Statistics ------- ----------- IO Statistics ------------

User = 25 % Initial Pbit = 4 % User = 186 IO/Sec ( 4,475 KB/Sec)
IO Finish = 1 % Other Pbit = 0 % MCP = 57 IO/Sec ( 199 KB/Sec)
MCP = 2 % True Idle = 68 % DC = 951 IO/Sec ( 249 KB/Sec)
Search = 0 % False Idle = 0 % Total = 1,194 IO/Sec ( 4,924 KB/Sec)
4,079 Process-switches/sec 1,239 IO Interrupts/Sec
Ips: 6 Standard, 2 Special Purpose
------------ Disk Cache ------------ ------------ Memory Disk -------------

Total = 291 Rq/Sec ( 4,505 KB/Sec) User = 0 IO/Sec ( 0 KB/Sec)
Readhits/Requests = 25 % MCP = 0 IO/Sec ( 0 KB/Sec)
Total = 0 IO/Sec ( 0 KB/Sec)
Example 2
The following example shows the response to the U ALL command:
U ALL
----- Standard IP Statistics --------

User = 45 % Initial Pbit = 4 %
IO Finish = 1 % Other Pbit = 0 %
MCP = 2 % True Idle = 50 %
Search = 0 % False Idle = 0 %
2,491 Process-switches/sec Ips = 6
--------Java IP Statistics ---------

273 Process-switches/sec Ips = 2
704 8600 0395-514

U (Utilization)
Example 3
The following example shows the response to the U ALL command for a system that
supports custom processor sets:
U ALL
----- STD:0 IP Statistics --------

2,491 Process-switches/sec Ips = 6
---- STD:1 IP Statistics ----

273 Process-switches/sec Ips = 2

Processing Utilization
The processing utilization time is divided into eight components, each described as a
percentage of the last time interval. The time interval can vary, and is set with the
SBP (System Balancing Parameters) command.
On systems that support multiple processor sets, the processing utilization

percentages reflect only that time that can be attributed to processors running in the
standard processor set. Use the ALL option to report processing utilization for all
active processor sets.
The percentage for a component is calculated by dividing the processor time

accumulated during the interval for that component by the summation of the
processor times accumulated for all the components during the interval. Reduce
capacity is not one of the components in this calculation.
User The percentage of processor time spent in user stacks,

excluding time charged to other accounts such as IOFINISH
or INITIALPBIT. User stacks include user programs, job
stacks, and library maintenance. Other independent runners
are not included.
I/O Finish The percentage of processor time spent handling I/O

completion.
8600 0395-514 705

U (Utilization)
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.
MCP The percentage of processor time charged to the combination

of the following accounts:
MCPSTACK
Processor time spent in MCP stacks, not including time
spent performing other tasks in this list. MCP stacks are
all MCP-independent runners, such as NSP stacks and
CONTROLLER. Library maintenance stacks are not
included.
PROCESSSWITCH
Processor time spent switching between stacks, processor
time required to select a new stack from the READY queue
and extract it, and processor time required to insert the
old stack into the READY queue. Several system-wide
functions performed regularly, such as checking for
suspended I/O operations, are also included. This time is
not charged to any stack.
LISTEN
Processor time spent during an interrupt by another
processor for a reason other than overlay searching.
706 8600 0395-514

U (Utilization)
Search The percentage of processor time charged to the combination

of the following accounts:
SEARCHLEAD
All processor time spent searching stacks throughout the
overlay process. It includes the time needed to
synchronize with any other processor running stacks with
visibility to the data or code being overlaid. SEARCHLEAD
also includes search time incurred by the overlay
algorithms, which are controlled by factor 1. For more
information about overlay algorithms, refer to the SF (Set
Factor) system command.
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.
Process- The number of process switches that occur per second. A

switches/sec process switch occurs when a processor stops executing a
particular process and begins executing a different process.
On a multiprocessor system, this value is the sum of all
process switches performed on all the processors per second.
8600 0395-514 707

U (Utilization)
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.
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.
Disk Cache Utilization

The following disk cache utilization statistics are reported if the system is using disk
cache:
The number of requests presented per second to disk cache

The effective data rate represented by these requests
The percentage of these requests that are read hits
For more information on disk cache utilization, refer to the Disk Cache Module
Installation and Operating Guide.
708 8600 0395-514

UL (Unlabeled)
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:
The device type mnemonic must be either MT or SC.

If a labeled file is assigned to a task in this way, all records of the file,
including the label, are read as data.
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
8600 0395-514 709

UP (Up Resource)
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.
Many forms of the UP command cause a brief system pause.
Note: UP is a synonym for ACQUIRE. Use UP on IOP systems. Use ACQUIRE on IOM
systems.
Syntax
<CTL specification>
<resource> (Libra Model 185, 580, 585, 590, 595 systems)
<resource> (Libra Model 680, 690 systems)
Note: For Libra Model systems, you can separate the variables with either hyphens (-) or
underscores (_).
<pod>
710 8600 0395-514

UP (Up Resource)
<subpod>
<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.
<cell>
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.
CTL or PORT failures. You might need to perform the following steps to recover CTLs
that are involved in such failures:

2. Enter DOWN CTL <CTL number list>.
3. Enter UP CTL <CTL number list>.
UP CTL <CTL number list> :TEMPORARY
UP CTL <CTL number list> :TEMP
Acquires the CTLs identified by the CTL number list until the next halt/load of the
system. If group reconfiguration does not occur when the system is halt/loaded, the
CTL reverts to a logically unowned status as a freed device of its partition.
UP <device type> <unit number list>

Acquires the unit or units identified by the device and unit number list. The system
automatically readies the units unless you use the SAVE option.
8600 0395-514 711

UP (Up Resource)
UP <device type> <unit number list> :SAVE

UP <device type> <unit number list> :SV
Acquires the units in the saved state; that is, the units are acquired and saved in one
step.
UP <device type> <unit number list> :TEMPORARY

UP <device type> <unit number list> :TEMP
Acquires the designated units until the next halt/load of the system. If group
reconfiguration does not occur when the system is halt/loaded, each unit reverts to a
logically unowned status as a freed device of its partition.
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,
712 8600 0395-514

UP (Up Resource)
IONODE_<cell> cannot be acquired in a partition if PROCNODE_<cell> 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 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.
8600 0395-514 713

UP (Up Resource)
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
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
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
714 8600 0395-514

UQ (Unit Queue)
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.
UQ <device type> <unit number list> <number>

Assigns jobs from the input devices in the unit number list to the job queue specified
by <number>.
UQ <device type> <unit number list>

Displays the current or default queue assignments for jobs from the input devices in
the unit number list.
UQ <device type> <unit number list>

Disables the default queue assignments for jobs from the input devices in the unit
number list. Jobs currently in the previously specified queue may be reinserted into a
different queue as a side effect of this or future system commands as the queue
assignment no longer applies. Refer to MQ (Make or Modify Queue).
8600 0395-514 715

UQ (Unit Queue)
Examples
Example 1
This example shows a query and response about unit queue assignments.
UQ
NO UNIT QUEUE ASSIGNMENTS
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
716 8600 0395-514

UR (Unit Reserved)
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.


THIS UNIT.
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.
8600 0395-514 717

UR (Unit Reserved)
UR <device type> <unit number list>

UR <device type> <unit number list> MAINT
Restore the units identified by the device type and the unit number list to the
system. For pack and memory disk units, the system performs an implicit RY
(Ready) command on the unit after it becomes available. If you specify MAINT, the
system disables maintenance access to the device. MAINT is valid only for packs.
UR CTL <CTL number>

UR CTL <CTL number> MAINT
Stop issuing operations through the specified control. If there are dependent devices
that are served only by the specified control, they are marked no path. If you specify
MAINT, the system also enables maintenance access to the control.
UR CTL <CTL number>

UR CTL <CTL number> MAINT
Cause the executing partition to resume operations through the specified control. If
the DLP has been reserved for maintenance, the system also sets the maintenance
mask, which disables maintenance access to the control.
UR PORT <port number>

Makes the port unavailable as a path for I/O operations.
UR PORT <port number>

Causes the system to resume I/O operations through the specified port.
UR DTU <DTU number>

Makes the data transfer unit (DTU) unavailable as a path for cached I/Os. If the
specified DTU is the last one, caching is suspended.
UR DTU <DTU number>

Makes the DTU available. If the specified DTU is the only one available to the
partition, caching can resume.
UR IOU <IOU number>

Takes an active IOU out of service. Use this version of the command if only one IOM
is available on the system.
UR IOM <IOM number> IOU <IOU number>

Takes an active IOU out of service. The variable <IOM number> identifies the
requestor number of the IOM that contains the IOU to be reserved.
UR IOU <IOU number>

Restores an IOU into service if it is currently out of service either because it is
reserved or because it failed a previous recovery attempt. Use this form of the
command if only one IOM is active on the system.
718 8600 0395-514

UR (Unit Reserved)
UR IOM <IOM number> IOU <IOU number>

Restores an IOU into service if it is currently out of service either because it is
reserved or because it failed a previous recovery attempt. The variable <IOM
number> identifies the requestor number of the IOM that contains the IOU to be
reserved.
Examples
Example 1
This example makes the designated port an unavailable path for I/O operations:
UR PORT 1002
PORT 1002 WILL BE RESERVED
Example 2
This example causes the system to resume I/O operations for the designated port:
UR - PORT 1000
PORT 1000 WILL BE AVAILABLE
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
IOM 1 IOU 1 RESERVED.
Example 6
This example shows an attempt to take a distinguished IOU out of service:
UR IOM 0 IOU 1
IOM 0 IOU 1 NOT RESERVED. IT IS DISTINGUISHED.
8600 0395-514 719

UR (Unit Reserved)

Using Preferred Terms
Although PORT and CTL are the preferred mnemonics for port and control devices
respectively, MLI and DLP continue to be allowed as alternatives to the new
mnemonics, but their use is discouraged. The mnemonics MLI and DLP will be
deimplemented in some future software release.
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.
Reserving the Last Ready ODT

If the last ready ODT is being reserved, the system displays the following message:
<mix number> JOB 80 UNITHANDLER

<mix number> SC <unit number> IS THE LAST READY ODT.
ENTER "OK" TO RESERVE IT, "DS" TO ABORT.
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.
720 8600 0395-514

UR (Unit 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.
Reserving a Unit with a Single Number

For units that can be referenced either by device and unit number or by CTL and
device number, you need to use the UR or URcommand only once. For example,
you can use the same number to reference an NSP either as a control or as a unit.
For example, you can reserve or make available NSP 108 by entering either UR/UR
CTL 108 or UR/UR DC 108. It is not necessary to enter both.
The following units are currently in this category:

Integrated communications processors (ICPs)
Reserving VC Units
Only one UR/UR VC <unit number> command needs to be executed to affect all 26
VC units outboard of the same VIM CTL. A separate UR/UR CTL <device number>
command must be issued to affect the CTL.
Reserving TSP Units

You must explicitly reserve or unreserve each unit that makes up a Telephony
Services Platform (TSP). You can enter either a separate UR or UR TSP <unit
number> command for each unit or explicitly list each unit in one command as
follows:
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.
Placing a Unit in Maintenance Mode

You must specify MAINT when you are placing the unit in maintenance mode for
offline maintenance. Do not use MAINT to reserve the unit for online maintenance.
Dealing with an Out of Service CTL or Port

If a control or a port was marked as out of service, you can make it usable by
entering UR , provided that the device initializes successfully.
8600 0395-514 721

USERLICENSE
USERLICENSE
The USERLICENSE command assigns or displays user license information.
On LX Series systems, the number of concurrent users of such products is limited

based on the values of the run-time license keys. The number of concurrent users is
controlled separately for each release of each product. Enforcement occurs as
follows:
Concurrent users up to the license limit are allowed.

You can use the USERLICENSE command to display the current number of
users, or to specify a usage percentage level that causes a warning to be
displayed.
When the number of concurrent users reaches the warning percentage of
licensed users, the following RSVP message is displayed:
Warning! User Licenses for <product> (<release>) have reached threshold
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.
722 8600 0395-514

USERLICENSE
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.
USERLICENSE <product> <percent>

Changes the warning percentage for the product (all release levels). The warning
percentage determines when the system is to display a warning, indicating that the
number of active licenses is approaching the maximum.
USERLICENSE - <product> <release>

Deletes the user license information for the product with the specified release level.
This command enables you to delete information about old releases that are no
longer being used, to avoid clutter in the USERLICENSE response.
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.
8600 0395-514 723

USERLICENSE
USERLICENSE NOWARN <product> <release>

Suppresses the generation of the daily reminder messages when the product has
entered the 60-day grace period. Use this command when you have ordered
additional licenses for the product.
Examples
Example 1
Following is a display from an LX Series system:
USERLICENSE
User License Information
Product Release Active (Peak) Limit Warn Grace Period

Transaction Server 50.1 None (5) 72 90%
Transaction Server Logon 50.1 None (5) 90 90%
Data Access 51.1 3 (4) 8 85%
Client Access Services 10.0 None (None) None 90%
Client Access Services 9.0 18 (18) 16 *90% 11/25/2004
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
User License Information
Product Release Active (Peak) Limit Warn Grace Ends

Transaction Server 51.1 None (3) [None]
Transaction Server 50.1 None (2) [None]
Transaction Server LogOn 51.1 None (4) [None]
Transaction Server LogOn 50.1 2 (2) [None]
Data Access 51.1 None (None) [None]
Data Access 50.1 None (None) [None]
Client Access Services 10.0 None (3) [None]
Client Access Services 9.0 2 (2) [None]
SOMS 10.0 None (None) None 80%
724 8600 0395-514

USERLICENSE
Example 3
The following command sets the warning percentage:
USERLICENSE TRANSSERVER 85
Warnings will be generated for TRANSSERVER at 85% of limit
Example 4
The following command removes user license information for Transaction Server
(formerly COMS):
USERLICENSE - TRANSSERVER 50.1
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):
USERLICENSE NOWARN CLIENTACCESS 10.0
8600 0395-514 725


The W (Waiting Mix Entries) command displays any tasks that need operator or user
action because they are suspended on an RSVP condition. The text of the Wait
message is included in the display.
Syntax
<wild card>
<delim>
/ \ I ~ ! @ # $ % ^ & * '
<wild-card string>
following special characters:

space character.
726 8600 0395-514

W NAME =pack=,
"pack":
W NAME LIT ^=pack=^
Explanation
W
Displays all waiting jobs or tasks.
W NAME <wild-card string>

Displays all waiting jobs or tasks whose task names match the specified card string.
W MCSNAME = <MCS name>

W MCS = <MCS name>
Display only waiting jobs or tasks originating from the specified MCS.
W QUEUE
WQ
Display waiting jobs and tasks from all queues.
W QUEUE <queue number>

Displays any waiting jobs and tasks from the specified queue.
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:
---Job--Task-Pri---Elapsed------ 2 WAITING ENTRIES ----------------------

7200/ 7202 50 10:01 (USER1) *LIBRARY/MAINTENANCE
LOGTAPE/FILE000 REQUIRES MT #1
177/ 177 80 :06 Job (MARTIN)OBJECT/SYMBOL/ACCOUNTS/PAYABLE
504 SECTORS REQUIRED ON VACATION PK 120
The heading line appears on the first page of the Waiting Entries display and before
the Waiting Entries in automatic display mode (ADM).
8600 0395-514 727

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:

Example 2
This example shows waiting jobs and tasks from all queues:
W QUEUE
---Job--Task--Que-Pri---Elapsed------ 1 WAITING ENTRY ALL QUEUES --------

2298/ 2630 22 50 40:44 (FITZ) *SYSTEM/DUMPANALYZER ON NI38
ACCEPT: OK OR RESTART.
Example 3
This example displays only the waiting job that has no usercode associated with it:
W USER=""
---Job--Task-Pri---Elapsed------ 1 WAITING ENTRY USER= ----------------

177/ 177 80 :06 Job (MARTIN)OBJECT/SYMBOL/ACCOUNTS/PAYABLE
504 SECTORS REQUIRED ON VACATION PK 120
728 8600 0395-514

WM (What MCP)
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.
The WM command displays the following information.
Information
MCP Displays the MCP code file name and release level.
Release ID Displays the RELEASEID file attribute of the MCP code

file.
H/L unit Displays the unit number on which the current MCP code
file resides.
Backup unit If present, displays the backup halt/load disk unit

numbers. If a unit number appears in parentheses, the
unit has incurred an excessive number of I/O errors to
the MCP code file, and the MCP on that unit is no longer
used.
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.
8600 0395-514 729

WM (What MCP)
Information
Group ID Displays the name of the current group. For more

information on GROUP ID, refer to the RECONFIGURE
GROUP (Reconfigure System) command.
Hostname Displays the hostname of the system. For more

information, refer to the HOSTNAME (Hostname) system
command.
System serial Displays the unique serial number of the system.

number
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.
Catalog level On a cataloging system, displays the current setting of

the SYSOPS CATALOGLEVELSET parameter. The catalog
level should be zero, unless you use the cataloging
feature. Refer to the System Administration Guide for
more information about the cataloging feature.
Permanent MCP When the system is running on a temporary MCP, the

current permanent MCP is displayed.
Next MCP Displays the designated code file title if an operating

system change is pending.
The MCP bound Displays the language or languages that were

language incorporated into the current code file for display of
system messages. For information about the LANGUAGE
system option, refer to the SYSOPS (System Options)
system command.
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.
730 8600 0395-514

WM (What MCP)
Examples
Example 1
This example shows a typical display generated by a WM command:
WM
MCP: *SYSTEM/DELTA/MCP/501/IC28 [SSR 50.1 (50.189.8192)]

Release ID: IC MCP-050.1A.28 [50.189.028] (50.189.8192)
H/L unit: PK 503 [SYS501]
Compiled: Thursday, July 8, 2004 @ 16:30:50 [NEWP SSR 50.1 (50.150)]
TRACE DIAGNOSTICS EXPERIMENTAL LINEINFO

READLOCK READLOCKTIMEOUT ASDDEBUG DELTAONLY
Haltload reason: HL REQUEST

Haltload time: Wednesday, July 21, 2004 (2004203) 13:37:03
Group ID: DEFAULTNAME
Hostname: MP097
System serial number: 2334
System type: CS7101-1007, 1 CPU
Processor type: CS7101
Catalog level: 0
Next MCP: NOT SPECIFIED
The MCP bound language: ENGLISH
Controlware types saved: NONE
8600 0395-514 731

WM (What MCP)
Example 2
This example shows a display generated by a WM command when the system is
running on a temporary MCP:
WM
MCP: *SYSTEM/521/051114/DELTA/MCP [SSR 52.1 (52.140.1079)] (TEMPORARY)

Release ID: MCP 11.0 [52.140.000] (52.140.1079)
Halt/Load unit: PK 500 [DISK]
Compiled: Monday, November 14, 2005 @ 16:05:35 [NEWP SSR 52.1 (52.140)]
TRACE DIAGNOSTICS EXPERIMENTAL LINEINFO

READLOCK READLOCKTIMEOUT ASDDEBUG DELTAONLY
Haltload reason: CM REQUEST

Haltload time: Monday, January 9, 2006 (2006009) 14:31:41
Group ID: DEFAULTNAME
Hostname: BLUE
System serial number: 2334
System type: LX100, 1 CPU
Processor type: LX100
Catalog level: 0
Permanent MCP: *SYSTEM/DELTA/MCP/DIAGNOSTICS
Next MCP: NOT SPECIFIED
The MCP bound language: ENGLISH FRENCH
Controlware types saved: NONE
732 8600 0395-514

X25MCS (Command Prefix)

The X25MCS (Command Prefix) command is used to start and terminate the X.25
MCS. This command is also used to direct system commands to the X.25 MCS
operator interface.
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.
X25 + <file title>

Starts X.25 initialization using the specified file.
8600 0395-514 733

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.
X25MCS = <file title>

Specifies the X.25 MCS initialization file that is to be used when the X.25 MCS is
initialized.
Example
X25MCS +
X25 IS ALREADY RUNNING
734 8600 0395-514

XD (Bad Disk)
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.
HEX <hex starting address>

Indicates that the address is specified in hexadecimal characters.
Example
XD PK33 ADDRESS 62345 FOR 20
1706 JOB 99 XDDISK
MSG
1706 BADDISK/FMLYINX1/UNIT33/ADF389H CREATED ON DISK PK 033
8600 0395-514 735

XD (Bad Disk)

Only one XD process can execute for a given disk family at a time. The XD command
cannot be used while a RES or SQUASH process is executing for that family.
When an XD operation is performed, the system displays all addresses in

hexadecimal characters and appends H to the address in the file title.
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:
PK <unit number> <baddisk filename> NOT CREATED

(DISK IN USE) <family name>
If this occurs, use the RES (Reserve) command, which moves the files and removes
the sectors from the available disk table.
736 8600 0395-514

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.
The <mix number> Y command displays the following information:
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
8600 0395-514 737

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
Status of Task 12200\656 at 4:49:39

Program name: *OBJECT/ED ON MCPMAST
Codefile created: Monday, June 7, 2004 (2004159) at 16:35:18
Priority: 50
Target Processor Set: 1, Actual Processor Set: 0
Origination: ODT/601/CANDE/1 (LSN 171)
MCS: SYSTEM/CANDE
Usercode: UC1
Chargecode: 6685
Stack State: Waiting on an event
738 8600 0395-514

Example 2
This example shows a response for a job that has a fetch statement:
1555 Y
Job 1555 is waiting in queue 4 at 04:55:08

This job cannot be selected until:
The FETCH statement is OK'ed
Job name: CANDE/JOB
Priority: 60
Origination: Unit 1
Usercode: UC2
CPU Limit: 00:00:03
IO Limit: 00:00:20
Line Limit: 50
Enqueued: Tuesday, June 8, 2004 (2004160) at 04:54:27
This job has an unchecked FETCH statement
Example 3
This example shows a response for a library. It lists the programs that are linked to
the library:
1446 Y
Status of Job 1446/1446 at 04:59:55

Program name: *SYSTEM/COMS ON DISK
Codefile created: Monday, June 7, 2004 (2004159) at 18:21:09
Priority: 80
Origination: Unit 0
Stack State: Frozen, Permanent
Display: COMS:PK47 *COMS/INPQ REPLACED ON DISK
Displayed Thursday, June 20, 2004 at 14:10:43
This library is being used by 6 programs:

01516: *SYSTEM/COMS/PSH/TTP ON DISK
01515: COMS/PA/FACILITY
01504: MARC
01503: *SYSTEM/MARC/COMMANDER ON DISK
01501: MARC
01487: *SYSTEM/COMS ON DISK
Example 4
This example shows the response for a job that has a specified start time:
9325 Y
Job 9325 is waiting in queue 5 at 15:40:22

This job cannot be selected until:
-- The STARTTIME is satisfied
8600 0395-514 739

Job name: BEGIN JOB;STARTTIME =+1:20;

Priority = 50
Origination: Unit 1
Usercode:
Limits: None
Enqueued: Wednesday, August 4, 2004 (2004216) AT 15:30:13
Starttime: Wednesday, August 4, 2004 (2004216) AT 16:50:00
Example 5
This example shows the response for a job that has completed:
9122 Y
Task 9122 is completed
9120/9122 15:01 P-DS *SC
Example 6
This example shows the response for a job in which the process name and the code
file title differ:
9442 Y
Status of Task 16902\5665 at 13:02:59

Program name: (UNX)HUEY
Codefile title: (UNX)OBJECT/WY/3 ON SUPPORT
Created: Friday, June 11, 2004 (2004162) at 13:00:18
Priority: 50
Origination: OCFPIPE17/CANDE/1 (LSN 706)
MCS: SYSTEM/CANDE
Usercode: UNX
Stack State: Waiting on an event
Example 7
This example shows the response for a task with a non-zero CPURATEBIAS:
4218 Y
Status of Task 4210\4218 at 05:13:44

Program name: (ADM)OBJECT/SYMBOL/SOAKER ON USER
Codefile created: Wednesday, September 14, 2005 (2005257) at 05:1
Priority: 50
CPURateBias: 0.99
Origination: CCFPORT1/CANDE/1 (LSN 171)
MCS: SYSTEM/CANDE ON SYS521
Usercode: ADM
Stack State: In Hold Queue
740 8600 0395-514

??CD (Conditional Dump)

The ??CD (Conditional Dump) command lets you enable a CONDITIONALDUMP stop
to cause the system to stop, dump, or record a trace entry.
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 + <stop number>

Enables the TRACE function for CONDITIONALDUMP stop <stop number>.
??CD
Disables the TRACE function for all stops.
??CD <stop number>

Disables the TRACE function for CONDITIONALDUMP stop <stop number>.
??CD STOP
??CD STOP77
The keywords STOP and STOP77 are synonymous; both enable the STOP function.
The system stops whether or not CONDITIONAL HALT is set.
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.
8600 0395-514 741

??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.
742 8600 0395-514

??CL (Clear)
??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
<unit number list>
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.
8600 0395-514 743

??CM (Change MCP)
??CM (Change MCP)

The ??CM (Change MCP) command immediately changes the system so that a
halt/load occurs without waiting for a zero mix count.
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.
Note: The ??CM command does not permit ON <family name>.
??CM # <file name>

Changes the system to a new MCP without waiting for a zero mix count and without
changing the disk bootstrap.
A subsequent halt/load loads the previous MCP because the disk bootstrap still points
to it.
744 8600 0395-514

??CMPAUDIT (CMP Audit)

The ??CMPAUDIT (CMP Audit) command controls tracing of the console multiplexing
protocol (CMP) messages passed between the console and the MCP for systems
supporting the CMPLINK ODT. Tracing these messages can be helpful for resolving
problems with system stability reporting (SSR) or electronic service requests (ESRs).
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.
8600 0395-514 745

??COPY (Copy Files)
??COPY (Copy Files)

The ??COPY (Copy Files) command allows files between tapes and disks to be copied
without the use of the WFL compiler. Since the normal COPY command is compiled
by WFL, this file duplication command should be used only when the WFL library
code file is missing, or does not freeze. Unlike WFL COPY, the default KIND of the
source or destination is set to TAPE even if the name is PACK or DISK.
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.
746 8600 0395-514

??DIALT (Dial Trace)

The ??DIALT (Dial Trace) command initiates DIAL tracing.
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.
8600 0395-514 747

??DS (Discontinue)
??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.
If a discontinued task does not terminate and the CONTROLLER is functioning

normally, subjecting the task to ??DS is no more likely to result in task termination
than a nonprimitive DS command.
Syntax
Explanation
??DS
Discontinues all ordinary tasks.
?? <mix number> DS
Discontinues the task identified by the mix number.
748 8600 0395-514

??DUMP (Dump Memory)

The ??DUMP (Dump Memory) command invokes a nonfatal memory dump.
For more information about memory dump processing, refer to
Memory Dump Processing

Memory Dump Commands
The ??MEMDP (Dump Memory) primitive command
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.
??<mix number> DUMP

Invokes a program dump of the task identified by the mix number.
8600 0395-514 749

??FS (Force Schedule)

The ??FS (Force Schedule) command starts scheduled jobs or tasks.
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.
750 8600 0395-514

??HALT (Halt System)

The ??HALT (Halt System) command unconditionally halts the system. If the
DIAGNOSTICS compile-time option is set, the debugging variants ??HALT AT and
??HALT IN can halt the system at a specified code address.
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.
??HALT IN <code file name>

Marks the specified code file so that whenever this code file is activated the following
AX <SDI> TO SET HALT FOR THIS CODE FILE, "NO" OTHERWISE
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.
8600 0395-514 751

??HALT AT <SDI> FROM USERSTACK

Causes an unconditional halt in the operating system code segment at the specified
SDI whenever the code segment is called from the halt-enabled user program stack.
When this option is used the following message is displayed:
AX "OK" TO HALT AT MCP SDI = <SDI>, "NO" OTHERWISE
Enter AX OK to cause the program to be halted at the specified SDI. Enter AX NO to

prevent halting the program.
??HALT
Disables any halts that have been set. This command does not unmark any
previously marked code files.
??HALT IN <code file name>

Unmarks the specified code file so that it no longer becomes a waiting entry each
time it begins execution.
752 8600 0395-514

??HS (Hold Schedule)

The ??HS (Hold Schedule) command suspends or resumes the starting of new jobs
and tasks.
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.
8600 0395-514 753

??LH (Load Host)
??LH (Load Host)

Note: This command is relevant to IOM systems only.
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
DLP 4007 WILL BE LOADED

The DLP must have been previously reserved.
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.
754 8600 0395-514

??MARC (Transfer to Menu-Assisted Resource Control)
??MARC (Transfer to Menu-Assisted Resource

Control)
The ??MARC (Transfer to Menu-Assisted Resource Control) command lets an ODT
operate as a data comm remote terminal in an environment directed by
SYSTEM/COMS and COMS/ODT/DRIVER.
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.

The ODT must be configured for use as a data comm device before the ??MARC
command is used. If the ODT is not in data comm mode, the system responds with a
UNIT IN USE OR RESERVED message. Refer to the Menu-Assisted Resource Control
(MARC) Operations Guide for more information.
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:
INITIALIZING MESSAGE CONTROL SYSTEM TABLES.
8600 0395-514 755

One of the following messages is issued if the ??MARC primitive command fails:
COMS/ODT/DRIVER HAS BEEN DSED.
COMS/ODT/DRIVER IS NOT DECLARED AS AN MCS.
COMSSUPPORT LIBRARY HAS NOT BEEN SL-ED.
<COMSSUPPORT code file name> (MCS) REQUIRED.
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.
#SC <unit> HAS NO MCS ASSIGNMENT. ENTER ??ODT TO RESUME AS AN ODT.
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>.
#STATION LIMIT EXCEEDED. ENTER ??ODT TO RESUME AS AN ODT.
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.
#UNABLE TO EFFECT MCS TRANSFER. ENTER ??ODT TO RESUME AS AN ODT.
A problem occurred during a transfer of the pseudostation to SYSTEM/COMS (or

<MCS name>, if given).
#NO PSEUDOSTATIONS COULD BE OBTAINED. ENTER ??ODT TO RESUME AS AN ODT.
COMS/ODT/DRIVER cannot obtain a pseudostation from the system.
COMS/ODT/DRIVER recognizes the following commands if they are entered through

the <mix number> SM command. Refer to the SM (Send to MCS or Database)
command.
Command Description
QUIT Lets COMS/ODT/DRIVER be terminated normally. A

DCPTERMINATED result is returned to the controlling
MCS of any pseudostation that was transferred.
756 8600 0395-514

Command Description
CLEAR <ODT unit> Causes COMS/ODT/DRIVER to immediately disconnect

the pseudostation allocated for <ODT unit> from the
MCS to which it has been transferred. After you enter
??ODT to resume ODT operations under the
CONTROLLER, a ??MARC command starts a new
transfer sequence. The ODT unit must be the unit
number of an ODT that was previously switched by the
??MARC primitive command.
ODTS Causes COMS/ODT/DRIVER to display a list of

pseudostations and the corresponding owning ODT
unit, followed by a list of ODT units and corresponding
pseudostations (if a current assignment exists).
8600 0395-514 757

??MEMDP (Dump Memory)

The ??MEMDP (Dump Memory) command is the same as the ??DUMP primitive but is
always recognized by the system (even if the ODT on which it is entered is under the
control of COMS/ODT/DRIVER). Therefore, it is the preferred primitive for forcing a
system dump.
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.
??<mix number> MEMDP

Invokes a program dump of the task identified by the mix number.
758 8600 0395-514

??ODT (Return from Menu-Assisted Resource Control)
??ODT (Return from Menu-Assisted Resource

Control)
The ??ODT (Return from Menu-Assisted Resource Control) command returns
processing of input to the CONTROLLER and the system. This command does not
work unless an ODT was previously transferred to the data comm environment by
the ??MARC primitive command.
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.
8600 0395-514 759

??OK (Reactivate)
??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.
760 8600 0395-514

??OL (Display Label and Paths)

The ??OL (Display Label and Paths) command displays the label and path information
for peripheral devices. If the response to this command requires more than one
screen, the system displays the screens at 8-second intervals.
Syntax
Explanation
??OL <device type> <unit number list>
Displays the label and path information for the devices.

This command is the same as the nonprimitive OL (Display Labels and Paths)
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. For details about the information displayed, refer to the OL (Display
Label and Paths) command.
8600 0395-514 761

??PD (Print Directory)

The ??PD (Print Directory) command enables you to view files on disk when the
controller is suspended. If the response to this command requires more than one
screen, the system displays the screens at 8-second intervals.
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 ("").
Using ??PD <file name> on a Cataloging System

You can also query cataloged tape file entries with the ??PD command. The system
returns information about the cataloged tape file only if you have set the
CATALOGING system option (option 23). The system must be running and active;
otherwise, the system displays the NO FAMILY message. TAPE is the family name
for tape files on a cataloging system.
??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.
762 8600 0395-514

??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.
8600 0395-514 763

??PHL (Programmatic Halt/Load)

The ??PHL (Programmatic Halt/Load) command causes an immediate programmatic
halt/load.
Syntax
Explanation
The ??PHL command causes a programmatic halt/load.
764 8600 0395-514

??REMOVE (Remove File)

The ??REMOVE (Remove File) command removes a file from disk without the use of
the WFL compiler.
Syntax

Since the regular REMOVE command is compiled by WFL, the ??REMOVE command
can be used under the following circumstances:
The WFL library code file is missing or will not freeze.

Space on disk needs to be made for a new WFL library code file.
8600 0395-514 765

??RESTRICT (Restrict ODT)

The ??RESTRICT (Restrict ODT) command sets or removes restrictions on the use of
the ODT at which the command is entered.
Syntax
<security key>
A string from 1 to 17 alphanumeric characters.
Explanation
??RESTRICT + (<security key>)
Restricts the ODT to MARC use.
??RESTRICT (<security key>)

Removes the restriction from the ODT. The security key must be the same as the
key specified when the ODT was restricted.

The primitive command ??RESTRICT provides a convenient method of releasing a
restricted ODT from the restricted ODT itself. It is particularly useful if privileged
access to the system (either through another, unrestricted ODT, or through a
usercode with security administrator privileges) is not available.
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.
766 8600 0395-514

??RJ (Remove JOBDESC File)

The ??RJ (Remove JOBDESC File) command marks the JOBDESC file as to be
reinitialized at the next halt/load. The file is not reinitialized until the next halt/load
takes place. The JOBDESC file resides on the family specified in DL JOBS at the time
of the last halt/load.
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
8600 0395-514 767

??RUN (Run Code File)

The ??RUN (Run Code File) command initiates a code file as an independent process.
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.

This command is sometimes used in preference to the Work Flow Language (WFL)
RUN statement (also available at the ODT) because a WFL RUN statement creates a
WFL job that initiates the code file. The ??RUN command saves memory by initiating
the code file directly, without creating a WFL job.
768 8600 0395-514

??RV (Restart Volume Directory)

On systems with a volume directory, the ??RV (Restart Volume Directory) command
causes a new volume directory to be started after the next halt/load. The old volume
directory is erased during the halt/load. The system stores volume directory
information on the DL CATALOG family in either the SYSTEM/ACCESS or
SYSTEM/CATALOG directory depending on the OP CATALOGING setting.
Syntax
Explanation
The ??RV command tells the system to start a new volume directory after the next
halt/load.

At the next halt/load, the system verifies that a new volume directory is still needed
before starting it.
8600 0395-514 769

??SECAD (Security Administrator Authorization)

The ??SECAD (Security Administrator Authorization) command authorizes security
administrator status on the system. This command is available only as part of Secure
Access Control Module security enhancement software.
Security administrator status must be granted to a usercode through

SYSTEM/MAKEUSER. Until the first security administrator is designated, a privileged
user is allowed to run SYSTEM/MAKEUSER to designate a security administrator.
After one security administrator is designated and the security administrator status is
authorized for the system, only a security administrator can designate other
usercodes as security administrators.

usercode is required for changing security options, changing the USERDATAFILE, and
invoking system commands or SETSTATUS calls that confer privileges or affect
system security.
The following are the restricted system commands and related SETSTATUS calls.
CF LG RESTRICT
DL LOG LOGGING SECOPT
DL MP SL
USERDATA
HU MU ??SECAD
ID REMOTESPO
The MARC DIRECTIVE command is another security-critical function that can be

performed only by security administrators.
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.
If security administrator status is authorized for the system, restricted commands

can be entered only from a source with SECADMIN status. Such sources include
A MARC session with a security administrator usercode.

A program using SETSTATUS that is running under a usercode with
SECADMIN status.
A program using DCKEYIN that is marked with SECADMIN status by the MP
(Mark Program) command.
770 8600 0395-514

The following are required when ??SECAD is set:
A security administrator usercode to update the network information file

A REMOTESPO : OK to activate the remotespo stations
Syntax
Explanation
??SECAD
Displays the current SECADMIN option setting.
??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.
8600 0395-514 771

??ST (Stop)
??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.
772 8600 0395-514

??TRACE (Trace Table)

The ??TRACE (Trace Table) command clears the trace table or specifies that a
system dump is to be performed each time the trace table is filled.
The ??TRACE command is available only if the MCP was compiled with the TRACE
compile-time option set.
For additional information, refer to the ??CD (Conditional Dump) primitive

command.
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 ().
8600 0395-514 773

??UNWRAP (Unwrap Files)

The ??UNWRAP (Unwrap Files) command unwraps a single wrapped file or a file
within a wrapped container from a CD-ROM or disk without the use of the WFL
compiler.
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.
774 8600 0395-514

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.)
The remaining options are described separately below.
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.
OUTOF <container name>

Specifies that the unwrapped file is to be created from a wrapped file in the specified
container.
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.
8600 0395-514 775

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:
??UNWRAP (THIEN)RECEIPTS/FILE AS (THP)RECEIPTS/INCOMING FROM DISK

TO LFPACK(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:
??UNWRAP (THIEN)RECEIPTS/MONDAY OUTOF (THP)RECEIPTS/FEBRUARY

FROM LFPACK(DISK)
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:
??UNWRAP (THIEN)RECEIPTS/MONDAY AS (THP)ACCTS/MONDAY OUTOF

(THIEN)RECEIPTS/FEBRUARY FROM DISK TO LFPACK(DISK)

If the security option RESTRICTUNWRAP is set, object code files that are unwrapped
are marked as restricted. To prevent the unwrap process from restricting the object
code files, reset the security option RESTRICTUNWRAP or use the RESTRICTED =
FALSE specification. Refer to the Security Administration Guide for more information
on the SECOPT system command and the RESTRICTUNWRAP option.
776 8600 0395-514

??UR (Unit Reserved)

The ??UR (Unit Reserved) command reserves a unit to allow maintenance to be
performed or makes a previously reserved unit available for normal use. Once a unit
has been reserved, it is no longer available for assignment to user programs.
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.
8600 0395-514 777

??W (Waiting Mix Entries)

The ??W (Waiting Mix Entries) primitive command displays the waiting tasks that
need operator action because they are suspended on an RSVP condition. The reason
for suspension is also displayed. If the response to this command requires more than
one screen, the system displays the screens at 8-second intervals.
Syntax
Explanation
The ??W command displays all waiting jobs or tasks.
778 8600 0395-514

??ZFA (Zero Failure Analysis)

The ??ZFA (Zero Failure Analysis) command resets the error counters kept by Failure
Analysis and displayed in response to an FAS (Failure Analysis Summary) command.
Refer to the FAS (Failure Analysis Summary) command.
Syntax
Explanation
??ZFA
Clears all error counts for all modules.
??ZFA CPM <number>

??ZFA MSM <number>
Reset the error counters kept by Failure Analysis for a central processing module
(CPM) or memory subsystem module (MSM).
8600 0395-514 779

780 8600 0395-514

Section 2
Memory Dump Processing and
Commands

The following table lists memory dump commands and their meanings. You can use
these commands while the memory dump procedure is running.
Command Explanation
ALLINUSE Enables a more comprehensive dump when a dump to tape

is underway. If a PARTIAL dump is initiated, you can use the
ALLINUSE command to terminate the current dump and to
start processing an ALLINUSE memory dump. Only the in-
use areas of memory are dumped.
AUTOSUPPRESS Following the memory dump, marks the AUTOSUPPRESS

entry in the Dump History file for automatic suppression.
For more information, refer to the MDT (Memory Dump
Type) command.
AUTOSUPPRESS Cancels the previous AUTOSUPPRESS command.
CD <unit Invokes memory dump to CD-ROM.

number>
CL If the dump is to tape, immediately discontinues the dump

and then restarts it.
COMPLETE Enables a more comprehensive dump when a dump to tape

is underway. If a PARTIAL or ALLINUSE dump is initiated,
you can use the COMPLETE command to terminate the
current dump and to start processing a COMPLETE memory
dump. The entire memory image is dumped.
DS Discontinues the dump. In the case of a fatal dump, a

halt/load occurs. Otherwise, processing resumes as normal.
HL, HL + Cause a halt/load to be performed. If the command is

entered after the dump has started, the halt/load
immediately follows the dump. If it is entered before the
dump starts, the dump is discontinued and the halt/load
takes place immediately.
8600 039-514 781

Command Explanation
HL Cancels a halt/load previously requested by an HL or HL +

command that was entered while a dump was running.
HS, HS + Halt the starting of new jobs or tasks after the dump.
HS Resume the starting of new jobs or tasks after the dump.
MIX Displays the reason for 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.
NODUMP Sets the system run-time option NODUMP to FALSE after

the dump.
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.
PROG, <SPCFY> Request that automatic progress reports be directed to this

ODT. The system displays a bar chart that shows the
current dump progress. The charts are updated every 10
seconds. When progress reports are already in progress, the
system immediately refreshes the screen. Note that
excessive progress report requestssuch as repeatedly
pressing the SPCFY keycan result in greatly increasing the
time required to complete the dump.
PROG Discontinues progress reports at all ODTs.
RESTART If the dump is to tape, immediately discontinues the dump

and then restarts it.
782 8600 0395-514

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.
SUPPRESS Following the memory dump, performs an MDT SUPPRESS

<dump number> action for the current dump. You can use
this command only during a nonfatal memory dump. For
details, refer to the MDT (Memory Dump Type) command.
SUPPRESS Cancels a previous SUPPRESS command.
TAPE Causes a dump that is to be written to disk to be written to

tape or CD-R instead. If the dump is already processing, it is
terminated.
8600 0395-514 783


The system automatically starts a memory dump when certain software or hardware
errors occur. You can also request a memory dump, as discussed in the DUMP
(Dump Memory), ??MEMDP (Dump Memory), and ??DUMP (Dump Memory)
commands. When a memory dump runs, it produces a display that shows the reason
for the dump and whether or not the dump is fatal. If a dump is fatal, after the
memory dump completes, the system automatically halt/loads. If the memory dump
is not fatal, after the memory dump completes, the system starts running again.
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.
When a HLUNIT TAPE <unitnumber> is specified, a Force Dump is able to

automatically initiate when a "DUMMMP" scratch tape is mounted on the tape
unit. This action enables automatic force dumps to proceed when requested from
the MCP on an unattended system.
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.
784 8600 0395-514

Memory Dump to CD-R

Memory dump to CD-ROM is invoked by entering CD <unit number> when prompted
SCRATCH TAPE OR CD REQUIRED. If the dump will not fit on a single CD-ROM, you
are prompted to provide media for continuation CD-ROMs as needed. The
FAMILYNAME of the first CD-ROM containing a memory dump is of the form
DP_<date>_<time>. Continuation CDs (if any) are named
DP_<date>_<time>_<integer>. Following are examples of names for a three CD
dump:
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.
Handling Memory Dumps

The following table describes the system commands that control the way the system
handles memory dumps. See Memory Dump Commands for commands that you can
use while the memory dump procedure is running.
Command Description
CM + Directs memory dumps to a dump disk file on the halt/load

HLDUMPDISK family.
DA Starts the DUMPANALYZER system utility.
DF Empties dump disk files.
DL DPFILES Directs DUMPDISKMASTER to unload memory dumps from a

dump disk file to a disk.
DN <file name> Directs memory dumps to a dump disk file.
DUMP, ??DUMP, Request that a memory dump be performed.

and ??MEMDP
8600 0395-514 785

Command Description
MDT Either sets or interrogates the current system-wide memory

dump type options. The MDT command enables you to do
the following:
Set a system-wide memory dump type to override the
dump call initiated by the operating system.
Set the noncompression option for complete dumps to
disk.
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.
OP The memory dump will be discontinued if it encounters

AUTORUNNING problems such as: the dumpdisk file has insufficient capacity
for the dump, or a fatal IO error occurs while writing the
dump.
For more information, see Handling Dumps to Disk.
OP NODUMP Determines whether or not memory dumps are to be

performed.
Memory Dump Performance

The MDT NONCOMPRESSED option was originally implemented to improve
performance on systems that could perform the I/O faster than the processor could
compress the data. It was not recommended for use on larger systems with faster
processors because the option increased the total elapsed time of the dump.
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.
786 8600 0395-514

Following are a few details to be aware of when attempting to improve complete

memory dump elapsed times by utilizing the MDT NONCOMPRESSED option:
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.
Handling Dumps to Disk

When a memory dump to disk is finished, the system automatically starts a
DUMPDISKMASTER job that attempts to unload the dump from the dump disk file.
The action that DUMPDISKMASTER takes depends on whether the system option
AUTORUNNING (OP 15) is set, or either of the MDT options AUTOSAVE and
AUTOUNLOAD is set, and whether DL DPFILE is specified.
If MDT AUTOSAVE is set, DUMPDISKMASTER creates a SAVEDUMP file by

interfacing with Dumpanalyzer during the unloading of the dump to perform a
SAVE command. The file is created on the DL DPFILES disk family if specified,
otherwise it is created on the halt load family.
If MDT AUTOSAVE is reset and OP AUTORUNNING is set, DUMPDISKMASTER

creates a raw memory dump image in a DP file. As with the MDT AUTOSAVE
command, the file is created on the DL DPFILES disk family if specified,
otherwise it is created on the halt load family.
If both MDT AUTOSAVE and OP AUTORUNNING are reset, DUMPDISKMASTER

inspects the MDT AUTOUNLOAD setting. If the option is set, the dump will be
unloaded automatically to a DP file on the DL DPFILES family, or as a
MEMORY/DUMP tape.
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.
When DUMPDISKMASTER creates a DP or SAVEDUMP disk file, it gives the file a

name that includes either the DP or SAVEDUMP prefix and includes the date and
8600 0395-514 787

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
The command produces the following response:
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.
Running the DUMPANALYZER System Utility

You can analyze memory dumps by running the SYSTEM/DUMPANALYZER utility
program. The DUMPANALYZER utility can analyze dumps stored on MEMORY/DUMP
tapes, DP disk files, and saved memory dump disk files created by an earlier
DUMPANALYZER run.
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>;
To analyze a memory dump on a MEMORY/DUMP tape, you also run the

DUMPANALYZER utility. It expects an input tape file named MEMORY/DUMP by
default. To make sure that the program analyzes the correct memory dump, you can
label equate the serial number of the tape as follows:
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.
788 8600 0395-514

Analyzing dumps with the EDITOR System Utility

You can analyze memory dumps by loading them into the Editor utility program. You
can load any file accepted by DUMPANALYZER, including dumps stored on
MEMORY/DUMP tapes, unsaved dumpdisk files, and saved memory dump disk files
created by DUMPANALYZER or by the Editor. Use the LOAD DUMP <dump file>
syntax to load the dump. For further information, refer to the Editor online help.
Improving performance when using the NONCOMPRESSED option

Dumps that are taken uncompressed (when MDT NONCOMPRESSED is SET) utilize a
scheme whereby concurrent I/O's are performed when there are multiple units in the
DN family in order to improve performance, However, because memory dumps are
performed using a primitive I/O interface, there is a limit to the number of I/O's that
may be performed at one time. For uncompressed dumps, the dump process
recognizes that additional I/O's may be performed by utilizing slots normally
reserved for ODT units. To take advantage of this scheme, it is recommended that
ODT units be freed from the partition if they do not exist.
Refer to the FREE (Free Resource) and DOWN (Down Resource) commands.
8600 0395-514 789

790 8600 0395-514

Appendix A
Functional Command Groupings
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.
Automatic Display Mode (ADM) and ODT Control Commands
BNA Commands
Data Comm Commands
Directory and Disk File Management Commands
Disk Pack Commands
Dump Commands
Installation and Licensing Commands
Job Queue Commands
Log Commands
Maintenance Commands
MCP Commands
Memory Management Commands
Peripheral Commands
Printer Commands
Program Communication Commands
System Configuration Commands
System Security Commands
Tape Commands
Old and New Command Mnemonics
8600 039-514 791

Automatic Display Mode (ADM) and ODT Control

Commands
Refer to the following commands:
CQ (Clear Queue)
CU (Core Usage)
FIND
LABEL (Label ODT)
MAX (Maximums)
ML (Mix Limit)
MX (Mix Entries)
NS (Next Screen)
O (Overlay)
??ODT (Return from Menu-Assisted Resource Control)
PMIX (Processor Mix)
PS STATUS (abbreviated as PS in the ADM command syntax)
SHOW
792 8600 0395-514

SUPPRESSED option of MP (Mark Program)
TERM (Terminal)
U (Utilization)
8600 0395-514 793

BNA Commands
BNA Commands
AT (At Remote Host)
BNA
BNAVERSION
CA (Candidate)
HOSTNAME (Hostname)
HU (Host Usercode)
NET (Network)
NW (Network Prefix)
794 8600 0395-514

Data Comm Commands
Data Comm Commands

SEND (Send Message)
8600 0395-514 795


DIR (Directory)
DIRECTORY ONLY
DL (Disk Location)
PD (Print Directory) and PDRES (Print Directory Resident Files Only)
PV (Print Volume)
RB (Rebuild Access)
RES (Reserve)
RM (Remove)
796 8600 0395-514

SHOWOPEN (Show Open Files)
SQUASH SYSTEMDIRECTORY (Consolidate Disk Allocation SYSTEMDIRECTORY)
TL (Transfer Log)
XD (Bad Disk)
8600 0395-514 797

Disk Pack Commands
Disk Pack Commands

CLOSE (Close Pack)
DIRECTORY ONLY
FIND
IOTIMER (IOM Systems)
LH (Load Host)
??LH (Load Host)
MODE (Unit Mode)
?OL (Display Label and Paths)
PARTIALSETS
PG (Purge)
REMOTEDISK
RES (Reserve)
SHOW
798 8600 0395-514

Disk Pack Commands
SHOWOPEN (Show Open Files)
SQUASH SYSTEMDIRECTORY (Consolidate Disk Allocation SYSTEMDIRECTORY)
STORESAFE
XD (Bad Disk)
8600 0395-514 799

Dump Commands
Dump Commands
HLDUMPDISK option of CM (Change MCP)
DA (Dump Analyzer)
DPFILES option of DL (Disk Location)
DN (Dump Name)
DUMP (Dump Memory)
NODUMP option of OP (Options)
800 8600 0395-514


IK (Install Keys)
LICENSESTATUS
USERLICENSE
8600 0395-514 801

Job Queue Commands
Job Queue Commands

JOBDESC option of DL (Disk Location)
DQ (Default Queue)
DS (Discontinue)
??DS (Discontinue)
FS (Force Schedule)
HS (Hold Schedule)
ML (Mix Limit)
OK (Reactivate)
??OK (Reactivate)
PF (Print Fetch)
PQ (Purge Queue)
PR (Priority)
QF (Queue Factors)
SQ (Show Queue)
UQ (Unit Queue)
802 8600 0395-514

Log Commands
Log Commands
LOG option of DL (Disk Location)
LC (Log Comment)
LJ (Log to Job)
LOG (Analyze Log)
TL (Transfer Log)
8600 0395-514 803

DO (Diagnostic OptionsIOM Systems)
LOADMICROCODE (Load Microcode)
PG (Purge)
RES (Reserve)
RF (Reliability Factor)
RY (Ready)
SV (Save)
UP (Up Resource)
UR (Unit Reserved)
804 8600 0395-514

XD (Bad Disk)
8600 0395-514 805

MCP Commands
MCP Commands
CM (Change MCP)
??CM (Change MCP)
DA (Dump Analyzer)
DL (Disk Location)
DN (Dump Name)
DR (Date Reset)
DUMP (Dump Memory)
HS (Hold Schedule)
ML (Mix Limit)
MP (Mark Program)
OP (Options)
OPLOCKTIMEOUT
806 8600 0395-514

MCP Commands
PRIMITIVE RUN
TD (Time and Date)
TR (Time Reset)
U (Utilization)
WM (What MCP)
8600 0395-514 807


ASDU (ASD Usage)
CACHE (Disk CacheExcept VM Systems)
CU (Core Usage)
DL (Disk Location) OVERLAY option
FIND
FREE
FS (Force Schedule)
HS (Hold Schedule)
ML (Mix Limit)
MM (Memory Module)
SAVEMEMORYLIMIT option of MQ (Make or Modify Queue)
O (Overlay)
RY (Ready)
SF (Set Factor)
SHOW
ST (Stop)
808 8600 0395-514

??ST (Stop)
SV (Save)
U (Utilization)
8600 0395-514 809

Peripheral Commands
Peripheral Commands
CACHE (Disk CacheExcept VM Systems)
CL (Clear)
??CL (Clear)
FIND
IL (Ignore Label)
MODE (Unit Mode)
NAMEMAP
OU (Output Unit)
PG (Purge)
REMOTEDISK
RF (Reliability Factor)
RY (Ready)
SHOW
SN (Serial Number)
SV (Save)
810 8600 0395-514

Peripheral Commands
UL (Unlabeled)
UP (Up Resource)
UQ (Unit Queue)
UR (Unit Reserved)
8600 0395-514 811

Printer Commands
Printer Commands
BACKUP option of DL (Disk Location)
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
812 8600 0395-514

Printer Commands
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)
8600 0395-514 813

Processor Management Commands
Processor Management Commands

FIND
ML (Mix Limit)
MP (Mark Program) CONTROL option
MQ (Make or Modify Queue) PRIORITY and PROCESSTIME options
O (Overlay)
PR (Priority)
SHOW
TI (Times)
U (Utilization)
UP (Up Resource)
814 8600 0395-514


ASDU (ASD Usage)
AX (Accept)
BADFILE (Bad File)
BR (Breakout)
CU (Core Usage)
DS (Discontinue)
??DS (Discontinue)
DUMP (Dump Memory)
FA (File Attribute)
FM (Form Message)
FR (Final Reel)
FS (Force Schedule)
IL (Ignore Label)
LJ (Log to Job)
LP (Lock Program)
NF (No File)
OF (Optional File)
OK (Reactivate)
??OK (Reactivate)
8600 0395-514 815

OU (Output Unit)
PF (Print Fetch)
PR (Priority)
QT (Quit)
RM (Remove)
ST (Stop)
??ST (Stop)
SW (Switches)
TI (Times)
UL (Unlabeled)
816 8600 0395-514


LOADMICROCODE (Load Microcode)
MM (Memory Module)
NAMEMAP
RY (Ready)
SV (Save)
UP (Up Resource)
UR (Unit Reserved)
8600 0395-514 817


USERDATA option of DL (Disk Location)
HU (Host Usercode)
MP (Mark Program)
MU (Make User)
OK Option of REMOTESPO (Activate REMOTESPO)
SYSADMIN COMMAND
User option of TERM (Terminal)
818 8600 0395-514

Tape Commands
Tape Commands
BADFILE (Bad File)
??COPY (Copy Files)
FIND
FR (Final Reel)
IL (Ignore Label)
MODE (Unit Mode)
OF (Optional File)
OU (Output Unit)
PG (Purge)
PV (Print Volume)
RW (Rewind)
SEND (Send Message)
SHOW
SN (Serial Number)
TV (Type Volume)
UL (Unlabeled)
8600 0395-514 819


The following table provides cross-references for the old and new forms of the
system commands. The old mnemonics shown in this table are currently accepted as
valid. If they are deimplemented in a future release, appropriate warnings will be
issued.
Old New
M MX (Mix Entries)
NEXT NS (Next Screen)
P PER (Peripheral Status)
820 8600 0395-514

Appendix B
Using CANDE and WFL at an ODT
Entering CANDE Control Commands at an ODT

You can enter certain CANDE control commands at an ODT as part of an SM (Send to
MCS or Database) command. These commands are described in either the CANDE
Configuration Reference Manual or the CANDE Operations Reference Manual.
The following commands are described in the CANDE Configuration Reference

Manual:
?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
8600 039-514 821

Entering CANDE Control Commands at an ODT
?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
822 8600 0395-514

Starting Work Flow Language (WFL) Jobs at an ODT
Starting Work Flow Language (WFL) Jobs at an

ODT
You can start WFL jobs at an ODT in either of two ways:
By entering a START statement to initiate a job stored in a disk file

By entering the complete job at the ODT and transmitting it
A complete job that is entered at the ODT should begin with a BEGIN JOB statement.
It is not necessary to end the job with an END JOB statement, because WFL adds
this statement automatically. Alternatively, you can specify that a WFL job is to be
passed to the WFL compiler by preceding the statement with either the letters CC or
a question mark (?). Examples of these formats are ?MOVE and CC RESTORE.
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:
ABORT COPY RESTORE
ACCESS DISPLAY RESTOREADD
ADD MKDIR RUN
ALTER MODIFY SECURITY
ARCHIVE PASSWORD START
BEGIN PRINT UNWRAP
BIND PROCESS USER
CATALOG PTD VOLUME
CHANGE QUEUE WRAP
CLASS REMOVE
COMPILE RERUN
8600 0395-514 823

Starting Work Flow Language (WFL) Jobs at an ODT
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
DISK = DISK ONLY
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.
824 8600 0395-514

Appendix C
Cold-Start Default Values
Default Options after a Cold-Start

The Option column of the table shows the name of the system command that
displays the status of that option.
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.
8600 039-514 825

Option Default
ACCOUNTING ACCOUNTING DEPENDENTTASK IDENTIFIED.

ACCOUNTING FILE IDENTIFIED
Refer to ACCOUNTING (Resource Accounting)
ADM ADM (ACTIVE 7, WAITING 3, SCHEDULED 2, COMPLETED

5, MESSAGES) DELAY 9
(Dependent on JOBDESC)
Refer to ADM (Automatic Display Mode)
AI No automatic initiation programs

Refer to AI (Automatic Initiation)
ASD ASD 50
Refer to ASD (Actual Segment Descriptor)
AUTORESTORE DONTCARE
Refer to AUTORESTORE (Archiving AUTORESTORE Option)
BNA INIT/INFO file = *NULL. Next INIT/INFO file = *NULL

Refer to BNA
BNAVERSION BNAV2
Refer to BNAVERSION
CF CF
(Dependent on LOADER)
Refer to CF (Configuration File)
CM CM <MCP name> (halt/load unit index) HLDUMPDISK

STANDBY
Refer to CM (Change MCP)
CO CO ERRORDP, INPUT, MONITOR, SPRWARN

Refer to CO (CONTROLLER Options)
COMPILERTARGET COMPILERTARGET THIS

Refer to COMPILERTARGET (Set Default Target Value)
CS CS
Refer to CS (Change Supervisor)
826 8600 0395-514

Option Default
DL DL BACKUP <halt/load family>

DL CATALOG (has no default)
DL DPFILES
DL JOBS <halt/load family>
DL OVERLAY 504 <halt/load family>
DL ROOT
DL SORT DISK
DL USERDATA <halt/load family>
(Dependent on CONFIGURATION, LOADER)
Refer to DL (Disk Location)
DN DN
Refer to DN (Dump Name)
DO All options are RESET
DQ DQ 0
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)
LOGGING LOGGING DEFAULT

Refer to LOGGING (Logging Options)
8600 0395-514 827

Option Default
MAX MAX MESSAGES 500, MAX COMPLETED 500, MAX

SESSION 9999
Refer to MAX (Maximums)
MIRROR OPTION MIRROR OPTION PARTIALSETS WAIT

MIRROR OPTION QUICKAUDIT OFF
Refer to MIRROR (Mirror Disk)
MDT MDT COMPLETE

Refer to MDT (Memory Dump Type)
MIXLIMIT MIXLIMIT
Refer to ML (Mix Limit)
MSC MSC CLEAR

Refer to MSC (Message Control)
MQ MQ 0, MIXLIMIT 10,
DEFAULTS (PRIORITY = 50),
LIMITS (PRIORITY = 99)
Refer to MQ (Make or Modify Queue)
NET NET = *NULL

Refer to NET (Network)
NETEX NETEX = *DEFAULT

Refer to NETEX (Support NETEX Software)
OP OP + TERMINATE, LPBDONLY AUTORM AUTORECOVERY

MOREBACKUPFILES
or
OP + 2, 4, 5, 8, 25.
Refer to OP (Options)
OPLOCKTIMEOUT OPLOCKTIMEOUT = 30,10

Refer to OPLOCKTIMEOUT
PLI PLI 60
PLI
Refer to PLI (Periodic Logging Interval)
828 8600 0395-514

Option Default
PS ACTIVE PS ACTIVE BNA

PS ACTIVE REMOTE
PS ACTIVE SITE=0
(Dependent on PRINTERINFO)
Refer to PS ACTIVE
PS ASSOCIATE PS ASSOCIATE<device specifier>

Refer to PS ASSOCIATE
PS BANNER PS BANNER PAGECOMP

Refer to PS BANNER
PS CONFIG PS CONFIG + <all line printers>

Refer to PS CONFIGURE
PS DEFAULT PS DEFAULT COMPRESSFILES = FALSE, CONFIGURE =

AUTOMATIC,
DESTINATION (unspecifieddefault pool),
JOBSUMMARY = UNCONDITIONAL, PRINTDISPOSITION
= EOJ, REMOVEDLOCKED = NEVER, PRINTERKIND =
DONTCARE, REQUESTMAX = 9999999, SHOWDISPLAY
= UNSORTED
Refer to PS DEFAULT
PS FONTLIB PS FONTLIB <PRINTERKIND value>

Refer to PS FONTLIB
PS GROUP PS GROUP <group name>

Refer to PS GROUP
PS HEADER PS HEADER
Refer to PS HEADER
PS SELECTION PS SELECTION criterion 1: volume

Refer to PS SELECTION
8600 0395-514 829

Option Default
PS TRAILER PS TRAILER
Refer to PS TRAILER
REMOTESPO : OK No authorized REMOTESPO stations

Refer to REMOTESPO (Activate REMOTESPO)
RESTRICT No restricted commands

COMMAND Refer to RESTRICT (Set Restrictions)
SB SB DISK = DLBACKUP PACK = PACK TAPE = TAPE

Refer to SB (Substitute Backup)
SBP SBP INTERVAL = 10, SLICERATE = 50

Refer to SBP (System Balancing Parameters)
SECOPT SECOPT CLASS U

Refer to SECOPT (Security Options)
SEGARRAYSTART SEGARRAYSTART = 4096 (unless the page size for that

model is greater than 4096, in which case the page size
value is the default)
Refer to SEGARRAYSTART (Array Segmentation Start
Size)
SF SF OLAYGOAL 0 AVAILMIN 0 FACTOR 100 BUFFERGOAL

2048 OLAYSATURATION 15 OLAYCHANGE 10
Refer to SF (Set Factor)
SI No intrinsic file name

Refer to SI (System Intrinsics)
830 8600 0395-514

Option Default
SL Establishes the following support libraries. The codefile

family is the halt/load family.
Refer to SL (Support Library)
SL CENTRALSUPPORT=*SYSTEM/CENTRALSUPPORT
SL
CREDENTIALSUPPORT=*SYSTEM/CREDENTIALSUPPORT
SL DATACOMSUPPORT=*SYSTEM/DATACOMSUPPORT
SL DRCSUPPORT=*SYSTEM/DRCSUPPORT
SL EVASUPPORT=*SYSTEM/EVASUPPORT
SL GENERALSUPPORT=*SYSTEM/GENERALSUPPORT
SL JOBFORMATTER=*SYSTEM/JOBFORMATTER
SL PRINTSUPPORT=*SYSTEM/PRINT/SUPPORT
SL RSSSUPPORT =*SYSTEM/RSSSUPPORT
SL VSLSUPPORT=*NAPSYSTEM/VSL
SL WFLSUPPORT=*SYSTEM/WFLSUPPORT
STRUCTURECACHE STC DIRECTORY 100

STC HEADERS 30
STC CODESTACKS 15, 60
STC USERDATAFILE 200
Refer to STRUCTURECACHE (Cache Maintenance)
SUPPRESSWARNING SUPPRESSWARNING NONE

Refer to SUPPRESSWARNING (Suppress Warning)
8600 0395-514 831

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)
TERM TERM LINES 24 WIDTH 80 FIRST 2 TRUNCATED TRUE

RESPONSE EXPANDED MESSAGES FALSE
Refer to TERM (Terminal)
TL TL * ROWS 140 RECORDS 1000

Refer to TL (Transfer Log)
UQ UQ <device type> <unit number list>

Refer to UQ (Unit Queue)
??SECAD ??SECAD
Refer to ??SECAD (Security Administrator Authorization)
832 8600 0395-514

Default Status of Units

The default status of units is easier to describe. First, a unit must be available. Then
its status is determined by whether the unit is readyand write-enabled when
applicable. You can determine additional status by the system commands listed in
the following table.
Status Default
CACHE CACHE <unit>

CM CM STANDBY ON <family name>
MODE MODE <unit> IO

MODE <unit> AUTOUNLOAD OFF
RESTRICT RESTRICT <unit>
RY RY <unit>
UR UR <unit>
8600 0395-514 833

834 8600 0395-514

Appendix D
Basic Constructs
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 bus address>

The maintenance card address of the base. It must be a number in the range 0
through 255.
<base bus number>

The maintenance bus number of the base. It must be a number in the range 0
through 15.
<base extension number>

A number in the range 0 through 15.
<base number>
The number that identifies a base.
<bus>
A number identifying a PCI bus within a PCI bridge or IONODE on an IOP 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.
8600 039-514 835

Basic Constructs
<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
<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>.
<CTL number list>
<day of week>
The value used to indicate the days of the week.
836 8600 0395-514

Basic Constructs
<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 number list>

Any number in the range of 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
DK Disk or memory disk
HC Host control unit
HY HYPERchannel unit
LP Line printer
MT Magnetic tape drive
NP Network processor
PK Pack
SC ODT (or System Console)
TSP Telephony Services Platform

unit
8600 0395-514 837

Basic Constructs
Device Meaning
Type
UD Unknown device; usually a

small computer systems
interface (SCSI) unit that has
not yet been identified to the
system as either a tape or a
pack
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).
838 8600 0395-514

Basic Constructs
<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.
<DTU number list>
<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.
8600 0395-514 839

Basic Constructs
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.
As an alternate syntax for indicating a file associated with a usercode, instead of

preceding the file name with the usercode in parentheses, you can precede the file
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.
<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>
840 8600 0395-514

Basic Constructs
<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
<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>
<MIObus>
A number identifying a particular MIO bus of a PCI bridge on an IOP system. Valid
numbers are 0 and 1.
8600 0395-514 841

Basic Constructs
<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.
<mix number list>

Two or more mix numbers (or ranges of mix numbers), separated by commas.
<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.
System MSU Number Value
MCPvm 0
NX5600 Any number in the range 0 through 1.
IOP Any number in the range 0 through 2.
<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.
842 8600 0395-514

Basic Constructs
<nonquote EBCDIC character>

Any EBCDIC character for which the hexadecimal code is greater than or equal to
hexadecimal 40 and that is not the EBCDIC quotation mark character (").
<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.
<port number list>
<queue number>
Any number in the range 0 through 1023.
<queue number list>
<scratch pool name>

Starting with a letter or digit, followed by from 0 to 16 letters, digits, hyphens, or
underscores.
<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.
8600 0395-514 843

Basic Constructs
<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
IOM = 1 through 32767

IOP = 1 through 65535
<unit number list>
Unit and Mix Number Ranges

The number of units and mix numbers that can be specified in a single command is
limited. If you specify too many numbers, the MCP generates the error TOO MANY
NUMBERS. When you include unit and mix number ranges in a command (for
example, RY PK 500 - 509), the range is expanded as if each individual usint or mix
number was explicitly specified. If a command generates the error TOO MANY
NUMBERS, reduce the size of any unit or mix number range.
844 8600 0395-514

Basic Constructs
<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.
8600 0395-514 845

Basic Constructs
846 8600 0395-514

Appendix E
Understanding Railroad Diagrams
Understanding Railroad Diagrams

Railroad diagrams are diagrams that show you the standards for combining words
and symbols into commands and statements. These diagrams consist of a series of
paths that show the allowable structures of the command or statement.
This topic contains the following information about railroad diagrams:
Railroad diagram concepts:

Paths
Constants and variables
Constraints
Following the paths of a railroad diagram
Examples with sample input
8600 039-514 847

Paths
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 following example has three paths:
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.
Railroad diagrams are intended to show
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.
The following table introduces the elements of a railroad diagram:
Elements of a Railroad Diagram
The diagram element . . . Indicates an item that . . .
Constant Must be entered in full or as a specific abbreviation
Variable Represents data
Constraint Controls progression through the diagram path
848 8600 0395-514

Constants and Variables
Constants and Variables

A constant is an item that must be entered as it appears in the diagram, either in full
or as an allowable abbreviation. If part of a constant appears in boldface, you can
abbreviate the constant by
Entering only the boldfaced letters

Entering the boldfaced letters plus any of the remaining letters
If no part of the constant appears in boldface, the constant cannot be abbreviated.
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 railroad diagrams, variables are enclosed in angle brackets.
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.
Valid abbreviations for BEGIN are
BE
BEG
BEGI
8600 0395-514 849

Constraints
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
850 8600 0395-514

Constraints
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.
Some loops include a return character. A return character is a characteroften a

comma (,) or semicolon (;)that is required before each repetition of a loop. If no
return character is included, the items must be separated by one or more spaces.
8600 0395-514 851

Constraints
Bridge
A loop can also include a bridge. A bridge is an integer enclosed in sloping lines (/ \)
that
Shows the maximum number of times the loop can be repeated

Indicates the number of times you can cross that point in the diagram
The bridge can precede both the contents of the loop and the return character (if
any) on the upper line of the loop.
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.
852 8600 0395-514

Following the Paths of a Railroad Diagram
Following the Paths of a Railroad Diagram

The paths of a railroad diagram lead you through the command or statement from
beginning to end. Some railroad diagrams have only one path; others have several
alternate paths that provide choices in the commands or statements.
The following railroad diagram indicates only one path that requires the constant
LINKAGE and the variable <linkage mnemonic>:
Alternate paths are provided by
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>.
8600 0395-514 853

Railroad Diagram Examples with Sample Input

The following examples show five railroad diagrams and possible command and
statement constructions based on the paths of these diagrams.
Example 1
<lock statement>
Sample Input Explanation
LOCK (FILE4) LOCK is a constant and cannot be altered. Because no

part of the word appears in boldface, the entire word
must be entered.
The parentheses are required punctuation, and FILE4 is
a sample file identifier.
Example 2
<open statement>
OPEN DATABASE1 The constant OPEN is followed by the variable

DATABASE1, which is a database name.
The railroad diagram shows two user-selected items,
INQUIRY and UPDATE. However, because an empty
path (solid line) is included, these entries are not
required.
OPEN INQUIRY The constant OPEN is followed by the user-selected

DATABASE1 constant INQUIRY and the variable DATABASE1.
OPEN UPDATE The constant OPEN is followed by the user-selected

DATABASE1 constant UPDATE and the variable DATABASE1.
854 8600 0395-514

Example 3
<generate statement>
GENERATE Z = The GENERATE constant is followed by the variable Z, an

NULL equal sign (=), and the user-selected constant NULL.
GENERATE Z = X The GENERATE constant is followed by the variable Z, an

equal sign, and the user-selected variable X.

AND B equal sign, the user-selected variable X, the AND command
(from the list of user-selected items in the nested path),
and a third variable, B.

+B equal sign, the user-selected variable X, the plus sign (from
the list of user-selected items in the nested path), and a
third variable, B.
Example 4
<entity reference declaration>
ENTITY REFERENCE The required item ENTITY REFERENCE is followed

ADVISOR1 (INSTRUCTOR) by the variable ADVISOR1 and the variable
INSTRUCTOR. The parentheses are required.
ENTITY REFERENCE Because the diagram contains a loop, the pair of

ADVISOR1 (INSTRUCTOR), variables can be repeated any number of times.
ADVISOR2
(ASST_INSTRUCTOR)
8600 0395-514 855

Example 5
<PS MODIFY command>
PS MODIFY 11159 The constants PS and MODIFY are followed by the

variable 11159, which is a request number.
PS MODIFY Because the diagram contains a loop, the variable

11159,11160,11163 11159 can be followed by a comma, the variable
11160, another comma, and the final variable 11163.
PS MOD 1115911161 The constants PS and MODIFY are followed by the

DESTINATION = "LP7" user-selected variables 1115911161, which are
request numbers, and the user-selected variable
DESTINATION = LP7, which is a file attribute phrase.
Note that the constant MODIFY has been abbreviated
to its minimum allowable form.
PS MOD ALL The constants PS and MODIFY are followed by the

EXCEPTIONS user-selected constants ALL and EXCEPTIONS.
856 8600 0395-514

8600 0395-514 857

Index
??CD (Conditional Dump), 741 ACCOUNTING (Resource Accounting),

??CL (Clear), 743 11
??CM (Change MCP), 744 ACQUIRE (Acquire Resource), 13
??CMPAUDIT (CMP Audit), 745 active database stacks, displaying, 255
??COPY (Copy Files), 746 active jobs, displaying, 255
??DIALT (Dial Trace), 747 active mix entries, displaying, 5
??DS (Discontinue), 748 active tasks, displaying, 255
??DUMP (Dump Memory), 749 actual segment descriptor, 39
??FS (Force Schedule), 750 actual segment descriptors in use, 42
??HALT (Halt System), 751 AD (Access Duplicate), 21
??HS (Hold Schedule), 753 ADM (Automatic Display Mode), 23
??LH (Load Host), 754 AI (Automatic Initiation), 32
??MARC (Transfer to Menu-Assisted analyzing
Resource Control), 755 memory dumps, 109
??MEMDP (Dump Memory), 758 analyzing, 109
??ODT (Return from Menu-Assisted AR (Archive Release), 35
Resource Control), 759 ARCCOPY (Copy Archive Directory), 34
??OK (Reactivate), 760 ARCDUPLICATE (Duplicate Archive
??OL (Display Label and Paths), 761 Directory), 36
??PD (Print Directory), 762 archive directory
??PHL (Programmatic Halt/Load), 764 creating an offline copy, 34
??REMOVE (Remove File), 765 creating duplicate copy, 36
??RESTRICT (Restrict ODT), 766 deleting duplicate copy, 36
??RJ (remove JOBDESC File), 767 replacing, 37
??RUN (Run Code File), 768 archive directory, 36
??RV (Restart Volume Directory), 769 archive log
??SECAD (Security Administrator creating new, 35
Authorization), 770 releasing old, 35
??ST (Stop), 772 archive log, 35
??TRACE (Trace Table), 773 archiving options, 53
??UNWRAP (Unwrap Files), 774 ARCREPLACE (Replace Archive
??UR (Unit Reserved), 777 Directory), 37
??W (Waiting Mix Entries), 778 areas of a disk, clearing, 520
??ZFA (Zero Failure Analysis), 779 array size, setting, 567
ASD (Actual Segment Descriptor), 39
A (Active Mix Entries), 5 ASD table, 39
ABCDIAG system option, 656 ASD usage, 42
ACCEPT messages, 54 ASDU (ASD Usage), 42
access structure assigning serial numbers to tape
determining location, 21 volumes, 620
duplicating or removing duplicate, assigning/ starting time and date to
21 jobs in a queue, 631
access structure, 21 AT (At Remote Host), 43
8600 039-514 859

Index
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
860 8600 0395-514

Index
controlling messages, 358 deleting a duplicate copy of the

controls archive directory, 36
displaying label and path detaching disk packs from the system,
information, 401 79
controlware file, loading to disk pack detaching resources, 139, 192
controller, 274 devices
CONVENTION system option, 656 acquiring, 13
COPYCAT (Copy Catalog), 103 clearing, 75, 743
copying files without the WFL reserving for maintenance, 717, 777
compiler, 746 devices, 75
COUNTRY system option, 656 DF (Empty Dumpdisk File), 114
CPM diagnostic options, 136
acquiring, 13 dial tracing, initiating, 747
CPM, 13 DIR (Directory), 116
CPM threshold, setting, 173 directing a system command to
CQ (Clear Queue), 104 another host in the network, 43
creating a duplicate copy of the directories
archive directory, 36 expanding, 165
creating an inactive copy of the listing, 116
system catalog, 103 tape, 677
creating backup copy of flat directory, directories, 116
112 directories, disk, 113
CREDENTIALS system option, 656 directories, flat, see flat directories,
CS (Change Supervisor), 105 112
CTLs DIRECTORY ONLY, 113
acquiring, 13 DIRECTPRINTER system option, 656
CTLs, 13 discontinuing jobs and tasks, 152
CU (Core Usage), 107 discontinuing tasks, 748
CUPRATE, setting, 556 disk attributes, displaying, 595
disk cache
DA (Dump Analyzer), 109 displaying statistics, 67
DAMAGEDFILES report file, 564 disk cache, 67
DAMAGEREPORT report file, 564 disk directories, 113
data communications, initializing, 213 disk drives, displaying status, 443
data link processor, reserving, 717 disk families
data structures, displaying cache reserving for use by directories only,
values, 640 113
database stacks sharing, 588
active, 5 space usage, 156
displaying, 255 system files location, 117
displaying active, 110 disk families, 588
database stacks, 110 disk files
DATACOMINFO file, 213 open, 605
DATACOMSUPPORT library, initializing, viewing when the controller is
213 suspended, 762
date, system, 146 disk files, 605
DBS (Database Stack Entries), 110 disk fragmentation, reducing, 627
DD (Directory Duplicate), 112 disk mirroring, 312
default options after a cold-start, 825 disk packs
default queue for system, 144 loading controlware, 274, 754
default status of units, 833 purging, 456
default value for TARGET option, read error analysis, 564
setting, 98 reconfiguring, 488
8600 0395-514 861

Index
disk packs, 274 ESR system option, 656

disk resource control system, 149 exception event, causing, 201
disk subsystem, finding information executing SYSTEM/DUMPANALYZER,
about, 178 109
disks EXPAND (Expand Directory), 165
bad sectors on, 735
caching, 67 FA (File Attribute), 168
closing, 79 FACTOR, 584
detaching from system, 79 Failure Analysis, resetting error
displaying spares, 607 counters, 779
listing directories, 116 families
mirrored, 440 central directory, 171
reconfiguring, 488 deleting backup copy of flat
specifying time-out values for READs directory, 112
and WRITEs, 251 marking as usable for disk
utilization, 156 directories only, 113
variable sector size (VSS), families, 112
initializing, 242 families, disk, 117
disks, 735 famillies
displaying the halt/load unit, 202 disk space being used, 156
displays on the ODT, 680 family
DL (Disk Location), 117 creating a duplicate copy of an
DLP active archive directory, 36
acquiring, 13 creating an archive directory, 34
DLP, 13 family name, changing, 261
DN (Dump Name), 132 FAMILYACCESS (Directory Location),
DO (Diagnostic Options), 136 171
DOWN (Down Resource), 139 FAS (Failure Analysis Summary), 173
downloading microcode, 274 FETCH message, displaying, 454
DQ (Default Queue), 144 FI (File Information), 174
DR (Date Reset), 146 file access structure, rebuilding flat
DRC (Disk Resource Control), 149 directory of a family, 486
DS (Discontinue), 152 file locking time limit, setting, 177
DSA keys, 221 FILELOCKTLIMIT (File Lock Time
DU (Disk Utilization), 156 Limit), 177
DUMP (Dump Memory), 160 files
dumpdisk files, emptying, 114 assigning unlabeled files to disk, 709
DUMPDISKMASTER, 114 configuration, 198
dumps copying without using the WFL
conditional, 741 compiler, 746
memory, 132, 160, 781, 784 duplicates, removing, 538
program, 160 logging periodic information, 465
dumps, 741 nonresident, checking for, 73
duplicate files, removing, 538 open, 174
duplicating the active access structure, record-locking time limits, setting,
21 177
removing duplicates, 538
emptying dumps from dumpdisk files, removing from disk without using
114 the WFL compiler, 765
entering CANDE control commands at resident program status, 539
an ODT, 821 running code files, 768
erasing CD-RW media, 456 security restrictions, setting, 529
error counts, summary, 173 system, 117
862 8600 0395-514

Index
tape, designating final reel, 189 hardware resources, regrouping, 500

unlabeled, assigning to disk, 709 HC units/purging, 456
viewing on disk when the controller HI (Cause Exception Event), 201
is suspended, 762 HLUNIT (Specify Halt/Load Unit), 202
wrapped, 774 HOLD (Hold Unit for Operator Use),
files, 174 205
FILES (FTAM command), 43 host control units/purging, 456
final reel of unlabeled tape file, 189 host name
FIND, 178 displaying current, 207
firmware files, copying to IOP systems, establishing new, 207
270 host name, 207
flat directories Host Services requests
creating backup copy, 112 designating usercode for, 210
deleting backup copy, 112 Host Services requests, 210
flat directories, 112 host usercode, 210
FM (Form Message), 188 HOSTCCS system option, 656
following the paths of a railroad HOSTNAME (Hostname), 207
diagram, 853 HS (Hold Schedule), 209
forcing a job or task, 190 HU (Host Usercode), 210
FORMID attribute
altering, 168, 188 I/O capacity licensing information, 221
FORMID attribute, 188 I/O modules, recovering failed units,
FR (Final Reel), 189 503
FREE (Free Resource), 192 IB (Instruction Block), 212
frozen libraries ID (Initialize Data Comm), 213
displaying, 277 ignore label response, 241
thawing, 684 IK (Install Keys), 221
FS (Force Schedule), 190 IL (Ignore Label), 241
FTAM commands to use at remote host immediate halt/load, 744
CHANGE, 43 incompatible attribute messages,
LFILES, 43 responding to, 168
MODIFY, 43 independent runners
REMOVE, 43 SUMPDISKMASTER, 114
FTAM commands to use at remote independent runners, 114
host, 43 INITIALIZE (Initialize Disk), 242
function names, displaying, 611 initializing data communications, 213
initiating a checkpoint for a task, 60
GC (Group Configuration), 198 initiating dial tracing, 747
group configuration, displaying initiating programs automatically, 32
current, 198 INSTALL (Install Software), 245
installing
halt/load software from system release media,
programmatic, 764 245
system, 83 software keys, 221
halt/load, 764 installing, 245
halt/load unit, displaying or specifying, instruction block for job, displaying,
202 212
halting the system, 751 INTERVAL rate for computing system
hardware channel card replacement, utilization, setting, 556
517 introduction to Print System
hardware modules commands, 472
acquiring, 13 IOM
hardware modules, 13 acquiring, 13
8600 0395-514 863

Index
IOM, 13 LC (Log Comment), 267

IOP systems LFILES (FTAM command), 43
DOWN (Down Resource), 139 LG (Log for Mix Number), 268
UP (Up Resource), 710 LH (Load HostIOM Systems), 274
IOP systems, 139 LH (Load Host--IOP Systems), 270
IOTIMER (Specify Time-out Value), libraries
251 active, 5
connection, 277
J (Job and Task Display), 255 frozen, 277
job displays, suppressing, 642 server, 277
job information, displaying, 625 setting trace, 280
job log, entering a comment, 285 LIBS (Library Task Entries), 277
job queues LIBTRACE (Library Trace), 280
attributes, 479 LICENSESTATUS, 284
terminating jobs, 469 line printers, displaying status, 443
job queues, 479 listing diagnostic options, 136
JOBDESC file, reinitializing at next listing frozen libraries, 277
halt/load, 767 listing the directory of files on system
jobs disk or another pack, 116
active, displaying, 5 LJ (Log to Job), 285
assigning a starting date and time, LMBLOCKSIZE system option, 656
631 LMSINGLESPACE system option, 656
assigning priority, 470 loading controlware file, 274, 754
completed, displaying, 62 LOADMICROCODE (Load Microcode
discontinuing specified jobs, 152 IOM Systems), 286
instruction block for, 212 localization of numeric separator
restarting, 528 characters, 1
resuming new jobs, 209 location of system files, 117
scheduled, starting, 750 locking files, setting time limit, 177
starting jobs in a queue, 190 locking programs, 292
status, displaying, 737 LOG (Analyze Log), 288
stopping new jobs, 209 log, transferring to a new SUMLOG file,
suppressing displays, 642 686
suspending, 753 logged comments, printing, 267
terminating all jobs in a queue, 469 LOGGING (Logging Options), 289
terminating specified jobs, 152 logging information about open files,
jobs, 642 465
logging options for the system, 289
keys logging specified tasks, 268
partition processor image licenses, LONGFILENAMES system option, 656
221 loops in railroad diagrams, 850
performance licenses, 221 LP (Lock Program), 292
processor licenses, 221
run-time licenses, 722 maintenance mode for IOM systems,
software licenses, 221 717
keys, 722 mapping function names to library
code files, 611
LABEL (Label ODT), 259 marking disk units as remote disk
LABELFORMAT system option, 656 units, 505
LANGUAGE system option, 656 master control program, 83
languages, terminal display, 680 MAX (Maximums), 293
LB (Relabel Pack or Host Control Unit), MCP
261 changing, 83, 744
864 8600 0395-514

Index
displaying information about current ML (Mix Limit), 332

MCP, 729 MLI, 717
MCP, 83 MM (Memory Module), 333
MCS (Message Control System), 297 MODE (Unit Mode), 335
MDT (Memory Dump Type), 299 MODIFY (FTAM command), 43
media library monitoring programs, 483
communicating with, 569 monitoring Store Safe, 632
system commands, 569 MOVE (Move Job or Pack), 339
media library, 569 MP (Mark Program), 342
memory disk, utilization data, 703 MQ (Make or Modify Queue), 352
memory dumps MSC (Message Control), 358
analyzing, 109 MSG (Display Messages), 372
commands, 781 MSM
performing, 160, 749, 758 acquiring, 13
processing, 132, 784 MSM, 13
memory dumps, 132 MU (Make User), 375
memory dumps, 160 MX (Mix Entries), 377
memory dumps, 749
memory dumps, 758 NAMEMAP, 381
memory management parameters, NET (Network), 385
setting, 584 NETEX (Support NETEX Software), 386
memory usage, 107 network processors, displaying status,
MEMORYCEILING (Set Memory 443
Ceiling), 310 new archive log, creating, 35
message level interface, reserving, NEW SYSTEMDIRECTORY (Replace an
717 Existing SYSTEMDIRECTORY), 388
message responses NF (No File), 392
BADFILE, 56 NODATEOFFSET system option, 656
message responses, 56 nonfatal memory dumps, 749
messages nonresident files, checking for, 73
ACCEPT, 54 NOTOK (Do Not Reactivate), 393
communicating with NPSUPPORT NPSUPPORT library, communicating
library and media library, 569 with, 569
controlling, 297 NS (Next Screen), 394
displaying, 372 numeric separator characters, 1
forms, 188 NW (Network Prefix), 395
incompatible attributes, 168 NX (NETEX Software Input), 396
responses, 241
sending from ODT to data comm O (Overlay), 397
station, 629 ODT
system, clearing from queue, 104 as remote terminal, 680
messages, 54 attaching a file name, 259
messages, 629 conventions for dates and times, 680
microcode, loading, 274, 286 displays, 680
MIRROR (Mirror Disk), 312 entering CANDE control commands,
MIRROR_CREATE, 312 821
mirrored disks, 440, 488 restricting, 529, 766
mix starting WFL jobs, 823
attributes, 595 ODT, 766
current limit, 332 ODT, 821
finding information about, 178, 377 OF (Optional File), 399
scheduled entries, 550 OK (Reactivate), 400
mix entries, active, 5 OL (Display Label and Paths), 401
8600 0395-514 865

Index
OLAYCHANGE, 584 PERMDIRECTORIES system option,

OLAYGOAL, 584 656
OLAYSATURATION, 584 PF (Print Fetch), 454
old archive log, releasing, 35 PG (Purge), 456
OP (Options), 422 PLI (Periodic Logging Interval), 465
open disk files, displaying, 605 PMIX (Process Mix), 466
open files POWER (Power Up/DownVM Systems
logging periodic information, 465 Only), 467
obtaining general information, 174 PQ (Purge Queue), 469
open files, 174 PR (Priority), 470
operator display terminal, 766, 821 primitive commands
OPLOCKTIMEOUT, 434 ??CD (Conditional Dump), 741
options ??CL (Clear), 743
CONTROLLER, 94 ??CM (Change MCP), 744
diagnostic, 136 ??CMPAUDIT (CMP Audit), 745
operating system, 422, 656 ??COPY (Copy Files), 746
options, 422 ??DIALT (Dial Trace), 747
OT (Inspect Stack Cell), 436 ??DS (Discontinue), 748
overlay factors, setting, 584 ??DUMP (Dump Memory), 749
overlay row size, displaying, 567 ??FS (Force Schedule), 750
overlay utilization statistics, 397 ??HALT (Halt System), 751
owner of pack, changing name, 261 ??HS (Hold Schedule), 753
??LH (Load Host), 754
packs ??MARC (Transfer to Menu-Assisted
closing, 79 Resource Control), 755
detaching from system, 79 ??MEMDUMP (Dump Memory), 758
listing a directory, 116 ??ODT (Return from Menu-Assisted
read error analysis, 564 Resource Control), 759
replacing a volume, 509 ??OK (Reactivate), 760
page size for paged arrays, displaying, ??OL (Display Label and Paths), 761
567 ??PD (Print Directory), 762
paged arrays, displaying, 567 ??PHL (Primitive Halt/Load), 764
PARTIALSETS, 440 ??REMOVE (Remove File), 765
partition processor image licenses, 221 ??RESTRICT (Restrict ODT), 766
paths in railroad diagrams, 848 ??RJ (Remove JOBDESC File), 767
PB (Print Backup), 441 ??RUN (Run Code File), 768
PDIR (Process Directory), 442 ??RV (Restart Volume Directory),
PER (Peripheral Status), 443 769
percent signs in railroad diagrams, 850 ??SECAD (Security Administrator
performance keys, 221 Authorization), 770
peripheral devices, see peripheral ??ST (Stop), 772
units, 761 ??TRACE (Trace Table), 773
peripheral status, displaying, 443 ??UNWRAP (Unwrap Files), 774
peripheral units ??UR (Unit Reserved), 777
clearing, 75 ??W (Waiting Mix Entries), 778
clearing exception flags, 743 ??ZFA (Zero Failure Analysis), 779
displaying label and path PRIMITIVE RUN, 471
information, 401 Print System
displaying labels and paths, 761 introduction, 472
reserving (IOM systems), 717 Print System, 472
setting security restrictions, 529 printing logged comments, 267
peripheral units, 75 printing/backup tape files, 441
processor license keys, 221
866 8600 0395-514

Index
program initiation, automatic, 32 RECONFIGURE (Reconfigure System),

programmatic halt/load, 764 500
programs record-locking time limit, setting, 177
displaying name, 737 RECOVER (Recover I/O Module), 503
dumping, 160, 749 recovering failed I/0 modules, 503
locking, 292 reducing disk fragmentation, 627
monitoring by MCP, 483 regrouping hardware resources, 500
programs, 160 relabeling the disk pack, 261
purging disk packs, 456 relabeling the host control unit, 261
purging host control units, 456 reliability factor on IOM systems,
purging jobs in a queue, 469 displaying, 536
purging tapes, 456 Reliable Session Service (RSS), 541
PV (Print Volume), 477 remote disk units, marking, 505
remote hosts, directing system
QF (Queue Factors), 479 commands to, 43
QT (Quit), 481 remote ODT, activating, 506
QUEUEDAX system option, 656 remote terminal, ODT as, 680
queues REMOTEDISK, 505
clearing, 104 REMOTESPO (Activate REMOTESPO),
default, 144 506
displaying attribute values, 479 REMOVE (FTAM command), 43
displaying job information, 625 removing a duplicate access structure,
purging, 469 21
removing a file without using the WFL
RA (Register Application), 483 compiler, 765
railroad diagram/paths, 853 removing duplicate files, 538
railroad diagrams REPLACE (Replace Pack Volume), 509
basic constructs, 835 REPLACECARD (Replace Card), 517
bridges, 850 replacing
constants and variables, 849 archive directory with backup
constraints, 850 archive directory, 37
examples with sample input, 854 replacing a pack volume, 509
explanation, 847 replacing hardware channel cards, 517
following paths, 853 replacing/, 517
loops, 850 required items in railroad diagrams,
percent signs, 850 850
required items, 850 RES (Reserve), 520
right arrows, 850 reserving a family member for use by
user-selected items, 850 directories only, 113
vertical bars, 850 reserving units for maintenance (IOM
railroad diagrams, 847 systems), 717
RB (Rebuild Access), 486 resetting error counters for Failure
RC (Reconfigure Disk), 488 Analysis, 779
RCBP system option, 656 resetting the system date, 146
reactivating suspended tasks, 400, resident programs, displaying and
760 marking, 539
read error analysis of disk packs, 564 resource accounting, 11
readying devices, 547 resources
readying inaccessible or locked acquiring, 13
devices, 547 detaching, 139, 192
rebuilding file access structure of the freeing, 192
falt directory of a family, 486 resources, 13
resources, 139
8600 0395-514 867

Index
resources, 192 on commands, 529, 651

RESTART (Restart Jobs), 528 on files, 529
restricting command usage, 651 on peripherals, 529
restricting tape units for operator use, on the system, 566
205 on volumes, 529, 701
resuming new jobs or tasks, 209 security restrictions, 529
rewinding tapes, 546 SEGARRAYSTART (Array Segmentation
RF (Reliability Factor) on IOM systems, Start Size), 567
536 SEND (Send Message), 569
right arrows in railroad diagrams, 850 sending a control command to an MCS
RM (Remove), 538 or a database, 618
RP (Resident Program), 539 sending message from ODT to data
RSS (Reliable Session Service Prefix), comm stations, 629
541 serial numbers, assigning to tape
RSS systems, directing commands to, volumes, 620
541 server libraries, 277
RSVP condition SF (Set Factor), 584
responses for incompatible SHARE (Shared Family), 588
attributes, 168 sharing disk families, 588
RSVPONTAPEERROR system option, SHOW, 595
656 SHOWOPEN (Show Open Disk Files),
running code files as independent 605
processes, 768 SHOWSPARES (Show Spare Disks),
RW (Rewind), 546 607
RY (Ready), 547 SI (System Intrinsics), 609
SL (Support Library), 611
S (Scheduled Mix Entries), 550 SLICERATE, setting, 556
SB (Substitute Backup), 554 SM (Send to MCS or Database), 618
SBP (System Balancing Parameters), SN (Serial Number), 620
556 software
SC (System Configuration), 558 installing from system release
SCAN (Scan Pack Volume), 564 media, 245
scheduled jobs keys, installing, 221
displaying, 550 licenses, displaying information, 284
resuming, 209, 753 software, 245
starting, 190, 750 software licenses, displalying
scheduled jobs, 550 information, 284
scheduled mix entries, displaying, 550 spare disks, displaying, 607
scheduled tasks specifying programs that are to be
displaying, 550 automatically initiated, 32
resuming, 209, 753 specifying the halt/load unit, 202
starting, 190, 750 specifying values for disk READs and
scheduled tasks, 550 WRITEs, 251
SECOPT (Security Options), 566 SQ (Show Queue), 625
sectors SQUASH (Consolidate Disk Allocation),
available, 156 627
damaged, 564 SS (Send to Station), 629
in use, 156 stack cell, displaying properties, 436
sectors, 156 stack entries, database, 110
SECTORSINERROR report file, 564 stack state, displaying, 737
security administrator /authorizing, starting jobs or tasks, 753
770 starting scheduled jobs or tasks, 750
security restrictions starting SYSTEM/LOGANALIZER, 288
868 8600 0395-514

Index
STARTTIME (Start Time), 631 releasing old, 35

statistics system archive log, 35
overlay utilization, 397 system catalog
utilization, 703 creating an inactive disk copy, 103
statistics, 703 system catalog, 103
status system commands
compiler, 102 directing to another host in the
jobs or tasks, 737 network, 43
status, 737 system files location, 117
stopping new jobs or tasks, 209 system log file, entering comments,
stopping the system, 741 267
Store Safe, configuring and system log, entering a comment, 285
monitoring, 632 system software, installing, 245
STORESAFE, 632 system status information, automatic
STRUCTURECACHE (Cache display, 23
Maintenance), 640 SYSTEM/ACCESS file, moving, 171
substituting backup media, 554 SYSTEM/CATALOGING file, moving,
SUMLOG, entering a comment, 285 171
summary of recent error counts, 173 SYSTEM/DSAKEYSFILE, 221
supervisor programs, 105 SYSTEM/DUMPANALYZER, executing,
SUPPRESS (Suppress Display), 642 109
SUPPRESSACTIVE system option, 656 SYSTEM/FILEDATA, invoking, 677
SUPPRESSWARNING (Suppress SYSTEM/KEYSFILE, 221
Warning), 644 SYSTEM/LOGANALYZER, starting, 288
suspended tasks, reactivating, 400 SYSTEM/SUMLOG, adding comments,
suspending new jobs or tasks, 753 267
suspending tasks, 772 SYSTEMDIRECTORY
SV (Save), 646 system option, 656
SW (Switches), 649 SYSTEMDIRECTORY, 656
SW task attributes, setting, 649
SYSADMIN COMMAND, 651 tape drives, displaying status, 443
SYSOPS (System Options), 656 tape files
system designating the final reel of an
balancing parameters, 556 unlabeled file, 189
configuring, 558 printing backup tape files, 441
date, resetting, 146 tape files, 189
default queue, 144 tape subsystem, finding information
disk, listing directory, 116 about, 178
dumps, 773 tape units
intrinsics, 609 restricting for operator use, 205
keys, installing, 221 tape units, 205
log, 686 tape units, unloading, 546
logging options, 289 tape volumes, assigning serial
memory dumps to disk, 132 numbers, 620
messages, clearing from queue, 104 TAPEEXPIRATION system option, 656
options, 422, 656 TAPEMANAGER system option, 656
pack, listing directory, 116 TAPEOVERWRITE system option, 656
utilization, 556, 703 tapes
variables, 293 assigning density, 620
system administrator, commands assigning serial numbers, 620
restricted to, 651 displaying attributes, 595, 701
system archive log purging, 456
creating new, 35 rewinding, 546
8600 0395-514 869

Index
tapes, 456 default status, 833

TAPESERVER system option, 656 reserving for maintenance (IOM
tasks systems), 717
active, displaying, 5 unlabeled files, 709
assigning unlabeled file to, 709 unloading tape units and CD-ROM
completed, displaying, 62 drives, 546
discontinuing, 152, 748 UR (Unit Reserved), 717
display suppression, 642 usercodes
initiating a checkpoint, 60 creating, 375
logging specified tasks, 268 for DSS Host Service requests, 210
reactivating suspended tasks, 400, usercodes, 210
760 user-selected items in railroad
resuming new tasks, 209, 753 diagrams, 850
scheduled, displaying, 550 utilization statistics, 703
starting new tasks, 753
starting tasks in the schedule mix, variable sector size disks, 520
190 variables in railroad diagrams, 849
status, displaying, 737 vertical bars in railroad diagrams, 850
stopping new tasks, 209, 753 viewing files on disk when the
suppressing display, 642 controller is suspended, 762
suspended, displaying, 726, 778 volume directory
suspended, reactivating, 760 restarting new directory, 769
suspending, 630, 753 volume labels, creating new set, 488
terminating, 152, 748 volume library, displaying information,
time accumulators, 685 477
waiting, 726 volume serial number, changing, 261
tasks, 642 volumes, setting security restrictions,
terminating jobs and tasks, 152 529
terminating the printing of a backup VSS disks
file, 481 clearing, 520
time accumulators, displaying, 685 initializing, 242
time interval for computing system migrating, 174
utilization, 556 replacing, 509
time-out values for Client Access VSS disks, 520
Services, 434
timeout values for disk READ and WARNFACTOR system option, 656
WRITE activities, 251 warning messages to be suppressed,
TOO MANY NUMBERS error, 1 displaying or modifying list, 644
trace entries, recording, 741 WFL jobs, starting at an ODT, 823
trace table, 773 WLFPERIODS system option, 656
trace, setting for libraries, 280 Work Flow Language (WFL), 70
TSP Work Flow Language (WFL) jobs,
acquiring, 13 starting an an ODT, 823
TSP, 13 Work Flow Languge (WFL)
submiting with CC command, 70
UDCHAINLENGTH system option, 656 WRAPNOWAIT system option, 656
unit and mix number ranges, 1 wrapped files
units unwrapping, 774
clearing, 75, 743 wrapped files, 774
870 8600 0395-514

.
*86000395-514*
86000395-514

Unisys MCP Commands 86000395-514

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Unisys MCP Commands 86000395-514

Caricato da

Copyright:

Formati disponibili

ClearPath Enterprise

ClearPath MCP Release 11.0 or Later

2006 Unisys Corporation.

ClearPath MCP Release 11.0 or Later

COMPILERTARGET (Set Default Target Value) ..................... 98

ID (Initialize Data Comm) ...............................................213

8600 0395-514 iii

NS (Next Screen) ...........................................................394

RSS (Reliable Session Service Prefix)................................541

Section 2 Memory Dump Processing and

Appendix A Functional Command Groupings

Appendix B Using CANDE and WFL at an ODT

Appendix C Cold-Start Default Values

8600 0395-514 vii

Appendix D Basic Constructs

Appendix E Understanding Railroad Diagrams

Index ........................................................ 859

viii 8600 0395-514

System Commands Overview

This document provides complete descriptions of all system commands. It presents

Unit and Mix Number Ranges

Network Support Processors (NSPs)

Sources for Entering System Commands

Operator display terminals (ODTs).

Operations Center. This utility provides a graphical interface to selected system

Menu-Assisted Resource Control (MARC). For further information, refer to the

The DCKEYIN function in a privileged Data Communications ALGOL (DCALGOL)

Using CANDE and WFL at an ODT

CANDE Control Commands

Work Flow Language (WFL)

System Command Descriptions

A brief description of the functions of the command.

A syntax diagram outlining the various options of the command.

An explanation of each option of the command.

The command descriptions are presented in alphabetical order according to the

Learning Which Commands to Use

TERM Convention Numeric Separator Example

BELGIUM (.) Period 1.234.567

NORWAY ( ) Blank 1 234 567

SWITZERLAND (') Prime 1'234'567

JORDAN No Separator 1234567

ASERIESNATIVE (,) Comma 1,234,567

The following system commands are affected by internationalization:

ASD (Actual Segment Descriptor)

ASDU (ASD Usage for specified mix numbers)

OL (Display label and path information of a unit)

OT (Show Stack Cell- decimal values only)

PD (and PDRES single instance only)

SHOWOPEN (Show the open files of a disk family)

TI (Times - operations counts only)

For more information, refer to the MultiLingual System Administration, Operations,

A (Active Mix Entries)

The first delimiter must be the same as the second delimiter.

Equal sign (=) Matches any sequence of characters

Question mark (?) Matches any single character

Tilde (~) Matches any sequence of characters except a slash (/)

The wild-card string is automatically uppercased, except for characters enclosed in

A NAME LIT ^=pack=^

A NAME <wild-card string>

A MCSNAME = <MCS name>

A QUEUE <queue number>

---Mix-Pri--CPU Time------------ 93 ACTIVE ENTRIES -----------------

The Pri field shows the priority of the job or task.