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. For an explanation of how to read these, refer to “Understanding Railroad Diagrams.”

Arithmetic Operators

The following symbols are the standard arithmetic operators used in this document.

Arithmetic Operator

Meaning

+

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 several interfaces, including:

  • 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:

System Command Descriptions

Each of the system command descriptions in this manual includes the following information:

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

  • Examples of various forms of the command and possible responses from the system. The system responses are indented to distinguish them from the commands.

  • Any restrictions or differences dependent on the system type, if applicable.

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.

Using Primitive Commands

Primitive commands are processed directly by the MCP, bypassing the ordinary system command handler. Therefore, they can be entered even when a software failure in the CONTROLLER makes it impossible to enter ordinary system commands. All primitive commands must begin with two question marks (??).

Several primitive commands are described as applying to all ordinary tasks. In this context, an ordinary task is a visible job or task that is not a message control system (MCS), a permanent frozen library, or privileged.

Periods in File Titles

Unlike WFL, when using a a file title that includes a period in a system command, you must enclose the node that contains the period in quotation marks.

For example:

  • In WFL, you enter the following command

    COPY README.TXT
  • However, to use the PD system command with the same file name, you enter

    PD “README.TXT”

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

The following ODT 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 ClearPath Enterprise Servers MultiLingual System Administration, Operations, and Programming Guide and the TERM (Terminal) command.