NOS_2_Analysis_Handbook_Ref_60459300M_Dec88_Part_1 NOS 2 Analysis Handbook Ref 60459300M Dec88 Part 1

NOS_2_Analysis_Handbook_Ref_60459300M_Dec88_Part_1 NOS_2_Analysis_Handbook_Ref_60459300M_Dec88_Part_1

User Manual: Pdf NOS_2_Analysis_Handbook_Ref_60459300M_Dec88_Part_1

Open the PDF directly: View PDF .
Page Count: 1000

Download
Open PDF In Browser	View PDF

NOS Version 2
Analysis Handbook

Reference
yams

This product is intended for use only as
described in this document Control Data
cannot be responsible for the proper
functioning of undescribed features and
parameters.

Publication Number 60459300

Manual History
Revision

System
Version

PSR
Level

Date

2.0

562.

April 1982

2.1

580.

January 1983

2.2

596.

October 1983

2.3

617.

October 1984

2.4.1

630.

March 1985

2.4.2

642.

October 1985

2.5.1

664.

September 1986

2.5.1

670.

December 1986

2.5.2

678.

April 1987

2.5.3

688.

September 1987

2.6.1

700.

April 1988

2.7.1

716.

December 1988

Revision M of this manual, printed December 1988, reflects NOS 2.7.1 at PSR level
716. This edition obsoletes all previous editions. It documents the following:
• Addition of Job Scheduler enhancements containing pseudo-control points; revisions
to IPRDECK entries and DSD commands (SERVICE and DELAY); and new features
including IPRDECK entries (TRACE and FLEXIBLE PARTITIONS), DSD commands
(ENPR and FLEXIBLE PARTITIONS), DIS command (,), and CMR dump directives
(MCT, PCP, and TBDUMP).
• Support of the 9853 Disk Storage Subsystem, the CC598 console, and the 960 and
994 Computer Systems.
• Changes to the TRACER and PROBE utilities.
• Addition of new DSD debugging commands (TRACE and TRAP).
• Addition of EQPDECK entries (UP and DOWN) and a IPRDECK entry
(HARDWARE FAULT INJECTION).
Miscellaneous editorial and technical corrections are made. Technical changes in this
manual are indicated by bars in the margins.

©1982, 1983, 1984, 1985, 1986, 1987, 1988 by Control Data Corporation
All rights reserved.
Printed in the United States of America.

2 NOS Version 2 Analysis Handbook

/^^S

Revision M

Contents
About

This

Manual

Audience
Organization
Conventions
Related Publications
Submitting Comments
CYBER Software Support
Hotline
Disclaimer
Controlware

Utilities

11
11
11
12
13
20
20
20
1-1

Loading Controlware 1-1
Dumping Controlware 1-4
Deadstart

'..

2-1

Modifying the CMRDECK 2-3
Modifying the EQPDECK 2-4
Modifying the APRDECKs 2-22
Modifying the IPRDECK 2-23
Loading the System 2-24
Initiating Job Processing 2-26
Preparing for Recovery Deadstart 2-28
Level 0 Initial Deadstart 2-36
Error
Processing
2-36
Deadstart

Decks

CMRDECK
EQPDECK
APRDECK
IPRDECK
LIBDECK
DIS

Operations

3-1
3-2
3-13
3-103
3-107
3-159
4-1

DIS Job Dayfile Display (A) 4-3
DIS Job Status Display (B) 4-4
DIS Memory Displays (C, D, F,
G)
4-6
DIS Exchange Package Display
(X)
4-8
DIS Directory Display (Z) 4-9
Console Operation 4-10
Display Selection Commands 4-13
DIS Keyboard Entries 4-14

Revision M

Memory Entry Commands 4-18
PP Call Commands 4-20
DSD

Commands

5-1

Display Selection Commands 5-2
D a y fi l e
Commands
5-3
Queued File Utility Commands ... 5-4
Job Processing Control
Commands
5-4
Peripheral Equipment Control
Commands
5-24
Subsystem Control Commands 5-50
System Control Commands 5-56
Secured System Control
Commands
5-70
Memory Entry Commands 5-72
Channel Control Commands 5-74
Extended Memory Flag Register
Commands
5-75
Breakpoint Package Commands .. 5-75
Debugging Commands 5-84
Express Deadstart Dump
Interpreter
(DSDI)

6-1

Calling the Express Deadstart
Dump
Interpreter.
6-3
Input
Directives
6-6
Interactive Use of DSDI 6-55
Printer Output Listing Examples . 6-65
Install
K-Display

Command
Utilities

7-1
8-1

FLAW
K
Display
8-3
INITIALIZE K Display 8-8
Machine Recovery (MREC)
Utility K Display 8-16
MREC
Procedures
8-17
MREC Unit and Controller
Reservations
8-23
Mass Storage Extended
Subsystem (MSE) K Display 8-25
Network Access Method (NAM)
K
D i s p l a y.
8-27
Queue File Transfer Facility
(QTF)
K
Display
8-41

Contents 3

REDEFINE K Display 8-61
Remote Batch Facility (RBF) K
Display
8-72
Remote Host Facility (RHF) K
Display
8-75
SCOPE 2 Station Facility (SSF)
K
Displays
8-85
File Transfer Limit Commands ... 8-87
Transaction Facility (TAF) K
Displays
8-89
L-Display

Utilities

9-1

FOTD
L
Display
9-2
LIDOU
L
Display
9-3
Q D S P L AY L D i s p l a y 9 - 6
SCTD
L
Display
9-10
S D S P L AY L D i s p l a y 9 - 1 2
SUBSYST L Display 9-20
LID/RHF Configuration Files 10-1
L I D C o n fi g u r a t i o n F i l e 1 0 - 1
R H F C o n fi g u r a t i o n F i l e s 1 0 - 9
QTF Configuration Requirements 10-23
Mass Storage Extended
Subsystem
(MSE).

11 - 1

Introduction
11 - 1
MSE
Utilities
11 - 1 3
MSE Operational Procedures 11-78
Ta p e A l t e r n a t e S t o r a g e 1 2 - 1
Introduction
MAGNET Command
GENPFD
Utility

12-1
12-8
12-9

Multimainframe Operations 13-1
Introduction
13-1
Linked SDM Operation 13-2
Independent SDM Operation 13-10
NAD Maintenance Utilities 14-1
Dump NAD Memory (DMPNAD) . 14-1
Maintenance Host Facility
(MHF)
14-3
Listing NAD Dumps 14-3

Network

Operations

15-1

Network Organization 15-1
NAM
Startup
15-5
NAM
Shutdown
15-8
Network Control by HOP 15-9
Network Control by NOP 15-21
Network Control by DOP 15-43
Recent HISTORY Command 15-52
Report Unsolicited Status
Command
15-53
Send Message Command 15-54
Status Network Element
Command
15-55
Summary of Network Operation
Commands
15-59
,(K

About This Manual
This manual describes the CONTROL DATA® Network Operating System (NOS)
Version 2. NOS 2 operates on the following computer systems:
• CDC® CYBER 180 Computer Systems Models 810, 830, 835, 840, 845, 850, 855,
860, 870, 960, 990, 994, and 995
• CDC CYBER 170 Computer Systems Models 171, 172, 173, 174, 175, 176, 720, 730,
740, 750, 760, 815, 825, 835, 845, 855, 865, and 875
• CDC CYBER 70 Computer Systems Models 71, 72, 73, and 74
• CDC 6000 Computer Systems

Audience
This manual assumes you are a site analyst. It assumes you are familiar with the
hardware of your computer system(s) and that you understand the functions of the
various components of NOS.

Organization
This manual includes information required for the day-to-day maintenance of the
operating system and for troubleshooting. Topics discussed include the mass storage
subsystems, network operations, the K and L utilities, backing up and reloading files,
deadstart, and DIS operations.

Since the sections of the manual are self-contained in that they do not build on each
other, the sections are ordered alphabetically by title. The appendixes include character
set tables; a glossary; and descriptions of the SCOPE 2 Station Facility, the
status/control register simulator, programmable format control for 580 printers, disk
pack reformatting for 881/883 units, address formats for NOS/VE, management of
storage media defects, and the display disk file utility.

0m\

Revision

About

This

Manual

Conventions
The following conventions are used in this manual:
examples Examples of user entries and computer responses are shown in a
font that resembles computer output.
lowercase In a format, lowercase letters represent values you choose.
Numbers All numbers are decimal unless otherwise noted.
UPPERCASE In a format, uppercase letters represent reserved words defined by
the system for specific purposes. You must use these words exactly
as shown.
Vertical bar A vertical bar in the margin indicates a technical change.
The CDC 18002-2 console is available as an option for CYBER 180 Models 810 and 830
Systems using NOS 2.3, PSR level 617 or later operating systems. This product -^
includes a CDC 634B display terminal (also known as the 721-21 display terminal) and )
an AV117A cable. This console is referred to throughout the manual as the CC634B.
The CDC 19003 console is available as an option for certain CYBER 180-class
machines. This product includes a video monitor; keyboard; 40-Mbyte hard disk
(Winchester) drive; 1.2-Mbyte, 5-1/2-in floppy disk drive; 640-Kbyte RAM memory; one
parallel printer port; and nine RS-232-C serial ports. This console is referred to
throughout this manual as the CC598B console.
Models 815, 825, 835, 845, and 855 of the CYBER 170 Computer Systems share many **\
of the functional and architectural attributes of the CYBER 180 Computer Systems.
This manual uses the term CYBER 180-class machines when describing these similar
models collectively.
Extended memory for models 865 and 875 and CYBER 180-class machines is unified
extended memory (UEM) and may also include either extended core storage (ECS),
extended semiconductor memory (ESM), or STORNET. Extended memory for model 176
is large central memory extended (LCME) and may also include ECS, ESM, or
STORNET. Extended memory for all other NOS computer systems is either ECS, ESM,
or
S T O R N E T.
In this manual, ECS refers to both ECS, ESM, and STORNET; and extended memory
refers to all forms of extended memory unless otherwise noted. However, when
referencing extended memory in the context of a linked shared device multimainframe
complex or distributive data path (DDP) access, UEM and LCME are excluded. ECS,
ESM, and STORNET are the only forms of extended memory that can be shared in a
linked shared device multimainframe complex and can be accessed by a DDP.
(Manuals dealing with the various form of extended memory are listed, under Related
Publications.)

NOS

Version

Analysis

Handbook

Revision

Related Publications
AU of the following manuals are available through Control Data sales offices or
through:
Control Data
Technology and Distribution Services
308 North Dale Street
St. Paul, MN 55103
The reader should be thoroughly familiar with the material in the following NOS
publications.
Manual
NOS

Publication
Number

Title

Version

Operations

Handbook

60459310

NOS Version 2 Reference Set, Volume 2, Guide to System Usage 60459670
NOS Version 2 Reference Set, Volume 3, System Commands 60459680
The following lists contain manuals that provide additional information about NOS and
its product set. For the reader's convenience, these are grouped according to topic:
CDCNET manuals, hardware manuals, NOS 2 manuals, and optional product manuals.
In addition, the NOS System Information manual contains brief descriptions of all NOS
operating system and NOS product set manuals. It is accessed by logging into NOS and
entering the EXPLAIN command.

0$ms

0^S.

Revision

About

This

Manual

CDCNET Manuals
The following list contains manuals that describe the Control Data Distributed
Communications Network (CDCNET).
Manual Title

Publication
Number

CDCNET Batch Device User Guide

60463863

CDCNET Conceptual Overview

60461540

CDCNET Configuration and Site Administration

60461550

CDCNET DI Installation and Checkout

60460580

CDCNET Network Analysis

60451590

CDCNET Network Operations

60461520

CDCNET Network Performance Analyzer

60461510

CDCNET Systems Programmer's Reference Manual, Volume 1
Base System Software

60462410

CDCNET Systems Programmer's Reference Manual, Volume 2
Network MEs and Layer Interfaces

60462420

CDCNET Systems Programmer's Reference Manual, Volume 3
Network Protocols

60462430

CDCNET Terminal Interface Usage

60463850

14 NOS Version 2 Analysis Handbook

Revision M

y^^SK

Extended Memory Manuals
Programming information for the various forms of extended memory can be found in
the COMPASS Version 3 Reference Manual (publication number 60492600) and in the
appropriate computer system hardware reference manual. Hardware descriptions of the
various forms of extended memory can be found in the following manuals.
Manual

Publication
Number

Title

CYBER 5380-100 STORNET Subsystem (SNSS) 60000188
Hardware Reference
Extended

Core

Storage

Reference

Manual

60347100

Extended Core Storage II and Distributive Data Path 60430000
Reference Manual
Extended Semiconductor Memory Hardware Reference Manual 60455990

0ims

0$ms.

Revision

About

This

Manual

^/■S<§\

Hardware Manuals
The following list contains manuals that describe Control Data computer systems and
related equipment.
Publication
Number

Manual Title

CYBER 70 Model 71 Computer System Hardware Reference Manual 60453300
CYBER 70 Model 72 Computer System Hardware Reference Manual 60347000
CYBER 170 Computer Systems Models 171 through 175 60420000
(Levels A, B, C) Model 176 (Level A, B, C)
Hardware Reference Manual
CYBER 170 Computer Systems Models 720, 730, 740, 750, and 760 60456100
Model 176 (Level B/C)
Hardware Reference Manual
CYBER 170 Computer Systems Models 815 and 825 60469350
Hardware Reference Manual
CYBER 170 Computer Systems Models 835, 845, and 855
CYBER 180 Computer Systems
Models 835, 840, 845, 850, 855, 860, and 990
CYBER 990E, 994, and 995E Computer Systems CYBER 170 State
Hardware
Reference
Manual

60469290

CYBER 170 Computer Systems Models 835, 845, and 855 60458390
CYBER 180 Computer Systems Models 835, 845, and 855
Hardware Operator's Guide
CYBER 170 Computer Systems Models 865 and 875 60458920
Hardware Reference Manual
CYBER 180 Models 810 and 830 Computer Systems 60469440
Hardware Operator's Guide
CYBER 180 Models 810 and 830 Computer Systems 60469420
Hardware Reference Manual
CYBER 840A, 850A, 860A, and 870A Computer Systems 60463560
Hardware Reference Manual
5870

Printer

User's

Reference

CYBER
960
Computer
CYBER 170 State
Hardware Reference Manual

Manual

Systems

60462720
60000127

19003 System Console CC598-A/B Operations and 60463610
Maintenance Guide
380-170 Network Access Device Hardware Reference Manual 60458500

>S3SN

16 NOS Version 2 Analysis Handbook

Revision M

NOS 2 Manuals
The following list contains NOS 2 manuals.

Manual Title

Publication
Number

COMPASS Version 3 Reference Manual

60492600

CYBER Initialization Package (CIP) Reference Manual

60457180

CYBER Loader Version 1 Reference Manual

60429800

CYBER Record Manager Advanced Access Methods Version 2
Reference Manual

60499300

CYBER Record Manager Basic Access Methods Version 1.5
Reference Manual

60495700

Modify Version 1 Reference Manual

60450100

Modify Instant

60450200

NOS Online Maintenance Software Reference Manual

60454200

NOS Version 2 Administration Handbook

60459840

NOS Version 2 Applications Programmer's Instant

60459360

NOS Version 2 Diagnostic Index

60459390

NOS Version 2 Installation Handbook

60459320

NOS Version 2 Reference Set, Volume 1
Introduction to Interactive Usage

60459660

NOS Version 2 Reference Set, Volume 4
Program Interface

60459690

NOS Version 2 Security Administrator's Handbook

60460410

NOS Version 2 System Overview

60459270

NOS Version 2 Systems Programmer's Instant

60459370

Revision M

About This Manual 17

>fi5^

Optional Product Manuals
The following list contains manuals that describe optional products.
Manual

Publication
Number

Title

Binary Maintenance Log (BML) Message Formats 60459940
COBOL

Version

Reference

Manual

60497100

Communications Control Program Version 3 Diagnostic Handbook 60471500
CYBER Cross System Version 1 Build Utilities Reference Manual 60471200
CYBER Supermini Operations User's Guide 60459850
F O RT R A N E x t e n d e d Ve r s i o n 4 R e f e r e n c e M a n u a l 6 0 4 9 7 8 0 0
FORTRAN

Version

Reference

Manual

60481300

M e s s a g e C o n t r o l S y s t e m Ve r s i o n 1 R e f e r e n c e M a n u a l 6 0 4 8 0 3 0 0
MSSI

Version

Reference

Manual

60458820

Network Access Method Version 1/Communications Control Program 60480600
Version 3 Terminal Interfaces Reference Manual
Network Access Method Version 1 Host Application Programming 60499500
Reference Manual
Network Access Method Version 1 Network Definition Language 60480000
Reference Manual
N O S Ve r s i o n 2 F u l l S c r e e n E d i t o r U s e r ' s G u i d e 6 0 4 6 0 4 2 0
N O S Ve r s i o n 2 S c r e e n F o r m a t t i n g R e f e r e n c e M a n u a l 6 0 4 6 0 4 3 0
N O S V e r s i o n 2 Ta p e M a n a g e m e n t S y s t e m ( T M S ) 6 0 4 6 3 3 5 0
Site Operations Manual
N O S V e r s i o n 2 Ta p e M a n a g e m e n t S y s t e m ( T M S ) 6 0 4 6 3 1 1 0
User Reference Manual
NOS/VE System Analyst Reference
System Performance and Maintenance Manual

Set

60463915

R e m o t e B a t c h F a c i l i t y Ve r s i o n 1 R e f e r e n c e M a n u a l 6 0 4 9 9 6 0 0
Remote Host Facility Access Method Reference Manual 60459990
Remote

Host

Facility

Usage

60460620

><^^y

18 NOS Version 2 Analysis Handbook

Revision M

yams

Manual
SCOPE
TA F

Publication
Number

Title
Version
Version

TA F

Version

2.1
1

Operator's

Reference
1

User's

Guide

60455090

Manual

60459500

Guide

60459520

TA F / C R M D a t a M a n a g e r Ve r s i o n 1 R e f e r e n c e M a n u a l 6 0 4 5 9 5 1 0
Update

Version

Reference

Manual

60449900

j0m\.

Revision

About

This

Manual

Submitting Comments
The last page of this manual is a comment sheet. Please use it to give your opinion on
the manual's usability, to suggest specific improvements, and to report any errors. If
the comment sheet has already been used, you can mail your comments to:
Control Data
Technology and Publications Division, ARH219
4201 Lexington Avenue North
St. Paul, MN 55126-6198
Additionally, if you have access to SOLVER, an online facility for reporting problems,
you can use it to submit comments about the manual. Use NS2 as the product
identifier. Include the name and publication number of the manual.
Address questions about the physical packaging and/or distribution of printed manuals
to Literature and Distribution Services at the following address:
Control
Technology and Publications Services
308 North Dale Street
St. Paul, Minnesota 55103

Data

or you can call (612) 292-2101. If you are a Control Data employee, call (612)
292-2100.

CYBER Software Support Hotline
Control Data's CYBER Software Support maintains a hotline to assist you if you have
trouble using our products. If you need help beyond that provided in the documentation
or find that the product does not perform as described, call one of the following
numbers and a support analyst will work with you.
From the USA and Canada: (800) 345-9903
From other countries: (612) 851-4131

Disclaimer
NOS and its product set are intended to be used only as described in this document.
Control Data cannot be responsible for the proper functioning of undescribed features or
parameters.

NOS

Version

Analysis

Handbook

Revision

Controlware Utilities

(P*

Loading
Controlware
•
Control
Module
C o n t r o l w a r e ■■ •
•
•
•
•
Disk
Controlware
.....
.........
■.
■
Network Access Device (NAD) Controlware

1"!
1-1
1-2
1-2

Dumping

1-4

Controlware

.......

v_,

0$m*t.

Controlware Utilities
This section describes the utilities used for loading and dumping controlware.

Loading Controlware
By using the LOADBC utility, you can download control module controlware, disk
controlware, or network access device (NAD) controlware to the associated controller.

Control Module Controlware
You can use the LOADBC utility to load controlware into a control module for the 834
or 836 Disk Storage Subsystem. The calling job must be of system origin or you must
be validated for system origin privileges, and the system must be in engineering mode
(refer to the DSD ENABLE command in section 5). LOADBC will issue appropriate
messages to indicate the success or failure of the attempt to load controlware.
The format of the command is:
LOADBC,EQ=est,F=loadfile.

Parameter Description
EQ=est est is the EST ordinal of the control module in which to load the
controlware.
F = loadfile Name of the local file from which control module controlware is to
be loaded. If F = loadfile is specified, local file loadfile must contain
the control module controlware in binary format and an appropriate
header (refer to the NOS Version 2 Installation Handbook). If
F = loadfile is omitted, controlware is read from the system library
SYSTEM.

Revision

Controlware

Utilities

1-1

Disk Controlware

Disk Controlware
You can initiate downloading of disk controlware only from the system console. Also,
you can load the disk controlware to a channel only if it is either active or down and
unassigned. The calling job must be of system origin or you must be validated for
system origin privileges. The system must be in engineering mode (refer to the DSD
ENABLE command in section 5). LOADBC will issue appropriate messages to indicate
the success or failure of the disk controlware load attempt.
The format of the command is:
LOADBC,C=ch,F=loadfile,D=dumpflle.

Parameter Description
C=ch ch is a 2-digit octal number of the channel to which the disk
controlware is to be loaded. The controlware can be loaded only if
the channel status is UP or if the channel status is DOWN and not
assigned to a maintenance user.
F = loadfile Name of the local file from which disk controlware is to be loaded.
If F=loadfile is specified, local file loadfile must contain the disk
controlware in binary format and an appropriate header (refer to
the NOS Version 2 Installation Handbook). If F = loadfile is omitted,
controlware is read from the system library SYSTEM.
D=dumpfile Name of the local file to which 7155/7165/7255 disk controlware is
to be dumped before reloading. This parameter is ignored for other
types of controllers and an informative message is issued. LOADBC
performs a binary comparison between the old and new controlware
and writes this data to a file that can be processed by DSDI by
using the DMB parameter (refer to section 6 for information on
DSDI).

Network Access Device (NAD) Controlware
The LOADBC utility can be used to load NAD controlware into local NADs (380-170)
and remote NADs (380-170, 380-200, 380-370, and 380-110). Since the NAD controlware
is not automatically loaded at deadstart, LOADBC must be used before a local NAD
can be used by the operating system. NAD controlware may be automatically loaded by
the Remote Host Facility (RHF) when RHF is initiated. Refer to the RHF K display in
section 8.
LOADBC can be called from the console or a batch job. When loading 380-170
controlware into a local NAD, the EST entry associated with the NAD's channel
number must be OFF or the controlware-not-loaded flag must be set.
When loading a remote NAD, a local NAD that is not reserved for maintenance must
be defined in the EST. The EST entry must be ON. Controlware must be loaded and
running in the local NAD before loading the remote NAD.
Remote NAD loading operations can occur concurrently with RHF use of the local
NAD. However, extreme care should be exercised when performing a remote NAD load
to ensure that the correct remote NAD is being loaded and that the remote NAD is
not being used by the mainframe to which it is connected. LOADBC will issue
appropriate messages to indicate the success or failure of the NAD controlware load
attempt.

1-2

NOS

Version

Analysis

Handbook

Revision

^*®^Ss\

Network Access Device (NAD) Controlware

The format of the command is:
LOADBC,Pi,P2, •••,Pn-

Description

C=ch

The 2-digit octal number of the channel to which the NAD
controlware is to be loaded. This parameter is required.

F=filename

Name of the local file from which NAD controlware is to be loaded.
If F=filename is specified, local file filename must contain the
NAD controlware in binary format and an appropriate header (refer
to the NOS Version 2 Installation Handbook). If F=filename is not
specified, the NAD controlware type specified by the TY parameter
is read from the system library SYSTEM.

The following parameters apply only when loading remote NAD controlware.
Parameter Description
AC=aaaa

The 4-digit hexadecimal number specifying the remote NAD's access
code (refer to the RHF K display in section 8). The default is
AC = 0000.

LT = totlt2t3

The 4-digit binary bit pattern specifying the local trunk control
units (TCUs) that are enabled. At least one TCU enable must be
specified for remote NAD controlware loading. tn = l enables TCUn.
For example, LT=1010 indicates that the local TCUs 0 and 2 are
enabled.

ND = nn

The 2-digit hexadecimal number specifying the remote NAD's
address (refer to the RHF K display in section 8). This parameter
is required for remote NAD loads.

TY = value

Type of controlware to be loaded.

/0!m^.t

value Description
170

CYBER 170 controlware (380-170)

IBM

IBM controlware (380-370)

MIN Minicomputer controlware (380-110)
The default value is TY=170.
Under certain conditions, a remote NAD loading operation will fail on the first attempt
but a second loading attempt will succeed. This loading problem can be prevented by
always preceding a remote NAD loading operation with a remote NAD dumping
operation to ensure the remote NAD controlware is halted before loading is attempted.
For example, to load a remote NAD with NAD address 7F and access code F0F0
connected to TCU 0 of the local NAD on channel 5, enter the following commands.
X.DMPNAD(CH=05,ND=7F,AC=FOFO,LT=1000)
X.LOADBC(C=05,ND=7F,AC=F0F0,LT=1000)

Revision M

Controlware Utilities 1-3

Dumping Controlware

Dumping Controlware
The DMPCCC utility provides the capability to dynamically dump the CYBER channel J
coupler (CCC) memory in an online environment. The calling job must be of system
origin or you must be validated for system origin privileges, and the system must be
in engineering mode (refer to the DSD ENABLE command in section 5).
The format of the command is:
DMPCCC,C=ch,L=out file.
Parameter Description
C=ch ch is a 1- or 2-digit octal number of the channel from which the
CCC memory is to be dumped. The specified channel number must
be in the range from 0 to 13s or from 208 to 33s. The default is
C = 0.
L = o u t fi l e T h e 1 - t o 7 - c h a r a c t e r n a m e o f t h e fi l e t o w h i c h t h e d u m p i s t o b e ^ v
written.
The
default
is
L = O U T P U T.
1
DMPCCC lists the CCC memory in line format. Each line consists of 16 CCC memory
words in hexadecimal format. Repetitive lines are suppressed.

1-4

NOS

Version

Analysis

Handbook

Revision

f"'

Deadstart

Modifying

the

2-4
2-9
2-9
2-13
2-16
2-19
2-20

Modifying

APRDECKs

2-22

IPRDECK

2-23

System
Time

2-24
2-24
2-25

2-26

the
the

Loading
Messages
Entering

the
..
the

Initiating

xf^'

2-3

Modifying
the
EQPDECK
..........
Deadstart
Displays
_
Equipment
Status
Display
#
Mass
Storage
Status
Display
.
Mass
Storage
Initialization
Status
Display
Controlware
Status
Display
.
.
Disk
Thresholds
Display

Modifying

{*'

CMRDECK

Job

Date

and

Processing

Preparing
Level
Level
Level
2

for
Recovery
Deadstart
3
Recovery
Deadstart
1
Recovery
Deadstart
Recovery
Deadstart
..

Level

Initial

Deadstart

Error
Processing
Recovery
Functions
...............
Error
Idle
Recovery
Removable
Device
Nonremovable
Device

,
,

2-28
2-31
2-34
2-35
2-36
2-36
2-37
2-44
2-44
2-44

Deadstart
Deadstart is the process that makes the system operational and ready to process jobs.
After performing the appropriate deadstart procedures described in the CIP User's
Handbook, you can continue the deadstart process as shown in figure 2-1 and described
in detail following the figure.
This section also describes what you can do to recover if you experience system
problems during the deadstart process.

PERFORM APPROPRIATE
DEADSTART PROCEDURES
OESCRIBED IN CIP USER'S
HANDBOOK

MODIFY

CMRDECK

ENTER

MODIFY

NEXT.

EQPDECK

ENTER NEXT.
UNTIL YOU
LOCATE THE
DESIRED
APRDECK

ENTER TIME
AND DATE
(IF NECESSARY)

MODIFY
APRDECK

ENTER

MODIFY

IPR.

IPRDECK

WAIT FOR
DEADSTART
TO COMPLETE

INITIATE
JOB
PROCESSING

Figure 2-1. Deadstart Process

Revision M

Deadstart 2-1

Deadstart

NOTE
Modifying the deadstart decks (CMRDECK, EQPDECK, APRDECKs, and IPRDECK) ""'***)
does not apply to a level 3 recovery deadstart. Modifications made during the last
level 0, 1, or 2 deadstart are recovered during a level 3 recovery deadstart.

2-2

NOS

Version

Analysis

Handbook

Revision

Modifying the CMRDECK

Modifying the CMRDECK
If bit 6 of word 13 (word 12 for warmstart on a CYBER 70 or 6000 Computer System
with an active PP) is set (ppp = 001), or if you select the D = Y option on the *P*
display, an instruction display entitled CMRINST appears on the console screen(s) after
the CTI displays on a level 0, 1, or 2 deadstart. .All valid CMRDECK entries are
defined in this display. Several of the entries listed are assigned system default values.
These values are assumed if the entries do not appear in the CMRDECK being used.
To view the contents of the CMRDECK being used, toggle from the CMRINST display
to the CMRDECK display. If either the CMRDECK or CMRINST overflows two
screens, the display can be paged.
Modify the CMRDECK by entering the appropriate changes or additions from the
console keyboard. These entries can be made while either CMRDECK or CMRINST is
being displayed. Generally, each console entry supersedes the value currently specified
in the CMRDECK (or default value in CMRINST).
Refer to section 3, Deadstart Decks, for complete information on all CMRDECK
entries.
NOTE
The modified CMRDECK remains in effect only until the next level 0 deadstart is
performed. Changes to the CMRDECK are not recovered for the next deadstart unless
a new deadstart file is created. If you want these changes to take place on the next
level 0 deadstart, make the appropriate changes to the CMRDECK after NOS is up
and running and use LIBEDIT to replace the record on the deadstart file.
0$m\.

After all CMRDECK modifications have been made and you want to modify an
EQPDECK, APRDECK, or IPRDECK, enter:
NEXT.

Refer to Modifying the EQPDECK, Modifying the APRDECKs, or Modifying the
IPRDECK in this section. Otherwise, to indicate that all modifications to the
CMRDECK are complete and you want to begin loading the system, enter:
GO.

Revision

Deadstart

2-3

Modifying the EQPDECK

Modifying the EQPDECK
After completing all CMRDECK modifications, you can also modify the default
EQPDECK, an APRDECK, or the IPRDECK being used. If no changes need to be
made to any EQPDECK, but you do need to modify an APRDECK or the IPRDECK,
refer to Modifying the APRDECKs or Modifying the IPRDECK later in this section.
To modify an EQPDECK, enter
NEXT.

while the CMRDECK or CMRINST is being displayed.
You can make changes when the EQPDECK, EQPINST, or any one of the deadstart
displays is displayed at the console screen (refer to Deadstart Displays described later
in this section).
Table 2-1 describes the entries that can be made only at the console keyboard at
deadstart time and cannot be stored in the EQPDECK on the deadstart file. Refer to s*%i
section 3, Deadstart Decks, for complete information concerning all EQPDECK
entries.
After making the changes to EQPDECK you can toggle through the deadstart
displays to ensure all the changes are made.
NOTE
The modified EQPDECK remains in effect only until the next level 0 deadstart is
performed. Changes to the EQPDECK are not recovered for the next deadstart unless
a new deadstart file is created. If you want these changes to take place on the next
level 0 deadstart, make the appropriate changes to the EQPDECK after NOS is up
and running and use LIBEDIT to replace the record on the deadstart file.
After all EQPDECK modifications have been made and you want to modify an
APRDECK or IPRDECK, enter:
NEXT.

Refer to Modifying the APRDECKs or Modifying the IPRDECK later in this section.
Otherwise, to indicate that all modifications to the EQPDECK are complete and you
want to begin loading the system, enter:
GO.

2-4

NOS

Version

Analysis

Handbook

Revision

Modifying the EQPDECK

Table 2-1. EQPDECK Entries
Entry

Function

AUTOLOAD.

Toggles the selection of buffer controller
autoloading for all 7054/7154/7152/7155/7165/7255
control module controllers. This entry is valid only
when entered from the console keyboard. That is,
the AUTOLOAD entry cannot be included as part
of the EQPDECK on the deadstart file. This entry,
which affects all 7054/7154/7152/7155/7165/7255
control module controllers defined on the
mainframe being deadstarted, is not necessary for
normal system operation but is provided as an aid
to hardware checkout.

GRENADE.

Toggles the selection of the grenade function. This
entry is valid only when entered from the console
keyboard. That is, the GRENADE entry cannot be
included as part of the EQPDECK on the
deadstart file. The grenade function is issued to
all 7054/7154/7152/7155/7255 control module
controllers, once the controlware is loaded. This
function causes unit reservations to be cleared on
all 834, 836, and 844 units physically connected to
each controller. This entry is normally used when
a unit reservation from a downed mainframe
exists on a device. Use this entry with caution
since it can interrupt the operation of another
machine that could be accessing affected units
through another controller.

INITIALIZE ,op,esti ,est2,... ,estn.

Creates new labels for the specified mass storage
devices during a level 0 deadstart. This entry is
valid only when entered from the console
keyboard. That is, the INITIALIZE entry cannot
be included as part of the EQPDECK on the
deadstart file. Before any mass storage device
defined in the EQPDECK (by an EQ entry) can be
used, it must have a label that can be recognized
by the system. Existing labels are normally
recovered automatically during all levels of system
deadstart. However, if the existing label is
destroyed (for example, during maintenance
operations on the device) or if a new mass storage
device is added to the system, you enter the
INITIALIZE command to create a new label.

0P*\

(Continued)

Revision M

Deadstart 2-5

Modifying the EQPDECK

Table 2-1. EQPDECK Entries (Continued)
Entry

Function

INITIALIZE,op,esti,est2,...,estn.

(Continued)
Parameter

■"^5\

Description

op Level of initialization:
AL Total initialization.
PF Permanent files.
QF Queued files.
DF System dayfile.
AF Account dayfile.
EF Error log.
FP Format pack (844 or 895).
MF Binary maintenance log.
esti The 1- to 3-digit number specified in
the EQ entry for the device (for
example, EQ005...). This is also the
EST ordinal for the device. Any
number of devices can be initialized
with the same level of initialization,
provided the command is no more
than 72 characters.
Depending upon the levels of initialization
selected, all or part of the previously existing
information on the device is lost when the new
label is created. Total initialization of 844 or 895
format pack (AL or FP options) destroys all
information on a device. The other options
selectively purge information. A separate
INITIALIZE entry is required for each option
selected. Selecting FP results in an automatic
system selection of AL. The system deletes all
existing files, including a system deadstart file,
from a device initialized with the AL option. CTI,
MSL, and HIVS information is not deleted when a
device is initialized with the AL option. You
cannot initialize the device from which you are
deadstarting. You should initialize a device if you
just loaded CTI, HIVS, or MSL on it.
(Continued)

2-6 NOS Version 2 Analysis Handbook

Revision M

Modifying the EQPDECK

Table 2-1. EQPDECK Entries (Continued)
0m*\

Entry

Function

INITIALIZE,op,esti ,est2,... ,estn. (Continued)
No options (except AL and FP) are processed until
deadstart is completed. At that time, the K
display is requested and you must enter the
family name (FM) and device number (DN) of the
device to be initialized. This is a final check to
ensure that the correct device is being initialized;
the selected options are then processed.
If permanent files are to reside on the device
being initialized, the EQPDECK should contain a
PF entry for that device. The PF entry
corresponds to the EST ordinal specified in the EQ
entry and indicates that permanent files can reside
on the device. If the EQPDECK displayed contains
a PF entry for the device being initialized, a new
PF entry is not required unless the existing entry
is to be altered, or the associated EQ entry is
altered. Redefining the existing EQ entry clears
all associated attributes. In addition, if PF entries
do not exist in the EQPDECK, initializing the
device causes a default family name and device
number to be assigned. Thus, it is necessary to
reestablish the PF entry via the console keyboard
if the device is to remain a permanent file device.
For this reason, it is recommended that the PF
entry for all mass storage devices used for
permanent files reside in the EQPDECK. Although
this is recommended, it is not required.
If the EQ entry in the EQPDECK displayed
indicates that the status of a particular mass
storage device is off when the INITIALIZE entry
is made, initialize status is maintained and occurs
automatically when the DSD command ON is
entered for that device during normal system
operation.
Note that initialization of mass storage devices
can also be accomplished during normal system
operation via the DSD command INITIALIZE.
(Continued)

Revision

Deadstart

2-7

Modifying the EQPDECK

Table 2-1. EQPDECK Entries (Continued)
Entry

Function

PRESET,n.

Initializes tables (MST, TRT, MRT, and DAT) on
the link device that are required for the
management of shared multimainframe mass
storage devices. The entry is valid only for level 0
deadstarts by the first mainframe in the
multimainframe complex to deadstart. This entry
is valid only when entered from the console
keyboard. That is, the PRESET entry cannot be
included as part of the EQPDECK on the
deadstart file.
n

Description

n Number of shared devices.
If you do not specify n, the link device is preset,
and the amount of table space reserved for the
shared devices is determined by the number of
shared device entries in the EQPDECK.
PRESET=esti ,est2,...,estn.

RESET=esti ,est2,... ,estn.

2-8 NOS Version 2 Analysis Handbook

Presets independent shared devices in a
multimainframe complex. It is valid only on a
level 0 deadstart by the first mainframe in the
multimainframe complex. This entry is valid only
when entered from the console keyboard. That is,
the PRESET entry cannot be included as part of
the EQPDECK on the deadstart file.
esti

Description

esti

EST ordinal of independent shared
device.

Rescinds all device-related attributes except those
specified on the EQ entry. It restores the values
specified with the last encountered EQest entry. If
the DOWN command was specified, EQestn will be
up, but off. Ranges of ordinals are not allowed;
each ordinal must be entered individually. This
entry is valid only when entered from the console
keyboard. That is, the RESET entry cannot be
included as part of the EQPDECK on the
deadstart file.

Revision M

y=S^\

Deadstart Displays

Deadstart Displays
When processing the EQPDECK, the following deadstart displays are available in
addition to the EQPDECK and EQPINST displays. You can page through the deadstart
displays in a circular manner.
Display

Description

Equipment Status

Shows the hardware configurations (refer to figure 2-2).

Mass Storage Status

Shows how the system allocates files on a mass storage
device (refer to figure 2-3).

Mass Storage
Initialization Status

Shows the initialization status of the devices (refer to
figure 2-4).

Controlware Status

Shows the status of the controlware loaded (refer to
figure 2-5).

Disk Thresholds

Shows the disk threshold values at deadstart time (refer to
figure 2-6).

Equipment Status Display
The equipment status display lists the status of all the devices.
Figure 2-2 illustrates the equipment status display.

EQUIPMENT STATUS

EST
0.
1.
2.
3.

TYPE

CHANNELS

RD
DS
NE
TE

ON
ON
ON
ON

0.
7.
0.
0.

00.
00.
00.
00.

00.
10.
00.
00.

Figure 2-2. Equipment Status Display

Revision M

Deadstart 2-9

Equipment Status Display

Each entry in the display appears in the following format:
est

type

Header
|

est

channels

Description

EST

ordinal.

| type Device type. The following device types can appear in the
I e q u i p m e n t s t a t u s d i s p l a y.
|

type

Description
C C S a t e l l i t e C o u p l e r.
CM Control module for an 834 Disk Storage Subsystem.
CP 415 Card Punch.
C R 4 0 5 C a r d R e a d e r.
DB-i 885-42 Disk Storage Subsystem (1 ^ i ^ 3; full
track).
DC-i 895 Disk Storage Subsystem (1 ^ i ^ 2; full track).
DD-i 834 Disk Storage Subsystem. (1 ^ i ^ 8; full track).
D E E x t e n d e d m e m o r y.
DF-i 887 Disk Storage Subsystem (4K sector; 1 ^ i ^ 3;
full track).
DG-i 836 Disk Storage Subsystem (1 ^ i ^ 3; full track).
DH-i 887 Disk Storage Subsystem (16K sector; 1 ^ i ^ 2;
full track).
Dl-i 844-21 Disk Storage Subsystem (1 ^ i ^ 8; half
track).
DJ-i 844-41/44 Disk Storage Subsystem (1 ^ i ^ 8; half
track).
DK-i 844-21 Disk Storage Subsystem (1 ^ i ^ "8; full
track).
DL-i 844-41/44 Disk Storage Subsystem (1 ^ i ^ 8; full
track).
DM-i 885-11/12 Disk Storage Subsystem (1 ^ i ^ 3; half
track).
DN 9853 Disk Storage Subsystem (2K sector; full track).
DP Distributive data path to extended memory.
DQ-i 885-11/12 Disk Storage Subsystem (1 ^ i ^ 3; full
track).

2-10

NOS

Version

Analysis

Handbook

Revision

Equipment Status Display
0SS

Header
type

Description
(Continued)
type

Description

DV 819 Disk Storage Subsystem (single density).
DW 819 Disk Storage Subsystem (double density).
LQ Any line printer.
L R 5 8 0 - 1 2 L i n e P r i n t e r.
L S 5 8 0 - 1 6 L i n e P r i n t e r.
LT 5 8 0 - 2 0 L i n e P r i n t e r.
LX

5870

Printer.

M T M a g n e t i c Ta p e D r i v e ( 7 t r a c k ) .
NC 380-170 Network Access Device.
ND CDCNET Device Interface (MDI or MTI).
NP 255x Network Processing Unit.
N T M a g n e t i c Ta p e D r i v e ( 9 t r a c k ) .
RM Two-port multiplexer (models 865, 875, and CYBER
180-class machines).
SS MSE Controller.
TT Internal stimulation device.
The system creates the following device types at deadstart for
internal use. Except for the display console, DS, physical hardware
does not exist for these device types. The device types appear in
the second column of the equipment status display along with the
real device types.
type Description
DS Display console (EST ordinal 1).
NE Null e q u i p me n t (EST o rd i n a l 2 ).

Revision

Deadstart

2 - 11

Equipment Status Display

Header

Description

type

(Continued)
type

Description

Used for online reconfiguration of mass storage (EST
ordinal 0).
Tape equipment (EST ordinal 3).

TT Used for assignment of terminal files (EST ordinal 4).
st

Equipment status (ON, OFF, IDLE, or DOWN).

Equipment number that corresponds to switch settings on the
controller that connects the equipment to the channel(s). The site
engineer is responsible for setting these switches. Ask your
customer engineer for the correct switch settings if you are
unsure.

Unit number (serves as ID code for unit record devices). The ID
code provides a method of grouping unit record devices when a
site has several units. Output from a job read in through a card
reader with identifier un can only be directed to a device with
the same identifier. Changing the identifier code via the ROUTE
command can direct program output to a special printer.
Most equipment has the unit number labeled on the equipment.
Some equipment has the unit number as part of a switch or
button. Ask your customer engineer for the correct unit numbers
if you are unsure.

channels

Channel(s) on which equipment is available. An asterisk (*)
instead of a period (.) following the channel number entry
indicates that the channel is down.

2-12 NOS Version 2 Analysis Handbook

Revision M

Mass Storage Status Display

Mass Storage Status Display
The mass storage status display provides detailed information about all mass storage
devices.
Figure 2-3 illustrates the mass storage status display.
MASS STORAGE STATUS

EST
5.
6.
7.
10.
11.
14.
15.
16.
17.
20.
21.
22.
23.
24.
25.

0m\.
v

TYPE
DE
DB
DB
DB
DB
DQ
D
Q
D
Q
D
Q
D
Q
DQ
DL
DL
DL
DL

STATUS

FILES
S

S 3
S—
S—
S—

B—

R--T
R--T
R—T
R—T

F~R—
—R—
—R—
—R—

Figure 2-3. Mass Storage Status Display

Revision M

Deadstart 2-13

Mass Storage Status Display

Each entry in the display appears in the following format:
,tf*3^v

est

type

Header
est
type

status

fi l e s

Description

EST

ordinal,

Device

type:

type Description
DB-i 885-42 Disk Storage Subsystem (1 ^ i ^ 3; full
track).
DC-i 895 Disk Storage Subsystem (1 ^ i ^ 2; full track).
DD-i 834 Disk Storage Subsystem (1 ^ i ^ 8; full track).
D E E x t e n d e d m e m o r y.
DF-i 887 Disk Storage Subsystem (4K sector; 1 ^ i ^ 3;
full track).
DG-i 836 Disk Storage Subsystem (1 ^ i ^ 3; full track).
DH-i 887 Disk Storage Subsystem (16K sector; 1 ^ i ^ 2;
full track).
Dl-i 844-21 Disk Storage Subsystem (1 ^ i ^ 8; half
track).
DJ-i 844-41/44 Disk Storage Subsystem (1 ^ i ^ 8; half
track).
DK-i 844-21 Disk Storage Subsystem (1 ^ i ^ 8; full
track).
DL-i 844-41/44 Disk Storage Subsystem (1 ^ i ^ 8; full
track).
DM-i 885-11/12 Disk Storage Subsystem (1 ^ i ^ 3; half
track).
DN 9853 Disk Storage Subsystem (2K sector; full track).
DP Distributive data path to extended memory.
DQ-i 885-11/12 Disk Storage Subsystem (1 ^ i ^ 3; full
track).
DV 819 Disk Storage Subsystem (single density).
DW 819 Disk Storage Subsystem (double density).

2-14

NOS

Version

Analysis

Handbook

Revision

Mass Storage Status Display

Header

Description

status

Status conditions. Any combination of conditions can exist. The
following codes are listed in the order in which they appear on the
display.

files

Revision M

status

Description

A copy of the system resides on this device.

Device is shared by more than one mainframe.

Device is removable.

Independent shared device.

Alternate system device.

Initialization requested or format is pending.

Preset of the device requested.

System dayfile on this device.

Account dayfile on this device.

Error log on this device.

Binary maintenance log on this device.

System "default family on this device.

Checkpoint device. A copy of the checkpoint file resides
on this device.

Types of files that are allowed on this device. Any combination of
types can exist. The following codes are listed in the order in
which they appear on the display. Refer to the MSAL EQPDECK
entry in section 3, Deadstart Decks.
status

Description

Secondary rollout.

LGO.

Local.

Primary.

Job dayfile.

Rollout.

Output.

Input.

Temporary.

Deadstart. 2-15

Mass Storage Initialization Status Display

Mass Storage Initialization Status Display
The mass storage initialization status display shows the initialization status of mass
storage devices on the system.
Figure 2-4 illustrates the mass storage initialization status display.
MASS STORAGE INITIALIZATION STATUS

EST

DE
DB
DB
DB
DB
D
Q
D
Q
D
Q
D
Q
D
Q
D
Q

5.
6.
7.
10.
11.
14.
15.
16.
17.
20.
21.

DAM

IAM

OPTIONS

FM/PN

N
C

QSA-E—PQSAED
FT
377.
000.

377.
377.

FEATURE
R4IAE

40.

000.
000.

Figure 2-4. Mass Storage Initialization Status Display
Each line in the display appears in this format:
est

type

Header

options

iam

dam

fm/pn

Description

est

EST

ordinal.

type

Device

type.

type Description
DB-i 885-42 Disk Storage Subsystem (1 ^ i ^ 3; full ]
track).
DC-i 895 Disk Storage Subsystem (1 ^ i ^ 2; full track).
DD-i 834 Disk Storage Subsystem (1 ^ i ^ 8; full track).
D E E x t e n d e d m e m o r y.
DF-i 887 Disk Storage Subsystem (4K sector; 1 ^ i -£ 3;
full track).
DG-i 836 Disk Storage Subsystem (1 ^ i ^ 3; full track).
DH-i 887 Disk Storage Subsystem (16K sector; 1 ^ i ^ 2;
full track).
Dl-i 844-21 Disk Storage Subsystem (1 *s i ^ 8; half ^^
track).

2-16

NOS

Version

Analysis

Handbook

Revision

Mass Storage Initialization Status Display

Header

Description

type

(Continued)
type Description
DJ-i
DK-i

844-41/44 Disk Storage Subsystem (1 ^ i ^ 8; half
track).
844-21 Disk Storage Subsystem (1 «s i ^ 8; full track).

DL-i

844-41/44 Disk Storage Subsystem (1 ^ i ^ 8; full
track).

DM-i

885-11/12 Disk Storage Subsystem (1 ^ i as 3; half
track).

9853 Disk Storage Subsystem (2K sector; full track).

Distributive data path to extended memory.

DQ-i

885-11/12 Disk Storage Subsystem (1 ^ i ^ 3; full
track).

DV 819 Disk Storage Subsystem (single density).
DW 819 Disk Storage Subsystem (double density).
options

Initialize options. Maximum of eight options are displayed.
options Description
F

Format pack.

Total system.

Permanent files.

Queue files.

System dayfile.

Account dayfile.

Error log.

Binary maintenance log.

Type of unit device.
t

Description

Family device.

Auxiliary device.

0ms

Revision M

Deadstart 2-17

Mass Storage Initialization Status Display

Header Description
iam Indirect access mask,
dam Direct access mask,
fm/pn Family name/pack name.
fm/pn Description
F Family name.
X

Pack

name,

dn Device number if the device unit is the family device,
nc Number of permanent file catalog tracks.

2-18

NOS

Version

Analysis

Handbook

Revision

Controlware Status Display

Controlware Status Display
/$foft\

The controlware status display shows what type of controlware is loaded to which
channels.
Figure 2-5 illustrates the controlware status display.

CONTROLWARE STATUS
CHANNEL

CONTROLWARE

00.
01.
02.
03.
04.
05.
07.
10.
11.
12.
13.

N
N

F
M
NN

Figure 2-5. Controlware Status Display
jfiffiQifirSy

Each line in the display appears in this format:
channel controlware
Header

Description

channel

Channel on which equipment is available.

controlware

Name of the controlware loaded. Refer to the LBC EQPDECK
entry in section 3, Deadstart Decks, for a list of controlware
types.

Revision M

Deadstart 2-19

Disk Thresholds Display
/<^^\

Disk Thresholds Display
The disk thresholds display shows the disk threshold values at deadstart time. The
system uses these threshold values as limits when monitoring disk verification failures,
available disk space, and disk error processing. If a threshold value is exceeded, the
system performs a corrective action, such as notifying the operator or restricting
activity on the affected disk.
Figure 2-6 illustrates the disk thresholds display.
EST

TYPE

SIZE

DL-3

3150

100

315

146

100

Figure 2-6. Disk Thresholds Display
Each line in the display appears in the following format:
est

type

Header
est
type

size

Description

EST

ordinal,

Device

type.

2-20

NOS

Version

Analysis

Handbook

Revision

Disk Thresholds Display

Header
type

Description
(Continued)
type Description
DL-i 844-41/44 Disk Storage Subsystem (1 ^ i ^ 8; full
track).
DM-i 885-11/12 Disk Storage Subsystem (1 -* i ss 3; half
track).
DN 9853 Disk Storage Subsystem (2K sector; full track).
DP Distributive data path to extended memory.
DQ-i 885-11/12 Disk Storage Subsystem (1 ^ i ^ 3; full
track).
DV 819 Disk Storage Subsystem (single density).
DW 819 Disk Storage Subsystem (double density),

size Total number of logical tracks on the corresponding device type,
v f V e r i fi c a t i o n f a i l u r e t h r e s h o l d ,
ra Restricted activity threshold.
Is

Low

space

threshold,

re Recovered error threshold,
ue Unrecovered error threshold.

Revision

Deadstart

2-21

Modifying the APRDECKs

Modifying the APRDECKs
After completing all EQPDECK modifications, you can also modify the default
APRDECK, the APRDECK for a specific equipment, or the IPRDECK being used. You
can modify an APRDECK only when you are initializing the corresponding equipment.
If no changes need to be made to any APRDECK, but you do need to modify the
IPRDECK, refer to Modifying the IPRDECK later in this section.
The APRDECK contains entries identifying areas of mass storage that are not usable
(flaws). The APRDECK used can vary from equipment to equipment. One of the
parameters specified when an equipment is defined in the EQPDECK is the
APRDECK number that applies to that equipment. The default (APRDOO) is selected
if this parameter is not specified.
To modify an APRDECK, enter
NEXT.

while the EQPDECK or EQPINST is being displayed. The APRINST display describes ^
the valid entries. You can toggle between the APRDECK and APRINST. Enter the
changes or additions to the APRDECK from the console keyboard (refer to section 3,
Deadstart Decks, for a description of the entries).
If there are no changes to the APRDECK displayed, enter
NEXT.

to go to the next APRDECK. Repeat this process until the appropriate APRDECK is
displayed or until you have changed all APRDECKs needing changes. '"^
After all APRDECK modifications are complete, you can skip to the IPRDECK by
entering:
IPR.

Refer to Modifying the IPRDECK, next, for more information. Otherwise, to indicate
that all modifications to the APRDECKs are complete and you want to begin loading
the system, enter:
GO.

2-22

NOS

Version

Analysis

Handbook

Revision

Modifying the IPRDECK
00®S
(

Modifying the IPRDECK
The IPRDECK contains installation parameters that describe the mode of system
operation. IPRDECK modification is seldom required during deadstart since nearly all
IPRDECK commands are also valid DSD commands that make the same changes
during normal system operation. Generally, installation parameters changed during
normal operations (with DSD commands or by modifying the IPRDECK) are retained
only across a level 3 recovery deadstart.
After entering
IPR.

when all the CMRDECK, EQPDECK, or APRDECK modifications are complete or after
repeatedly entering
N E X T.

to step through all the APRDECKs, the instruction display entitled IPRINST appears
on the console screen(s). This display defines all valid IPRDECK entries. Most of these
entries are also valid DSD commands.
To view the contents of the IPRDECK being used, toggle from the IPRINST display
to the IPRDECK display. If either the IPRDECK or IPRINST overflows two screens,
you can page the display.
Enter the appropriate changes or additions from the console keyboard. These entries
can be made while either IPRINST or IPRDECK is being displayed. A console entry
supersedes the value currently specified in the IPRDECK.
NOTE
The modified IPRDECK remains in effect only until the next level 0, 1, or 2
deadstart is performed. Changes to the IPRDECK are retained if a level 3 recovery
deadstart is performed. If you want these changes to take place on the next level 0
deadstart, make the appropriate changes to the IPRDECK after NOS is up and
running and use LIBEDIT to replace the record on the deadstart file.
For complete information concerning IPRDECK entries, refer to section 3, Deadstart
Decks, and to section 5, DSD Commands.
To indicate that changes to the CMRDECK, EQPDECK, APRDECK, and/or IPRDECK
are completed and you want to begin loading the system, enter:
GO.

Revision

Deadstart

2-23

Loading the System

Loading the System
If you are performing a level 0 or level 2 deadstart, the system library is
automatically loaded from the deadstart file to each mass storage device specified in
the EQPDECK as a system device. If no system device is specified, the system is
loaded on the first nonremovable mass storage device in the equipment status table.
Mass storage labels are validated for all levels of deadstart. This ensures that the
configuration matches the one specified in the EQPDECK. Normally, the device label
validation display appears for only a few seconds. However, this display remains
longer (from 30 seconds to 3 minutes) if 834, 836, 887, or 9853 disk units must first
be automatically spun up in order to validate their labels.
If you specify a level 1 or level 3 recovery deadstart, the system library is not
reloaded. In this case, the deadstart file is rewound and is not accessed again until
another deadstart operation is performed. The system library is recovered from
checkpoint information on mass storage. Central memory tables such as the system
file name table (FNT), executing job table (EJT), queued file table (QFT), equipment
status table (EST), and track reservation table (TRT) are either recovered from
checkpoint information for level 1 or from central memory (and the link device,
extended memory, if in multimainframe mode) for level 3.

Messages
If a deadstart error occurs, a message appears on the right console screen and,
depending upon the nature of the error, deadstart processing may halt. Refer to Error
Processing later in this section for complete information and corrective action. If the ^_
system is being loaded (level 0 or 2 only), the name of each system library program is j
also displayed on the right console screen as it is being loaded. This allows you to
monitor deadstart progress.
The left console screen may display the message ENTER DATE YY/MM/DD. You can
enter the date while the system is being loaded.

2-24

NOS

Version

Analysis

Handbook

Revision

Entering the Date and Time

Entering the Date and Time
Each time a system deadstart function is performed, it is necessary to enter the
current date and time (except for CYBER 180-class machines; they get the date and
time from CTI during deadstart). The system uses the date and time (updated every
second) for dayfile messages and for permanent file catalogs and directories for files
being accessed. This includes the creation, last modification, and last access date and
time for each permanent file in the system. It is important to enter the correct date
and time in order to accurately maintain these system records. If you are performing a
level 3 recovery deadstart, it is possible to recover the date and time from the previous
system deadstart. However, this is not recommended since the new date and time
recorded for system records would no longer be accurate.
When the system loading (or recovery) phase of deadstart is about to begin, the
system checks for the correct date and time. If CTI is unable to determine the correct
date and time or the mainframe is other than a CYBER 180-class, the following
message appears on the left console screen requesting entry of the current date.
ENTER DATE YY/MM/DD.

Enter the current date, followed by CR, in this format:
yy/mm/dd.
Entry
yy

Ye a r ;

Description
00

through

99.

mm Month; 01 through 12.
dd Day; 01 through nn (nn is the number of days in the month).
For deadstart levels 0, 1, and 2, pressing CR without first entering the date causes the
system to assume the date that the deadstart file was created. For a level 3 recovery
deadstart, pressing CR alone recovers both the previous date and time (time entered
during the last deadstart plus time accumulated until this deadstart).
When the system accepts the date entry, it displays the following request for entry of
the current time.
ENTER TIME HH.MM.SS.

Enter the current time in this format:
hh.mm.ss.
Entry
hh

Hour;

Description
00

through

23.

mm Minute; 00 through 59.
ss Second; 00 through 59.
For deadstart levels 0, 1, and 2, pressing CR without first entering the time causes the
system to set the time to 00.00.00. If you enter CR alone following the date prompt on
ra level 3 recovery, this prompt to enter time does not appear (the previous time is

Revision

Deadstart

2-25

Initiating Job Processing

Initiating Job Processing
DSD commands specified in the IPRDECK automatically initiate normal job processing
except on a level 3 recovery where you must enter AUTO. If a level 1 or level 3
recovery deadstart is being performed, the system recovers all jobs and active files and
resumes normal operation immediately. However, if an initial deadstart (level 0) or
level 2 recovery deadstart is being performed, job processing may not be initiated
immediately. The time of initiation depends upon the time it takes to load the system
from the deadstart file (you can monitor progress on the right console screen). If file
loading is not completed when the time entry is made, the DSD commands specified in
the IPRDECK are displayed on the left screen. Until file loading completes, you can
clear one or more of the DSD commands.
Clearing a command prevents it from being executed when file loading completes. In
this case, you must manually enter the commands necessary to initiate job processing
from the console keyboard.
To initiate job processing, enter either:
AUTO.

or
MAINTENANCE

Following entry of the AUTO or MAINTENANCE command during an initial (level 0)
deadstart, the deadstart sequencing process begins. Deadstart sequencing causes job
processing to be suspended until all system files in the default family are initiated. To
initiate a family other than the default, enter the command:
X.ISF(FM=family)

Parameter

Description

family

Alternate family of devices.

For additional information concerning the ISF command and deadstart sequencing, refer
to section 20, System File Initialization.

2-26 NOS Version 2 Analysis Handbook

Revision M

y^=5^>

Initiating Job Processing

Normal job processing begins after the deadstart sequencing job completes. If the
J^v AUTO command is entered, the subsystems enabled in the IPRDECK are automatically
V assigned to specified control points. Assuming that all standard subsystems are set to
be enabled, the system calls them to specific control points as shown in the following
example:
Control Point Job Sequence
Number
Name
Activity
1

IAF

Interactive

F a c i l i t y.

NAM

Network

Access

RHF

Remote

Host

SMF

Screen

n-2x
.2

n_1

Central

n2
n

F a c i l i t y.

Management

MAG
BIO

Method.

F a c i l i t y.

Magnetic tape subsystem executive routine.
site

batch

input/output.

R B F R e m o t e B a t c h F a c i l i t y.
.2

SYS

System.

The MAINTENANCE command performs the same function as the AUTO command.
Additionally, it assigns several maintenance routines, according to mainframe type, to
available control points and runs them as normal jobs with minimum queue and CPU
priorities. These are CPU or central memory test routines designed to detect hardware
errors. The routines display error messages either at the control point on the B,0
display or in the system error log. To display the error log, enter:
A,ERROR LOG.

You should monitor these routines from time to time. If a maintenance routine displays
an error message indicating a hardware malfunction occurred, call a customer engineer.
It is recommended that these programs be run at all times. The maintenance programs
use little memory, are run at minimum CPU and queue priority, and are automatically
^^ rolled out if necessary; thus, system performance is not severely affected. Descriptions
^^ of the maintenance routines are in the NOS Online Maintenance Software Reference
Manual.
You can use the SCHEDULE command to schedule jobs, but it does not initiate
subsystems or maintenance jobs. Refer to the NOS Version 2 Operations Handbook
for a description of the SCHEDULE command.

1. n is the number of control points defined by the NCP entry in the CMRDECK.

Revision

Deadstart

2-27

Preparing for Recovery Deadstart

Preparing for Recovery Deadstart
Sometimes during system operation an uncorrectable error occurs that prevents further
system activity. Often the situation can be corrected by deadstarting the system and
recovering prior activity. The success of such a recovery depends upon the severity of
the problem and the extent to which system information is destroyed. There are three
levels of recovery deadstart available (levels 1, 2, and 3). Table 2-2 lists each deadstart
level, including level 0 (initial deadstart), and describes the extent of recovery possible.
If the MS VALIDATION installation option is enabled during a level 1 or 2 recovery,
or if both the MS VALIDATION and PF VALIDATION options are enabled during a
level 3 recovery, the system:
• Verifies selected mass storage files.
• Checks files identified in the queued file table (QFT) to ensure that all tracks in
the chain are reserved and that no circular linkage exists.
• Depending on file type, checks the track reservation table (TRT) to ensure that
the file is preserved.
• Checks all preserved files for proper length.
If the system encounters a verification failure, it clears the queued file table entry but
does not release disk space assigned to the file. If a length error is detected, the
system sets error idle status and terminates recovery operations on the device. To
recover from an error idle condition, refer to Error Idle Recovery under Error
Processing later in this section.
During level 0 deadstart, the system verifies the length of preserved files regardless
of the setting of the MS VALIDATION option. If a length error is detected, the
system reads the disk chain to determine the correct length of the file, issues a
message to the B,0 display, and stops recovery of the device. To alter the EOI for
the file and proceed with recovery, enter:
GO,SYS. or GO,.

To terminate recovery of the device, enter:
PAUSE,SYS.

2-28

NOS

Version

Analysis

Handbook

Revision

Preparing for Recovery Deadstart

y*^\

Table 2-2. Levels of System Deadstart: Information Recovered
Deadstart
Level

Perma
nent
Files

System

System
Dayfiles

Jobs

Queued Files

Batch jobs are
rerun.

Recovered as
inactive.

Yes.

No.

Yes.2

Recovered from
last checkpoint.

Active queues
recovered from
last checkpoint.

Yes.

Recovered
from last
checkpoint.

Yes.

Recovered from
last checkpoint.

Active queues
recovered from
last checkpoint

Yes.

No.

Yes.

Recovered from
CM copy of EJT.3

Active queues
recovered from
CM copy of QFT.

Yes.

1. The input and output queues are recovered. Rolled out and executing batch jobs
are also rerun. The input files associated with these jobs are returned to the input
queues, unless the device they reside on is initialized. Permanent files are recovered
unless the device is initialized.
2. Dayfiles are recovered unless initialized by an INITIALIZE entry in the
EQPDECK.
3. Jobs that are rolled out continue. Jobs that are in CM are aborted with EXIT
processing and then rerun if possible.

Revision M

Deadstart 2-29

Preparing for Recovery Deadstart

CAUTION
Before attempting any level of recovery deadstart, whether it is a level 0, 1, 2, or 3 )
deadstart, enter a CHECKPOINT SYSTEM command, and wait for the CHECKPOINT
COMPLETE message to appear on the system console. The CHECKPOINT SYSTEM
performs the following functions:
1. All currently executing jobs are rolled out. (Ensures that these jobs can roll back
and continue executing after a level 3 deadstart.)
2. All mass storage tables and track reservation tables are copied to disk, and all
pending disk I/O operations are completed. (Ensures the integrity of the disks
after a level 0, 1, or 2 deadstart.)
3. A system checkpoint file (which includes a copy of all the system tables in central
memory) is written to disk. (Provides a system checkpoint file for a level 1 or 2
deadstart.)
If, due to a system hang or other problem, it is not possible to enter a .<**%^
CHECKPOINT SYSTEM, or if the CHECKPOINT COMPLETE message does not /
appear, the disk updates may not have been performed. If a level 0 deadstart is
performed at this time, permanent file information may be lost. To prevent such a
loss, always perform a level 3 deadstart after a system hang. Select the ABORT
option on the level 3 deadstart display to abandon the deadstart; the ABORT option
performs the disk updates and then abandons the deadstart.
The following topics provide general information concerning each level of system
deadstart and recommended steps of preparation.

2-30

NOS

Version

Analysis

Handbook

Revision

Level 3 Recovery Deadstart

Level 3 Recovery Deadstart
Usually you perform a level 3 recovery deadstart following an equipment or system
malfunction (for example, channel or PP hung), providing the system remains intact
Basically, the system FNT, QFT, EJT, TRT, EST, and control-point areas of central
memory must be intact in order to successfully perform a level 3 recovery deadstart.
However, unless you can determine that central memory is no longer intact, attempt a
level 3 recovery deadstart before a level 0 deadstart. This is recommended because
system activity, as it existed at the time of the malfunction, can best be recovered by
performing a level 3 recovery deadstart. Only PP memory confidence testing occurs
during a level 3 recovery deadstart; central memory is not affected.
Requests for device checkpoint are retained over a level 3 recovery. Therefore, if a
system malfunction prevents a device checkpoint from being done, the checkpoint is
processed after level 3 recovery is successfully completed. If a level 3 recovery fails,
always do another level 3 recovery with the ABORT option selected before doing a '
level 0 deadstart. This ensures that all checkpoint processing is done correctly.
f^' On a level 3 deadstart the CMRDECK, the EQPDECK, the APRDECKs, and the
IPRDECK cannot be viewed or changed. The CMRDECK, the EQPDECK, the
APRDECKs, and the IPRDECK specified during the last level 0 deadstart remain in
effect. If you set the CMRDECK switch (bit 6 in word 13 of the deadstart panel) or
select the D = Y option on the CTI *P* display; the system halts and displays level 3
deadstart options. The options and their default values are displayed on the left
screen (figure 2-7) and instructions on the right screen (figure 2-8).

LEVEL 3 OPTIONS
A B O R T.

A B O R T, B .

AUTOLOAD.

YES

GRENADE.

AUTO.

YES

Figure 2-7. Level 3 Deadstart Left Screen Display

Revision

Deadstart

2-31

Level 3 Recovery Deadstart

INSTRUCTIONS FOR SELECTING LEVEL 3 RECOVERY OPTIONS.
ENTER COMMAND TO TOGGLE SELECTION.
ENTER GO. TO CONTINUE RECOVERY.
ABORT.
CHECKPOINT ALL DEVICES AND ABORT LEVEL 3 RECOVERY.
SELECTING -ABORT.* DESELECTS -ABORT,B.*
ABORT,B.
CHECKPOINT ALL NONBUFFERED DEVICES AND ABORT LEVEL
3 RECOVERY. SELECTING *ABORT,B.* DESELECTS -ABORT.*.
AUTOLOAD.
TOGGLE THE SELECTION OF BUFFER CONTROLLER AUTOLOADING.
GRENADE.
TOGGLE THE SELECTION OF THE GRENADE FUNCTION. THE
GRENADE FUNCTION IS ISSUED ONCE THE CONTROLWARE IS
LOADED, CAUSING UNIT RESERVATIONS TO BE CLEARED ON
ALL 844 UNITS PHYSICALLY CONNECTED TO EACH CONTROLLER.
AUTO.
TOGGLE THE SELECTION OF THE DSD AUTO COMMAND.

Figure 2-8. Level 3 Deadstart Right Screen Display
Entering a command will toggle the level 3 deadstart selections. The ABORT command
checkpoints all the devices and aborts level 3 recovery. Selecting the ABORT command
automatically deselects the ABORT,B command. The ABORT,B command checkpoints
all the nonbuffered devices and aborts level 3 recovery. Selecting the ABORT,B
command automatically deselects the ABORT command. The AUTOLOAD command
toggles the selection of buffer controller autoloading. The GRENADE command toggles
the selection of the grenade function. The AUTO command toggles the selection of the
DSD AUTO command. Refer to table 2-1 for more information about the AUTOLOAD
and GRENADE commands. When you are done making changes, enter ^
GO.

to continue the deadstart recovery. If you choose not to display the level 3 options, the
default values are used.
A level 3 recovery deadstart is impossible after:
• An attempted checkpoint recovery (level 1).
• An aborted level 0 (initial) deadstart.
• The MREC utility (refer section 8, K-Display Utilities) has been run for the
machine to be deadstarted while in multimainframe mode.

2-32

NOS

Version

Analysis

Handbook

Revision

Level 3 Recovery Deadstart

It is recommended that you stop system activity prior to beginning the system
deadstart procedure. To accomplish this, enter the following DSD commands:
Command

Description

E,M.

Displays the disk status display (E,M).

UNLOCK.

Unlocks the system console. This command is necessary only if the
system console is locked.

CHECK POINT
SYSTEM.

Provides for termination of job processing and for writing the
contents of central memory tables to mass storage. For a complete
description of this process, refer to the CHECK POINT SYSTEM
command in section 5, DSD Commands.

STEP.

Prevents the system from processing PP requests. This stops all
central memory input/output (I/O) operations. You should enter the
STEP command after all device checkpoints are completed.
Determine checkpoint status from the disk status display (E,M)
(refer to the NOS Version 2 Operations Handbook).

NOTE
To recover interactive users after a level 3 recovery, sense switch 1 must be set in
the IAF procedure. Sense switch 1 is set by default in the released IAF procedure.

Revision M

Deadstart 2-33

Level 1 Recovery Deadstart

Level 1 Recovery Deadstart
Usually you perform a level 1 recovery deadstart to resume normal processing
following maintenance procedures. The system, all jobs, and all active files are
recovered from checkpoint information on mass storage.
NOTE
A level 1 recovery deadstart is not intended to be a recovery process after a system/
equipment malfunction. You should never attempt it after a level 3 recovery
deadstart fails.
Level 1 recovery is also useful in system test situations. If two systems are being
alternated, separate mass storage devices and tapes must be available for both
systems. Tapes are not repositioned after a level 1 deadstart. Thus, if a job was
previously assigned to the tape unit that has been used for deadstarting, the job cannot
be recovered. The tape unit should be left unloaded after recovery until it is no longer
assigned to the job (job aborted).
The following rules apply when performing a level 1 recovery deadstart.
• The DSD command CHECK POINT SYSTEM must have been successfully
completed immediately before the end of the last NOS operating period.
« The contents of the extended memory must not be destroyed from the time of the
CHECK POINT SYSTEM command.
® Memory dumps must be completed before level 1 recovery deadstart begins since
memory confidence testing destroys the contents of both central memory (except '^
on CYBER 180-class machines) and PPs.
• The mass storage equipment configuration must be the same as specified during
the most recent level 0 deadstart; that is, the same EQPDECK must be used.
© The system devices (mass storage devices on which the system library resides)
must be the same as or fewer than those specified during the most recent level 0
deadstart.
It is recommended that you stop system activity before beginning the system deadstart /es%,
procedure. To accomplish this, enter the following DSD commands:
Command

Description

_____

UNLOCK. Necessary only if console is currently locked.
CHECK POINT Provides for termination of job processing and for writing the
SYSTEM. contents of central memory tables to mass storage.
STEP. Prevents the system from processing PP requests. This stops all
central memory I/O operations.

2. Separate tapes are necessary only if tape jobs are being checkpointed.

2-34

NOS

Version

Analysis

Handbook

Revision

Level 2 Recovery Deadstart

Level 2 Recovery Deadstart
0ms
V Usually you perform level 2 recovery deadstart in system test situations; it is not
recommended for the normal production environment. If you select level 2 recovery, all
jobs and active files are recovered from checkpoint information on mass storage as in
level 1 recovery. However, no attempt is made to recover the system. Instead, the
system is loaded from the deadstart file as in level 0 deadstart. In all other respects,
level 2 recovery is identical to that described for level 1, and all level 1 rules apply'

Revision

Deadstart

2-35

Level 0 Initial Deadstart

Level 0 Initial Deadstart
Use level 0 or initial deadstart in cases where a recovery deadstart is not possible.
This is a complete or initial load from the deadstart file. Only preserved files, which
include permanent files, queued files, and system dayfiles, are recovered (preserved
files are recovered on all levels of system deadstart). Because memory confidence
testing destroys the contents of central memory (except on CYBER 180-class machines)
and PPs, all memory dumps must be completed before deadstart begins.
NOTE
If the machine is the first machine being deadstarted in a shared device
multimainframe environment, you must enter a PRESET command (refer to section
13, Multimainframe Operations).

Error Processing
If no CTI display appears when you initiate a deadstart, perform the following steps as
needed. After each step, reinitiate the deadstart to see if the problem has been
eliminated.
Deadstart from tape:3
1. If the unit select switch on the deadstart tape unit is not on (tape does not move),
check the channel, controller, and unit selections on the deadstart panel or display
to ensure they are set correctly.
2. If the unit select switch is on, the correct unit was selected; however, check word
11 of the deadstart panel or display to ensure it is set correctly.
3. Ensure that a 7-track tape is not mounted on a 9-track drive or vice versa. Also,
ensure that a deadstart tape is not mounted on a tape unit that does not support
the density of the deadstart tape.
4. Ensure that the deadstart tape is an l-format unlabeled tape.
5. Ensure that the card reader and tape unit (667 or 669 only) are not on the same ^\
channel and that the card reader is not on a channel with a PP. Also, ensure
that two or more units do not have the same physical unit number.
6. If still no display appears after initiating the deadstart, there might be a parity
error on one of the first records of the deadstart tape or the magnetic tape
controller might have detected a channel parity error on a CYBER 170 Computer
System.

3. When deadstarting a CYBER 180-class machine, the disk containing the CIP module must be used.

2-36

NOS

Version

Analysis

Handbook

Revision

Recovery Functions

[

Deadstart

from

disk:

1. Ensure that disk power is on and the disk is ready for operation.
2. Ensure that the disk has the CIP module loaded.
3. Ensure that the deadstart panel or display is set correctly.
4. Select an alternate channel.
5. If still no display appears after initiating the deadstart, there might be a parity
error on one of the first records of the deadstart file or the disk controller might
have detected a channel parity error on a CYBER 170 Computer System.
For a proper understanding of the problems that can occur during deadstart, you
should be familiar with several basic concepts. For example, because most errors that
occur involve mass storage devices, you should be familiar with their use in the
system. Each mass storage device has a label that contains descriptive information
about its contents. For certain levels of recovery deadstart, this information must be
consistent with corresponding information either contained in central memory or
provided through deadstart procedures. Conflicts can result in the system issuing
deadstart error messages. An attempt is made to recover all mass storage devices
defined in the EST during all levels of system deadstart.

Recovery Functions
The specific recovery function performed depends upon the level of deadstart selected.
Table 2-3 describes the recovery function performed for each deadstart level and the
types of errors you can encounter. The system response to errors and the recommended
action are also listed.
Refer to the NOS Version 2 Operations Handbook for information concerning all
deadstart messages.

Revision

Deadstart

2-37

Recovery Functions
■'<:S%v

Table 2-3. Mass Storage Device Recovery

01
JC

01 60
CWrl
kl
r A) xi sa <*i 3
IO TJ CO -H kl O
tn • 3 K «J O J=
O
k>

-4 SO U
s

oi c THl

11
gO
k. J-

u u
ii K a o

»H Ck

CL 01 tO 4J

kl
kl

N-l

kl
O

>>
kl
V H

CO
t l 01
B

Brt
d
oi > e
H I I O CO

■M
TJk3l
v-

k l

01
k l

kl jC
Ol
01
B E N
n
o
t

k .

g"S

■HM*U

C -H kl K
T< Ol rH
U
JP

^
«l<
» kl M
kl *-rt->
kl
O
M
« tj tj as
9 10 01 rH
B u m
Ol
c
O ki tt) ID

■H01JPB
>

NH
k l

01
tr.

k l

91 rH
u. •
h U TJT)
41 0> 0)
X Si tt X
H -H o
3
H
b
6 0) X O
U 01
D
rt O
X Cl 91 -t
kl ti JP kl
ra o.
IM Q> rH Ti
Ui
X
k. it
UTJ
U
to n r H
• «JP u
co
tj
tj
jp
u gi 0» 91
ui ai x

<0£D
01
»H
O
O. ki 0) E B ^ 91 •»«
im
n
-h
to
*»
j:
hH
»-H
Gtokiki
O TJ rH tO d O Ioi to u tu rH ta e
•
•
k
H
«
a
ki
o
Q TJ (I IJ U^ II 10
O
«
uh
«
jp
tj
6
oi e c 6 -H « oi
o i u u H s a i H t i u
6.
o
u
x
-i
ta
to
>%kftntDft)fg-Ha>>%
W Q.-H -t CUrt 9 ki CO

kl C
01 « «H

iJ o
8
«
M 01 >n
tl W TJ

•
Ot
U
rH
>
01
TJ

TJ
«l
u
n
a
h
h
tn
rH
O
a
ki
c
•M «H O "H
kl
kl

V t } t
Ck-H kl
-h jp
«M 01 B n t o
K
K
n 9
rH

fi g

00 ki
01 00-H CO
TJ 6 ki TJ
-J N-l to
CO 3 01 0)
Ol O JB TJ
ki rH kl
T,
TJ
tn O 6 B
01 «kl
IU X kl CO rH
kl 10 rH <0
kl
U
O.X
B - 5. ta
4 1 0 1 P. H 0 0
B O CO TJ B
•
rl
NH
6 > V SI CO
it 01 HH 01
01 TJ to 0 01
o. to O O
01 co B O
im X e» O ki
it u e si a.
i

01
cc

01 X
CO to

tk,

t o

>o.Mu

tn
9
kl
19

CO HI
Id O
U

O) kl

I M

t v,
O

"' IS -»
pa

i£s8
83

-H
to
>
to
B
3

r H

i n

TJ 01
B rH
CO

3 "

B -H k.

CO kl
n cj to
x* -M X
tl kl
01 to
O 0 CO

01 ci
TJ -H
o
>
U 01

8
h
ki sn

> k l r H CO
01 3 t

tun

01 01 0)
O rH TJ
■H JO N*
> 10 CO
01 > 01
TJ O kl
a
e oi a
01 ki 0)
kl B kl
CO O CO

>. B >,
tn *t ra

k l

kl
•
3 TJ
JO 4)

kl
•H

t l

01 O.—1
01
ki
01
Ol J B V
TJ U H H
TJ -H
r H k l a . CO CO B CS
0)
01 O
X
c
k >

?
«8 ■
01 CD oiH

o
I M

k l

Cl
Ol
L.

t i

01
k l

oc
IM

k l

c i 01
Ol

j :
k i

r H
01
X i

o
B

r H

tn
tO

01
J9
to

r H

0)
k i

tn
ki

a jp

t i TJ
0)
C O C l kMl -•H
rt
o
c IM

•rt

ty
to
nH
01

B
6 u
Cl
nH
■0 01 •M
oo
a
0> Ol
at -( co eg a tj tj

-rt

(Continued)
ytSS^K

2-38 NOS Version 2 Analysis Handbook

Revision M

Recovery Functions

Table 2-3. Mass Storage Device Recovery (Continued)

B
e
k>
Cl

m
ki
e
0)
O
k,
o
ki
ki
Ah
e
(M
JJ
W
01
CO
0)
0)
CB
kl
ta
oi
tj
m
co
Ss
0>
>
«S
3
>>
CO rH -1 0) 00 10
H
bll
TJ
-rt
Ck
B
tl
IM
IM
•
co
o
oi
o
e
o
tj
rt
O
k,
O
91
TJ
kl
rH
O
kl
kl
CD
O
U
to
0)

n
e
a
m
xE
l, ea
tdrst n
ert on
lct.

HTJTJC0

S K
03

r4
eu
CB
•rt
TJ
Z
Cd

m
orferl e
n
d
fir ho
ctm
tan
ge
o
ce
lr
O

_T J
>MI T
H
IB
CO
N -ol k i g l
o
tn
ki
b
oi
o O kl
X
*
10
CB
r
-4
tX
to
01
01
©
CO
*,
kl
IMO
to
to
-t
IC
a
X r H
CO
E
CO
01
o>
ti
01 kl
CIC93
01
H
0)
Ml.
k l
> k.
N-i
3
e
o
oi
>
sn
O TJ OJ e)
TJ
ki
k,
cn
Cl
Mb]
01 01 r H k l
ECOlM
00
E
O
Ort
ki X TT 0)
n-i
M
SJ
EOk,
l-l
nJ
O
T J
0>>H
HUB,
Z
h
T J C O C CB
41
»
O
k l 01 01
TJTJCO
Oklkl
tt]
O
k l Ot TJ
O
S
rt
rt
X
ki
C£
>
>
« CO
O
tO
rt
00
CO
O
h
-rt
kl B
Cl
O
rt
kl
DC
(ki
01
01
Ih
ti
Cl
w
i<
n
KU
(J
M ta x
0
O
--•
TJ
10
n£
<
0 ) ■H »
ki
U
>
01
0)
10
U
b
||
X
X
«
CO 01 TJ H kl TJ
T J

k l

k l
M
t o

o
u
Ol
01
B

C k
CD
01
OS

e
0 )
k l
CR

. >.
CR

•
6

kl
01

H
kl

CO TJ Cl
kl
CO
CA O

01
9>
nH
k l
t>
CO

k.
NH
01
£
kl

-4 01
H
>
to CO •
X cn
kl
CJ
a to -t
jr oi >H
kl O OS
01 41 CO
E TJ 0)
3
Cl
tt 01 o
ih
g
CO JP
CO M

ra > ci

•rl O
E
kl 01
im k.

91
k.
Ti
TJ

01 OS
41 rH 3
Cl TJ kl
-h
c
W
> N-l kl
01 Ck 0)
TJ
CO
-rt
zj
6
41
O
TJ kl N-i O M kl
C
rH
91

r
TJ
nH
rt

k J f B r J O l O l S t T J t Q

Q rt ri 91 >
TJ H JP oi kl J<
o i c o e o t o j p t s c i o i
CU
CH
OJ
|l
b
k.
HHH
U£
It
3
B
f*.
CO
(J
kl H UH > 01 0! >s
01 H CO X 0) B CU
M t t u e P t i o x
3 01 3 rt X kl
CU
kl
Ck
>
kl
U
IS

tO
01
kl
•
41
tM
k l I M « »■. T J 4 > n H
CO
rH
01
H
u

sr. ti h co oo to oi
ti
rt
X
X
6
C
NH rt IC Bl Nrt TJ H
BBHHBE
cj
B
3
H
nH
rt
e
ti
tax
at
cs
h
oi
— ' N H u U k i E n k i
h
bH
O
II
ll£
II
< o 3 Q. tn k. u tj

•

01
Cl

a0 1
MH

0
01
CL
>s

01
>
•
-rt
01
kl
0)
CJ
H
II

k)
kl

-rt
B
M

Exam
nehit ertd
a
e
fad: com
eietp
tl vceo
irct

91
c
»)
rt

01
>
NH
kl
CJ
CO

«-«
CO
ttl
rH
H
IM

tt
>

it
Cl

B
01

m
R
eo d
e
rt

ki
O
u
u
t o
I M
c
B
O
H
U
Ou
>M
M
Cl
01

£
IM <-l
0 k,
to
-4 kl
OJ 01
5> TJ
01 <0
J 01

o
B
0

k l
Cl
c
3

9*.
u
o>

>
o
o

01
oc

Nonr m
ero drei

01
OS

•
M
»
fl
k,
CO
-"•
o
Li
m
k.
k>
ta
r
^
|0
U 3 TJ hni
ii
o.k
a
Cl
«!
>
M
o
Tl
«
II
•
|l£
tl
kl
IM XI X CJ TJ kl —i CM o
H
-i
TJ
C
l i H U C t n t O C O T

01
J P

ki
Cl

CO
>

nhuoi

><
C
(
UU
Or1
b
co x co o tn c ra
HHTJ
«
U
—1
3
QJ
iM
H
U
il
ft
Jl
II
3
Hjhh
u
C O X O O B E S S u h
j
h
utiiNH
3
e
jj
o

k.
O
ki
k,
01

01
H
TJ
E
-H
B.

c ec cn
O E rt 01
rt H u jp
kl E Tt
te h 3 ki
ci te b o
rt
E
c
IM 01 IM
rt ti O t)
k.
H
r
Oi 6 tn 3 TJ
> O 0) O 0>
h
ci
h
H H TJ nW
11 O C J l r l
JP JP rt Cl M
tr B Cl. CO 41
_3 _i id a >

fvl

-*
H
01
*
te
h
tj
.-»
Cl
H
TJ
•
OJ
TJ
—
rt
A")H
C
II
ll
«
1
CC
OiSOHrtHEBOl
U
41
>»
klO-rt9
0.0.3rtrtt5
o
—.
jr
tn
e
o<»
too
t.
X
CL
^bCCIrtOeniCU
'3
rex tr. -H o M 41 u c ^ X —' 4) 41 « > —i
O
-t
>
91
O
t
—
1-3
XCO
Cl
B.
C
e
3
rt
X
0—'
1
ocun
io-h
t.
en
3
s
e>
^
■
it
iu
uh
oixm
OICIErt-H^-^-.
«rt
>I-HHS)H
E O 01 h CM 00 J 3 <— 01 tO TJ C
rtrttnual
QOJ^rt-BWBtirt
tO > C H CvM
CO 0)
UJ k.

tl
rt
>
01
TJ

E O "C
T, i J C
oi tj
41 01
Cl 00
rt C
> te
01 X
tj ci

a
K
rt
ki
rt
3
e

(Continued)

Revision M

Deadstart 2-39

Recovery Functions
.-^mu.

Table 2-3. Mass Storage Device Recovery (Continued)

i n
S*
W

01 00 CO

tn H 00 rt
9 . > 6 kl
< Q 4) rt O
Om O TJ 03 rt
k i I M 0 13 4K1

I
H

rH
rt
IM

kEl
OH
fO
4)
•
N
rt
Q
kl
CO
•
»H
B
CO
>i TJ TJ rrt Sd t, O
CO Ol SI CO ti 01 H
« 01 ti rt 01 a
© O 01 kl kl 41
O O kl rt CJ — X

ij «e e •

u 6 e fl rt

01 O. 01 H a 4) H
5.
ti
x
h
ts o co a eg B

rt tj »
01 CO
O . S U
Ck CB rt
CO rt CB

a x

01 CO

00 rt 00

co
tj ret
CO
a oi co

4] rt CO

fod

O
rt
kl
Cl

01 TJ kl 01

rt
B
a)
X
W

ti
41
ki
>M
10

01
kl
si
rt
O.

H
kl
tl
41
ti

SI
H M
0 1 rt
> H

oi a

TJ 01

e rt
C
B

00
OS l - l
CO
CO

O
(9

u
tin
u
oi
3
ra
tv
O kl rt U —X t3 r3
kl C B S H 3r,C0tO
01 Cl 4) rt al 41 rt li oi-nn
CL
ti
X
rt
kl
TJ
U.

E
b
O rt

H TJ
01 B
Oh 03

rococo te a Tt e si o.

(rtklrtH

•X
eo

0 O CJ
co ci
00 B O

01
ol ci
TJ rt
O 8>
U
V
TJ
ki

O kl kl
rt X ti

k, f-l

bIS

fH
CO

5 8

( H

o—

"to 2*

O
C
H

O.H

Cd 01 03
I
^
_
rt
t k i _o >.
ki oi

qj kl TJ 4)
H 6 B 00

IM
CO
CO Ih im
CO O O <-*
0) UH CO 01 H O
6
w
0a
rt
Ck a k, oi uh

co
us
01 !». 00 TJ
X to E 6
kl H rt CO kl
a
n
4 1 O H ta cs rt eo a o w
B H tO Ck kl CO E TJ 01
rt TJ UJ B 0 3 > » h o ) t o t l
01 TJ H H 01 4> rt
co se oi kk ll 0C)O B« 3C Br t 0T1 J Hr t 0 >1
X -X
W W k l < TJ IB UH ti UH TJ

. 2

co
, ki

rt
kl

I M

O H kl
UJ ti CO
TJ
01 01 03
X X 01
H kl TJ

bl CO 01
u kl
Ol co ol
X TJ TJ

tip •
• ki C B

O kl kl
rt X Ih

rt CO

B 0 01
a a
00 6 o
B 0 U
t\ ti eu

• Ol 00 CO -n.
tH
Cl
B
01
Oh
CO rt 00 rt rt 0u • kl
S •> C kl rt CO TJ rt
t
r
N
rt
CO
kl
a
ki
CO • -t, B 09 CO kl kl
>• TJ TJ rt CO E O U C
l A O I S I C O l H O I H a c O O l
» OJ kl rt J) Ci. « kl

kl S»
09 01
TJ TJ

M
O

a CB
r i
»
ri

B
O

rt 00 to

01 01 CB
X X 01
fH kl TJ

6. SK kl
a to rt
eg h to
a
x
a> a
00 rt oo
CB TJ 6
CB
rt
CO 01 CO
8 H O C0O1
CB Cl
00 B O
B O ti
rt ci a
3
O kl kl
rt X kl
H 00 CB
O r t M
Uh ti CO

• > to

sss

rt 00 to to,
OrtM

TJ
II 01 CB
X X 01
H kl TJ

O X
kl CO
II rt 09
H 3 01

rt
3

SHrt

CO
Cft V O t M
01 CO CO o
U 3 _ 10

u cb 3 m
3 Cl 41 kl
CO
01
TJ
k l X 10 01

o
B

tn X O T3 >
-n» 01 01

TJ 00 CB
ri B H

co 3 r t U J
a) S >»Nrt

kl «J rH ti TJ

Cl UH
Tt SN tkl
kl W Cl k, p
rt rt 01 kl CS

tj x a b Ou
W H « 41 <

eg b Ol ki 0)
CO TJ
TJ rt
01 5

2 -*

01 Ui
•H 01

II H

(Continued)

2-40 NOS Version 2 Analysis Handbook

Revision M

Recovery Functions

Table 2-3. Mass Storage Device Recovery (Continued)

TJ
B
Art

01
6

ti
CB
kl
Cl
X

ki
0)

Br
M
.«C

vi CQ
«
C9
H
01
01
OC
O
X
kl
O
O
rt
M
B
TJ
m
>
T34I
CO
HklCO
kl

.t fl

B
O
T i
14
U

•

O
Uj
U

ao.o

o
C
Uh

oic

s*xkirta
XBOOIHO
UVD,
QH

so)

•

oiskoo
tj
ti
<
Tt
>kixte
XCBBB
01
O
•
41
U
u
ki
rt
rt
to
m
•
in
k,
a
ki
tj
a
«~
art
tiO
oij^k,
ki
c
cc
I)
tO
H
M
O
rt
M
M
Cl
O
CO
I)
0TJ
TJnHT3HS>
X
-X
MSIBOIBOBCBOIrtCI
Cd
Id
kl
<
TJ
OH
(
II
O
UH
M
uh
TJ

«t

•
ca

CO
ti
03
01
a

t i
0
t i
b
b l

TO
B
CB
•
CO
Sk
kl

41
CO
B

o
14 •

a
SK
cn

O
uh
ti
91
a

O
rt
-i
O

3
O
H
rt
O
uh

kl
X
00
rt
k,
oi

O
Ih

ee
<
f_
CO
C
HS
bl
O

kl
li
«
kl
CO
TJ
CB

9 k

Ol
t i
B
O

k ,
Cd
UH

o
B
O

rt
k>
Cl
03
h

E
eg

•

E
o

O
rt

a cj x ai to

01
k l
II
TJ

•
li

rt
kl

O
t.

01
ey

Z
f

kl
kl

rt
-3

b a

M
0

b.
X
O

tj
6
te

te
rt
eg
B

•
«1
01
O

tl
T3
B
w
01 0

>
41
TJ

a
41
TJ
O
Cl
k,
O
M
Ih
bl

ki
01
to

01
3
kl
10
kl
09

art

—i
Uh
Sk
eg
TJ

01
O
rt
>

ti -4 UH
Cl
O
0
CO
cj
ca
cj
4'
w
k,
rt
U TJ 00 OJ rt
k.
6
X
uh

0) to 01 rt 0
B
kl
OOTJ
3
09
rt
tn
eg
cj
b
eo
8
TJ
01
tl
41
eg to cn oi oi ci
X
01
01
ki
X
Cl
bl
TJ
X
a
kl
OB

09
01
41
Cl
01
U
01
X
eg eo ki
t o
u
to
E
Cl
01
Tt
01
41
M
B
01
rt
rt

Uh
01

41
Ih

CO
I I
CJ

II
rt
bl
Uh
CO
(9K
td
10
r
S
TJ
kl
Ou
kl
•
CB
•
B
ti
01
R
CO
CO
3
0
X
C
BJ
OC
O
k.
kl
O
-H
O
Ok.
UH
-t
ot
«J
6
Uh
OC
kl
rt
00
Id

01
T J

U
M
CJ

6
rt

-rt

"
CB

OJ ti
O
41
-t
X

In
ki
V

01
3
b l TJ
SC

B
rt

>-•
b.

> B

09
OJ

co
(0
0
C7
41
01
H
to
-4
art

T J

BE
01

09
01

rt
nH

6 h a o
rt

41
T J

0 )
k l
CO
9 k
CO
B
O
Z

•

Jt
CO
X

<
- 4

•

Cl
rt
03

CJ
B

Ol
TJ
oi

o
B
J*
ci

eg
01 H

•
01

8
CJ
B

s»
01

U i

O
Id
>
OS

41
Cl

co oi a u Sk eg
-a o rt u a
01

B
5

kl
rt

01
B
ta

e
k,
M
oi

Uh
O

eg
rt

Cl
01
U

01
r
C
TJ
kl
kl
CO
rt
B
O
Ui
01
rt
II
eg
u
tj
li
01 01 E rt
II
rt
X
B
TJ

§ B*

B 41 01
O
k,
>

B Uh 41
O 9K 01 Uh X
Cl M k.
O
M

( M m
M
CO U4
01 O

01
S>

a oi o

o ..
-

ci tj oi g
rt TJ 8

CB
Cl
rt

03
UH

B
rt

Z
0.

01
H
Sk U 01 CB
H
Tt
Cl
Cl
r-i
>
^
^4
CO I) > kl

00
O
O
O
X
00
kl
h
ki
E
3
0
I.
rt CB
kl
li k. NH C
OJ O
O
rt
TJ
01
eg 01
M Uh
•
01
I
k,

OrtM
uh

TJ UH
B
O
to

01 Cl
k>
10 41

kl
X

a
TJ
eg
01
01 TJ

01
H
X
UH
M
B

SK
- 4
t,

01
kl Ol
B
00
3 CO
O ti
Cl
o

oi
X
ki

^rt

B
41
B
01 k, 01
kl
E
kl
B O O )
SK
6
9k
CO

CO
rt
TJ

eg
rt
>
Srt

Lo
eg
Ol
»

k l

a
o

CB
01
4J

•

l-l

k ,
O

4i
X

41
r t
X
«3
9>

ti
eg
ki
CO
TJ

41
oi

r
kl

01
Cl
- i

>
O
B

01 09
00 rt 00
tO
TJ
6
CO
rt
CQ 01 CO
41
H
D
B
O
01

B
O

O
••
00

_
Ort
kl

rt
CJ
SE
bl

01
6
O

CO
01
Cl
t.

01
UH TJ
UH
O TJ
TJ
01
E
B
rt
to
U
Ui
3
rt
kl kl Cl
ti
01
CB
9K
kl rt
to
CB
TJ
eg oi
Cl
X
CO
Ol rt
m
TJ
00
01
O
Ui
os H
O

B
TJ
tO
01
01
rt
TJ
II
Ui
4)

a oi o sp
cj h cb ty
00
B

>
O

TJ
Ol

09
01

rt
uh

Uh
O

CO
rt
00
TJ
6
rt

CO TJ
k,

01
00
CS
CO

Ol
X
ki

bl
h
rH
<
b.

a to h

O
M

ci
a
X
01
CJ

Brtki

41
Sk
U

TJKBSJSrQklknCI

01
B

B X -u rt B

CO
CO
kl
ai
e
CJ
O
l<
X
rt
oi
O
ki
>
X
II
kl
ki
E
TJ
01
rt
01
X
0
>
B
3 18 3 01

rt
X

10
eo

3
eg
0
3
kl
M
k.

oi
X
kl
01
>
CO

(-■ X 6 BOX

H
eg
00
01
—1
TJ
10
Oi
In
O
kl
01
ti
3
n«
rt
IB
bi

co ts
tc
ts
41
3
cl
Cl
ki
es
O
ui
•
41
kl
Cl
Ih
X 09 Cl II O
(rt rt 01 CO kl
k.
CJ
JS
rt
M
01
• Cl TJ CO 09
M
eg
u
O
ti
IM
rt
B
u
u>
O
ut
41
O
kl
4) 09 00 kl CO
CS 01 E 3 SK
U
nH
X
09
B
eg
E
01
U
C
B
10
M
rt
-i
nH
CO TJ 00 CB M
Sk
6
OJ
X
O
tn
nH
X
Cl
B
H
gC
H

Uh
0

kl
ti
t o
-4
kl
01 CO
>
TJ

0) a
01
e

-1

o
CJ

3
t k
S k
t i

a
>
o

>
Cl
01
Of

rt
B

01
n
a
in
CO
0)
3
II
a
ci
to
rt
B
rt
B
rt
> 01 UH
rt
O
•
rt
TJ
O
M
Sk
eg
ki
6
ki
01
01
rt
9k
00
B
6
li
uh to oi to eo
rt
kl
kl
fl
01
ti
O
09
t,
M
01 kl Sk 41 B
>
oo
eg
art

CB
u
<9
TJ

09
09

tl
Cl
O
Cl
rt
CB
t i
01 M
M
Cl
E
01
rt
k,
rt
r
b TJ 01
IB
01
01
kl
rt
H
O
H
CJ UH UH

(Continued)

/fF*>

Revision M

Deadstart 2-41

Recovery Functions

Table 2-3. Mass Storage Device Recovery (Continued)

3 01 X OJ DO
CO ki u B B

rt 9k 00 E k.
Uh
•O
H

TJ Ut
a
tl 10
01
ti
a- 3 Id TJ H
u c o O b l CO OS rH UJ
s a o i t l r O CO rH 3
S k H
Tt Cl O
09 rt kl Uh
oi
Uh Ih O
OJ 5k «
B eg ki ki 00
rt TJ D 01 O
UK
09 B O
co s at
X O 01 3
. -■h - S h u ,

B to

E
0

8 rt
CO

01
H
00 rt
CO UH

S""B
C

3
0

9k
eo

H
0

TJ
B

Oi
O
PC
DC

to
Z

T *

rt
r H
UH

00H

U i

OJ
IH
01
W
B
3
0
Cl
B
01

X
01
TJ
B
rt
ti
01
09
S>

k,
01

M
B

ti
k.

01
T J

ti Tl
O H
6 Ui

- CO
O 01

a cj

I H r t 0)
rt
0 k l
T J U H CO
9 k
Uh
1 ) CO
O
X
01
ki
k l
3
•
O S>
CJ k.

jj w
eg
B

rt X TJ O

Id 01 ki
S X CO t - i

rt TJ ti k,
9k O TJ B ki 01

i u
t i
i u
01

11
rH
Tt

•

X
Uh

b l
r J
X

rt
UH
TJ

09
eg

3
rt
01 Uu
6
TJ

bl
to
to

rt u. t;
. * * * ^ k
rt

ca
eg

B 0*
3 O
0 OC
Cl PC

b l

41 0 )
0 0
eg
09 UH
09 9k

rt TJ

co bl
&

b
E
3 SP

I I
B O H
6
rt
NH UH
3
9k

O OJ
uh X

0 O
Cl CJ
9 k
I h
OJ

ki ec

in o

OJ oc

O-oc

Id b.

k l
41
NH
Uh T J
0 )
>H
01 CO
t l
r H
^ H
a i d UH

09 f«J
14
CO
T J

r n

u h

k l

k l
. X
Cl 0 3 Cl
0
OJ
- 4
in
t i
01
k i
k l r H
B NH
M
U h rH

01
eg

T O
u u bi
CO 41

(Continued)

2-42 NOS Version 2 Analysis Handbook

Revision M

Recovery Functions

0ms
Table 2-3. Mass Storage Device Recovery (Continued)
JtrW^K.

kl TJ
O 01

td 0 01
N 6 >

01 Tl
ti Uh
ti
Tt

O Cl
Cl 01
41

rt
kl

•

CJ
01
9k C 41
Uh
rt
X
rt
X
kl
Ih CJ

O
ki
eg
bl O O CJ
Oj UH H TJ
41 01 H
B B C eg
3 rt rt —
Ot X X Ul

41 eg B
> B rt

(J rt
• gC l es
E

eg •
CB
Sk M
a -H
rt eg
CO

eg ki bl cj
b CO es

rt
9k
U
Uh
01 nH
X
Cl
M
01

essB

■MTJ 4i
O SB Ou k,

ti eg tj X
II II Cu
Ou tj eg o

06
b l
CB

rt
3

CJ
O

W
X

TJ
01 oi eg
X X oi

U.
cs

TJ
01 01 CO
X X 01
H kl TJ

TJ b
01 01
U X
01 M
kl o
B C

Ut
O

8§■

kl rt
09
3 09
Cl rt

01
r t
tO

CO SK
B
UH TJ

oi to
60 rt 00

OJ
09
Cd
0C-rt 00
03 TJ C Z

CO CJ
6
O

6 O li
rt ci a
3
O M M
H
X
b
h 00 eg
O
UH

H
M
U CO
TJ

01 Ol eg
X X 01
kl

a
ts
eg
h

•
h
to

<■
9 "

ib l

oc
oc
S 3
C J

>
O

c
in
b
to
Oi
6 .

O
td

2.sk2 §
f-

B 41
>t at

4J ttl
Pu TJ

tn tj
b
C
eg
to

b
O

bj h m
B o oi

z
U3

b cn
01 O

—t
01

CO TJ
b
B
cb eg •
41
cs
a 9k ki
a ts rt
<0 rt eg

k i

II
U
B
tl
rt 01
X
M
Cl
ti

CB TJ 6
CS
rt
09 II CS

O
kl
kl
P O
rt X k. Z U.
rt 00 CS bl
OrtM
UH
M

es TJ B
09
rt
9co oi co oc
CJ
rt
o
o
fl
O
41
X
00
BOM

O
M
kl
H
X
ti
H 00 CS
O r t M
UH ti CS

cj
<.
cc
h

ax
co
09
<
00 rt oo J

PS
O 0
M
ci

rt a eg o
bl co B u si a

a
tj
MB
eg
a
r
«,
cs
a sk m
rt

oi
UH

•
01

00 h
E
X
01 *rt

£S

H X

CB Uh rt
bi
•
kl
rt
01
C O T J r. c
TJ
M
rt
03 IB O X E X
01
C l 3 Cl
tj oo 0 eg b to
41 E rt 6

03 01 CO
Jl o
H 0o3i
a
eo ci

Z ki t<
m o eg
H
oi
01 X H cs
> M 01 01
ci rt a E
rt
3
H

a x

eg tj c
a
rt

(-.

T t

b l

BJ S3
00 rt CO

B
rt

CS TJ
ti
B

eg
0)
O.
a
eg

TJ
II

ki
es
B 01 CB
01 X 3

o
u

H
H

O CO Uh CO
rt
TJ

4J
<

-t

O H kl kl
BJ O O kl
41 E eg
B
S.
kl

kl cs u
t, td
ki
q

41
I I

S"s

41 TJ
> 01

c
o

Jlu

TJ
oi oi eg
X X OJ
h
"TJ

k u

eg rt as

a x

oi cs
60 rt 00
eg tj E
CS
rt
CS OJ CS
OJ rt CS
B O 01
to Cl
00 B O
E O b
rt ci a

a eg rt

id
H

cs bj tn
oj
rt
in
o
BOO)
bl
in
o
z
00 E O rn
E
O
b
U.
rt
ci
a
id
3
O
O
ki
ki
Z
rt X b 5
rt 00 10
OrtM
©

tj
B
eg r
a
5 k m

9 -

os •
o to

X ot

S i

a td
t d

O M 14
h je b
h oo eg

S OC

§b i £r t

f PC
X <
bl 0.

O r t M
Uh
b
6S

TJ
Oi oi eg

X X bj

H kl TJ

2.
> K

T J
01
T J

T J
41
T J

TJ
Ol
TJ

T J
01
T J

01
M

41
k l

01
14

X
b l

X
bl

X
I d

X
b l

T J
01
T J

t i

t i
k l

o
B
o

NH
k l

b
Cl

cc
h

UH
O
H

01
6

CS
OJ

CJ rt 8
tj X eg
rt cl b
81 ts Uh
41

B
M Sknh
Cl k. X
CB Q kl
M B rt

t
00 eg
9k E 1
ti
O

rt
E

B rt >

E u

TJ O eg .
01
ci
-i
UH

rH
TJ

41 TJ E 01
X 41 3 6
IB TJ O rt

Ol eg rt
B M M

-4

es
m
rt
B
rt

E oi O 3
01 rt im
ki X es
X es d m
Cd M rt rt

Hr.
TJ
rt

M
*

kl
O

41
M

rt oi B 01
eg
tj
>

o eg I.
ui 3 a

,-.

T J
01
.
kl
01

Cl to
01 3
01 E
CO rt

01 *
B CJ
rt td

Cl oc

£5

oi a
> TJ
o to

E
Q
1)
M

tS
X

a x m
ca oi b co
HE

oi rt

X to
In B

iiE'Srt
O
X
ra C c ci
IS X O 03
X CO rt B
k l

9k b 3 b
b II Cl OJ
O X Ol X
8 ul X kl
01 rt 41 O
B
01
B
01 CB
TJ
-X
II TJ kl E
TJ
01
O
6 00 9k
01 C X to
s a rt k i e g I d
O 01 X X X b £
Uh a H 01 Cl O X

01
01
rt 01 TJ 14
II
X
H
CS
E TJ M 09 Cl
rt OJ OJ rt
X E E b TJ
Cl
rt
rt
B
eg
to
9srt
a m tj b
C C o to

E kl
01 3
JC Cl
CO 01
M

B
rt
03
09
01

01 Cl
09
U
eg o to
3

kl
rt
X
01

00
6
rt
M

b
O
b
b
Id

o
rt
U
Cl

a 3

fl
b
01 ki
M CS
M
6
S3 rt

T J
41
T J
CJ

C l

r t

ti
M
CB
kl

eg u «h
3 TJ X kl
g]

O
J

9 k
M
M
6

r t

^cj
B
O

T t

u
Sl

3
Pw
9k
b
01

>
o

tl
01
BJ!

Revision M

rt
kJ

2 at
B B
uh rt
01

9k
k.
01
>

B
eg •
Ih 1)
UH o

o e. rt

Cl rt >
01 S3 1)
O f fl T J

Deadstart 2-43

Error Idle Recovery

Error Idle Recovery
Setting the device error idle status helps to prevent error propagation by inhibiting
new file assignment on the device and by inhibiting any new PFM, PFLOAD, or
QLOAD activity from occurring on the device. The error idle status is indicated by the
EI error code on the E,M display. Error idle status is set when:
• Mass storage read or write errors occur in the catalog or permit chains.
© There is an incorrect user index in the permit sector.
® Direct or indirect access files are too long or too short.
Correcting the error idle condition requires total initialization of the affected device.
This can be accomplished online for a removable device, but must be performed during
a level 0 deadstart for a nonremovable device. Suggested recovery procedures follow.
Removable Device
1. Dump inactive queued files, if present on the device (QDUMP).
2. Dump permanent files (PFDUMP).
3. Perform a total initialization of the device (INITIALIZE,AL,est.). If the error idle
status was caused by a mass storage error, the appropriate track should be
flawed.
4. Reload inactive queued files, if applicable (QLOAD).
5. Reload permanent files (PFLOAD).
Nonremovable Device
1. Dump queued files (QDUMP).
2. Terminate any dayfiles that must be saved (DFTERM).
3. Dump permanent files (PFDUMP).
4. Idle the system and perform a level 0 deadstart.
5. Perform a total initialization of the device affected by the error idle condition
(INITIALIZE,AL,est.). If the error idle status was caused by a mass storage error,
the appropriate track should be flawed.
6. Reload queued files (QLOAD).
7. Reload permanent files (PFLOAD).

2-44

NOS

Version

Analysis

Handbook

Revision

Deadstart Decks
CMRDECK
Central

jp^

..
Memory

....
Descriptions

3-2
3.3

EQPDECK
3.13
D a y fi l e
Descriptions
3_jg
General Description of Equipment Assignment Entries . 3-18
Clear
EST
Assignment
Entry
........
3-18
Equipment
Assignments:
Nonmass
Storage
3-21
Nonstandard
Equipment
EST
Entry
'.[]
3-21
Pseudoequipments
3_22
Unit
Record
Equipment
EST
Entry
3-23
Magnetic
Ta p e
Equipment
EST
Entry
.....
3-27
Mass Storage Extended Subsystem EST Entry ... 3-30
Stimulator Equipment EST Entry ... .... .' 3.31
Network
Processing
Unit
EST
Entry
3-32
CDCNET Device Interface EST Entry .'!."".!!.!!!!!...'..'.'!.'.'!!!! 3-34
Network
Access
Device
EST
Entry
3.35
Two-Port
Multiplexer
EST
Entry
3-36
MAP
III
or
IV
Equipment
EST
Entry
3-37
6683
Satellite
Coupler
EST
Entry
..
3-38
CYBERPLUS
Ring
Port
EST
Entry
...'.
3-39
Equipment
-Assignments:
Mass
Storage
3-40
NOS
Mass
Storage
Concepts
3-41
Alternate
System
Device
3-41
Alternate
Permanent
File
Family
3-44
Auxiliary
Device
,
3.45
Family
Device
3.46
Link
Device
3-46
Master
Device
..
3.46
Multispindle
Device
3-48
844
Expander
....
3.48
Nonremovable
Device
3.54
Removable
Device
..
3-54
Shared
Device
3.54
System
Device
3-54
Te m p o r a r y
File
Device
....
3-54
Buffered
Disks
.,-.
3-55
Extended
Memory
Overview
...........
3-56
Physical
C o n fi g u r a t i o n
3-56
Logical
C o n fi g u r a t i o n
3.57
C M a n d U E M S i z e S p e c i fi c a t i o n a n d D e t e r m i n a t i o n 3 - 5 9
S i m u l t a n e o u s U s e o f Tw o Ty p e s o f E x t e n d e d M e m o r y . . . 3 - 5 9
Specifying
Ranges
of
EST
Ordinals
3-6O
-ESQ
—
Disk
Equipment
EST
Entry
3-60
EQ
—
Control
Module
EST
Entry
3-66
EQ
—
Extended
Memory
EST
Entry
3-68
Examples of EQPDECK Entries for Extended Memory 3-72
Single
Mainframe
Examples
3.72
Multimainframe
Examples
3.75
MSAL — Mass Storage Allocation Control Entry 3-78
DOWN
—
Down
Channel
Entry
3-80
UP
—
Up
Channel
Entry
3-80
PF — Permanent Files Device Assignment Entry 3-81

^ %

S Y S T E M — S y s t e m L i b r a r y D e v i c e A s s i g n m e n t E n t r y . - . . .■ 3 - 8 5
ASR — Alternate System Library Device Assignment Entry 3-86 ^v
SGKP — System Checkpoint File Device Assignment Entry 3-86 f
FA M I LY — D e f a u l t F a m i l y N a m e A s s i g n m e n t E n t r y . 3 - 8 7
REMOVE — Removable Device Assignment Entry 3-87
SHARE — Shared Deyice Entry ......... .. .. 3-88
ISHARE — Independent Shared Device Entry 3-89
LBC
—
Load
Buffer
Controllers
Entry
3-90
XM — Declare Extended Memory Space for Buffers or User Access 3-92
UEMIN
—
UEM
Equipment
Initialization
3-93
ACCESS
—
Set
Access
Level
Limits
,
3-94
THRESHOLD
—
Set
Disk
Thresholds
3-95
EQPDECK Entries Made Only During Deadstart 3-96
AUTOLOAD
—
To g g l e
Autoloading
3-96
GRENADE — Clear Unit Reservations ....... 3-96
INITIALIZE
—
Initialization
Entry
...
3-96
PRESET — Preset the Link Device Entry . 3-101
PRESET — Preset the Independent Shared Device Entry ... 3-102 ^^
RESET
—
Reset
Device
Attributes
3-102
^
APRDECK
3-103
APRDECK
Format
,.
3-103
CAF
—
Clear
All
Flaw
Reservations
..
3-104
SLF — Set Logical Flaws on Any Mass Storage Device , 3-105
CLF — Clear Logical Flaws on .Any Mass Storage Device 3-105
SPF .— Set Physical Extended Memory Track or Disk Area Flaws 3-105
CPF — Clear Physical Extended Memory Track or Disk Area Flaws 3-106
IPRDECK
.
,
3-107
Job
Control
Information
.......
3-108
Job
Scheduling
....
■. . . . .■
3-108
Control
Points
...
•
•
•
3 - 11 0
Pseudo-control
Points
......
..
3 - 111
Number of Control Points and Pseudo-control Points Available ............ 3-111
Memory
Control
.
•
•
•
•
•
•
3 - 11 2
Example
of
Job
Control
Parameters
3 - 11 2
I P R D E C K E n t r i e s M a d e O n l y D u r i n g D e a d s t a r t . 3 - 11 8
COMLIB
3 - 11 8
CPM
.
■•■
■•
3 - 11 8
CSM
•
3-121
DISK
VA L I D AT I O N
.,
3-121
DSD
...
•
•
•
3-122
EI
...............
.3-123
EOTJSNDED
S TA C K
PURGING
3-123
HARDWARE
FA U LT
INJECTION
3-123
KEYPM
3-124
MEMORY
CLEARING
3-124
MICRO
.
.......
3-125
NAMIAF
-..
3-125
PROBE
3-125
SCP
•
3-126
SCRSIM
3-126
S E C C AT S
3-127
SPC
3-127
SPD
3-128
SPL
3-128
SPW
3-128

^ s '

SUBCP
3_12o,
TCVM
3_129
TDEN
3_130
TDTR
•
•
3_130
™S..3-131
TMSTO.
3-131
TRACE
3-132
IPRDECK Entries '.[ .. .][[......... .....'.. \..' 3.133
Subsystems
3
233
A U TO R E S TA RT
'.'.'.'.'.'.'""
"
*
"
3.136
C A RT R I D G E P F S TA G I N G . . . . . . . . . . . . ' . ' . . . . . . . . . . 3 - 1 3 6
GLASS
3^37
CPTT
,.
3-138
DEBUG
3.138
D E L AY
.
3_139
DDP
ROLLOUT
PAT H
"*."".
"
3.140

dfpt.

M ^

..;;;;;:::;:;

ENGR
FLEXIBLE
PA RT I T I O N S
LOCK
.'....'..'.'.'.'.'.'.'.'.'.
LOGGING
MASTERMSE
'
'"
'"
MS
VA L I D AT I O N
.
"
*'
OQSH
PCLASS
PF
VA L I D AT I O N
PRIVILEGED
A N A LY S T
MODE
PRIVILEGED
RDF
QUEUE
.....'
R E M O VA B L E
PA C K S
RESIDENT
RDF
SECONDARY
USER
COMMANDS
SECURES
SERVICE
SPINDOWN
SRST
SYSTEM
DEBUG
TA P E
PF
S TA G I N G
UNLOCK
USER
EXTENDED
MEMORY
,..,..
LIBDECK

3-uo
3_U1
3-141
3-142
3.142
3.143
3.143
3.144
3.144
3.145
3-145
3-146
3.146
3-148
3.449
3-149
3-150
3-151
3-156
3-156
3-157
3-158
3-158
3-158
3-159

0ms

Deadstart Decks
Deadstart decks are text records that reside on the deadstart file. This section
describes the following deadstart decks.
Deck

Description

CMRDECK Central memory resident deck.
EQPDECK Equipment deck.
APRDECK Auxiliary mass storage parameter deck.
IPRDECK System installation parameter deck.
LIBDECK System library deck.
This section contains detailed information about how you can modify the released
versions of the deadstart decks.

jg^S

Revision M

Deadstart Decks 3-1

CMRDECK
/*s%

CMRDECK
The central memory resident deck (CMRDECK) resides on the deadstart file as a text
record that is processed during system initialization. It contains entries defining the
following types of information.
• Central memory.
• Table sizes.
• Configuration information not oriented to equipment.
The deadstart file can contain up to 1008 CMRDECKs. Having several CMRDECKs on
the same deadstart file is advantageous because one file can deadstart several
configurations. You can obtain a listing of all CMRDECKs by accessing the system file
SYSTEM with an ASSIGN or COMMON command, then using the T parameter on the
CATALOG command (refer to the NOS Version 2 Reference Set, Volume 3 for more
information concerning these commands). CMRDECKs are named CMRDnn, where nn
is from 00 to 778.
You can modify the released settings of the CMRDECK in two ways: type a new
entry when the CMRDECK is displayed during deadstart, or create a new deadstart
file. The usual method of modifying a CMRDECK follows.
1. Deadstart, using the released deadstart file, and select the CMRINST and the
CMRDECK to be displayed (refer to section 2, Deadstart).
CMRINST lists all valid CMRDECK entries. Default values, described in this
section, are assumed if the entries do not appear in the CMRDECK being used. If
either CMRDECK or CMRINST overflows two screens, you can page the display.
2. Modify the released version of CMRDECK by entering the changes or additions
from the system console while either the CMRDECK or CMRINST is displayed.
Each console entry supersedes the value currently specified in the CMRDECK (or
the default value).
NOTE
The modified CMRDECK remains in effect only until the next deadstart is
performed, except for a level 3 deadstart. That is, changes to the CMRDECK are
not recovered across level 0, 1, and 2 deadstarts unless a new deadstart file is
created to reflect them.
3. To expedite subsequent deadstarts, modify the CMRDECK on the deadstart file
using SYSGEN (refer to the NOS Version 2 Installation Handbook).
When constructing or modifying a CMRDECK, separate parameters with commas and
terminate each entry with a period. When an error exists in an entry in a CMRDECK
on the deadstart file, the CMRDECK is displayed and the error is indicated. This
occurs even if you do not select the display CMRDECK option.

'^H,

3-2

NOS

Version

Analysis

Handbook

Revision

Central Memory Descriptions

Central Memory Descriptions
The general function of central memory description entries is to assign the amount of
central memory to be used for central memory resident (CMR) and the amount to be
used for job processing. The simplified relationship is: the more central memory that is
assigned to tables in CMR, the less is available for job field lengths.
If you will run only a few batch jobs, fewer control points may be required. Thus,
you could decrease the control point area in CMR, which requires 2008 words per
control point.
The following entries are specified in the SET program with the released default
values listed.

Entry Format
/ms.

BSP=option.

Released
Default Value

Significance
Specifies whether NOS should build the SCI
parameter table. If the table is built by NOS,
then one copy of SCI services MDD mode and the
NOS/VE console in a dual-state environment.
NOTE
For compatibility, if NOS 2.6.1 level 700 is run in
a dual-state environment with a NOS/VE system
which is pre-1.3.1 level 700, then you must enter
the BSP entry in order to use MDD.

Revision M

option

Description

If Y is specified, the SCI parameter
table is built in the NOS CMR.

If N is specified, the SCI parameter
table is not built in the NOS CMR
unless the NOS console is a CC598B or
CC634B. In this case, the table is
always built.

Deadstart Decks 3-3

Central Memory Descriptions

Entry Format

Released
Default Value

C LT = n u m b e r 0

Significance
Specifies the octal number of common library table
(CLT) entries allowed. The number can range from
0 to 1008.
If the table exists, the first entry is reserved for
the system; so you should equate CLT with the
number of entries you want, plus 1. For example, if
you want three entries, enter CLT=4.
Common library table entries are described in the
IPRDECK entry COMLIB.
The dedicated fault tolerance (DFT) entry specifies
whether to run DFT in dedicated mode or in
nondedicated mode. In dedicated mode, the DFT PP
is loaded during the NOS deadstart process and
DFT resides in the PP for the life of the system.
Dedicated mode allows the halt-on-error hardware
feature of the model 990 to be used. It also results
in capturing the relevant data about hardware
errors closer to the actual point of failure. In
nondedicated mode, DFT is called to process
mainframe errors when necessary.

DFT=mode

mode Description

EJT=number.

6208

If D is specified, DFT runs in dedicated
mode. DFT also runs in dedicated mode if
the VE CMRDECK entry is specified (other
than VE = *).

If N is specified, DFT runs in nondedicated
mode (unless the VE CMRDECK entry is
specified).

Specifies an octal number of entries for the
executing job table (EJT). The system uses the EJT
entries to keep track of executing jobs.
The maximum value for number is 7777s; the
minimum value is 3.

EQP = number.

Number of
CMRDECK

Specifies the number of the EQPDECK to use at
deadstart. The EQPDECK contains equipment
assignments. Up to 1008 EQPDECKs can exist on a
deadstart file; the number can range from 00 to 77s.
If an EQP entry is not included in the CMRDECK,
the system uses the EQPDECK with the same
number as the CMRDECK being used.

3-4 NOS Version 2 Analysis Handbook

Revision M

Central Memory Descriptions

Released
Entry Format Default Value Significance
FNT=number. 23s

Sets the octal number of entries allowed in the
system file name table (FNT). The system FNT
contains the system file and all fast-attach files.
Determine the necessary number of FNT entries by
using the formula:
number = SY+RS+(VL+PR)*FM+SFA

Va r i a b l e D e s c r i p t i o n
SY

Number of system files.

Number of resource files.

Number of VALIDUs files per family.

Number of PROFILa files per family.

Number of families that can be active at
any one time.

SEA

Site defined fast-attach files.

For a system installed with the released defaults
and with no additional files added to the system
FNT by local code, the maximum number of FNT
entries necessary is 2018.
The maximum value for number is 7777s; the
minimum value is 3.
FOT=number. 108

Sets the number of entries in the family ordinal
table (FOT). Each family is allowed one entry in
the table. The first entry in the FOT is reserved for
system use. The system uses family name and user
index for job ownership and file routing. The family
ordinal is a 6-bit number that corresponds to a
particular family name. The FOT maintains the
family name to family ordinal relationship. If a
family is unloaded and later reloaded, it continues
to use the same family ordinal.
The maximum value for number is 100s; the
minimum value is 3. The size of the FOT need not
be the same for each mainframe in a
multimainframe environment.

Revision M

Deadstart Decks 3-5

Central Memory Descriptions

Released
Entry Format Default Value Significance
INB=number 0

Specifies a block of memory for site use. The size of
the installation block can range from 0 to 77778
central memory words.

I P D = n u m b e r. F i r s t
IPRDECK on
deadstart file

Specifies the number of the IPRDECK to use at
deadstart. The IPRDECK contains installation
parameters. Up to 100s IPRDECKs can exist on a
deadstart file; the number can range from 00 to 77s.
If an IPD entry is not included in the CMRDECK,
the first IPRDECK on the deadstart tape is
processed and is not displayed.

LDT = number. 0

Specifies the number of central memory words
allocated to the LID table. The minimum value is
0; the maximum value is 16610s. The value to be
specified can be determined by using this formula:
(3+lid)*pid

Parameter Description
lid

Maximum number of LIDs allowed
per PID.

pid

Total number of PIDs in all networks
defined on this mainframe.

One central memory word is always allocated for
the LID table header.
As an example, assume lid = 5 and pid=6. By using
the formula, you come up with (3 + 5)*6 = 48. Adding
one word for the LID table header makes 49, or
618, central memory words that should be allocated
to the LID table.
LIB = number. 0

Specifies the number of the LIBDECK to use at
deadstart; the number can range from 00 to 77s.
LIBDECK is a directive record used by SYSEDIT.

MID=id.

Specifies the 2-character machine identification (id)
that is associated with the mainframe. The id
characters must be alphanumeric.

jr«£-fflroSv

3-6 NOS Version 2 Analysis Handbook

Revision M

Central Memory Descriptions

Entry Format

Released
Default Value

MINCM = size. 14008

Significance
Reserves an amount of central memory to be used
by NOS when running in dual state with NOS/VE.
The VEMEM utility can help you determine how
NOS and NOS/VE will share central memory (refer
to the DUAL installation procedure in the Special
Product Installation Information chapter in the NOS
Version 2 Installation Handbook for more
information about VEMEM). (UEM is defined in the
extended memory equipment EST entry). The
remaining central memory is available for use by
NOS/VE. Use the VE CMRDECK entry to reserve
central memory for NOS/VE if UEM is defined. The
minimum and default value for size is 1400s.
Parameter

Description

size

The size of central memory to
reserve in words/1008. Size is a 1- to
4-digit octal value (1- to 5-digit octal
value for a model 865, 875, or
CYBER 180-class machine) that
restricts the actual central memory
size. The value cannot be 0 and
cannot exceed the total number of
words of memory present in the
machine. Refer to table 3-1.
Size CM Words CM Words
(Octal) (Octal) (Decimal)
1400
140000
2000
200000
3000
300000
4000
400000
6000
600000
10000 1000000
14000 1400000
20000 2000000
24000 2400000
30000 3000000
34000 3400000
40000 4000000
44000 4400000
50000 5000000
54000 5400000
60000 6000000
64000 6400000
70000 7000000
74000 7400000
100000 10000000

Revision M

49152
65536
98304
131072
196608
262144
393216
524288
655360
786432
917504
1048576
1179648
1310720
1441792
1572864
1703936
1835008
1966080
2097152

Deadstart Decks 3-7

Central Memory Descriptions

Entry Format
NAME=date
line.

Released
Default Value

Significance

NETWORK
OPERATING
SYSTEM

Specifies the system date line, which is displayed on
the system console display and on the terminal
when an interactive user logs in to the system.
Parameter Description
date line Alphanumeric string; must be fewer
than 39 characters. If the date line is
not terminated with a period, one
will be appended. If the date line is
38 characters, the last character
must be a period.

NCP = number. 12s

Sets the number of control points available for job
processing. Refer to Job Control Information later in
this section for a discussion of the proper number of
control points to select.
Parameter Description
number

3-8 NOS Version 2 Analysis Handbook

Number of control points available in
central memory; number can be from
2 to 348.

Revision M

Central Memory Descriptions

Released
Entry Format Default Value Significance
PCP=number. 0 Sets the number of pseudo-control points available
for job processing. Refer to Job Control Information
later in this section for a discussion of the proper
number of pseudo-control points to select.
Parameter Description
number Number of pseudo-control points
available in central memory; number
can be from 2 to 34s.
OPSECM = n. 0 Specifies the operating system security mode. The
site security administrator supplies the value for
this entry. Refer to the NOS Version 2 Security
Administrator's Handbook for information on this
entry.
n

Description

0 or Sets the system to unsecured mode,
omitted
1 Enables multilevel security. The values oft
the system access level limits can be set |
by the SECURES IPRDECK entry or by |
the console command. The SECURES
console command can be used to raise or |
lower system access level limits.
2 Enables multilevel security. The values oft
the system access level limits are set by I
the SECURES IPRDECK entry. The
SECURES console command can be used |
to raise but not to lower system access
level limits.
3 Enables multilevel security. The values of|
the system access level limits are set by |
the SECURES IPRDECK entry only; the j
SECURES console command is not
allowed.

Revision

Deadstart

Decks

3-9

Central Memory Descriptions

Entry Format

Released
Default Value Significance

PPU=ppi,
PP2,...,PPn.

All available
PPs are active

/«^!\

Toggles the active status of the physically available
PPs except for PPs 1, 2, and 10, which are always
active. Active means the PP is available for system
use; inactive means it is not available for system
use. The PPU entry is not in the released
CMRDECK; therefore, all available PPs are active.
PPU is a toggle entry: each entry changes the
active status of the PPs.
Parameter

Description

ppi Number of the PP; from 0 to lis and
208 to 318. Specifying an asterisk (*)
on the entry instead of ppi toggles
the status of PPs 20s to 31s.
This entry may be useful if PP memory is failing
or if a channel is causing problems on its associated
PP. For example, the following entry deactivates PP
3 and PP 4 (assuming no other entries have been
made for PP 3 and PP 4).
PPU=3,4.

QFT = number. 620s

Sets the number of entries allowed for the queued
file table (QFT). The system uses the QFT to
manage all files in the input and output queues,
number is a 1- to 4-digit number from 3 to 77778.

^ftsj.

1. APP that has been turned off by CTI is physically unavailable and cannot be turned on by the PPU
entry.

3-10 NOS Version 2 Analysis Handbook

Revision M

Central Memory Descriptions

Entry Format
VE = integer.

Released
Default Value

Significance
Reserves an amount of central memory to be used
by NOS/VE when running in dual state with NOS.
The VEMEM utility can help you determine how
NOS/VE and NOS will share central memory (refer
to the DUAL installation procedure in the Special
Product Installation Information chapter in the
NOS 2 Installation Handbook for more information
about VEMEM).
If you want to run NOS/VE in dual-state mode and
you do not have UEM (specified by either the
extended memory equipment EST entry or XM
EQPDECK entry), enter VE = 0 and use the MINCM
entry to reserve an amount of central memory for
NOS.

If you want to run NOS/VE in dual-state mode and
you have UEM, you must enter VE = integer to
reserve an amount of central memory for NOS/VE.
The memory is reserved even when NOS/VE is not
running.
Use VE = * if you do not want to run NOS/VE in
dual-state mode.
On a dual-CPU 830 machine, NOS automatically
disables processor 1 at deadstart time if there is no
VE = * entry. This is done because NOS/VE does not
support dual state in both processors. For all other
CYBER 180 machines, NOS uses only processor 0.

Revision M

Parameter

Description

integer

Octal number divided by 1000s of
central memory words to reserve for
NOS/VE when you have UEM. If you
do not have UEM and want to run
NOS/VE in dual-state mode, use the
MINCM entry and VE = 0 entry.
Refer to table 3-1 for a list of
memory sizes. NOS/VE requires at
least 6.5 megabytes of central
memory.

Deadstart Decks 3-11

Central Memory Descriptions

Entry Format
VERSION=name.

Released
Default Value

Significance

NOS 2.5.3
688/688

Specifies the system version that is displayed on
the system console display.
Parameter Description
name

Alphanumeric string; must be
fewer than 18 characters. If name
is not terminated with a period,
one will be appended. If name is
17 characters, the last character
must be a period.
The operating system version
number should be in character
positions 5 through 7 of the name
parameter, since the value in
character positions 5 through 7 is
available to users through the
symbolic name VER.

Table 3-1. Table of Central Memory Sizes

CM Size1

CM Words
(Octal)

CM Words
(Decimal)

lMbyte/128K
1.5Mbyte/192K
2Mbyte/256K
3Mbyte
4Mbyte
5Mbyte
6Mbyte
7Mbyte
8Mbyte
9Mbyte
10Mbyte
11Mbyte
12Mbyte
13Mbyte
14Mbyte
15Mbyte
16Mbyte

400000
600000
1000000
1400000
2000000
2400000
3000000
3400000
4000000
4400000
5000000
5400000
6000000
6400000
7000000
7400000
10000000

131072
196608
262144
393216
524288
655360
786432
917504
1048576
1179648
1310720
1441792
1572864
1703936
1835008
1966080
2097152

CM Words
(Hexa
decimal)
20000
30000
40000
60000
80000
OAOO00

ocoooo

OE0O00
100000
120000
140000
160000
180000
1A0000
1C0000
1E0000
200000

CM Bytes
(Decimal)

CM Bytes
(Hexa
decimal)

1048576
1572864
2097152
3145728
4194304
5242880
6291456
7340032
8388608
9437184
10485760
11534336
12582912
13631488
14680064
15728640
16777216

100000
180000
200000
300000
400000
500000
600000
700000
800000
900000
0A00000
0B00000
0C00000
0D00O00
0E00000
0F00000
1000000

1. K is 1,024 60-bit words. Mbyte represents megabytes. One megabyte is 1,048,576
8-bit bytes, which is equivalent to 100,000 hexadecimal 8-bit bytes or 131,072 60-bit
words.

3-12 NOS Version 2 Analysis Handbook

Revision M

■'*:^%\

A*^*S

EQPDECK

EQPDECK
The equipment deck (EQPDECK) resides on the deadstart file as a text record that is
processed during system initialization. It contains entries defining the following types of
information.
• Dayfile buffer size.
• Hardware configuration.
• File residence on mass storage devices.
• Permanent file family residence.
• Multimainframe configurations.
• Software attributes associated with hardware (such as forms code).

An EQPDECK entry is described under the type of information it defines.
The deadstart file can contain up to 100s EQPDECKs. Having several EQPDECKs on
the same deadstart file is advantageous because one file can deadstart several
configurations. You can obtain a listing of all EQPDECKs by accessing the system
file SYSTEM with a COMMON command, then using the T parameter on the
CATALOG command (refer to the NOS Version 2 Reference Set, Volume 3 for more
information concerning these commands). EQPDECKs are named EQPDnn, where nn
is from 00 to 77s.

rYou can modifyentry
the when
released
the EQPDECK
settings isofdisplayed
the EQPDECK
during deadstart,
in two orways:
create type
a newadeadstart
new
file. The usual method of modifying an EQPDECK follows.
1. Deadstart, using the released deadstart file, and select the EQPINST and the
EQPDECK to be displayed (refer to section 2, Deadstart).
EQPINST lists all valid EQPDECK entries. Default values, described in this
section, are assumed if the entries do not appear in the EQPDECK being used. If
either EQPDECK or EQPINST overflows two screens, you can page the display.
^^ 2. Modify the released version of EQPDECK by entering the changes or additions
from the system console while either the EQPDECK or EQPINST is displayed.
Each console entry supersedes the value currently specified in the EQPDECK (or
the default value).
NOTE
The modified EQPDECK remains in effect only until the next level 0, 1, or 2
deadstart is performed. That is, changes to the EQPDECK are retained across a
level 3 deadstart, but not across a level 0, 1, or 2 deadstart (unless a new
deadstart file is created to reflect them).
3. To expedite subsequent deadstarts, modify the EQPDECK on the deadstart file
using SYSGEN (refer to the NOS Version 2 Installation Handbook).
Several equipment status displays are available during deadstart (refer to section 2,
Deadstart).
jp*.

Revision

Deadstart

Decks

3-13

EQPDECK

.■^%j.

When constructing or modifying an EQPDECK, the following restrictions apply:
© The equipment assignment entry (EQ) must precede any other assignments for a
device (such as assigning it for permanent file, system, or temporary file use). If
you redefine the EQ entry (by clearing the entry and retyping a new entry or by
changing the device type in the entry), reenter all other assignments for that
equipment. If you need to modify an EQ entry, you need only enter the changes
rather than reentering the entire entry. You do not need to reenter other
assignments for that equipment. This is especially useful for changing channels or
units and for reconfiguring around hardware malfunctions.
Example:
The following mass storage assignments are in the EQPDECK.
EQ7=DI,ST=ON,UN=60,CH=1.
PF=7,F,125,125,SYSTEM,3,200.

If you want to specify unit 70 rather than 60, you need only enter:
EQ7=DI,UN=70.

You.do not need to modify the PF entry.
• EST ordinals range from 1 to 777s. This range depends on the value of ESMX
(refer to PPCOM parameters in the NOS Version 2 Installation Handbook).
Ordinals 1 through 4 are reserved for pseudoequipment EST entries that are
automatically defined by the system and cannot be changed. Ordinal 5 is reserved
for extended memory if it is used as a link device in a multimainframe
environment (refer to EQ - Extended Memory EST Entry later in this section).
Otherwise, EST ordinal 5 can be used for any equipment type.
• The device from which you are deadstarting must be defined.
• Commas must separate parameters.
• A period must terminate each entry.
• Except where explicitly specified that controllers and/or equipment can be shared
between mainframes, assume they cannot be shared. For example, NOS does not
support sharing a two-channel tape controller between mainframes; nor does it
support sharing mass storage controllers, except as specified in section 13,
Multimainframe Operations.
When an error exists in an entry in an EQPDECK on the deadstart file, the
EQPDECK is displayed and the error is indicated. This occurs even if you do not select
the display EQPDECK option or if you enter GO after displaying the EQPDECK.

3-14

NOS

Version

Analysis

Handbook

Revision

Dayfile Descriptions
J^S.

J^S

Dayfile Descriptions
One of the functions of dayfile description entries is to assign the amount of central
memory to be used for buffers. The more central memory assigned to dayfile buffers in
CMR, the less central memory available for job field lengths.
If, for example, you need a large portion of central memory to run a job, it might be
advisable to decrease the size of the dayfile buffers area in CMR to accommodate that
job. However, when dayfile buffers are smaller, the information stored in them is
written to mass storage more often, which requires more system overhead.
The following entries are specified in the SET program with the released default
values listed.
Entry Format

Released
Default Value

ACCOUNT=est,length. 400s

Significance
Sets the residence of the account dayfile
and the length of the account dayfile
buffer.
The account dayfile is an accounting
record containing information such as
type and quantity of resources used, and
job and execution times. This account
information is written to the central
memory account dayfile buffer during job
processing; the central memory buffer is
written to mass storage when it is full.
The account dayfile buffer resides in
CMR in the dayfile buffer area.

Revision M

Parameter

Description

est

The 1- to 3-digit octal
equipment status table
(EST) ordinal of the
equipment on which the
account dayfile is to
reside. A null value means
the system uses the first
system device it can find.
If the existing account
dayfile is recovered, the
account dayfile buffer
resides on that equipment
and the est parameter is
ignored.

length

The 3- or 4-digit octal
length of the account
dayfile buffer in CMR;
must be a multiple of 100s
and less than or equal to
10008. If 0 (zero) is
specified, messages issued
to the account dayfile are
discarded.
Deadstart Decks 3-15

Dayfile Descriptions

Entry Format

Released
Default Value

DAYFILE=est,length.

400s

Significance
Sets the residence of the system dayfile
and the length of the system dayfile
buffer.
The dayfile buffer contains the dayfile
information, which is maintained in the
same way as the account dayfile buffer. It
resides in CMR in the dayfile buffer area.
Parameter

Description

est The 1- to 3-digit octal EST
ordinal of equipment on
which the dayfile is to
reside. A null value means
the system uses the first
system device it can find.
The residence of this dayfile
is normally determined by
the recovery of the existing
dayfile. Use this parameter
if no system dayfiles are
recovered.
length The 3- or 4-digit octal
length of the system dayfile
buffer in CMR; must be a
multiple of 100s and less
than or equal to 10008. If 0
is specified, messages issued
to the system dayfile are
discarded.
ERRLOG=est,length.

1008

Sets the residence of the error log and the
length of the error log buffer.
The error log is a record of hardware
error and status messages. This
information is maintained in the same way
as the account dayfile buffer.

3-16 NOS Version 2 Analysis Handbook

Parameter

Description

est

The 1- to 3-digit octal EST
ordinal of equipment on
which the error log is to
reside. A null value means
the system uses the first
system device it can find I f
the existing error log is
recovered, the error log
buffer resides on that
equipment and the est
parameter is ignored.

Revision M

Dayfile Descriptions

0$ms

Entry Format

Released
Default Value

ERRLOG=est,length.
(Continued)

Significance
Parameter

Description

length The 3- or 4-digit octal
length of the error log
buffer in CMR; must be a
multiple of 100s and less
than or equal to 10008. If 0
is specified, messages issued
to the error log are
discarded.
MAINLOG=est,length. 1008

yfP^N.

Sets the residence of the binary
maintenance log and the length of the
binary maintenance log buffer. The binary
maintenance log is a record of hardware
diagnostic information.
Parameter

Description

est

The 1- to 3-digit octal EST
ordinal of equipment on
which the binary
maintenance log is to reside.
A null value means the
system uses the first system
device it can find. If the
existing binary maintenance
log is recovered, the binary
maintenance log buffer
resides on that equipment
and the est parameter is
ignored.

length

The 3- or 4-digit octal
length of the binary
maintenance log buffer in
CMR; must be a multiple of
1008 and less than or equal
to 10008. If 0 (zero) is
specified, messages issued to
the binary maintenance log
are discarded.

j0m\

Revision M

Deadstart Decks 3-17

General Description of Equipment Assignment Entries

S^^S

The general format of the EQ entry is:
EQest =type,keywordi=valuei,... ,keywordn=valuen.

Keyword=value entries are order independent.
Depending on the type of equipment being defined, certain keywords are required,
while others are optional, as shown in table 3-2.
You can redefine an EST entry by entering an EQ entry for the EST ordinal with a
different equipment type. This action clears the original entry before creating the new
entry. You can also modify an EST entry by entering an EQ entry with the same
equipment type and only the keyword(s) you want changed.
Clear EST Assignment Entry
Use the following entry to clear an assignment that currently exists for an EST -*a%.
ordinal. Clearing the assignment does not clear flaw entries for that equipment. The
EQest=0 entry is not required when you are assigning the EST entry to a different
type of equipment.
EQest=0.
or
EQest=.

Parameter Description
est EST ordinal of the equipment; est can be from 5 to 777s.

3-18

NOS

Version

Analysis

Handbook

Revision

Clear EST Assignment Entry

Table 3-2. Required and Optional Keywords
Equipment
Type

Required
Keywords

Optional
Keywords

EQ,CH

ST,IB

EQ,CH

CW,IB

EQ,CH

ST,ID,FC,IB

EQ,CH

ST,ID,IB

UN,CH

ST,AP,IB

UN,CH

ST,AP,IB

ST,MA,ET,

UN,CH

ST,AP,IB,AP,MC,IB

ST,AP,IB

UN,CH

ST,AP,IB

UN,CH

ST,AP,IB

UN,CH

ST,AP,IB

UN,CH

ST,AP,IB

UN,CH

ST,AP,IB

UN,CH

ST,AP,IB

EQ,UN,CH

ST,AP,IB

SZ,CH

ST,MA,ET,AP,MC,IB

UN,CH

ST,AP,IB

0m*s,

00&S

(Continued)

Revision M

Deadstart Decks 3-19

Clear EST Assignment Entry

Table 3-2. Required and Optional Keywords (Continued)
Equipment
Type

Required
Keywords

Optional
Keywords

UN,CH

ST,AP,IB

UN,CH

ST,AP,IB

EQ.CH

ST,ID,FC,TN,PS,IB

EQ,CH

ST,ID,FC,TN,PS,IB

EQ,CH

ST,ID,FC,TN,PS,IB

EQ,CH

ST,ID,FC,TN,PS,IB

ST,IB

EQ,UN,CH,TF

ST,IB

ST.IB

EQ,CH,PI,ND,NT

ST,IB

EQ,CH,PI,ND,SA

ST,IB

EQ,UN,CH,TF

ST,IB

CH,PT

ST,IB

EQ,UN,CH

ST,IB

EQ.CH

ST,PT,IB

WI
>^^.

3-20

NOS

Version

Analysis

Handbook

Revision

Equipment Assignments: Nonmass Storage
y^s

Equipment Assignments: Nonmass Storage
The following EST entries are described in this subsection.
Nonstandard equipment
Pseudoequipments
Unit record equipment
Magnetic tape equipment
Mass Storage Extended Subsystem equipment
Stimulator equipment
Network processing unit
CDCNET device interface

yfPN

Network access device
Two-port multiplexer
MAP III or IV equipment
6683 Satellite Coupler
CYBERPLUS ring port equipment
yams

Nonstandard Equipment EST Entry
The nonstandard equipment EST entry allows you to define nonstandard equipment or
to add site debugging modifications.
Use the following format to enter the actual octal value that is to reside at that EST
ordinal.
EQest=**,Wo=valueo,Wi=valuei

Parameter Description
est

EST ordinal of the equipment; est can be from 5 to 777s.

valuei

The 1- to 20-digit octal value; this value is entered in the EST word i
for the specified ordinal. The word is right-justified and zero-filled if
valuei has fewer than 20 digits.

Revision M

Deadstart Decks 3-21

Pseudoequipments

^ms
Pseudoequipments
The system automatically defines EST ordinals 0 through 4 as pseudoequipment EST
entries; they cannot be used for other equipment definitions. You cannot declare,
change, or remove pseudoequipments.
EST Ordinal

Description

Ordinal 0 (RD)

This ordinal reserves an EST entry and MST entry to be used for
device reconfiguration.

Ordinal 1 (DS)

This ordinal represents the system display console.

Ordinal 2 (NE)

The system uses 2 internally to signify that a file is assigned, but
that no space exists on the device. If a read is tried,
end-of-information (EOI) status occurs. If a write is attempted, the
data is discarded.
For example, you can use ordinal 2 with the permanent file utility
(PFDUMP) to validate the integrity of a permanent file device,
without taking the time to actually create a dump file on tape. In
this case, enter:
X.DIS.
ASSIGN,NE,TAPE.
PFDUMP.

This causes all dump data to be discarded, even though the
permanent file device is read and informative messages about the
permanent file device are issued to the system console. These
messages are described in the NOS Version 2 Operations Handbook.
Ordinal 3 (TE)

If an association is established between file name and volume serial
number with an ASSIGN, LABEL, REQUEST, or VSN command,
the system automatically enters EQ3 in the file's FNT/FST entry.
When a tape having the desired volume serial number is assigned
to the file, the system replaces EQ3 in the file's FNT/FST entry
with the EST ordinal of the tape unit on which the tape is
mounted. If a file that has had the file name and volume serial
number association established by a VSN command is returned
prior to attempting to assign the tape equipment to the file, the
FNT/FST entry is canceled.

Ordinal 4 (TT)

The system assigns to this equipment a file used for either input
from or output to an interactive terminal. This allows the system
to determine whether a file requires the special handling needed to
accomplish terminal input/output. Byte 4, set by the NAMIAF
IPRDECK entry, contains the number of network terminals.

3-22 NOS Version 2 Analysis Handbook

Revision M

Unit Record Equipment EST Entry

Unit Record Equipment EST Entry
A unit record equipment EST entry defines channel connected card readers, card
punches, and line printers.
Unit record equipment connected to RHF or PSU through communications ports are
defined in the network configuration files rather than with individual EST entries.
EQest=type,ST=status,TN=tn,EQ=eq,CH=ch,lD=id,FC=fc,PS=ps,lB=ib.
or
EQest=type-P,ST=status,TN=tn,EQ=eqfCH=ch,ID=id,FC=fc,PS=ps,IB=1b.
Parameter Description

est EST ordinal of the unit record equipment; from 5 to 7778.
type Unit record equipment type; NOS supports the following unit record
equipments.
type Equipment
Card reader
CR 405-3447/3649
Card punch
CP 415-3446/3644
CP 415-30
LR
LS
LT
LX

Line printer
580-12
580-16
580-20
5870

P Specifies that a 580 printer is equipped with a programmable format
controller.

Revision

Deadstart

Decks

3-23

Unit Record Equipment EST Entry

Parameter Description
TN=tn

Print train for local batch line printer; from 1 to 7. NOS supports the
following print trains.
tn

P r i n t Tr a i n D e s c r i p t i o n

0 595-1/596-1 CDC graphic 63/64-character set.
1 595-1/596-1 CDC graphic 63/64-character set.
4 595-6/596-6 ASCII graphic 95-character set or ASCII graphic
63/64-character set.
5 595-5/596-5 ASCII graphic 63/64-character set.
6 595-6/596-6 ASCII graphic 95-character set.
7 595-6/596-6 ASCII graphic 95-character set or ASCII graphic
63/64-character set.
If you set a nonsupported print train value, tn defaults to a supported
value. If you omit tn or specify 2 or 3, the actual value of tn is 1.
If an invalid external characteristic (EC)2 is specified, the queued file
processor cannot output the file. The following shows which files will
print and which files will not print for a given print train selection.

ST=status

Print Train
Selected

Will Print File
With Specified EC

Will Not Print File
With Specified EC

None, B4, B6

A4, A6, A9

None, B4, B6

A4, A6, A9

None, A4, A6, A9

B4, B6

None, A4, A6

B4, B6, A9

None, B4, B6, A4, A6

None, B4, B6, A4, A6,
A9

Specifies whether unit record equipment is available for system use;
enter oms of these values:
status

Description

ON Unit record equipment is available.
OFF Unit record equipment is ignored during system operation.

2. Refer to the NOS Version 2 Reference Set, Volume 3 for a discussion of-the ROUTE command EC
parameter.

3-24 NOS Version 2 Analysis Handbook

Revision M

Unit Record Equipment EST Entry
0^*S.

Parameter Description
r

EQ=eq Controller number for equipment; from 0 to 7. To determine the number
for most unit record equipment, look at the dial switch on the controller.
To determine the equipment number for an LX printer, use the following
equation:
eq * 2 + 1 = addr

where addr is the 5870 host address obtained from the 5870 installer.
CH = ch Number of channel to which unit record equipment is connected; from 0
to 138 and from 20s to 338.
NOTE
If you want to use a card reader to perform a coldstart on a 66x tape
controller, the card reader must be available on channel 12s, 13s,
328, or 338.
To ensure that all printers are restored to their original states (such as
8 lines per inch and auto page eject) after a master clear has been
issued, all unit record equipment should be available on dedicated
channels. If it is not, printers revert to 6 lines per inch, and no auto
page eject status after a master clear is issued.
ID=id The 1- or 2-digit octal numeric identifier assigned to the device; from 0
to 678. This id is assigned to any output created by a job. For card
readers, all jobs loaded from this card reader are assigned the
identifier id.
FC = fc The 2-character optional forms code assigned to a line printer or card
punch. If the forms code is not present, the forms code field is cleared.
The forms code must either be null (not specified) or in the range from
AA to 99.
NOTE
The forms code cannot be assigned to a card reader.

/$P^V

Revision

Deadstart

Decks

3-25

Unit Record Equipment EST Entry

Parameter Description
PS=ps

Paper size, L or S, for local batch line printer. Default is L.
ps Description
Long (11 inch) paper will be mounted.
Short (8 1/2 inch) paper will be mounted.

IB=ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

Examples:
EQ11=CR,ST=ON,EQ=4,CH=12.
EQ11=CP,EQ=5,CH=12,ST=0N.
EQ20=LR,ST=ON,CH=12,EQ=6,ID=15,FC=AA.
EQ21=CR,ID=15,ST=ON,EQ=7,CH=12.
EQ22=LT-P,TN=6,ST=0N,EQ=2,CH=12.

3-26 NOS Version 2 Analysis Handbook

/A^^^L

Revision M

Magnetic Tape Equipment EST Entry
Aims.

Magnetic Tape Equipment EST Entry
The released tape subsystem supports a maximum of 16 magnetic tape units. The
minimum number of magnetic tape units that NOS requires is one 639 667 669 677
679, or 698. The format of the entry is: '
EQest =MT-n,ST=statusfEQ=eq,UN=un,CH=ch1/ch2,TF=tf,IB=ib.or
EQest =NT-n,ST=status,EQ=eq,UN=un,CH=ch1/ch2,TF=tfIlB=ib.
Parameter Description

est EST ordinal of the tape unit; from 5 to 777s. Refer to the MT-n or
NT-n parameter.
MT-n Equipment type; MT specifies 7-track tape units, and NT specifies
or 9-track tape units, n is the total number of magnetic tape units
NT-n connected to the controller, from 1 to 20s for 677, 679, and 698 units
with a 7021-31/32 controller and from 1 to 10s for 667 and 669 units
with a 7021-21/22 controller. The system automatically generates n
EST entries with consecutive EST ordinals beginning with the ordinal
specified in the est parameter. The n units begin with the unit number
specified in the UN=un parameter.
For 639 units, n should not be specified; if it is specified, it should be
given a value of 0 (zero).
NOTE
To clear an MT-n or NT-n assignment, enter an EQest=0 entry for all
n units. For example, to clear EQ50 = MT-4,ST=ON,..., enter:
EQ50=0.
EQ51=0.
EQ52=0.
EQ53=0.

0ms

Revision

Deadstart

Decks

3-27

Magnetic Tape Equipment EST Entry

Parameter Description
ST=status Indicates whether the tape unit is available for access; enter one of
these values:
status Description
ON Magnetic tape unit is available for access.
OFF Magnetic tape unit is ignored during system operation.
DOWN All access to the magnetic tape unit is inhibited for the
operating system and user jobs. Specify DOWN if the
equipment is malfunctioning and access is not desirable or the
unit is to be used by NOS/VE in a dual-state environment
(669, 679, and 698 units only).3
EQ=eq Controller number for the tape unit; from 0 to 7. This number is usually
0 unless the controller is switched to a different number. Ask your
customer engineer for the correct number if you are unsure.
UN=un Number of the lowest numbered magnetic tape unit to be processed;
units must have consecutive physical unit numbers; from 0 to 7 for 667
and 669 units or from 0 to 17s for 677, 679, and 698 units. The unit
number is on the front of the tape unit, either as a switch or a label.
CH = chi Number of the channel(s) to which the tape unit is connected; from 0 to
138 and from 20s to 33s.
A controller can be connected to one or two channels, depending on the
controller model. However, a maximum of two channels can be handled
regardless of the number of controllers.

3. If a magnetic tape unit is accessible from more than one mainframe, concurrent use must be disabled by
one of these methods: set access switches on the tape controller so that only one mainframe can access the
unit at any time or make sure that the EST entry for each shared unit is defined as ON in only one of the
mainframes.

3-28 NOS Version 2 Analysis Handbook

Revision M

Magnetic Tape Equipment EST Entry

Parameter Description
0^&t

TF=tf Hardware features available. This parameter specifies the following
hardware characteristics of the tape unit(s) being defined; select one
option.
The following options apply to 677/679/698 units:
tf

Description

ATS The unit(s) being defined cannot process 6250-cpi groupencoded (GE) tapes. If the system detects a unit with this
capability, it automatically changes this value to ATSGE
or CMTGE, indicating the availability of the GE feature.
ATSGE The unit(s) being defined can process 6250-cpi GE tapes,
or Specify this value (ATSGE for 679; CMTGE for 698) only
CMTGE if a unit being defined has the capability of processing GE
tapes but is down. In such a case, the system would not
be able to connect to the unit to determine the
availability of the GE feature.
The following options apply to 667/669 units:
tf

Description

MTS The FCOs needed to implement the block identification feature
have been installed in the 7021 controller for the unit(s) being
defined. If the controller is a two-channel model, the block
identification feature must have been implemented on both
channels.
The following options apply to 639 units:
tf

Description

I S T S p e c i f y T F = I S T.
IB=ib The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

Revision

Deadstart

Decks

3-29

Mass Storage Extended Subsystem EST Entry

Mass Storage Extended Subsystem EST Entry
The Mass Storage Extended Subsystem (MSE) hardware consists of a 7991 storage
module and a 7990 controller.
A mainframe that runs SSSLV in slave mode must have an MSE EST entry, even
though no MSE hardware is actually configured for this mainframe. A mainframe
that runs SSEXEC in master mode must have an LBC EQPDECK entry with a
controlware type of N8 or M8 specified.
The MSE EST entry format is:
EQest=SS,ST=status,EQ=eq,UN=un,CH=ch,IB=1b.

Parameter Description
est

EST ordinal of the 7990 controller; from 10s to 777s.

Indicates a 7990 controller.

ST=status

Specifies whether the 7990 controller is available for use; enter one of
these values:
status

<^^Y

Description

ON 7990 controller is available.
OFF 7990 is ignored during system operation.
EQ = eq

Logical controller number.
This number sets the controller location in the unit device table within
SSEXEC's memory. Enter one of these values:
eq

Description
First 7990 controller.
Second 7990 controller.
Third 7990 controller.
Fourth 7990 controller.

UN=un

7991 storage module unit number; must be 0 (zero).

CH = ch

Number of the channel to which the 7990 controller is connected; from
0 to 138 and from 20s to 33s. You can specify up to two channels.

IB=ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

3-30 NOS Version 2 Analysis Handbook

Revision M

Stimulator Equipment EST Entry

0ms.
Stimulator Equipment EST Entry
NOS IAF supports a stimulator called STIMULA. However, there are other stimulators
such as PACER that can use this EST entry. (PACER is a product that can be ordered
from the Special Products Library.)
The format of the EST entry used by the interactive subsystem during stimulation is:
EQest=TT,ST=status>EQ=eq,CH=ch,PT=lines,IB=ib.

Parameter Description
est

EST ordinal of the interactive stimulator; from 5 to 7778.

Indicates an interactive stimulator.

ST=status

Specifies whether the interactive stimulator is available for use; enter
one of these values:
status

Description

ON Stimulator is available.
OFF Stimulator is ignored during system operation.
EQ = eq

Number of the controller; from 0 to 7. Refer to the description of the
channel parameter.

CH=ch

Number of the channel; from 0 to 13s and from 20s to 33s. The
channel/controller combination must not have any equipment attached
to it.

PT=lines

Number of lines to stimulate; from 1 to 10008. If this parameter is
omitted, 1008 is used.

IB = ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

0S^s.

Revision M

Deadstart Decks 3-31

Network Processing Unit EST Entry

Network Processing Unit EST Entry
A total of 16 NPU, MDI, and MTI ESTs can be available (ST=ON) at the same time.
The format of the EST entry is:
EQest=NP,ST=status,EQ=eq,PI=plp,CH=ch,ND=node,SA=sa,IB=ib.

Parameter

Description

^^^^

est

EST ordinal of the NPU; from 5 to 7778.

Indicates a 255x NPU.

ST = status

Specifies whether the NPU is available for use; enter one of these
values:
status

Description

ON NPU is available.
OFF NPU is ignored during system operation.
EQ=eq

Number of the controller for the NPU; from 0 to 7.

PI=pip

Peripheral interface program index, which determines which copy of
the PP driver drives this NPU; from 1 to 4. Up to four EST entries
can have the same PIP index (that is, one PP can drive a total of four
front ends consisting of NPUs, MDIs, or MTIs).

CH=ch

Number of the channel to which the NPU is connected; from 0 to 13s
and from 20s to 33s.

ND=node

Node number of the coupler associated with the NPU being defined;
from 1 to 3778. This value is the same as the NODE parameter on the
COUPLER statement in the network configuration file definition. For
the procedure to assign this value, refer to the Network Definition
Language Reference Manual.
NOTE
The node parameter is specified as an octal value on the NPU entry.
The NODE parameter is specified on NDL statements as a decimal
value.

3-32 NOS Version 2 Analysis Handbook

Revision M

Network Processing Unit EST Entry

Parameter Description
JpN.

SA = sa

System autostart module (SAM) flag (refer to CCP in the NAM Host
Application Programming Reference Manual). This parameter is required.
sa

Description

ON SAM is present on the NPU.
OFF SAM is absent. The host attempts to load the system autostart
module program (SAM-P) to the NPU if the NPU is down.
If an NPU is channel-connected to a single host in a single-host
network, the NPU does not need a SAM. However, if an NPU is
channel-connected to two hosts, the NPU should have a SAM; otherwise,
both hosts might attempt to reload SAM-P if the NPU is down. This
requires operator intervention to resolve the problem. The NPU EST
entries for both hosts should specify SA=ON.
IB=ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

Example:

/fP^V

Assume that three NPUs exist on channels 4, 5, and 6, all with controller 7. The
NPUs are connected to coupler nodes 2, 8, and 11, respectively. The NPU on channel
5 has a system autostart module; the others do not. The first two NPUs are to be
driven by the same PP. The EST entries for these NPUs follow.
EQ70=NP,ST=ON,CH=4,EQ=7,PI=1,ND=2,SA=OFF.
EQ71=NP,ST=0N,CH=5,EQ=7,PI=1,ND=10,SA=ON.
EQ72=NP,ST=0N,CH=6,EQ=7,PI=2,ND=13,SA=0FF.

The NDLP input for the network configuration would include the following statements
(refer to the Network Definition Language Reference Manual for a complete
description of these statements).
CPL1: C0UPLERN0DE=2,HNAME=H0ST1.
CPL2: C0UPLERN0DE=8,HNAME=H0ST1.
CPL3: COUPLERNODE=11,HNAME =HOST1.

The node parameter of the EST entry and NODE on the COUPLER statement have
the same numeric values, in this case 2, 8 (10s), and 11 (13s).

r
Revision M

Deadstart Decks 3-33

CDCNET Device Interface EST Entry

CDCNET Device Interface EST Entry
Each mainframe device interface (MDI) or mainframe terminal interface (MTI) in a
CDCNET network that is connected to a CYBER mainframe must have an EST entry.
A total of 16 MDI, MTI, and NPU ESTs can.be available (ST=ON) at the same time.
The format of the EST entry is:
EQest=ND,ST=status,EQ=eq,PI=pip,CH=ch,ND=node,NT=node,IB=ib.
Parameter Description
est

EST ordinal of the MDI or MTI; from 5 to 7778.

Indicates an MDI or MTI.

ST=status

Specifies whether the MDI or MTI is available for use; enter one of
these values:
status

Description

ON MDI or MTI is available.
OFF MDI or MTI is ignored during system operation.
EQ=eq

Number of the controller for the MDI or MTI; from 0 to 7.

PI=pip

Peripheral interface program (PIP) index, which determines which copy
of the PP driver drives this MDI or MTI; from 1 to 4. Up to four EST
entries can have the same PIP index (that is, one PP can drive a total
of four front ends consisting of MDIs, MTIs, or NPUs).

CH = ch

Number of the channel to which the MDI or MTI is connected; from 0
to 138 and from 208 to 33s.

ND=node4

Node number of the coupler associated with the MDI or MTI being
defined; from 1 to 377s.

NT=node4

Node number of the MDI or MTI; from 1 to 377s. This node number
identifies the Control Data Network Architecture (CDNA) transport
function.

IB = ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

The node numbers assigned to an MDI or MTI must be consistent with those assigned
to a 255x NPU network configuration defined through NDL. To minimize the impact on
existing 255x NPU networks, assign node numbers as follows:
1. Assign the lowest node numbers to NPU coupler nodes.
2. Reserve node numbers subsequent to those assigned in step 1 for NPU nodes.
3. Assign the remaining node numbers to MDI or MTI coupler nodes.
4. Reserve one node number to identify the CDNA transport function.

4. The procedure for assigning node numbers and creating network configuration file definitions is described
in the Network Definition Language Reference Manual.

3-34 NOS Version 2 Analysis Handbook

Revision M

Network Access Device EST Entry

Network Access Device EST Entry
The format for the network access device (NAD) EST entry is:
EQest=NC,ST=status,CH=ch,IB=ib.
Parameter Description
est

EST ordinal of the NAD; from 5 to 7778.

Indicates a NAD.

ST---status

Specifies whether the NAD is available for use; enter one of these
values:
status Description
ON NAD is available.
OFF NAD is ignored during system operation.

CH=ch

Number of the channel to which the NAD is connected; from 0 to 138
and from 20s to 33s.

IB=ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

j^S.

Revision M

Deadstart Decks 3-35

Two-Port Multiplexer EST Entry

Two-Port Multiplexer EST Entry
The two-port multiplexer (TPM) must be described in the EST to allow use of the
Remote Diagnostic Facility (RDF) on models 865 and 875 and CYBER 180-class
machines.
The format of the TPM EST entry is:
EQest=RM,ST=status,PT=pt,CH=ch,IB=ib.

Parameter Description
est

The 1- to 3-digit octal EST ordinal of the TPM; 5 to 777s.

TPM equipment type.

ST=status

Specifies whether the TPM is available for use; enter one of these
values:
status Description
ON TPM is available.
OFF TPM is ignored during system operation.

PT=pt

Port number to be used by RDF; 0 or 1. RDF normally uses port 1.
RDF and the system console cannot use the same port number.

CH=ch

Channel number on models 865 and 875 and CYBER 180-class
machines; channel 15 is required.

IB=ib

y=**ss$v

The 1- to 4-digit octal value;.this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

3-36 NOS Version 2 Analysis Handbook

Revision M

MAP III or IV Equipment EST Entry

MAP III or IV Equipment EST Entry
^PN

The MAP III or IV equipment EST entry allows use of the matrix algorithm processor
(MAP).
The format of the MAP III or IV EST entry is:
EQest=MP,ST=status,CH=ch,IB=ib.

Parameter Description
est EST ordinal of MAP; from 5 to 777s.
MP Indicates MAP equipment.
ST=status Specifies whether the MAP is available for use; enter one of these
values:
status Description
ON MAP is available.
OFF MAP is ignored during system operation.
CH=ch Number of the channel to which the MAP is connected; from 0 to 13s
and from 20s to 338.
IB=ib The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

Revision

Deadstart

Decks

3-37

6683 Satellite Coupler EST Entry

6683 Satellite Coupler EST Entry
The 6683 satellite coupler EST entry allows use of the NOS-SCOPE 2 Station Facility.
The format for the entry is:
EQest=CC.ST=status,EQ=eq,CH=chfIB=1b.

Parameter Description
est EST ordinal of 6683 coupler; from 5 to 777s.
CC Indicates 6683 coupler.
ST=status Specifies whether the 6683 coupler is available for use; enter one of
these values:
status Description
ON 6683 coupler is available.
OFF 6683 coupler is ignored during system operation.
EQ=eq Controller number for equipment; from 0 to 7.
CH=ch Number of channel to which coupler is connected; from 0 to 138 and
from 208 to 33s.
IB=ib The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

3-38 NOS Version 2 Analysis Handbook

Revision M

CYBERPLUS Ring Port EST Entry

CYBERPLUS Ring Port EST Entry
The CYBERPLUS ring port equipment EST entry allows use of the CYBERPLUS
Subsystem. The format of the entry is:
EQest=RP,ST=status,CH=ch,lB=ib.
Parameter Description
est

EST ordinal of the ring port; from 5 to 777s.

Indicates ring port.

ST=status

Specifies whether the ring port is available for use; enter one of these
values:
status Description
ON Ring port is available.
OFF Ring port is ignored during system operation.

CH=ch

Number of the channel to which ring port is connected; from 0 to 13s
and from 208 to 33s. This parameter is required.

IB = ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

0ms

Revision M

Deadstart Decks 3-39

Equipment Assignments: Mass Storage

Equipment Assignments: Mass Storage
This subsection describes the following EST entries and mass storage equipment
assignments.
Equipment

Entry

Disk equipment

Control module

Extended memory

Mass storage allocation control

MSAL

Down channel entry

DOWN

UP channel entry

Permanent files device

System library device

SYSTEM

Alternate system library device

ASR

System checkpoint file device

SCKP

Default family name

FAMILY

Removable device

REMOVE

Shared device

Independent shared device

ISHARE

Load buffer controllers

LBC

Extended memory allocation

UEM equipment initialization

UEMIN

Set access level limits

ACCESS

Set disk thresholds

THRESHOLD

3-40 NOS Version 2 Analysis Handbook

Revision M

NOS Mass Storage Concepts

NOS Mass Storage Concepts
( Following are descriptions that define the NOS mass storage terminology and
summarize the kinds of mass storage equipment assignments that can be specified in
the EQPDECK. Table 3-3 summarizes the various functions that a particular mass
storage device can serve. For example, if a device is an alternate system device (listed
under the Alternate System column in table 3-3), then it cannot be a system device; it
can contain temporary files, direct access files, and indirect access files; it can be a
master device or a nonmaster device; it cannot be removable; it can be either an
auxiliary device or a family device; and it can be a shared device or a link device.
Alternate System Device
Whereas a system device contains all the routines in the system library, an alternate
system device contains copies of selected system library routines. The ASR entry in the
EQPDECK (refer to ASR - Alternate System Library Device Assignment Entry later in
this section) specifies which mass storage devices are to be alternate system devices;
the *AD LIBDECK entry on the deadstart file specifies which system library routines
are to reside on these alternate system devices. During system processing, the routines
on the alternate system device are used instead of the ones on the system device.
This feature allows each routine in the system library to reside on the mass storage
device that is most appropriate to the routine's use. For example, instead of using an
844 system device, a routine that is frequently used could use extended memory,
which has a faster transfer rate, as an alternate system device.
NOTE
0ms
f Use care when specifying alternate system devices. A mistake could result in no
alternate system device defined. For example, suppose you specify the following in
your EQPDECK:
ASR=7.
ASR=11.

and you specify the following in the corresponding LIBDECK:
*AD,5,ABS/COMPASS
•AD.11.PP/1SJ

Since the system could not match equipment numbers between the EQPDECK and
the corresponding LIBDECK, the system library routine COMPASS will not be on
equipment 7 or 5. However, 1SJ will be on equipment 11 as specified.

Revision

Deadstart

Decks

3-41

NOS Mass Storage Concepts

Table 3-3. Mass Storage Functions for Various Device Types
Other
Possible
Functions
Alternate
system
device

,A*^S

Type1

Type2

System
device

Type3

Type4

Type5

Type6

Type7

Type8

Type9

Yes

m
m

Yes

Contain
temporary
files

Yes

Contain
direct
access files

Yes

Contain
indirect
access files

Yes

Master
device

Yes

Nonmaster
device

Yes

Removable
device

Yes

Nonremov
able device

Yes

1. System.
2. Alternate system.
3. Containing temporary files.
4. Containing direct access files.
5. Containing indirect access files.
6. Auxiliary.
7. Default family.
8. Shared.
9. Link.
(Continued)

3-42 NOS Version 2 Analysis Handbook

Revision M

NOS Mass Storage Concepts

Table 3-3. Mass Storage Functions for Various Device Types (Continued)
Other
Possible
Functions Type1 Type2 Type3 Type4 Type5 Type6 Type7 Type8 Type9
Auxiliary
device

Ye s

Family
device

Ye s

Shared
device

Ye s

Link
device

Ye s

Ye s
Ye s

Ye s

1. System.
2. Alternate system.
3. Containing temporary files.
4. Containing direct access files.
5. Containing indirect access files.
6. Auxiliary.
7. Default family.
8. Shared.
9. Link.

yf^V

Revision

Deadstart

Decks

3-43

NOS Mass Storage Concepts

Alternate Permanent File Family
More than one permanent file family can exist in a system: one default permanent file
family and one or more alternate permanent file families. One permanent file family is
defined as the default family by the EQPDECK FAMILY entry (refer to FAMILY Default Family Name Assignment Entry later in this section). If another system's
permanent file family is introduced, it is an "alternate permanent file family; it can be
added without interrupting the default permanent file family's operation.
This is a useful feature if a site has more than one system or has groups of
installations. If one system fails, its permanent files can be accessed from another
system.
As an example, a site with two systems might run with the mass storage
configuration shown in table 3-4.
Table 3-4. Mass Storage Configuration for Two Systems at One Site
Access
Used

System

Ordinal

Device

844

Direct access files

844

Direct access files

Spindles

Contents

If system Y became inoperative, the B access could be connected to system X. This
could be done without interrupting operations of system X.
The EQPDECK entries in system X would be:
Entries

Comments

EQ7=DI,ST=ON,UN = 0/l,CH = 0/3.

Defines access A.

EQ10 = DI,ST=OFF,UN = 0/1.CH = 1/4.

Defines access B.

REMOVE=10.

Allows introduction of access B into system
X during operation.

The EQPDECK entries in system Y would be:
Entries

Comments

EQ7=DI,ST=ON,UN=0/1 ,CH = 1/4.

Defines access B.

EQ10 = DI,ST=OFF,UN = 0/l,CH = 0/3.

Defines access A.

REMOVE = 10.

Allows introduction of access A into system
Y during operation.

3-44 NOS Version 2 Analysis Handbook

Revision M

NOS Mass Storage Concepts
0f&S

To allow for introduction of an alternate permanent file family:
1. Define the equipment to be introduced or removed in the EQPDECKs for both
systems (refer to the previous example).
2. Specify all of the equipment that may be introduced or removed during system
processing as removable.
3. When you want to introduce the equipment into a system, use the ON operator
command to indicate that the equipment that was set to the OFF position in the
system in.operation is now available. This introduces the alternate permanent file
family.
4. Enable the validation files for the family by entering X.ISF(FM=familyname).
Refer to section 20, System File Initialization.
Auxiliary Device
An auxiliary device is a mass storage device that is not part of a family. It is a
supplementary permanent file storage device, which may be privately owned (PRIVATE)
or may be shared by many users (PUBLIC). An auxiliary device resides on either a
removable or nonremovable device. On the permanent file entry (PF) for an auxiliary
device (for both a removable device and a fixed device without packs), a pack name is
specified instead of a family name.
Refer to the NOS Version 2 Reference Set, Volume 3, for additional information
about private and public auxiliary devices.
As an example, four 844 spindles to be used as a public auxiliary device could be
defined as follows:
EQ6=DI,ST=0N,UN=174,CH=2.
PF=6,X,name.

Private auxiliary devices can be created only after the system is up and running. An
operator can make a public device a private device by entering the INITIALIZE
command with the UN and TY=X parameters (refer to section 8, K-Display
Utilities).

Revision

Deadstart

Decks

3-45

NOS Mass Storage Concepts

Family Device

/^s

A family device is a mass storage device that is part of a family. It can be either a
removable device or a nonremovable device. The only difference between the two is
that a nonremovable device containing permanent files can also contain a copy of the
system library and/or temporary files. Refer to Alternate Permanent File Family earlier
in this section.
On the PF entry, the family name is important if two systems' permanent files are to
run on the same system. A user can only use one family of permanent files at one
time; if the user does not specify one, the default FAMILY entry is used.
A family device can contain direct and indirect access files. These files are defined in
the NOS Version 2 Reference Set, Volume 3. The files that are allowed are set by
the device mask and secondary mask on the PF entry.
Link Device
Either extended core storage or extended semiconductor memory or STORNET is the
medium through which several computer systems are linked to form a multimainframe
operating environment (shared MMF). The link device contains the information
necessary to manage the mass storage that can be shared by more than one
mainframe. For a description of shared mass storage, refer to SHARE - Shared Device
Entry and ISHARE - Independent Shared Device Entry later in this section.
Master Device
The master device contains all of the permanent file catalog entries, indirect access
files, and file permits for a specific user. If permanent file access is required, the user's
master device must be available on the system, unless all access is to be to an
auxiliary device. The user index and family name uniquely describe a user's master
device.
Each master device is organized into five logical sections.
1. Allocation information.
A master device, like all mass storage devices, maintains device labels and track ^^^
reservation
tables
( T R Ts ) .
1
The device label contains information describing the device, such as family name
and user mask, as well as locations of permit and catalog information and indirect
access files. Refer to the INITIALIZE - Initialization Entry later in this section.
The TRT is the key to allocating information on the master device and to
describing the physical layout of data on the device. Refer to APRDECK later in
this section.
2. Catalog information.
Catalog entries are used to determine the locations and attributes of permanent
files. The catalogs for a master device are allocated to contain catalog entries for
a specific group of user indexes. A particular catalog track may contain entries
for many users, the number depending upon the number of catalog tracks defined
for the device. The user index provides the mechanism for differentiating between
user's files on a particular catalog track.

3-46

NOS

Version

Analysis

Handbook

Revision

NOS Mass Storage Concepts

3. Permit information.
Users can explicitly or implicitly allow other users to access their permanent files.
Refer to the PERMIT command in the NOS Version 2 Reference Set, Volume 3.
Information describing the permission for all permanent files is in the permit file.
Catalog entries contain a relative sector address within this permit file for
permissions that have been granted for the file.
4. Indirect access files.
The master device contains all of the user's indirect access files. These files can
be accessed by commands that generate working copies for manipulation by the
user.
5. Direct access files.
Direct access files can reside either on the master device or on another device in
the family, depending on the device masks specified on the PF entries. Direct
access files are files that can be accessed at their location on mass storage. A
working copy is not generated, so any updates or alterations made to the files are
permanent.

Revision

Deadstart

Decks

3-47

NOS Mass Storage Concepts

Multispindle Device
To accommodate files that are larger than one device, you can specify multispindle
device assignments. Up to eight spindles of 844 disk drives or up to three spindles of
885 disk drives can be included in the equipment definition of one logical device, when
the device is first defined. All spindles must be available for access whenever the
device is accessed.
Multispindle devices are treated as one logical device, having a track size equal to n
times the single-spindle track size (n is the number of spindles in the device). The
tracks of an n-spindle device are broken down into n equally-sized segments, each
having a length equal to the single-spindle track size. Each segment is contained on
a different physical unit.
844 Expander
A nonexpanded controller can have up to eight disk drives connected to it. Each of the
connection paths is called a port and is identified by a port number ranging from 0 to ^^
7. An expander (10304 extender) is a hardware device that can be connected between j
controllers and 844 disk drives to increase the number of disk drives that each
controller can access.
The expander can be used only with 844-21 drives, although all equipment definitions
and equipment driving software support the 64-drive addressing scheme for both
844-21 (DI/DK) and 844-41 (DJ/DL) type equipment.
Each expander consists of either two or four expansion elements. An expansion
element connects to a single controller port and forms a connection path from that
port to from one through eight disk drives. The connection paths between an
expansion element and the eight possible disk drives are called ranks and are
identified by a rank number ranging from 0 to 7. Two expanders with four expansion
elements each can be connected to a single controller to allow that controller to
access a maximum of 64 disk drives. Each expansion element, however, is logically
independent and, as such, could be connected to any port of any controller.

3-48

NOS

Version

Analysis

Handbook

Revision

NOS Mass Storage Concepts

A single controller maximum configuration can be visualized as an 8- by 8-square
checkerboard with each square representing one of 64 disk drives (figure 3-1).
C o n t r o l l e r Port

Expander Rank

67,,
_^ Unit
Numbers
(octal)
77-* ""^

0ms,

Port Digit
Rank Digit

Figure 3-1. Expander Addressing Map
A column of squares in figure 3-1 represents all the drives that are accessed through a
single controller port. A row of squares represents all the drives that have the same
expander rank. Each disk drive that can be accessed by the controller is addressed by
a 6-bit unit number. The rightmost 3 bits of this unit number select to which of the
eight controller ports the drive is connected. The leftmost 3 bits of the unit number
select to which of the eight ranks on an expansion element the drive is connected. This
unit number is specified as a 2-digit octal number in the mass storage equipment EST
entry (refer to EQ - Disk Equipment EST Entry later in this section). The right digit
(port digit) of the unit number is the port number and the left digit (rank digit) is the
rank of the unit in the particular expansion element.

0H$mS

If two disk drives are vertically adjacent on the expander addressing map (figure 3-1),
their unit numbers are considered to be vertically ordered; that is, both drives are
connected to the same expansion element, both have the same port number, and their
rank numbers differ by one (refer to example 1).
If two disk drives are horizontally adjacent on the expander addressing map
(figure 3-1), their unit numbers are considered to be horizontally ordered; that is,
both drives have the same rank number, and their port numbers differ by one (refer
to example 2). The special case of rank numbers of 0 for two horizontally adjacent
drives is equivalent to the definition of consecutive unit numbers for other equipment.
All drives connected to a controller, either directly or through an expansion element,
are supported as single-unit or multiunit logical devices. Unit numbers can range
from 0 to 778, rather than from 0 to 7, as for other equipment. Thus, a maximum of
sixty-four 844 disk drives connected to a single controller can be addressed. However,
a maximum of eight units can be specified per multiunit device. In addition, all units
of a multiunit device must be connected to the same channel and, therefore, to the
same controller.

Revision M

Deadstart Decks 3-49

NOS Mass Storage Concepts

Figure 3-2 illustrates a configuration in which two expansion elements and 20 disk
drives are connected through one controller. An expansion element with eight drives is
connected to port 0, an expansion element with six drives is connected to port 1, and
six drives are connected to six ports (ports 2 through 7). Each disk drive is shown as a
square with its appropriate unit number inside. This configuration is used in the
following three examples to illustrate multiunit device assignments. The controller is
assumed to be connected to channel 1. Refer to EQ - Disk Equipment EST Entry later
in this section for specific information on assigning these devices.
Controller Port

Expander Rank

60
70

Figure 3-2. 844 Expander Configuration With 20 Drives
NOTE
The following examples illustrate multiunit device assignment of devices. For a
description of the mass storage EST entry in the EQPDECK, refer to EQ - Disk
Equipment EST Entry later in this section.

3-50 NOS Version 2 Analysis Handbook

Revision M

NOS Mass Storage Concepts

Example 1:
Figure 3-3 illustrates a possible configuration for a three-unit vertically adjacent
multiunit device. This device could be assigned in the EQPDECK, specifying EST
ordinal 6, as:
EQ6=DI,ST=ON,UN=50/60/70,CH=1.

Controller Port

Expander Rank

60
70

vertically Auiaceni xnree-unu uevice

Figure 3-3. Vertically Adjacent Three-Unit Device

Revision M

Deadstart Decks 3-51

NOS Mass Storage Concepts

Example 2:
Figure 3-4 illustrates a possible configuration for a two-unit horizontally adjacent
multiunit device. This device could be assigned in the EQPDECK, specifying EST
ordinal 7, as:
EQ7=DI,ST=0N,CH=1,UN=40-41

Controller Port

Expander Rank

60
70

Figure 3-4. Horizontally Adjacent Two-Unit Device

3-52 NOS Version 2 Analysis Handbook

Revision M

NOS Mass Storage Concepts

Example 3:
Figure 3-5 illustrates a possible configuration of 20 disk drives into seven devices.
These devices could be assigned in the EQPDECK as follows:
EQ6=DI,ST=ON,UN=60,CH=1.
EQ7=DI,ST=0N,UN=70,CH=1.
EQ10=DI,ST=ON,UN=50-51,CH=1.

EQ11=DI,ST=0N,UN=10/20/30/40,CH=1.
EQ12=DI,ST=ON,UN,11/21/31/41,CH=1.
EQ13=DI,ST=0N,UN=0-3,CH=1.
EQ14=DI,ST=0N,UN=4-7,CH=1.

Devices on ordinals 6 and 7 are defined as single units. These units may be
initialized online into a two-unit device if they are also defined as removable.
Controller Port
0

EQ13

Expander Rank

EQ10

EQ6

EQ7

EQll

6
EQ14

EQ12

Figure 3-5. Hardware Configured into Seven Devices

j/ms

Revision M

Deadstart Decks 3-53

NOS Mass Storage Concepts

Nonremovable Device
S*^S

A nonremovable device cannot be physically removed during system operation. It can 1
contain a copy of the system library, which means it is a system device; it can also be
available for temporary files. It may or may not contain permanent files.
Removable Device
A removable device can be logically or physically added or removed during system
operation without causing system malfunction.
A device is specified as removable with the REMOVE entry in the EQPDECK.
During deadstart, a removable device is recovered just as is any other mass storage
device, if the status is on. If the device is not available, then the status is displayed
for the operator (E,M display).
Removable devices can contain permanent files but cannot contain the system library
or temporary files, because a device containing active files (such as temporary or ^^
library files) cannot be removed from the system. A removable device can be either /^\
an auxiliary device or an alternate permanent file family device.
Shared Device
A shared device contains permanent files that can be accessed by more than one
mainframe. To have these permanent files accessible to the mainframe, the device must
be defined as shared in the mainframe. Refer to SHARE - Shared Device Entry and
ISHARE - Independent Shared Device Entry later in this section.
A shared device can be removable. However, when unloading a shared device, it must }
be in global unload status before you remove it. Refer to the DSD commands
UNLOAD and MOUNT in section 5 for more information concerning removable
shared devices.
System Device
The system device is a nonremovable device on which the system library resides. It can
also contain permanent and temporary files.
Temporary File Device
The temporary file device is a nonremovable device on which the following temporary
system files reside:
• Library files
• Local files
© Queued files
• Rollout files
• System files
• Timed/event rollout files

3-54

NOS

Version

^^s.

Analysis

Handbook

Revision

NOS Mass Storage Concepts

Buffered Disks
Buffered disks are those disks for which the system provides an extended memory data
buffer. The following buffered disks are supported on the mainframes indicated:
• The 819 Disk Storage Subsystem is available only on model 176. The buffer is
kept in LCME.
• The 885-42 Disk Storage Subsystem is available on all models except CYBER
180-class machines and model 176. The buffer is kept in ESM.
• The 895 Disk Storage Subsystem is available on all CYBER 180-class machines
except models 810, 815, 825, and 830. The buffer is kept in UEM.
• The 887 and 9853 Disk Storage Subsystems are available only on models 860,
960, 990, and 995. The buffer is kept in UEM.
• Buffered disks are not available on models 810, 815, 825, and 830.
Using extended memory as a data buffer provides the following capabilities.
• The system treats the buffer as a disk cache so that multiple requests for a
particular disk data block can potentially be satisfied by doing only one disk read.
• The system buffers data to maintain maximum transfer rates regardless of the
user's buffer size.
To maintain maximum transfer rates, a CPU program that resides in CPUMTR
controls the buffered disk I/O request processing. The system maintains the standard
disk I/O interface to the user's programs.
The buffered disk error reporting process logs read/write errors in the binary
maintenance log. An unrecovered read/write error is also logged in the system error
log and an error message appears at the system control point. The binary
maintenance log must be processed by the Hardware Performance Analyzer (HPA) to
get detailed information concerning buffered device errors.
The amount of I/O buffer space in extended memory is important to system
performance. Refer to XM - Declare Extended Memory Space for Buffers or User
Access later in this section.
There may be situations when a particular user job runs slower with buffered disks.
This happens if the job issues CIO reads when a buffer is full or issues CIO writes
when a buffer is empty. (Both cases indicate inefficient programming techniques.) You
can speed up the job by entering the DSD command ENABLE,LOGGING. The system
will perform faster I/O and issue warning messages to the job dayfile.

Ji^V

Revision

Deadstart

Decks

3-55

NOS Mass Storage Concepts

Extended Memory Overview
Extended memory (EM) refers to the five types of additional memory used by NOS to
supplement central memory space and connect mainframes. This extended memory can
be used to store programs and data, but not to execute programs. Shown below are the
five types of extended memory and the mainframes that support each type. Also shown
are the maximum EM size supported by each mainframe, how each mainframe connects
to the extended memory, and what buffered devices are supported for each EM type.
Extended
Memory

Mainframe

Maximum
Size

Mainframe
Connection

Buffered
Device 5

ECS

All

2MW

CPU port,6 DDP

ESM

All

16MW

CPU port,6 LSP

885-42

LCME

176

2MW

CPU port

819

STORNET

All "

4MW

LSP

UEM

815,825,835,865,875
810,830
840,845,850,855,860,
870, 910
990,995

2MW
8MW
16MW

No connection,
part of mainframe's
main memory

895, 887,
9853

8MW

Physical Configuration
Extended core storage (ECS) is an external memory available for all mainframes. ECS
connects to the mainframe using either a CPU port6 or a distributive data path (DDP)
through a peripheral processor.
Extended semiconductor memory (ESM) is an external memory available for all
mainframes. ESM connects to the mainframe using either a CPU port or a low-speed
port (LSP) through a peripheral processor.
Large central memory extended (LCME) is an external memory available only for
model 176 mainframes. LCME connects to the model 176 using a central processor
unit (CPU) port.
STORNET is an external memory available for all CYBER 170 and CYBER 180
mainframes. STORNET connects to the mainframe using a low-speed port (LSP)
through a peripheral processor.

5. The buffered devices shown are not necessarily supported on all of the mainframe types indicated.
6. A CPU port connection is not available on CYBER 180-class machines. CPU port on model 176 machines
can only connect to LCME.

3-56 NOS Version 2 Analysis Handbook

Revision M

<^^5S

NOS Mass Storage Concepts

Unified extended memory (UEM) is a part of the mainframe's main memory and is
separated from central memory by a partition defined at deadstart time by the site.
All extended memory except STORNET is accessed by special instructions
Instructions exist for multiple word transfers (FORTRAN: Level 1 variables;
COMPASS: RE/WE instructions) and single word transfers (FORTRAN- Level 2
variables; COMPASS: RX/WX instructions). The multiple word transfers are available
on all mainframe types; the single word transfers are available only with LCME and
UEM on models 176, 865, 875, and CYBER 180-class machines.
Logical Configuration
Extended memory can be used for several purposes. The physical characteristics of the
various extended memory types differ, which affects the ways in which extended
memory can best be used. The possibilities are:
• To connect mainframes in a multimainframe environment (ESM, ECS and
STORNET).
• To store system routines and data files (all EM types).
• To supplement user central memory space (all EM types except STORNET).
• To provide a cache buffer for buffered I/O devices (LCME, ESM, and UEM).
ESM, ECS, or STORNET can be used as a link device to interconnect mainframes in a
multimainframe environment. UEM cannot be used as the link device since it is part
of a mainframe's main memory. For additional information concerning multimainframe
operations, refer to section 13, Multimainframe Operations.
Extended memory can be used as a mass storage device. The following system files
can be made extended memory resident as opposed to using central memory or disk
space.
System Files

Description

Operating system

The alternate system residency EQPDECK entry ASR defines a
device to be an alternate system device. LIBDECK directives
specify which system library routines are to be placed on the
alternate system device.

Temporary and
rollout

The EQPDECK entry MSAL,T=est. or MSAL,R=est., where est
is the EST ordinal of the EM device, causes the system to use
extended memory as a mass storage device for temporary files or
rollout files.

Secondary rollout

The EQPDECK entry MSAL,S=est., where est is the EST ordinal
of the EM device, causes jobs that are less than a specified size
to be rolled out to extended memory. The IPRDECK entry SRST
defines the size of the rollout files allowed in extended memory.

Revision M

Deadstart Decks 3-57

NOS Mass Storage Concepts

System files should be placed in extended memory only if a performance improvement
can be gained. Whether performance improves or not depends on your production
environment, including memory and input/output requirements, available central and
extended memory, and available disk units and channels.
The amount of memory available to a user job can be increased by defining
user-accessible extended memory. NOS allows user data structures to reside in
memory external to the job's field length. (Refer to COMPASS and FORTRAN
reference manuals.)
A portion of extended memory is reserved for users by the XM EQPDECK entry. The
user's memory is reserved in allocation units dependent on the amount of
user-accessible extended memory defined at deadstart. The minimum allocation unit
(user EM block size [M = million] UEBS) varies as follows. Service limits are defined
for the user in the IPRDECK in UEBS units.
At least

But less than Allocation unit (UEBS)

1000 words

IM words

10008

IM words

2M words

2000s

2M words

4M words

40008

4M words

8M words

100008

8M words

16M words

20000s

This means that if you define 3 million words of user-accessible extended memory and
a user executes RFL(EC=1), that user will be assigned 40008 words of extended
memory.
Extended memory provides a cache buffer for buffered I/O devices. Space is allocated
by the system for buffered I/O with the XM EQPDECK entry. In most cases, system
performance improves as the amount of extended memory defined for buffered I/O
increases. However, ample space must be available for other uses.

3-58 NOS Version 2 Analysis Handbook

Revision M

NOS Mass Storage Concepts

CM and UEM Size Specification and Determination
When UEM is defined, its size is specified on the EQ EQPDECK entry for UEM. For
models 865 and 875, the remaining memory is used for central memory. On CYBER
180-class machines, the remaining memory is divided between native mode (NOS/VE or
EI) and central memory. If running in dual-state mode, the VE CMRDECK entry
specifies the memory for NOS/VE. If running NOS only, central memory size equals
the total memory size minus the EM size minus the EI size.
Simultaneous Use of Two Types of Extended Memory
NOS allows the simultaneous use of two types of extended memory in the following
cases
Models 865 and 875 can access both UEM and ESM/ECS simultaneously. The
recommended use of this combination of extended memory is to define ESM/ECS
for system file residence and/or as a link device in a multimainframe environment
and to define UEM for user-accessible extended memory. Since the main memory
size for models 865 and 875 is limited to two million words, central memory space
is given up for any UEM defined. Also, since ESM/ECS is an external device,
fewer memory conflicts result when it is accessed rather than UEM.
In this case, an EQ entry is required in the EQPDECK for ESM/ECS as well as
ASR and MSAL entries, as desired. User access is restricted to UEM via the XM
entry when the EM parameter is specified.

00&S

•

CYBER 180-class machines can also access both UEM and ESM/ECS/STORNET
simultaneously. The purpose of the ESM/ECS/STORNET access is to allow
connection of CYBER 180-class machines into a multimainframe environment. In
this case, ESM/ECS is defined in the EQPDECK as the link device and UEM is
defined for system files, I/O buffers, and user-accessible extended memory.
An EQ EQPDECK entry is required for both ESM/ECS/STORNET, but is not
required for UEM. The ESM/ECS/STORNET EQ entry defines the extended
memory as a link device via the LSP/DDP. The UEM EQ, if present, entry allows
the use of extended memory as a mass storage device. An XM entry allocates
extended memory for buffered I/O and user access.

Revision

Deadstart

Decks

3-59

Specifying Ranges of EST Ordinals

Specifying Ranges of EST Ordinals
Several EQPDECK entries allow you to specify multiple EST ordinals in the same
entry. For example, instead of entering
REMOVE=6,7,10,11,12.

you can enter:
REMOVE=6-12.

Ranges of ordinals can be mixed with individual ordinals, such as:
REMOVE=6,10-16.23.

Empty ordinals within a range are ignored. For example, specifying a range of 6
through 12 will ignore an unassigned ordinal 7. However, inappropriate devices
within a range or specified individually (such as specifying a printer as a removable
device) are diagnosed as errors.
EQ — Disk Equipment EST Entry
The purpose of the mass storage equipment (EQ) entries is to describe all mass storage
peripheral equipment. This includes disk equipment and extended memory equipment.
NOS requires that at least 6 million words of mass storage be available.
There can be up to 200 logical mass storage devices, and therefore, up to 200 mass
storage EST entries (this number does not include ordinals 0 through 4, which are
reserved for specific uses). An entry, however, can refer to more than one physical ^^\
unit. For example, two 885 spindles can be defined as either two logical devices with
two EQ entries or as one logical device with one EQ entry.
A unit is a dual-access unit if it is accessed by one mainframe through two different
controller-channel access routes. To define a unit as a dual-access unit with its EQ
entry, specify two channel parameters. The channels should be from two controllers.
Only one channel of a dual-channel access controller is recommended for use on a
single mainframe, since using both channels of the controller results in a performance
degradation rather than an improvement. Therefore, if both channel accesses of a
controller are physically connected to the same mainframe, you should define only
one of them on an EQ entry.
NOTE
A device's EQ entry must precede any of the following entries for that device: ASR,
MSAL, REMOVE, PF, SYSTEM, FAMILY, INITIALIZE, SHARE, ISHARE, ACCESS,
and THRESHOLD. If you redefine a device's EQ entry, then you must also redefine
those entries.

y * ^ % .

3-60

NOS

Version

Analysis

Handbook

Revision

EQ — Disk Equipment EST Entry

The format of the EQ entry for disk units is:
EQest =type,ST=status,UN=units,CH=ch,pt1/ch2pt2.AP=ap,IB=ib,EQ=eq.
Parameter Description
est EST ordinal of the disk units; from 5 to 777s.
type Equipment type. The following disk units are supported by NOS.
type

Equipment

Number

Units

DB7 885-42, 7155-401 (full track) 1 to 3
DC8 895, 7165 (full track) 1 to 2
DD9 834, 7255-1 (full track) 1 to 8
DF10 887 (4K sector; full track) 1 to 3
DG9 836, 7255-1 (full track) 1 to 3
DH10 887 (16K sector; full track) 1 to 2
DI 844-21, 7054/7154 (half track) 1 to 8
DJ 844-41/44, 7054/7154 (half 1 to 8
track), 7155-1

0ams

DK 844-21, 7154 (full track) 1 to 8
DL 844-41/44, 7154 (full track), 1 to 8
7155-1
DM 885-11/12, 7155-1 (half track) 1 to 3
D N 1 0 9 8 5 3 ( 2 K s e c t o r, f u l l t r a c k ) 1
f^

8 8 5 - 11 / 1 2 ,

7155-1
(full
track)
1
DVn
Single-density
819
D W 11

Double-density

819

to
1

When running NOS/VE in dual state with NOS, disks DC, DD, DF,
DG, or DH should not be defined in the NOS EQPDECK if NOS/VE is
to use them.

7. Not applicable for CYBER 180-class machines.
8. Applicable for CYBER 180-class machines except models 810, 815, 825, and 830. You must also specify
the UEM EQ entry and XM entry to define the I/O buffer area in UEM.
9. Applicable for models 810, 815, 825, and 830 only. You must also specify the control module EQ entry.
10. Applicable to models 860, 960, 990, and 995 only.
11. Applicable to model 176 only.

Revision

Deadstart

Decks

3-61

EQ — Disk Equipment EST Entry

Parameter Description
ST=status Specifies whether or not the equipment is available for access; enter one
of the following values:
status

Description

DOWN

All access to the equipment is inhibited for the operating
system and user jobs. Specify DOWN if the equipment is
malfunctioning and access is not desirable or the equipment is
to be used by NOS/VE in a dual-state environment (not
applicable for disks DC, DD, DF, DG, or DH).

IDLE

New files are not assigned to a device with IDLE status
unless no suitable alternative device exists, but you may
continue to access files already on the device as if the device
had a status of ON.

OFF

No user jobs can access the equipment; however, system
utilities are permitted to access the device, so it can be
dumped or loaded.

The specified equipment is generally available.

If the equipment is removable and is not available at deadstart, the
system determines it is unavailable, even if its EQ status entry specifies
ON. If INITIALIZE is entered, the equipment is not initialized until it is
set to ON status. During system operation, the operator can initiate
access to this device by entering the ON command.
If the equipment can be used with either one of two different systems
(removable devices, not dual access), define the status of the EQ entry
as ON in the system to which it is currently available for access; define
the status of the EQ entry as OFF in the system to which it is not
currently available for access.
Use the ST=DOWN parameter to prevent NOS from using disks that
are to be used by NOS/VE. This applies to all disks except DC, DD, DF,
DG, or DH (these disks should not be defined in the NOS EQPDECK if
NOS/VE is to use them).

3-62 NOS Version 2 Analysis Handbook

Revision M

EQ — Disk Equipment EST Entry

Parameter Description
UN=units Defines unit number(s). Unit numbers are configuration dependent.
For 834 or 836 units, unit numbers are generated as follows:
unit number = (control module physical equipment
number)*108 + (834 or 836 disk physical unit number)
For example, in UN = 10 the 1 is from the EQ = 1 parameter in the
control module entry and the 0 is the physical unit number of the
disk drive.
For 819 units, unit numbers are either from 0 to 3, if on FLPP channels
2 and 3, or from 4 to 7, if on FLPP channels 6 and 7.
For 844 units, unit numbers are from 0 to 77s.
For 885 units, unit numbers are from 40s to 77s.
For 887 units, unit numbers are from 0 to 7.
For 895 units, unit numbers have the following format:
unit number = shxxxx
where:
s = storage control address (0 or 1).
h = head of string controller address (0 or 1).
xxxx = spindle number (0 to 17s).

J^N

For 9853 units, unit numbers are from 0 to 7.
You can define the 834, 836, 844, 885, 887, 895, and 9853 physical units
with a separate EQ entry for each unit, or, if more continuous storage is
needed than is possible with one unit, you can define more than one
physical unit as one logical device with one EQ entry. If the EQ entry
is defining more than one unit of a multispindle device, unit numbers
can be specified as UN=um-unn, if units are contiguous, or as
UN=uni/un2/.../unn,if units are noncontiguous. For 834, 836, and 9853
units, contiguous means that the units are all on the same control
module.
For example, three 885 units (0, 1, and 2) to be accessed as three units
are defined as follows:
EQest=DM,ST=status,UN=0,CH=ch,AP=ap.
EQest=DM,ST=status,UN=l,CH=ch,AP=ap.
EQest =DM,CH=ch,UN=2,AP=ap,ST=stat us.

Revision M

Deadstart Decks 3-63

EQ — Disk Equipment EST Entry

Parameter Description
y-a^i\

UN=units (Continued)
Three 885 units (0, 1, and 2) to be accessed as one logical unit are
defined as follows:
EQest =DM,ST=status,UN=0-2,CH=ch,AP=ap.

or
EQest=DM,ST=status,UN=0/1/2,CH=ch,AP=ap.

An advantage to accessing the three units as one logical unit is that
less space is used in CMR. A disadvantage is that if any of the units
malfunctions or is destroyed, all units are affected.
| CH=chi

For all devices except 819s, 834s, 836s, 887s, and 9853s number of the
channel or channels to which the controller is connected; from 0 to 13s
and from 20s to 33s. For 819s, the channel pair for input/output(I/0)
multiplexer (primary access); enter one of these values:
chi Description
2 Channels 2 and 3.
4 Channels 4 and 5.
6 Channels 6 and 7.
For 834s and 836s, the channel number is specified on the control
module EQ entry.
For 887s and 9853s, the channel number for primary access; from 0 to
lis. The primary and secondary channel numbers must be different.
For 895s, a concurrent channel is specified by Cchi, or Cch2. For
example, CH = O2/C03 defines the channel pair as nonconcurrent channel
02 and concurrent channel 03. Use of a concurrent channel frees up two
nonconcurrent PPs for each channel that is moved to the concurrent I/O
subsystem (CIO). If an 895 is used to deadstart, one channel access to
the 895 must remain on a noncurrent channel.

I Pti

For 887s and 9853s only, the channel port (A or B) for the primary
access channel. Default is port A.

A^S\

3-64 NOS Version 2 Analysis Handbook

Revision M

EQ — Disk Equipment EST Entry

Parameter Description
/ch2 For all devices except 819s, 834s, 836s, 887s, and 9853s indicates
dual-access unit; cannot be 0; chi and ch2 should be connected to
different controllers. The system balances channel activity on dual-access
units. The balancing is done by alternately checking chi and ch2 for
availability. cti2 is assigned first if it is free. However,MTR logically
reverses chi and ch2 during system operation.
For 819s, the secondary access channel pair; one of the values described
for chi.
For 834s and 836s, dual access is indicated on the control module EQ
entry.
For 887s and 9853s, the channel number for secondary access; from 0 to
118. The primary and secondary channel numbers must be different.
pt2 For 887s and 9853s only, the channel port (A or B) for the secondary
access channel. Default is port A.
AP=ap The 1- or 2-digit octal number that indicates which APRDECK to use. If
AP=ap is omitted, the first APRDECK, APRD00, is assumed.
IB=ib The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.
j0^s EQ=eq Control module number for the 9853 disk. Control module numbers are
f
from
0
to
7.

JJ0^*

Revision

Deadstart

Decks

3-65

EQ — Control Module EST Entry

EQ —■ Control Module EST Entry
An 834 or 836 Disk Storage Subsystem consists of from one to eight 834 or from one
to three 836 disk units and the corresponding control modules. To be operational, both
the disk units and the control modules must be defined in the EQPDECK. The EQ
entry for the 834 or 836 disk units is described under EQ - Disk Equipment EST
Entry earlier in this section. The description of the EQ entry for a control module
follows.
A control module for the 834 or 836 Disk Storage Subsystem is a controller that
drives up to four 834 or three 836 disks and that interfaces with the operating
system using one or two 7255-1 adapters (one per channel). The control module EQ
entry is used to:
• Specify the channels to be used to access the 834 or 836 drives defined on the
control module. Channel entries are not allowed on the 834 or 836 disk unit EQ
entries.
• Specify what level of controlware is to be loaded into the control module during *aS*^
deadstart or when you use a LOADBC command.

• Allow maintenance access to a control module without affecting other control
modules on the same channel(s).
The format of the control module entry is:
EQest =CM, EQ=eq, CH=ch, /ch2, CW=cw, I B=1 b.

Parameter

Description

a^^\

est EST ordinal of the control module; from 5 to 7778EQ=eq Physical equipment number of the control module; from 0 to 7. Each
control module must be assigned a unique equipment number.
CH=chi Number of the channel to which the control module is connected; from
0 to 138 and from 20s to 338.
/ch2 Indicates a dual-access control module; from 1 to 138 and from 20s j^m.
to
33s.
"^

3-66

NOS

Version

Analysis

Handbook

Revision

EQ — Control Module EST Entry

Parameter Description
0^S

■

( CW=cw Indicates the control module type and whether controlware is to be
installed in the control module during deadstart. The control module
load sequence takes at least 15 seconds for each control module. It is
advised that you load controlware only when necessary, cw can be one of
these values:
cw

Description

CM Control module for 834 disk. Install controlware (default).
NCM Control module for 834 disk. Do not install controlware.
C2 Control module for 836 disk. Install controlware.
NC2 Control module for 836 disk. Do not install controlware.
IB=ib The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

0&&S

Revision

Deadstart

Decks

3-67

EQ — Extended Memory EST Entry

EQ — Extended Memory EST Entry
NOS supports the following types of extended memory.
• Large Central Memory Extended (LCME)
• Extended Core Storage (ECS)
• Extended Semiconductor Memory (ESM)
• Unified Extended Memory (UEM)
• STORNET
Refer to the Extended Memory Overview earlier in this section for an explanation of
the various physical and logical configurations using extended memory. Also refer to
the Examples of EQPDECK Entries for Extended Memory to see examples of how to
use EQPDECK entries to define extended memory for both single mainframe and
multimainframe configurations.
You can use extended memory as an alternate system residency for often accessed
system routines. The faster access may result in a performance improvement.
However, you should use caution when placing system routines in UEM to avoid
possible performance degradation instead of an improvement. This can happen because
a portion of central memory is reserved for UEM and therefore that portion is
unavailable to users. Also, accessing the system routines that reside in UEM may
require additional CPU overhead. Use the ACPD and PROBE utilities (refer to
TRACER/PROBE Utilities, section 21) to determine the impact on system resources
when using UEM.
NOTE
If extended memory is not included in the hardware configuration, do not make an
extended memory EST entry.
The format of the entry is:
EQest=typefST=status,MA=niorJe,ET=xmem/ddp/nc,SZ=size,CH=chi/ch2,AP=ap,MC=mc,IB=ib.
Parameter Description
est EST ordinal of the extended memory equipment; from 5 to 777s. If you
are using extended memory as a link device in a multimainframe
environment, est must be ordinal 5. Otherwise, extended memory can
be defined as any EST ordinal in the given range.
type Extended memory equipment type; enter one of these values:
type Description
DE DDP or LSP is not available.
DP DDP or LSP is available (not applicable for UEM).

/*w%\

3-68

NOS

Version

Analysis

Handbook

Revision

EQ — Extended Memory EST Entry

Parameter Description
ST=status

Specifies whether extended memory is available for access; enter one of
these values:
status Description
ON

Extended memory is available.

OFF Extended memory is ignored during system operation.
MA=mode

Maintenance mode (not applicable for UEM). If you specify MA=ON,
online extended memory diagnostics are allowed to reference the half of
extended memory that is placed in maintenance mode at the controller.
The other half of extended memory is available to the system. The size
of available physical extended memory is divided by 2 at deadstart.
When you initially place an extended memory device in maintenance
mode, all mainframes using the extended memory must initialize it.
When you place ECS in maintenance mode, you must also make the
PRESET entry for multimainframe operation. Refer to INITIALIZE and
PRESET later in this section. If you omit the MA = mode parameter, the
default is MA=OFF.
If you use part of extended memory in maintenance mode and you have
ESM, you must also use the MC=mc parameter to define which
maintenance port to use.

ET=xmem/ Type of large memory and ddp. If you specify ddp, you must also specify
ddp/nc xmem. If this parameter is not specified, El/Dl is assumed*
xmem Description
El

ECS I for all mainframes.

ECS II for all mainframes.

LCME only for model 176.

UEM for models 865 and 875 and CYBER 180-class machines.
Type must be DE. The system ensures that the sum of memory
words specified by the MINCM CMRDECK entry and specified
by this entry for UEM is present.

ESM for all mainframes.

STORNET for all CYBER 170 and CYBER 180 mainframes.

ddp

Description

DI DC135 DDP. Default for xmem of El or E2.
D2 DC145 (parity enhanced) DDP, or ESM low-speed port (LSP).
Default for xmem of ES and SN.
nc
NC

Revision M

Description
Indicates type DP does not have a CPU coupler. NC is not
valid for xmem of DE. Default for xmem of SN.

Deadstart Decks 3-69

EQ — Extended Memory EST Entry

Parameter Description

I SZ=size

Size of extended memory in words/10008. This value must not be larger
than the size of the physical memory that is present.
• For ECS II and LCME, size can range from a minimum of 108 to a
maximum of 100008.
• For STORNET, size can range from a minimum of 10s to a
maximum of 20000s.
• For ESM, size can range from a minimum of 108 to a maximum of
1000008.
• For UEM, size can range from a minimum of 108 to a maximum of
(1000008-CM size).
NOTE
Since CIP uses a small amount of CM, you may need to make
allowances for CIP when you enter a value for size.
• For ECS I, size is one of the values in the following table.
ECS I
Size (Octal) Available Number of Banks
400

125K12

1000

250K

2000

500K

4000

1000K

10000

2000K

The following table shows the value in EM words (both octal and
decimal) for a given value of size.

EM Words
Size (Octal)

(Octal)

(Decimal)

10
400

10000
400000
1000000
2000000
4000000
10000000
20000000
40000000
100000000

4096
131072
262144
524288
1048576
2097152
4194304
8388608
16777216

1000
2000
4000
10000
20000
40000
100000

12. K is 1000 60-bit words.

3-70 NOS Version 2 Analysis Handbook

Revision M

EQ — Extended Memory EST Entry

Parameter Description
CH=chi,/ch2

Numbers of the channels to which the DDP is connected; from 0 to 13s
and from 20s to 33s.
If the equipment type is DE, do not specify a channel parameter. If a
channel parameter is specified, the system recognizes the DE entry as a
DP entry.
If the equipment type is DP, specify either one or two channels. The
second channel cannot be 0 (zero). If a DDP is present, the loading of
CPU programs residing in ECS or ESM still occurs via the CPU. A
DDP must be connected to a channel by itself.

AP=ap

The 1- or 2-digit octal number that indicates which APRDECK to use. If
you omit AP=ap, the first APRDECK, APRD00, is assumed.

MC=mc

Number of the channel to which the maintenance port is connected; from
1 to 138 and from 20s to 33s. Channel 0 cannot be used for the
maintenance port. This channel is for ESM only and must be specified
for proper reporting of ESM errors.

IB=ib

The 1- to 4-digit octal value; this value is entered in the installation
byte for the specified EST ordinal. Refer to EST Formats in the NOS
Version 2 Systems Programmer's Instant.

Revision M

Deadstart Decks 3-71

Examples of EQPDECK Entries for Extended Memory

Examples of EQPDECK Entries for Extended Memory
The following examples show the EQPDECK entries that are necessary to define
extended memory in various configurations.
Single Mainframe Examples
The EST ordinal of extended memory equipment ranges from 5 to 7778. For single
mainframe configurations, extended memory can be defined as any EST ordinal in the
given range. For these examples, the machine identifier of the mainframe is assumed
to be .AA.
Example 1:
This example shows a CYBER 170 mainframe with ESM connected via the high-speed
port. ESM can be used as a mass storage device, user-accessible extended memory,
and for 885-42 disk I/O buffers.
EQ6=DP,ET=ES,ST=ON,S2=10000,CH=32,
MSAL,S=6.
ASR=6.
XM=AA,3000,1000.

(Define 2 million words of ESM.)
(Define ESM as secondary rollout device.)
(Define ESM as alternate system residency
device.)
(Allocate 3000000 octal words for 885-42
I/O buffers and 1000000 octal words for
user-accessible extended memory.)

Example 2:
This example shows a CYBER 180-class machine with part of its mainframe memory
defined as UEM, which can be used as a mass storage device, for user-accessible
extended memory, and for 887, 895, or 9853 disk I/O buffers.
EQ7=DE,ST=ONfET=EM,SZ=2000
XM-AA,1000,200.

(Define 1/2 million words of memory as
UEM.)
(Allocate 1000000 octal words for 895,
887, or 9853 I/O buffers and 200000 octal
words for user-accessible extended
memory.)

NOTE
If you are running a dual-state system, the VE CMRDECK entry will affect the
amount of memory available for NOS and thus for UEM.
Example 3:
This example shows a CYBER 180-class machine where UEM is used only for
user-accessible extended memory, not as a mass storage device or for I/O buffers. No
EQ entry for UEM is necessary in this case.
XM=AA,,200,

3-72 NOS Version 2 Analysis Handbook

(Allocate 200000 octal words for
user-accessible extended memory.)

Revision M

Examples of EQPDECK Entries for Extended Memory

08&*\

Example 4:
This example shows a CYBER 170 model 865 or 875 mainframe with no ESM. Part
of the mainframe memory is defined as UEM and is used as a mass storage device
and for user-accessible extended memory. UEM cannot be used for 885-42 disk I/O
buffers.
EQ11=DE,ST>ON,ET=EM,SZ=2000
MSAL,S=11.
ASR=11.
XM=AA.,200.

(Define 1/2 million words of UEM.)
(Define UEM as secondary rollout device.)
(Define UEM as alternate system
residency device.)
(Allocate 200000 octal words for
user-accessible extended memory.)

Example 5:
This example shows a CYBER 170 model 865 or 875 mainframe with no ESM (as in
example 4) except that UEM is used only for user-accessible extended memory and
not as a mass storage device. No EQ entry for UEM is necessary in this case.
XM=AA,,200.

(Allocate 200000 octal words for
user-accessible extended memory.)

Example 6:
This example shows a CYBER 170 model 865 or 875 mainframe with ESM connected
via the high-speed port. ESM is used as a mass storage device, for 885-42 I/O buffers,
and for user-accessible extended memory. No UEM is defined.
EQ10=DP,ST=ON,ET=ES,SZ=10000,CH=7
MSAL,S=10.
ASR=10.
XM=AA,3000,1000.

Revision M

Deadstart Decks 3-73

Examples of EQPDECK Entries for Extended Memory

H^ifSgs

Example 7:
This example shows a CYBER 170 model 865 or 875 mainframe with ESM connected
via the high-speed port. ESM is used as a mass storage device and for 885-42 disk
I/O buffers. Part of the mainframe's memory is defined as UEM and used for
user-accessible extended memory.
You have the option on CYBER 170 model 865 and 875 mainframes to define
user-extended memory either in ESM or UEM. If ESM is present, as indicated by an
EQ entry for it, then user-accessible extended memory resides in ESM by default.
However, you can force user-accessible extended memory to reside in UEM with the
EM parameter on the XM entry. 885-42 disk I/O buffers must reside in ESM.
EQ10=DP,ST=ON,ET=ES,SZ=10000,CH=7
MSAL,S=10.
ASR=10.
XM=AA,3000,1000,EM.

(Define 2 million words of ESM.)
(Define ESM as secondary rollout device.)
(Define ESM as alternate system residency
device.)
(Allocate 3000000 octal words for 885-42
I/O buffers in ESM and 1000000 octal
words for user-accessible extended memory
in UEM.)

A**3S

3-74 NOS Version 2 Analysis Handbook

Revision M

Examples of EQPDECK Entries for Extended Memory

Multimainframe Examples
For all multimainframe configurations, the extended memory link device must be
defined as the equipment with EST ordinal 5. The machine identifiers of the connected
mainframes are assumed to be AA and AB. The following examples do not show the
SHARE EQPDECK entries that are required to indicate multimainframe operation.
Example 1:
This example shows two CYBER 170 mainframes linked to ESM via high speed ports.
In addition to being the link device, ESM can also be used as a mass storage device,
for 885-42 disk I/O buffers, and for user-accessible extended memory.
EQ5=DP,ST=0N,ET=ES,SZ=10000,CH=5.
XM=AA,1000,200.

JPV.

(Define 2 million words of ESM.)
(Allocate 1000000 octal words for 885-42
I/O buffers and 200000 octal words for
user-accessible extended memory in ESM
for machine AA.)
XM=AB,,400. (Allocate 400000 octal words for useraccessible extended memory in ESM for
machine AB.)
The EQPDECK entries for the linked mainframe would be the same as shown above;
the link device (ESM) is defined as equipment 5 and both XM entries must be
present.
Example 2:
This example shows two linked CYBER 180-class machines connected to ESM via
low-speed ports. Part of the mainframe memory for machine AA is defined as UEM,
which is used as a mass storage device, for 895, 887, or 9853 disk I/O buffers, and
for user-accessible extended memory. On CYBER 180-class machines, user-accessible
extended memory and 887 or 895 disk I/O buffers must reside in UEM; they cannot
reside in ESM.
EQ5=DP,ST=0N,ET=ES/D2/NC,SZ=10000,CH=4

EQ6=DE,ST=0N,ET=EM,SZ=2000

MSAL,S=6.
ASR=6.
XM=AA,1000,200

Revision M

(Define ESM as the link device. NC
indicates that there is no CPU access to
ESM.)
(Define 1/2 million words of UEM; without
this EQ entry, UEM can be used only for
user-accessible extended memory.)
(Define UEM as secondary rollout device.)
(Define UEM as alternate system
residency device.)
(Allocate 1000000 octal words for 895,
887, or 9853 I/O buffers and 200000 octal
words for user-accessible extended memory
in UEM.)

Deadstart Decks 3-75

Examples of EQPDECK Entries for Extended Memory

The EQPDECK for the linked CYBER 180-class machine AB might look like the
following. This mainframe has part of its memory defined as UEM used only for
user-accessible extended memory.
EQ5«DP,ST=ON,ET=ES/D2/NC,SZ=10000,CH=4.
XM=AB,,200.

(Define ESM as the link device.)
(Allocate 200000 octal words for
user-accessible extended memory in UEM.
Since no EQ entry is present for UEM, it
cannot be used as a mass storage device
or for I/O buffers.)

The XM entries appear only in the EQPDECK for the machine where the memory is
being allocated. Do not place them in the EQPDECKs of any linked mainframes.
Example 3:
This example shows a CYBER 170 mainframe connected to ESM via a high-speed
port linked to a CYBER 180-class machine connected to ESM via a low-speed port.
EQPDECK for CYBER 170
EQ5=DP,ST=ON,ET=ES,SZ=10000,CH=5.
MSAL,S=5.
ASR=5.
XM=AA,1000,400.

(Define ESM as the link device.)
(Define ESM as secondary rollout device.)
(Define ESM as alternate system residency
device.)
(Allocate 1000000 octal words for 885-42 I/O
buffers and 400000 octal words for
user-accessible extended memory in ESM.)

EQPDECK for CYBER 180

| EQ5=DP,ST=ON,ET=ES/D2/NC,SZ=10000,CH=4.
| EQ6=DE,ST=ON,ET=EM,SZ=2000.

| MSAL,S=6.
I ASR=6.
XM^AA,1000,400

| XM=AB,1000,200

(Define ESM as the link device.)
(Define 1/2 million words of UEM; without
this EQ entry, UEM can be used only for
user-accessible extended memory.)
(Define UEM as secondary rollout device.)
(Define UEM as alternate system
residency device.)
(Linked 170 XM entry must be present to
define user-accessible extended memory
and 885-42 I/O buffers in ESM.)
(Allocate 1000000 octal words for 895,
887, or 9853 I/O buffers and 200000 octal
words for user-accessible extended memory
in UEM. This entry can not be in the 170
EQPDECK.)

>tf^v

3-76 NOS Version 2 Analysis Handbook

Revision M

Examples of EQPDECK Entries for Extended Memory
y$$S

Example 4:
This example shows a CYBER 170 model 865 or 875 connected to ESM via a
low-speed port linked to a CYBER 180-class machine also connected to ESM via a
low-speed port. This configuration allows continued system operation if the high-speed
port to ESM from the CYBER 170 model 865 or 875 was down.
EQPDECK for CYBER 170 model 865 or 875
Note that ESM cannot be used for user-accessible extended memory or for 885-42 I/O
buffers if a high-speed port is not present.
EQ5=DP,ST=ONFET=ES/D2/NC.SZ=10000,CH=4. (Define ESM as the link device; NC
indicates that there is no CPU access.)
EQ11=DE,ST=ON,ET=EM,SZ=2000. (Define 1/2 million words of UEM. This is
allowed; in contrast to example 8 earlier,
because ESM has no CPU access.)
M S A L , S = 1 1 ( D e fi n e U E M a s s e c o n d a r y r o l l o u t d e v i c e . )
A S R = 1 1 . ( D e fi n e U E M a s a l t e r n a t e s y s t e m r e s i d e n c y
device.)
XM=AA,,200. (Allocate 200000 octal words for
user-accessible extended memory in UEM.
This entry cannot be in the 180
EQPDECK.)
EQPDECK for CYBER 180
EQ5=DP,ST=ON,ET=ES/D2/NC,SZ=10000,CH=4. (Define ESM as the link device.)
EQ6=DE,ST=ON,ET=EM,SZ=2000. (Define 1/2 million words of UEM; without
this EQ entry, UEM can be used only for
user-accessible extended memory.)
m s a l , S = 6 . ( D e fi n e U E M a s s e c o n d a r y r o l l o u t d e v i c e . )
A S R = 6 . ( D e fi n e U E M a s a l t e r n a t e s y s t e m r e s i d e n c y
device.)
XM=AB, 1000,200. (Allocate 1000000 octal words for 895, 887,
or 9853 I/O buffers and 200000 octal words
for user-accessible extended memory in
UEM. This entry cannot be in the 170
EQPDECK.)

Revision

Deadstart

Decks

3-77

MSAL — Mass Storage Allocation Control Entry

MSAL — Mass Storage Allocation Control Entry
The MSAL entry assigns job files of the specified type to the mass storage devices
defined by the specified EST ordinal.
The format of the MSAL entry is:
:
I MSAL,t=esti,est2,. ..,estn.

I Parameter Description
I t File type; one of these values:
I

Description

LGO

Job

Input

fi l e s .
d a y fi l e s .
fi l e s . 1 3

Local

fi l e s .

O O u t p u t fi l e s . 1 3
f'.

Primary

Rollout

fi l e s .
fi l e s .

S Secondary rollout files.
I

Te m p o r a r y

fi l e s .

I esti EST ordinal of a nonremovable mass storage device, from 5 to 57a
f R a n g e s o f o r d i n a l s c a n b e s p e c i fi e d .
I

NOTE

In most cases, using ESM or UEM as a secondary rollout device
improves system performance. On the other hand, depending on the '^]
I mainframe type, the size of the jobs being rolled out, and the
secondary rollout sector threshold (IPRDECK and DSD SRST
command), CPU overhead may increase significantly. Using central
memory for pseudo-control points instead of using the same memory as
UEM for secondary rollout is normally preferable because of reduced
CPU overhead. Use the ACPD and PROBE utilities (refer to
TRACER/PROBE Utilities, section 21) to determine the best use of
system resources.

13. Routing a file to queues changes a file's type, not its residency. Thus specifying an MSAL,I=est or
MSAL,0=est entry does not necessarily force all input or output queued files to the specified devices.

3-78

NOS

Version

Analysis

Handbook

Revision

MSAL — Mass Storage Allocation Control Entry

0ms.

Secondary rollout files are rollout files whose size in sectors is smaller than a
threshold specified by the IPRDECK or DSD entry SRST. These files are rolled out to
devices specified by the MSAL,S= entry. All files selected for rollout that are equal to
or greater in size than the threshold are rolled out to devices specified by the
MSAL,R= entry. The default value of SRST is 0 (zero); thus, no secondary rollout files
exist unless this value is changed. A possible use of this feature is:
Entries

Comments

EQPDECK

EQ5=DP,ST=ON,SZ=1000,CH=27. Specify equipment 5 as extended memory with a DDP.
M S A L , S = 5 . D i r e c t s e c o n d a r y r o l l o u t fi l e s t o e x t e n d e d m e m o r y.
IPRDECK
S R S T = 2 0 . S e t t h r e s h o l d c o u n t s o t h a t n o l a r g e r o l l o u t fi l e s a r e
rolled out to extended memory.

Revision

Deadstart

Decks

3-79

DOWN — Down Channel Entry

| DOWN — Down Channel Entry
I The DOWN entry disables the use of channels at deadstart before the system attempts /
I to use them to access devices connected to them. If a channel is the only remaining
| access to a device, .it may not be downed unless that device is defined as DOWN. The
I DOWN entry does not apply to either the deadstart channel or the CIP channel.
| The DOWN entry format is:
|

DOWN,CH=ch1fch2

chn.

| Parameter Description
| chi Number of the channel; from 0 to 13s and 208 to 338. A concurrent
channel is indicated by a C prefix (Cchi).
|

Example:

| The following entry sets DOWN status for both nonconcurrent channel yrt_
23
and
concurrent
channel
4.
^
|

D0WN,CH=23,C4.

| UP — Up Channel Entry
| The UP entry allows resumption of normal use of channels that have been disabled by
| a previous DOWN entry.
|

The

entry

format

is:

^=^

U P, C H = c h 1 t c h 2 , . . . , c h n .

| Parameter Description
I chi Number of the channel; from 0 to 13s and 20s to 33s. A concurrent
channel is indicated by a C prefix (Cchi).
I

Example:
The following entry clears DOWN status of both nonconcurrent channel ***\
23 and concurrent channel 4.

U P, C H = 2 3 , C 4 .

3-80

NOS

Version

Analysis

Handbook

Revision

PF — Permanent Files Device Assignment Entry
jgjffe\

PF — Permanent Files Device Assignment Entry
Before initializing a mass storage device (with the INITIALIZE entry in the
EQPDECK), add a PF entryu for that device to the EQPDECK anywhere after the
device's EQ entry. The PF entry information becomes part of the device's label when it
is initialized during deadstart; this label is recovered during subsequent deadstarts. For
subsequent deadstarts, it is not necessary that the PF entry be part of the EQPDECK
on the deadstart file; if it is, it is ignored. Refer to the INITIALIZE entry for the
default PF entries.
If the unit is a family device, the format is:
PF=est,type,dm.sm,name,device,nc.
If the unit is an auxiliary device, the format is:
PF=est,type,name,nc.
Parameter Description
est EST ordinal of the device; from 5 to 7778.
type Type of device; one of these values:
type Description
F Family device. It can contain indirect access files if the dm
parameter is from 1 to 377s. It can contain direct access files
if the sm parameter is from 1 to 377s. It is a master device
if the dm parameter is specified.
X Auxiliary device, which can contain both direct and indirect
access files. X must be specified on a unit's PF entry if any
of the auxiliary device commands are to be used for the
device.
dm Specifies the unit's device mask; from 0 to 3778. Set according to
information under Device Masks in section 17, PF Utilities. Omit this
parameter if the device is an auxiliary device.
The device mask for a permanent file device defines the groups of
users whose catalogs reside on the device for a particular family.
sm Specifies the unit's secondary mask; from 0 to 3778. Set according to
information under Device Masks in section 17, PF Utilities. Omit this
parameter if the device is an auxiliary device.
This parameter controls the residence of direct access files in the same
way that dm controls the residence of indirect access files.

0n^S
14. Refer to table 3-5 for dependencies.

Revision

Deadstart

Decks

3-81

PF — Permanent Files Device Assignment Entry

Table 3-5. PF Entry Parameter Settings (type, dm, name, device, and sm)
Type of PF Files Permitted on
Device
Device

type

name

device sm

pack

Omit

family

1-778

Omit

Auxiliary

Indirect and/or X
direct

Omit

Family

Direct

Indirect only
(master device)

1-3778 family 1-778

Indirect
and
direct (master device)

1-3778 family l-77s 1-3778

only

1-3778
0

1. If the device is to be a private auxiliary device, enter the INITIALIZE command
after deadstart and specify the user name. Refer to section 8, K-Display Utilities, for
the
procedure.
-

3-82 NOS Version 2 Analysis Handbook

Revision M

PF — Permanent Files Device Assignment Entry

Parameter Description
name

Designates either the name of the family to which the unit belongs or
its pack name if it is an auxiliary device; from 1 to 7 alphanumeric
characters. Do not use the family name 0: it is reserved.
The family name describes the permanent file devices available to a
user. A family may consist of from 1 to 63 logical devices; however,
the master devices within the family must have device masks totaling
3778 if all possible user indexes are to be accommodated.
Usually a system runs with one family of permanent file devices
available. But you can activate additional families on a system, in order
to allow the users of these families to access their permanent files
through an alternate system. This might be helpful if one system
supplies backup service to another system. When more than one family
is active on a system, users with matching user indexes access the same
permanent files on a public auxiliary device. You can avoid this
situation by predetermining a range of user indexes for each family
running on a system. When a new family is introduced into a system,
its user indexes should be checked against those of the family or
families currently running and any matching indexes should be changed.
Refer to the IPRDECK entry COMLIB later in this section.
The pack name is the unique 7-character name associated with an
auxiliary device. An auxiliary device is a self-contained permanent file
device: all permanent files (whether direct or indirect access) represented
by the catalogs on the device reside on that device. To access a file on
an auxiliary device, users must specify the pack name as part of the
permanent file request. The pack name is used instead of the usual
algorithm for determining catalog location (user masks and family
name). An auxiliary device can be private or public. Any user who
knows the pack name and has the appropriate permissions and
validations can access files on an auxiliary device. Only the owner user
name can create files on a private auxiliary device (perform DEFINE,
SAVE, or REPLACE requests).

device

Number of the device in the family; from 1 to 77s. Omit this parameter
if the device is an auxiliary device.
A permanent file that does not reside on the master device has a device
number in the catalog entry or on the master device. The device number
specifies on which alternate device within the family the file resides.

15. If not otherwise specified, the default family name becomes part of the tape label information. It is
checked and verified if the user specifies the FA=A parameter on a command. Refer to the NOS Version 2
Reference Set, Volume 3 for a discussion of FA=A.

Revision M

Deadstart Decks 3-83

PF — Permanent Files Device Assignment Entry

Parameter Description
Number of catalog tracks (optional) used only for master devices; from 1
to 2008. This value must be a power of 2. If you do not specify nc, one
of the following default values (based on the equipment type) is supplied.

Default nc

Equipment

Type

819

DV/DW

834

836

844-21

DI/DK

844-41/44

DJ/DL

885-11/12

DM/DQ

885-42

887(4K)

887U6K)

895

9853

Extended
memory

ECS or ESM
with DDP

Private device

Examples:
PF=6,F,125,125,SYSTEM,3,200
PF=17,X,PACK.

3-84 NOS Version 2 Analysis Handbook

Revision M

SYSTEM — System Library Device Assignment Entry

SYSTEM — System Library Device Assignment Entry
The SYSTEM entry specifies which mass storage devices are to contain copies of the
NOS system library from the deadstart file. A system device can be any disk storage
device as well as extended memory.
Throughput can be greatly improved by specifying more than one system device For
example, if two system devices are specified and they are on different channels, the
time required to access system programs can be reduced. When the channel for one
system device is busy, the other is accessed. Also, if hardware problems occur on one
system device, the other system device can still be accessed. A good general rule is
to have one copy of the NOS system library per pair of channels with a maximum of
three copies. This allows alternate access to the system library while saving mass
storage space.
The following restrictions apply.
• The EQ entry for a system device cannot have the status set to OFF.
• A REMOVE entry cannot exist in the EQPDECK for a device being specified as a
system device.
• If more than one device is specified as a system device, all devices specified must
be of the same type and have the same number of spindles. For example, if there
are two system devices and the equipment EST ordinal for one of them specifies
DI (single spindle), the equipment EST ordinal for the other one must also specify
DI (single spindle).
• If no devices are specified as system devices, the system library resides on the
first nonremovable mass storage device.
• An ASR entry cannot exist in the EQPDECK for a device being specified as a
system device.
The SYSTEM entry format is:
SYSTEM=est1fest2 estn.

Parameter Description
esti

EST ordinal of the device to contain a copy of the system library on
the deadstart file; from 5 to 37s . The EQ entry must be set to ON
status. One or more ordinals can be specified with one SYSTEM entry.
Ranges of ordinals can be specified. The maximum number of system
devices allowed depends upon the value of MXSY (refer to COMSMSC
Parameters in the NOS Version 2 Installation Handbook).

0m**.
Revision M

Deadstart Decks 3-85

ASR — Alternate System Library Device Assignment Entry.

ASR — Alternate System Library Device Assignment Entry
This entry specifies which mass storage devices are to be alternate system devices. An
alternate system device is a mass storage device on which duplicate copies of system
routines can be placed by the system, either for faster access than is possible from a
system device or because they are frequently used programs. The following restrictions
apply.
• The device must be a mass storage device, including extended memory.
• The device cannot be a removable device.
• The device cannot be a system device.
When loading a system routine, the system will access the routine from the alternate
system device if practical. However, if the alternate system device is down or its access
is more congested than the system device, the system will access the routine from the
system device.
The procedure for selecting the records to be placed on the alternate device is in
LIBDECK.
The ASR entry format is:
ASR=est1,est2,....estn.

Parameter Description
esti EST ordinal of mass storage device to be used as an alternative
system device; from 5 to 37s. Ranges of ordinals can be specified.
SCKP — System Checkpoint File Device Assignment Entry
The SCKP entry specifies on which mass storage devices the checkpoint file is to
reside. This entry is processed during a level 0, 1, or 2 deadstart. If no checkpoint
devices are defined, the checkpoint file will reside on the first default mass storage
device.
A level 0 deadstart clears the checkpoint status on all mass storage devices. To clear
the checkpoint status for a specific mass storage device, use the RESET entry.
The SCKP entry format is:
SCKP=esti,est2,...,estn.

Parameter Description
esti EST ordinal of the mass storage device to be defined as a system
checkpoint file device; from 5 to 7778. Ranges of ordinals can be
specified.

3-86

NOS

Version

Analysis

Handbook

Revision

FAMILY — Default Family Name Assignment Entry

0ms.
FAMILY — Default Family Name Assignment Entry
The FAMILY entry defines the default family. The family that is to be defined as the
default family may reside on more than one device. The EST ordinal of any device
within the family can be specified on the FAMILY entry, except in the following
situation. If the member of the family whose device mask will have bit 27 (200s in
mask) set is being initialized, the FAMILY entry must specify the ordinal of this
device. In all cases, the FAMILY entry must follow the EQ entry for the device
specified.
The following restrictions apply.
• The status parameter for a default family device's EQ entry cannot be set to OFF.
• A REMOVE entry cannot exist in the EQPDECK for a device being specified as a
default family device.
The FAMILY entry format is:
FAMlLY=est.

Parameter Description
est ' EST ordinal number of the mass storage device that the system
automatically uses to determine your family when you do not specify a
family name at login or job initiation; from 5 to 7778.
REMOVE — Removable Device Assignment Entry
If a mass storage device is to be considered removable, you must specify it as such at
deadstart with the REMOVE entry. This allows it to be introduced or removed during
system operation. A device specified as removable cannot also have associated with it
an ASR, SYSTEM, MSAL, FAMILY, DAYFILE, ACCOUNT, ERRLOG, or MAINLOG
entry (refer to Dayfile Descriptions earlier in this section for the last four entries).
The format is:
REMOVE=esti,est2....,estn.

Parameter Description
esti EST ordinal of mass storage device that is to be removable; from 5 to
7778. One or more ordinals may be specified with one REMOVE entry.
Ranges of ordinals can be specified.

0^s
Revision

Deadstart

Decks

3-87

SHARE — Shared Device Entry

SHARE — Shared Device Entry
This entry identifies the rotating mass storage devices to be shared through a link
device (ECS, ESM, or STORNET) by from two to eight mainframes in a
multimainframe complex. The tables necessary for the management of these devices
(MST, TRT, MRT, and DAT) are maintained on the link device. The presence of the
SHARE entry implies a multimainframe complex; shared status will be set for the link
device. If the link device is the only device to be shared, it must be specified in the
SHARE entry. If the SHARE entry is specified, the ISHARE entry must be omitted.
Refer to PRESET - Preset the Link Device Entry later in this section.
Following is a list of the equipment types that can be shared.
Equipment

Type

ECS
without
or
ESM without LSP

DDP

ECS
with
DDP
or ESM with low-speed port (LSP)
or STORNET
844-21

DI/DK

844-41/44

DJ/DL

8 8 5 - 11 / 1 2

DM/DQ

The

format

is:

SHARE=esti,est2,...,estn.

Parameter Description
esti EST ordinal of the mass storage device being shared; from 5 to 777s
(EST ordinal 5 is reserved for the link device). Ranges of ordinals can
be specified.
Refer to section 13, Multimainframe Operations, for suggestions on shared device /*^v
configurations.

3-88

NOS

Version

Analysis

Handbook

Revision

ISHARE — Independent Shared Device Entry

ISHARE — Independent Shared Device Entry
This entry identifies the rotating mass storage devices that are to be independently
shared by from 2 to 16 mainframes in a multimainframe complex. The tables necessary
for the management of these devices (MST, TRT, MRT, and DIT) are maintained on
the shared device. You cannot designate ECS or ESM in an ISHARE entry. When the
ISHARE entry is specified, the SHARE entry must be omitted. Refer to PRESET Preset the Independent Shared Device Entry later in this section.
Listed are the equipment types that can be independent shared devices.
Equipment Type
834

836

844-21 DI/DK
f^

844-41/44

DJ/DL

8 8 5 - 11 / 1 2 D M / D Q
The ISHARE entry format is:
ISHARE=esti .est 2 estn

Parameter Description
esti EST ordinal of the mass storage device being shared; from 5 to 7778.
Ranges* of ordinals can be specified, as described under Specifying
Ranges of EST Ordinals earlier in this section.
Refer to section 13, Multimainframe Operations, for suggestions on shared device
configurations.

Revision

Deadstart

Decks

3-89

LBC — Load Buffer Controllers Entry

LBC — Load Buffer Controllers Entry
This entry identifies the type of controlware to be installed on the specified disk
channels. Depending on the specified parameters, this entry can identify the channels
as having half-track or full-track controlware but not install the controlware.
Unless you specify'the LBC entry, the system examines the mnemonics of the device
in the EQPDECK entry and causes the default version of controlware to be installed
as follows:
Device Type Controlware Version Number
DB16

MA722

DC17

MA464

DD18

MA462

DG18

MA462

MA710

MA401

MA721

Use the LBC entry to override these defaults. The LBC entry format is:
LBC,type, ci,C2,....cn.

Parameter Description
type Controlware to be installed; one of these values.
type

Description

CC Install 7165 controller with full-track (MA464) controlware.
CN Identify channel(s) as having full-track 7165 controller, but do
not install the controlware.
FM Install controller with full-track (MA721) controlware.
FT Install controller with full-track (MA401) controlware.

16. Not applicable for CYBER 180-class machines.
17. Applicable for CYBER 180-class machines except models 810, 815, 825, and 830.
18.
Applicable
for
models
810,
815,
825,

3-90

NOS

Version

Analysis

Handbook

and

Revision

830

o n l y.

>«s%

LBC — Load Buffer Controllers Entry

Parameter Description
type (Continued)
type Description
HT Install controller with half-track (MA710) controlware.
ID Install 7255-1 adapter with full-track (MA462) controlware.
M8 Install 7990 controller with MB466 controlware.
NF Identify channel(s) as having full-track controller, but do not
install the controlware.
NH Identify channel(s) as having half-track controller, but do not
install the controlware.
NI Identify channel(s) as having full-track 7255-1 adapter, but do
not install controlware.
NM

Identify channel(s) as having full-track 7155-1 controller, but
do not install the controlware.

NN Identify channel(s) as having NADs, but do not install the
controlware.
NP Identify channel(s) as having 7155-401 controller, but do not
install the controlware.
NX Identify channel(s) as having 5870 printer, but do not install
the controlware.
N8 Identify channel(s) as having 7990 controller, but do not install
the controlware.
PH Install 7155-401 controller with MA722 controlware.
ci Disk channels; type determines if controlware is installed on these
channels.

yms.

Revision

Deadstart

Decks

3-91

XM — Declare Extended Memory Space for Buffers or User Access

The controlware version number that can be loaded into the adapter or controller
types
is:

i***MS

Adapter
Controller Controlware Version Number
7054

MA710

7152 MA710, MA401
7154 MA710, MA401
7155-1 MA721
7155-401 MA722
7165

MA464

7255-1 MA462
7990

MB466

XM — Declare Extended Memory Space for Buffers or User Access
The XM entry reserves space for I/O buffers and causes initialization of tables for user
access to extended memory.
NOTE
Except on models 865 and 875, the assignment of user access to extended memory ^^
forces jobs using user access to use CPU 0. This prevents CPUMTR from being
locked out during large block transfers to or from extended memory on dual-CPU
mainframes.
The XM entry is required if the system contains user-accessible extended memory or
buffered devices. If UEM is to be used only for user-accessible extended memory, you
do not need to specify an extended memory EST entry in the EQPDECK. To access
UEM, it must be enabled (refer to the USER EXTENDED MEMORY IPRDECK entry
later in this section).

3-92

NOS

Version

Analysis

Handbook

Revision

UEMIN — UEM Equipment Initialization

The XM entry format is:
XM=id,iob,uec,EM.
Parameter Description
id Identifier of the mainframe that will access the reserved extended
memory space; id is required.
If an XM entry refers to shared extended memory (ECS or ESM as a
link device), the XM entry must be present in the EQPDECKs of all
linked mainframes. If an XM entry refers to nonshared extended
memory (UEM), the XM entry must be present only in the EQPDECK
for its own mainframe.
iob Number of words/10008 reserved for buffers for DB, DC, DF, DH, DN,
DV, or DW devices; from 40s to 37770s. This value is limited by'the '
amount of memory available; either physically present or logically
available (allocated in the CMRDECK and EQPDECK entries). The
optimum number of words to reserve is the amount left after the
alternate system library and user-accessible extended memory are
taken into account. If no buffered devices are defined, enter 0.
uec Number of words/10008 of extended memory to reserve for user access;
maximum value is 777408. This value is limited by the amount of
memory available; either physically present or logically available
(allocated in the CMRDECK and EQPDECK entries).
EM For models 865 and 875 and CYBER 180-class machines,
user-accessible extended memory can be allocated in UEM without
allocating UEM as an equipment. If you want only user-accessible
extended memory in UEM, clear or do not specify an extended memory
EST entry in the EQPDECK and enter XM with the uec size and the
EM keyword.
For models 865 and 875, if you specify EM, user-accessible extended
memory is allocated in UEM regardless of the presence of ECS or
ESM; if you omit EM, user-accessible extended memory is allocated in
the device defined in the extended memory EST entry.
UEMIN — UEM Equipment Initialization
The UEMIN entry enables full initialization for UEM equipment during a level 0
deadstart. It is equivalent to an INITIALIZE,AL,est entry. The UEMIN entry can be
included as part of the EQPDECK on the deadstart file or it can be entered from the
system console at deadstart time. If the UEMIN entry is being used, the EQ entry for
the DE equipment is required. If you enter UEMIN when it's already set, it disables
the automatic initialization of UEM. The UEMIN format is:
UEMIN.

H$PP5\

Revision

Deadstart

Decks

3-93

ACCESS — Set Access Level Limits

.,rf^\

ACCESS — Set Access Level Limits
The ACCESS entry allows you to specify equipment access level limits for mass
storage, magnetic tape, two-port multiplexer, stimulator multiplexer, and unit record
type equipment. This entry is invalid for other types of equipment. This entry
determines the upper and lower limits for the range of access levels of the data
allowed to be read from or written to the equipment. The default equipment access
level limits are zero; no secure data can be read from or written on the equipment.
Values for this entry should be supplied by a site security administrator.
If you want the equipment access level limits specified by this entry to become the
device access level limits for mass storage equipment, that equipment must be
initialized. Refer to the NOS Version 2 Security Administrator's Handbook for more
information about equipment access and device access level limits.
This entry is ignored if the system is running in unsecured mode.
The format of the ACCESS entry is:
ACCESS,1ower,upper,ord11st.

Parameter Description
lower * Access level name specified in deck COMSMLS (refer to the NOS
Version 2 Installation Handbook) corresponding to the desired lower
limit.
upper Access level name specified in deck COMSMLS corresponding to the
desired upper limit.
ordlist One or more EST ordinals, separated by commas, or a range of
ordinals as described in Specifying Ranges of EST Ordinals earlier in
this section.

/ • ^

3-94 NOS Version 2 Analysis Handbook

Revision M

THRESHOLD — Set Disk Thresholds

THRESHOLD — Set Disk Thresholds
0ims.

The THRESHOLD entry enables you to set threshold values for the disk storage
devices specified by EST ordinals. The system uses these threshold values as limits
when monitoring disk verification failures, available disk space, and disk error
processing. If a threshold value is exceeded, the system performs a corrective action,
such as notifying the operator or restricting activity on the affected disk. The format of
the THRESHOLD entry is:
THRESHOLD,type=value,ordlist.

Parameter Description
type

value

You can specify one of the following threshold types. Refer to the DSD
THRESHOLD command in section 5 for additional information.
type

Description

Verification failure threshold (default).

Restricted activity threshold.

Low space threshold.

Recovered error threshold.

Unrecovered error threshold.

The threshold value can range from 0 to 3777s. If the value parameter
is omitted, the following default values are used.
type

value

ordlist

Revision M

1/8 of the number of tracks on the device.

1/16 of the number of tracks on the device.

50s

Enter one or more EST ordinals, separated by commas, or a range of
ordinals as described in Specifying Ranges of EST Ordinals earlier in
this section.

Deadstart Decks 3-95

EQPDECK Entries Made Only During Deadstart
A*ms

EQPDECK Entries Made Only During Deadstart
The following entries are valid only from the system console at deadstart time. They '
cannot be included as part of the EQPDECK on the deadstart file.
AUTOLOAD — Toggle Autoloading
The AUTOLOAD entry toggles the selection of buffer controller autoloading for all
7054/7154/7152/7155/7165 controllers and the 7255 adapter. The AUTOLOAD format is:
AUTOLOAD.

GRENADE — Clear Unit Reservations
The GRENADE entry causes unit reservations to be cleared on all 844 units physically
connected to each 7054/7154/7152/7155 controller and any 834 or 836 units connected to
a 7255 adapter. The GRENADE format is:
GRENADE.

)

INITIALIZE — Initialization Entry
To use a mass storage device that is defined with an EQ entry, it must have a label.
A label is written on a device when you initialize it by using either the INITIALIZE
command, during system operation, or the INITIALIZE entry in the EQPDECK, when
it is displayed at the system console at deadstart time.
A mass storage device's label is contained on a logical track (usually track 0). It *^^
contains information about the allocation and characteristics of a device (and its
units, if there is more than one unit on a device). This information is in the form of
a label sector for the first unit, a TRT for the device, and a label sector for each
unit.
Initialization does not automatically occur at each deadstart because mass storage
device labels are recovered during all deadstarts. Therefore, initialize a device only in
the following situations.
• To a d d a n e w m a s s s t o r a g e d e v i c e ( n o l a b e l e x i s t s o n t h e d e v i c e ) u s e t h e ^ ^
INITIALIZE entry.
• If parts of the label on a permanent file device have been destroyed by
maintenance operations (permanent files having been dumped to another device
before diagnostics were run), use the INITIALIZE entry during deadstart to write
a new label. Then reload the permanent files.
• If a device (usually a private auxiliary, public auxiliary, or alternate permanent
file family device) is added to a system during operation, use the DSD
INITIALIZE command to initialize it if it does not have a valid label on it when
it is added to the system.
• When an extended memory device is initially placed in maintenance mode, all
mainframes using extended memory must initialize it (the maintenance mode
parameter is described under EQ - Extended Memory EST Entry earlier in this
section). You must also enter the PRESET entry for multimainframe operation. ^a^

3-96

NOS

Version

Analysis

Handbook

Revision

INITIALIZE — Initialization Entry

During a deadstart, the INITIALIZE entry has the following characteristics.
• During a level 0 deadstart, it can be entered at the system console only when the
EQPDECK is displayed. It can be entered anywhere after the EQ entry for the
device.
If it is placed in the deadstart file EQPDECK, the system issues the error
message INCORRECT ENTRY when the EQPDECK is read from the tape.
• A total initialization (op=AL) assumes that no valuable information exists on the
device and creates a new label. When the new label is created, all previously
existing information on the device, except CTI, CDA, HIVS, and MSL, is lost.
• If the EQ status for the device is OFF when INITIALIZE is entered, initialization
of the device occurs whenever the device is set to ON status by the operator with
the DSD ON command during normal system operation.

0ms.

• If the device is not a master device, INITIALIZE (op=AL) only writes a label; if
it is a master device, then it also initializes the catalog track and writes EOIs at
the beginning of the permit track, the indirect access track (data chain), and each
catalog track.
• During a deadstart initialization (op=AL), all flaw reservations specified for a
device are lost and must be reentered, except for 844 type devices with
factory-formatted disk packs.
• During an initialize format pack (op=FP) for an 895 disk, NOS only formats
those cylinders it plans to use in large record format. NOS does not format the
disk cylinders occupied by CIP.
NOTE
If a disk deadstart is in progress, the deadstart disk cannot be initialized. An
attempt to initialize it will result in the system issuing the error message
INCORRECT ENTRY.
The format of INITIALIZE is:
INITIALIZE,op,est,,est2 estn.
Parameter Description
op Level of initialization; one of these values:
op

Description

AF Initialize account dayfile.
AL Total initialization. For an 895 disk, the AL parameter is
equivalent to the FP parameter if an initial install of CIP was
done or if CIP was released.
DF Initialize system dayfile.
EF Initialize error log.

Revision

Deadstart

Decks

3-97

INITIALIZE — Initialization Entry

Parameter Description
op

(Continued)

^fsm%^

op Description
FP Initialize format pack (an automatic selection of AL also occurs).
This option applies to 844 and 895 disks only.
MF Initialize binary maintenance log.
PF Initialize permanent files.
QF Initialize queued files.
esti EST ordinal of mass storage device to be initialized; from 5 to 7778.
If the ordinal refers to a family permanent file device, then family
name, device number, and mask (if it is a master device) are specified
on the PF entry.
If it is an auxiliary device, the pack name is specified on the PF entry.
Total initialization (op=AL or FP) is the only initialization that is independent of the
content of the pack, if the initialization occurs during deadstart. If the initialization is
done while the system is running, it is applied to the device after the check mass
storage (CMS) routine has recovered it. If CMS cannot recover the device, the
initialization is similar to a deadstart initialization (that is, all information on the
device is lost).
The device number, family name, and device masks can only be changed during a
total initialization. Since all devices may contain permanent files, you should include
a PF entry for a device when performing a total initialization. If you do not, the
device is assigned a default family name, device number, and device masks. It is
possible that these parameters may conflict with other devices in the system. If a
conflict occurs, resolve it by using PF entries.
If you initialize a nonremovable device without a PF entry, the device mask and
secondary mask default to 377s for the smallest EST ordinal larger than 5. For all
other equipment, including equipment 5, the default masks are set to 0 (zero). The '*4S5%,
d e f a u l t f a m i l y n a m e i s S Y S Ti d ( w h e r e i d i s t h e m a c h i n e i d e n t i fi e r ) . T h e d e f a u l t '
device numbers begin at 1 and increase by 1 (starting with EST ordinal 5) for each
device that you initialize without a PF entry.
The INITIALIZE entry operates in conjunction with the dayfile entries DAYFILE,
ACCOUNT, ERRLOG, and MAINLOG (refer to Dayfile Descriptions earlier in this
section) to determine where the dayfiles actually reside. The following examples
illustrate the various cases. Assume that the system has three mass storage devices
(EST ordinals 6, 7, and 10).

3-98

NOS

Version

Analysis

Handbook

Revision

INITIALIZE — Initialization Entry

Example 1:
For this example, no dayfile entries are made and no previous dayfiles exist.
The following EQPDECK entry is made.
INITIALIZE,AL,6,7,10.

All dayfiles reside on ordinal 6.
Example 2:
In this example dayfile entries are made, but no previous dayfiles exist.
The following EQPDECK entries are made.
DAYFILE=6,200.
ACCOUNT=7,200.
ERRLOG=10.
MAINLOG=10,200.
INITIALIZE,AL,6,7,10.

In this case, the dayfiles reside on the indicated devices (system dayfile on ordinal 6,
account' dayfile on ordinal 7, error log and binary maintenance log on ordinal 10).
The default buffer length is used for the error log buffer.
Example 3:
In this example, dayfile entries are made and previous dayfiles do exist.
Assume that the EQPDECK entries in example 2 are used.
Since a total initialization has been done on each device, no dayfiles are recovered.
They reside on the indicated devices.
Example 4:
In this example, dayfile entries are made, previous dayfiles exist, but no dayfile
initialization entries are made.
The following EQPDECK entries are made.
DAYFILE=6.
ACCOUNT=7.
ERRLOG=10.
INITIALIZE,PF.6.

The dayfiles may already reside on the specified devices, or they may reside on some
combination of the possible devices. In either case, since no dayfile initialization
entries are made, the old dayfiles are recovered. The residence of these dayfiles is
governed by the residence of the old dayfiles. The PF initialization entry returns all
permanent file space and relabels the device based on the recovered device
parameters. The dayfiles and queued files on this device are not affected by this
entry.

Revision

Deadstart

Decks

3-99

INITIALIZE — Initialization Entry

Example 5:
In this example, dayfile entries are made, previous dayfiles exist, no dayfile
initialization entries are made, and duplicate dayfiles are in existence.
Assume that the EQPDECK entries in example 4 are used.
For the dayfiles that do not have duplicates, the residence is defined by the current
residence of the files, not the EQPDECK entries. But assume that an error log is
recovered from ordinals 6 and 10. In this case, the most recent file becomes the
active error log. Its previous residence overrides the EQPDECK entry. The other file
becomes an inactive error log (an entry exists in the mass storage table of the device
pointing to the inactive file, but the file is not in use by the system).
To produce an inactive error log, the site must run in the following manner.
1. Assume an 844 disk subsystem with two or more spindles is being used. Run with
unit 1 equated to EQ6 and unit 0 unused.
2. Redeadstart, equate unit 0 to EQ6, and do not use unit 1. 1
3. Redeadstart, equate unit 0 to EQ6, and unit 1 to EQ7.
Since unit 0 has the most recent copy of the error log, this copy would become an
active error log and the copy on unit 1 would become an inactive error log.
Example 6:
In this example, dayfile entries are made, the previous dayfiles from example 2 exist, ^^
and
initialization
entries
are
made.
)
The following EQPDECK entries are made.
DAYFILE=7.
ACCOUNT=7.
ERRLOG*10,300.
MAINLOG=10.
INITIALIZER, 6.
INITIALIZE,QF,6.

In this case, the account dayfile is recovered and continued on ordinal 7. The binary
maintenance log is recovered and continued on ordinal 10 with a CM buffer length of
100. The error log is recovered and continued on ordinal 10 with a CM buffer of 300s
words. The system dayfile space on ordinal 6 (from example 2) is released and the
new system dayfile starts on ordinal 7. The QF initialization entry releases all space
reserved by queued files on ordinal 6.
The CM buffer length is not affected by dayfile recovery. It is always specified by the
values defined in the EQPDECK entries. If no buffer length entries exist, the system
default values are used.

r"5*%

3-100

NOS

Version

Analysis

Handbook

Revision

PRESET — Preset the Link Device Entry

PRESET — Preset the Link Device Entry
This entry defines allocation space and initializes the tables (MST, TRT, MRT, and
DAT) on the link device that are required for management of shared multimainframe
mass storage devices. The entry is valid only for level 0 deadstarts by the first
mainframe in the multimainframe complex to deadstart.
Once PRESET is issued, the SHARE entry is disabled. Therefore, all SHARE entries
must precede the PRESET entry. The PRESET entry has two formats:
PRESET.

or
PRESET,n.

Parameter Description
n Number of shared devices; from 1 to 77s.
If you specify n, space is allocated for the specified number of shared devices. Use this
entry when the total number of shared devices is greater than the number of shared
devices defined in the EQPDECK of the first mainframe in the multimainframe
complex to do a level 0 deadstart.
If you do not specify n, the link device is preset, and the amount of table space
reserved for the shared devices is determined by the number of shared entries in the
EQPDECK.

Revision

Deadstart

Decks

3-101

PRESET — Preset the Independent Shared Device Entry

PRESET — Preset the Independent Shared Device Entry
This entry presets the independent shared devices in a multimainframe complex. The )
MST, TRT, MRT, and DIT are maintained on the mass storage device itself and are
not affected by the PRESET entry. This entry is used in conjunction with the ISHARE
entry. It is valid only on a level 0 deadstart by the first mainframe in the
multimainframe complex to deadstart. All ISHARE entries must precede the PRESET
entry.
The format is:
PRESET=est1,est2,...,estn.

Parameter Description
esti EST ordinal of the ISHARE device; from 5 to 777s. Ranges of ordinals
can be specified, as described under Specifying Ranges of EST Ordinals
earlier in this section.
Refer to section 13, Multimainframe Operations, for suggestions on shared device ^]
configurations.
WARNING
If a PRESET is entered for a device that is already in use by a second machine in a
multimainframe complex, system failures may occur on both machines, and data on
the device may be destroyed.
If a PRESET is entered for a device while a second machine in a multimainframe
complex is down, and if that second machine later attempts to perform a level 3 /a(S%
deadstart and use that device, system failures may occur on both machines, and data
on the device may be destroyed.
RESET — Reset Device Attributes
The RESET entry rescinds all device-related attributes resulting from entries such as
REMOVE, SYSTEM, MSAL, and so on. It restores the values specified with the last
EQest
entry
encountered.
The
format

is:

RESET=est 1,est z....,estn •

Ranges of ordinals are not allowed; each ordinal must be entered individually.

z^SSv

3-102

NOS

Version

Analysis

Handbook

Revision

APRDECK

APRDECK
The auxiliary mass storage parameter deck (APRDECK) is a text record on the
deadstart file that is processed during system initialization. APRDECK entries identify
areas of mass storage that are unusable (flawed areas) and prevent the system from
accessing them. The system uses the information in the APRDECK entries to build the
TRT for each device that resides in CMR and also in the mass storage device label.
You can place up to 64 APRDECKs on the deadstart file. Placing several APRDECKs
on the same deadstart file allows you to use the same file to deadstart several
configurations.

APRDECK Format
The first line in an APRDECK is the deck name. The format of the APRDECK name
is:
APRDnn

Parameter Description
nn Number identifying the APRDECK; from 00 to 77s.
An APRDECK must have a name and may have flaw entries. The first APRDECK
must contain the deck name APRD00 and nothing else. Subsequent APRDECKs must
be numbered consecutively and can contain flaw entries.
^^ The released version of the APRDECK contains no entries. You can enter flaws at
{ three different times:
• During deadstart, after entering all EQPDECK modifications.
• During system operation, using the FLAW entry (refer to section 8, K-Display
Utilities).
• During the configuration of a deadstart file.
If during deadstart you initialize a device and then enter NEXT, the system displays
f^ both the parameters on the device's EST entry and the APRDECK referenced by the
EST entry. You can then change the flaws for the device. If the first APRDECK is
referenced by the EST entry, the system displays the parameters on the device's EST
entry and the APRDECK name, APRD00. You can then enter flaws for the device.
These changes to the APRDECKs remain in effect until the next deadstart.
For example, in a EQPDECK, the EST entry for an 844-21 disk is:
EQ07=DI,ST=0N,EQ=0,CH=31/33,AP=5,UN=2.

After you initialize equipment 07 and enter NEXT, the following display appears.
EQ
07

TYPE
DI-1

UNITS
0

CHANNELS
31

APRD05
SLF=4173.
SLF=7062.

Revision

Deadstart

Decks

3-103

CAF — Clear All Flaw Reservations

The APRDECK entries described in this section are those to be used for entering /4esm.
flaws during deadstart or during the configuration of the deadstart file. Use the )
entries as follows.
• Use the CAF entry to clear all flaw reservations on a device.
• Use the SPF entry to specify the physical address of a flaw in extended memory.
(If a reservation for that physical address already exists, it remains in effect.)
• Use the SPF entry to specify the cylinder, track, and sector of a flaw in a disk.
(If a reservation for that physical area already exists, it remains in effect.)
• Use the CPF entry to cancel a particular SPF entry.
• Use the SLF entry to specify the logical address of a flaw. (If a reservation for
that logical address already exists, it remains in effect.)
• Use the CLF entry to cancel an SLF entry.
NOTE
All numeric values entered in the APRDECK must be entered in octal.
Either obtain flaw addresses from a customer engineer, or run the MST (mass storage
test) on the device to determine the bad areas. MST specifies the physical address of
flaws.
The system reads the flaw information recorded on the utility flaw map of an
881/883/885 disk pack during the initialization of 844/885 equipment and reserves the
appropriate areas. For multiunit devices, the flaw reservation is the union of all
utility flaw maps. This automatic flawing process occurs in addition to any
APRDECK entries. However, you cannot clear areas recorded as flawed on the utility
flaw map of an 881/883/885 disk pack with the CAF entry. Refer to appendix G for
information on clearing these flaws.
You can list all APRDECKs on the deadstart file by accessing the system file
SYSTEM with an ASSIGN or COMMON command, then using the T parameter on
the CATALOG command. Refer to the NOS Version 2 Reference Set, Volume 3 for
more information.
CAF — Clear All Flaw Reservations
The CAF entry clears all flaw reservations previously made with SLF or SPF entries.
The format is:
CAF.

3-104

NOS

Version

Analysis

Handbook

Revision

SLF — Set Logical Flaws on Any Mass Storage Device

SLF — Set Logical Flaws on Any Mass Storage Device
Use this entry to specify the logical address of a flaw. If the track was previously
reserved, that reservation remains in effect. The format is:
SLF=track.

Parameter Description
track Logical track number. Refer to table 3-6 for valid ranges of track
numbers.
CLF — Clear Logical Flaws on Any Mass Storage Device
To cancel a reservation made with an SLF entry, enter the identical track number
using the CLF entry. The format is:
CLF=track.

Parameter Description
track Logical track number. Refer to table 3-6 for valid ranges of track
numbers.
SPF — Set Physical Extended Memory Track or Disk Area Flaws
Two formats exist for the SPF entry. One format prevents the system from using
blocks (tracks) of extended memory. The other format prevents the system from using
sectors on disks.
Use the following SPF format to prevent the system from using blocks (tracks) of
extended memory.
SPF=Aaddress.

or
SPF=Aaddressi-Aaddress2.

Parameter Description
Aaddress The 1- to 7-digit octal logical address in a track of extended memory;
track containing the absolute address is reserved. The letter A must
precede the address.
Aaddressi Lowest (Aaddressi) and highest (Aaddress2) addresses in a range of
Aaddress2 logical addresses in one or more tracks of extended memory. All tracks
in the range are reserved. The letter A must precede the addresses;
the hyphen is required.
Use the following SPF format to prevent the system from using sectors on disks.
SPF=Ccylinder,Ttrack,Ssector.

0m*s

Revision

Deadstart

Decks

3-105

CPF — Clear Physical Extended Memory Track or Disk Area Flaws

Refer to table 3-6 for the number of cylinders, tracks, and sectors for each device.
Parameter Description
Ccylinder Cylinder number; the letter C must precede the number.
Ttrack Track number; the letter T must precede the number.
Ssector Sector number; the letter S must precede the number.
CPF — Clear Physical Extended Memory Track or Disk Area Flaws
To cancel a reservation made with an SPF entry, enter the identical information with
a CPF entry. The format is the same as for the SPF entries.
Table 3-6. Information for Setting or Clearing Flaw Areas

Device

Device
Type

Logical
Track
Range1

Cylinders/
Device1

Tracks/
Cylinder1

Sectors/
Track1

819, single density
819, double density
834
836
844-21, half track
844-21, full track
844-41/44, half track
844-41/44, full track
885-11/12, half track
885-11/12, full track
885-42, full track
887, 4K sector
887, 16K sector
895
9853, 2K sector
Extended memory

DV
DW
DD
DG
DI
DK
DJ
DL
DM
DQ
DB
DF
DH
DC
DN
DE/DP

4000-5465
4000-7153
4000-7135
4000-6565
4000-7137
4000-7137
4000-7147
4000-7147
4000-7221
4000-7221
4000-7221
4000-7343
4000-7343
4000-7351
4000-7726
4000-7620

633
1466
1457
1273
630
630
1464
1464
1511
1511
1511
1562
1562
1565
2601

12
12
12
30
22
23
23
23
50
50
12

24
24
40
57
30
30
30
30
40
40
40
46
13

17
23

1. Numbers are in octal.

3-106 NOS Version 2 Analysis Handbook

Revision M

IPRDECK

0^s

IPRDECK
The IPRDECK contains the system installation parameters that determine the system's
operation mode. From 1 to 64 IPRDECKs can exist on a deadstart file. The IPD entry
in the CMRDECK specifies which IPRDECK to use. If you omit the IPD entry, the
system uses the first IPRDECK on the deadstart file. IPRDECKs are named IPRDnn,
where nn is from 00 to 77s.
There are two IPRDECK console displays. The initial display, IPRINST, is an
instruction display. It gives a brief description of all valid IPRDECK entries. The
second display is the current IPRDECK. If either display overflows two screens, you
can page the display.
You can modify the IPRDECK by entering the appropriate changes or additions from
the console keyboard. Make these entries while either the IPRINST or IPRDECK is
displayed. Each console entry supersedes the value currently specified in the
IPRDECK.
NOTE
Changes made to the IPRDECK at deadstart time will be recovered across a level 3
deadstart; but not across a level 0, level 1, or level 2 deadstart. To make these
changes permanent, you must create a new deadstart file with these changes
incorporated into the IPRDECK.

You can list all IPRDECKs on your system by accessing the system file SYSTEM
with a COMMON command, then using the T parameter on the CATALOG command.
Refer to the NOS Version 2 Reference Set, Volume 3 for more information concerning
these commands.
Most of the IPRDECK entries are also valid DSD commands that can be used to
make changes during system operation. Changes to the IPRDECK using DSD
commands are retained after a level 3 deadstart, but not after a level 0, level 1, or
level 2 deadstart.

/0m*..

Revision

Deadstart

Decks

3-107

Job Control Information

Job Control Information
The QUEUE, SERVICE, and DELAY entries in the IPRDECK relate to job control. '
General information concerning job control follows.
Job Scheduling
Job scheduling is the control of jobs in the input (IN), executing (EX), and output (OT)
queues for each service class. Scheduling in the input and output queues is based on
the priority of a queue entry relative to all queue entries in the system. The priority
of a queue entry depends both upon how long the entry has been waiting in the queue
and upon the parameters specified on the QUEUE entry in the IPRDECK. The
following formula shows how the system computes the priority; all values are octal.
p

(ct-et)
»
+
wf

Va r i a b l e

Description

p Priority; LP ^ p ^ UP. LP (a parameter on the QUEUE entry) is the
lowest priority and UP is the highest priority.
wf Weighting factor; WF parameter on the QUEUE entry.
ct Current time in seconds.
et Time in seconds at which the job entered the queue.
lp Lowest priority; LP parameter on the QUEUE entry.
When an input or output queue entry is created, its priority is the lowest priority (LP)
for its service class. The queue priority of the queue entry increases as time passes.
The rate at which the priority increases depends upon the weighting factor (WF). The
larger the weighting factor, the slower the priority increases. (The queue priority of an
entry with a WF of 108 increases eight times slower than an entry with a WF of 1.)
The queue priority increases either until the queue entry is selected for processing or
until the queue priority reaches the highest priority (UP). If the queue priority of an
entry reaches UP, it remains at UP until the entry is selected for processing. If the •y(!S%
queue priority is zero, the job or file is never selected by the job scheduler and stays '
in the queue until the operator either enters a DROP command or resets the priority
to a nonzero number.
Job scheduling for executing jobs determines how much execution time a job gets.
The amount of execution time depends both on the job's scheduling priority (which is
parameters specified on the QUEUE and SERVICE entries in the IPRDECK) and on
the scheduling priorities of other jobs that may be waiting for execution.

3-108

NOS

Version

Analysis

Handbook

Revision

Job Scheduling

When a job in the input queue is selected for execution, it gets an initial priority (IP;
a parameter on the QUEUE entry) for the execution queue. Scheduling priority
increases for a job in the execution queue in the same way as in the input and
output queues. After the job is scheduled to a control point, its scheduling priority
does not age; it is set to fixed values that are changed only when specific events
occur. Initially, the job's scheduling priority is set to the upper priority bound for its
service class (the value of the UP parameter on the QUEUE entry). The job's
scheduling priority remains at this fixed value until the job exceeds either its control
point time slice or its central memory time slice.

0$ms.

If the job exceeds its control point time slice (the CT parameter on the SERVICE
entry), its scheduling priority is lowered to the control point slice priority (the CP
parameter on the SERVICE entry). If the job exceeds its central memory time slice
(the CM parameter on the SERVICE entry) for the first time, its scheduling priority
is lowered to the initial lower priority (the IL parameter on the QUEUE entry); if
the job exceeds its central memory time slice for a second or subsequent time, its
scheduling priority is lowered to the lower priority bound (the LP parameter on the
QUEUE entry).
Exceeding the CP or CM slice does not, by itself, force a job to roll out. A job
remains at a control point until the job scheduler determines that it needs this job's
control 'point and/or memory for a job with a higher priority. If a job rolls out, either
to mass storage or to a pseudo-control point, its scheduling priority starts at the
current value and begins to age upward (in the same fashion as input and output
queue files). When the job scheduler again selects this job to run at a control point,
its scheduling priority is again set to UP.
For interactive jobs, there is an additional execution queue priority, TP (a parameter
on the SERVICE entry). It is assigned to the execution queue entry of a job
restarting after terminal I/O. The value of TP aids response time to program
prompts. Also, for interactive jobs, the initial priority (IP) has an added significance.
In addition to being the priority at which jobs are scheduled from the input queue to
the execution queue, IP is the priority assigned when a terminal command is entered.
Using separate TP and IP parameters allows the system to give faster responses to
users interacting with a job. To achieve this, a value for the TP parameter slightly
greater than the value for the IP parameter is recommended (refer to tables 3-7 and
3-8 and figure 3-6).
The relative values of the QUEUE and SERVICE parameters, both among service
classes and within a service class, affect system performance. For an example of
ranges of service class priorities, refer to figure 3-6. For an example set of specific
entries for the QUEUE and SERVICE parameters, refer to tables 3-7 and 3-8.

Revision

Deadstart

Decks

3-109

Job Scheduling

Control Points
A job leaves a central memory control point when any of the following conditions are
present:
• A job completes, aborts, or is suspended.
• A system request causes a job to be rolled out to wait for a resource to become
available or for a specified time period to elapse.
Such system requests include a job request for a tape or disk pack, a ROLLOUT
command, and execution of the ROLLOUT macro.
• Terminal input/output is required.
A job leaves central memory when the following conditions occur:
- The system requests terminal input and typeahead input is not available.
- You request terminal output and the recall parameter is specified on the
request.
- You issue a RECALL macro after a request for terminal output that omitted
the recall parameter.
• The control point is made available for a higher priority job.
This ensures reasonable service to all users in the system. The operating system
controls the amount of time each type of job can be at a control point. This
ensures that one job does not monopolize system resources.
When a job is rolled out, the priority increases as time passes, giving that job a better
chance to be selected for execution again. When the job is selected and rolled in, its
priority is changed to the value of the UP parameter on the QUEUE entry, and the
job scheduling priority cycle begins again. This description on job rollout applies to
local batch, remote batch, and interactive jobs that are not doing interactive I/O. For
interactive jobs that do terminal I/O within a time slice, scheduling priority is slightly
different. When I/O is complete and input, for example, is available, the system assigns
the rolled-out job the terminal I/O scheduling priority (TP parameter on the SERVICE
entry). The TP parameter can be used to give the job a priority equal to the priority of ^^
jobs still within their initial time slice, an advantage over jobs in a second time slice, /^%
and a larger advantage over jobs in a third or higher time slice.
If a job at a control point exceeds the central memory time slice and it is not a
subsystem, the scheduling priority is set to the initial lower or lower bound priority
(the IL or LP parameter on the QUEUE entry) for its service class. Thus, any job in
the queue with a higher priority forces the executing job with the lower priority to
be rolled out. The rolled-out job ages normally until its priority is higher than the
priorities of either the jobs in the input queue or a job that is executing; then it is
again scheduled to a control point.
Once a job is scheduled, it is desirable to use the resources allocated before another
job forces it out. If a job maintained its scheduling priority when it was assigned to a
control point, another job could age past that job and force it to be rolled out before
it had an opportunity to use its time slice. For this reason, when a job is assigned to
a control point and its priority is within the queue aging range, it is given a priority
equal to the highest priority (the UP parameter in the QUEUE entry) for its service
class.

3 - 11 0

NOS

Version

Analysis

Handbook

Revision

Job Scheduling

Pseudo-control Points
/S*!\

If pseudo-control points are defined, a job that is forced out of a control point may
remain in central memory at a pseudo-control point, rather than being rolled out to a
mass storage device.
• If the job is preempted by a higher priority job, the scheduling priority stays the
same.
• If the job's control-point time slice has expired, the scheduling priority drops to
the control-point slice priority.
Jobs with the following characteristics are excluded from using pseudo-control points:
• Connection to a system control point.
• Accumulator overflow flags set.
j ^ ^ N t

• Assigned to the first control point or the last control point.
• Error flag set.
Number of Control Points and Pseudo-control Points Available

0^S

Selecting the number of control points available on the system depends on the amount
of memory space available, the job mix, and the mode in which the system is being
run. Up to 348 control points can be defined. Each control point needs 2008 words of
CMR space. For example, if an installation is running only TAF, then four or five
control points may suffice. On the other hand, if the system is running a large number
of interactive terminals with heavy permanent file activity, 20 or more control points
may be needed. You may need to study memory and control point use in order to
correctly determine the setting of this option. The DSD W,R display and/or the ACPD
and PROBE utilities may be useful in making this determination.
• If memory use is high and control point use is low, select fewer control points.
• If control point use is high and memory use is low, select more control points.
Selecting the number of pseudo-control points depends on the same variables that are
used to determine the number of control points. Up to 34s pseudo-control points can
be defined. The pseudo-control points provide more effective use of central memory in
environments where an insufficient number of control points create a system
bottleneck. Like a control point, each pseudo-control point needs 200s words of CMR
space.
• If memory use is high and control point use is lower, do not select any
pseudo-control points.
• If control point use is high and memory use is low, select pseudo-control points.

/im^s

0^S

Revision

Deadstart

Decks

3 - 111

Memory Control

Memory Control
You can control the maximum memory allowed for job types and for service classes x /
with the parameters you specify on the SERVICE and DELAY entries in the
IPRDECK.
These parameters specify these lengths:
• Maximum field length divided by 1008 for a job in a service class.
Maximum field length divided by 1008 for all jobs of the specified service class.
Maximum extended memory length in words divided by 10008 for a job in a
service class.
Maximum extended memory length in words divided by 1000s for all jobs of the
specified service class.
• Amount of central or extended memory to leave between job field length, if
possible.
Initially, the scheduler attempts to find the highest priority job that meets the memory
constraints. However, if the scheduler is unable to schedule a job and has explicitly
rejected one or more jobs because the total field length or the total extended memory
field length for a service class would be exceeded, it attempts to schedule a job a
second time if flexible partitions are enabled (refer to FLEXIBLE PARTITIONS in this
section). During this second attempt, any job that requires other jobs to be rolled out is
not scheduled; otherwise, the constraints (service class total field length and total
extended memory field length) are ignored, and the job is scheduled at the lower bound
priority, LP (a parameter on the QUEUE entry). This means that the constraints are
applied as long as there are enough jobs of each service class. However, if central
memory is unused and no other jobs are available, the scheduler attempts to schedule
the jobs without the constraints.
All of these parameters can be changed by using the SERVICE, QUEUE, and DELAY
entries.
Example of Job Control Parameters
An example set of entries for the job control parameters is shown in tables 3-7 and
3-8. These entries fall within the example of ranges of service class priorities shown in
figure 3-6. Neither the specific entries nor the ranges are recommended; they are
strictly examples to aid you in selecting QUEUE and SERVICE entry parameters.
The following discussion indicates the significance of the values chosen and how they
relate to each other.
The entry (lowest) priority (LP parameter in the QUEUE entry) of the system service
class input queue is higher than all entry priorities, except the network supervision
and subsystem entry priorities, because it is assumed that an operator-initiated job
should receive prompt attention. A system job rolls out any batch job. The entry
priority (LP) of the network supervision service class input queue is set high to
ensure adequate response time from network programs and facilities such as CS, NS,
and NVF.
.•*^\

3 - 11 2

NOS

Version

Analysis

Handbook

Revision

Example of Job Control Parameters

The queue priorities for local batch, remote batch, and detached jobs are similar. The
time slice for detached jobs is shorter than for the local batch and remote batch jobs.
The assumption is that detached jobs need less CPU time than either local batch or
remote batch jobs.
The queue priorities are explained under Job Scheduling earlier in this section.
The time slices for the various service classes reflect the following objectives:
• To keep system jobs with their high entry priority from monopolizing system
resources.
• To keep at a minimum rollout activity caused by diagnostics running as
maintenance service class jobs.
• To allow most interactive jobs to compile, load, and begin execution in one time
slice.
• To give batch jobs a large time slice, because little is gained from rolling out
batch jobs. There is no problem with the time slices for batch jobs compared to
interactive jobs, because, with the priorities shown, an interactive job generally
causes a batch job to roll out.
• To ensure prompt service to all interactive users, without employing an excessive
number of rollouts, by setting the time slices for interactive jobs low. The time
slice parameters are critical to good interactive performance. In some cases,
depending on the system load, job size, and so forth, it may be desirable to
change these parameters during operation.

Revision

Deadstart

Decks

3 - 11 3

Example of Job Control Parameters

Interactive performance is sensitive to the relative values of the QUEUE and SERVICE
scheduling parameters, both within a service class and among service classes. Tables
3-7 and 3-8 show almost no overlaps of values except that local batch, remote batch,
and detached jobs could age slightly past interactive jobs if they remained rolled out
for a very long time (about 26 minutes). For the interactive service class, the range
between entry (lowest) priorities and the highest priority is wide, so that few jobs are
at the highest priority simultaneously. If many jobs reach the highest priority, their
priorities are the same, and the order in which the jobs entered the queue is lost. The
job scheduler selects jobs with equal queue priority in a random manner. The terminal
I/O priority (TP) is set slightly higher than the initial priority (IP) to reduce response
time for the user interacting with a job as compared to the user initiating a new job
step. This parameter setting improves the perceived responsiveness of the system for
the interactive users.
The CPU priorities reflect the following objectives.
• The maintenance service class jobs are run at the lowest priority. This handles
the background CPU and memory diagnostics.
• All other jobs, except network supervision service class jobs, run at the same
priority. It is generally not desirable to run one class of jobs at a higher priority
than another because the system would roll in jobs that occupy memory without
executing, until they exceed the central memory time slice.
• The network supervision service class is set high to ensure adequate performance
from network programs and facilities such as CS, NS, and.NVF.

3 - 11 4

NOS

Version

Analysis

Handbook

Revision

Example of Job Control Parameters

Table 3-7. Example Set of Job Control Parameters, Part I
Service
Classs

LP1

UP1

SY (system)

7770

BC (local
batch)

LP2

UP2 WF2 IP2

IL2

7776

2000

7000 1

7000

4000

1000

4004 1

2000

RB (remote
batch)

4000

1000

4004 1

2000

CT
(communica
tion task)

7770

7776

3000

7000 1

7000

4000

TS
(interactive)

7000

"7770

3700

7000 1

4004

3770

NS
(network
supervision)

7770

7776

7770

7776 1

7772

DI
(detached)

4000

1000

4000 1

2000

SS
(subsystem)

7770

7776

7770

7776 1
•

7772

MA
(mainte
nance)
In
(Installation)4

WF1

4000

1000

4004 1

2000

TP3

4024

2000

1. Input queue QUEUE parameter.
2. Execution queue QUEUE parameter.
3. Interactive job initial scheduling TP SERVICE parameter.
4. Installation classes 10, II, 12, and 13 all have release values the same as class BC.
5. All values are octal; DELAY parameters are JS=1, CR=30, AR=1750, and
MP = 400.

Revision M

Deadstart Decks 3-115

Example of Job Control Parameters

Table 3-8. Example Set of Job Control Parameters, Part II
Service?
Class

7776 1

10 • 20 6770 7777

30/30

| BC (local
| batch)

4000 1

20 200 3770 7777

30/30

| RB (remote
| batch)

4000 1

20 200 3770 7777

30/30

7776 1

10 200 6770 7777

30/30

1TS

7000 1

| NS (network
| supervision)

7000 1

10 200 7770 7777

| DI (detached)

7000 1

2 0 2 0 3 7 7 0 7 7 7 7 3 4 11 0 3 0 / 3 0

| SY (system)

1CT

7000

TD4

NJ4

LP1 UP1 WF1 CT2 CM2 CP3

7000

| (communica| tion task)
10

6770

7777

11 3 9

30/30

| (interactive)

1SS

7400

7776 1

j MA
| (mainte| nance)

7000

7776 1

7000 1

10 200 3770 7777

7770

7777

74/74

70/70

| (subsystem)

j In
| (installation8)

7777

2/2

30/30

| 1. Output queue QUEUE parameter.
| 2. Time slice SERVICE parameters
I 3. Control point slice priority CP SERVICE parameter.
| 4. Number of jobs NJ SERVICE parameter.
j 5. Time-out delay TD SERVICE parameter.
| 6. CPU priority (lower and upper bounds) CB SERVICE parameter.
| 7. All values are octal; DELAY parameters are JS=1, CR=30, AR=1750, and
| MP=400.
I 8. Installation classes 10, II, 12, and 13 all have release values the same as class BC.
| 9. A TS suspended job times out after 10 minutes when the time-out delay is 113.
| 10. A DI suspended job times out after 30 minutes when the time-out delay is 341.

3-116 NOS Version 2 Analysis Handbook

Revision M

Example of Job Control Parameters

10000-r

-IP.IL, B-IP.IL,
CP
CP

7400 --

7000--

IP IP-—
-CP
CP-

i-CP

6400--

6000

5400--

5000 --

4400--

IL.

4000 --

CP CP

■TP
•IP
IL B-CP

3400--

3000--

2400--

2000

- I P. I L

I P. I L

1400--

1000-I P. I L
400- •

Jk.

SY BC RB CT TS NS DI SS IMA SY BC RB CT TS NS DI SS MA SY BC RB CT TS NS DI SS MA
INPUT

EXECUTION

OUTPUT

Figure 3-6. Example of Ranges of Service Class Priorities

r
Revision M

Deadstart Decks 3-117

IPRDECK Entries Made Only During Deadstart

IPRDECK Entries Made Only During Deadstart
You can enter the following IPRDECK entries only during deadstart. They cannot be
entered as DSD commands. Changes to the IPRDECK are not retained across deadstart
unless a new deadstart file is created to reflect those changes. The entries are
described in alphabetical order.
COMLIB
Format:
COMLIB,username,family,D.
Default:
None.
Significance:
This entry specifies a user name and family for a library of permanent files that
can be accessed by users on all other families. This feature eliminates the need to
maintain duplicate copies of the files on the families that require access to the
files-. This entry can also be used to reduce validation file accesses for user names
such as LIBRARY in a single family environment. The number of COMLIB
entries that can be specified is controlled by the CMRDECK entry CLT.
Parameter Description
username The 1- to 7-character user name to be associated with the files to
be accessed. This parameter should be unique to all families in the
system. It cannot be associated with more than one family.
family Family name to be associated with username.
D If D is specified, the associated username and family are deleted
from the common library table.
CPM
Format:
CPM, Si =11!, 52^2.

Default:
System selection.
Significance:
This entry alters the central processor multiplier of type si, which is used in SRU
calculations. The si parameters are either 0 or 1 to indicate the multipliers SO or
Sl, respectively. Entering 0=n obtains a multiplier to be used for SO and entering
l = n obtains a multiplier to be used for Sl. (Refer to the NOS Version 2
Administration Handbook for a discussion of multiplier use.) The values of ni
range from 1 to 47s and are used as indexes to values defined in COMSSRU in
order to determine the multiplier value. The default values are listed in table 3-9. ^35%
/<^^\

3 - 11 8

NOS

Version

Analysis

Handbook

Revision

CPM

Table 3-9. CPM Default Values for n\
ni (Octal)

COMSSRU
Name

Mainframe
Model

COMSSRU Default
Multiplier Value

CP62

6200

1.0

CP64

6400

1.0

CP65

6500

1.0

CP66

6600

1.0

CP67

6700

1.0

CP71

1.0

CP72

1.0

CP73

1.0

CP74

1.0

C171

171

1.0

C172

172

1.0

C173

173

1.0

C174

174

1.0

C175

175

1.0

C176

176

1.0

C720

720

1.0

C730

730

1.0

(Continued)

0$ms
Revision M

Deadstart Decks 3-119

CPM

Table 3-9. CPM Default Values for ni (Continued)
ni (Octal)

COMSSRU
Name

Mainframe
Model

COMSSRU Default
Multiplier Value

C740

740

1.0

C750

750

1.0

C760

760

1.0

C810

810

1.0

C815

815

1.0

C825

825

1.0

C830

830

1.0

C835

835

1.0

C840

840

1.0

C845

845

1.0

C850

850

1.0

C855

855

1.0

C860

860/870

1.0

C865

865

1.0

C875

875

1.0

C960

960

1.0

C990

990/994/995

1.0

ICM1

Model on which
you are installing.

1.0

ICM2

Model on which
you are installing.

2.0

ICM3

Model on which
you are installing.

3.0

ICM4

Model on which
you are installing.

4.0

ICM5

Model on which
you are installing.

5.0

3-120 NOS Version 2 Analysis Handbook

Revision M

CSM

0jms
CSM
Format:
CSM=csm.

Default:
64
Significance:
This entry sets the operating system character set mode. To change the character
set mode for the products, a change must be made in IPARAMS, and the products
must be reassembled.
csm Description
63 63-character set.
64 64-character set.
The system assumes a 64-character set if there is no CSM entry in the current
IPRDECK.
NOTE
Unpredictable and possibly serious problems occur if the operating system is
operating in one character set and the products are operating in another.
Therefore, ensure that all installed products and the operating system are in the
same mode.
DISK VALIDATION
Format:
ENABLE,DISK VALIDATION.
DISABLE,DISK VALIDATION.
Default:
Enabled.

Significance:

0m\

NOS performs hardware verification on each mass storage device during the
deadstart process before users are allowed to access the device. The hardware
verification sequence includes writing data to the disk, reading the data from the
disk, and finally comparing the read data with the write data to ensure integrity.
For 887 and 9853 disks, the hardware verification includes running in-line
diagnostics. Since the diagnostics verify the quality of the disk media more
completely, it is advantageous to run them. These diagnostics take approximately
3 minutes to execute, during which time the 887 or 9853 disk is not available for
use. In order to keep deadstart time to a minimum (such as, during testing), disk
validation can be disabled using the DISABLE,DISK VALIDATION command.

Revision

Deadstart

Decks

3-121

DSD

DSD
Format:
DSD, level ,commandi#command2#.. .#commandn
Default:

None.
Significance:
This entry specifies the initial command(s) to be executed by the DSD program
when the deadstart is complete. The commands can be the minimum number of
characters recognizable by DSD but must include terminating characters. Only the
last DSD entry on the IPRDECK for a given deadstart level is processed; other
DSD entries for the same level are ignored. The DSD entry cannot exceed one
line and a maximum of 60 characters can be specified.
Parameter

Description

)

level Level of deadstart (0, 1, or 2).
commandi DSD command to be executed for the level of deadstart specified.
Several commands can be specified by separating them with the #
(6-bit display code 60) or % (6-bit display code 63) character. These
characters may misposition parts of the console display of
IPRDECK if they appear as the upper 6 bits in a byte.
If you specify a series of commands including DSD display selection
commands, the display selection commands must be the last
commands. Failure to do so results in the system ignoring any
commands following the DSD display selection commands.
Examples:
DSD,0,MAI%X.QREC(PO=N)
DSD,0,X.QREC(PO=N)#SET,AEIQ.#QB.

3-122

NOS

Version

Analysis

Handbook

Revision

EI
Format:
EI =nn 1, nri2,..., nnx.
Default:
None.
Significance:
The EI entry should be used to ensure loading of the correct environment
interface for the operating system. This entry specifies up to six 2-character
environment interface names, one of which must be loaded while deadstarting a
CYBER 180-class machine. The deadstart will not be allowed to continue if the
environment interface loaded by CTI is not one of those specified by the EI entry.
You will have to load the correct environment interface or modify the EI entry in
the IPRDECK. If an EI entry is not present, you will not be warned at deadstart.
EXTENDED STACK PURGING
Formats:
ENABLE,EXTENDED STACK PURGING.
DISABLE,EXTENDED STACK PURGING.
Default:
Disabled.

Significance:
These entries specify the default action for instruction-stack purging for
nonsystem-origin jobs on CYBER 180-class machines. Refer to the MODE macro in
the NOS Version 2 Reference Set, Volume 4 for a description of instruction-stack
purging.
HARDWARE FAULT INJECTION
Formats:
ENABLE,HARDWARE FAULT INJECTION.
DISABLE,HARDWARE FAULT INJECTION.

Default:
Disabled.
Significance:

00?S

The entries enable and disable the simulation of hardware faults by normal jobs
executing special instructions. This simulation is intended for test purposes only,
and should not be enabled on a production system.

Revision

Deadstart

Decks

3-123

KEYPM

KEYPM
Format:
KEYPM»cc.

Default:
26
Significance:
This entry specifies the keypunch mode to be assumed during system operation.
cc

Description

26 026 keypunch mode.
29 029 keypunch mode.
This entry is used for all batch jobs submitted if the keypunch mode is not
specified on the job command. This does not apply to RBF.
MEMORY CLEARING
Formats:
ENABLE,MEMORY CLEARING.
DISABLE,MEMORY CLEARING.

Default:
Disabled.
Significance:
When memory clearing is enabled, central and extended memory are cleared when
released from a job (that is, when a job is rolled out, terminates, or reduces its
field length). When memory clearing is disabled, memory is cleared only when a a*z®s
job
requests
additional
m e m o r y.
■

3-124

NOS

Version

Analysis

Handbook

Revision

MICRO

MICRO
/$85»s

Format:
MICRO=namei, name2 name?.

Default:
None.
Significance:
The MICRO entry should be used to ensure loading of the correct microcode for
the operating system. This entry specifies up to seven 7-character microcode
names, one of which must be loaded while deadstarting a CYBER 180-class
machine. The deadstart will not be allowed to continue if the microcode loaded by
CTI is not one of those specified by the MICRO entry. You will have to load the
correct microcode or modify the MICRO entry in the IPRDECK. If a MICRO entry
is not present, you will not be warned at deadstart.
NAMIAF
Format:
NAMIAF=maxt.

Default:
2008
Significance:
This entry specifies the number of network terminals that can be connected to
IAF at one time. The maximum number of terminals IAF can support is 1039.
However, this value is dependent on the number of network terminals, multiplexer
ports, and stimulator ports specified in the deadstart decks.
Parameter Description
yms.

maxt Total number of network terminals; maxt can range from 1
to 14408.
PROBE
Formats:
ENABLE,PROBE.

DISABLE,PROBE.

Default:
Disabled.
Significance:
These entries enable and disable the data gathering facility of CPUMTR.

Revision

Deadstart

Decks

3-125

SCP

SCP
Formats:
ENABLE,SCP.
DISABLE,SCP.

Default:
Disabled.
Significance:
These entries specify whether to use the system control point facility. You must
enable SCP if CDCS, IAF, MAP, MCS, MSE, NAM, NVE, PLA, RBF, RHF, SMF,
SSF, or TAF will be used. If none of these will be used, leave SCP disabled so
that more CMR space is available.
SCRSIM
Formats:
ENABLE,SCRSIM.
DISABLE,SCRSIM.
Default:

Disabled.
Significance:
These entries enable or disable the simulation of the status/control register using
the interlock register on CYBER 70 Computer Systems (refer to appendix D for
information on the SCRSIM simulator).

3-126

NOS

Version

Analysis

Handbook

Revision

SECCATS
J0$^\

SECCATS
Format:
SECCATS=cat i,cat2, -..,catn.
Default:
All categories are enabled.
Significance:
This entry specifies the security access categories that will be allowed in the
system for processing when the system is in a secured mode. The values should
be supplied by a site security administrator. Refer to the NOS Version 2 Security
Administrator's Handbook.
Parameter Description
cati

Category names specified in deck COMSMLS corresponding to the
desired access categories. Initially, all categories are enabled. The
first SECCATS entry clears all categories, then sets the specified
categories. Subsequent SECCATS entries set additional categories:
SECCATS=ALL.

Enables all 32 categories.

SECCATS=NUL.

Disables all 32 categories.

SPC
Format:
SPC,d=lines.

Defaults:
64 lines at 6 lines per inch.
85 lines at 8 lines per inch.
Significance:
This entry specifies the charge in number of lines for a page of printed output at
the specified print density on non-PFC printers.
Parameter Description
d Density in lines per inch; d can be 6 or 8 lines per inch, but must
be specified in octal (6 or 10s).
lines

Revision M

Lines per page; lines can range from 16 to 255, but must be
specified in octal (20s to 377s).

Deadstart Decks 3-127

SPD

SPD
Format:
SPD=d.

Default:
6
Significance:
This entry specifies the assumed density for printed output.
d Description
6 6 lines per inch.
108 8 lines per inch.
SPL
Format:
SPL=length.

Default:
60
Significance:
This entry specifies the assumed page length in number of lines for printed
output; length can range from 16 to 255, but must be specified in
octal (208 to 3778).
SPW
Format:
SPW=width.

Default:
136
Significance:
This entry specifies the assumed page width in number of characters for printed
output; width can range from 40 to 136, but must be specified in octal (508
to 2108).

■ "

3-128

NOS

Version

Analysis

Handbook

Revision

SUBCP

SUBCP
Formats:
ENABLE,SUBCP.
DISABLE.SUBCP.
Default:
Disabled.

Significance:
These entries specify whether CPUMTR is to be initialized to handle subcontrol
point (TAF) processing.
If SUBCP is disabled, CPUMTR is not initialized to handle subcontrol point
processing. If you are not running TAF and if no user applications use subcontrol
point processing, disable SUBCP so that CPUMTR uses less central memory.
TCVM
Format":
TCVM=mode

Default:
(^

AS
Significance:
This entry sets the tape conversion mode to be assumed during system operation.
mode Description
AS ASCII 9-track conversion.
US ANSI (previously known as USASI) 9-track conversion (same as AS).
EB EBCDIC 9-track conversion.

Revision

Deadstart

Decks

3-129

TDEN

TDEN
Format:

TDEN=denslty.

Default:
HY for 7-track tapes.
PE for 9-track tapes.
Significance:
This entry sets the system tape density. When the density is set, any tape unit
accessed is automatically set to this density unless specified otherwise by a
magnetic tape request. Two TDEN entries may be present, one for 7 track and
one for 9 track.
density Description
LO 200 cpi (7 track).
HI . 556 cpi (7 track).
HY 800 cpi (7 track).
HD 800 cpi (9 track).
PE 1600 cpi (9 track).
GE 6250 cpi (9 track).
TDTR
Format:
TDTR=tracktype.
Default:
NT
Significance:
This entry sets the default track type.
tracktype Description
MT

track.

3-130

NOS

Version

Analysis

Handbook

Revision

TMS

TMS
Formats:
ENABLE,TMS.
DISABLE,TMS.

Default:

Disabled.
Significance:
These entries enable and disable the Tape Management System (TMS). These
entries are meaningless if the TMS binaries are not installed in the deadstart file.
TMSTO
V

Format:
TMSTO,N=tO,S=tO.

Default:
N=TC,S=FC
Significance:
( This entry specifies the default values for the TMS tape options parameter for the
LABEL command and the LABEL macro. The N parameter specifies the default
for nonsystem origin jobs and the S parameter specifies the default for system
origin jobs.
to Description
TC Sets the default to TO=TC (TMS processing with catalog error checking).
TE Sets the default to TO=TE (TMS processing without catalog error
(^

checking).
FC Sets the default to TO=FC (non-TMS processing with catalog error
checking).
FE Sets the default to TO = FE (non-TMS processing without catalog error
checking).
This entry is meaningless if TMS is disabled.

Revision

Deadstart

Decks

3-131

TRACE

TRACE
Formats:
ENABLE,TRACE.
DISABLE,TRACE.

Default:
Disabled.
Significance:
The entries enable or disable specification of monitor functions and other system
data to be traced, the TRACE and TRAP capabilities. To use these capabilities,
ENABLE,SYSTEM DEBUG, must also be entered.

j^S^v

3-132

NOS

Version

Analysis

Handbook

Revision

IPRDECK Entries

IPRDECK Entries
You can enter the following IPRDECK entries during deadstart and online during
system operation using the L display or DSD commands. The reason for entering them
online is to change the system's operation between deadstarts. Entries made during
system operation are not retained across deadstarts. Entries made during deadstart are
not retained across deadstarts unless a new deadstart file is created to reflect the
changes.
A description of the enabling and disabling of subsystems follows. The remaining
IPRDECK entries are described in alphabetical order.
Subsystems
You can initiate a subsystem by either of the following methods:
• Enter an explicit call to the subsystem procedure using a DSD command. The
command format is:
subffff

Variable Description
sub 3-character mnemonic for the name of the subsystem and subffff is
the name of the subsystem procedure (refer to Subsystem Control
Commands in section 5).
• Enter the DSD command AUTO or MAINTENANCE. This will initiate calls to all
subsystems that are currently enabled. The calls will be to subsystem procedures
with the same name as the name of the subsystem. You can choose to have either
the AUTO command or the MAINTENANCE command issued automatically at
deadstart time by specifying the command on the DSD entry in the IPRDECK.
A subsystem procedure may be either a record in the deadstart file or a permanent file
under system user name SYSTEMX (user index 377777s). If a subsystem procedure
with the same name is present in both places, the permanent file copy will be used.
Note that a *PROC is required in the LIBDECK for any procedure in the deadstart
file.
NOTE
Before you initiate a subsystem that uses the system control point facility (such as
NAM or CDCS), you must enable the system control point facility with the
ENABLE,SCP IPRDECK entry. Refer to SCP earlier in this section.
All subsystems, except BIO and MAG, are disabled by default. You can enable or
disable a subsystem by using IPRDECK entries or by using the SUBSYST L-display
utility. (For information about the SUBSYST L display, refer to the NOS Version 2
Operations Handbook.)
The IPRDECK entries that enable and disable subsystems may also assign a default
control point for a subsystem. Thus, even if you do not want to enable a subsystem,
you may want to explicitly disable a subsystem with an IPRDECK entry to assign a
default control point for the subsystem.

Revision

Deadstart

Decks

3-133

Subsystems

Use these IPRDECK entries to enable or disable a subsystem:
ENABLE,subsystem,cp.
DISABLE,subsystem,cp.
Parameter Description
subsystem Three characters that select the desired subsystem; one of these values:
subsystem Description
BIO

Local batch I/O for central site line printers, card
readers, and card punches.

CDC

CYBER Database Control System.

IAF

Interactive Facility. Do not specify the cp parameter on
the ENABLE entry for IAF.

MAG

Magnetic Tape Subsystem. Enable MAG if removable
auxiliary packs are used. Disabling MAG frees a control
point for other use.

MAP

MAP III or MAP IV.

MCS

Message Control System.

MSE

Mass Storage Extended Subsystem.

NAM

Network Access Method.

NVE

NOS/VE dual state.

PLA

Plato-NAM Interface.

RBF

Remote Batch Facility.

RDF

Remote Diagnostic Facility. Do not specify the CP
parameter on the ENABLE entry for RDF.

RHF

Remote Host Facility.

SMF

Screen Management Facility.

SSF

NOS-SCOPE 2 Station Facility.

STM

STIMULA. Do not specify the cp parameter on the
ENABLE entry for STM.

TAF

Transaction Facility.

3-134 NOS Version 2 Analysis Handbook

Revision M

r^^\

Subsystems

Parameter Description
r^

subsystem

(Continued)
NOTE
When MCS and RBF are started by the NAMI startup master file, the
ENABLE and DISABLE commands are ignored.
If an ENABLE is made for NVE and the subsystem procedure name is
also NVE, use the DSD IPRDECK entry to automatically down any
channels that NOS/VE uses.

CP Control point where the subsystem will reside. If you omit cp, the

current control point is used. If you enter 0 (zero) as the control point,
the subsystem may reside at any available control point. If you enter -n
as the control point, the subsystem's control point will be relative to the
system control point (-1 would be the last control point before the
system control point).

Omit cp for IAF, RDF, and STM.

0ms.

Revision

Deadstart

Decks

3-135

AUTORESTART
^m?\

AUTORESTART
Formats:
ENABLE,AUTORESTART.
DISABLE,AUTORESTART.
Default:
Disabled.

Significance:
These entries enable or disable the AUTORESTART installation parameter. If
AUTORESTART is enabled and if step mode is set during an environmental
shutdown, the system automatically clears step mode when the power environment
returns to normal. All jobs waiting in the input and rollout queues are initiated
by performing the processing associated with the DSD AUTO command. This
recovery process requires no operator interaction.
CARTRIDGE PF STAGING
Formats:
ENABLE,CARTRIDGE PF STAGING.
DISABLE.CARTRIDGE PF STAGING.
■'

Default:
Disabled.

Significance:
These entries specify whether permanent files that reside on MSE are staged to
disk. If disabled, jobs that attempt to access MSE-resident files are aborted.

3-136

NOS

Version

Analysis

Handbook

Revision

CLASS

CLASS
jg^V

Format:
CLASS,Ot ,SCi,SC2,

...,scn.

Default:
Origin Type

Service Class

Batch

Remote batch

Interactive

Significance:
Specifies the valid service classes for each origin type. The system stores this
information in the service class table (refer to the NOS Version 2 Systems
Programmer's Instant).
Parameter Description
ot Origin type; must be BC (batch), RB (remote batch), or IA
(interactive). This parameter is required and order dependent.
sci Service classes. Each class selected causes validation for that
service class for the origin type specified by ot. Entering a service
class that already has validation clears validation for that service
class. You can select from 1 to 36 service classes for each origin
type. This command does not accept class SS (subsystem).
Service class is one of these values:
sc Description
BC Local batch.
CT Communication task.
DI Detached interactive.
In Installation class n (0 ^ n ^ 3).
MA Maintenance.
N S N e t w o r k s u p e r v i s o r.
RB Remote batch.
SY System.
TS Interactive.
ALL Causes validation of all service classes except subsystem
(SS) amd deadstart (DS).
NUL Clears validation for all service classes.

Revision

Deadstart

Decks

3-137

CPTT

CPTT
Format:
CPTT=n.

Default:
1008 sectors.
Significance:
This entry specifies the CPUPFM transfer threshold (CPTT). The value of CPTT
determines whether an indirect access file transfer will be processed entirely
within the PP program PFM or whether the CPU program CPUPFM will be
called to perform the transfer. Since CPUPFM can transfer large files faster than
PFM, CPUPFM transfers files that exceed the threshold value.
Depending on the configuration, a site can adjust this value up or down. A site
with buffered I/O devices, for example, may find it advantageous to set a lower "^
value. If a site wishes to disable CPUPFM transfers altogether, a value of zero
(CPTT=0) may be specified.
Parameter Description
n CPUPFM transfer threshold value that will be defined in common
deck COMSPFM; 0 ^ n ^ 7777s PRUs.
DEBUG
Format:
DEBUG.

Default:
Disabled.
Significance:
This entry selects or clears debug mode, depending upon the current status.
If enabled, debug mode is selected. The message DEBUG appears in the header of
the left screen display. Debug mode provides system origin privileges to validated
users and allows modifications to be made to the running system.
If disabled, debug mode is cleared. It is recommended that debug mode not be
allowed in a normal production environment.
On a secured system, this entry is ignored. While the console is in security
unlock status, debug mode can be set using DSD command DEBUG.

3-138

NOS

Version

Analysis

Handbook

Revision

DELAY

DELAY
Format:
DELAY,ARar.CIci.CRcr.JQjq.JSjs.MPmp.
Default:
None.
Significance:
This entry specifies the system delay parameters. Refer to table 3-7 for an
example set of parameter entries. Refer to figure 3-6 for an example of ranges of
service class priorities.
Parameter Description
ARar

PP recall interval in milliseconds. This parameter specifies the time
interval after which a peripheral processor unit (PP) in the PP
recall queue will be recalled, ar ranges from 1 to 77778.

CIci

CPU job priority interval in milliseconds. This parameter specifies
the time interval after which the priorities of jobs in the wait
queue are incremented, ci ranges from 0 to 7777s.

CRcr

CPU recall period in milliseconds. This parameter specifies the
amount of time a job remains in recall (X status) when an RCL
request is placed in RA + 1. cr ranges from 1 to 77778.

JQjq

Exponent used to determine the input file scheduling interval in
seconds, jq ranges from 0 to 14s. The interval in seconds between
scheduling of input files is calculated as follows:
interval = 2**jq

JSjs

Job scheduler interval in seconds. This parameter specifies the
interval in which the job scheduler is called. The scheduler may
also be called at other times, js ranges from 1 to 7777s.

MPmp

Memory padding value expressed as 100s word blocks, mp ranges
from 0 to 7778. This parameter specifies how much additional
(unassigned) memory should be allocated between the end of the
newly assigned job field length and the beginning of the next job.
Increasing this value reduces the probability that a job will be
storage moved in response to a request for more memory.

Revision M

Deadstart Decks 3-139

DDP ROLLOUT PATH

DDP ROLLOUT PATH
Formats:
ENABLE,DDP ROLLOUT PATH
DISABLE,DDP ROLLOUT PATH

Default:
Disabled.
Significance
These entries determine which path a rollout to extended memory will take (CPU
or PP). The required supporting hardware (EM or DDP) must be present.
DFPT
Format:
DFPT=dtn.

Default:

DI1 (see the DFPT installation parameter in common deck COMSPFM).
Significance:
The DFPT entry resets the system default removable pack type. When accessing a j
removable auxiliary device with a permanent file command, the system checks
that the equipment type and pack name of the device match the equipment type
(R parameter) and pack name (PN parameter) on the command. If R is not
specified, the system uses the equipment type specified by DFPT.
Parameter Description
dt Disk device type of the removable pack.
n

3-140

Number

NOS

spindles

Version

the

Analysis

removable

Handbook

pack;

Revision

'"^

ENGR

ENGR
Formats:
ENABLE,ENGR.
DISABLE,ENGR.

Default:

Disabled.
Significance:
These entries enable or disable engineering mode. If enabled, the ENGR message
appears in the header of the left screen display. Engineering mode allows the
peripheral processing unit (PPU)/hardware diagnostics and the 881/883 pack
reformatting utility FORMAT to run while the system is in operation.
On a secured system, these entries are ignored. When the console is in security
unlock status, engineering mode can be enabled using the DSD command
ENABLE,ENGR.
FLEXIBLE PARTITIONS
Formats:
ENABLE,FLEXIBLE PARTITIONS.
DISABLE,FLEXIBLE PARTITIONS.
Default:
Enabled.

Significance:
This entry enables or disables flexible memory partitioning. The job scheduler
attempts to use memory space to the greatest extent possible when flexible
partitions are enabled. Some service classes may be allotted more total memory
space than memory partitioning constraints normally allow. If flexible partitions
are disabled, the total memory used by jobs of a given service class are never
allowed to exceed the maximum specified on the SERVICE command (AM and EM
parameters).

Revision

Deadstart

Decks

3-141

LOCK

LOCK
Format:
LOCK.

Default:
Unlocked.
Significance:
This entry specifies the system is locked. This software function prevents entry of
restricted commands; all other DSD commands can be entered. The console is
normally locked when the system is being used in a production environment.
LOGGING
Formats:
ENABLE,LOGGING.
DISABLE,LOGGING.

Default:
Disabled.
Significance:
These entries specify whether dayfile messages intended for system analysis are
logged in the dayfile. Typical messages deal with informing the user that the
program is making inefficient CIO calls, such as reading to a full buffer or
writing from an empty buffer. The dayfile messages are documented in an
appendix of the NOS Version 2 Operations Handbook.

3-142

NOS

Version

Analysis

Handbook

Revision

MASTER MSE

MASTER MSE
Formats:
ENABLE,MASTER MSE
DISABLE,MASTER MSE

Default:

Disabled.
Significance:
These entries specify whether the MSE executive program (SSEXEC), when
initialized, is to run in master (enabled) or slave (disabled) mode.
MS VALIDATION
Formats:
ENABLE,MS VALIDATION.
DISABLE,MS VALIDATION.

Default:
Disabled.
Significance:
This entry enables or disables mass storage validation. If enabled, CMR is
increased by 48 words, and the system verifies that, for each mass storage device,
the sum of the counts of unreserved tracks and preserved files equals values
specified in the device's mass storage table.
If the device is a master device (contains user catalogs), the system also verifies
these conditions:
• The device's track reservation table (TRT) specifies that the first tracks of the
indirect access file chain and the permit area are reserved and preserved.
The label track is linked to the first catalog track.
The number of catalog tracks is a power of 2.
The catalog chain is reserved, of correct length, and contiguous if flagged as
such in the device's MST.
To enable/disable mass storage validation with a DSD command entry, enable the
validation in the IPRDECK during a level 0, 1, or 2 deadstart.

Revision

Deadstart

Decks

3-143

OQSH

OQSH
Format:
OQSH=level.

Default:
None.
Significance:
This entry specifies the value of the output queue special handling (OQSH) level.
Output files with an access level equal to or greater than the output queue
special handling level will remain in the queue until released by the DSD
command RELEASE. When no OQSH level or access level name LVLO is selected,
all files will be processed. The value for this entry is supplied by the site security
administrator.
Parameter Description
level

Access level name specified in deck COMSMLS (refer to the NOS
Version 2 Installation Handbook) that corresponds to the desired
output queue special handling level.

PCLASS
Format:
CLASS, SCO,SCi , ....SC7 .

Default:
None.
Significance:
Specifies the service class associated with each priority level (PO through P7) for
selection on the Job command (refer to the NOS Version 2 Reference Set,
Volume 3).
Parameter Description
SCi

The 2-character service class symbol. Because parameters are
positional, a comma must appear for any null parameter. The
default for a null parameter is that no service class will be
associated with the priority level represented by the null
parameter's position in the string. This command does not accept
the SS (subsystem) service class. Refer to the SERVICE IPRDECK
entry later in this section for a list of service classes.

.imfejjjV

3-144 NOS Version 2 Analysis Handbook

Revision M

PF VALIDATION

PF VALIDATION
Formats:
ENABLE,PF VALIDATION.
DISABLE,PF VALIDATION.
Default:

Disabled.
Significance:
These entries enable or disable preserved file (PF) validation. If enabled, the
system aborts an attach of a direct access permanent file if its end-of-information
(EOI) was altered during recovery of the file. If NA (no abort) is specified on the
attach request, the system attaches the file.
If mass storage validation is also enabled, TRT verification of preserved files
takes place during a level 3 deadstart as follows:
• For all files, the system ensures that all tracks are reserved and that no
circular linkage exists.
• For all queued, permanent direct-access, and fast-attach files, the system also
ensures that the first track is preserved.
If mass storage validation is enabled on a level 1 or 2 deadstart, TRT verification
takes place automatically, regardless of the status of PF VALIDATION.
PRIVILEGED ANALYST MODE
Formats:
ENABLE,PRIVILEGED ANALYST MODE.
DISABLE,PRIVILEGED ANALYST MODE.

Default:
Disabled.
Significance:
These entries enable or disable privileged analyst mode operations. If enabled, a
user validated with AW = CPAM (refer to the NOS Version 2 Administration
Handbook for information on MODVAL validation) is permitted to read system
status information (such as the system dayfile, account file and error log) using a
nonsystem-origin job. On a secured system, this entry is ignored. Refer to the
DSD ENABLE/DISABLE command in section 5 for more details.

Revision

Deadstart

Decks

3-145

PRIVILEGED RDF

PRIVILEGED RDF
Formats:
ENABLE,PRIVILEGED RDF.
DISABLE,PRIVILEGED RDF.

Default:
Disabled.
Significance:
These entries enable or disable privileged mode of RDF. If enabled, a user's
commands are checked to ensure that a maintenance function is being performed.
QUEUE
Format:
QUEUE,sc,qt,IL11,IPip,LPlp,UPup,WFwf.
Default:

None.
Significance:
This entry specifies the queue priorities associated with the input, executing, and
output queues for each job service class. Refer to table 3-7 for an example set of
parameter entries and to figure 3-6 for an example of ranges of service class
priorities.
Parameter Description
sc

Service class.
sc Description
BC

Local batch.

Communication task.

Detached interactive.

Installation class n (0

Maintenance.

Network supervisor.

Remote batch.

Subsystem.

System.

Interactive.

n *- 3).

<<<3^\

3-146 NOS Version 2 Analysis Handbook

Revision M

QUEUE

Parameter Description
qt

Job queue type.
qt

Description

EX Executing jobs.
I N I n p u t q u e u e d fi l e s .
OT Output queued files.

r
r

ILil

Priority a job receives when it initially exhausts its CM time slice
(refer to the SERVICE command CM parameter). Thereafter,
whenever the CM time slice is exhausted the job's priority will be
set to the value of lp. il ranges from 0 to 7777s, but must be in the
range of values for lp and up. This parameter is valid only for
executing jobs (EX).

IPip

Initial priority only for an executing batch job or for an interactive
job when a terminal command is entered. Online interactive jobs
with terminal I/O available are scheduled at tp priority (refer to the
SERVICE command TP parameter), ip ranges from 0 to 7777s, but
must be in the range of values for lp and up.

LPlp

Lowest priority. For an input or output queue file, the priority
assigned to a file or job entering the queue. For an executing job,
the priority assigned to job which has exceeded a non-initial CM
slice. The IL value is used for the first CM slice, lp ranges from 0 to
77778, but must be less than the value of up.

UPup

Highest priority. For input and output queues, this is the highest
priority a file can reach in that queue; aging stops when this priority
is reached. For the execution queue, this is the priority assigned to a
job when initially assigned to a control point, up ranges from 0 to
77778, but must be greater than the value of lp.

WFwf

Weighting factor for queue priority calculation; wf must be a power
of 2, from 1 to 40008. The smaller the weighting factor, the faster
the queue entry reaches its highest priority.

jp»\

Revision M

Deadstart Decks 3-147

REMOVABLE PACKS
y * ^ \

REMOVABLE PACKS
Formats:
ENABLE,REMOVABLE PACKS.
DISABLE,REMOVABLE PACKS.

Default:
Enabled.
Significance:
These entries enable or disable automatic label checking for mass storage devices
that are defined as removable.
If enabled, automatic label checking occurs. This status must be available to
perform label verification before removable devices can be accessed.
If disabled, any removable devices introduced into the system will not be
recognized.

,>«^SK

3-148 NOS Version 2 Analysis Handbook

Revision M

RESIDENT RDF

RESIDENT RDF
Formats:
ENABLE,RESIDENT RDF.
DISABLE.RESIDENT RDF.

Default:

Disabled.
Significance:
These entries enable or disable resident mode of RDF. While in resident mode,
RDF remains active, regardless of terminal inactivity, until RDF is disabled.
When resident mode is disabled, RDF becomes inactive if no one is logged on at
the remote diagnostic terminal for 15 minutes.
SECONDARY USER COMMANDS
Formats:
ENABLE.SECONDARY USER COMMANDS.
DISABLE,SECONDARY USER COMMANDS.
Default:
Disabled.

Significance:
The enable option allows jobs to issue more than one USER command. These
entries are ignored on a secured system since secondary USER commands are not
allowed on a secured system.

Revision

Deadstart

Decks

3-149

SECURES

SECURES
Format:
SECURES,0t,LA=1a,UA=ua.

Default:
The security access limits of the system origin type (SY) are set to access level
name LVLO. All security access limits for other origin types are set to system
limits.
Significance:
This entry specifies system limits for the system origin type (ot equals SY) or
limits for other origin types (ot equals BC, IA, or RB). System limits define the
highest and lowest levels allowed in the system. No job may execute and no file
may be accessed or created at a level outside this range.
Limits for origin types other than SY must be within the system limits. If origin /*%
type SY is specified, limits for all origin types are set to the selected values.
Both la and ua must be entered; they can be set to the same value, restricting
system access or a particular origin type access to a single level. These values are
supplied by a site security administrator.
This entry is not meaningful in an unsecured system.
Parameter Description
ot

Origin

type.

ot Description
SY System.
BC

Batch.

IA Interactive.
RB Remote batch.
la Access level name specified in deck COMSMLS (refer to the NOS
Version 2 Installation Handbook) corresponding to the desired lower
access level limit.
ua Access level name specified in deck COMSMLS corresponding to the
desired upper access level limit.

3-150

NOS

Version

Analysis

Handbook

Revision

SERVICE

SERVICE
Format:
SERVICE,sc.AMam.CBlpup,CMcm.CPcp.CScs.CTct.DSds.DTsc.ECec.EMem.FCfc.FLfl,
FSfs.NJnj.SDsd.TDtd.TPtp.

Default:
None.
Significance:
This entry specifies the service limits associated with each service class. Refer to
table 3-7 for an example set of parameter entries and to figure 3-6 for an
example of ranges of service class priorities.
Parameter

Descriiption

Service5 class; one of these values:
•

Description

Local batch.

Communication task.

Detached interactive.

Installation class n (0 -£ n -£ 3).

Maintenance.

Network supervisor.

Remote batch.

Subsystem.

System.

Interactive.

AMam Maximum field length divided by 100s for all jobs of the specified
service class. This parameter partitions central memory by limiting the
field length available to each service class. For example, if scheduling
a job to a control point would cause the AM value for its service class
to be exceeded for its service class, it may not be scheduled until the required field length is available. This means that a lower priority job
from a different service class may be scheduled first. However, a job
that would cause the AM value for its service class to be exceeded,
can be scheduled to a control point if not enough jobs in other service
classes exist to fill central memory and FLEXIBLE PARTITIONS is
enabled. The system attempts to use central memory to its greatest
capacity, am ranges from 0 to 77777s.

Revision M

Deadstart Decks 3-151

SERVICE

Parameter Description
CBlpup

Upper and lower bound CPU priorities.
Va l u e D e s c r i p t i o n
lp

Lower bound CPU priority, lp ranges from 0 to 77s.

Upper bound CPU priority, up ranges from 0 to 77s, but
must be equal or larger than the value of lp.

CMcm

Central memory time slice in seconds. This parameter specifies the
maximum amount of time a job of the specified service class can remain
in central memory either at a control point or at a pseudo-control point
before its priority is set to the lower boundary. When the job initially
exhausts its CM time slice, this lower boundary is the value of il.
Subsequently, when the job exhausts its CM time slice, this lower
boundary is the value of lp (refer to the QUEUE command IL and LP
parameters), cm ranges from 0 to 7777s.

CPcp

Control point slice priority. This parameter specifies the value of the
scheduling priroity which will be set after a job has been at a control
point for ct seconds. The priority specified must be greater than or equal
to the lower bound and less than or equal to the upper bound execution
queue scheduling priorities specified by the CB parameter
(lp ^ cp ^ up). Refer to the QUEUE command LP and UP parameters.

3-152 NOS Version 2 Analysis Handbook

Revision M

SERVICE

/ms
Parameter Description
CScs Cumulative size in PRUs allowed for all indirect access permanent files.
cs indicates a limit value for the cumulative size.
c s L i m i t Va l u e
0

Unlimited

1000s

5000s

500008

1000008

200000s

4000008

Unlimited

CTct Control point time slice in seconds. This parameter specifies the
maximum amount of time that a job of the specified priority can remain
at a control point before its priority is changed to the control point slice
priority (cp). ct ranges from 1 to 7777s.
0ps

DSds Size in PRUs allowed for individual direct access permanent files, ds
indicates the limit value for the size of the files.
ds

Limit Value

Unlimited

10008

50008

50000s

1000008

2000008

4000008

Unlimited

DTsc Service class to which a detached job is assigned if the job is detached.
The default value for sc is DI (detached interactive).
ECec Maximum user-accessible extended memory field length in words divided
by UEBS for any job of the specified service class. This parameter
performs the same function for extended memory field length that the
FL parameter does for central memory field length, ec ranges from 0 to
37778.

19. Refer to Extended Memory Overview earlier in this section to determine the value of UEBS.

Revision

Deadstart

Decks

3-153

SERVICE

Parameter Description
EMem

Maximum extended memory length in words divided by UEBS for all
jobs of the specified service class. This parameter performs the same
function for extended memory field length that the AM parameter does
for central memory field length, em ranges from 0 to 37778.

FCfc

Number of permanent files allowed, fc indicates a limit value that is the
maximum number of permanent files allowed.
fc

Limit Value
Unlimited
108
408

1008

2008

5
6
7
FLfl

10008TBL
40008
Unlimited

Maximum field length divided by 1008 for any job of the specified
service class. If more memory is requested, the job is aborted. You
typically use this parameter to limit the memory requirement for jobs of
a specific service class during certain hours of the day. For example,
you may use the FL parameter to specify a maximum field length for
all batch service class jobs between the hours of 2 p.m. and 4 p.m. fl
ranges from 0 to 7777s.

3-154 NOS Version 2 Analysis Handbook

Revision M

SERVICE

Parameter Description
FSfs

Size in PRUs allowed for individual indirect access permanent files, fs
indicates a limit value for the size of the files.
fs

Limit Value
Unlimited
10s
30s
1008
3008
1000s
2000s
Unlimited

NJnj

Maximum number of jobs. For each service, this parameter specifies the
number of jobs that can be executing in the system, nj ranges from 0 to
7777s.

SDsd

CPU job switch delay in milliseconds, sd ranges from 0 to 7777s.

TDtd

Suspension time-out delay. A suspended job will not be timed out for
td*108 seconds. The maximum delay is approximately 9 hours, td ranges
from 0 to 7777s.

TPtp

Terminal job priority assigned to a terminal job that is rolled out
waiting for terminal input, tp ranges from 0 to 7777s, but must be in
the range of values for the execution queue parameters lp and up (refer
to the QUEUE command LP and UP parameters).

Revision M

Deadstart Decks 3-155

SPINDOWN

SPINDOWN
Formats:
ENABLE,SPINDOWN.

DISABLE,SPINDOWN.

Default:
Enabled.
Significance:
These entries enable or disable the spindown of 834, 836, 887, and 9853 disk
units. When spindown is enabled, entering a CHECK POINT SYSTEM command
will cause all 834, 836, 887, and 9853 disk units that are on and not globally
unloaded to automatically spin down. When spindown is disabled, entering a
CHECK POINT SYSTEM command will not spin down the 834, 836, 887, and
9853 disk units. System checkpoints that are initiated by mainframe errors do not
affect the state of these disk units.
SRST
Format:
SRST=n.

Default:
0
Significance:
This entry specifies the secondary rollout sector threshold. Any rollout file smaller
than n sectors (0 ^ n ^ 7777s) is considered a secondary rollout file for the
purpose of equipment selection.
NOTE

•■•"**%

The size of the rollout file for any job must be at least seven sectors larger than
the combined size in sectors of the job's central memory and extended memory
field lengths.

3-156

NOS

Version

Analysis

Handbook

Revision

SYSTEM DEBUG

SYSTEM DEBUG
Formats:
ENABLE,SYSTEM DEBUG.
DISABLE,SYSTEM DEBUG.

Default:

Disabled.
Significance:
These entries enable or disable the system debug mode of operation. When the
system is in system debug mode, it is less tolerant of system errors; that is, it is
more likely to hang upon experiencing errors. When the system is not in system
debug mode, it rates system errors as critical or noncritical. For critical errors,
For noncritical
the system
logs them
in the binary
maintenance
(BML)
rthe system partially
or totallyerrors,
interrupts
system
operation
to tend
to the log
errors.
and inasmuch as possible allows system operation to proceed. You can initiate the
system debug mode with the DSD ENABLE command or the corresponding
IPRDECK entry.
There is another system state called debug mode, which is conceptually different
from that of system debug mode. Debug mode is the state of the system where a
user with system origin privileges can make modifications to the running system.
You can initiate this mode of operation with the DSD command DEBUG. The left
screen header of the system console indicates whether the system is in debug
mode or not.

Revision

Deadstart

Decks

3-157

TAPE PF STAGING

TAPE PF STAGING
Formats:
ENABLE,TAPE PF STAGING.
DISABLE.TAPE PF STAGING.

Default:
Disabled.
Significance:
These entries specify whether permanent files that reside on tape alternate
storage are staged to disk. If disabled, jobs that attempt to access tape alternate
storage resident files are aborted.
UNLOCK
Format:
UNLOCK.

Default:
Unlocked.
Significance:
This entry specifies the system console is unlocked. All DSD commands can be
entered when the console is unlocked. The console is usually locked when the
system is being used in a production environment. Refer to LOCK earlier in this
section.
USER EXTENDED MEMORY
Formats:
ENABLE,USER

EXTENDED

M E M O R Y.

DISABLE,USER EXTENDED MEMORY.
Default:
Disabled.

Significance:
These entries enable or disable scheduling of jobs that access user extended
memory.

3-158

NOS

Version

Analysis

Handbook

Revision

LIBDECK

LIBDECK
LIBDECK is a SYSEDIT directive record on the deadstart file. SYSEDIT reads
LIBDECK during the system load. LIBDECK specifies program residence, field length,
record type, and parameter format.
Up to 64 LIBDECK records can be placed on the deadstart file. LIBDECKs are
named LIBDnn, where nn is 00 to 77s. A specific record can be selected with a
LIB = n entry in CMRDECK. The multiple deadstart deck capability enables the use
of a single deadstart file on virtually any system configuration.
You can list all LIBDECKs on the deadstart file by accessing the system file
SYSTEM with a COMMON command, then using the T parameter on the CATALOG
command. Refer to the NOS Version 2 Reference Set, Volume 3 for more information
concerning these commands.

/P*\

The following list provides brief descriptions of SYSEDIT directives acceptable in
LIBDECK. Complete descriptions of all SYSEDIT directives are in section 19,
SYSEDIT. A list of valid record types follows the directives.
Directive Format

Significance

*AD,nn,tyi/reci,ty2/rec2,...,tyn/recn

Specifies the alternate device to be
used in addition to the system
device(s) for storing ABS, OVL, PP,
and REL type records, nn is either
the EST ordinal or the equipment
type, tyi is the record type, and reci
is the record name.

*CM,tyi/reci,ty2/rec2,...,tyn/recn

Defines record reci of type tyi as
being central memory resident; valid
only for record types ABS, OVL, or
PP. Like any other job in NOS,
SYSEDIT has a field length
restriction of 3760008 central
memory words. You cannot use more
than approximately 326000s central
memory words (3760008-500008 words
for SYSEDIT's program FL) when
defining records to be central
memory resident.

*FL,tyi/reci-fli,ty2/rec2-fl2,...,
tyn/recn-fln

Record reci of type tyi is loaded with
a field length specified by fli (fli is
field length divided by 100s).

*MS,tyi/reci ,ty2/rec2,... ,tyn/recn

Defines record reci of type tyi as
being mass storage resident. This is
the default residence for routines
with no storage area specified in
LIBDECK.

Revision M

Deadstart Decks 3-159

LIBDECK

Directive

Format

S i g n i fi c a n c e

♦PROC,reci,rec2,...,recn Defines record reci of type PROC as a
procedure file.
* S C , t y i / r e c i , t y 2 / r e c 2 , . . . , D e fi n e s r e c o r d r e c i o f t y p e t y i a s
tyn/recn
product
set
format
commands.
The
command parameters are processed in
product set format (refer to the NOS
Version 2 Reference Set, Volume 3).
*/

comments

D e fi n e s

comment

lines.

The following record types may be specified in SYSEDIT directives. Some directives do
not allow all types.
Type (tyi) Description
ABS Multiple entry point overlay.
CAP Fast dynamic load capsule.
OPL Modify old program library deck.
OPLC Modify old program library common deck.
OPLD Modify old program library directory.
OVL Central processor overlay.
PP

12-bit

peripheral

processor

program.

PPL 16-bit peripheral processor program (CYBER 180 models only).
PPU First-level peripheral processor (FLPP) program (model 176 only).
PROC Procedure.
REL Relocatable central processor program.
TEXT Unrecognizable as one of the other types.
ULIB User library program.

3-160

NOS

Version

Analysis

Handbook

Revision

)

DIS

Operations

DIS

Job

D a y fi l e

Display

(A)

4.3

DIS

Job

Status

Display

(B)

4.4

DIS
DIS

Memory

Displays

Exchange

DIS

Directory

Display

Selection
Keyboard

Memory
PP

(X)
(Z)

Operation

Display
DIS

(C,

Package

Console

f*»

Entry
Call

4-6
4.8
4.9
4-10

Commands
Entries

4.13
4-14

Commands
Commands

4-18
,

4-20

*■)■

S
"

..*%

DIS Operations
DIS displays information about a single job. Under DIS, the X display shows the
exchange package area for the job. Central memory addresses relative to the job's
reference address are used for the data and program displays.
Initiate DIS at a control point to monitor the progress of a job by using any of the
following methods:
•

You can call DIS by entering X.DIS,fl (fl=field length desired) or X.DIS (field
length of 600008 assumed by default). This brings DIS to an empty control point
to initiate utility programs.
A job can execute a command in the form DIS (the job must be system origin or
have system origin privileges).
You can call DIS to an existing job by entering the command:
DIS,jsn.

Parameter Description
jsn Job sequence name to which you want DIS assigned.
On either a secured or unsecured system, before you can call DIS to an existing job,
the console must be unlocked (refer to the DSD UNLOCK command in section 5). For
a secured system, the system must be set to security unlock status by the security
administrator.
You can toggle between DSD and DIS. DIS permanently returns control to DSD when
you enter DROP.; the job is not dropped unless no commands remain.
When DIS is called to a control point, automatic command processing stops and the A
and B displays for DIS appear on the left and right display screens, respectively.
Keyboard entry is necessary to begin processing subsequent commands. Unless
automatic command processing is reenabled,* the job is stopped after each command
is processed. That is, only one command can be processed at a time. Under DIS, the
#^ B display shows only the condition of the job to which it is assigned, including
^ upcoming commands. When the job is not using the central processor, a copy of its
exchange package is displayed on the X display. Displays available under DIS are
selected in the same manner as DSD displays. Refer to Console Operation later in
this section for information concerning display selection commands and to DIS
Keyboard Entries for information about other DIS commands.

1. You can initiate automatic command processing by entering either a period (.) or the RCS command (refer
to Console Operation and to DIS Keyboard Entries later in this section).

Revision

DIS

Operations

4-1

DIS Operations

The displays available under DIS are:
Display
I d e n t i fi e r D e s c r i p t i o n
A Job dayfile. Messages and files (local FNT entries) attached to the job.
B Job status. Individual job status, equipment assigned, current messages,
and command buffer.
C,D Central memory. Contents of central memory words (selectable 8-word
groups) in five columns of four octal digits with display code
equivalents (same as the DSD C and D displays).
F Central memory. Contents of central memory words (selectable 8-word
groups) in four columns of five octal digits with display code
equivalents.
G Central memory. Contents of central memory words (selectable 8-word
groups) in four columns of five octal digits with COMPASS instruction "*^
mnemoric equivalents.
H File status. All files assigned to the job as well as equipment assigned
to files.
M Extended memory. Contents of 60-bit words of extended memory
(selectable 8-word groups) in five columns of four octal digits with
display code equivalents (same as the DSD M display).
N B l a n k s c r e e n . Yo u m a y w i s h t o s e l e c t t h e N d i s p l a y o r o n e s c r e e n t o / 0 m \
reduce the screen filter on the other screen.
T,U Text display. Displays text from central memory in coded lines (up to
60 characters per line). The display terminates after 256 words have
been displayed.
V Central memory buffer. Displays directly from central memory. The
display terminates after 512 words have been displayed.
X Exchange package. Breakpoint address and the exchange package. /-"*\
Y Monitor functions. Displays mnemonics and the values of all monitor
functions (same as the DSD Y display).
Z D i r e c t o r y. D I S d i s p l a y s a v a i l a b l e .
NOTE
Although all displays listed may appear on the left screen, only the B,
C, D, and N displays may appear on the right screen. If you attempt to
bring any other display to the right screen, the message INCORRECT
COMMAND is issued to the job dayfile and is displayed in the message
buffer of the B display.

4-2

NOS

Version

Analysis

Handbook

Revision

DIS Job Dayfile Display (A)

DIS Job Dayfile Display (A)
Figure 4-1 shows the DIS job dayfile display (A). The figure shows the job dayfile
messages for the control point to which DIS is currently assigned and as many files
attached to that control point as will fit in the display. All files attached to the job can
be observed by using the file status display (H).

DIS A. XB DAYFILE.

D a y fi l e
sessages

09.46.34.RFL(060000)
09.46.34.DIS.
09.47.31.USER.ABC1234,.
09.47.31.ABSC. S.
09.48.43.PACKNAM,721C.R-DL.
09.49.39.NOS.
09.50.06. 6ET.N0S/PN«PACKC.R"DJ.UN«KRONM0D.
09.50.06. DEVICE UNAVAILABLE.
09.50.29. EXIT.
09.50.41. 6ET.NOS/PN-PACKV2.R»DJ.UN-KRCNM0D.
09.50.41. DEVICE UNAVAILABLE.
09.55.21.COMMON.SYSTEM.
F N T N A M E T Y P E E S T T R A C K F S S TAT U S
0
5
10
11

INPUTIN»
7
4004
ND
5
SYSTEM
Ll»
6
4010
1
ZZZZZCO LI> 7 4213 ND 5
ZZZZZC2 LO 6 5652 ND 307

LEVEL
LVLO
LVLO
LVLO
LVLO

Files (local fnt
entries) attacned
to the joo

Figure 4-1. DIS Job Dayfile Display (A)
The level field, shown in the figure, is displayed only on a secured system.

yms

Revision M

DIS Operations 4-3

DIS Job Status Display (B)
Aa!S^S.

DIS Job Status Display (B)
The DIS B display shows the status of a specific job executing at a control point. It
also shows: any equipment assigned exclusively to the job by EST ordinal, message 1
and message 2 from the control point area, and the current command buffer, allowing
you to anticipate future job requirements.
Figure 4-2 shows the DIS job status display (B).
DIS B. JOB STATUS.

JSN

EJTO
=5
P
SRUA
=1
RA
UI
=
2755
SRUL
=
777777
FL
F M = M L S T E S T C S » B AT C H R A E
PN
=
721C
CONN
=0
FLE
L E V E L = LV L O C PA
CPU = X
EST

AAAC

}

Equipment

MS1 = DEVICE UNAVAILABLE.
MS2 =

=
»
=
=
=
=

2046
1741

26
160

Job status

600

assigned

Current messages

NOS.PACKV2.
RETURN,NOS.
REVERT,NOLIST.
EXIT.
REVERT,ABORT.PACKC OR PACKV2 NOT FOUND.
REVERT,NOLIST.
EXIT.
REVERT.CCL
EXIT.CCL
REVERT,ABORT.CCL

Command b u f f e r

Figure 4-2. DIS Job Status Display (B)

4-4 NOS Version 2 Analysis Handbook

Revision M

DIS Job Status Display (B)

A^S.

The job status portion of the display shows three columns of information. Each item
has the form item=value. The items are described next in the order that they appear
on the display.
Item Description
JSN Job sequence name of the DIS job.
UI User index.
FM Current family name.
PN Current pack name.
CPU CPU status.
EJTO Executing job table ordinal.
SRUA System resource units accumulator.
SRUL Account block limit for system resource units.
CS Connection status.
CONN Connection number (interactive jobs only).
LEVEL Job access level (secured systems only).
P P register address from exchange package.

/^eJm^v

RA Central memory reference address.
FL Central memory field length.
RAE Extended memory reference address.
FLE Extended memory field length.
CPA Control point area address.

Revision M

DIS Operations 4-5

DIS Memory Displays (C, D, F, G)

DIS Memory Displays (C, D, F, G)
Figure 4-3 shows the DIS data storage display (F). The contents of each central
memory word is displayed in columns of five octal digits along with the display code
equivalent. Only the memory locations currently assigned to the job can be displayed.
The message ****SECURED AREA**** is displayed for all other locations.
The DIS C and D displays have the same format as the DSD C display, except that
the DIS memory displays may show a managed table bias word preceding the groups
of central memory words.

DIS F. CENTRAL MEMORY.

00000060
00000061
00000062
00000063
00000064
00000065
00000066
00000067

00000 00000
ooooo 00000
00000 00000
OOOOO OOOOO
03171 51517
40000 00000
40000 00000
40000 OOOOO

OOOOO
OOOOO
OOOOO
OOOOO
16000
00010
00020
OOOOO

OOOOO
00000
OOOOO
00000
00001
00507
00131
OOOOO

00000070
00000071
00000072
00000073
00000074
00000075
00000076
00000077

03171
24051
00000
00000
00000
00000
00000
OOOOO

16562
00000
OOOOO
OOOOO
OOOOO
OOOOO
00000
OOOOO

33123
00000
OOOOO
00000
OOOOO
OOOOO
00000
OOOOO

51517
55700
00000
00000
00000
00000
OOOOO
00000

COMMON A
5 A EG
5 B AY

COMMON,SYS
TEM.

Figure 4-3. DIS Data Storage Display (F)

4-6 NOS Version 2 Analysis Handbook

Revision M

DIS Memory Displays (C, D, F, G)

Figure 4-4 shows the DIS program storage display (G). The G display shows the
contents of central memory and the COMPASS mnemonic translation.

OIS G. CENTRAL E8EMORY.

OOOOOOOO

00000001
00000002
00000003
00000004
00000005
00000006
00000007
00000010
00000011
00000012
000000.13
00000014
00000015
00000016
00000017

Address

00000 00000 00000 00000
05160 42000 00000 00000
23312 32405 15000 00001
00000 00000 00000 00000
00000 00000 00000 00000
00000 00000 00000 00000
00000 00000 00000 00000
00000 00000 00000 00000

PS
NE BB
AX XB
PS
PS
PS
PS
PS

ooooo
ooooo
ooooo
ooooo
ooooo
ooooo
ooooo ooooo
ooooo ooooo

PS
PS
PS
PS
PS
PS
PS
PS

00000
00000
00000
00000
00000
00000

ooooo
ooooo
ooooo
ooooo
ooooo
ooooo
ooooo
ooooo

Memory
contents

ooooo
ooooo
ooooo
ooooo
ooooo
00Q00

ooooo
ooooo

DXX+X

PS
PS
BXX°-X PS
PS
PS
PS
PS
PS
PS
PS
PS
PS
PS
PS
PS
PS

COMPASS aneaontc
translation

Figure 4-4. DIS Program Storage Display (G)

Revision M

DIS Operations 4-7

DIS Exchange Package Display (X)

DIS Exchange Package Display (X)
The DIS X display shows the breakpoint address (BKP=addr) if a breakpoint was set
at address addr. The breakpoint address is followed by the job's exchange package.
Figure 4-5 shows the DIS exchange package display (X).
DIS X.

BKP

EXCHANGE PACKAGE.
I00.

P =
452
RA
174100
FL
600
E
M = 74070000
RAE
FLE
M
A
600
EEA
X
O
X1
X2
X3
X4
X5
X6
X7

= 7777 7777
= oooo 0000
= oooo 0000
= oooo 0000
= oooo 0000
= 2331 2324
= 0516 0420
= 0000 0000

AO =
A1 =
A2 =
A3 =
A4 =
A5 =
A6 =
A7 =
7777
0000
0000
0000

600

375

0000
0000
0375
0000
oooo oooo 0003
0515 0000 0001
oooo oooo 0000
oooo oooo 0000

BO =
B1 =
B2 » 777776
B3 B4 =
B5 =
B6 =
B7 =

7700
0000
0000
0000

SYSTEM A
ENDP

+ AND - WILL SET *BKP* TO (P) +/- 1.

Figure 4-5. DIS Exchange Package Display (X)

4-8 NOS Version 2 Analysis Handbook

Revision M

DIS Directory Display (Z)

DIS Directory Display (Z)
Figure 4-6 shows the DIS directory display (Z). The Z display lists all displays
available under DIS control. If the letter entered to select the left screen display is not
a valid display identifier, the Z display is selected automatically.
DIS Z. DIRECTORY. LEFT SCREEN ONLY DISPLAY
A JOB DAYFILE.
F CENTRAL MEMORY. FOUR GROUPS OF FIVE
G CENTRAL MEMORY. FOUR GROUPS OF FIVE
H FILE STATUS.
M EXTENDED MEMORY.
T TEXT DISPLAY.
U TEXT DISPLAY.
V CM BUFFER.
X EXCHANGE PACKAGE.
Y MONITOR FUNCTIONS
Z DIRECTORY.

LEFT AND RIGHT SCREEN DISPLAYS

B
C
D
N

JOB STATUS.
CENTRAL MEMORY.
CENTRAL MEMORY.
BLANK SCREEN.

FIVE GROUPS OF FOUR
FIVE GROUPS OF FOUR

Figure 4-6. DIS Directory Display (Z)

0ms
Revision M

DIS Operations 4-9

Console Operation

Console Operation
Unlike DSD, DIS is not interpretive. You must complete every entry and signal DIS to
act upon the message by pressing CR or NEXT. The following rules apply to all DIS
commands.
• For input, spaces in an octal field are ignored but can be inserted for readability.
• For output, all octal fields are right-justified with leading zero fill; excess octal
digits are ignored.
In addition to the command entries, the following keys have special meaning to DIS
when entered as the first character. The corresponding special keys for the CC545,
CC598B, and CC634B console types are listed along with a description of the use of
each key.
CC545

CC598B

CC634B Description
X ^ X

F15

If DSD has relinquished the main
display console to DIS, this key acts as
a quick hold, and DIS drops the display
channel so that DSD can use it.

Up arrow, +, +
or grey +

Pages the left screen forward for the A,
C, D, F, G, H, M, T, and U displays.
Increments the breakpoint address for
the X display.

Down arrow,
-, or grey -

Pages the left screen backward for the
C, D, F, G, M, T, and U displays.
Decrements the breakpoint address for
the X display. Resets the A and H
displays to the beginning.

PgUp or ( (

Pages the right screen forward for the C
and D displays.

PgDn or ) )

Pages the right screen backward for the
C and D displays.

Advances the left screen memory display
address by the value in the lower 18
bits of the first word displayed
(applicable only to memory displays C,
D, F, G, and M).

Sets auto mode (initiates automatic
command processing). This key performs
the same function as the RCS command
described under DIS Keyboard Entries
later in this section.

4-10 NOS Version 2 Analysis Handbook

Revision M

/<^lsN.

Console Operation

CC545

CC598B

CC634B Description

Advances the pointer indicating the first
address of managed tables for the left
screen (applicable only to memory displays
C, D, F, and G).
Decrements the pointer indicating the first
address of managed tables for the left
screen (applicable only to memory displays
C, D, F, and G).

Right blank
(display key)

Tab

Advances the left screen display sequence
established by the SET,screen. command
(refer to Display Selection Commands later
in this section).

CR (carriage
return)

Enter/Return NEXT

Sets the repeat entry flag; the message
REPEAT ENTRY is displayed on the error
message line of the left screen. The
subsequent command entry is processed
but is not erased after completion. That
command is processed each time this key
is pressed. To clear the repeat entry mode,
press the left blank (erase) key on the
CC545 or the |< key on the CC634B.

The following keys are interpreted as control characters by DIS.
CC545

CC598B

CC634B Description

Left blank
(erase)

Esc

|< or Clears current DIS keyboard entry and
ERASE any resultant error message; auto mode
(automatic command processing) is also
cleared.

BKSP
(backspace)

Back Space <

Deletes last character displayed and
clears error message (if one exists).

CR (carriage
return)

Enter/Return NEXT

Initiates processing of an entered
command.

The following keyboard messages may appear above your entry
Message

Description

AUTO MODE.

The command buffer is read automatically. Automatic
command processing can be selected by the RCS command
or by entering a period.

COMMAND BUFFER
FULL.

The ELS command has been entered and there is
insufficient room in the command buffer to add the
characters requested.

COMMAND TOO
LONG.

The command you entered is too long.

yms
Revision M

DIS Operations 4-11

Console Operation

Message

Description

COMMANDS ON
FILE.

The ELS command has been entered and commands are
currently located in a file instead of in a command buffer. It
is not possible to add a command to the file.

DIRECT CPU INPUT.

The N command has been entered and all data entered from
the keyboard is being passed directly to central memory.

DISK BUSY.

DIS is waiting for an overlay to be loaded from a mass
storage device.

EXTENDED MEMORY
NOT AVAILABLE.

You entered the ENFLE command, but user extended
memory is not defined.

INCORRECT ENTRY. The command cannot be processed.
INCORRECT FL
REQUEST.

You entered an ENFL command to set the field length. The
requested field length must be greater than 100008 and less
than 3777008 including negative field length.

INCORRECT
PRIORITY.

The priority you entered using the ENPR command is not
correct. CPU priority must be greater than 1 and less than
718.

INSUFFICIENT FIELD
LENGTH.

Your field length is not long enough to support either
extended memory or 026.

JOB ACTIVE.

The previous request has not completed. The command must
be reentered when the job is not active.

OUT OF RANGE.

The memory entry address is greater than the field length.

PP BUSY.

DIS is waiting for a PP to be assigned in order to process a
keyboard entry.

REPEAT ENTRY.

The command in the command buffer is repeated each time
you press CR, Enter/Return, or NEXT. This can be cleared
by pressing the left blank, Esc, or |< key.

REQUEST EXCEEDS
MAXIMUM FLE.

You requested more extended memory than your system can
support.

STORAGE NOT
AVAILABLE.

The amount of central memory requested by the ENFL
command or required by the 026 file editor is not available.

WAITING FOR
EXTENDED
MEMORY.

DIS is waiting for extended memory after you entered the
ENFLE command.

WAITING FOR
STORAGE.

DIS is waiting for central memory after you entered the
ENFL or 026 command.

4-12 NOS Version 2 Analysis Handbook

Revision M

Display Selection Commands

Display Selection Commands
Specify the displays you want shown on the console's left and right screens by using
the following commands. Follow the entry with a carriage return.
Command

Description

xy.

Brings the x and y displays to the left and right screens, respectively.
Note that although all DIS displays may appear on the left console
screen, only the B, C, D, and N displays may appear on the right
screen. If you attempt to bring any other display to the right screen,
the entry is interpreted as a command and the message INCORRECT
ENTRY appears. In addition, if the letter entered to select the left
screen display (x) is not a valid display identifier, the Z display is
selected automatically.

xz,loc.

Brings specified memory display to the left screen, if not currently
selected, and provides display modifications as follows:
Parameter Description
Display identifier (C, D, F, G, or M).
Type of display modifications: 0-3, 4, 5, or 6
Use 0-3 to display specified group (8 words) starting at
location loc.
Use 4 to display all 8-word groups in contiguous
locations starting at location loc.
Use 5 to advance the display by loc locations.
Use 6 to decrement the display by loc locations.
loc

Location parameter (maximum of eight digits for central
memory address or seven digits for extended memory
address).

x.addr.

If x specifies one of the memory displays (C, D, F, G, or M), addr is
the address used to obtain the bias address for the managed table
display. (The bias address is the lower 18 bits of the word at addr.)

SET.xxxx.

Sets the left screen display sequence; xxxx consists of one to four
display identifiers. Pressing the right blank key on the CC545, the
Tab key on the CC598B, or the —> key on the CC634B after this
command is entered causes the first display to appear on the left
console screen. Pressing the key again selects the second display. The
next display in the specified sequence appears on the left screen each
time the key is pressed, for example, SET,ACFD.

Revision M

DIS Operations 4-13

DIS Keyboard Entries

DIS Keyboard Entries
You can enter the following commands while in DIS.
If a job is currently active (CPU active, waiting, on recall, or PP active), many
commands are not accepted and the message JOB ACTIVE is displayed.
Command

Description

BEGIN ,pname,pfile.

Sets auto mode and calls the procedure pname that is on file
pfile.

BKP,addr.

Breakpoint to address addr in the program. Central processor
execution begins at the current value of P and stops when
P=addr, and DIS is the only PP active at the control point.

BKPA,addr.

Breakpoint to address addr in the program with assigned
PPs. Central processor execution begins at the current value
of P and stops when P = addr. PPs attached to the control
point can still be active. DIS clears addr to stop the program
at that point. The breakpoint may be cleared by setting the
breakpoint address to a new value.

CEF.

Clears the skip-to-exit flag. This allows command processing
to continue with the next command instead of skipping to
the EXIT command after an error.

DCP.

Drops the central processor and displays the exchange
package area on the X display.

DDF.

Calls the display disk file (DDF) utility to the control point.

DIS.

Reloads the main DIS overlay.

DROP.

Drops DIS, but normal processing of the job continues (it
does not drop the job until all commands are processed).

ELS.commandstring.

Allows entry of the commandstring command after the last
command in the command buffer, if there is space. This
command is valid only when auto mode is not set.

ENAi,addr.

Sets register Ai = addr in the exchange package area.

ENBi,addr.

Sets register Bi=addr in the exchange package area.

ENEM,n.

Sets CPU program exit mode to n (0 ^ n ^ 7).

ENFL,fl.

Sets central memory field length FL=fl in the exchange
package area (0 ^ fl ^ 777777s). fl must be at least 100008
if user extended memory is assigned.

4-14 NOS Version 2 Analysis Handbook

Revision M

sfMS

DIS Keyboard Entries

Command

Description

ENFLE,fle.

Sets extended memory field length FLE to fleOOO in the
exchange package area (1 ^ fie ^ 7777s). If user extended
memory is assigned (fle = 0), central memory FL, set by the
ENFL command, must be greater than or equal to 10000s.

ENP,addr.

Sets P=addr (next instruction address).

ENPR,pr.

Sets CPU priority to pr (2 ^ pr ^ 70s).

ENPR,*.

Sets CPU priority to the minimum non-decrementing
value, 60s.

ENS.commandstring.

Allows entry of the commandstring command as the next
unprocessed command in the command buffer. The command
can then be processed using RNS, RSS, or DROP. Use of
ENS with CCL procedure files produces unexpected results.
This command is valid only when auto mode is not set.

ENTERVcommandl/
command2.

Allows entry of the commandl and command2 commands
from the keyboard and sets auto mode.

ENTL,timlmt.

Sets the job time limit to timlmt (77777s specifies no limit).

ENXi,cont.

Sets register Xi = cont in the exchange package area.

ENXi,Lcont.

Sets register Xi = cont, left-justified, in the exchange package
area.

ENXi,Dcharacters.

Sets register Xi to characters in display code.

ENXi,b,value.

Sets byte b of register Xi to value.

ERR.

Sets forced error flag (FSE), terminates program execution,
and clears auto mode if set.

GO.

Restarts a program that has paused.

HOLD.

DIS relinquishes the display console, but the job is held at
the present status. The console must be reassigned to
continue use of DIS.

M.characters.

Enters characters as a CPU program command. Data is
stored at RA + CCDR.

N.characters.

Sets direct CPU input mode. Characters entered from
keyboard are passed one character at a time, right-justified,
directly into central memory at RA + CCDR. Pressing the left
blank key on the CC545, the Esc key twice on the CC598B,
or the K key twice on the CC634B clears direct CPU
input mode.

Revision M

DIS Operations 4-15

DIS Keyboard Entries

Command

Description

OFFSWs.

Turns off sense switch s for the job (1 ^ s ^ 6).

ONSWs.

Sets sense switch s for the job (1 ^ s ^ 6).

026.

Calls the 026 file editor to a control point. Refer to the NOS
Version 2 Systems Programmer's Instant for a description of
the editing commands.

RCP.

Requests central processor. Depending on job priority,
execution begins at the next program address for a job
suspended by a DCP request.

RCS.

Sets auto mode, which initiates automatic command processing.
All succeeding commands are read from the command buffer
and processed automatically until an SCS command, an erase
function, or an error is encountered. A period (.) may also be
used to initiate automatic command processing.

RNS.

Reads and processes the next command in the DIS command
buffer.

ROLLOUT.

Allows the job to roll out. This command should be issued
when the message ROLLOUT REQUESTED appears (or the *
or F15 key may be used).

ROLLOUT,spr.

Places job in rollout status for spr job scheduler delay
intervals. The job is automatically rolled back in after this
period of time. If a number greater than 7778 is specified for
spr, 7778 is used.

RSS.

Reads the next command from the command buffer and stops
prior to CPU execution. This is used to initiate breakpointing
of a program.

RSS,commandstring.

Reads the commandstring command and stops prior to
execution. The action is similar to ENS followed by RSS
except that the command buffer is not cleared.

SCS.

Clears auto mode, which stops automatic command processing.

SULuserindex.

Allows access to a user index above AUIMX (377700s). Any
permanent file activity that is to be done on such user indices
must be done through system origin jobs. This command is not
accepted by a secured system.

T,addr.

Changes the T display to start at address addr.

4-16 NOS Version 2 Analysis Handbook

Revision M

DIS Keyboard Entries

Command

Description

U,addr.

Changes the U display to start at address addr.

UCC=c

Sets the uppercase character c. This command does not
terminate with a period.

V,addr.

Changes the V display to start at address addr.

X.commandstring.

Processes commandstring as the next command. Only the first
50 characters following X are used. This may be used to enter
a leading slant or a command that is the same as DIS
display.

* commandstring.

If an asterisk (*) followed by a blank and commandstring is
encountered during automatic command processing (auto
mode), commandstring is interpreted as a direct DIS display
selection command. For example, * C4,100. will set the left
screen display to the central memory C display at address
100. Using this feature, it is possible to set up procedure files
that use DIS to breakpoint a program to a desired stopping
point.

commandstring.

Processes commandstring as a command if it is not a
recognizable DIS command.
Calls the 026 file editor to a control point. Refer to the NOS
Version 2 Systems Programmer's Instant for a description of
the editing commands. (This command is the same as the
026 command.)

Revision M

DIS Operations 4-17

Memory Entry Commands

Memory Entry Commands
The following commands are used in conjunction with the C, D, F, G, and M memory
displays to change the contents of central memory and extended memory. Only
locations relative to the reference address (RA) of the job to which DIS is assigned can
be changed. When changing the contents of memory relative to a job, the negative field
length area of the job can be accessed by specifying a negative address. For example,
to change the content of RA-3, enter the address 777775s.
On a secured system no memory entry commands are allowed unless the security
unlock status is set. The memory display shows the message
••••SECURED AREA****

instead of the contents of the memory locations to prevent you from examining these
locations; you may not alter the contents of these locations.
Character values or numeric data can replace the current word contents. Either one
12-bit byte, one 15-bit parcel, one 30-bit parcel, or 60 bits can be changed. A single ""^
byte can be changed by inserting the byte number after the location to be changed;
bytes are numbered 0 through 4 from left to right. The address and contents are
assembled right-justified with leading zero fill. Leading zeros may be omitted in the
entry. Only words within the field length of the job may be changed.
CAUTION
Improper use of these commands may result in damage to the system or to user jobs.
Formats and descriptions of the memory entry commands follow. )
Command

Description

addr,cont. Changes the contents of memory location addr to
or cont. The second form of the command performs
addr+cont. essentially the same function but leaves the address at
addr + 1, allowing immediate entry for the next memory
location.
addr,b,cont. Changes the contents of byte b at memory location /^^
or addr (eight digits) to cont. Each location
addr+b,cont. consists of five 12-bit bytes, numbered 0 through 4 from left
to right. The contents are octal characters. The second form of
the command performs essentially the same function but
leaves the address at addr+1, allowing immediate entry for
the next memory location.

2. If the message REPEAT ENTRY is displayed above the entry line, the cont field is not cleared and may ^^S
be entered in successive memory locations as many times as desired by pressing CR or NEXT. The repeat
entry mode is enabled by pressing CR or NEXT before initial entry of the command. This is also applicable
to the b and n fields of the second, fifth, and seventh commands.

4-18

NOS

Version

Analysis

Handbook

Revision

Memory Entry Commands

igffrSi

Command

Description

addr,Dcont.
or
addr + Dcont.

Changes the contents of memory location addr (eight digits)
to display code characters cont (left-justified and
zero-filled). The second form of the command performs
essentially the same function but leaves the address at
addr+1, allowing immediate entry for the next memory
location.

addr,Lcont.
or
addr + Lcont.

Changes the contents of memory location addr (eight digits) to
left-justified cont. The second form of the command performs
essentially the same function but leaves the address at
addr + 1, allowing immediate entry for the next memory
location.

addr,In,cont.
or
addr + In,cont.

Changes the contents of instruction n (0 through 3 from
left to right) at memory location addr (eight digits) to
cont; cont may be a 15- or 30-bit instruction. However, one or
more bits must be set in the upper 15 bits of a 30-bit
instruction or the entry will be treated as a 15-bit instruction.
The second form of the command performs essentially the
same function but leaves the address at addr + 1, allowing
immediate entry for the next memory location.3

Eaddr ,cont.
or
Eaddr + cont.

Changes the contents of extended memory location addr to
cont. The second form of the command performs essentially
the same function but leaves the address at addr + 1, allowing
immediate entry for the next extended memory location.

Eaddr,b,cont.
or
Eaddr+ b,cont.

Changes the contents of byte b at extended memory location
addr to cont. Each location consists of five 12-bit bytes,
numbered 0 through 4 from left to right. The contents are
four octal characters. The second form of the command
performs essentially the same function but leaves the address
at addr + 1, allowing immediate entry for the next extended
memory location.

Eaddr,Dcont.
or
Eaddr + Dcont.

Changes the contents of extended memory location addr to
display code characters cont (left-justified and
zero-filled). The second form of the command performs
essentially the same function but leaves the address at
addr + 1, allowing immediate entry for the next extended
memory location.

3. If the message REPEAT ENTRY is displayed above the entry line, the cont field is not cleared and may
be entered in successive memory locations as many times as desired by pressing CR or NEXT. The repeat
entry mode is enabled by pressing CR or NEXT before initial entry of the command. This is also applicable
to the b and n fields of the second, fifth, and seventh commands.

Revision M

DIS Operations 4-19

PP Call Commands

PP Call Commands
Any PP program having a name that begins with a letter may be initiated by DIS.
However, before entering any of these commands, it is necessary to have a working
knowledge of the PP program to be called. This ensures correct use of the specified
program.
CAUTION
Improper use of these commands may result in damage to the system or to user jobs.
In table 4-1, prg denotes the name of the PP program and n is the control point
number.
Table 4-1. PP Call Formats
Command Description

Format of PP
Call Initiated

prg. Calls PP program prg to the control
point.

18/3Lprg,6/n,36/0

prg,pl.* Calls PP program prg to the control
point; pl is an octal parameter required
by prg.

18/3Lprg,6/n,18/0,18/pl

prg,pl,p2. Calls PP program prg to the control
point; pl and p2 are octal parameters
required by prg.

18/3Lprg,6/n,18/pl,18/p2

/^®Sk

4-20 NOS Version 2 Analysis Handbook

Revision M

0ms

DSD
Display

Commands
Selection

D a y fi l e
Queued

File

Utility

5.3
Commands

5.4
5.4
5-4
5-8
5-9
5-10

Peripheral

5-24

System
Secured

Equipment

Control

System

Channel

Control
Flag

Commands
Commands
Commands

5-50
5-56
5-70
5-72
5-74

Commands

5-75

Breakpoint
Package
Commands
,
PP
Breakpoint
Commands
V
Display
PP
Breakpoint
Precautions
CPUMTR
Breakpoint
Commands
CPUMTR
Breakpoint
Display
(C
Display)
CPUMTR
Breakpoint
Precautions

5-75
5-75
5-77
5-79
5-80
5-81
5-83

Debugging

Memory

Commands
Control

Entry

Commands

Control

Memory

Extended

Commands

5.2

Job
Processing
Control
Commands
General
Job
Control
Commands
Interactive
Job
Control
Commands
Job
Communication
Commands
Job
Flow
Commands

Subsystem

r^
-

Commands

5-84

V^ J

DSD Commands
After the system has been deadstarted successfully, you can enter the DSD commands
necessary to provide optimum performance and reliability for users. The following
general categories of DSD commands are available for this purpose.
Category

Description

Display selection

Selects DSD displays.

Dayfile

Dumps the system, account, or error log
dayfile to a specified device.

Queued file utility

Provides control over selected queued files.

Job processing control

Provides added control over job scheduling and
processing.

Peripheral equipment control

Controls the peripheral equipment available to
the system.

Subsystem control

Schedules a subsystem to a control point or
terminates a current subsystem.

System control

Maintains system integrity in a normal
production environment or debugs a system
that is in an abnormal state.

Memory entry

Changes the contents of central memory and
extended memory.

Channel control

Controls activity on a specified data channel
in circumstances where abnormal hardware
and/or system operation is detected.

Extended memory flag register

Clears and sets bits in the extended memory
flag register.

Breakpoint package

Provides control over PP breakpoint processing
and CPUMTR breakpoint processing.

Debugging commands

Traps certain conditions and traces selected
pool PP to CPUMTR and MTR to CPUMTR
functions.

Although all DSD commands are generally available, many of them are seldom used in
a normal production environment. Many DSD commands are used only by the system
analyst for maintenance or debugging. These commands include all memory entry and
channel control commands as well as several commands in the other categories listed
on an unsecured system. Memory entry and several other commands are restricted on a
secured system (refer to the UNLOCK command later in this section).
When unusual problems arise, do not attempt corrective action unless you have
considerable experience relating to the current problem. Misguided attempts to correct
a system problem can often destroy information required to successfully analyze the
problem.

Revision M

DSD Commands 5-1

Display Selection Commands

To assist customer engineers and software analysts in tracking problems, the system
enters the first characters (up to 25) of the following commands into the error log ^^\
after each execution.
DOWN,param.
FORM,param.
IDLE,param.
INITIALIZE,param.
LOG,param.
OFF,param.
ON,param.
REDEFINE.param.
99.
Memory entry commands
Channel control commands
Any other commands that you specify at installation time
These commands are prefixed by the characters DS in the error log but otherwise
appear exactly as they are entered. This feature can be enabled and disabled using the "^)
99 command (refer to System Control Commands later in this section).
The manner in which the DSD commands are entered and the use of special keyboard
characters are described in the NOS Version 2 Operations Handbook. Command
formats are fixed field; that is, the fields in the command format must be specified as
shown. Embedded blanks are allowed in octal fields. Leading spaces in command
entries are not allowed.

Display

Selection

Commands

The system display program DSD generates system-oriented displays. You can select
any of the DSD displays with the following DSD command:
xy.
where x and y represent the letter designation (screen identifier) of the displays.
Display x appears on the left screen and display y appears on the right screen. If x
and y are identical, both screens display the same information, except for the B and ^^
P displays when using the CC598B or CC634B console. Refer to the NOS Version 2 '
Operations Handbook for details concerning the DSD display formats and keyboard
operating instructions. You can specify a sequence of DSD displays that you want
displayed on the left screen. To preselect the left screen display sequence, enter the
following DSD command:
SET,screens.

where screens represents a string of four letters (screen identifiers) designating any
four DSD displays. Usually you specify four different displays although DSD accepts
any four valid screen identifiers. Refer to the NOS Version 2 Operations Handbook for
DSD displays and keyboard operating instructions.

5-2

NOS

Version

Analysis

Handbook

Revision

Dayfile Commands

Dayfile Commands
The system saves messages in five types of dayfiles.
• Account dayfile
• Binary maintenance log
• Error log
• Job dayfile
• System dayfile
The account dayfile keeps a record of all resources charged to a job. This dayfile can
be used for customer billing and other accounting purposes. The binary maintenance
log records the information used in Control Data maintenance in binary format. The
error log records system error messages, such as disk errors. Job dayfiles keep entries
for individual jobs. The system dayfile keeps a history of all commands for all jobs
processed.
The following commands dump the account dayfile, system dayfile, or error log to a
systemrdefined mass storage device. The resultant mass storage file is put in the
output queue for printing. The system automatically prints the job dayfile at the end
of the job's output.
Command

Description

^ w n X . A F D . R e q u e s t s t h a t t h e a c c o u n t d a y fi l e b e d u m p e d t o a
system-defined mass storage device. The resultant mass
storage file is put in the output queue for printing.
X.DFD. Requests that the system dayfile be dumped to a
system-defined mass storage device. The resultant mass
storage file is put in the output queue for printing.
X.ELD. Requests that the error log be dumped to a system-defined
mass storage device. The resultant mass storage file is put
in the output queue for printing.
Refer to section 18, Queue/Dayfile Utilities, for more information on dayfile dumps.
The binary maintenance log is designed to be processed through an interpreter
program, and therefore is normally dumped to tape or disk.
Refer to the NOS Version 2 Operations Handbook for descriptions of dayfile displays.

Revision

DSD

Commands

5-3

Queued File Utility Commands

Queued File Utility Commands
The following commands are used to control queued input and output files.
Command Description
X.QREC Deactivates or activates selected queued files and purges selected
inactive queued files.
X.QMOVE Moves queued files from one mass storage device to another.
Refer to section 18, Queue/Dayfile Utilities, for more information on queued file utility
commands.

Job Processing Control Commands
Under normal circumstances, control over job processing is performed automatically by
the system. Although the following commands may not be used frequently, they provide ^_
an
added
measure
of
control
over
job
processing.
^

General Job Control Commands
Several of the commands described here change internal system parameters which
control job scheduling and processing. Give careful consideration to their use since job
flow and overall system performance can be affected. Refer to the individual command
descriptions for further information.
Command

Description

>*^\

CKPJsn. Checkpoints the job with job sequence name jsn. The
checkpoint information includes a copy of the job's field length,
the system information used for job control, and the name and
contents of all local files currently assigned to the control
point. It is the responsibility of the user's job to establish a
magnetic tape or mass storage permanent file to receive the
checkpoint information. Otherwise, checkpoint information is
automatically written to a local file named CCCCCCC and is
n o t a v a i l a b l e i f a r e s t a r t b e c o m e s n e c e s s a r y ( r e s t a r t i s ■^ s \
user-controlled and is accomplished using the RESTART
command). Refer to the NOS Version 2 Reference Set, Volume
3 for supplementary information concerning the
checkpoint/restart feature available to users.
NOTE
If the current job command has secure system memory (SSM)
status set, the job cannot be checkpointed. SSM status is set
for certain jobs to prevent dumping of the job's field length.
Subsystems cannot be checkpointed.

^3ss!\

5-4

NOS

Version

Analysis

Handbook

Revision

General Job Control Commands

Command

Description

DROP,jsn,qt,ujn.

Drops the job with job sequence name jsn from the queue qt
where it currently resides. If a jsn is not specified, a 1- to
7-character user job name ujn can be specified after the queue
type.
The console must be unlocked to use this form of the DROP
command. If no jsn or ujn is specified, all jobs in the specified
queue type are dropped. If the queue type is not specified, the
default is the executing queue.
The DROP command cannot be used to terminate a subsystem.
Also the DROP command will not terminate an interactive
user's session (this can be done only with a KILL command).
The queue type is one of the following:
qt Queue Type
ALL

All jobs and queued files.

All jobs in the executing queue (including the rolled
out jobs).

All jobs in the input queue.

All jobs in the plot queue.

All jobs in the print queue.

All jobs in the punch queue.

All jobs in the wait queue.

ENPR,jsn,pr.

Sets CPU priority to pr (2 ^ pr ^ 70s).

ENPRJsn,*.

Sets CPU priority to the minimum non-decrementing
value, 60s.

ENQP,jsn,pr.

Enters queue priority of pr for a queue type file with job
sequence name jsn. The value of pr can range from the
minimum to the maximum for the job's service class. If the
priority is zero, an input file is not scheduled back to a
control point automatically. The value specified overrides the
current queue priority for the file. The current queue priority
can either be increased or decreased using this command.

Revision M

DSD Commands 5-5

General Job Control Commands

Command

Description

KILLjsn.

Drops the job with job sequence name jsn from the executing
job table (EJT) without exit processing. If you want the job to
proceed with exit processing, use the DROP command. The
KILL command cannot be used to drop a subsystem.
KILL is the only command that immediately terminates an
interactive user's session. The DROP and OVERRIDE
commands only terminate the current job step and do not log
the user out of the system. There will be no recoverable job
after you issue the KILL command.
NOTE
Before initiating the command, ensure that the correct job
sequence name has been specified.
In some cases, a KILL command will be intercepted by a job's
reprieve processing. If the job does not terminate after
finishing its reprieve processing, issue another KILL command
to terminate the job.

OVERRIDEJsn.

Certain types of job processing are unaffected by the DROP,
KILL, or STOP commands. These include operations such as
setting permanent file device interlocks, interlocking
files/tracks, clearing VSN entries, and waiting for certain
types of tape/PP activity to end. The OVERRIDE command
terminates this type of processing and drops the job with job
sequence name jsn from the executing job table regardless of
queue priority. The OVERRIDE command will not terminate
an interactive user's session (this can be done only with a
KILL command). Unlock the console (refer to the UNLOCK
command later in this section) to enter this command. Use of
this command is recorded in the error log.
NOTE
Exercise extreme caution in using the OVERRIDE command.
Undesirable situations (such as interlocks being left set, VSN
entries remaining uncleared, or certain tape/PP activities left
outstanding) could occur that would cause potentially
damaging system activity. Never use this command during
normal operations.

5-6 NOS Version 2 Analysis Handbook

Revision M

General Job Control Commands

Command

Description

RERUNJsn.

Terminates the job with job sequence name jsn, then reruns
the job from the beginning. The job must be in rerun status
as set by the RERUN command or macro.

ROLLIN,jsn,L.

Allows the job defined by job sequence name jsn to be
scheduled to an available control point. L is optional; if
omitted, the job can be selected by the scheduler for rollout.

ROLLOUT,jsn,sd.

Removes the currently executing job with job sequence name
jsn and makes it a rolled out job. A subsystem cannot be
rolled out. sd is the number of scheduler intervals before the
job can be scheduled again. The acceptable range for sd is
between 0 and 777s. If sd is not present or is 0, the job is not
scheduled back to a control point automatically. That is, your
action is required to return the job to a control point. This
can be done by using the ROLLIN command.
The amount of time required for one job scheduler interval is
initially set in the IPRDECK but may be changed by using
the DELAY command (JS parameter) described later in this
section. Normally, it is a 1-second interval.

Revision M

DSD Commands 5-7

Interactive Job Control Commands
a&$S

Interactive Job Control Commands
The following commands apply only to interactive online jobs. The interactive facility
subsystem must be active at control point 1. Refer to the CDCNET Network Operations
Manual for information about sending messages to terminal users that are connected
through CDCNET.
Command

Description

DIAL,jsn,messagetext.

Sends message messagetext (48 characters maximum) to the
terminal currently assigned to the job with job sequence name
jsn. Examine the T display to determine the appropriate job
sequence name. The message is sent to the terminal
immediately except when output is being sent to the terminal.
In that case, the message follows the output data.

WARN,messagetext.

Sends message messagetext (48 characters maximum) to all
terminals currently logged into IAF. The message is received
at a terminal upon completion of the current command or at
the end of a job step. Each subsequent terminal that logs into
IAF also receives this message. This continues until either a
new message is entered or the message is cleared by using
the WARN command. In addition, the current message also
appears at the IAF Subsystem control point on the B,0
display.
When sent to an interactive terminal, the message
messagetext is always preceded by the statement
hh.mm.ss.

WARNING

specifying the time (hours.minutes.seconds) when you entered
the WARN command.
For example, if you enter
WARN,SYSTEM SHUTDOWN AT 1500.

the following information would be transmitted to all
interactive terminals.
hh.mm.ss.

WARNING

SYSTEM SHUTDOWN AT 1500.

This command is typically used to notify interactive users of
an interruption in service or system shutdown.
WARN.

Clears the message entered by the WARN,messagetext
command. Unless this command is entered, the existing
message (if any) continues to be transmitted to each new
terminal that logs into IAF.

5-8 NOS Version 2 Analysis Handbook

Revision M

Job Communication Commands

Job Communication Commands
The following job communication commands are used to communicate with a job
currently in the executing job table.
Command

Description

CFO,jsn,messagetext.

Sends a message messagetext (36 characters maximum) from
the console to the job with job sequence name jsn. Bit 14 of
the job's RA must be set before the CFO command is accepted.
The message is placed in locations RA + 70s through RA + 74s
of the program's field length.

COMMENTjsn,
messagetext

Enters comment messagetext (48 characters maximum) in the
dayfile for the job with job sequence name jsn.

GO, jsn.

Clears the pause bit of the job with job sequence name jsn. A
job may set the pause bit if an error is encountered or if an
operator response is required. If jsn is not specified,, the
command applies to the system control point.

OFFSW,jsn,si,S2,...,se.

Turns off one or more sense switch(es) si (1 ^ si ^ 6) of the
job with job sequence name jsn. Refer to Subsystem Control
Commands later in this section for definitions of the sense
switches that can be set for the BIO, IAF, MSE, and TAF
Subsystems.

ONSW,jsn,si,s2,...,S6.

Turns on sense switch(es) si (1 ^ si ^ 6) of the job with job
sequence name jsn. Refer to Subsystem Control Commands
later in this section for definitions of the sense switches that
can be set for the BIO, IAF, MSE, and TAF Subsystems.

PAUSEJsn.

Sets the pause bit of the job with job sequence name jsn. If
jsn is not specified, the command applies to the system control
point.

Revision M

DSD Commands 5-9

Job Flow Commands

Job Flow Commands
The following job flow commands affect scheduling and execution of jobs in the system. )
Improper use of these commands can drastically hamper job flow as well as system
performance. In certain cases, jobs may be lost.
The priority associated with each priority parameter in the following commands is
established by an entry in the IPRDECK for each service class. The value of each
priority parameter for each service class is listed on the system control display(s)
(refer to the NOS Version 2 Operations Handbook for more information on the S
display).
Command

Description

CLASS,ot,sci,sc2,.-.scn. Defines the authorized service class for each origin type.
Refer to the SCTD L display in section 9, L-Display
Utilities, for further information.
Parameter

Description

Ams

ot Origin type (must be batch, remote batch, or
interactive). This parameter is order
dependent. Types with brief descriptions
follow:
BC Batch.
RB Remote batch.
IA

Interactive.

"^%^

sci Authorizes service classes for the specified
origin type. Entering a service class that
already has validation clears validation for
that service class. Service classes with brief
descriptions (in parentheses) follow:
BC (Local batch).
CT

(Communication

task).

""^

DI (Detached interactive).
In [Installation class n (0 ^ n ^ 3)].
MA (Maintenance).
NS (Network supervisor).
RB (Remote batch).
SY (System).
TS (Interactive).
ALL (Sets all classes except SS and DS).
NUL

5-10

NOS

Version

Analysis

(Clears

Handbook

all

service

Revision

classes).

)

Job Flow Commands

0^S

Command

Description

CPTT=n

Changes the CPUPFM transfer threshold (CPTT) to the value
n (0 *s n ^ 77778 PRUs). The value of CPTT determines
whether an indirect access file transfer will be processed
entirely within the PP program PFM or whether the CPU
program CPUPFM will be called to perform the transfer. Since
CPUPFM can transfer large files faster than PFM, CPUPFM
will transfer files that exceed the threshold value.
The default value is 100s sectors, as defined in common deck
COMSPFM. Depending on the configuration, you may want to
adjust this value up or down. A site with buffered I/O devices,
for example, may find it advantageous to set a lower value.
To disable CPUPFM transfers altogether, enter CPTT=0. The
current value of CPTT is displayed on the W,M display.

DELAY,pi,p2,...,pn.

Alters current system delay parameters. Examine the W,M
display to determine the current delay parameter values.
Pi

Description

ARar

PP recall interval in milliseconds. This parameter
specifies the time interval after which a peripheral
processor unit (PP) in the PP recall queue will be
recalled, ar ranges from 1 to 7777s.

CIci

CPU job priority interval in milliseconds. This
parameter specifies the time interval after which
the priorities of jobs in the wait queue are
incremented, ci ranges from 0 to 7777s.

CRcr

CPU recall period in milliseconds. This parameter
specifies the amount of time a job remains in recall
(X status) when an RCL request is placed in
RA+1. cr ranges from 1 to 7777s.

JQjq

Exponent used to determine the input file
scheduling interval in seconds, jq ranges from 0 to i
148. The interval in seconds between scheduling of
input files is calculated as follows:

J0^!s\

interval = 2**jq
JSjs

Revision M

Job scheduler interval in seconds. This parameter
specifies the interval in which the job scheduler is \
called. The scheduler may also be called at other
times, js ranges from 1 to 7777s.

DSD Commands 5-11

Job Flow Commands

Command
| DELAY,pi,p2,...,pn.

Description
(Continued)
Pi

Description

MPmp Memory padding value expressed as 100s word
blocks, mp ranges from 0 to 777s. This
parameter specifies how much additional
(unassigned) memory should be allocated
between the end of the newly assigned job field
length and the beginning of the next job.
Increasing this value reduces the probability
that a job will be storage moved in response to
a request for more memory.
The value for each system delay parameter may be established
by using a DELAY command entry in the IPRDECK. If no
DELAY entry is present, default values are provided.
Figure 5-1 provides space to record the original values
(specified in the W,M display) in the event that any are
altered temporarily. For additional information concerning the
DELAY command, refer to section 3, Deadstart Decks.

DELAY

VALUES

AR
CI
CR
JQ
JS
MP

Figure 5-1. Record of Original Values in W,M Display (Delay Values)

5-12 NOS Version 2 Analysis Handbook

Revision M

Job Flow.Commands

Command

Description

PCLASS,sco,sci,...,sc7.

Selects the service class associated with each priority level
(pothrough P7) on the Job command. This parameter is order
dependent; a comma must appear for any parameters not
specified. The default for any parameters not specified is 0
(zero). Subsystem (SS) service class is not allowed with this •
command. Refer to the SCTD L display in section 9, L-Display
Utilities, for more information.
sci is a 2-character service class parameter. Entries are listed
and briefly described below.

Revision M

sci

Description

Local batch.

Communication task.

Detached interactive.

Installation class n (0 *s n ^ 3).

Maintenance.

Network supervisor.

Remote batch.

System.

Interactive.

DSD Commands 5-13

Job Flow Commands

Command

Description

QUEUE,sc,qt,qpi,
qp2„...,qpn.

Alters the queue priorities qpi associated with the input,
executing, and output queues qt for each service class sc.
Examine the L display SDSPLAY to determine the priority
values currently associated with each service class.
sc

Description

BC Local batch.
CT Communication task.
DI Detached interactive.
In Installation class n (0 ^ n =£ 3).
MA Maintenance.
N S N e t w o r k s u p e r v i s o r.
RB Remote batch.
SS Subsystem.
SY

System.

TS Interactive.
There are three job queue types.
qt

Description

Executing.

Input.

Output.

5-14 NOS Version 2 Analysis Handbook

Revision M

Job Flow Commands

Command
{'

QUEUE,sc,qt,qpi,
qp2„...,qpn.

Description
(Continued)
There are five priorities.
qpi

Description

ILil Priority a job receives when it initially exhausts I
its CM time slice (refer to the SERVICE
command CM parameter). Thereafter, whenever |
the CM time slice is exhausted, the job's
priority will be set to the value of lp. il ranges |
from 0 to 77778, but must be in the range of
values for lp and up. This parameter is valid
only for executing jobs (EX).
IPip Initial scheduling priority for an executing batch!
job or for an interactive job when a terminal
command is entered. Online interactive jobs withf
terminal I/O available are scheduled at tp
priority (refer to the SERVICE command TP
parameter), ip ranges from 0 to 7777s, but mustf
be in the range of values for lp and up.
LPlp Lowest priority. For an input or output queue
file, the priority assigned to a file or job
entering the designated queue. For an executing!
job, the priority assigned to a job which has
exceeded a non-initial CM slice. The IL value is I
used for the first CM slice, lp ranges from 0 to |
77778, but must be less than the value of up.
UPup Highest priority. For input and output queues,
this is the highest priority a file can reach in
that queue; aging stops when this priority is
reached. For the execution queue, this is the
priority assigned to a job when initially assigned;:
to a control point, up ranges from 0 to 7777s,
but must be greater than the value of lp.
WFwf Weighting factor wf for queue priority
calculation, wf must be a power of 2, from 1
to 40008. The smaller the weighting factor, the 1
faster the queue entry reaches its highest
priority.
The priority associated with each queue is established by
using QUEUE command entries in the IPRDECK for each
service class. These entries normally reflect the ideal queue
priorities for the job mix of the particular installation. The
values specified in the IPRDECK are considered critical to
optimum system performance and are not normally altered.
Figure 5-2 provides space to record the original values
specified in the L display SDSPLAY. For additional
information on the QUEUE command, refer to section 3,
Deadstart Decks.

Revision

DSD

Commands

5-15

Job Flow Commands

JOB

PRIORITIES FOR EACH QUEUE TYPE

SERVICE
CLASS

INPUT QUEUE

EXECUTIN6 QUEUE

OUTPUT QUEUE

U
F

SY
BC
RB
TS

yS^s.

DI
NS
SS
NA
CT
10
11
12
13

Figure 5-2. Record of Original Values in L Display SDSPLAY

>«C^v

5-16 NOS Version 2 Analysis Handbook

Revision M

Job Flow Commands
JP*\

Command

Description

SERVICE,sc,pi,p2,. ..,pn. Alters the service limits pi associated with each service
class sc.
sc

Description

Local batch.

Communication task.

Detached interactive.

Installation class n (0 ^ n ^ 3).

Maintenance.

Network supervisor.

Remote batch.

Subsystem.

System.

Interactive.

Description

AMam Maximum field length/100s for- all jobs of the
specified service class. This parameter is used
to partition central memory by limiting the
total field length available to each service class.
For example, if scheduling a job to a control
point would cause the AM value to be exceeded
for its service class, it may not be scheduled
until the required field length is available.
This means that a lower priority job from a
different service class may be scheduled first.
However, a job that would cause the AM value
for its service class to be exceeded can be
scheduled to a control point if there are not
enough jobs in other service classes to fill the
central memory and if FLEXIBLE PARTITIONS
is enabled. The system always attempts to use
central memory to its greatest capacity, am
ranges from 0 to 77777s.

Revision M

DSD Commands 5-17

Job Flow Commands

Command

Description

SERVICE ,sc,pi ,p2,... ,pn. (Continued)
pi
CBlpup

Description
Upper and lower bound CPU priorities.
lp is the lower bound CPU priority,
lp ranges from 0 to 77s.
up is the upper bound CPU priority,
up ranges from 0 to 77s, but must be
equal to or larger than the value of lp.

CMcm

Central memory time slice in seconds. This
parameter specifies the maximum amount of time
a job of the specified service class can remain in
central memory, either at a control point or at a
pseudo-control point, before its priority is set to
the lower boundary. When the job initially
exhausts its CM time slice, this lower boundary
is the value of il. Subsequently, when the job
exhausts its CM time slice, this lower boundary
is the value of lp (refer to the QUEUE command
IL and LP parameters), cm ranges from 0 to
77778.

CPcp

Control point slice priority. This parameter
specifies the value of the scheduling priority
which will be set after a job has been at a conrol
point for ct seconds. The priority specified must
be greater than or equal to the lower bound and
less than or equal to the upper bound execution
queue scheduling priorities specified by the CB
parameter (lp ^ cp ^ up). Refer to the QUEUE
command LP and UP parameters.

'"<%Y

^ ^ S

5-18 NOS Version 2 Analysis Handbook

Revision M

Job Flow Commands
jjgfPS

Command

Description

SERVICE,sc,pi ,p2,...,pn. (Continued)
Pi

Description

CScs

Cumulative size in PRUs allowed for all indirect
access permanent files; cs indicates a limit value
for the cumulative size:
0 Unlimited
1 10008
2 5000s
3 50000s
4 1000008

J&Ray

5 2000008
6 400000s
7 Unlimited
CTct

Control point time slice in seconds. This
parameter specifies the maximum amount of time:
that a job of the specified priority can remain at j
a control point before its priority is changed to
the control point slice priority (cp). ct ranges
from 1 to 77778.

JfP*V

0ms
Revision M

DSD Commands 5-19

Job Flow Commands

Command

Description

SERVICE,sc,pi,p2,...,pn.

(Continued)
Pi

Description

DSds

Size in PRUs allowed for individual direct
access permanent files; ds (0 through 7) is used
to specify the corresponding values shown next:
0 Unlimited
1 10008
2 50008
3 500008
4 100000s
5 2000008
6 4000008
7 Unlimited

DTsc

Service class to which a detached job is
assigned. The default value for sc is DI
(detached interactive).

ECec

Maximum user-accessible extended memory field
length in words divided by UEBS* for any job
of the specified service class. This parameter
performs the same function for extended memory
field length that the FL parameter does for
central memory field length, ec ranges from 0 to
3777s.

EMem

Maximum extended memory divided by UEBS
for all jobs of the specified service class. This
parameter performs the same function for
extended memory field length that the AM
parameter does for central memory field length,
em ranges from 0 to 3777s.

1. Refer to Extended Memory Overview in section 3 to determine the value of UEBS.

5-20 NOS Version 2 Analysis Handbook

Revision M

Job Flow Commands

Command

Description

SERVICE,sc,pi,p2,...,pn. (Continued)
Pi

Description

FCfc

Number of permanent files allowed; fo
(0 through 7) is used to specify the
corresponding values (limit value in octal) shownf
next:
0 Unlimited
1 108
2 40s
3 1008
4 2008
5 10008
6 40008
7 Unlimited

FLfl

Maximum field length divided by 100s for any
job of the specified service class. If more
memory is requested, the job is aborted. You
typically use this parameter to limit the
memory requirement for jobs of a specific
service class during certain hours of the day.
For example, you may use the FL parameter to I
specify a maximum field length for all batch
service class jobs between the hours of 2 p.m.
and 4 p.m. fl ranges from 0 to 7777s.

FSfs

Size in PRUs allowed for individual indirect
access permanent files; fs (0 through 7) is used |
to specify the corresponding values (limit value |
in octal) shown next:
0 Unlimited
1 108
2 30s
3 1008
4 300s
5 10008
6 20008
7 Unlimited

Revision M

DSD Commands 5-21

Job Flow Commands

Command

Description

SERVICE ,sc,pi ,p2,... ,pn. (Continued)
Pi

Description

NJnj Maximum number of jobs. For each service
class, this parameter specifies the number of
jobs that can be executing in the system, nj
ranges from 0 to 77778.
SDsd CPU job switch delay in milliseconds, sd ranges
from 0 to 77778.
TDtd Suspension time-out delay. A suspended job will
not be timed out for td*10s seconds, td ranges
from 0 to 77778. The maximum delay is
approximately 9 hours.
TPtp Terminal job priority assigned to a terminal job
that is rolled out waiting for terminal input, tp
ranges from 0 to 7777s, but must be in the
range of values for the execution queue
parameters lp and up (refer to the QUEUE
command LP and UP parameters).

/^^\

The service limits associated with each service class are
established by using SERVICE command entries in the
IPRDECK. These entries normally reflect the ideal service
limits for the job mix of the particular installation. The
values specified in the IPRDECK are important to optimum
system performance and are not normally altered. However,
when changes are necessary they are usually temporary and
the original values will be reset. Figure 5-3 provides space
to record the original values specified in the L display
SDSPLAY. For additional information concerning the
SERVICE command, refer to section 3, Deadstart Decks.
SRST,t.

Changes the secondary rollout sector threshold to the value t
(0 s£ t ^ 77778). Any rollout file smaller than t sectors is
considered a secondary rollout file for the purpose of
equipment selection.

A^^S.

NOTE
The size of the rollout file for any job must be at least
seven sectors larger than the combined size in sectors of the
job's central memory and extended memory field lengths.

■^^s

5-22 NOS Version 2 Analysis Handbook

Revision M

Job Flow Commands
vfitftafy

JOB

SERVICE LIMITS

SERVICE
CLASS

CB/L

C
M

CB/U

FL A
M

E
M

SY
BC
RB
TS
DI
NS
SS
NA
/0^S

CT
IO
11
12
13

Figure 5-3. Record of Original Values in L Display SDSPLAY

Revision M

DSD Commands 5-23

Peripheral Equipment Control Commands

Peripheral Equipment Control Commands
The commands described in this category provide control of the channel-connected
peripheral equipment available to the system. To control unit record equipment that is
connected through communications ports, use the RBF K display described in section 8
and the PSU K display described in the NOS Version 2 Operations Handbook. You
should become familiar with the following DSD displays, which are closely associated
with the use of these and other commands described throughout this section.
• Equipment status display (E,A).
• Disk configuration display (E,C).
• Disk errors display (E,E).
• Family status display (E,F).
• Disk thresholds display (E,H).
• Disk status display (E,M).
• Resource requests display (E,P).
• Tape status display (E,T).
• BIO status display (I).
A complete description of each of these displays is given in the NOS Version 2
Operations Handbook.
Command

Description

ASSIGN,jsn,est. Assigns equipment defined by EST ordinal est (normally a
tape unit) to the job with job sequence name jsn. This
command is entered in response to a flashing REQUEST
message. Use of this command for assignment of a tape unit
should not normally be required because tape assignment is
performed automatically when a volume serial number (VSN)
i s s p e c i fi e d i n t h e j o b r e q u e s t . H o w e v e r, i f a V S N i s n o t ^ .
specified in the job request for a labeled or unlabeled tape, the j
REQUEST message appears at the job's control point (on the
B,0 display), and the ASSIGN command must be entered to
assign a tape unit to the job.
BKSP,est,rr. Backspaces rr octal logical records on the print file for the
BIO equipment defined by EST ordinal est. When rr is not
specified, the default is one record.
BKSPF,est,ff. Backspaces ff octal files on the print file for the BIO
equipment defined by EST ordinal est. When ff is not
specified, the default is one file.

" * )
2. Operation of peripheral equipment is described in the NOS Version 2 Operations Handbook.

5-24

NOS

Version

Analysis

Handbook

Revision

Peripheral Equipment Control Commands

Command

Description

BKSPRU,est,ss.

Backspaces ss physical record units (PRUs) on the print file
for the BIO equipment defined by EST ordinal est. The PRU
count, ss, must be specified. There is no default setting.
Printing resumes at the beginning of a line.

CONTINUE,est.

Resumes printing on the BIO equipment defined by EST
ordinal est.

DOWN,CH = ch,
EQ=est.
or
DOWN,CCH=cch,
EQ=est.
or
DOWN,MCH = ch,
EQ=est.
or
DOWN,EQ=est.

The first two forms of the command disallow the use of
channel ch or concurrent channel cch for the mass storage
device specified by EST ordinal est. If the EQ = est
parameter is omitted, channel ch or cch is disallowed for
all devices in the EST. The EQ=est parameter cannot be
specified if the CH=ch or CCH=cch parameter specifies a
magnetic tape channel. Use of all ports of a concurrent
channel is disallowed.
If channel ch or cch is the only channel available to a mass
storage device, its use is disallowed providing the device is
down. If channel ch or cch is
• not defined as a magnetic tape or mass storage channel
• the last active channel on an equipment that is not
globally unloaded (status N on the E,M display)
• a nonimpact printer channel and any equipment on the
channel is logically ON or assigned to a control point
the command is ignored and the following message appears on
the left screen.
INCORRECT ENTRY

Correct the entry and retry the command.
The third form of the command disallows the use of MUX
channel ch for the equipment specified by EST ordinal est
(this form applies only to model 176). If the EQ=est
parameter is omitted, MUX channel ch is disallowed for all
equipments in the EST.
The fourth form of the command disallows the use of
equipment with EST ordinal est for all channels. It disallows
all access to the equipment by the operating system and user
jobs. This device state is used to allow diagnostic routines
exclusive use of the device for problem isolation and for
preventing access to a device that is being repaired.

Revision M

DSD Commands 5-25

Peripheral Equipment Control Commands

Command

Description

DOWN,CH=ch,
EQ=est.

(Continued)
This command also clears the SUSPCT state for a tape unit
that is currently unavailable (but not OFF or DOWN) because
an unrecovered hardware or tape I/O error has occurred on
the tape or unit. This command can be entered followed by
the ON,EQ=est command to restore the unit to service after a
customer engineer has checked it out, or the unit has been
tested following Control Data's recommended procedures:
You receive an error message if you attempt to DOWN
equipment:
• That already has a DOWN status.
• That is assigned to a job.
• That is the last system device not DOWN.3
• That contains the system dayfile, account file error log, or
maintenance log.
In these cases, the following message appears.
INCORRECT ENTRY

Correct the entry and retry the command.
NOTE
This command should be used with caution since it directly
affects the operation of system peripheral equipment.
DOWN,MID=mid.

Confirms that a machine running in low-speed port
multimainframe mode with machine identifier mid is down.
Enter this command in response to a request at the system
control point of the form:

,A^^S

IF mid DOWN ENTER *D0WN,MID=mid*

Make this entry if the machine is down; otherwise, clear the
message by entering:
GO,SYS.

<^fe\
3. Applies only to mass storage equipment.

5-26 NOS Version 2 Analysis Handbook

Revision M

Peripheral Equipment Control Commands

Command

Description

END,est,rc.

Terminates the current operation on the BIO equipment
defined by EST ordinal est. If est defines a line printer or
card punch, BIO then assigns the next available file to that
equipment. If est defines a card reader that is actively reading
cards when END,est is entered, the job terminates at the last
card read. The next card is treated as the beginning of a new
job. If another card deck follows the end-of-information card
(multipunch 6/7/8/9), it is processed normally.
If est defines a card reader that is stopped because of a
compare error when END,est. is entered, perform the following
steps:
1. Remove the remainder of the card deck, except the
end-of-information card, from the card reader input hopper.
2. Ready the card reader to read the end-of-information card.

yms

The job terminates; and if another card deck follows the
end-of-information card, it is processed normally.
The re parameter cancels a portion of the repeat count
specified for that equipment (refer to the REPEAT command
later in this section). For example, if the current operation on
equipment est had been set to be repeated five times
(operation performed six times), entering a value of 4 for re
would permit the operation to be performed just two times. If
the repeat count is zero, this command performs the END
operation once.
FORM,est,fc.

Assigns a 2-character forms code fc to the BIO line printer or
card punch defined by EST ordinal est. Only those files in the
output queue assigned the forms code fc are directed to
equipment est. A user can assign a forms code to an output
file using the ROUTE command. (For a description of the
ROUTE command, refer to the NOS Version 2 Reference Set,
Volume 3.) The value of the forms code can range from AA to
99. If the forms code is not present, the current forms code
field is cleared (value is null).

ID,est,id.

Assigns a numeric identifier id to the card punch, card reader,
or printer defined by EST ordinal est. The value of the
identifier can range from 00 to 67s. Only those files in the
proper queue with an identifier equal to id are directed to the
card punch or printer defined by est. Refer to the LOAD
command in this section to assign an identifier to a queue
type file. All subsequent jobs loaded from card reader est are
assigned the identifier id.

Revision M

DSD Commands 5-27

Peripheral Equipment Control Commands

Command

Description

IDLE,EQ=est.

Use this command when you want to continue using the disk
storage device specified by EST ordinal est even though it is
failing occasionally. When the IDLE command is used in
conjunction with the THRESHOLD command, it allows some
degree of flexibility in deciding when to repair such a device.
New files will not be assigned to a device with IDLE status
unless no suitable alternative device exists, but files already
on the device may continue to be accessed as if the device had
a status of ON. If the device is a spun down 834, 836, 887, or
9853 drive, it will be automatically spun up. It may take up
to 3 minutes to spin up the device.
Suppose a failing disk storage device causes the system to set
the device's status to OFF. Suppose also that the device is
failing infrequently, for example, once or twice per hour, and
contains several permanent files that must remain available
during peak production periods. In this situation, you may use
the THRESHOLD command to increase the verification failure
threshold and then use the IDLE command to allow continued
use of the device. This device could then be repaired after the
peak production period has passed, causing less disturbance to
system users.
NOTE
The decision to continue using a failing device should be made
under the advisement of a customer engineer. If there is a
good chance of data corruption due to the nature of the
failure, it may be best to leave the device OFF until it can be
repaired.
If you enter an IDLE command for a device with a status of
OFF or DOWN, the system performs a device verification to
ensure the hardware is usable and the disk pack contains
valid data. If this verification fails and the verification failure
threshold is exceeded, the device state remains unchanged.
However, if the device verification finds no errors the device's
state changes to IDLE, the verification failure count (displayed
on the E,H display) is set to zero, and any jobs that were
rolled out waiting for the device are allowed to continue
processing.

5-28 NOS Version 2 Analysis Handbook

Revision M

Peripheral Equipment Control Commands

yms
Command

Description

IDLE,EQ = est.

(Continued)
If you attempt to change a device's state to IDLE, the message
INCORRECT ENTRY appears if one of the following
conditions is true:
• The device is already IDLE.
• The device is DOWN and assigned to a job.
• The device is DOWN and no channels are UP for the
device.
If you enter IDLE for a device with a status of ON, the
verification process is not performed; the device state is simply
changed to IDLE.
If you enter IDLE for a device other than a disk, the IDLE
command is ignored.

IDLEFAMILY,est.

This command performs one of the two following functions,
depending on the status of the family.
• If the family is active, the IDLEFAMILY command
deactivates it by aborting all new jobs and USER
commands for the family on the equipment specified by
EST ordinal est. Jobs in progress are allowed to complete.
ISF and permanent file utilities, such as PFDUMP, can be
used on the inactive family.
• If the family is inactive, the IDLEFAMILY command
activates it. Jobs can then access the family on the
equipment specified by EST ordinal est.
The FAMC column of the E,F display shows the number of
jobs in progress on the equipment.

Revision M

DSD Commands 5-29

Peripheral Equipment Control Commands

Command

Description

INITIALIZE,op,esti,
est2,...,est5.

Reverses current setting of initialize option op for mass
storage devices defined by EST ordinals est (maximum of five
devices). Examine the E,A display to determine correct EST
ordinals.
Level of Initialization

AF Initialize inactive account dayfile.
A L To t a l i n i t i a l i z a t i o n .
DF Initialize inactive system dayfile.
EF Initialize inactive error log.
FP Format pending.4
FT Total initialization as full-track device.5
HT Total initialization as half-track device.5
MF Initialize binary maintenance log.
PF Initialize permanent files.
QF Initialize inactive queue files.
This command provides the capability to initialize and flaw
tracks on any mass storage device during normal system
operation. Each time this command is entered it is logged in
the error log.
If local unload (L) status is set for the device, the INITIALIZE
command is ignored and the following message appears on the
left console screen.
INCORRECT ENTRY

However, the INITIALIZE command is allowed to execute
while local unload status is set if an error code (CE, IL, LE)
is set.

4. Sets format pending bit in the MST for 881/883 pack reformatting. Refer to the description of the
FORMAT program in appendix G.
5. Device must be removable.

5-30 NOS Version 2 Analysis Handbook

Revision M

Peripheral Equipment Control Commands

Command

Description

INITIALIZE,op,esti,
est2,...,est5.

(Continued)
Entry of this command does not in itself initialize the
specified device. It merely sets initialize status for the device
so that it may be initialized. However, if fast attach files
(special system files) are active on the specified device and
initialization level of AL or PF is specified, initialize status
cannot be set until these files are returned. In this case, the
message
FAST ATTACH FILES ON DEVICE.

appears at the system control point on the system status
display (B,0). Refer to the description of this message in the
NOS Version 2 Operations Handbook for additional
information.
The procedure involved in initializing a mass storage device is
described in section 8, K-Display Utilities, under the heading
Initialize K Display. The following describes system activity
when initialization occurs.
If the device is shared in a multimainframe environment,
initialization does not proceed until all other mainframes
sharing the device have processed an UNLOAD command for
the device and user counts on all machines are zero. If all
machines have not unloaded the device, this control point
message is displayed:
EQest BUSY ON 10=1d.

Va r i a b l e D e s c r i p t i o n

Revision M

est

EST ordinal.

Machine identifier of the first machine found
without unload status set.

DSD Commands 5-31

Peripheral Equipment Control Commands

Command

Description

INITIALIZE,op,esti,
est2,...,est5.

(Continued)

/s?v

If initialize status is set on this device for another mainframe,
the INITIALIZE command is ignored and this message appears
at the system control point on the system status display (B,0):
INITIALIZE PENDING ON THIS DEVICE.

When the AL initialization option is specified, the label on the
device to be initialized is either updated or a new label is
created. If the label on the device is bad or cannot be
recognized, the new label is created and all current data on
the device is lost. If the label is found to be good, it is
updated and all permanent file information is cleared. In this
case, system library or temporary files (local, rollout, and so
forth) residing on the device are not disturbed. If the device
being initialized is a master device, the system scans all other
mass storage devices in the family that contain direct access
files and releases the space for files with catalogs on this
device. If the device being initialized contains direct access
files, the system scans all other master devices and sets the
catalog entries on those devices to indicate that the files were
purged. All or part of the permanent file system can be
initialized and then reloaded if necessary (refer to the
description of permanent file utilities in section 17, Permanent
File Utilities.
LOAD,est,id.

Requests that a job be loaded from equipment defined by EST
ordinal est (normally tape unit). The job is assigned a numeric
identifier id ranging from 00 to 67s. If id is not specified, it
defaults to 00. Examine the E,A display to determine the EST
ordinal of the equipment to be used.

5-32 NOS Version 2 Analysis Handbook

Revision M

r
r

Peripheral Equipment Control Commands

Command

Description

MOUNT,est,P.

Clears the local unload (L) and global unload (N) status for a
mass storage device and reactivates the device. If the device is
a spun down 834 or 836 drive, it will be automatically spun
up. The device is defined by EST ordinal est (examine the E,A
display to determine the EST ordinal).
When you specify P in the MOUNT command for an
independent shared device in a multimainframe environment,
the system presets the device with EST ordinal est. The preset
(P) option can be specified only on the first mainframe to
access the device.
If the device defined by EST ordinal is not a mass storage
device, the MOUNT command is ignored and this message
appears on the left console screen:
INCORRECT EQUIPMENT.

If the device is shared in a multimainframe environment and
another mainframe has an unsatisfied initialize request
pending for that device, the MOUNT command is ignored and
this message appears at the system control point on the
system status display (B,0):
INITIALIZE PENDING ON THIS DEVICE.

Revision M

DSD Commands 5-33

Peripheral Equipment Control Commands

Command

Description

MSAL,t=esti,
est2,...,estn.

Assigns job files of type t to mass storage devices defined by
EST ordinals esti. The specified mass storage device must be
nonremovable. A limit of 47 devices may be specified on a
single entry. Examine the disk status display (E,M) to
determine if the device is nonremovable.
t Description
B

LGO.

D J o b d a y fi l e .
I

Input.

Local.

O Output.
P P r i m a r y.
R Rollout.
S Secondary rollout.
T Te m p o r a r y .
If no devices are specified for a file type, the system selects a
temporary device.
Secondary rollout files do not exist until the command
SRST=t (where t is the size in sectors of the file, from 0 to
77778) defines a threshold; the default value of a threshold is
0. All rollout files smaller than the threshold are secondary
rollout files. These files are assigned to the devices specified
with the MSAL,S command.
All files greater than or equal to the threshold are assigned to
the rollout file devices (MSAL,R command).
The following example illustrates a use for secondary rollout
files. Equipment 5 is extended memory via DDP. Secondary
rollout files to extended memory is assigned by
MSAL,S=5.

5-34 NOS Version 2 Analysis Handbook

Revision M

Peripheral Equipment Control Commands

Command

Description

MSAL,t=esti,
est2,...,estn.

(Continued)
The threshold count is set by the SRST command so that
rolled out files under 20 sectors long are assigned to extended
memory. For additional information concerning the SRST
command, refer to section 3, Deadstart Decks.
EQPDECK

EQ005=DP,ST=0N,SZ=4000,CH=30.

MSAL,S=5.

IPRDECK

SRST=20

NEXTREEL,est.

Indicates to the system that you have verified that the correct
tape has been mounted (or is about to be mounted) on the
specified tape drive. You enter this command in response to a
CHECK AND MOUNT message on the E,P display.
The system issues the CHECK AND MOUNT message
whenever it unloads an unlabeled tape as a result of a ring
conflict or an end-of-reel condition. This message reminds you
that the specified tape unit is still assigned to a job and is
not available for general use. The system only issues this
message if the COMSMTX installation parameter PONR is 1.

0ms
Revision M

DSD Commands 5-35

Peripheral Equipment Control Commands
yS&V

Command

Description

OFF,EQ=est. Logically turns off the device defined by EST ordinal est. This
command allows you to logically remove a device from the
operating environment so that no user access of the device is
permitted. If a user job attempts to access the device, it is
rolled out to wait for the device status to become ON or
IDLE. However, system utilities are permitted to access the
device, so it can be dumped or loaded. If the device is a spun
down 834, 836, 887, or 9853 drive, it will be automatically
spun up. It may take up to 3 minutes to spin up the device.
If you enter the OFF command for a device with a status of
DOWN, the system performs a verification of the device label.
This provides assurance that the correct pack is mounted on
the drive and the controller is accessing the right drive after
a repair action.
If you attempt to change a device's state to OFF, the message
INCORRECT ENTRY appears if one of the following
conditions is true:
• The device is already OFF.
• The device is DOWN and assigned to a job.
• The device is DOWN and no channels are UP for the
device.
Examine the E,A display to determine the EST ordinal and
current status (ON, OFF, IDLE, or DOWN) of the device. If
est specifies a disk storage device and the system library or
temporary files (local, rollout, and so forth) reside on that
device, it should not be turned off. Examine the disk status
display (E,M) to determine which disk storage devices have
system residency or allow system allocation of temporary files.
In addition, if an MSAL entry is currently specified for a disk
storage device, it is cleared when that device is turned off.
The MSAL designation is not reset automatically when the
device is turned back on and must be reset manually (if
necessary) using the DSD command MSAL.
This command also clears the SUSPCT state for a tape unit
that is currently unavailable (but not OFF or DOWN) because
an unrecovered hardware or tape I/O error has occurred on
the tape or unit. This command can be entered followed by
the ON,EQ=est command to restore the unit to service after a
customer engineer has checked it out, or the unit has been
tested following Control Data's recommended procedures.

5-36

NOS

Version

Analysis

Handbook

Revision

Peripheral Equipment Control Commands

Command

Description

ON,EQ=est.

Logically turns on the device defined by EST ordinal est. This
command allows you to activate a device currently having
OFF status in the EST. If the device is a spun down 834, 836,
887, or 9853 drive, it will be automatically spun up. Examine
the E,A display to determine the EST ordinal and current
status (ON, OFF, IDLE, or DOWN) of the device.
Use this command to bring a disk storage device back into
use following its repair. You can also use the ON command
after repairing a controller that provides the only access to a
disk storage device.
When you enter ON for a device with a status of OFF or
DOWN, the device's state does not change to ON immediately.
First the system attempts to verify that the drive and
channels accessing the device are usable and the data on the
disk pack is in the proper format. If this verification process
fails and the verification failure threshold is exceeded, the
system sets the device's state to OFF. If the verification finds
no errors, the device's state changes to ON, the verification
failure count (displayed on the E,H display) is set to zero, and
any jobs that were rolled out waiting for the device are
allowed to continue processing.
If you enter ON for device with a status of IDLE, the
verification process is not performed; the device's state simply
changes to ON.
If you attempt to change a device's state to ON, the message
INCORRECT ENTRY appears if one of the following
conditions is true:
• The device is already ON.
• The device is DOWN and assigned to a job.
• The device is DOWN and no channels are UP for the
device.

PRSIZE,est,ps.

Revision M

Sets the paper status ps to short (S) or long (L) paper for the
printer with EST ordinal est. Short paper has a form length of
8.5 inches and long paper has a form length of 11 inches.

DSD Commands 5-37

Peripheral Equipment Control Commands

Command

Description

REPEAT,jsn,rc.6

Alters the repeat count for the queue file specified by job
sequence name jsn. If the file is still in the queue, the repeat
count for the file is set to re. If the file is already being
processed by BIO, the remaining repeat count for the file is
increased by re. The maximum value that can be entered for
re is 778. The default value for re is 1.

REPRINT,est,pr.

Terminates the current operation on the BIO printer
equipment defined by EST ordinal est and reenters the job in
the print queue with a queue priority specified by prOO
(service class minimum ^ prOO ^ service class maximum;
refer to the S display in the NOS Version 2 Operations
Handbook; pr value is multiplied by 100s internally). If pr is
not specified, the service class default priority is assigned.

REPUNCH,est,pr.

Terminates the current operation on the BIO card punch
equipment defined by EST ordinal est and reenters the job in
the punch queue with a queue priority specified by prOO
(service class minimum ^ prOO ^ service class maximum;
refer to the S display in the NOS Version 2 Operations
Handbook; pr value is multiplied by 1008 internally). If pr is
not specified, the service class default priority is assigned.

RETRY,est.

Reissues a tape operation that previously aborted with one of
the following load point errors appearing in the E,P display:
CLEANER FAULT
READ ID BURST
WRITE ID BURST
est represents the EST ordinal of the tape unit where the load
point error occurred. Examine the E,P display to determine
the EST ordinal. The tape unit must be ready before you
enter the RETRY command. Examine the E,T display to
ensure that the tape is loaded and the tape unit is ready.
The RETRY command is to be used after the system detects a
load point error on a tape. Upon detecting such an error, the
system issues an error message to the E,P display and unloads
the tape. The operator then has the opportunity to fix the
failing tape or tape drive. Upon completing this step, the
operator reloads the tape on the same tape unit and enters
the RETRY command. The system then reissues the tape
operation. If the failure cannot be fixed at this time, the
operator should enter the TERMINATE command to abort the
recovery attempt.

6. When the current BIO operation is repeated, maximum line and card limits are reinitialized prior to
printing or punching of the file being processed. User control limits apply individually to each output file
copy produced.

5-38 NOS Version 2 Analysis Handbook

Revision M

Peripheral Equipment Control Commands

Command

Description

SCRATCH,est.

Declares the tape mounted on an unassigned magnetic tape
unit, defined by EST ordinal est, to be a scratch tape. This
command enables a tape to be available to satisfy scratch
VSN requests and still be assigned by its original VSN Thus
the VSN defined on the tape (in VOL1 label) is not redefined'
as scratch although the VSN will appear as SCRATCH on the
tape status display (E,T).
Scratch status is retained for only one job assignment. This
allows a tape to be used for scratch purposes on a temporary
basis. For example, a job requests a tape mounted on the tape
unit defined in this command by specifying the current VSN
for that tape in the request. The tape is then assigned to the
job as a scratch tape (the original VSN is retained and not
made scratch). When that job releases the tape, SCRATCH
status is cleared, and unless this command is entered again,
that tape would not be assigned as a scratch tape in future'
requests. To determine if SCRATCH status is in effect for a
tape, monitor the tape status display (E,T).

SECUREQ,est,
LA = lowerlevel,
UA=upperlevel.

Changes the equipment access level limits for the unit record
equipment with EST ordinal est. On a secured system, only
files that have access levels within these limits can be printed
on the specified equipment. The original limits are set during
deadstart by the ACCESS command entries in the EQPDECK.
The parameters LA = lowerlevel and UA = upperlevel specify
the lower and upper access level limits for the equipment.
NOTE
On a secured system this command is accepted only if a
security administrator has placed the system in security
unlock status.

SKIP,est,rr.

Skips forward rr octal logical records on the print file for the
BIO equipment defined by EST ordinal est. When rr is not
specified the default is one record.

SKIPF,est,ff.

Skips forward ff octal files on the print file for the BIO
equipment defined by EST ordinal est. When ff is not specified
the default is one file.

Revision M

DSD Commands 5-39

Peripheral Equipment Control Commands

Command

Description

SKIPRU,est,ss.

Skips forward ss PRUs on the print file for the BIO
equipment defined by EST ordinal est. All parameters must be
specified; there are no default settings. The PRU count, ss, is
limited to 10s PRUs (the current buffer size) plus the number
of PRUs remaining in the buffer. If the buffer was empty, ss
would be limited to 20s PRUs. If ss is larger than the number
of PRUs remaining in the buffer, the buffer is filled again and
the additional PRUs are skipped on the new print file. For
example, if five PRUs remained in the print file and ss was
specified as 10, the remaining five PRUs would be skipped,
the buffer filled again, and five additional PRUs skipped.
Printing resumes at the beginning of a line.

SPINDOWN,est.

Spins down the 834, 836, 887, or 9853 disk storage device
defined by EST ordinal est. To enter this command, the
console must be unlocked (refer to the UNLOCK command
later in this section).

SPINUP,est.

Spins up the 834, 836, 887, or 9853 disk storage device
defined by EST ordinal est.
NOTE
Spinning down an 834, 836, 887, or 9853 disk storage device
that does not have global unload status (N), can cause mass
storage device status errors or permanent file errors when the
device is spun up.

STOP,est.

Stops printing on the BIO equipment defined by EST ordinal
est.

^ s

5-40 NOS Version 2 Analysis Handbook

Revision M

Peripheral Equipment Control Commands

Command

Description

SUPPRESS,est.

Suppresses automatic printer carriage control on the BIO line
printer defined by EST ordinal est. This command stops the
page eject function on the line printer to provide a continuous
listing for the current job.

TEMP=esti,
est2,...,estn.

Reverses current set or clear condition of temporary file status
for mass storage devices defined by EST ordinals esti. When
temporary file status is set, the system can use the specified
device for allocation of temporary files. This command is not
valid if the device specified is defined as removable. Examine
the disk status display (E,M) to determine:
• The EST ordinal of the device.
• If the device is defined as removable.
• If temporary file status is currently selected (set) for the
device.

jp^s.

TERMINATE,est.

Aborts a tape load point error recovery attempt (refer to the
RETRY command in this section), est represents the EST
ordinal of the tape unit where the load point error occurred.
Examine the E,P display to determine the EST ordinal.
The TERMINATE command also clears the error message in
the E,P display and issues the error message to the system
dayfile.

Revision M

DSD Commands 5-41

Peripheral Equipment Control Commands

Command

Description

THRESHOLD, You can use the THRESHOLD command to set disk storage
type=value, device thresholds for the devices defined by EST ordinals esti.
esti,est2,...,estn. You must specify at least one EST ordinal. Use this command
in conjunction with the IDLE command. You can specify one
of the following threshold types. If no threshold type is
specified, VF is assumed.
type Description
VF Verification failure threshold. Each time an
unrecovered error occurs on a device, the system
performs a device verification. If the error occurs
again during the verification process and the error is
in the device or in the only available channel or in
controlled access to the device, the verification failure
count is incremented and compared with the
verification failure threshold. If the threshold is
exceeded, the system sets the device's state to OFF.
If the threshold is not exceeded, the device's state is
set to IDLE to restrict allocation of new files on the
device. Because a disk storage error can cause a job
to abort, it is important to understand that the higher
this threshold is set the more jobs that may abort
before the system sets the device's state to OFF. By
setting the verification failure threshold to a value
greater than zero, you can continue to use a failing
device. Do this only when the failures are relatively
infrequent, the failures do not cause corruption of
permanent files, and the device is essential during the
next several hours of production. After the peak hours
of production, the device can be repaired during a
planned corrective maintenance period.
RA Restricted activity threshold. When the available
space on a device falls below this threshold, new files
are not assigned to the device unless no other
suitable device is available.
LS Low space threshold. When the available space on a
device falls below this threshold, the operator is
notified on the A.OPERATOR display.
RE Recovered error threshold. Each time a recovered
error occurs on a disk storage device a count is
incremented and checked against the recovered error
threshold for that device. If the threshold is exceeded,
the operator is notified on the A,OPERATOR display.
UE Unrecovered error threshold. Each time an
unrecovered error occurs on a disk storage device a
count is incremented and checked against the
unrecovered error threshold for that device. If the
threshold is exceeded, the operator is notified on the
A,OPERATOR display.
v^^v

5-42

NOS

Version

Analysis

Handbook

Revision

Peripheral Equipment Control Commands

Command

Description

THRESHOLD,
type = value,
esti,est2,.-->estn.

(Continued)
The threshold value can range from 0 to 3777s. Specify a
threshold value of * to obtain the default value for the
specified type, for example, THRESHOLD,RA=*,21*. The
following default values are used.
type

value

TRAIN,est,t.

1/8 of the number of tracks on the device

1/16 of the number of tracks on the device

50s

Assigns or changes print train identifier t of the line printer
defined by EST ordinal est. This command can set the
identification if it was not specified in the EQ entry of the
EQPDECK, or change an identification previously included in
the EQPDECK. An LR designation in the EQ entry indicates
a 580-12 line printer, LS is a 580-16 line printer, LT is a
580-20 line printer, and LX is a 5870 printer. Print trains
supported for the 580 printers are 595-1/596-1, 595-5/596-5,
and 595-6/596-6. The print train supported for the 5870 printer
is t = 7. The t field specifies the print train.
t

Description

0 595-1/596-1 (CDC graphic 63/64-character set);
default.
595-1/596-1 (CDC graphic 63/64-character set).
Reserved for future use.
Reserved for future use.7
595-6/596-6 (ASCII graphic 63/64-character set or
ASCII graphic 95-character set).
595-6/596-6 (ASCII graphic 63/64-character set).
595-6/596-6 (ASCII graphic 95-character set).
595-6/596-6 (ASCII graphic 63/64-character set or
ASCII graphic 95-character set).

7. These values are allowed but will default to 595-1/596-1.

Revision M

DSD Commands 5-43

Peripheral Equipment Control Commands

Command
TRAIN,est,t.

Description
(Continued)
If an invalid external characteristic (EC)8 is specified, the
queued file processor cannot output the file. The following
shows which files will print and which files will not print
for a given print train selection.
Print Train
Selected

Will Print File
With the
Specified EC

Will Not Print
FUe With the
Specified EC

None, B4, B6

A4, A6, A9

None, B4, B6

A4, A6, A9

None, A4, A6,
A9

B4, B6

None, A4, A6

B4, B6, A9

None, B4, B6, A4, A6

None, B4, B6,
A4, A6, A9

y^BB\
8. Refer to the NOS Version 2 Reference Set, Volume 3 for a discussion of the ROUTE command EC
parameter.

5-44 NOS Version 2 Analysis Handbook

Revision M

Peripheral Equipment Control Commands

Command

Description

UNLOAD,est.

Physically unloads a tape or logically removes a removable
disk storage device from the operating system. The device to
be unloaded is defined by EST ordinal est (examine the E,A
display to determine the EST ordinal). Also, in a
multimainframe environment, the UNLOAD command must
be issued if another mainframe wants to initialize a shared
mass storage device, whether the device is removable or
nonremovable (refer to the INITIALIZE command earlier in
this section). If a magnetic tape is specified, the tape is
physically unloaded. If a removable disk storage device is
specified, you can dismount the disk pack on that device
after all activity on the device has been completed.
NOTE
If a nonremovable shared mass storage device is to be
specified, the console must be unlocked (refer to the
UNLOCK command later in this section).
Magnetic tape units:
If a tape is currently assigned to a job, it cannot be
unloaded. If you attempt to unload it, the UNLOAD
command is ignored and this message appears on the left
console screen:
UNIT NOT AVAILABLE

Examine the tape status display (E,T) before entering the
UNLOAD command to determine if the tape to be unloaded
is currently assigned to a job. If the tape is not currently
assigned, entering this command unloads the specified tape.
Mass storage devices:
The UNLOAD command is valid for any shared mass
storage device in a multimainframe environment for the
purpose of initialization. Otherwise, the command is valid
only for removable devices. (Only removable devices may be
physically removed by unloading.) After entering the
UNLOAD command, monitor the disk status display (E,M).
Execution of this command immediately causes local unload
(L) status to appear in the STATUS field for that device.
While L status is displayed, no new users are permitted to
access files on the device. A user currently accessing files on
the device can continue while at least one direct access file
from the device is attached to the job. When the user count
is zero and there are no checkpoint requests pending, one of
the following two actions occurs.

Revision M

DSD Commands 5-45

Peripheral Equipment Control Commands

Command

Description

UNLOAD,est.

(Continued)
• If the device is removable and the L status is set in all
machines accessing the device, global unload (N) status is
displayed. This indicates that the device may now be
physically dismounted.
NOTE
If a multispindle family is mounted on a single spindle
device, only the first device shows the global unload status.
• If an initialize is pending on the device and all other
machines accessing the device have L status set, the
initialization proceeds. However, initialization cannot take
place if the device has been unloaded.
NOTE
A device should be physically dismounted only if global
unload status (N) is displayed on all machines accessing
the device.
If a removable pack is dismounted before the N status is
displayed, the following may occur.
• Mass storage device status errors.
• Permanent file errors when the pack is remounted at some
later date.
• If another pack has been mounted, accesses made by a
previously attached user may destroy information on the
new pack or the user may retrieve information from the
new device which he is not necessarily privileged to access.
Mass storage device status errors are also possible in this
situation.
NOTE
If the Mass Storage Extended Subsystem (MSE) is active,
it must be idled before unloading a removable family pack
which has MSE files. After dismounting the family pack,
MSE can be initialized again.

5-46 NOS Version 2 Analysis Handbook

Revision M

^ ^ S

Peripheral Equipment Control Commands

Command

Description

UP,CH=ch.
or
UP,MCH=ch.9
or
UP,CCH=cch,
EQ=est.

The first two forms of the command allow resumption of
normal use of channel ch by magnetic tape units or
mass storage devices, reversing the effects of the
DOWN command.
The third form of the command allows resumption of normal
use of both ports of concurrent channel cch for the mass
storage device specified by EST ordinal est. If the EQ=est
parameter is omitted, channel cch resumes normal use for
all devices in the EST.
If you enter UP for a channel (ch or cch) that is already
UP, the following message appears on the console:
INCORRECT ENTRY

If the channel is already up, no further action is necessary.
VALIDATE,est.

Causes validation of mass storage tables associated with the
equipment defined by EST ordinal est. The equipment must
be available mass storage and the MS VALIDATION option
must have been selected in the IPRDECK at deadstart.

VSN,est,.

Declares the tape mounted on an unassigned magnetic tape
unit, defined by EST ordinal est, to be a scratch tape. This
command is similar in function to the SCRATCH command
in that it enables a tape to be available to satisfy scratch
VSN requests. However, if the tape is labeled and a write
function is performed, the VSN specified in the VOL1 label
will be rewritten as a scratch VSN, destroying the original
VSN and making the tape available for future scratch VSN
requests. The VSN also appears as ***est (est is the ordinal
of the est) on the tape status display (E,T). Refer to the'
VSN,est,vsn command, next, for a discussion of the
INCORRECT ENTRY message which is also applicable to
VSN,est,.

9. Model 176 only.

Revision M

DSD Commands 5-47

Peripheral Equipment Control Commands

Command

Description

VSN,est,vsn.10 Assigns VSN vsn to an unassigned magnetic tape unit defined
by EST ordinal est. This command allows you to specify a
1- to 6-character VSN for a mounted, unlabeled tape so it may
be assigned and referenced automatically. For example, when
a job specifies a VSN in the request for an unlabeled tape, an
entry for that job appears in the resource requests display
(E,P). This display indicates the job sequence name of the job,
the type of tape unit, 7 track (MT) or 9 track (HD, PE, or
GE), on which the tape is to be mounted, the required VSN,
user name of the job, and the required write ring status (IN
or OUT). If the correct tape is not currently mounted, mount
the tape on an available unit (ensuring that track type and
write ring status are correct), ready the unit, and enter this
command. The system equates the VSN you enter with that
specified by the job and assigns the tape automatically upon
demand.

If the tape mounted on the tape unit defined by EST ordinal
est is a labeled tape, has already had a VSN assigned by
console command, or has not yet been checked for a label by
the magnetic tape subsystem, this command is ignored. The
message
INCORRECT ENTRY

a p p e a r s o n t h e l e f t c o n s o l e s c r e e n . To c h a n g e a V S N _ ^ ~
previously assigned by this command, clear the first VSN by 1
entering:
VSN,est.

est

Description

est EST ordinal of the tape unit.
/ssev

5-62 NOS Version 2 Analysis Handbook

Revision M

System Control Commands

Command

Description

DISABLE,op.
or
ENABLE,op.

(Continued)
op

Description

SYSTEM DEBUG

Enables or disables the system debug
mode of operation. Unlock the console
(refer to the UNLOCK command later
in this section) to enable or disable this
option.
When the system is in system debug
mode, it is less tolerant of system
errors; that is, it is more likely to hang
upon experiencing errors. When the
system is not in system debug mode, it
rates system errors as critical or
noncritical.
For critical errors, the system partially
or totally interrupts system operation to
tend to the errors. For noncritical
errors, the system logs them in the
binary maintenance log (BML) and
inasmuch as possible allows system
operation to proceed. You can initiate
the system debug mode with the DSD
ENABLE command or the corresponding
IPRDECK entry.

There is another system state called
debug mode which is conceptually
different from that of system debug
mode. Debug mode is the state of the
system where a user with system origin
privileges can make modifications to the
running system. You can initiate this
mode of operation with the DSD
command DEBUG. The left screen
header of the system console indicates
whether the system is in debug mode
or not.

0ims

Revision M

DSD Commands 5-63

System Control Commands

Command

Description

DISABLE,op.
or
ENABLE,op.

(Continued)
op

Description

TAPE PF STAGING

Enables or disables the staging of tape
alternate storage resident files to disk.
Disabling TAPE PF STAGING causes
jobs to abort if they attempt to access
files which only reside on tape alternate
storage.

USER EXTENDED
MEMORY

Enables or disables use of the user
accessible area of extended memory. If
disabled, no job can access the user
area of extended memory and, other
than subsystems, all jobs currently
accessing the area are rolled out.

IDLE.

Prevents any new jobs from being scheduled to a control point
but does not terminate the jobs currently assigned. If a job is
rolled out while this command is in effect, it will not be
scheduled back to a control point until the AUTO,
MAINTENANCE, or SCHEDULE command is entered.

K.messagetext

Allows entry of data messagetext in the user- or
system-defined CPU buffer for control when the K display is
active. Refer to section 8, K-Display Utilities, for information
about the K display.

L.messagetext

Allows entry of data messagetext in the user- or
system-defined CPU buffer for control when the L display is
active. Refer to section 9, L-Display Utilities, for information
about the L display.

LOCK.

Locks the console keyboard. This command prevents entry of
restricted commands (refer to the UNLOCK command later in
this section for a list of restricted commands). All other DSD
commands can be entered when the console is locked. The
console is normally locked when the system is being used in a
production environment.

^"^^\

5-64 NOS Version 2 Analysis Handbook

Revision M

System Control Commands

Command

Description

MAINTENANCE.

This command performs the same functions as the AUTO
command but additionally starts several maintenance routines.
Refer to Initiating Job Processing in section 2, Deadstart, for
complete information concerning this command.

SCHEDULE

Initiates automatic job processing (reversing the effect of a
previous IDLE command), but does not initiate subsystems as
the AUTO command does.

STEP.

Sets the monitor in step mode. Setting the monitor in step
mode stops all central memory I/O operations and prevents the
system from processing PP requests when the next monitor
function is encountered. Pressing the space bar releases the
present step and stops again for each subsequent monitor
function. If a DSD command is entered while the system is
in step mode and all PPs are assigned, it is possible the
request cannot be satisfied. In that case, the screen(s) blinks
until you correct the condition by clearing the entry.
When step mode is set, the message STEP appears in the
header of the left screen display. Unlock the console before
entering this command (refer to the UNLOCK command later
in this section).
This command is generally used for debugging purposes and
should not be used in a normal production environment. In
addition, the system may set step mode automatically upon
detection of a main power failure or abnormal environmental
condition.

17. Monitor functions are described in the NOS Version 2 Systems Programmer's Instant.

Revision M

DSD Commands 5-65

System Control Commands
>*^^v

Command

Description

STEP,jsn,ff,b,v.
or
STEP„ff,b,v.

Sets step mode for the job with job sequence name jsn
(first form of the command) or all jobs (second form of the
command) at the next occurrence of monitor function ff when
output register byte b has value v.
If jsn is specified (first form of the command), the monitor
function ff, the output register byte number b, and the output
register value v can be optionally specified for more precise
control of when the step mode is executed. The values for b
can be from 0 to 4; the values for v can be from 0 to 7777s.
If jsn is not specified (second form of the command), the
monitor function ff must be specified. The output register byte
number b and value v can be optionally specified for more
precise control of when the step mode is executed. The values
for b can be from 0 to 4; the values for v can be from 0
to 77778.
For either form of the command, pressing the spacebar
releases the current step and steps the job or system at the
next occurrence of the monitor function ff, if specified, or the
next monitor function from the job if the first form is used
and no monitor function is specified.
Using the second form of the command may stop all central
memory I/O operations and prevent the system from processing
PP requests. If a DSD command is entered while the system
is in step mode and all PPs are assigned, it is possible the
request cannot be satisfied. In this case, the screens blink
until you clear the entry. The message STEP followed by the
monitor function number ff (if specified) appears in the header
of the left screen displays while this command is in effect.
The console must be unlocked before entry of this command is
permitted (refer to the UNLOCK command later in this
section).
These commands are generally used only for debugging
purposes. Do not enter these commands if the system has
automatically set step mode because of a power failure or
abnormal environmental condition.

TIME.hh.mm.ss.

Changes the current system time. Unlock the console before
entering this command (refer to the UNLOCK command later
in this section).
Parameter

Description

Hour; 00 through 23.

Minute; 00 through 59.

Second; 00 through 59

y ^ ^ \

5-66 NOS Version 2 Analysis Handbook

Revision M

System Control Commands

Command

Description

UNLOCK.

Unlocks the console keyboard. When this command is active,
the message UNLOCK appears in the header of the left screen
display. Although all DSD commands can be entered when the
console is unlocked, the following commands are restricted to
entry only when the console is unlocked.
DATE.yy/mm/dd.18
DEBUG.
DISABLE,PRIVILEGED ANALYST MODE.19
DISABLE.SECONDARY USER COMMANDS.19
DISABLE,SYSTEM DEBUG.
DROP„qt,ujn.
ENABLE,ENGR.18
ENABLE,PRIVILEGED ANALYST MODE.19
ENABLE,SECONDARY USER COMMANDS.19
ENABLE,SYSTEM DEBUG.
OVERRIDEJsn.
SPINDOWN,est.
STEP.
STEP,jsn,ff,b,v.
STOP,sub.
TIME.hh.mm.ss.18
UNLOAD,est. (est specifies a nonremovable shared mass
storage device)
UNSTEP.
All memory entry commands18
All channel control commands
All extended memory flag register commands
All breakpoint package commands18

18. Refer to Secured System Control Commands later in this section for information on unlocking the console
keyboard on a secured system.
19. Not allowed on secured systems.

Revision M

DSD Commands 5-67

System Control Command's

Command

Description

UNLOCK.

(Continued)
Always lock the console when the system is being used in a
production environment. However, you can unlock the console
to enter the STEP command if a system failure requiring a
recovery deadstart occurs (refer to Preparing for Recovery
Deadstart in section 2, Deadstart).

UNSTEP.

Clears step mode. This command clears the effect of any
format of STEP command. Unlock the console before entering
this command (refer to the UNLOCK command later in this
section). If the system has set step mode because of a main
power failure or abnormal environmental condition, do not
enter this command until the conditions that caused the
automatic setting have returned to normal.
Refer to Secured System Control Commands later in this
section for information on unlocking the console keyboard on a
secured system.

X.MDD(p)

Initiates the monitor display driver (MDD). MDD is a PP
program and is independent of the operating system. Refer to
the CYBER Initialization Package User's Handbook for more
information.
Parameter

Description

■^^s

p Port number parameter. If you enter 1, the first
port is connected. If you enter 2, the second
port is connected. If you do not specify this
parameter, the second port is connected by
default.
X.name.
or
X.name(parameters)
or
X.name,fl.

Calls a system program or utility specified by name
to an available control point. If parameters are to
be passed to the program, the second form of the command
is used where (parameters)the parameters. In both the
first and second form of the command, the field length
specified in the library for the command is used. If no field
length is specified in the library, a value of 600008 is
assumed. If a field length different from the default is
required, the third form of the command is used. The field
length is specified by fl. Only the first 58 characters following
X. are used.

■^ \

5-68 NOS Version 2 Analysis Handbook

Revision M

System Control Commands

Command

Description

99. Disables or enables syntax overlay processing and logging of
DSD commands in the system dayfile and error log. That is,
depending upon current status, syntax overlay processing and
logging are reversed. When this mode is enabled, 99 appears
on the left screen header.
When syntax overlay processing and logging of DSD commands
is disabled, DSD does not allow you to enter any command
requiring the loading of an overlay from mass storage. Disable
overlay loading only when the system is in an abnormal state
to prevent PPs from being requested when they cannot
perform the necessary tasks (for example, when a system disk
channel is hung). A 99 command that enables logging will be
logged itself, but a 99 command which disables logging will
not be logged.
This command is normally used only for debugging purposes.
When the system is in an abnormal state, the commands that
require entry of the 99 command depend on which syntax
overlays for DSD are in central memory.

Revision

DSD

Commands

5-69

Secured System Control Commands

Secured System Control Commands
The following commands are allowed only on a secured system.
Command

Description

OQSH=level.

Specifies the output queue special handling (OQSH) level on a
secured system. The (OQSH) level is set initially during
deadstart by the OQSH IPRDECK entry. The current OQSH
level appears on the DSD S display. The OQSH command can
be entered at any time from the system console to change the
current level. Output files with an access level greater than or
equal to the OQSH level specified in this command are not
printed but remain in the queue until released by the operator
(refer to the RELEASE command, next). If level is set to the
lowest access level or no level is specified, no files are held in
the queue.

RELEASEjsn.

Allows the operator to release a file from the output queue
whose access level is equal to or above the OQSH level on a
secured system. Output queue files and their access levels can
be examined using the DSD Q display. The output file with
job sequence name jsn is released from the output queue and
is processed by the Batch Input/Output Subsystem. The
RELEASE command can be entered at any time from the
system console. Other restrictions based on device access levels
and file access levels set by your site continue to apply.

SECURES,ot,
LA=lowerlevel,
UA = upperlevel.

Sets the security access level limits for the system
(ot=SY) or the security access level limits for a
particular origin type (ot=IA, BC, or RB). The system limits
determine the range of access levels allowed in the system;
jobs may not execute at an access level outside this range,
and files may not be created or accessed at an access level
outside this range. Origin type limits determine the range as
it applies to jobs of one particular origin type. By default, all
origin type limits are the same as the system limits.
The options available for using this command to change the
system limits (that is, whether they can be raised, lowered, or
both) are controlled by the OPSECM CMRDECK entry (refer
to section 3, Deadstart Decks). The origin type limits for
ot=IA, BC, and RB can be changed to any values within the
system limits. When the system limits are changed (ot=SY),
all origin type limits are reset to the new system limits.
The parameters LA and UA specify the lov/er and upper
access level limits. Both parameters must be specified. The
value corresponding to the lower access level must be less
than or equal to the value corresponding to the upper access
level.

5-70 NOS Version 2 Analysis Handbook

Revision M

Secured System Control Commands

Command

Description

UNLOCK,username,
password.

Unlocks the console keyboard for special commands when
the system is running in secured mode. When this command is
entered, the message SECURITY UNLOCK appears in the
header on the left screen display. If the system is running in
secured mode, the following commands are restricted to entry
only when the console is in security unlock status.

y^^^s

DATE.yy/mm/dd.
X.DDF.
DEBUG.
DISJsn.
ENABLE,ENGR.
QDSPLAYJsn.
SECURES,ot,LA=lowerlevel,UA=upperlevel.
SECUREQ,est,LA = lowerlevel,UA = upperlevel.
TIME.hh.mm.ss.
All memory entry commands.
y^$s

All PP breakpoint commands.
All CPUMTR breakpoint commands.
In addition, the memory displays are partially disabled on a
secured system unless the console is in security unlock status.
If you attempt to display anything outside of the system
tables, a memory display shows the following message instead
of the contents of the memory locations.
****SECURED AREA****

Revision M

DSD Commands 5-71

Memory Entry Commands

Memory Entry Commands
The following commands are used to change the contents of central memory and
extended memory. Either absolute locations or those relative to a specific job's
reference address (RA) can be changed.
CAUTION
Use these commands with extreme caution to avoid damage to the system or to user
jobs.
Before entering these commands you must unlock the console keyboard (refer to the
UNLOCK command earlier in this section). On a secured system, the console must be
in security unlock status. To change central memory, you must bring a central memory
display (C, D, F, or G) to the left screen. To change extended memory, you must bring
the M display to the left screen. It is this display that controls whether the memory
entry commands change absolute memory locations or relative memory locations.
For example, if you enter
C,.

to bring up the C display, any memory entry commands entered make changes to
absolute memory locations. If you enter
C.jsn.

where jsn is a valid job sequence name, any memory entry commands entered make ■'***%
changes to memory locations relative to the job's RA.
Character values or numeric data can replace the current word contents. Either one
12-bit byte or a 60-bit word can be changed. A single byte can be changed by
inserting the byte number after the location; bytes are numbered 0 through 4 from
left to right. The address and contents are assembled right-justified with zeros filling
unused leading positions. Leading zeros may be omitted in the entry.
When you are changing the contents of memory relative to a specific job (a valid job
sequence name was specified when the memory display was brought to the left ""^
screen), the negative field length area of the job can be accessed. This area is
accessed by specifying a negative address in the memory entry command. For
example, to change the contents of word RA-3, you enter the address 77777775s.
On an unsecured system when you are changing a memory location relative to a
specific job's RA, the system checks for field length violations. If you specify an
address larger than your job's RA plus field length, you cannot change its contents.
On a secured system no memory entry commands are allowed unless the security
unlock status is set. The memory display shows the message
♦••"SECURED AREA****

instead of the contents of the memory locations to prevent you from examining these
locations; you may not alter the contents of these locations. When you are displaying
absolute memory you can see only the system tables.

/**S\

5-72

NOS

Version

Analysis

Handbook

Revision

Memory Entry Commands

Formats and descriptions for these commands are:
Command

Description

addr,cont.
or
addr+cont.20

Changes the contents of central memory location addr
(maximum of eight digits) tc cont (maximum of 20
digits). The second form of the command performs essentially
the same function but is used when it is necessary to change
successive memory locations.

addr,b,cont.
or
20
addr+b,cont.

Changes the contents of byte b at central memory location
addr (maximum of eight digits) to cont. Each location
consists of five 12-bit bytes, numbered 0 through 4 from left
to right. The contents are four octal characters. The second
form of the command performs essentially the same function
but is used when it is necessary to change successive memory
locations.

addr,Dcont.
or
addr+Dcont.20

Changes the contents of central memory location addr
(maximum of eight digits) to display code characters cont
(left-justified and zero-filled). The second form of the command
performs essentially the same function but is used when it is
necessary to change successive memory locations.

Eaddr,c.ont.
or
Eaddr + cont.20

Changes the contents of extended memory location addr
(maximum of seven digits) to cont (maximum of 20 digits).
The second form of the command performs essentially the
same function but is used when it is necessary to change
successive extended memory locations.

Eaddr,b,cont.
or
Eaddr+ b,cont. 20

Changes the contents of byte b at extended memory location
addr (maximum of seven digits) to cont. Each location
consists of five 12-bit bytes, numbered 0 through 4 from left
to right. The contents are four octal characters. The second
form of the command performs essentially the same function
but is used when it is necessary to change successive extended
memory locations.

Eaddr,Dcont.
or
Eaddr+ Dcont.20

Changes the contents of extended memory location addr
(maximum of seven digits) to display code characters
cont (left-justified and zero-filled). The second form of the
command performs essentially the same function but is used
when it is necessary to change successive extended memory
locations.

20. If the + sign is specified, the address is incremented by one location (addr + 1) after the initial entry is
processed; the - sign causes the address to be decremented by one location (addr-1). This allows immediate
entry for the next (or previous) memory location. If the message REPEAT ENTRY is displayed above the
entry, the cont field is not cleared and can be entered in successive memory locations as many times as
desired.

Revision M

DSD Commands 5-73

Channel Control Commands

Channel Control Commands
The following commands enable control activity on a specified data channel in
circumstances where abnormal hardware and/or system operation is detected. Extreme
caution must be exercised if any of these commands are entered during normal system
operation. In addition, the console keyboard must be unlocked before entry of any of
these commands is permitted (refer to the UNLOCK command earlier in this section).
DSD does not reserve the channel specified in any of the channel control commands.
The channels are numbered 0 to 13s in a 10 PP system and 0 to 13s, 20s to 33s in a
20 PP system.
CAUTION
Extreme caution must be exercised when using the following channel control
commands.
Command

Description

ACN,cc.

Activates channel cc. This command alerts and prepares
peripheral equipment on channel cc for the exchange of data.

DCH,cc.

Drops channel cc. This is a software function to release the
current reservation of channel cc.

DCN,cc.

Deactivates channel cc. As a result, peripheral equipment on
channel cc stops and any current I/O operation is terminated.

FCN,cc,func.

Outputs a function code func to channel cc. This releases all
equipment selections on that channel. If func is not specified,
a zero function code (no activity) is output.

IAN,cc.

Inputs data to the pseudo A register from channel cc.

LDC,nnnn.

Loads the pseudo A register with nnnn (normally a
peripheral equipment function code). The current value of
nnnn is shown in the channel status display (W,C).

MCH,cc.

Master clears and removes all 3000 Computer Systems
peripheral equipment selections on channel cc (6681 function
code 17008 is issued).

OAN,cc.

Outputs the contents of the pseudo A register to channel cc.

5-74 NOS Version 2 Analysis Handbook

Revision M

Extended Memory Flag Register Commands

Extended Memory Flag Register Commands
The extended memory flag register commands are used to set or clear specific bits in
the extended memory flag register. These commands are typically used when debugging
a problem in a multimainframe environment. The console must be unlocked (refer to
the UNLOCK command earlier in this section).
CAUTION
Extreme caution must be exercised when using these commands.
Command

Description

CFR,bb. Clears the extended memory flag register bit bb
(0 ^ bb ^ 17).
jpv

SFR,bb. Sets the extended memory flag register bit bb
^
bb
^
17).

Breakpoint Package Commands
The breakpoint package consists of a set of DSD commands that controls PP breakpoint
processing and CPUMTR breakpoint processing.

PP Breakpoint Commands
y^\ The following DSD commands control PP breakpoint processing. These commands and
V the DSD V display enable you to communicate with the PP breakpoint package. The V
display is described following the command descriptions. The PP breakpoint commands
require that the system console be unlocked (refer to the UNLOCK command earlier in
this section); on a secured system, the console must be in security unlock status.
CAUTION
Use these commands with extreme caution to avoid damage to the system or to user
jobs. Incorrect usage may cause a system to hang up and require a deadstart.
NOTE
Breakpoint can be set for only one PP program at a time. Before setting breakpoint
for another program, it must be cleared on the first program.

0$m\

00!&\

Revision

DSD

Commands

5-75

PP Breakpoint Commands

Command

Description

| BKP.

Clears an existing PP breakpoint.

| BKP,prog,cp.

Sets breakpoint for PP program prog at control point cp. The
control point parameter cp is optional. The PP program prog
can be any PP program or overlay except the following:
• PPR overlays (1DD, OSE, etc.).
• Mass storage drivers.
• Mass storage error processors.
• Any PP program that overwrites PP memory greater than
75008 with instructions or data. The breakpoint program
uses PP memory locations 75008 to 77778. If the PP
program is allowed to modify those locations on load,
execution, or overlay load, unpredictable results may occur.
Refer to the PP breakpoint precautions in the following
section.
• Concurrent (16-bit) PP programs.
The PP program need not be a main program, and it can
reside in central memory, disk, or extended memory
(ECS/ESM/UEM).

| PPnn.A,val.

Sets the A register to the value val for PP number nn. Up to
18 bits can be specified for the value parameter val.

I PPnn.C,addr.

Causes the V display for PP number nn to display 100s bytes
of PP memory, starting at base address addr, as the C block.

| PPnn.C,addr,val.

Changes the contents of PP memory word addr for PP number
nn to value val. The specified address must point to one of the
PP memory words displayed in the C block of the V display.

| PPnn.D,addr.

Causes the V display for PP number nn to display 1008 bytes
of PP memory, starting at base address addr, as the D block.

| PPnn.D,addr,val.

Changes the contents of PP memory word addr for PP number
nn to value val. The specified address must point to one of the
PP memory words displayed in the D block of the V display.

§ PPnn.EXR.

Resumes execution in PP number nn with a breakpoint set in
the PP-resident subroutine EXR (after the next overlay load
completes, but before execution of the overlay begins).

I PPnn.FTN.

Resumes execution in PP number nn with a breakpoint set in
the PP-resident subroutine FTN + 1 (to trap the next monitor
function before it is issued to MTR/CPUMTR).

5-76 NOS Version 2 Analysis Handbook

Revision M

^<«S5sV

V Display

Command

Description

PPnn.G.

Resumes normal PP program execution for PP number nn
with no breakpoint set.

PPnn.G,addr.

Resumes PP program execution for PP number nn with a
breakpoint set at address addr. The address addr must be
within executable code and lie on a PP instruction boundary,
but the validity of the address is not checked.

PPnn.P,addr.

Resets the P register to address addr for PP number nn.
When the PP program resumes execution, it will start at
P = addr.

PPnn.S.

Steps the PP program one instruction for PP number nn.
Indexed jump instructions, channel jump instructions, and
instructions that jump to the current program address or
current program address minus one cannot be stepped. If you
try to step these instructions, the following message appears
on the system console:
CAN-T STEP.

PPnn.SX.

Steps the PP program one instruction for PP number nn. This
command performs the same function as the PPnn.S. command
except that if an RJM instruction is encountered, a breakpoint
is set to the instruction after the RJM and the entire
subroutine is executed.

V,nn.

Brings up the DSD V display for PP number nn.

V,HNG.

Brings up the DSD V display for a hung PP.

V,PS.

Brings up the DSD V display for the pseudo PP.

00^S

V Display
0&%S

The DSD V display complements the PP breakpoint commands to provide an analyst's
tool for PP breakpoint processing. The information displayed is for the PP number
specified in the V,nn command. Figure 5-4 shows the format of the V display. The
display shows the PP communications area for the specified PP (10s CM words), the
contents of the P and A registers, and two 1008 word blocks of PP memory (C and D).
The base addresses of the C and D blocks are set by PPnn.C,addr and PPnn.D,addr
commands.
If the specified PP is not at breakpoint when the V display is brought up, the display
shows only the communications area and the following message:
NOT AT BREAK.

Revision M

DSD Commands 5-77

V Display

V,nn

PP BREAKPOINT.

7420

0310 1702 oooo 0000 1234
0000 0001 OOOO OOOO OOOO

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
C

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

= 0460
A = 220346

(1100)
(1110)
(1120)
(1130)
(1140)
(1150)
(1160)
(1170)

0200 2754 2000 3465 5400 3472 1006 3401

(0000)
(0010)
(0020)
(0030)
(0040)
(0050)
(0060)
(0070)

oooo

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

0002 0056 4567
OOOO 0001 0000 OOOO

oooo
oooo

0003 4157 0234
OOOO oooo oooo

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

y^*feav

xxxx
xxxx
xxxx
xxxx
xxxx
xxxx

Figure 5-4. PP Breakpoint V Display

-*^\

5-78 NOS Version 2 Analysis Handbook

Revision M

PP Breakpoint Precautions

PP Breakpoint Precautions
The following precautions and information are important to the successful use of the
PP breakpoint package.
• The breakpoint must be set in executable code and must lie on a PP instruction
boundary.
• When a breakpoint is set, two words of PP memory are replaced with the
following:
RJM BKP

When the breakpoint is hit, the two replaced words are immediately restored.
However, 16-bit instructions are not restored properly since they revert to 12-bit
instructions.
• The PP breakpoint package uses PP locations 7500s through 7777s. If these
locations are altered by the running PP, the system will probably fail.
• If the PP program being breakpointed encounters a mass storage error, the mass
storage driver's error processor will overlay the PP breakpoint code, and will
probably crash the operating system.
• If the PP program being breakpointed performs code modification on the
instruction at the address at which the breakpoint has been set, unpredictable
results may occur.
• The PP breakpoint package cannot be used on DIS or 026. However, it can be
used on other PPs at the same control point as DIS or 026.
• The PP breakpoint information (BKP,prog) remains set until BKP is entered or a
SYSEDIT or any level of deadstart is performed.

Revision

DSD

Commands

5-79

CPUMTR Breakpoint Commands

CPUMTR Breakpoint Commands
The following DSD commands control CPUMTR breakpoint processing. These commands
and the DSD C display enable you to communicate with the CPUMTR breakpoint
package. The C display is described following the command descriptions. The CPUMTR
breakpoint commands require that the system console be unlocked (refer to the
UNLOCK command earlier in this section); on a secured system, the console must be
in security unlock status.
CAUTION
Use these commands with extreme caution to avoid damage to the system or to user
jobs. Incorrect usage may cause a system to hang up and require a deadstart.
NOTE
Only one CPUMTR breakpoint can be set at a time. Any existing breakpoint is
cleared when you enter a CPB,BKP,... command.
Command

Description

CPB,BKP,addr.

Sets breakpoint at absolute address addr. Restarts execution,
if the CPU is waiting for a GO.

CPB,BKPy/addr.

Sets breakpoint at CPUMTR relative address addr. Restarts
execution, if the CPU is waiting for a GO.

CPB,BKP,/bbbb/addr.

Sets breakpoint at address addr in CPUMTR block bbbb.
Restarts execution, if the CPU is waiting for a GO.

CPB,DSP.

Brings up the CPUMTR breakpoint variant of the C display
on the left screen if the C display is not already active.
Causes the memory block in the C display to begin at the
breakpoint address.

CPB,DSP,addr.

Brings up the CPUMTR breakpoint variant of the C display
on the left screen if the C display is not already active.
Causes the memory block in the C display to begin at
absolute address addr.

CPB,DSP,//addr.

Brings up the CPUMTR breakpoint variant of the C display
on the left screen if the C display is not already active.
Causes the memory block in the C display to begin at
CPUMTR relative address addr.

CPB,DSP,/bbbb/addr.

Brings up the CPUMTR breakpoint variant of the C display
on the left screen if the C display is not already active.
Causes the memory block in the C display to begin at
address addr in CPUMTR block bbbb.

CPB,DSP +

Brings up the CPUMTR breakpoint variant of the C display
on the left screen if the C display is not already active.
Advances each of the memory block addresses by 10s.

CPB,DSP-

Brings up the CPUMTR breakpoint variant of the C display
on the left screen if the C display is not already active.
Decrements each of the memory block addresses by 10s.

5-80 NOS Version 2 Analysis Handbook

Revision M

^^5\

CPUMTR Breakpoint Display (C Display)

Command

Description

CPB,GO. Clears any breakpoint that is set and allows CPUMTR to
restore its registers and continue execution.
CPB,P+ Sets breakpoint at the address following the current
breakpoint address and restarts execution, if the CPU is
waiting for a GO.
CPB,P- Sets breakpoint at the address preceding the current
breakpoint address and restarts execution, if the CPU is
waiting for a GO.
CPUMTR Breakpoint Display (C Display)
The CPUMTR breakpoint display is a variant of the DSD C display that is formatted
for use in CPUMTR breakpoint processing. This display is initiated by entering one of
the CPB,DSP commands. Figure 5-5 shows the format of the CPUMTR breakpoint
display. The display consists of the 208-word exchange package from the current or last
breakpoint (displayed in 5 groups of 4 octal digits per line). All exchange package
information is displayed except RA, FL, RAE, FLE, and MA. The P address shown is
the actual breakpoint address.
The exchange package is followed by two 108-word blocks of central memory
(displayed in 4 groups of 5 octal digits per line). The address of the memory block to
be displayed can be specified using one of the CPB,DSP commands. Even if the
address specified in the CPB,DSP command is a relative address, the addresses shown
in the display are absolute; thus, giving the actual location in memory of the
displayed data.

0$m\

Revision

DSD

Commands

5-81

CPUMTR Breakpoint Display (C Display)

C. CENTRAL MEMORY.

00062662
00062663
00062664
00062665
00062666
00062667
00062670
00062671

54726
1
0
0
106
1
0 55730 75230
0
43
55713
0
55731
4
0
1022
0
0 54533 55676
0
43
7200

00062672
00062673
00062674
00062675
00062676
00062677
00062700
00062701

7777 7777 7777 7777 0000
0000 0000 0000 0000 0003
3423 1200 0000 0000 0000
0000 0000 0000 0000 0001
OOOO OOOO OOOO OOOO 0003
OOOO OOOO 0002 OOOO oooo
3423 1200 0002 OOOO OOOO
4000 0002 0001 0040 0344

Exchange
Package

1SJ

1SJ B
5 B A 5C9

00054726
00054727
00054730
00054731
00054732
00054733
00054734
00054735

51200
11232
03330
43724
02000
10322
76770
20251

00052
51300
54777
20760
64037
43405
20451
12667

43324
00111
61000
51700
61000
51200
20735
11242

20360
20303
46000
55010
46000
00057
15664
43422

(P )8Z7C
ISUK IJCC
COE* D
8 7G ( E/H
B F54 D
HZT1E(P .
BD(P (.
PUIV ITT1R

00054736
00054737
00054740
00054741
00054742
00054743
00054744
00054745

13227
03030
61600
51200
21244
03010
20352
04000

03020
54777
54746
00144
73110
55735
15114
71362

54776
61000
07410
51140
03020
43301
36713
61000

46000
46000
55735
55010
54776
53110
15773
46000

KR XP=
CCE* D
E*-G6E.2
(P A9(LE/H
QT*YHCBE*
CAE.28XMYH
P2Q(L3 Y.
D GK D

,^ms

Memory
Block

Figure 5-5. CPUMTR Breakpoint Display

5-82 NOS Version 2 Analysis Handbook

Revision M

CPUMTR Breakpoint Precautions
j|^V

CPUMTR Breakpoint Precautions
The following precautions and information are important to the successful use of the
CPUMTR breakpoint package.
• The breakpoint must be set in executable code.
© When a breakpoint is set, DSD stores RJ BKP at the specified address. When the
breakpoint address is hit, CPUMTR saves all of the registers in the display area,
clears the breakpoint, and then waits to receive a GO. The message CPUMTR
BREAKPOINT HIT is displayed at the system control point.
a From the time that the breakpoint is hit until the CPU continues, the system
clock stops. Therefore, you should reset the system clock (with the DSD TIME
command) after you have finished breakpoint processing.
© A CPUMTR breakpoint can be set in monitor mode or program mode. However,
alternating between the modes is not advised. Going from monitor to program
mode is probably safe, but going from program to monitor mode is almost certain
to fail causing CPUMTR to abort with the following message issued to the system
console:
CPUMTR ERROR EXIT.

« Since the C display is resident in RPL, changing displays is allowed (before the
breakpoint is hit) because you can always return to the C display. However, once
the breakpoint is hit until the CPU continues, CPUMTR is hung. This means that
all activity in the system stops until the CPU restarts. If DSD attempts to
request a monitor function, the following message appears in the B display:
NO MONITOR RESPONSE.

This is normal since CPUMTR is hung in the breakpoint code and the message
may be ignored. In this case, the DSD request that required the monitor function
is not processed.
• If you attempt to reference a CPUMTR block that is not loaded, the following
message appears on the system console:
INCORRECT ENTRY.

• The C display retains the last addresses displayed. For example, if you change to
another display and then come back to the C display it will still show the same
absolute addresses.
• Once a breakpoint has been hit and CPUMTR is waiting for a CPB,GO (or
another CPB,BKP) command, the contents of any register or memory location can
be changed by using the normal memory entry commands. To change a register,
simply change the corresponding memory location on the C display (as initiated by
the CPB,DSP command). The exchange package shown on the C display will be
reloaded to display the actual registers when execution resumes.
NOTE
Since CPUMTR has been halted, any memory entries made at this time must be
preceded by a 99 command to disable DSD syntax overlay processing and the
logging of the command to the error log.

Revision

DSD

Commands

5-83

Debugging Commands

Debugging Commands
The following commands trap certain conditions and at the same time trace selected PP
and MTR to CPUMTR functions.
TRACE
TRAP
These debugging commands can be used to solve specific system problems. Care must
be exercised in using the commands in a production environment as performance may
be impacted significantly.
The following entry must be made in the IPRDECK at deadstart.
ENABLE.TRACE.

In addition, system debug mode must be enabled at the system console (the console
must be unlocked to do this) in order to execute the TRAP and TRACE commands.
Command

Description

TRACE.type, Permits specification of monitor functions and other system
parameters. data. Entering the command without any parameters
(TRACE,PPU. or TRACE,MTR.) clears the trace function.
The following types may be traced.
type

Description

PPU Traces PP to CPUMTR requests. Each trace
buffer entry consists of the following words:
• Time stamp.
• PP input register.
• PP output register.
• PP message buffer (6 words).
• Absolute address 1 (default is SMRL).
• Absolute address 2 (default is CMCL).
The format of the time stamp word is
•••dhmslll

In this format, dhms is bits 23-0 (day, hour,
minute, and second) of PDTL and 111 is bits
17-0 of RTCL.
The trace buffer can hold 20 entries. The
oldest entry in the buffer is overwritten by a
new entry once the buffer is filled. The DSDI
directive TBDUMP,PPU displays the buffer, as
well as the functions traced, the absolute
addresses saved, and the buffer IN pointer.

5-84

NOS

Version

Analysis

Handbook

Revision

^ ^ 5 V

Debugging Commands

Command

Description

TRACE,type,
parameter.

(Continued)
type

Description

MTR

Traces MTR to CPUMTR functions. Each trace
buffer entry consists of the following words:
Time stamp.
Function.
Absolute address 1 (default is SMRL).
Absolute address 2 (default is CMCL).
*MCT*

00S.

MCT* expands to the following for each entry
in the memory control table (MCT):
MCT word 1.
MCT word 2.
CPA/PCPA address 1 (default is STSW).
CPA/PCPA address 2 (default is FLSW).
Word TFSW from the CPA/PCPA.
Word JSNE from the EJT.
Depending on the number of pseudo-control
points defined, there is room for approximately
10 entries in the trace buffer. The oldest entry
in the buffer is overwritten by a new entry
once the buffer is filled.
The DSDI directive TBDUMP,MTR displays the
buffer, as well as the functions traced, the
absolute and CPA/PCPA addresses saved, and
the buffer IN pointer.
SET,ABS

Sets the absolute addresses of the CM words to
be saved in the trace buffer entry.

SET,CPA

Sets the CPA/PCPA addresses of the CM words
to be saved in the trace buffer entry.

yHflmm&y

Revision M

DSD Commands 5-85

Debugging Commands

I Command

Description

I TRACE,type,
| parameters.

(Continued)
The following parameters are used with TRACE,MTR and
TRACE,PPU. Trace data is collected by CPUMTR immediately
before the selected function is processed.
parameters Description
* Tr a c e s a l l f u n c t i o n s o f t h e s e l e c t e d t y p e .
Fi,F2,...,F3 Traces up to five functions. Functions are
specified by their symbolic names.
The following parameters are used with TRACE,SET,ABS and
TRACE,SET,CPA.
parameters Description

.^S^y

addri,addr2 Sets the absolute (TRACE,SET,ABS) or relative
(TRACE,SET,CPA) addresses of the words to be
saved in each trace buffer entry. The addresses
must be octal digits.
The following examples illustrate various forms of the TRACE
command.
Example

Description

TRACE, PPU, ROCM, j ACM. Causes a trace entry to be created each
time a JACM or ROCM monitor function
is issued.
TRACE,MTR,ACSF.

Causes a trace entry to be created each
time an ACSF function is issued.

TRACE,SET,ABS,21,152. Causes words 21s and 152s to be saved in
each trace buffer entry.
/*^™^*K

TRACE, SET, CP A, 21,57. Causes words 21s and 57s of each CPA and
PCPA to be saved for each MTR trace
buffer entry.

><5^v

5-86 NOS Version 2 Analysis Handbook

Revision M

Debugging Commands

Command

Description

TRAP,type,parameters. Halts the system immediately (in monitor mode) upon
detection of a specified condition. Only one type of trap can be
active at once. Entering the command without any parameters
(TRAP.) clears the trap.
The following types do not accept parameters.
type

Description

NFL Checks for erroneous data in negative field
length of executing jobs.
MCT Checks for invalid data in the memory control
table.
EJT Checks for invalid data in the executing job
table.
DJB Checks for jobs that are no longer executing,
but are failing to advance.
The following types accept parameters.
type

Description

CPA Checks a specified control point area field or
pseudo-control point area field for a given
value.

jHv&tizis

MEM Checks a field specified by an absolute address
(central memory only) for a given value.
The following parameters, which are associated with CPA amd
MEM, indicate the field and value being checked.
parameters Description
W Absolute address (type = MEM) or offset
(type = CPA).
V Va l u e ( o c t a l ) . I f V = N , a n y n o n z e r o fi e l d v a l u e
halts the system.
H L e f t - m o s t b i t o f fi e l d . D e c i m a l v a l u e r a n g e s
from 0 to 59.8
L R i g h t - m o s t b i t o f fi e l d . D e c i m a l v a l u e r a n g e s
from 0 to 59.

Revision

DSD

Commands

5-87

Debugging Commands

Command

Description

| TRAP,type,parameters. (Continued)
The following examples illustrate various forms of the TRAP
command.
Example

Description

T R A P, C PA , 2 0 , N , 4 7 , 3 6 . C h e c k s f o r a n y n o n z e r o
value in bits 47 to 36 of
word 20 in each control
point area.
TRAP,MEM,37461,36,7,3 Checks for a value of 36 in
bits 7 to 3 of 37461.

5-88

NOS

Version

Analysis

Handbook

Revision

(* Express Deadstart Dump Interpreter
(DSDI)
Calling the Express Deadstart Dump Interpreter 6-3

f^'

Input
Directives
6-6
Directive
Format
6-7
List
Control
Directives
6-8
EJ
—
Force
Page
Eject
6-8
EJOFF
—
Turn
Off
Auto
Page
Eject
6-8
EJON
—
Turn
On
Auto
Page
Eject
6-8
PD
—
Reset
Print
Line
Density
.
6-8
*.
—
Comment
in
Subtitle
Line
.
6-9
File Manipulation and Control Directives 6-10
DISPOSE — Dispose Alternate List File to Print Queue 6-10
OUTPUT — Assign Output to Alternate List File 6-10
R E A D — R e a d A l t e r n a t e D i r e c t i v e s F i l e 6 - 11
REWIND
—
Rewind
File
6 - 11
Central Memory/Extended Memory Dump Directives 6-12
Dump
Control
Directives
6-12
ALLMEM — Extend Central Memory Dumps 6-12
CM — Set Memory Type to Central Memory 6-12
E C — S e t M e m o r y Ty p e t o E x t e n d e d M e m o r y • 6 - 1 3
RA
—
Reset
Reference
Address
6-13
RAC — Reset Reference Address to RA of Control Point 6-14
. UEC — Set Memory Type to User-Access Extended Memory f>14
Memory
Dump
Directives
...
.
6-15
C — Dump Memory in Instruction Parcel Format . 6-15
D
—
Dump
Memory
in
Byte
Format
6-16
E
—
Dump
Memory
in
Word
Format
6-16
I — Dump 64-Bit Memory in Instruction Parcel Format 6-17
W — Dump 64-Bit Memory in Word Format 6-18
PP
Dump
Directives
6-19
AP — Dump Analysis of PP and PP Memory in Octal Line Format . 6-19
MPP
—
Move
PP
6-20
P — Dump PP Memory in Octal Block Format 6-20
P F. — D u m p F L P P M e m o r y i n O c t a l B l o c k F o r m a t 6 - 2 1
PMS
—
Read
PP
Select
Switches
6-21
PO — Dump 16-Bit PP Memory in Octal Block Format 6-22
PX — Dump 16-Bit PP Memory in Hexadecimal Block Format 6-22
Q — Dump PP Memory in Octal Line Format 6-23
QF — Dump FLPP Memory in Octal Line Format 6-23
QOA — Dump 16-Bit PP Memory in Octal/ASCII Line Format 6-24
QOD — Dump 16-Bit PP Memory in Octal/Display Line Format 6-24
QXA — Dump 16-Bit PP Memory in Hexadecimal/ASCII Line Format 6-25
QXD — Dump 16-Bit PP Memory in Hexadecimal/Display Line Format 6-25
CMR
Dump
Directives
6-26
ACCOUNT — Dump Account Dayfile Buffer 6-26
CBT
—
Dump
Control
Buffer
Ta b l e
6-27
CCT
—
Dump
Channel
Control
Ta b l e
6-27
CP — Dump Active Control Point Areas 6-28
CPO
—
Reset
Default
list
Options
6-30
CT
—
Dump
Channel
Ta b l e s
6-30
D AY F I L E — D u m p S y s t e m D a y f i l e B u ff e r 6 - 3 0
DB
—
Dump
Disk
Buffers
6-30

DBW — Dump Buffered Device/Buffer Statistics/PP-I/O Buffer Link Tables .. 6-31
DDB
—
Dump
Dayfile
Dump
Buffer
6-31
DP
—
Dump
Dayfile
Buffer
Pointers
6-31
EICB — Dump Environment Interface Communication Buffer 6-31
EJT
—
Dump
Executing
Job
Ta b l e
....
6-31
EPB
—
Dump
Extended
Memdry/PP
Buffer
6-32
ERRLOG
—
Dump
Error
Log
Buffer
.....
6-32
EST
—
Dump
Equipment
Status
Ta b l e
6-32
F N T — - D u m p S y s t e m F i l e N a m e / F i l e S t a t u s Ta b l e . . . . 6 - 3 2
FOT
—
Dump
Family
Ordinal
Ta b l e
6-32
H AT —
Dump
Hash
Ta b l e
6-33
JC — Dump Job Control Area for Each Service Class 6-33
LC—
Dump
Low
Central
Memory
.......
6-33
LDIS
—
Dump
L-Display
Buffer
6-34
LIDT
—
Dump
Logical
Identifier
Ta b l e
6-34
MAINLOG — Dump Binary Maintenance Log Buffer 6-34
M C T — D u m p M e m o r y C o n t r o l Ta b l e . . . . . 6 - 3 4
M S T — D u m p M a s s S t o r a g e / T r a c k R e s e r v a t i o n Ta b l e s 6 - 3 5
MTR
—
Dump
CPU
Monitor
.
.....
6-35
MTRQUEUE — Dump CPUMTR Request and Recall Queues . 6-36
ODIS
—
Dump
Operator
Display
Buffer
6-36
PCP
—
Dump
Pseudo-control
Point
...
6-36
PLD' — Dump Peripheral Library Directory ..... 6-37
PP
—
Dump
PP
Communication
Areas
6-37
PROBE
—
Dump
PROBE
Data
Ta b l e s
6-37
PST— Dump Program Status Table and Entry Point Directory .... 6-37
PUT
—
Dump
Physical
Unit
Ta b l e
6-38
Q F T — D u m p Q u e u e d F i l e Ta b l e . . . . . . . . - . . . 6 - 3 8
RCL
—
Dump
Resident
Central
Library
6-38
RPL
—
Dump
Resident
Peripheral
Library
6-39
SAB
—
Dump
System
Attribute
Block
...
6-39
SDA — Dump Extended Statistical Data Area .......;.. 6-39
SECDED — Dump SECDED Identifier Table................................ 6-39
SST — Dump Subsystem Control Point/Subsystem Assignment Tables 6-40
TBDUMP
—
Dump
Trace
Buffer
.....
6-40
Subsystem
Dump/Analysis
Directives
....
6-41
B AT C H I O ( B I O ) — D u m p A s s o c i a t e d M e m o r y f o r A n a l y s i s 6 - 4 1
IAF — Dump Associated Memory for Analysis ...... 6-42
MAGNET (MAG) — Dump Associated Memory for Analysis 6-44
RHF — Dump Associated Memory for Analysis .... 6-45
Hardware
Register
Dump
Directives
6-46
FMFREG
■—
Dump
PP
Registers
.
6-46
IOUCR — Dump Concurrent PP Channel Registers .. ... . 6-46
IOUMR — Dump IOU Maintenance Registers . .,..• 6-46
L P VA — L o a d C e n t r a l M e m o r y P VA i n t o P s e u d o R e g i s t e r 6 - 4 7
MEMMR — Dump Memory Maintenance Registers 6-47
PROCA — Dump Processor Operand Cache 6-48
PROCW — Dump Processor Controlware Part Number and Revision Level... 6-48
PROMR — Dump Processor Maintenance Registers .. 6-48
PROPM
—
Dump
Processor
Page
Map
.
6-49
PRORF — Dump Processor Register File .... ...., ..."... 6-49
PROSM—
Dump
Processor
Segment
Map
6-49
PROXP — Dump Processor Exchange Package 6-50
SC
—
Dump
S/C
Register
6-50
SETCPU—
Set
CPU
Number
6-50
SETIOU
—
Set
PP
Dump
Defaults
6-51
SETJPS—
Change
the
JPS
Register
Va l u e

6-51

)

^*%

SETRMA —
Convert Address
into
RMA
SETVEP — Set Virtual Address Parameters
T R A C E B K — Tr a c e b a c k S t a c k F r a m e S a v e A r e a .
XP - Dump Deadstart Exchange Package
Buffer
Controller
Directive

6-52
6-52
6-53
6-53
6-54

Interactive
Use
of
DSDI
"6-55
Te r m i n a l
Output
Directives
6-57
C — Dump Memory in Instruction Parcel Format 6-57
CP — Dump Active Control Point Areas 6-58
D
—
Dump
Memory
in
Byte
Format
6-59
PP
—
Dump
PP
Communication
Areas
6-60
Q — Dump PP Memory in Line Format 6-61
QOA, QOD, QXA, QXD •— Dump 16-Bit PP Memory in Line Format 6-62
Example
of
DSDI
Te r m i n a l
Use
6-63
Printer

/p*

(P*

j ^ v

Output

Listing

Examples

6-65

^f Express Deadstart
( D SDump
D I ) Interpreter

The deadstart dump interpreter (DSDI) is a utility program that converts selected
portions of the binary information on an express deadstart dump (EDD) file into reports
to be listed. The EDD file is generated on magnetic tape by the EDD utility, which
may be run at deadstart time after a system malfunction has occurred. Refer to the
CIP User's Handbook for complete information concerning the use of EDD.
Selection of data to be listed by DSDI is provided through input directives, either on
an input file or on the DSDI command. Normal octal dumps of central memory,
extended memory, and PP memory can be produced by these directives as well as
specially formatted dumps of specific system tables and buffers.
EDD and DSDI offer these features:
® The EDD tape file contains a dump of memory, the executing exchange packages,
the CYBER 170 status and control (S/C) registers, where applicable; maintenance
registers for models 865 and 875 and CYBER 180-class machines, register file,
exchange package, processor control store, processor operand cache, processor page
map, processor segment map, where applicable; and all PPs except for PPO, which
can be saved by either copying it to another PP or by biasing the PP switch on
the deadstart panel. EDD can optionally dump all or part of extended memory and
the selected buffer controllers. EDD and DSDI permit analysis of a system
malfunction to be performed entirely offline.
• Because DSDI copies the EDD file to a word-addressable random file on mass
storage, dump data can be accessed in any order.
• EDD requires only a small amount of time during deadstart because the data is
transferred in binary form to magnetic tape.
© The tape file created by EDD can be retained on magnetic tape or mass storage
until it is no longer needed. Thus, a selective listing can be generated at any
time.
y™srw?v

General information from the EDD file appears in the title and subtitle line of
each page of listed output. The first 50 columns of each input directive are
included in the title line of the output list it produces. An input directive is
provided that enables insertion of comments into the subtitle line.
Use of DSDI is possible from an interactive terminal as well as from the batch
environment. The output produced by several directives is formatted for terminal
output (72 columns). From a batch environment, output is formatted for a
136-column printer.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-1

Express Deadstart Dump Interpreter (DSDI)

DSDI can also be used to create a message file containing the contents of the
maintenance registers (input/output unit, memory, and processor) that were dumped to
the EDD file for CYBER 180-class machines. This message file, which is similar in
format to the binary maintenance log (BML), can then be analyzed by an interpreter
progam, such as the Hardware Performance Analyzer (HPA), to produce maintenance
register reports. Refer to the IOUMR, MEMMR, and PROMR DSDI input directives
later in this section for additional information.
DSDI writes up to three messages to this message file: one message each for
input/output unit errors, memory errors, and processor errors. If the status summary
register for a particular element is zero (signifying no errors for that element), DSDI
does not write the corresponding message to the message file.
In addition, the message file contains messages for any errors that were detected by
the dedicated fault tolerance (DFT) processor but not yet written to the BML at the
time the EDD file was created. These messages are identical in format to the ones that
would have been written to the BML by the normal logging process.

J^MW^V

6-2 NOS Version 2 Analysis Handbook

Revision M

Calling the Express Deadstart Dump Interpreter

/0m»._

Calling the Express Deadstart Dump Interpreter
Processing of the EDD file is initiated with the DSDI command. The format of the
command is:
DSDI,plFp2 pn.

Each parameter pi is either a keyword or a keyword equated to a value. All
parameters are optional and order independent.
Pi

Description

B=bmlfile

The 1- to 7-character name of the message file on which the
maintenance register messages and unlogged DFT error
messages are to be written. The message file is similar in
format to the BML and can be analyzed by HPA. This
parameter is valid only if maintenance register messages or
unlogged DFT error messages have been dumped to the EDD
file.

B omitted

No message file is to be created.

This parameter creates a random dump file with the same name
as the EDD file and returns the original EDD file. The created
file can then be used as the dump file on subsequent executions
of DSDI, eliminating the need to read the entire dump tape on
each call.

D omitted

No random dump file is to be created.

DMB

A binary dump file produced by the DMB or LOADBC command
is to be analyzed instead of an EDD file.

DMB omitted

EDD file is to be analyzed.
When the DMB parameter is specified for a DMB-created dump,
DSDI uses directives as though the job were running at control
point 1. The DMB command dumps the exchange package,
central memory, and extended memory in binary (refer to the
NOS Version 2 Reference Set, Volume 3). Use the following
directives to dump selected portions of memory to be analyzed.

Revision M

Directive

Description

CP,1

Dump exchange package.

RAC,1/C,fwa,lwa

Dump central memory in C format.

RAC,1/D,fwa,lwa

Dump central memory in D format.

RA,0/EC/C,fwa,lwa

Dump extended memory in C format.

'RA,0/EC/D,fwa,lwa

Dump extended memory in D format.

Express Deadstart Dump Interpreter (DSDI) 6-3

Calling the Express Deadstart Dump Interpreter

Description

DMB omitted

(Continued)
fwa and lwa are the first and last word addresses of memory to
be dumped. When this parameter is specified to analyze a
LOADBC controlware dump, the only DSDI directive that can be
used is:
BCDUMP/ops.

Refer to the BCDUMP directive described later in this section
for a description of the ops parameter.
F=dumpfile

The 1- to 7-character name of the EDD file that DSDI will
interpret.

F omitted

Same as F=DUMP.

I=infile

The 1- to 7-character name of file on which input directives are
written.

I omitted

Same as I=INPUT.

L=outfile

The 1- to 7-character name of file on which list output is to be
written. The user must save or print the file.

L omitted

Same as L=OUTPUT, except that the file is automatically
printed.

EDD file is not to be rewound.

NR omitted

EDD file is to be rewound before processing.

CMR pointers from the running system are to be used. Selecting
this parameter causes the CMR pointers from the running
system to be used to locate tables and buffer areas on the EDD
file. This parameter is typically used when it is known that the
CMR pointers on the EDD file were destroyed by system
malfunction. Directives used to dump CMR will dump the
pointers contained on the EDD file, not those from the running
system.
This parameter should be used only when the configuration of
the running system is the same as the system in use when the
EDD file was created.

P omitted

CMR pointers from EDD file are to be used.

PD = n

Print density in number of lpi (3, 4, 6, or 8).

,^^\

6-4 NOS Version 2 Analysis Handbook

Revision M

Calling the Express Deadstart Dump Interpreter

Description

Same as PD = 8.

PD omitted

Same as the job's default print density.

Input directives are contained on the command after the
terminator. The I parameter is ignored. This eliminates the need
to use a separate input file for the directives when only a few
directives are needed.

Z omitted

Input directives are not contained on the command. The system
uses the I parameter.
When input directives appear on the DSDI command, the first
character following the command terminator is the separator
character for all directives on the command. Any display code
character that is not used in any of the directives, including a
space, can be used as the separator character. Each directive
must be preceded by a separator and terminated by a period.
The directives can extend to column 72 on the command.
Continuation lines are not permitted.
For example, (slant used for separator):
DSDI,Z./SC./XP./P./D,0,20000./EC./D,0,10000.

If the directives are included in the input file, the following
equivalent job would appear.
DSDI.
—EOR—
SC.
XP.
p.
D,0,20000.
EC.
D,0,10000.

Dump CYBER 170 S/C register.
Dump executing exchange packages.
Dump all PPs.
Dump the first 20000s locations of central memory.
Set memory type to extended memory.
Dump the first 10000s locations of extended
memory.

—EOI—

A request for the EDD tape must precede the DSDI command. Since EDD writes
information on a labeled, 7- or 9-track tape at a density of 800 characters per inch
(cpi) for 7 track and 1600 or 6250 cpi for 9 track, the request should appear as follows:
LABEL,DUMP,D=density,tape,F=S,LB=KL,VSN=DUMP.

Parameter

Description

density

800 cpi for 7-track tape.
1600(PE) or 6250(GE) cpi for 9-track tape.

tape

MT for 7-track tape.
NT for 9-track tape.

The request is presented in the resource mounting preview display and the job is rolled
out until the tape is mounted and assigned. Although the default express dump file
name (DUMP) is used in this example, a different file name can be specified, provided
the same file name is also specified on the DSDI command (F parameter).
Revision M

Express Deadstart Dump Interpreter (DSDI) 6-5

Input Directives

Input Directives
DSDI input directives provide the capability to selectively dump only those portions of
the EDD file that are of interest. The input directives are grouped into the following
categories.
Type of Directive

Description

List control

Enables you to control line printer page eject and
print density, and to specify comments in subtitle line
of the output listing.

File manipulation and control

Enables you to specify alternate files for DSDI input
directives and listing output.

Central memory/extended
memory dump

Provides octal dumps of specified portion of central
memory or extended memory. Absolute or relative
addresses can be printed (three print formats are
available). Two additional dump formats are available
to print 64-bit memory in hexadecimal for CYBER
180-class machines.

PP dump

Provides octal memory dumps of all or selected PPs
(two print formats are available). PP analysis data can
be included in the dumps. Six additional formats are
available to print 16-bit PP memory for CYBER
180-class machines.

CMR dump

Provides specially formatted dumps of selected areas
in central memory resident. These areas are specified
by name rather than by address.

Subsystem dump/analysis

Provides specially formatted dumps of subsystem
control points and associated tables and buffers.

Hardware register dump

Provides dumps of specified hardware registers.

Several of the DSDI input directives have interactive capabilities. The output produced
by these directives is specially formatted for listing at an interactive terminal. Refer to
Interactive Use of DSDI later in this section for information concerning directive entry
and use of DSDI from an interactive terminal.
Refer to Printer Output Listing Examples, later in this section, for examples of
listings produced by several of the DSDI input directives.

6-6 NOS Version 2 Analysis Handbook

Revision M

y*^Hj!y

Directive Format

Directive Format
A directive has the following format.
directive, Pi ,P2,.•-.Pn-comments
Field Description
directive The directive name starts in column 1. It is terminated by a separator
or terminator character.
pi Parameter(s) for the directive. Depending on the requirements of the
directive, the directive may have no parameters or a number of
parameters.
comment Any characters following the directive terminator are considered
comments and are ignored by DSDI. However, the comments are
included with the directive in the title line of each page of the output
listing (a combined total of 50 characters appear in the title line).
separator You can use any character, including a space, to separate the fields of a
directive. The exceptions are:
A to Z
0 to 9

Refer to Interactive Use of DSDI later in this section for additional information
concerning directive entry from an interactive terminal.

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-7

List Control Directives

List Control Directives
The list control directives provide the capability to specify print density and page eject
options, and to add comments in the subtitle line of each page listed.
EJ — Force Page Eject
The EJ directive forces DSDI to issue a page eject function before listing the output
produced by the next directive processed. The EJ directive can also force a page eject
upon reaching a specified point on the page being printed. The page eject function is
performed automatically unless disabled by the EJOFF directive.
Format:
EJ,nn.
Parameter

Description

Force page eject only if less than nn decimal lines remain on the
current page. If nn is omitted, page eject is forced before listing the
output from the next directive processed.

EJOFF — Turn Off Auto Page Eject
The EJOFF directive disables auto page eject. Until this directive is processed, DSDI
automatically issues a page eject function before listing the output produced by each
new directive.
Format:
EJOFF.

EJON — Turn On Auto Page Eject
The EJON directive enables auto page eject (default condition). DSDI automatically
issues a page eject function before listing the output produced by each new directive
processed. This directive has no effect unless auto page eject has been disabled by the
EJOFF directive.
Format:
EJON.

PD — Reset Print Line Density
The PD directive resets the print line density to a value other than that specified on
the DSDI command.
Format:
PD.n.

Parameter

Description
New print line density in number of lpi (3, 4, 6, or 8). If n is omitted or
an incorrect value is specified, a diagnostic message is issued.

6-8 NOS Version 2 Analysis Handbook

Revision M

*. — Comment in Subtitle Line

*. — Comment in Subtitle Line
The *. directive specifies a comment that appears in the subtitle line of each page
listed.
Format:
*.ccc...ccc

Parameter Description
ccc...ccc Comment; up to 36 characters are printed.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-9

File Manipulation and Control Directives

File Manipulation and Control Directives
File manipulation and control directives provide the capability to specify alternate files
for DSDI input directives and listing output.
DISPOSE — Dispose Alternate List File to Print Queue
The DISPOSE directive causes the alternate list file specified by the OUTPUT directive
to be disposed to the print queue. DSDI listing output then resumes on the original
output file. This directive has no effect unless output has previously been assigned to
an alternate list file (refer to the OUTPUT directive, next). Refer to Interactive Use of
DSDI later in this section for additional information concerning use of this directive
from an interactive terminal.
Format:
DISPOSE,username.

Parameter Description
username User name under which the remote batch terminal to receive the
listing is logged in. If username is omitted, the listing is printed at a
central site line printer.
OUTPUT — Assign Output to Alternate List File
The OUTPUT directive temporarily assigns DSDI listing output to a file other than
that specified on the DSDI command. When the alternate file is disposed to the print
queue (refer to the DISPOSE directive, above), output resumes on the original output
file. If the alternate file is not disposed, both the original and the alternate output files
remain at the job control point as local files. Refer to Interactive Use of DSDI later in
this section for additional information concerning use of this directive from an
interactive terminal.
Format:
OUTPUT.filename.

Parameter Description
filename Name of alternate list file (from 1 to 7 characters). Only one alternate
output file may be active at a time; filename cannot be the same name
as the normal output file. If filename is omitted, the system assumes
file name ALTRNT.

■<-=5\

6-10

NOS

Version

Analysis

Handbook

Revision

READ — Read Alternate Directives File

READ — Read Alternate Directives File
The READ directive causes DSDI to temporarily stop reading the current directives file
and begin reading directives from the specified record on the named alternate file or
from the current position if the record name is omitted. DSDI reads from the specified
alternate directives file until an end-of-record is encountered (end-of-file or empty
record if * is specified) and then resumes with the next directive on the original input
directives file.
Format:
READ.filename,rec,*.

Parameter Description
filename Name of alternate directives file (local file).
rec Optional record name. If rec is specified, file filename is searched for
record rec from the current position to end-of-file or an empty record. If
rec is not found, DSDI issues an error message. If rec is not specified,
DSDI reads directives from the current position to end-of-record. Records
must be in text format where the first word of the record is the record
name, unless the file is assigned to an interactive terminal; then,
directives may be entered directly.
* Optional character specifying that DSDI is to read directives from all
records until an end-of-file or an empty record is encountered.
REWIND — Rewind File
The REWIND directive repositions the specified file to beginning-of-information.
Format:
REWIND,filename.
Parameter Description
filename Name of file to be rewound.

R e v i s i o n M E x p r e s s D e a d s t a r t D u m p I n t e r p r e t e r ( D S D I ) 6 - 11

Central Memory/Extended Memory Dump Directives

Central Memory/Extended Memory Dump Directives
The central memory/extended memory dump directives provide the capability to dump
any portion of central memory or extended memory in instruction parcel, byte, or word
format. There are 6-bit display code character equivalents included with each format.
Either absolute or relative memory locations may be dumped. Refer to CMR Dump
Directives later in this section for directives used to dump specific portions of NOS
central memory resident (CMR).
Dump Control Directives
Dump control directives select the type of memory to be dumped (central memory or
extended memory) and the addressing mode to be used (absolute or relative).
ALLMEM — Extend Central Memory Dumps
The ALLMEM directive enables central memory dumps to extend past the central
memory boundary on machines with central memory extension. ^^
Format:
ALLMEM.

CM — Set Memory Type to Central Memory
The CM directive specifies that subsequent C, D, and E directives dump central
memory locations. Unless the EC or TJEC directive is specified, central memory ^^
locations
are
dumped
by
default.
'^^j
Format:
CM.

6-12

NOS

Version

Analysis

Handbook

Revision

Dump Control Directives

EC — Set Memory Type to Extended Memory
The EC directive specifies that subsequent C, D, and E directives dump extended
memory or unified extended memory (UEM) locations. Unless the EC or UEC directive
is specified, central memory locations are dumped by default.
Format:
EC,emid.

or
EC.emid.fwa.
Parameter Description
emid Extended memory identification; emid can be UEM or ESM. If emid is
omitted, UEM is assumed. This parameter is useful only on models 865,
875, and CYBER 180-class machines since all other models have only
one type of extended memory available.
fwa First word address (fwa) divided by 1000s. fwa is added to the fwa and
last word address (lwa) parameters in subsequent C, D, and E directives
when dumping UEM. If fwa is omitted, DSDI determines the beginning
of unified extended memory from the pointer in CMR and adds it to the
fwa and lwa parameters of the C, D, and E directives.
This parameter is ignored on any machine other than models 865 and
875 and CYBER 180-class machines.
RA — Reset Reference Address
The RA directive specifies that subsequent C, D, and E directives dump memory
locations relative to a specified reference address. Unless the RA or RAC directive is
entered, absolute memory locations are dumped by default.
Format:
RA.nnnnnnn.

Parameter Description
nnnnnnn Reference address; addresses specified on subsequent C, D, and E
directives are relative to this address.
Clearing the reference address specified on the most recent RA or RAC directive
reenables absolute addressing. This is done by entering the RA directive in this format:
RA.O.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-13

Dump Control Directives

RAC — Reset Reference Address to RA of Control Point
The RAC directive specifies that subsequent C, D, and E directives dump memory 1
locations relative to the reference address of a specified control point. Unless the RA or
RAC directive is entered, absolute memory locations are dumped by default.
Format:
RAC,nn.

Parameter Description
nn Control point number; addresses specified on subsequent C, D, and E
directives are relative to the reference address of this control point.
Refer to the description of the RA directive to reenable absolute addressing.
UEC — Set Memory Type to User-Access Extended Memory
T h e U E C d i r e c t i v e s p e c i fi e s t h a t s u b s e q u e n t C , D , a n d E d i r e c t i v e s d u m p 7
user-accessible extended memory locations. Unless the EC or UEC directive is specified,
central memory locations are dumped by default.
Format:
UEC,fwa.

Parameter Description
f w a F i r s t w o r d a d d r e s s d i v i d e d b y 1 0 0 0 s f o r u s e r - a c c e s s i b l e e x t e n d e d m e m o r y. ^ \
fwa is added to the fwa and lwa parameters in subsequent C, D, and E
directives. If fwa is omitted, DSDI determines the beginning of
user-accessible extended memory from the pointer in CMR and adds it to
the fwa and lwa parameters of the C, D, and E directives.

.as^S

6-14

NOS

Version

Analysis

Handbook

Revision

Memory Dump Directives

Memory Dump Directives
Memory dump directives specify the area of memory to be dumped and determine the
format of the output listing (refer to Printer Output Listing Examples later in this
section for a sample output listing). The CM and EC or UEC directives determine the
type of memory to be dumped (default is central memory). Absolute memory locations
are dumped unless relative addressing has been enabled (refer to RA and RAC
directives earlier in this section).
C — Dump Memory in Instruction Parcel Format
The C directive causes the specified locations of central memory or extended memory to
be dumped in four groups of five octal digits (three words per line) with 6-bit display
code character equivalents. Repetitive data is suppressed.
Format:
C,fwa,lwa.

Parameter Description

jpfev

fwa

First word address to be dumped (mandatory).

lwa

Last word address, plus one location, to be dumped. If lwa is omitted,
fwa+1 is assumed by default.

yms

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-15

Memory Dump Directives

D — Dump Memory in Byte Format
The D directive causes the specified locations of central memory or extended memory
to be dumped in five groups of four octal digits (three words per line) with 6-bit
display code character equivalents. Repetitive data is suppressed.
Format:
D,fwa,lwa.
Parameter Description
fwa

First word address to be dumped (mandatory).

lwa

Last word address, plus one location, to be dumped. If lwa is omitted,
fwa+1 is assumed by default.

The output listing is read from top to bottom by column rather than across the page.
Refer to Interactive Use of DSDI later in this section for additional information
concerning use of this directive from an interactive terminal.
E — Dump Memory in Word Format
The E directive causes the specified locations in central memory or extended memory
to be dumped in word format (four words per line) with 6-bit display code character
equivalents.
Format:
E,fwa,lwa.
Parameter Description
fwa First word address to be dumped (mandatory).
lwa Last word address, plus one location, to be dumped. If lwa is omitted,
fwa+1 is assumed by default.

.-^^SivX

6-16 NOS Version 2 Analysis Handbook

Revision M

Memory Dump Directives

/ — Dump 64-Bit Memory in Instruction Parcel Format
The I directive is valid on CYBER 180-class machines only. It prints the specified
locations of central memory in four groups of four hexadecimal digits (three words per
line) with 7-bit ASCII code character equivalents. The second format is for NOS/VE
dumps.
Format:
I,fba,lba,ei.

or
I.fba,lba,asid.

Parameter Description
fba First byte address (fba), hexadecimal, to be printed (mandatory).
lba Last byte address (lba), plus one location, to be printed. If lba is
omitted, fba+8 is assumed by default.
ei If ei is 1, fba and lba specify byte addresses relative to byte 0 of the
environment interface. If ei is omitted, fba and lba specify absolute byte
addresses.

>ffiififfitfSV

asid Specifies an actual segment identifier (ASID) for NOS/VE dumps. If you
specify this parameter, the fba and lba parameters must represent byte
offsets and have values in the range of from 0 to 7FFFFFFF
hexadecimal. This parameter is optional.
When you call DSDI from a batch job the output from this directive is printed in three
columns, read from top to bottom, one column at a time. When you call DSDI from an
interactive job the words are displayed one word per line.
For NOS/VE dumps, the addresses given for the fba and lba parameters must be real
memory addresses (RMAs) or, when translated to system virtual addresses (SVAs), the
actual segment identifiers (ASIDs) must match. Refer to appendix H for NOS/VE
address formats to use with the DSDI utility.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-17

Memory Dump Directives

W — Dump 64-Bit Memory in Word Format
The W directive is valid on CYBER 180-class machines only. It prints the specified
locations of 64-bit memory in hexadecimal (4 words of 16 digits per line) with 7-bit
ASCII code character equivalents. The second format is for NOS/VE dumps.
Format:
W, f b a , l b a , e l .

or
W, f b a , l b a , a s i d .

Parameter Description
fba First byte address, hexadecimal, to be printed (mandatory).
lba Last byte address, plus one location, to be printed. If lba is omitted,
fba+8
is
assumed
by
default.
ei If ei is 1, fba and lba specify byte addresses relative to byte 0 of the
environment interface. If ei is omitted, fba and lba specify absolute byte
addresses.
asid Specifies an actual segment identifier (ASID) for NOS/VE dumps. If you
specify this parameter, the fba and lba parameters must represent byte
offsets and have values in the range of from 0 to 7FFFFFFF
hexadecimal. This parameter is optional.
For NOS/VE dumps, the addresses given for the fba and lba parameters must be real
memory addresses (RMAs), or when translated to system virtual addresses (SVAs), the
actual segment identifiers (ASIDs) must match. Refer to appendix H for NOS/VE
address formats to use with the DSDI utility.

6-18

NOS

Version

Analysis

Handbook

Revision

PP Dump Directives

PP Dump Directives
PP dump directives provide the capability to obtain a memory dump of all or selected
PPs. Two dump formats are available, block format and line format.
AP — Dump Analysis of PP and PP Memory in Octal Line Format
The AP directive causes PP memory to be dumped in line format with 6-bit display
code character equivalents (same format as the Q directive). Repetitive lines are
suppressed and zero bytes are represented by hyphens (—). An analysis of the PP is
printed before the memory dump. Analysis data includes the associated PP
communications area, resident entry point call addresses, read-only variables in direct
cells, and the values of the P, Q, K, and A registers (only applies to certain CYBER
180 class machines). Certain direct cell variables are verified and those in error are
indicated.
NOTE
Correct operation of this directive requires that the PP communication area on the
EDD file be intact.
Format!
P, n i , n 2

nm.

Parameter Description
n» Number of PP to be dumped or a program name. If a program name is
specified, all PPs executing that program are dumped. A warning
message is issued if an incorrect number is specified or the program
name is not found in any PP. If ni is omitted, all active PPs are
dumped.
Refer to Printer Output Listing Examples for a sample of the printer output listing
produced by this directive.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-19

MPP — Move PP

MPP — Move PP
The MPP directive causes the correct logical PP to be dumped if the logical position of
PPOO has been changed prior to the full dump to tape. If the PPS-O/PPS-1 toggle
switch has been toggled, the n parameter should not be specified. If PPOO has to be
moved to another PP via a deadstart panel program, the n parameter should be
specified.
Format:
MPP.n.

Parameter Description
Number of PP to which PPOO was moved, n cannot equal 0. If n is
omitted, 10 is assumed (CYBER 170 and CYBER 70 Computer Systems
with 20 PPs).
P — Dump PP Memory in Octal Block Format
The P directive causes PP memory to be dumped in block format, where each block
represents 64 words of memory. The blocks are read by column (top to bottom), where
each column contains eight 12-bit words in octal format numbered 0 through 7. There
are eight columns in each block, numbered 0 through 7. Repetitive data is not
suppressed and zero words are represented by hyphens (—). For models 865 and 875,
bytes 77768 and 77778 contain the PP's R register.
Format:
P»ni,n2,...,nm.

Parameter Description
ni

Number of PP to be dumped. If omitted, all PPs are dumped.

r^^S,

6-20 NOS Version 2 Analysis Handbook

Revision M

PF — Dump FLPP Memory in Octal Block Format

PF — Dump FLPP Memory in Octal Block Format
The PF directive causes first-level peripheral processor (FLPP)* memory to be dumped
in block format, where each block represents 64 words of memory. The blocks are read
by column (top to bottom), where each column contains eight 12-bit words in octal
format numbered 0 through 7. There are eight columns in each block, numbered 0
through 7. Repetitive data is not suppressed and zero words are represented by
hyphens (—).
Format:
PF,n1,n2,...,nII).
Parameter Description
m Number of FLPP to be dumped. If omitted, all FLPPs are dumped.
PMS — Read PP Select Switches
The PMS directive causes the dump of the S/C register (maintenance register for
models 865 and 875) to be read to determine the current value of the PP memory
select switches and the correct logical PP to be dumped, if the logical position of PPOO
has been changed prior to the full dump to tape. If the PP memory select switches
have been changed, this directive should be specified with the binary value of the
switches prior to the change. This directive is meaningful only on a CYBER 170
Computer System with the exception of models 815, 825, 835, 845, and 855.
Format:
0$**\.
PMS,n.

Parameter Description
n Previous select switch setting; 0 through lis. If n is the same value as
that read from the S/C register, this directive is not meaningful.

yims
1. Hardware manuals define peripheral processors making up a peripheral processor subsystem as PPs, and
the first-level peripheral processors as peripheral processing units (PPUs). In this manual, first-level
peripheral processors are referred to as FLPPs. FLPPs are available only on model 176.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-21

PO — Dump 16-Bit PP Memory in Octal Block Format

PO — Dump 16-Bit PP Memory in Octal Block Format
,*^\

The PO directive is valid on CYBER 180-class machines only. It prints PP memory in
block format, where each block represents 64 words of memory. DSDI represents each
16-bit word by six octal digits. Words whose upper 4 bits are zero are represented by
four octal digits. Blocks are read by columns (top to bottom), where each column
contains eight 16-bit words numbered 0 through 7. There are eight columns in each
block, numbered 0 through 7. Repetitive data is not suppressed and zero words are
represented by hyphens (—). The PP's R register is displayed preceding the first line
of the dump.
Format:
P 0, ni, n2, ...,n m.

Parameter Description
Number of PP to be dumped. If omitted, all PPs are printed.

PX — Dump 16-Bit PP Memory in Hexadecimal Block Format
The PX directive is valid on CYBER 180-class machines only. It prints 16-bit memory
in block format, where each block represents 256 words of memory. Each 16-bit word is
represented by four hexadecimal digits. Blocks are read by columns (top to bottom),
where each column contains sixteen 16-bit words in hexadecimal format numbered 0
through F. There are 16 columns in each block, numbered 0 through F. Repetitive data
is not suppressed and zero words are represented by hyphens (—). The PP's R register
is displayed preceding the first line of the dump.
Format:
PX,n1fn2

nm.

Parameter Description
ni

Number of PP to be printed. If omitted, all PPs are printed.

,^^y

6-22 NOS Version 2 Analysis Handbook

Revision M

Q — Dump PP Memory in Octal Line Format

Q — Dump PP Memory in Octal Line Format
The Q directive causes PP memory to be dumped in line format with 6-bit display code
character equivalents. Each line contains 16 bytes (PP words) printed in two sets of 8
bytes in octal format. Each set consists of an address, 8 bytes, and display code
character equivalents. Repetitive lines are suppressed and zero bytes are represented by
hyphens (—). Refer to Interactive Use of DSDI later in this section for additional
information concerning use of this directive from an interactive terminal.
Format:
Q,ni,n2,...,nm.

Parameter Description
ni Number of PP to be dumped. If omitted, all PPs are dumped.
QF — Dump FLPP Memory in Octal Line Format
The QF directive causes FLPP memory to be dumped in line format with 6-bit display
code character equivalents. Each line contains 16 bytes printed in two sets of 8 bytes
in octal format. Each set consists of an address, 8 data bytes, and 6-bit display code
character equivalents. Repetitive lines are suppressed and zero bytes are represented by
hyphens (—).
Format:
QF,n1fn2, . - -,nm.

Parameter Description
ni Number of FLPP to be dumped. If omitted, all FLPPs are dumped.

yams

2. Hardware manuals define peripheral processors making up a peripheral processor subsystem as PPs, and
the first-level peripheral processors as peripheral processing units (PPUs). In this manual, first-level
0^s peripheral processors are referred to as FLPPs. FLPPs are available only on model 176.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-23

QOA — Dump 16-Bit PP Memory in Octal/ASCII Line Format

QOA — Dump 16-Bit PP Memory in Octal/ASCII Line Format
The QOA directive is valid on CYBER 180-class machines only. It prints PP memory "l
in line format with 7-bit ASCII code character representation. Each line contains 16
words printed in two sets of eight. Each set consists of an octal address, eight words
(six digits per word if the upper 4 bits are nonzero, four digits otherwise), and 7-bit
ASCII code character equivalents. Repetitive lines are suppressed and zero words are
represented by hyphens (—). The PP's R register is displayed preceding the first line
of the dump. Refer to Interactive Use of DSDI later in this section for additional
information concerning use of this directive from an interactive terminal.
Format:
QOA,n1fn2,. ...nm.

Parameter Description
m Number of PP to be printed. If omitted, all PPs are printed.
QOD — Dump 16-Bit PP Memory in Octal/Display line Format
The QOD directive is valid on CYBER 180-class machines only. It prints PP memory
in line format with 6-bit display code character representation. Each line contains 16
words printed in two sets of eight. Each set consists of an octal address, eight words
(six digits per word if the upper 4 bits are nonzero, four digits otherwise), and 6-bit
display code character equivalents. Repetitive lines are suppressed and zero words are
represented by hyphens (—). The PP's R register is displayed preceding the first line
of the dump. Refer to Interactive Use of DSDI later in this section for additional
information concerning use of this directive from an interactive terminal.
Format:
Q0D,n,,n2 nm.
Parameter Description
m Number of PP to be printed. If omitted, all PPs are printed.

6-24

NOS

Version

Analysis

Handbook

Revision

QXA — Dump 16-Bit PP Memory in Hexadecimal/ASCII Line Format

QXA — Dump 16-Bit PP Memory in Hexadecimal/ASCII Line Format
The QXA directive is valid on CYBER 180-class machines only. It prints PP memory
in line format with 7-bit ASCII code character representation. Each line contains 16
words printed in two sets of eight. Each set consists of a hexadecimal address, eight
words (four hexadecimal digits per word), and 7-bit ASCII code character equivalents.
Repetitive lines are suppressed and zero words are represented by hyphens (—). The
PP's R register is displayed preceding the first line of the dump. Refer to Interactive
Use of DSDI later in this section for additional information concerning use of this
directive from an interactive terminal.
Format:
QXA,n,,n2,...,nm.

Parameter Description
ni Number of PP to be printed. If omitted, all PPs are printed.
QXD — Dump 16-Bit PP Memory in Hexadecimal/Display Line Format
The QXD directive is valid on CYBER 180-class machines only. It prints PP memory
in line format with 6-bit display code character representation. Each line contains 16
words printed in two sets of eight. Each set consists of a hexadecimal address, eight
words (four hexadecimal digits per word), and 6-bit display code character equivalents.
Repetitive lines are suppressed and zero words are represented by hyphens (—). The
PP's R register is displayed preceding the first line of the dump. Refer to Interactive
Use of DSDI later in this section for additional information concerning use of this
directive from an interactive terminal.
Format:
QXD,n,,n2,...,nm.

Parameter Description
ni Number of PP to be printed. If omitted, all PPs are printed.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-25

CMR Dump Directives

CMR Dump Directives
The CMR dump directives provide the capability to selectively dump specified areas of
central memory resident. Refer to the NOS Version 2 Systems Programmer's Instant
for detailed illustrations of central memory resident.
Successful use of the CMR dump directives is dependent upon the integrity of central
memory resident at the time EDD was performed. Most important is the integrity of
the CMR pointers on the EDD file. If these pointers are not intact, the dump
produced by DSDI may prove meaningless. Thus, if it is suspected that the CMR
pointers are not intact, specifying the P keyword on the DSDI command allows DSDI
to use the CMR pointers from the running system. This option should be used only
when the configuration of the running system is the same as the system in use at
the time the EDD file was created. If the CMR pointers on the EDD file are not
intact, the integrity of the other areas of central memory is also questionable. In this
case, the output produced by the CMR dump directives may be unpredictable.
ACCOUNT — Dump Account Dayfile Buffer
The ACCOUNT directive causes the account dayfile pointers and buffer to be dumped
in word format (four words per line) with 6-bit display code character equivalents. This
format is the same format as that for the E memory dump directive. This directive
also dumps the buffer in a line-by-line format, as on the DSD A display.
Format:
ACCOUNT.

.*^v

6-40 NOS Version 2 Analysis Handbook

Revision M

Subsystem Dump/Analysis Directives

Subsystem Dump/Analysis Directives
The subsystem dump/analysis directives provide the capability to selectively dump
portions of central and/or PP memory associated with a specific subsystem (BIO, IAF,
MAG, and RHF). Although many other directives already described in this section can
be used to dump the same areas of memory, these directives dump those areas most
frequently analyzed when subsystem-related malfunctions occur. In addition, many of
the dumps are specially formatted to provide a detailed description of the area being
dumped. If the specified subsystem was not active at the time the EDD file was
created, an error message is issued.
BATCHIO (BIO) — Dump Associated Memory for Analysis
The BATCHIO directive causes the areas of central and/or PP memory that are most
frequently analyzed when BATCHIO malfunctions are indicated to be dumped. The
areas and type of memory dumped are determined by the list options specified.
0$ms

Formats:
BATCH10,ops.

or
BIO,ops.

Parameter Description
°PS List options; a string of characters indicating the areas of memory to be
dumped. If no options are specified, all three options (PBN) are selected
by default and are processed in order as listed.
ops

Description

P Provides analysis and full memory dump of PPs having
resident copies of 1CD, 110, QAP, QAC, or DSP. The output
listing generated is the same (in format and content) as that
produced by entering the AP directive in this format:
AP,1CD,1I0,QAP,QACfDSP.

Refer to the description of the AP directive earlier in this
section for additional information.
B Provides specially formatted dumps of each active BATCHIO
buffer point. Included with the dump of each buffer point is
the associated equipment type and FET, as well as EST and
FNT/FST entries.
N Provides a dump of the negative field length associated with
the BATCHIO control point in byte format with 6-bit display
code character equivalents. This format is the same format as
that for the D memory dump directive.

y$*s

Revision M Express Deadstart Dump Interpreter (DSDI) 6-41

IAF — Dump Associated Memory for Analysis

IAF — Dump Associated Memory for Analysis
The IAF directive causes the areas of central and/or PP memory that are most
frequently analyzed when IAF malfunctions to be dumped. The areas and type of
memory are determined by the list options specified. The IAF current entry word
(SSPA) is always printed at the beginning of the listing, in byte format, regardless of
which list options are specified.
Format:
IAF,ops.

Parameter Description
ops List options; a string of up to five characters indicating the areas of
memory to be dumped. If no options are specified, four options (ETLP)
are selected by default and processed in order as listed.
ops

Description

C Provides analysis of the IAF command table.
E Dumps the IAF reentry table in byte format (two words per
line) with 6-bit display code character equivalents. The first
word in each line is preceded by its ordinal within the
table.
T Provides a specially formatted dump of the IAF terminal
table in which each word reflects the appropriate parameter
fields. The message status table entry is included when "*^\
dumping network terminal tables. In addition, each word is
preceded by a description of the parameter fields and its
COMSREM symbol. Terminal table entries that are empty,
except for having status bit 0 in word 3 (VROT entry) set,
are not printed.
L Provides a dump of pot link table and all pots. The pot link
table is dumped in byte format with pot link byte ordinals
indicated for each word, but no 6-bit display code character ^^
equivalents. Repetitive pot link table entries are suppressed. '^7
The pots are dumped in word format, three lines per pot,
with the first line containing only the pot number.

6-42

NOS

Version

Analysis

Handbook

Revision

IAF — Dump Associated Memory for Analysis

Parameter Description
ops

(Continued)
ops

Description
Provides analysis and full memory dump of all PPs having
resident copies of TLX, 1TA, ITN, and 1T0. This option also
provides an analysis and dump of all PPs having resident
copies of 1R0 and 1RI that are associated with control points
of interactive origin. The output listing generated is the same
(in format and content) as that produced by entering the AP
directive in this format:
AP.TLX,1TA,1TN,1T0,1R0,1RI.

The exception is that the AP directive also dumps all PPs
having copies of 1RO and 1RI rather than only those
associated with control points of interactive origin. Refer to
the description of the AP directive, earlier in this section, for
additional information.

/gS*y

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-43

MAGNET (MAG) — Dump Associated Memory for Analysis

MAGNET (MAG) — Dump Associated Memory for Analysis
The MAGNET directive causes the areas of central and/or PP memory that are most 1
frequently analyzed when a malfunction within the Magnetic Tape Subsystem is
indicated to be dumped. The areas and type of memory dumped are determined by the
list options specified.
Format:
MAGNET,ops.

or
MAG,ops.

Parameter Description
ops List options; a string of characters indicating the areas of memory to
be dumped. If no options are specified, all four options (UQSP) are
selected by default and are processed in order as listed. ***h
ops

Description

U Provides a specially formatted dump of the Magnetic Tape
Subsystem unit descriptor tables with associated FET, EST,
and FNT/FST. Each word of a unit descriptor table is
formatted to reflect appropriate parameter fields. In addition,
each word is preceded by a description of the parameter
fields and its COMSMTX symbol. If extended labels are
present, they appear with the FET in the output listing. The "^
FET also indicates the address and control point number of
the user.
Q Provides a dump of the Magnetic Tape Subsystem queue
table in byte format (two words per line) with 6-bit display
code character equivalents. The first word in each line is
preceded by its ordinal within the table.
S Provides a dump of the Magnetic Tape Subsystem active
stage job table, staging tape VSN list, and stage request ^^)
table, if they are defined. The tables are dumped in byte
format (two words per line) with 6-bit display code character
equivalents. The first word in each line is preceded by its
ordinal within the table.
P Provides analysis and full memory dump of all PPs having
resident copies of IMT. The output listing generated is the
same (in format and content) as that produced by entering
the AP directive in this format:
AP.1MT.

Refer to the description of the AP directive earlier in this
section for additional information.

6-44

NOS

Version

Analysis

Handbook

Revision

RHF — Dump Associated Memory for Analysis

RHF — Dump Associated Memory for Analysis
The RHF directive causes the areas of central and/or PP memory that are most
frequently analyzed when RHF malfunctions are indicated to be dumped. The areas and
type of memory dumped are determined by the list options specified.
Format:
R H F, o p s .

Parameter Description
ops List options; a string of characters indicating the areas of memory to be
dumped. If no options are specified, all three options (ACP) are selected
by default and are processed in order as listed.
ops
/^

with

6-bit

display

Description

A Provides a dump of the RHF dayfile buffer in word format
code character equivalents. This format is
the same format as that for the E memory dump directive.
This option also dumps a standard dayfile.
C Provides a dump of the RHF field length in byte format with
6-bit display code character equivalents. This format is the
same format as that for the D memory dump directive.
Provides analysis and full memory dump of all active PPs
associated with the control point.

>sffff\

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-45

Hardware Register Dump Directives

Hardware Register Dump Directives
The hardware register dump directives provide the capability to dump specified
hardware registers.
FMFREG — Dump PP Registers
The FMFREG directive is valid on CYBER 180-class machines only. For each PP
register (P, Q, K, A) stored while processing a fatal mainframe error, DSDI prints the
PP register contents.
Format:
FMFREG.

IOUCR — Dump Concurrent PP Channel Registers
The IOUCR directive is valid only on CYBER machines that support concurrent
channels and concurrent PPs. For each concurrent PP channel specified, DSDI prints
the channel number, channel type, IOU status register contents, T register contents,
fault status mask, and test mode operand generator. The channel number and channel
type are octal; all of the other fields are hexadecimal.
Format:
IOUCR,chi,ch2,...,chn.

Parameter Description
chi Channel number of the concurrent PP channel register to be printed. If
omitted, all concurrent PP channel registers are printed.
IOUMR — Dump IOU Maintenance Registers
The IOUMR directive is valid on CYBER 180-class machines only. For each
input/output unit (IOU) maintenance register specified, DSDI prints the hexadecimal
register number, the register contents, and the register description. For registers
containing error indicators, DSDI prints a description of each error.
Format:
I O U M R , fi r s t , l a s t .

Parameter Description
first First register (hexadecimal) to be printed. If omitted, printing begins
with register 00.
last Last register +1 (hexadecimal) to be printed. If omitted, printing ends
with register first+1.
If no parameters are specified, DSDI prints all maintenance registers.

^WsSky

6-46

NOS

Version

Analysis

Handbook

Revision

LPVA — Load Central Memory PVA into Pseudo Register

LPVA — Load Central Memory PVA into Pseudo Register
The LPVA directive is valid on CYBER 180-class machines only. You use this directive
when you are doing an analysis of a NOS/VE dump tape. It retrieves a copy of 48 bits
starting at the specified address and loads them into the pseudo register named process
virtual address (PVA). This value is printed at your terminal and saved for use by
subsequent directives.
Format:
LPVA,address,offset.

Parameter Description
address Specifies the beginning byte address of the 48 bits loaded into PVA.
You can enter this parameter in any of the acceptable NOS/VE address
formats. Refer to appendix H for NOS/VE address formats to use with
the DSDI utility. This parameter is required.
offset Specifies the hexadecimal number of bytes from the start-address to
begin loading the 48-bit address. This parameter is optional.
MEMMR — Dump Memory Maintenance Registers
The MEMMR directive is valid on CYBER 180-class machines only. For each memory
maintenance register specified, DSDI prints the hexadecimal register number, the
register contents, and the register description. For registers containing error indicators,
DSDI prints a description of each error.
Format:
M E M M R , fi r s t , l a s t .

Parameter Description
first First register (hexadecimal) to be printed. If omitted, printing begins
with register 00.
last Last register+ 1 (hexadecimal) to be printed. If omitted, printing ends
with register first+1.
If no parameters are specified, DSDI prints all maintenance registers.

0*®**..

Revision M Express Deadstart Dump Interpreter (DSDI) 6-47

PROCA — Dump Processor Operand Cache

PROCA — Dump Processor Operand Cache
The PROCA directive is valid on CYBER 180 model 990 and 995 machines only. This ^
directive prints the contents of the processor operand cache (POC) record from the EDD
file. The dump format has three columns. The first column contains the specified word
numbers, the second column contains the contents of the corresponding words from the
control memory part of the POC record in hexadecimal, and the third column contains
the contents of the corresponding words from the data memory part of the POC record
in hexadecimal.
Format:
P R O C A , fi r s t , l a s t .

Parameter Description
first First word number (hexadecimal) to be printed. If omitted, printing
begins with word 0.
last Last word number (hexadecimal) to be printed. If you specify first but
omit last, printing ends with word first+1. If you omit both first and
last, printing ends with word FFFi6.
PROCW — Dump Processor Controlware Part Number and Revision Level
The PROCW directive is valid on CYBER 180-class machines only. It prints the
processor controlware part number and the revision level. For model 990 and 995
machines, DSDI extracts the controlware revision level and date from the last 256-bit
w o r d o f t h e p r o c e s s o r c o n t r o l s t o r e ( P C S ) r e c o r d f r o m t h e E D D fi l e . < * ^
Format:
PROCW.

PRO MR — Dump Processor Maintenance Registers
The PROMR directive is valid on CYBER 180-class machines only. For each processor
maintenance register specified, DSDI prints the hexadecimal register number, the
register contents, and the register description. For registers containing error indicators, ^\
descriptions of each error are printed.
Format:
P RO M R, fi rs t,l a s t.

Parameter Description
first First register (hexadecimal) to be printed. If omitted, printing begins
with register 00.
last Last register+1 (hexadecimal) to be printed. If omitted, printing ends
with register first-I-1.
If no parameters are specified, all maintenance registers for both processors are
printed. If first and last are specified, then the specified registers are dumped for all
processors.

6-48

NOS

Version

Analysis

Handbook

Revision

PROPM — Dump Processor Page Map

PROPM — Dump Processor Page Map
The PROPM directive is valid on CYBER 180 model 990 and 995 machines only. The
directive prints the contents of the processor page map (PPM) record from the EDD
file. The listing consists of 128 data lines plus column headings. Each line contains a
set number (0 to 3), the entry number (0 to lFi6) within its set, and the contents of
that entry in hexadecimal.
Format:
PROPM.

PRORF — Dump Processor Register File
The PRORF directive is valid on CYBER 180-class machines only. For all CYBER
180-class machines except models 990 and 995, it prints the maintenance channel
interface port number followed by the hexadecimal register number and contents of
each processor register specified.
Format:
PRORF,first,last.

Parameter Description
first First register to be printed. If omitted, printing begins with register 00.
last Last register +1 to be printed. If omitted, printing ends with register
first+1.
If no parameters are specified, the entire register file for both processors is printed. If
first and last are specified, then the specified registers are dumped for all processors.
For CYBER 180 model 990 and 995 machines, enter the PRORF directive without
parameters. DSDI produces a listing of the entire contents of each of the following
records from the EDD file: PRF, PIS, PRG, and PRH. Refer to Printer Output Listing
Examples later in this section for a sample of the listing DSDI produces for model 990
and 995 machines.
PROSM — Dump Processor Segment Map
The PROSM directive is valid on CYBER 180 model 990 and 995 machines only. The
directive prints the contents of the processor segment map (PSM) record from the EDD
file. The listing consists of 64 data lines plus column headings. Each line contains a
set number (0 or 1), the entry number (0 to lFi6) within its set, and the contents of
that entry in hexadecimal.
Format:
PROSM.

yms
Revision M Express Deadstart Dump Interpreter (DSDI) 6-49

PROXP —- Dump Processor Exchange Package

PROXP — Dump Processor Exchange Package
The PROXP directive is valid on CYBER 180-class machines only. It prints the
maintenance channel interface port number followed by the hexadecimal register
number, the contents of each processor register, and (for most registers) a description
of the register's contents. The exchange packages for all processors are printed.
Format:
PROXP.

For NOS/VE dumps, use the following format:
PROXP,address.
Parameter Description
address Specifies the first byte address of the exchange package. You can enter
this parameter in any of the acceptable NOS/VE address formats. Refer
to appendix H for NOS/VE address formats to use with the DSDI
utility. If you omit this parameter, the current contents of the central
processor registers are printed. If the memory address you specify is
for the stack frame save area, the only registers printed are the
registers recorded in the save area.
SC — Dump S/C Register
The SC directive is valid only on CYBER 170 Computer Systems with the exception of
models 815, 825, 835, 845, and 855; it causes the S/C registers (maintenance registers a^s
for
models
865
and
875)
to
be
dumped.
■■ '
Format:
SC.

SETCPU — Set CPU Number
The SETCPU directive is valid on any CYBER model that supports 170 mode in both
C P U s . I t s e t s u p p r o c e s s o r p o i n t e r s f o r t h e C P U s p e c i fi e d i n t h e d i r e c t i v e . " ^ l
Format:
SETCPU,number.

Parameter Description
number Specifies the number of the CPU (0 or 1). Default is 0.

6-50

NOS

Version

Analysis

Handbook

Revision

SETIOU — Set PP Dump Defaults

0ms
SETIOU — Set PP Dump Defaults
The SETIOU directive presets the parameter defaults for processing PP memory dumps
to allow printing of concurrent PP memory.
Format:
SETIOU,opt ion.

Parameter Description
option

Specifies whether to process concurrent PPs or nonconcurrent PPs. If no
option is specified, option N is assumed.
option

Description
Process concurrent PPs to allow printing 8192 words of
concurrent PP memory. This option is valid only on CYBER
machines that support concurrent channels and concurrent
PPs.

Process nonconcurrent PPs to allow printing 4096 words of PP
memory.

SETJPS — Change the JPS Register Value

>#^N

The SETJPS directive is valid on CYBER 180-class machines only. You use this
directive when you are doing an analysis of a NOS/VE dump tape. It sets the pseudo
register named job process state (JPS) to a value different than the value of the JPS
register found in the dump.
Format:
SETJPS,address.

Parameter Description
address Specifies the location of, or the actual new value for, the JPS register.
You can enter this parameter in any of the acceptable NOS/VE address
formats. Refer to appendix H for NOS/VE address formats to use with
the DSDI utility. If you specify address as a process virtual address
(PVA) or system virtual address (SVA), the system loads the value stored
at that location into the pseudo JPS register. If you specify address as a
real memory address (RMA), the system loads that value into the pseudo
JPS register. This parameter is required.

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-51

SETRMA — Convert Address into RMA

SETRMA — Convert Address into RMA
>^™^v

The SETRMA directive is valid on CYBER 180-class machines only. You use this
directive when you are doing an analysis of a NOS/VE dump tape. It converts the
specified address into a real memory address (RMA) and saves that value in a pseudo
register (called RMA) for use in subsequent directives.
Format:
SETRMA,address.

Parameter Description
address Specifies the address to be converted to an RMA. You can enter this
parameter in any of the acceptable NOS/VE address formats. Refer to
appendix H for NOS/VE address formats to use with the DSDI utility.
This parameter is required.
SETVEP — Set Virtual Address Parameters
The SETVEP directive is valid on CYBER 180-class machines only. You can use this
directive when you are doing an analysis of a NOS/VE dump tape. It changes the
virtual .memory parameters used for the NOS/VE DSDI memory display directives (I
and W).
Format:
SETVEP,address,lengthtmask,mps.

Parameter Description
address

Specifies the beginning address of the page table as a hexadecimal
number of from 1 to 6 digits. This parameter is required.

length

Specifies the length of the page table as a hexadecimal number of from
1 to 6 digits. This parameter is required.

mask

Specifies the value of the page size mask as a hexadecimal number of
from 1 to 6 digits. This parameter is required.

mps

Specifies the contents of the pseudo register named monitor process state
(MPS) as a hexadecimal number of from 1 to 6 digits. This parameter is
required.

6-52 NOS Version 2 Analysis Handbook

Revision M

TRACEBK — Traceback Stack Frame Save Area

TRACEBK — Traceback Stack Frame Save Area
The TRACEBK directive is valid on CYBER 180-class machines only. You use this
directive when you are doing an analysis of a NOS/VE dump tape. It displays the
exchange package found at the specified address; and, for each stack frame, the module
name and contents of the registers saved.
Format:
TRACEBK,address.

Parameter Description
address Specifies the address of the exchange package where the traceback
starts. You can enter this parameter in any of the acceptable NOS/VE
address formats. Refer to appendix H for NOS/VE address formats to use
with the DSDI utility. If you omit this parameter, the system uses the
exchange package currently in the central processor.
0ms.
( If you enter this directive interactively, the output includes just the minimum save
area (the P register and address registers AO, Al, and A2). If you enter this directive
in a batch job with line printer output, the output contains the entire stack frame as
saved by the task. The actual contents depends on the information saved by the task.
XP - Dump Deadstart Exchange Package
The XP directive causes the CPU exchange package executing at the time of deadstart
to be dumped. If there are two CPUs in the system, both exchange packages in
0s execution at the time of deadstart are dumped.
Format:
XP.

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-53

Buffer Controller Directive

Buffer Controller Directive
The buffer controller directive provides the capability to dump specified buffer
controllers and list verification information for controlware dump files produced by the
LOADBC utility. The BCDUMP directive causes the selected buffer controllers to be
dumped.
Format:
BCDUMP/ops.
or
BCDUMP ,CCi,CC2 ccn.
or
BCDUMP,CCi/OPSi ,CC2/0PS2, . . . ?CCn/0PSn.

Parameter

Description

cci Channel number of buffer controller to be dumped. If no channels are
specified, all buffer controllers are dumped.
opsi List options; a character string indicating the line format, interpretation,
and verification of the selected buffer controllers to be dumped. If no
options are specified, options H and D are selected by default.
opsi

Line

Format

H Hexadecimal line format (default).
0

Octal

line

format.

Options A and D indicate interpretation.
opsi

Interpretation

A 7-bit ASCII code interpretation.
D

6-bit

display

code

interpretation

(default).

The following options indicate verification.
opsi

V e r i fi c a t i o n

V List verification information (used with the controlware
dump file produced by the LOADBC utility).
V omitted Do not list verification information.

6-54

NOS

Version

Analysis

Handbook

Revision

^^\

Interactive Use of DSDI

Interactive Use of DSDI
Incorporated within DSDI is an interactive facility that allows several of the directives
already described in this section to be entered interactively from a terminal. This
interactive facility is designed to provide the following additional capabilities.
• Allows preliminary examination of the EDD file to determine which areas should
be listed in detail at a line printer.
• Allows examination of certain areas of the EDD file not listed during normal
operational procedures following a system malfunction. Typically, predefined
portions of the EDD file are listed following a system malfunction.
• Allows online examination of the EDD file from a remote location.
Refer to Example of DSDI Terminal Use later in this section for an example showing
interactive use of DSDI.

0^s.

When the DSDI command is entered from an interactive terminal, there will be a 10to 60-second delay before input directives can be entered. During this delay, DSDI is
copying the EDD file to a random-access mass storage file. The length of the delay
depends on device speed and current system activity. When DSDI is able to accept
input directives, it will issue the following prompt to the terminal.
ENTER DIRECTIVES- ?

Directives are entered following the question mark prompt. Only one directive can be
entered at a time, and each directive is restricted to one line. The format is the same
as described for batch input (refer to Directive Format earlier in this section).
Generally, any of the DSDI input directives can be entered at an interactive terminal.
However, the output produced by many of the directives is formatted for listing only
at a line printer (136 columns) and cannot be listed at the terminal (72 columns).
The L parameter on the DSDI command initially determines the disposition of the list
output. If a file name is not specified, list output is assigned to file OUTPUT by
default (that is, the terminal). In this case, entry of directives that produce output
that cannot be listed at the terminal results in the message:
DIRECTIVE RESTRICTED TO PRINTER OUTPUT.

If a list output file name is specified on the DSDI command, all input directives can be
entered at the terminal. All list output (including error messages) is written to the
specified file.

jgpsv

Revision

Express

Deadstart

Dump

Interpreter

(DSDI)

6-55

Interactive Use of DSDI

These two input directives are provided to further control the disposition of list output:
Directive

Description

OUTPUT,filename. Assigns output to alternate file filename (file name OUTPUT
is not allowed; that is, alternate list output cannot be assigned
to the terminal). If filename is omitted, the system assumes
file name ALTRNT. While this directive is active, all input
directives can be entered at the terminal. All list output
(except error messages) is written to file filename and is
formatted for transmission to a line printer. Error messages
are written directly to the terminal.
DISPOSE. Disposes the alternate list file (specified in the OUTPUT
directive) to the print queue. Output will be printed at the
central site line printer. All subsequent list output resumes on
the original output file specified on the DSDI command.
Refer to File Manipulation and Control Directives earlier in this section for additional
information concerning use of these directives.

6-56 NOS Version 2 Analysis Handbook

Revision M

Terminal Output Directives

Terminal Output Directives
The following directives produce output formatted for listing at an interactive terminal.
C — Dump Memory in Instruction Parcel Format
The C directive causes the specified locations of central memory or extended memory to
be dumped in four groups of five octal digits (one word per line) with 6-bit display code
character equivalents. No pagination is processed for terminal output. The CM, EC, and
UEC directives (refer to Central Memory/Extended Memory Dump Directives earlier in
this section) determine the type of memory to be dumped; default is central memory.
The RA or RAC directive (refer to Central Memory/Extended Memory Dump Directives
earlier in this section) must be entered to dump relative addresses; default is absolute
addressing.
Format:
C, fwa, l wa.

Parameter Description
fwa

First word address to be dumped (mandatory).

lwa

Last word address, plus one location, to be dumped. If omitted, fwa+l
is assumed by default.

Figure 6-1 shows the terminal output produced by the C directive.
? C,6230,6240
0006230 34240
0006231 00764
0006232 04154
0006233 00004
0006234 05153
0006235 ooooo
0006236 ooooo
0006237 ooooo

10100 00012 50036 1TAA
AU 3
AAK
70000 ooooo 10113
70000 ooooo 10113 DM*
AAK
- A E
67446 74000 10005
05700 ooooo ooooo EMX.

ooooo ooooo ooooo
ooooo ooooo ooooo
00005 05111 14422

EEII9R

Figure 6-1. C Directive Output

yms

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-57

CP — Dump Active Control Point Areas

CP — Dump Active Control Point Areas
The CP directive causes the job sequence name and control point area address for each 1
control point to be dumped.
Format:
CP.

Figure. 6-2 shows the terminal output produced by the CP directive.
CP 01 CP 02 CP 03 CP 04 CP 05 CP 06 CP 07 CP 10
IAF
A A LT
NAM
AAKW
AAAG
AAAF
AAAE
0200 0400 0600 1000 1200 1400 1600 2000
C P 11 C P 1 2 C P 1 3 C P 1 4 C P 1 5 C P 1 6 C P 1 7 C P 2 0
AAAD
AAAC
AAAB
AALN
AALU
2200 2400 2600 3000 3200 3400 3600 4000
CP 21 CP 22 CP 23 CP 24 CP 25 CP 26 CP 27 CP 30
RBF
4200 • 4400 4600 5000 5200 5400 5600 6000
CP 31 CP 32 CP 33 CP 34 •<—Control Point Number
"AG BIO SYS «*—Job Sequence Name at Control Point
6200 6400 6600 7000 •<— Control Point Area Address

Figure 6-2. CP Directive Output

6-58

NOS

Version

Analysis

Handbook

Revision

D — Dump Memory in Byte Format

D — Dump Memory in Byte Format
The D directive causes specified locations of central memory or extended memory to be
dumped in five groups of four octal digits (one word per line) with 6-bit display code
character equivalents. No pagination is processed for terminal output. The CM, EC, and
UEC directives (refer to Central Memory/Extended Memory Dump Directives earlier in
this section) determine the type of memory to be "dumped; default is central memory.
The RA or RAC directive (refer to Central Memory/Extended Memory Dump Directives
earlier in this section) must be entered to dump relative addresses; default is absolute
addressing.
Format:
D,fwa,lwa.
Parameter Description
fwa

First word address to be dumped (mandatory).

lwa

Last word address, plus one location, to be dumped. If omitted, fwa+1
is assumed by default.

Figure 6-3 shows the terminal output produced by the D directive.
? D,6230,6240.
0006230 3424 0101 0000 0125 0036 1TAA AU 3
0006231 0076 4700 0000 0001 0113 *
AAK
0006232 0415 4700 0000 0001 0113 DM*
AAK
0006233 0000 4674 4674 0001 0005 - AE
0006234 0515 3057 0000 0000 0000 EMX.
0006235 0000 0000 0000 0000 0000
0006236 0000 0000 0000 0000 0000
0006237 0000 0000 0505 1111 4422
EEII9R

Figure 6-3. D Directive Output

J ^ W y,

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-59

PP — Dump PP Communication Areas

PP — Dump PP Communication Areas
The PP directive causes the PP number, executing program name, control point
assignment, and input register address for each PP communication area to be dumped.
Format:
pp.

Figure 6-4 shows the terminal output produced by the PP directive.

Program in Execution

PP Number
1 C o n t r o l Point Assignment

\
PPOO
WTR-34
7200

PP01
OSD-34
7210

PP02
QAC-16
7220

PP03
7230

PP04 \^ P P 0 5 / P P 0 6
1RO-05 1SJ-34
7240
7250 7260

PP07
1WT-31
7270

PP10
7300

PP11
OAC-14
7310
y*3i|y

PP20
PIP-03
7320

PP21
CPD-34
7330

PP22
QAC-02
7340

PP23
7350

PPOO

PP24
110-32
7360

PP25 \ PP26

PP27

7370 \7400

7410

PP30
1MA-01
7420

PP31
7430

Input Register Address

7440

Figure 6-4. PP Directive Output

"**%*

6-60 NOS Version 2 Analysis Handbook

Revision M

Q — Dump PP Memory in Line Format

00ms

Q — Dump PP Memory in Line Format
The Q directive causes the specified locations of PP memory to be dumped in line
format. Each line contains 8 bytes (PP words) with 6-bit display code character
equivalents. Repetitive lines are suppressed and zero bytes are represented by
hyphens (—).
Format:
Q,n,fwa,lwa.

Parameter Description

Number of PP to be dumped.

fwa

First word address to be dumped.

lwa

Last word address, plus one location, to be dumped.

NOTE
fwa and lwa are automatically adjusted so that the dump limits fall within a multiple
of 108 words.
This format is valid only for terminal output. If attempted from a job of batch origin
or while an alternate list file is active, the fwa and lwa parameter will be interpreted
as PP numbers.
Figure 6-5 shows the terminal output produced by the Q directive.
? Q . 5 ,0,100
0000
0003
0010
0064
0020
2250
0030
0011
0040
1501
0050
3404
0060
0070
0001

2020
0001
3225
7646
1116
2330
4521
0100

3340
7772

2014
0035
1000

0100
0027
0001
0074
6213
6101
0003

0614
0006
0012
0141
0203
1707
0001
6000

1073
4402
0600

0153
6250

4334
1401
5747

0117
6072
5751

4000
0001
6251

6675
0532
6252

CPPo5
R/2U
I MAINPL
1DSX 2

+Q
AA H

FL 81A0
A FH LA
W J93.*.(
AA6F

BC
KOG 5
A AAS AE2
C / ( )

Figure 6-5. Q Directive Output

00S

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-61

QOA, QOD, QXA, QXD — Dump 16-Bit PP Memory in Line Format

QOA, QOD, QXA, QXD — Dump 16-Bit PP Memory in line Format
These four directives are valid on CYBER 180-class machines only. Each directive
prints specified locations of 16-bit PP memory in line format. Each line contains eight
PP words in octal or hexadecimal with 6-bit display code or 7-bit ASCII.code character
representations. Repetitive lines are suppressed and zero bytes appear as hyphens (—).
Numeric
Character
Directive Format Representation Representation
QOA,n,fwa,lwa,R. Octal 7-bit ASCII code
QOD,n,fwa,lwa,R. Octal 6-bit display code
QXA,n,fwa,lwa,R. Hexadecimal 7-bit ASCII code
QXD,n,fwa,lwa,R. Hexadecimal 6-bit display code
Parameter Description
n Number of PP to be printed.
fwa First word address to be printed.
lwa Last word address, plus one location, to be printed.
R If specified, the R register is printed.
This directive format is valid only for terminal output. If it is used in a job of batch
origin or while an alternate list file is active, DSDI interprets the fwa and lwa
parameters as PP numbers.

6-62

NOS

Version

Analysis

Handbook

Revision

Example of DSDI Terminal Use

Example of DSDI Terminal Use
This example illustrates how DSDI might be used following a system malfunction to
analyze portions of the EDD file from an interactive terminal. It is assumed that an
EDD file was created during normal system recovery procedures. Vertical spacing has
been expanded to permit commentary. The example begins after the login sequence has
been completed.

0ms

batch
RFL.O.

Enter Batch subsystem.

/label,dump,vsn=dump,lb=kl,f=s,mt,d=800

The LABEL command is entered to
assign the EDD dump tape to this job.
Use of the vsn parameter allows the job
to be rolled out while the tape is
mounted and assigned.

/get.altdir

Retrieve alternate directives file ALTDIR
(refer to the example in figure 6-6).

/dsdi.

Calls DSDI, which copies EDD tape to a
random mass storage file.

ENTER DIRECTIVES - -

Enter terminal output directives (refer to
Terminal Output Directives earlier in
this section) to list any portion of the
EDD file at the terminal. DSDI issues
the prompt (?) when it is ready to accept
a new directive.

? output,a 1 tout

List output produced by subsequent
directives is written to local file
ALTOUT. This allows entry of directives
that produce line printer formatted
output.

? read.altdir

All input directives in alternate
directives file ALTDIR are read and
processed. List output is written to local
file ALTOUT. DSDI does not request
terminal input until the last directive on
ALTDIR is processed.

? dispose.

Dispose local file ALTOUT to the print
queue for listing at the central site line
printer. Output produced by subsequent
directives is listed at the terminal.

EXPRESS DUMP COMPLETE (FL USED XXXXXXB)
/

DSDI is terminated by entering a
carriage return in response to the ?
prompt.

In summary, the following operations were performed by DSDI. First, small areas of
the dump file were listed at the terminal for preliminary examination. This was done
both to analyze the cause and effect of the system failure, as well as determine the
extent of line printer listings required. An appropriate comment may be placed in the
list file subtitle at this time via the *.ccc...ccc directive.

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-63

Example of DSDI Terminal Use

Next, directives were entered to generate the necessary line printer listings. These
listings are generally extensive, or contain specially formatted output that cannot be
listed at the terminal. Thus, output was written to an alternate list file named
ALTOUT.
After all necessary directives had been entered from the terminal, an alternate
directives file (ALTDIR) was read. ALTDIR is a permanent file containing input
directives necessary to obtain a printer listing of specific areas in the dump file that
are frequently examined following a system failure (for example, CMR tables and
buffers, PP memory, and so forth). Figure 6-6 illustrates a typical alternate directives
file. Comments describing areas of the dump file to be listed appear, along with the
directive, in the title line of the output listing.5
When DSDI finished processing the last directive in file ALTDIR, it again issued the
? prompt to the terminal requesting further directive input from the keyboard. At
this time, the DISPOSE directive was entered causing file ALTOUT to be printed at
the central site line printer. Refer to Printer Output Listing Examples later in this
section for examples of printer output listings.

DUMP

LC.LOW CENTRAL MEMORY POINTERS
PP.PP-COMMUNICATION AREA
CPO.H.
EJOFF.
EJ.
CP.CONTROL POINT AREAS
CPO.XTAF.
DP.DAYFILE BUFFER POINTERS
EJ.
EST.EQUIPMENT STATUS TABLE
FNT.SYSTEM FILE NAME TABLE
EJ.
MST.MASS STORAGE TABLES
JC.JOB CONTROL PARAMETERS
CP.30/T.SYSTEM CONTROL POINT AREA
ACCOUNT.ACCOUNT FILE BUFFER
ERRLOG.ERROR LOG BUFFER
EJON.
AP.ACTIVE PPS

Figure 6-6. Sample Alternate Directives File

5. All records in an alternate directives file must be in text format; the first word in each record contains
only the record name.

6-64 NOS Version 2 Analysis Handbook

Revision M

Printer Output Listing Examples

Printer Output Listing Examples
The listings illustrated in this section are samples of the line printer output listings
produced by several of the input directives described under Input Directives earlier in
this section.
Each page of output listings begins with two header lines: a title line and a subtitle
line. The header lines are formatted as follows.
RA = current input directive DUMP nn DSDI yy/mm/dd. hh.mm.ss.
0000000 dump type hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM. NOS 2 comments

PAGE n

Header

Description

RA = 0000000

Indicates absolute addressing is in effect. If relative
addresses were being dumped (RA or RAC directive
entered), a nonzero reference address would appear in
this field.

current input directive

Input directive currently being processed, including
comments (50-character field).

DUMP nn

Reflects the EDD tape number currently being used
(nn is a 2-digit dump identifier assigned during EDD).

yy/mm/dd. hh.mm.ss.

This field reflects the date and time when DSDI was
executed.

dump type

Indicates type of memory currently being dumped
(central memory, extended memory, or a PP number).
If the AP directive is processed, the PP number is
followed by the name of the program currently being
dumped.

hh.mm.ss. yy/mm/dd.
CDC NETWORK
OPERATING
SYSTEM. NOS 2

Time of day, date, system title line, and system
version name taken from CMR.

comments

Up to 36 characters of comments specified on a
*.ccc...ccc input directive.

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-65

Printer Output Listing Examples

Example 1:
Figure 6-7 illustrates the printer output listing produced by the PP directive (dump
PP communication areas).
OURP 01
16.52.11. 82/01/06. CDC NETWORK OPERATING SYSTEM.

RA =
P P.
CC0DO0O CN

PPOO

MTR
CP34

PP02

RAC
UTER
CP16

PPW
CPOO

PP06

1SJ
LDAR
CP34

PP10
CPOO

PP20

PIP
CP03
CH05

DSDI
NOS 2

1524 2234 MOO OOOO OOOO
OOOO 0001 OOOO 0003 5570
0101 1501 OOOO OOOO 0007
OOOO OOOO OOOO 0004 0565
OOOO OOOO OOOO oooo oooo
oooo oooo oooo oooo oooo
oooo oooo oooo oooo oooo
oooo oooo oooo oooo oooo

HTR1
PP01
OSD
A
C
AAKA
G
CP34
OE

K
0
CA
CX

PP03
CPOO

R
AU
PP05

1R0
CP05

B2 R A
SB B BR
CA
CX
CO
1SJ1 C
H A9 CEN
A9 CE
BS4 E 6
8L9
CA
CX

PP07

1RT
LDAR
CP31

CO
PP11

QAC
UTER
CPI 4

BB2 D L
51 E/Y E=2
6T QWHTJ
BHXKP
PIPC

CIOC BCY
IX OOAE
A BB C
A RXDJAYA
1FLIZDEBLJ

PP21

CPO
LDAR
CP34

8 2 / 0 1 / 2 0.

16.22.05.

0423 0434 WOO OOOO OOOO
OOOO OOOO OOOO COM OOOO
3404 1434 0010 W44 0142
OOOO OOOO OOOO OOOO OOOO
OOOO WOO 1401 0613 5 4 W
5534 3457 3737 5733 3357
S543 3550 3334 5033 4157
W40 WW OOW OOW OOW
OOW OWO WOO w o o 7430
OOW OOW WW W W O O W
OOOO OWO OOW woo woo
WW 0002 0235 0022 0001
WW WOO OWO OWO OOW
W 0 4 W W 3 3 1 4 OOW 7325
0724 WOO 2127 1031 1200
W W W W 0 0 0 2 1030 1020
3422 1705 WW
2043 04W WW
0154 W11 4440
40W WW 0504
WW WOO OWO
0003 WW 1776
0301 6400 OWO
OOW OOW 1401

DSD1
1DL1 H 9A7
LAFK"
11 . 4 4 . 0 0 .
82/01/06.

BB2 R A
0 OL ll
GT BWHYJ
BHXKP

WOO
5400
0400
WOO
WOO
2777
WOO
3735

1R0E
PSD A<=
As 195 D
5 EDV

3415 2431 3170 OOOO W W
1055 W01 4472 0 2 3 0 1073
W W 0 W 1 4 4 7 2 0 2 3 0 OWO
0020 OOW WW OOW OOW
WOO OWO WOO WOO WW
3441 4033 3635 5 6 5 5 111 6
57W WOO 2100 3 6 4 5 0100
3S47 34W 20W 3 3 4 5 5415

1HTYY
H A9 BXH
A9 BX

2101 03S4 OOW
1077 OOW W03
0W4 0002 4476
OOW OWO 0237
WW WOO OWO
0013 OOW 4126
0724 OWO 2127
OOW OOW 0W2

OOW
0003
0152
W04
OWO
OOW
1031
1030

0216
3734
OWO
0010
OWO
4426
1200
1020

QAC= BN
H C C41
D B9 A)
B4 D H

0320
1055
WOO
OOW
OOW
0777
20W
0770

OOW
OOW
0131
W21
WOO
01W
3W3
3412

0225
W W
WOO
0022
OWO
71W
1013
3077

CPD1 BU
H
D SAY
EOT Q fi

0434 OOW
OOW WW
0W4 6123
0005 0424
WOO WW
1777 3777
0045 6001
1401 3411

OWO
0001
WOO
26W
OWO
OOW
WOO
0620

PA G E

C
CA

LAFP4Z

165032, IN
Q 3+A
2*1 P 0*=R

K 6V 9W
GT QWHYJ
BHXKP

G 0 4 A
P ♦ AXCKK
G LA1I1JX

Figure 6-7. Sample PP Directive Output

,*^^.

6-66 NOS Version 2 Analysis Handbook

Revision M

Printer Output Listing Examples

Example 2:
Figure 6-8 illustrates the printer output listing produced by the AP directive (dump
analysis of PP and PP memory in line format).

DUMP 01
6.52 11. 62/01/06. CDC NETWORK OPERATING SYSTEM.

IA •
A P. 3 .
0000000 FP03

DSDI
82/01/20.
NOS 2

16.22.09.

PA G E

ANALYSIS OP PP03
PP03

OOOO OOW OOW OOW 743D
OOOO OOW OOW WW OWO
CPOO 0000 OOW OOW WW OOW
OOW 0W2 0235 W22 W01

WW OOW OOW WW WW
0004 OOW 3314 OOW «B25 D
0724 OOW 2127 1031 12W GT
OOW WW 0002 1030 1020
RESIDENT DORY POINTS
NAME LOC CALLER
FTN
DFM
EXS
SKS
RDS
VDS
EMS

0163
0432
0471
0506
0553
0556
0561

2205
2341
1477
0355
0370
1740
0415

LAST HAIN PROGRAM LOADED LAST OVERLAY LOADED - 3ME
UST MASS STORAGE DRIVER - 6DI
BB2 R A
OL U
OVHYJ
BHXKP

LOW CORE CONSTANTS
NAME LOC ACTUAL EXPECTED
RA 55 4W4
PL 56 W21
ON 70 0001 0W1
HN 71 01W OIW
IB 72 10W 10W
TR 73 0W3 0W3
CP 74 62W
IA 75 7230
OA 76 7231
MA 77 7232
R-REC W010W0 OOOOOOOO

OPERATING REGISTERS
Q
K
BEFORE IDLE 00130
AFTER IDLE W133

0W76 006000
00064 1077W

W6135
W7371

DFT BUFFER 1 OOOOO
DFT BUFFER 2 030W

W170 000140
07410 WSW6

000010
OOOOOO

••• WARNING •**

PPU KEKORT
OOOO 0216 2210 2175 2616 0W6 W01 4473 0315
0020 W65 0030 0027
40W
0040
0002 5504
0203 W53 3101 W06
0060
3314
0100
W02
0343 0411
0120 0704 2000 1701 0576 3010 22W 0177 0336
0140 1720 0676 3076 6010 3010 1301 0546 3074
0160 6010 14W 01W 2205 0443 3410 3076 6210
0200 0510 6010 3010 1015 0731 2005 1455 6010
0220 1447 2610 6010 1014 0445 1720 0676 1502
0240 7762
0260 6173 0020 3051 1340 1006 3474 3574 3374
0300 3412 20W 1505 3413 1473 0200 0163 0326
0320 0100 0474 5400 0302 1063 5400 0277 3076
0340 34IS 5*00 0314 3011 1377 0542 3015 1702
0360 4003 3416 5W3 W01 3417 3003 02W 0553
0400 3016 4403 3017 5403 W01 2000 0506 3503
0420 2725 0302 3071 2342 0420 340) 1453 6173
0440 3412 1217 1111 0410 3602 4W2 0575 3602
0460 1452 02W 0163 3014 0444 2001 2225 6173
0590 0115 0W7 1466 6170 01W OIW 0355 2000
0520 SOW 0110 1237 0556 5000 0104 52W 0107
0540 0163 301) 1014 3112 6113 0551 0340
0560 01W 0415 14W 3413 4471 02W 0773 0370
0600 02W 0663 1404 02W 0746 7106 2116 0532
0620 4771 0705 3107 2300 0342 0403 0200 0663
0640 1131 0515 5C00 0556 6606 0644 7546 3410
0660 0524 0110
0602 3076 6010 3010 0574

~_ -—

—
——
—
•

—- ——
—

BMRHQ VN F A9 CM
X V 5
B D DC $YA P

OL
B C8DI
COP OAE XHR A C3
OFT X HXHKAE-X
HL A IE081HI H
EH HXHKKCYPEL H
L*VH HXLD+OPF Ml
PXCK5HF) 2 0
UP ME1KL B A CT
A D - CBH - B X
IH- CLXIX E7XK0B
SC1N/C AIOXCB E5
XN9CX0-C AP E 2C
VUCBX S7DP1ALS
1JJOIIDH3B5BE 3B
DB A XLD9PARU
AM CL A A C P
/ AHJ4E,/ AD) AC
A XIHLTJ KE(C5
A DHL IK9 B C C
B P LDB C- FQNEZ
» GETGS C7DCB F
IYEH/ E. FF9 -IH
ETAH PBX HXHE

0010
0030

W50
0070

OHO
0130
0150
0170
0210
0230
0250
0270
0310
0330
0350
0370
0410
0430
0450
0470
0510
0530
0550
0570
0610
0630
0650
0670

2120
0301
7*30 4W4 0021 0312
OWI OIW 10W 0W3 62W 7230 723) 7232
W04 2711
1006 0621 1002
1457 6010 3010 3374 0513 1425 0327 2000
1625 60)0 2411 3013 3455 30)4 3456 3076
1427 3210 0644 0312 0711 3011 1277 5100
3010 3111 0572 2005 1447 6370 0111 2W5
3500 0665 1476 6210 0356 2001 2551-6173
2W0 1704 0576 3075 6050 3050 0471 3077
3350 IW6 0200 0321 0115 W05 2W0 0036
3311 1014 3112 6113 2120 I4W 0200 0163
6010 3710 0543 3076 6210 3014 0502 3015
3403 3076 6004 02W 0506 1440 5500 OHO
0727 3607 5300 0106 0504 3407 4W3 3406
5715 0W3 0545 0200 0561 OIW 0315 20W
7762 0100 2341 5400 0457 1701 3402 1063
5200 0457 3411 1406 3401 3077 6301 2572
7764 1477 0200 0321 5000 0471 5415 0W6
7464 3105 60)0 3014 1003 1606 6170 0102
0420 55W 0107 3413 1441 3412 1473 0200
0100 1056 OIW 0370 0314 0100 1740 0334
54W 0606 4771 0705 3107 S3W 0624 0403
5000 0553 0335 54W 0640 1063 S4W 0633
4 0 7 1 0 4 0 3 2 0 0 0 1 1 3 5 02W 0746 7306
1412 02O0 0746 1401 7106 W13 0525 3013
3077 6204 1455 02W 0163 3714 4471 3107
40W

CA
X5D QCJ
AA H C XYZ
DWI HFFQHB
L. HXHO EKLUCWP
KU HTIXK1 XL1.X
LUZHF9CJGIXU (
XHYIE PEL* A1PE
2 F L HC,PAU(
P ODE X /X/D X
O/HFB CQAM EP 3
01HLYJ KQPL B A
H4HE8X HXLEBXM
1CX DB EFL5 AH
GW3CS AFED1CSC1F
.H CE+B E A CHT
' A S6- D.0A1BH
) 0.11LF1AX AU
L B CQ/ D -H F
YE HXLHCHF AB
DP AC1KL61JL B
A H,A C CU 05C1
- FF* CEYCS FTDC
/ ESC2- F5H - FO
5 DCP I2S C- F
UB G-U F KECXK
X DL B A 4L9 YG

Figure 6-8. Sample AP Directive Output

0$ms.

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-67

Printer Output Listing Examples

Example 3:
y*SW|L

Figure 6-9 illustrates the printer output listing produced by the CP directive (dump
active control points). The default list options (XTAF) are used to dump the control
point. This example consists of six pages. Also, notice that the columns cross page
boundaries; that is, the left column is read continuously, from the top of the second
page to the middle of the fourth page. The sequence then continues at the top of the
right column on the second page.
RA
«
C P, 2 .
DUMP
00
0OQ0000 CH 22.15.04. 83/06/02. CDC NETWORK OPERATING SYSTEM.

OSOI
83/06/02.
NOS 2

22.36.17.

PA 6 E

0400 - CONTROL POINT 02
CP02 EXCHANGE PACKAGE
P 33357 AO 22577 BO 0 (A0)«OOW OOW OOW 0002 2575
RA 120300 A1 1 Bl 3 (AD'OOW OOW WOO WOO WOO
FL 46600 A2 26250 82 31053 0WO WW WW 0003 3244
FLE 0 AS 33072 B5 31367 *WW OWO WW WW OWO
°3444 4400 OOW WW OOW 199
T (82>«04W 0320 25W OWO OWO D CPU
028 (B3>*00W OOW WW WW OOW
CZ9 (84)*OW0 WW OWO 0000 OWO
CZ (B5)>04W 0320 51W OWO OWO D CP<
<86)*S110 0336 3001 W03 3274 (HC3XA «
CZ9 <87>"00W 0004 0435 0204 3715 DD2BD4H

7777 7777 7700 OOW WW «WW WW WOO WOO WW
WW OOW OOW WW OWO CX1)«0OW OOW WW OOW OWO
WW WW WW WW W24 T (X2)*WW WW WW OWO OWO
OWO OOW OOW 0004 3521 D2R (X3)*10W 0150 OOW WW OOW H A/
WOO WOO WW W03 3243 C7.8 (X4><04W 0321 6630 2205 0301 D ca XRECA
OOW WW WW 0003 3273 CZ (X5>>00M OOW WW WW WW
2203 14W WW WW WW RCL /DNP'/SDRs EN PT FLAGS
SSJ«/VAL«/SS*» EN PT FLAGS
RESERVED
oooo
RESTART/SUPPRESS OHP* FLA6S
DM* FILE FLAGS
OMP* FL/100 (0 = ENTIRE FL)
oooo
S5J= PARAMETER 6LK ADDRESS
oooooo
SYSTEM PROC CALL WORD
SPCW W0506 oooooooooooooooooooo
CCL - EFF
JCDW 000507 0 0
A
CCL - RIG
oooooo
CCL - DATA
0001
oooooooo
RESERVED
CCL - EF
JCRW 000510 00
CCL - R3
oooooo
oooooo
CCL - R2
CCL - R1
oooooo
DBAW X0511 0
ASBAS'ASSEC NEN/K DIS FUGS
ECS AND CD CMF1 KOOE FLAGS
014043
INPUT BUFFER ADDRESS
014054
RIGHT SCREEN BFR ADD
014054
LEFT SCREEN BFR ADD
HAP OPTIONS/LIB FLAG
LB1W 000512 00

Figure 6-9. Sample CP Directive Output

Revision M

(Continued)

Express Deadstart Dump Interpreter (DSDI) 6-69

Printer Output Listing Examples

(Continued)
OWOWO

C P, 2 .
CH

83/06/02. 22.36.17.
2 2 15.04. 83/06/02. CDC NETWORK OPERATING SYSTE

INSTALLATION WORD 4
IN4M 000444 OOOOOOOOOOOOOOOOOOOO
INSTALLATION WORD 5
INSW 000445 OWWWWWWWWWO
INSTALLATION WORD 6
IN6W 000446 OOOOOOOOOOOOOOOOOOOO
INSTALLATION WORD 7
IN7W 000447 OOOOOOOOOOOOOOOOOOOO
LIMIT FUGS
ACTW
000450
00
N(WOR
OVERFLOW FUGS
SRUW
OOW
SRU
A C C U M U L ATO R / O V E R F L O W
00001651271722
CP ACCUM (NANOUNITS/4) C P T W 0 0 0 4 5 1 0 O O O W O 1 O 7 4 O 5 3 5 5 6 W 0 A 6 S S
I O AW 0 0 0 4 5 2 O 0 3 1 4 5 4 0 O 0 O O 0 O O O 0 4 1 6 Y » S D N
(0 ACCUMULATORS
M13 x HI ♦ H3
HP1W
000453
00W36
3
3
B
H14 ■ JTI * H4
000036
RESERVED
ADAW
0000002
ADDER ACCUMULATOR
Ml • 1000
HP2N
W0454
023420
SIP
0/
H12 • M1 • R2
001750
RESERVED
OOOOOOOO
DISABLE SRU ACCUM, CPM RP3W W0455 0000025700 B. 7X
ION
0000004230
SRU ACCOUNT BLOCK LRT STLW 000456 777777
COMPUTED SRU JOB STEP LIMIT 77777777777777
RESERVED
SRJW
000457
OWO
DCD
777777
SRU JOB STEP LIMIT
SRU ACCUM AT JOB STEP S T A R T
0000040304
CPJW
000460
WOO
N
RESERVED
CP TIME JOB STEP LIMIT
777777
CP
ACCUM
AT
JOB
STEP
S TA RT
0000000016
CHARGE/ACCOUNTING FLGS FPFW 000461 00
RESERVED
7777
SRU VALIDATION LIMIT
FNT ORDINAL OF PROFILE F I L E
OOOO
LEVEL-3 BLOCK TRACK
OOOO
OOOO
LEVEL-3 BLOCK SECTOR
RESERVED
000462 OOOOOOOOOOOOOOOOOOOO
MAX FL FOR JOB STEP
FLCW
000463
3765
4
F
4
LAST CARD FL (NFL)
06W
MAXIMUM FL FOR ENTIRE J O B
3765
RESERVED
OOOOOOOO
JOB STEP RAX ECS FL
ELCW
000464
0200
B
8
LAST CARD ECS FL (NFL)
OOOO
JOB MAX ECS FL
0200
RESERVED
OOOOOOOO
E0U1P ASSIGNED COUNT
EACW
000465
0001
A
RESERVED•
FLIW
000
SCHEDULER STATUS
NE6ATIVE FL FOR ROLLIN
OOOO
ECS FL REQUEST
OOOO
CM FL REQUEST
OOOO
TXOT SUBSYSTEM
TXSW 000466 00
RESERVED
TERMINAL NUMBER
TTNW
OOW
TERMINAL INT ADDR
TIAW
OOOOOO
OUTPUT POINTER
TION
OOOOOO
PFCW
000467
OOOOOOOOOOOO
H
RESERVED
EST
ORD
OF
FA M I LY
DEVICE
0010
LIMIT FOR SIZE OF OAF
LIMIT FOR NUMBER OF P
LIMIT CUNM SIZE 1APF

NOS 2
REDUCE/LOADER FLAGS
RESERVED FOR LOADER
OOW
INTERACTIVE DEBUG CONTROL
OOW
GLOBAL LIB INDICATORS
OWWWO
SECOND LIB/GLOBAL IND LB2W 0W513 W W W W D W O O O O O O O W
F I R S T L I B / G L O B A L I N D L B 3 W 0 W 5 1 4 OOOOOOOOOOOOOOOOOOOO
FNT ADDR LAST FIL EXEC EOCW 0W51S oooo
oooo
ECS FL FOR DMP> CALL PPDW
FL FOR DMP« CALL
oooo
00
DUMP WORD COUNT
FWA OF DUMP
oooooo

RESERVED
000516
OUTSTANDING CONNECT COUNT
ROLLOUT ALLOWABLE SSCW 000517
CONNECTION/WAIT RESPONSES
COMPUTED CP TIRE LIMIT CPLW 000520
LIST OF FILES INDEX LOFW 000521
RESERVED

woooooowowwo
0021
OOW
0000000000000000
S7777777777777000000 4
OOW

LIST OF FILES ADDRESS
023655
RESERVED
A P P L A C C E S S L E V E L A A LW
CM RESIDENCE TIME LMT TSCN 000522 00400323
RESERVED
INIT TIRE SLICE OCCUR FUG
CPU TIME SLICE LIMIT
ADMIN/D1AG/USER PW EXP JSCW 000523
PF PW EXP/LOVER JAL/FAL
WRITE DOWN/UNLABELED TAPES
RESERVED
JOB ACCESS LEVEL
USER ACCESS LEV VALIDATION
000
JOB ACCESS LEVEL LIMIT
USER ACCESS CATEGORY SET
oooowooow
D E F A U LT PA C K N A M E P K N W 0 W 5 2 4 oooooooooooow
DEFAULT PACK TYPE
oooooo
RESERVED
0 0 0 5 2 5 oooooooooooooooooooo
R E C A L L C R I T E R I O N R C C W 0 W 5 2 6 00000OOWO0OO00W002
RECALL
CRITERION
0 0 0 5 2 7 00000000000000000003
RECALL
CRITERION
0 W 5 3 0 00000000000000000004
RECALL
CRITERION
0 0 0 5 3 1 ODOOO00OO0OOOOOOOW5
RECALL
CRITERION
0 0 0 5 3 2 00000000000000000006
RECAU
CRITERION
0 W S 3 3 00OOO0O0OOOOOOWW07
RECALL
CRITERION
0 0 0 5 3 4 D0OOOOO0OOOW0OO0O1O
RECAU
CRITERION
0 0 0 5 3 5 0D00000000W000O0O11
RECALL
CRITERION
0 0 0 5 3 6 00000000000000000012
RECAU
CRITERION
0 0 0 5 3 7 00000000000000000013
RECAU
CRITERION
0 0 0 5 4 0 00000000000000000014
RECAU
CRITERION
0 0 0 5 4 1 03000000000000000015
RECAU
CRITERION
0 0 0 5 4 2 WO0W0OO0O0W0W016
RECAU
CRITERION
000543
RECALL RESUESTS IR-S RECW 000544
RECAU RESUESTS IR-S 00054S
RECAU REQUESTS IR-S 0W546
RECAU REQUESTS IR-S 000547
RECALL REQUESTS IR-S 000550
RECAU REQUESTS IR-S 0W551
RECALL REQUESTS IR-S 000552

ooooooooowwwooooa
oooooooooooooooooooo
oooooooooooooooooooo
oooooooooooooooooooo
oooooooooooooooooooo
ooooooowwooooooow
oooooooooooooooooooo
oooooooooooooooooooo

Figure 6-9. Sample CP Directive Output
(Continued)

6-70 NOS Version 2 Analysis Handbook

Revision M

Printer Output Listing Examples

(Continued)
0000000 CM

DUMP 00
22.15.04. 83/06/02, CDC NETWORK OPERATING SYSTEM

LIMIT
FOR
SIZE
OF
IAPF
7
USER NAME UIDW 000470 16052417202300
CHARGE
FUG,
USER
INDEX
377772
NO EXIT FLA6 EECW 0W471 2
RESERVED

REPRIEVE

000

D ATA

0077

TERMINAL
INPUT
POINTER
TINW
WWOO
REPRIEVE
D ATA
024010
EJT OROINAL OF JOB TFSW 000472 0017
PRIMARY
FILE
FNT
OFFSET
OOOO
RESERVED
DO
ROLLOUT
TIME
TERN
000
EVENT
DESCRIPTOR
OOOOOCO
RESERVED
CSPW
000473
00
LOGOUT EPILOG, .EPILOG REQ 0
PR
CHARGE/USER/INHIBIT
OEC
2
EOR
FUG/CS
COUNT
O O O 0 O O 11
NEXT
S TAT E M E N T
INDEX
0134
LIMIT INDEX
0065
INPUT/SKIP FLAGS
CSSW 000474 0
EST OROINAL
FIRST TRACK
CURRENT TRACK
CURRENT SECTOR
OVERLAP WORD COUNT
DAYFILE POINTERS AND BUFFER

•

-A

83/06/02. 22.36.17.

I RECALL REQUESTS IR-S
| RECAU REQUESTS IR-S
j RECALL REQUESTS IR-S
I l RECALL REQUESTS IR-S
! RECAU REQUESTS IR-S
J RECAU REQUESTS IR-S
I RECAU REQUESTS IR-S
|
j
!
•

RECAU
RECAU
RECALL
RECAU

REQUESTS
REQUESTS
REQUESTS
REQUESTS

MB-S
FB-S
H8-S
MB-S

I RECAU RESUESTS MB-S
|
j
j
J
I
I

RECAU
RECAU
RECAU
RECAU
RECAU
RECAU

REQUESTS
RESUESTS
REQUESTS
REQUESTS
RESUESTS
REQUESTS

HB-S
MB-S
HB-S
MB-S
MB-S
KB-S

j RECAU REQUESTS MB-S
• RECAU REQUESTS MB-S
j RECAU REQUESTS MB-S

000553
0W554
000555
000556
000557
000560
000561
REPW 0W562
W0563
000564
0W565
0WS66
000567
000570
W0S71
000572
000573
0WS74
0W575
000576
000577

OOOOOOOOOOOOOOOOOOOO
WWWOOOWWOOWOW
OOOOOOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOOOOOO
OOOOOOWWWWOWOOO
OOOWOOOOWOOQOWOW
OWWWOWOOWOOWDO
OOOOOOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOOOOOO
OOOOWOOOOWOOWOWO
OOOOOOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOOOOOO
WOWWOOOWWOOOOW

woooooowoawooww
oooooooooooooooooooo
owwwowowoowwo
oooooooooooooooooooo
oooooooooooooooooooo
oooooooooooooooooooo
oooooooooooooooooooo

| T Un Option rc«ua«t
I right colian oa «h««t

——l-J ♦

List

Option

0 0 1 2 0 2 7 5 0 0 11 7 7 7 7 O O W W O O 0 0 4 6
00120276 MOO OOOO 0114 OOW 0104

00120277 0007 4200 42W W10 Q003
W117777
00120003
00120007
00120013
00120017
00120023
00120027
00120033
00120037
00120043
W12W47
00120053
W120057
0012W63
00120067
00120073
00120077
00120103
WI 20107

55353557334057334157
55353557334057334157
17160055553636565514
55353557334057334157
0323551617O4O5OO5S33
55353557334057334457
36343336560516562214
WWWWOWOWWWW
14141116130055143333
16343335S5SSS0333336
.23163433355555565504
55353557333757373657
17010411160755511511
SS3SS5S7333757374157
55353557333757404157
17010411160755511603
55353557333757404257
55353557334057334157
S55S56010356343336W

G7 7 H C

55232520052226112311
16205023163433355555
05260514005540443756
16205023163433355555
33335655202205261117
162050231634333S5SSS
54365610461656231634
55353557334057334457
36343336560516562214
OOWOOOOWOOWWWOO
25152055162033333444
16235055555555555555
O355555552575500OO00
23163433355555565514
1623S0SS5S55S555SSSS
02555555525755000000
23163433355555565514
16205023163433355555

171655O7O11116OS04OO
55353557334057334157
5 5 2 6 0 1 2 2 11 0 11 6 2 4 0 0 S 5
5 5 3 5 3 SS7 3 3 4 0 5 7 3 3 4 1 5 7
25235516235516170405
55353557334057334457
3335SSS5S03333365623
1 6 2 0 5 0 2 3 1 6 3 4 3 3 3 5 S5 S5
54365610461656231634
16235055555555555555
44550317152014052405
55353557333757373657
55333557333757374157
1 7 0 1 0 4 111 6 0 7 5 5 5 1 0 2 11
55353557333757404157
55353557333757404257
17010455031715201405
SS3S3557334057334157
OOOOOOOOOOOOOOOOOOOO 5 5 3 5 3 5 5 7 3 3 4 0 5 7 3 3 4 1 5 7

OOOOOOOOOOOOOOUOOOOO
5 5 0 3 0 3 2 0 5 5 2 6 0 5 2 2 2 3 11
40443700000000000000
5 5 2 0 2 2 0 5 2 6 111 7 2 5 2 3 5 5
00553333330000000000
1 4 1 4 111 6 1 3 0 O S 5 1 4 3 3 3 3
1 6 3 4 3 3 3 5 S5 S5 5 0 3 4 3 3 3 6
55353557334057334457
33355555503433365623
55353557333757373657
04 570000000000000000
23163433355555565514
16235055555555555555
071415SS52S75S0OMM
23163433355555565514
16235055555555555555
240S04S700000WOOWO
16202500552316343335
16205023163433355555

22.05.06. SUPERVISION GAINED

22.05.06.NP/SN102 22.05.06. CCP VERSI
ON 33, LEVEL 594, VARIANT 594
22.05.06.HP/SN102 22.05.06. PREVIOUS
CS NODE 000, PREVIOUS NS NODE WO
22.05.09.NP/SN102 22.0S.09.LLINK LOO
31O3,EN,RL'3,H-N,SN102 /W3,SN102 /103
22.05.09.NP/SN102 22.05.09.
U1NK LW3103,EN,RL'3,H-N,SN102 /103,S
N102
/003
NS/
22.04.43.
SN102 , DUMP NP00199 COMPLETED.
22.04.43.NS/ 22.04.43.SN102 , L
OADING (MIC ). 22.04.46.NS/
22.04.46.SN102 , LOADING (BIGLM ).
22.04.56.HS/ 22.04.56.SN102 , L
OADING (NCB ). 22.04.57.NS/
22.04.57.SN102 , LOAD COMPLETED.
22.O5.O6.NP/SN102 22.05.06.NPU SN102
,AC,103 22.05.06.NP/SN102

DAYFILE LINES IN BUFFER
NS/ 22.04.43.SN102 , DUMP NP00199 COMPLETED.
22.04.43.NS/ 22.04.43.SN102 , LOADING (NIC ).
22.04.46.NS/ 22.04.46.SN102 , LOADING (B1GLN >.

Figure 6-9. Sample CP Directive Output
(Continued)

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-71

Printer Output Listing Examples

■^^s
(Continued)
ooooow

83/06/02. 22.36.18.

DUMP W
2 2 . 1 5 . 0 4 . 8 3 / 0 6 / 0 2 . CDC NETWORK OPERATING SYSTER

C P, 2 .
CR

NOS 2

22.04.56.SN102 , LOADING (NCB X.
22.04.57.SN102 , LOAD COMPLETED.
22.05.06.NPU SN102 ,AC,103
22.05.06. SUPERVISION GAINED
22.05.06. CCP VERSION 33, LEVEL 594, VARIANT 594
22.05.06. PREVIOUS CS NODE OW, PREVIWS NS NODE 000
22.05.09. LLINK LW3103,EN,RL»3,H-N,SN102 /W3,SN102 /103
22.05.09.LLINK L003103,EN,RL»3,H-N,SN102 /103,SN102 /003

22.04.56.NS/
22.04.57.HS/
22.05.06.NP/SN102
22.05.06.NP/SN102
22.05.06.NP/SN102
22.05.06.NP/SN102
22.05.09.HP/SN102
Z2.05.09.NP/SN1O2

F Ll»t Option

ATTACKED F
0304 INPUT I

FNT - 1116 2025 24W W01 17W INPUT AO
FST - 0006 4175 4175 0002 0W5 F6 6 B E
TRACK CHAIN 4175 0002

FUT WOO OOW WW WOO WW
EST 77W 6210 0013 1377 0421 127? H KK DOJ

FNT - 1601 15W WW WW 13W NAR R
FST - 0006 4176 4176 0004 0W5 F6 6 D E
TRACK CHAIN 4176 0W5

FUT OWO OWO WW WW WOO
EST 77W 6210 0013 1377 0421 1277 H KK DQJ

0315

OUTFIL

FNT - 1725 2406 1114 WW 15W OUTFIL M
FST - 0W7 4205 4205 0W1 0105 G7E7E AAE
TRACK CHAIN 4205 0003

FUT
EST

OOW WOO WOO OOW woo
7702 6210 W13 1377 0421 1302

H KK DBKB

0320

ZZZZZCO

FNT - 3232 3232 3203 3301 1007 ZZZZZCOAHG
FST - 0006 4175 4175 0W1 W05 F6 6 A E
TRACK CHAIN 4175 W02

FUT
EST

WW WW WOO WW WOO
77W 6210 W13 1377 0421 1277

H KK DSJ

0323

ZZZZZC2

FNT - 3232 3232 3203 3SW 1507 ZZZZZC2 MG
FST - W06 4177 4177 0W2 0307 F6 6 8CG
TRACK CHAIN 4177 0002

FUT
EST

OOW WW WW WW WOO
77W 6210 0013 1377 0421 1277

H KK DGJ

0326

OUTPUT

FNT - 172S 2420 2524 OOW 1200 OUT PUT J
FST - W10 6742 6742 0W1 0005 H 7 7 A E
TRACK CHAIN 6742 0W1

FUT
EST

WOO OOW 0700 OOW WOO G
7704 4210 3226 1377 0412 130S

7HZVK DJKE

0331

NRF1

FHT - 1622 0634 W W W W 1 5 W N R F 1 H
FST - 0W7 4210 4210 0002 0705 G7H7H BGE
TRACK CHAIN 4210 W03

FUT
EST

WOO WOO WW WOO WW
7702 6210 W13 1377 0421 1302

H XK 0«KB

0334

NRF2

FNT - 1622 0635 WW WW 1500 NRF 2 H
FST - 0006 42W 4200 0W1 0705 F7 7 AGE
TRACK CHAIN 42W 0003

FUT
EST

OOW WW WW WW WOO
77W 6210 W13 1377 0421 1277

H KK DSJ

0337

LIST

FNT - 1411 2324 WOO WOO 1200 LIST J
FST - W10 7052 7052 0001 WD5 H ) ) A E
TRACK CHAIN 7052 W01

FUT

OOOO

EST

7704 4210 3226 1377 0412 1305

FNT - 3232 3232 3220 2000 1200 ZZZZZPP J

FUT

0342

RA ■
OOOOOW

ZZZZZPP

CP,2.
C
M

DUMP OO

22 . 1 5 . 0 4 . 8 3 / 0 6 / 0 2 .

OOW

07W

0700

OOW

WOO

83/06/02. 22.36.18.

DSDI

7HZVK DJKE

PA 6 E

NOS 2

CDC NETWORK OPERATING SYSTER

FST - W10 7053
TRACK CHAIN 7053 0W1

7053 W01 OWS H S 1 A E

EST

7704 4210 3226 1377 0412 1305 7HZVK DJKE

0345

ZZZZORB

FNT - 3232 3232
FST - 0010 7054
TRACK CHAIN 7054 0W1

0415 02W 1200 ZZZZDMB J
7054 0W1 W05 H = ■ A E

FUT
EST

WW WOO 07W WW WOO G
7704 4210 3226 1377 0412 1305 7HZVK DJKE

0350

ZZZZZDN

FNT - 3232 3232
FST - 0007 4216
TRACK CHAIN 4216 W22

3204 1600 1500 ZZZZZDN H
4216 0022 0703 G7N7N RGC

FUT
EST

WW WOO WW WW WOO
7702 6210 0013 1377 0421 1302

H KK DOKB

Figure 6-9. Sample CP Directive Output

6-72 NOS Version 2 Analysis Handbook

Revision M

Printer Output Listing Examples

Example 4:
Figure 6-10 illustrates the printer output listing produced by the MST directive
(dump mass storage/track reservation table). The MST is listed in two columns. The
left column is read from top to bottom, perhaps across page boundaries, and continues
at the top of the right column. The track reservation table is listed in single column
following the MST.
RA
K S T. 1 3 .
DUMP
22
O0OO0W CH 09.52.49. 86/05/06. CDC NETWORK OPERATING SYST t i l

DSDI

NOS

86/05/06.

10.01.2b.

PA G E

EQUIPMENT 013 - MASS STORAGE TABLE
KUHBER OF TRACKS IDOL 014170 31S0 Y/ FZ6+SA
tr INTERLOCK / COUNTS 0000
LENCTH
OF
TRT
0632
FIRST
AVA I L
TRACK
PTR
*U5
HUM
AVA I L A B L E
TRACKS
2301
CTI/DS PILB/CT ISX OVF ACCL 014171 0 j-ha
RESERVED
000
DA ECS CHAIN FIRST TRACK 0000
DIRECT ACCESS FILE CRT 0012
FIRST
TRACK
IQFT
*6I5
REDEFINITION
S TAT U S E S
01
ALL KF UKLOADE0/ESROR IDLE 0
RESERVED
0
FLAC/KST LIKK OSV ADDR SDCL 014172 00010120 AAP AY W
H S T / T R T U P D AT E C O U N T 0 0 0 1 3 1 6 1 2 7
XF INDEX/CPUMIR INTERLOCKS 00
FIRST TRACK LAPF ALCL 014173 4042 575 58 5
LABEL
TRACK
4000
FIRST TRACK PERMITS 4043
N U H B E R . C ATA L O G T R A C K S 0 0 4 0
FIRST
TtACK
D AT
OOOO
FAMILY OR PACK NAHE FFCL 014174 1515060000000b KHF A
DEVICE
NUHBER
01
DEVICE AL LIMIT LOWES/UPPER 00
REL
UHIT
K U LT I U N I T
DEV
0
MM
UNIT
K U LT I U N I T
DEV
0
USER NUM PRIVATE PACK FUGL 014175 00000000000000
CONT LBL TRK/DEV RES MASKS 577777
FLAGS AND DAT INDEX MDCL 014176 1001 HAC8DI ACS
FT-HT FLAG •/« SECTOR LIMIT 0343
RESERVED
0 4 11 0 0
DRIVER
INDEX
ol
SECTOR
LIMIT
0343
TRACK TO BE FLAWED HVCL 014177 OOOO
RESERVED
OOOOOOOOOOOOO
RESERVED
UHIT
rLAGS
000
CLOBAL LHSIAL AREA ISGL 014200 OOOOOOOOOOOOOOOOOOOO
I2GL014201 OOOOOOOOOOOOOOOOOOOO
RES/DEVKE
S TAT S
"^
0,4M2
°
5
0D
SUSPECT/REST*. ACTIvm °
O LT S TA K D I K G R E Q I T S T 5 0 0
UNIT
INTERLOCKS
°000
CURRENT
POSITION
*0°0
NEXT
JEST
POSITION
WOO
CHANNEL
2
04
CHANNEL
1
04
A L L O C AT I O N
FLAGS
DILL
014203
OOOO
RESERVED POR CDC
0030
•PIT* ORD OF FIRST UNIT
OOOO
DEVICE FLACS
MEHORK TYPE - 3 BIT VALUE
CPU TYPE - 3 SIT VALUE
PP PATH TYPE - I BIT VALUE
"„
RESERVED
00
ALGORITHM INDEX
05

UHIT RESERVE COUNT DULL 014204 O
U
CUKUL TOT UNIT RES COUNTS
00
PF INTERLOCK / COUNTS
OOOO
RESERVED
00
MACHINE INDEX - 1
0)
CKPT FLG/SYSTEH TABLE TRACK
OOOO
FAMILY IDLE STAT/ACT COUNT
WOO
LOCAL STATUS FLACS STLL 014205 OOOOOO
06 A
ERROR STATUS
00
MACHINE ID
334)
CURRENT USER COUNT DAP
OOOO
NEXT EST ORDINAL IK CHAIN
000
LOCAL STATUS
SEDEF IN PROC/HULL EQ DDLL 01420b
RESERVED
ORIGINAL NO. OF UNITS - 1
CURRENT NO. OF UNITS - I
EQUIPMENT UNIT LIST
0000000000000001
LOCAL 1NSTAL AREA ISLL 014207 oooooooooooooooooooo
R E S E R V E D T R L L 0 1 4 2 1 0 00000000000000
BH4
FWA OF TRT
021637
VER1F FAILURE THRESHOLD 0)4211 0001
ACMA- / A
RESTRICT ACTIVITY THRESHOLD
03)5
LOU SPACE THRESHOLD
0)46
RECOVERED ERROR THRESHOLD
0050
UNRECOVERED ERROR THRESHOLD
000)
VERIFIFICATION FAILURE CUT 0)4212 OOOO
RESERVED
OOOOOOOO
RECOVERED ERROR COUNT
OOOO
UNRECOVERED ERROR COUNT
oooo
RESERVED
0 1 4 2 1 3 oooooooo
ERROR DATE/TIKE
oooooooooooo
RESERVED FOR CDC HCLL 014214 oooooooo
MST WRITE FLAG
oooo
PP INTERLOCK BIT MASK
00000400
RESERVED 014215 OOOOOOOOOOOOOOOOOOOO
014216 oooooooooooooooooooo
014217 oooooooooooooooooooo

TRACK RESERVATION TABIX
0 2 1 6 3 7 4 0 0 0 0 4 0 0 1 4 0 0 2 4 0 0 3 4 W 4 4 0 1 7 1 1111 S A 5 B 5 C 5 D 5 0
0 2 1 6 4 0 * 0 0 0 4 4 0 0 5 4 0 0 6 4 0 0 7 4 0 1 0 0 2 1 7 1 1111 5 E 5 P 5 C 5 H B 0
0 2 1 6 4 1 - K W 1 0 4 0 11 4 0 1 2 4 0 1 3 4 0 1 4 W 1 7 1111 5 I 5 J 5 K 5 L 0
021642 «0014 4013 4016 4017 4020 0217 1 1111 5HSN5O5PB0
021643 tO020 4021 4022 4023 U.1 2 4 0 11 7 1 — 1111 5 Q S R 5 S 5 TA O
Track Link
Byte Ordinal

Statu* Bit*

Figure 6-10. Sample MST Directive Output

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-73

Printer Output Listing Examples

Example 5:
Figure 6-11 illustrates the printer output listing produced by the C, D, and E
memory dump directives (instruction parcel, byte, and word format, respectively). The
same portions of central memory are dumped in each format. Auto page eject has
been disabled using the EJOFF directive to allow listing the output from all three
memory dump directives on one page.
C,50,110.

OUHP 01
C - FORMAT OUKP.
1 6 . 5 2 . 11 . 8 2 / 0 1 / 0 6 . CSC NETWORK OPERATING SYSTEM.

OOOWSO WWO 00OW OWOO OOOOO
WW052 OOOW OOWO WWO 07240 S
OOOW53 30766 01030 10057 43001 X HXHE XA
0000054 34131 44234 12147 302W 1KL71JL B
W0WS5 01633 01401 0W34 17761 A XLA C6
OOW0S6 OOWO WOW WWO 07164
0WWS7 77775 12230 W320 OWW (RX Z
WOW60 W751 1W00 WOW WOOO I
CH

0 , 5 0 , 11 0 ,

WOO OOOO
3010 0574
3412 1473
0100 0341
WOO OOOO
3W0 3200
WOO WOO

77770
OOOW
OOOOO
OQOOO
W042
WWO

WWO WWO
OWW 01065
OOOW WOOO
OOOW OOWO
71100 WOOO
WOW OWOO

ooooo
34137
WOW
51426
WOW
OOOW

00WO70 OOOW 033W 24040 40000
0000071 74500 W122 250W 07421

WW072 74647 56475 12W0 WOOO
OOW073 00033 36401 W007 30005
W00074 W033 56404 W035 00025
0000075 W03S 56406 W057 50002
W00076 WOOO OOOOO OOWO WOW
0WW77 OW07 754W 004W 07200
W00100 OOWO OOWO OOOW OWOO

0 TOO
/ ARU 0 W00107 W054 13700 01065 34117 E64 AFS60

7240
5
3001 X HXHE XA
0200 1KL71JL 6
7761 A XLA C6
7164
WW (RX I
WW
I

0000061 7777 OWO WOO WOO WW
OOW062 WW WW W01 0653 4137
00W063 OOW WW WOO WW WOO
0000064 WW OOW WW 0005 1426
W00065 W04 2711 WOO OWO WOO
O00W66 OOW OOW OOW OOW OOW

0000072 7464 7564 7512 WOO OWO J
AFS64 W00073 W03 3364 OIW 0073 0005 CO A E
0000074 0003 3564 0400 0350 0025 C2 0 C/ U
ELV OOW075 0W3 5564 06W 0575 0002 C F E B
WI W00076 OWO OOW OOOO OWO OOOO
0WW77 OOOO 7754 OOW 40W 72W * 5
0000100 WOO WOO OOOO WOO WOO
0 T0t>
ARU 8 W00107 0005 4137 0001 0653 4117 E64 AFS60

OOOW52
00W0S3
W00054
OW0055
000WS6
OW0057
0000060

WW
3076
3413
0163
OOW
7777
W75

WW050
WW054
0000060
00W064
000W70
0000074
W00100
WW104

OOOWOOOOWOOOWWW OOOOOWWWWOOWWO W0OO0WW0W0007240 30766010301005743001
341314423412147302W 01633014010W3417761 0W0WOOOOW0O007164 777751223W0320WW0 1KL71JL B A XLA C
W7511WWW0W000W 7777OWO0WWWWW0 00000000000106534137 OOWOOOOOOWOOWOWO I
000W0W0WW0051426 WO42711OW0W00OOW OOOOOOOWOOWOOOOWO OOOOOOOOOOOOOOOOOOOO ELV 0W1
W00W330024O4O4O0W 74500W122250W07421 746475647512WW00W 000333640100W730005 0 TOO / ARU
OW33564040003SOW25 0003SS6406000S7SOW2 OOWOWWOOOOOOOWW 0000775400W4W072W C2 0 C/ U C Ft
WWOWWOWOOOQWOO wooowwwwowoow owoowwwwwooooo wwowooowoooowoo
000WWW0WW00O0W 00OOOOWO0W0000O0W OOOOOOOWWOOWOOOW 00054137000106534117

E , 5 0 , 11 0 .

CO A
C2 0

0 - FORMAT OUKP.

OOOCOSO WOO WOO WW OOOO OOW
W W
6010
1442
3014
WOO
5122
11 W

W00061
00W062
W00063
0000064
OOW065
0000066

82/01/20. 16.22.27.

0000070 WW 0033 0024 0404 OOW
WW071 7450 W01 2225 WOO 7421

FORMAT OUHP.
HXHE XA
(RX 1

Figure 6-11. Sample C Directive Output

6-74 NOS Version 2 Analysis Handbook

Revision M

Printer Output Listing Examples

Example 6:
Figure 6-12 illustrates the printer output listing of the system file name table
produced by the FNT CMR dump directive. This table is printed in the same format
as that produced by the D memory dump option (refer to example 5).

RA =

wwwo

FNT.
OUKP 00 DSDI
C N 1 2 . 3 1 . 3 1 . 8 3 / 0 6 / 1 2 . C O C N E T W O R K O P E R AT I N G S Y S T E M N O S 2

83/06/12.

1 2 . 3 3 . 11 .

PA G E

SYSTEM FILENAME TABLE
0W247O6 2331 2324 0515 OOW 1W0 SYSTEM
W024707 W06 4005 OOW WW OOW FSE
0W24710 2223 3004 4137 OWO 13W RSX064
0W24711 0010 4463 OOW OOW OOW H9
W024712 2223 3026 4137 OOW 13W R5XV64
0W24713 0010 4201 OOW OOW OOW H7A
00024714 2022 1706 1114 03W 13W PROFILC
0W24715 W10 5410 OOW WW WW H'H
00024716 2601 1411 0425 23W 13W VALIDUS
0W24717 0010 6504 OOW OOW OOW H 0
tWixfiO 2601 1411 0425 23W 13W VALIOUS
W024721 WOS 4215 OOW OOW OOW E7N
00024722 0000 WW WW WOO W07

00024723 OOW WW OWO WW WOO
00024724 OOW OOW WW OOW W10
0W2472S OOW WW WW WW WW
W024726 OOW WW OOW WW 0011
OW24727 OOW WW WW OWO OWO
00024730 OOOO WW OOW OOW W12
W024731 WW WOO WW WW WOO
0W24732 OOW OOW OOW WW W13
00024733 WOO OOW WW WW OWO
0W24734 OWO OOW OOW WW W14
00024735 WW WW WW WW WOO
0W24736 WW OOW WW WW 0015
00024737 OOOO WW WW WW OOW

W024740 OWO WOO WW WW W16
H 0W24741 OOW OOW OOW OOW WW
W024742 OOW OOW OOW OOW W17
I 00024743 WW WW OOW OOW WW
0W24744 OOW WOO OOW WW 0020
J 0W24745 WW WW OOW OOW OOW
00024746 OOW WOO WW WW W21
K W024747 OOW OOW OOW OOW WW
00024750 OWO WW WW WW W22
L W024751 OOW OOW OOW OOW OOW

Figure 6-12. Sample FNT Directive Output

0$ss

Revision M

Express Deadstart Dump Interpreter (DSDI) 6-75

Printer Output Listing Examples

Example 7:
Figure 6-13 illustrates the printer output listing produced by the PRORF directive for
CYBER 180 model 990 and 995 machines.
1 R A • P R O R F.
0000000 CH

09.06.46. 85/07/2*.

ftUNP 00
COC NETWORK OPERATING SYSTEM

8S/08/07. 17.23.56.

RADIAL HCI « 1
IOU CURRENT INSTRUCTION REGISTER
0 0000 0800 0000 2000
1 OOOO 2000 0000 007B
2 0080 0000 0000 0000
3 0000 0000 0000 0078
4 FFFF EOOO FOFF EFOF
5 FFFF F30C FOFF 1603
6 0003 EOOO OOFF CO40
7 SCFf EOOO OQFO EOOO
EXECUTINS WORDS
ACU HZ
OOOO
ACU H3
0040
ACU M4
OOOO
OOOO
BOP
OOOO
EPN SCH
OOOO
epn tin
OOOO
IBU CS
OOOO
OODO
INU MAP
OOOO
INU IBS
FFFF
LSO
OBOO
SVA BN
ODOO

OF SOFT CONTROL MEMORIES
2000 oooo OOOO
OOOO 0060 OOOO
OOOO oooo OOOO
0800 oooo OOOO
OOOO oooo 0800
4V00 C001 C200
OOOO 0100 F200
OOOO oooo OOOO
OOOO oooo OOOO
OOOO 0030 4AF2
FFFF FFFF FFFF
OOOO OOOO OOOO
oooo BFFF F019

ERROR INFORMATION TABLE
0 OOOO OOOO OOOO F200
1 OOOO OOOO 0101 FZ10
2 OOOO OOOO 0202 F220
OOOO OOOO OEOE F2E0
OOOO OOOO OFOF F2F0

INSTRUCTION BUFFER STACK
0 C70D 9322 OBOO AAOA
1 F81Q 2BA6 AF32 F2S0
2 »»«2 9012 1000 0004

8042 225* 6C60 4224
44C6 EBCA 8E66 CI10

REGISTER UNIT
AO OOOO 1004 OOOO 67»0
A1 OOOO FFFF 8000 OOOD
A2 OOOO FFFF 8000 OOOO
OFFF 03F2 4E41 5500
07FF 03F2 4E41 5300
HISTORT FILE
0 X-REG 0030 OOOO OOOO OOOO
0 A-REC 1003 OOOO OOSE
0 P, N 0002 4640 9C00
1 X-RE4 OOFt COOO 01 AS 48B9
1 A-REC 10FF OOOF ECOO
1 P, N 0002 4644 4B00
X-REO OOOO OOOO OOOO OOOO
A-RES 1B03 OODO OOOO
r, H 0 0 0 2 4 6 0 0 8 0 0 0

Figure 6-13. Sample PRORF Directive Output

6-76 NOS Version 2 Analysis Handbook

Revision M

Install Command
NOS allows you to deadstart from a disk rather than from a tape. To deadstart from a
disk, you must first use the INSTALL command to install a deadstart file that you
specify to a deadstart disk. The disk that you select must be available on a single-unit
device such as an 844 or 885-11/12,1 and must have the Common Test and
Initialization (CTI) software. (For more information about CTI, refer to the CYBER
Initialization Package User's Handbook.) If the deadstart disk is a shared device in a
multimainframe environment, a full INITIALIZE must have been previously done. The
calling job must be of system origin or you must be validated for system origin
privileges and the system must be in debug mode. In addition, in a secured system,
INSTALL is allowed only from jobs with security administrator privileges.
You must re-execute the INSTALL command if a full INITIALIZE becomes necessary,
because PFDUMP and PFLOAD do not dump or load the system deadstart file (SDF).
The format of the command is:
INSTALL.filename,EQest.
Parameter Description
filename Disk file (assigned to the job) to be installed as an SDF. Default is
SYSTEM, which must be assigned to the job. The name SDF is a
reserved file name and cannot be specified for filename.
INSTALL stops reading the system deadstart file at the first EOF;
therefore, the new running system does not include any changes made
through SYSEDIT after a previous deadstart.
If the deadstart file to be installed is on tape, it must first be copied
to disk before INSTALL can be used.
NOTE
The deadstart file to be installed must contain a valid OPLD directory.
Note that when you use LIBEDIT to update a deadstart file and write
the new deadstart file directly to tape, the OPLD record on the tape
will not contain valid disk addresses. Therefore, if you want the
deadstart file on tape and you intend to later use the INSTALL
command on the deadstart file, you should have LIBEDIT write the
new deadstart file to disk, and then copy the file to tape using the
COPY command (refer to the NOS 2 Reference Set, Volume 3).
est

EST ordinal of the deadstart disk on which file filename is to be
installed.

1. The system deadstart file cannot be installed to an 819, 885-42, 887, or 9853 disk.

Revision M

Install Command 7-1

?*%

K-Display
FLAW

Utilities
K

INITIALIZE
Machine

MREC

Recovery

MREC
Using
Using

(MREC)

and

3.3

Display
Utility

Procedures
with
the
K
without
the

MREC
MREC
Unit

Display

Controller

8
8-8

Display

8-16

Display
..
K
Display

8-17
8-17
8-22

Reservations

8-23

Mass Storage Extended Subsystem (MSE) K Display 8-25

f^'

Network
Display
NAM
NAM
DB
DE
DU
FL
LB
LE
LR
RS
ST

Access

Method
(NAM)
K
Display
Control
Characters
K-Display
Operation
Mode
Maintenance
Commands
Command
Command
Command
Command
Command
Command
Command
...
Command
Command
,

8-27
8-29
8-30
8-32
8-32
8-33
8-33
8-34
8-34
8-35
8-35
8-36
8-37

Queue File Transfer Facility (QTF) K Display f
QTF
Selection
Classes
.
File
Selection
Process
.
Visualizing
the
File
Selection
Process
Queued
File
Size
Index
Queued
File
Size
and
Transfer
Times
QTF
K-Display
Usage
QTF
Operation
Under
RHF
QTF
Operation
Under
NAM
QTF
K
Display
Commands
CLASS
Command
DISABLE
Command
ENABLE
Command
HELP
Command
IDLE
Command
INCLUDE
Command
SCHED
Command
S TAT U S
Command
QTF
Physical
I d e n t i fi e r
K
Display
QTF
Selection
Class
K
Display
QTF
Transfer
K
Display
STOP
Command

8-41
8-41
8-41
8-42
8-44
8-44
8-45
8-45
8-46
8-47
8-48
8-49
8-49
8-50
8-50
8-51
8-52
8-53
8-55
8-57
8-59
8-60

REDEFINE

8-61

Remote

K
Batch

Facility

Display
(RBF)

Display

8-72

Remote
Host
Facility
(RHF)
K
Display
.
,
8-75
RHF
Initiation
>.
8-76
Operator
Interface
:
8-76
RHF
Commands
Under
K
display
,
8-78
Application
Ta b l e
Display
—
8-79
Network
Path
Ta b l e
Display
................
8-81
RHF Commands Available Under Application or Network Path Display ...... 8-84
RHF
Te r m i n a t i o n
8-84
SCOPE 2 Station Facility (SSF) K Displays ...... ,
Operator
Interface
....—
Station
Login
Enabling
and
Disabling
File
Transfers
Station
Recovery
.-..
Station Disconnection and Logout ..... — ..............;..

8-85
8-85
8-85
8-85
8-86
8-86

File
Transfer
Staged
File
Spooled
File

8-87
8-87
8-8&

Limit
Commands
,,.
Transfer
Commands
Transfer
Commands

Tr a n s a c t i o n F a c i l i t y ( TA F ) K D i s p l a y s . . . . . . .
TA F
Initialization
K
Display
,-,.
Restarting
TA F
K
Display
TA F
Status
K
Display
TA F
K-Display
Commands
.
TA F / C R M S t a t u s K D i s p l a y s a n d C o m m a n d s . . . . . . . . . . . . . . . . . . . . .

^ %

8-89
8-89
8-93
8-93
8-96
8-100

~ )

^ %

K-Display Utilities
This section documents the K displays listed next, along with the utilities used to
present them. Other K-display utilities described elsewhere in this manual include the
permanent file utilities, queued file utilities, and the status/control register simulator.
K-display utilities described in other manuals include those for the CDCNET network
(refer to the CDCNET network manuals) and the printer support utility (refer to the
NOS Version 2 Operations Handbook).
K Display

Description

FLAW

Disk flaw mapping.

INITIALIZE

Disk initialization.

Machine Recovery (MREC)

Multimainframe device recovery.

Mass Storage Extended Subsystem
(MSE)

K display of the MSE.

Network Access Method (NAM)

Operator interface to NAM.

Queue File Transfer Facility (QTF)

K display of the QTF application.

REDEFINE

Online reconfiguration display.

Remote Batch Facility (RBF)

K display of the RBF Subsystem.

Remote Host Facility (RHF)

K display of the RHF Subsystem.

SCOPE 2 Station Facility (SSF)

K display of the SSF Subsystem.

Transaction Facility (TAF)

K display of the TAF Subsystem.

Revision M

K-Display Utilities 8-1

K-Display Utilities
/*^k

By using the K display, a job can place information on the console screen and receive
information from the keyboard. The information is passed to the job by DSD. Normally, a*^%
these
displays
are
used
for
utility
programs.
'
The job first issues a request message on the B,0 display, asking you to bring up the
K display.
When this happens, enter:
K.jsn.
jsn

Description

jsn Job sequence name of the requesting job.
Once the display is assigned to a job, you can enter data by typing K. followed by
data. The data is transferred to a specified area of the job's field length when you
terminate the entry. If more than 50 characters are entered as data, the message
LINE

TOO

LONG.

/^^

appears on the screen. DSD does not accept the entry until the data string is
shortened.
K displays are job oriented. The job sequence name associated with each K display
appears at the top of the screen next to the display designator and name.
All parameter entries must be prefixed by K period (K.). However, after pressing CR
or NEXT for the first parameter entry, everything but the K. is erased. This allows
another parameter to be entered without entering K. first. All examples in this /SS%.
section show K. although you may not have to enter it. If you have to enter a DSD
command during parameter entry, backspace to erase the K., enter the command, and
then continue parameter entry by entering K. and the parameter.

8-2

NOS

Version

Analysis

Handbook

Revision

FLAW K Display

FLAW K Display
The FLAW utility reserves (flaws) tracks on any mass storage device during normal
system operation. Each entry identifies an area of mass storage that is unusable
(flawed area) and prevents the system from accessing it. Since 881 and 883 disk packs
normally contain flaw information in the utility sector, the FLAW utility should be
used on an 881 or 883 only to specify additional areas not currently in the utility
sector. Obtain flaw addresses from the customer engineer.
Flawing tracks on mass storage devices is accomplished using the FLAW K displays
(figures 8-1 and 8-2).
K.

FLAW.

AAAM

CURRENT SLF, CLF. SPF, AND CPF ENTRIES
EQ = 0 EST ORDINAL OF DEVICE.
NUM VALUES ENTERED TRT OCTAL VALUES • = DUPLICATE
1
2
3
4
5
6
7
8
9
10
11
12
13
14
ENTER EST ORDINAL.

Figure 8-1. FLAW K Display (Left Screen)

Revision

K-Display

Utilities

8-3

FLAW K Display

FLAW.

AAAM

MASS STORAGE DEVICE FLAWING
SLF, CLF, SPF AND CPF ENTRIES
SLF = NNNN SET LOGICAL TRACK FLAW.
CLF = NNNN CLEAR LOGICAL TRACK FLAW.
SPF = XX SET PHYSICAL TRACK FLAW.
CPF = XX CLEAR PHYSICAL TRACK FLAW.
WHERE
NNNN = VALID LOGICAL TRACK NUMBER.
XX = COO0.T00.SO0 (CYLINDER,TRACK.SECTOR.)
= A0000000 (ADDR/1OB, FOR DE/DP ONLY.)
NUMERIC VALUES ARE CONSIDERED OCTAL UNLESS THE
DIGITS 8 OR 9 APPEAR IN THE NUMBER, OR A *D* IS
APPENDED TO THE NUMBER.
SEE LEFT SCREEN FOR CURRENT ENTRIES,
UP TO 14 ENTRIES ALLOWED

Figure 8-2. FLAW K Display (Right Screen)
All console entry is performed under DSD control. The sequence is:
1. Call the FLAW utility by entering:
X.FLAW.

2. Bring the K display to the left console screen by entering:
K.jsn.

jsn

Description
Job sequence name of the job requesting the K display (the
message REQUEST *K* DISPLAY appears on the B,0 display).

jsn

3. You can bring the flawing instructions up on the right screen by entering KK.
4. Specify the mass storage device on which tracks are to be flawed. Enter:
K.EQ=est.

est
est

Description
EST ordinal of the mass storage device.
^^*\

8-4 NOS Version 2 Analysis Handbook

Revision M

FLAW K Display

0f^S

5. Enter flaws. A maximum of 14 flaw entries is allowed for each call to the FLAW
utility. In addition, there are four types of flaw entries that may be specified. The
general format for the K display entry is:
K.xtk=ta.

Va r i a b l e D e s c r i p t i o n
xtk Specifies one of the following types of flaw entries.
xtk

Description

SPF Sets the track reservation table (TRT) entry for the
specified physical block (track) address(es) in
extended memory or disk to indicate that the block
is unavailable for use.
CPF Clears that TRT flaw entry for the specified physical
block address(es) in extended memory or disk to
indicate that the block is available for use.
SLF Sets the TRT flaw entry for the specified logical
track to indicate that the track is unavailable for
use.
CLF Clears the TRT flaw entry for the specified logical
track to indicate that the track is available for use.
ta Specifies the track address to be reserved. (Refer to table 8-1.)
ta can be one of the following:
ta

Description

trk Logical track address for a disk or extended
memory. (Use with SLF and CLF.) The variable trk
can be any octal number in the specified range for
the particular type of disk drive or extended
memory.
Aaddr Physical block (track) address for extended memory.
(Use with SPF or CPF.) addr is the extended
memory address divided by 108.
Aaddr- Range of physical block addresses for extended
Aaddr memory. (Use with SPF or CPF.)
Ccyl, Physical track address for the disk. (Use with SPF
Ttrk, or CPF.) The variables cyl, trk, and sec can be any
Ssec octal number in the specified range for the
particular type of disk drive.
6. Initiate flawing of the specified device by entering:
K.GO.

Revision

K-Display

Utilities

8-5

FLAW K Display

The FLAW utility provides two messages in the system dayfile that indicate the results
of
the
fl a w i n g
operation.
The
fi r s t
message

is:

^^\

nn TRACKS FLAWED.

Description

nn Octal number of tracks that were successfully flawed.
The second message appears only if some of the flaws specified were not processed.
This occurs when the track specified for flawing is already reserved by the system (but
not as a flawed track). In this case, the following message also appears in the system
dayfile.
nn FLAWS NOT PROCESSED,list.

Va r i a b l e D e s c r i p t i o n
n n O c t a l n u m b e r o f fl a w s n o t p r o c e s s e d .
list List of the logical tracks that were not flawed.
The entries described here are similar to those entered in the APRDECK (refer to
section 3, Deadstart Decks) for flawing a device at deadstart time. However, the flaw
entries specified using the FLAW utility or DSD command INITIALIZE are not
recovered if the device is initialized at deadstart time. Only the flaw entries specified
in the APRDECK will be recovered. If a device is initialized during normal system
operation (INITIALIZE command), all flaws specified in the devices TRT, including ^
those entered using the FLAW utility or INITIALIZE command, will be recovered
providing the device has a good label at the time of initialization. If the label is bad, '**%.
or cannot be recognized, all current flaws are cleared. The left console screen
(figure 8-3) shows all flaw entries made through the FLAW utility and INITIALIZE
command. It lists the flaw entry and its logical track equivalent. If the same logical
track is referenced by more than one flaw entry, an asterisk appears to the right of
those entries, so that you are aware that only the last entry takes effect.

8-6

NOS

Version

Analysis

Handbook

Revision

FLAW K Display

r
K.

FLAW

AAAM

CURRENT SLF, CLF, SPF. AND CPF ENTRIES
EQ = 1 4 E S T O R D I N A L O F D E V I C E .
NUM VALUES ENTERED TRT OCTAL VALUES * = DUPLICATE

1 SLF=4000.
2 SLF=4000B.
3 SLF=4001.
4
5
6
7
8
9
10
11

4000
4000
4001

*
*

12
13
14

SLF=4001.

00&S

Figure 8-3. FLAW Utility K Display (Left Screen)
Table 8-1. Flawing Information for Disks and Extended Memory

Device Type

MNE

Logical
Track
Range1

DV
DW
DD
DG
DI
DK
DJ
DL
DM
DQ
DB
DF
DH
DC
DN
DE/DP

4000-5465
4000-7153
4000-7135
4000-6565
4000-7137
4000-7137
4000-7147
4000-7147
4000-7221
4000-7221
4000-7221
4000-7343
4000-7343
4000-7351
4000-7726
4000-7620

Cylinders/
Device1

Tracks/
Cylinder1

Sectors/
Track1

633
1466
1457
1273
630
630
1464
1464
1511
1511
1511
1562
1562
1565
2601

12
12
12
30
22
23
23
23
50
50
12

24
24
40
57
30
30
30
30
40
40
40
46
13

17
23

1. Numbers are in octal.

Revision M

K-Display Utilities 8-7

INITIALIZE K Display

INITIALIZE K Display
The INITIALIZE command can be used to reconfigure certain removable devices (844-21
and 844-41/44) to suit your needs. For example, if you currently have two single-unit
844 packs (DK-ls), both packs can be initialized and linked together to form a
multispindle device (DK-2). However, this can be done only if the devices to be linked
meet the following requirements:
• Same device type.
• Same channels.
• Same share status (shared or nonshared).
• Removable.
• Not currently in use.
The INITIALIZE command must be entered to set the initialize status for each device
to be chained. Current multispindle devices can also be initialized providing all packs
that form the device are mounted in a logical order as determined by the unit numbers
list on the E,C display. It is only necessary to enter the INITIALIZE command for the
first unit of a current multispindle device. The format of the INITIALIZE command is
described in section 5, DSD Commands.
NOTE
Examine the FAMC and DAFC fields in the family status display (E,F) before
entering the INITIALIZE command. The user count for the device must be zero before ^s%
this
command
is
valid.
/

8-8

NOS

Version

Analysis

Handbook

Revision

INITIALIZE K Display

0^S
yims

The following steps describe the procedures to initialize and (if necessary) flaw tracks
on a mass storage device.
1. Enter the INITIALIZE command for the device(s) to be initialized. Examine the
B,0 display for the following message:
REQUEST *K* DISPLAY.

Note the job sequence name of the job displaying the message is CMS.
2. Activate the K display for that job by entering:
K.CMS.

The INITIALIZE K display (figure 8-4) appears on the left console screen. All
parameters required to initialize and (if necessary) flaw the specified device are
entered through the K display.
K. INITIALIZE.

CMS

M A S S S T O R A G E D E V I C E I N I T I A L I Z AT I O N PA G E 1 O F 2
INITIALIZE EQUIPMENT

014
INITIALIZE R E Q U E S T * T O T A L *
OPTION

ypPk\

DESCRIPTION

EST ORDINAL OF DEVICE (5-777).
EQ = 014
FM = 0
FAMILY NAME OR PACK NAME IF TY=X (1-7 CHAR).
DN = 0
DEVICE NUMBER (1-77).
UN = 0
PRIVATE AUXILIARY DEVICE USER NAME (1-7 CHAR).
TY o 0
ACCESS TYPE (F OR X ).
LA = 0
LOWER ACCESS LEVEL (1-7 CHAR).
UA = 0
UPPER ACCESS LEVEL (1-7 CHAR).
DM = 0
DEVICE MASK (0-377).
SM = 0
SECONDARY MASK (0-377).
NC = 0
CATALOG TRACKS (0-200).
NP = 0
NUMBER OF PACKS (1-7).
ENTER OLD FAMILY NAME.

Figure 8-4. INITIALIZE Command K Display
The K display lists the options used to initialize a device (under the OPTION
column as shown in figure 8-4). Refer to table 8-2 for a description of each option.
Refer to table 8-3 for additional information. The EST ordinal of the device to be
initialized is listed under the INITIALIZE EQUIPMENT heading (see figure 8-4).

Revision M

K-Display Utilities 8-9

INITIALIZE K Display

Table 8-2. Device Initialization Options
Option1

Description

)

EQ EST ordinal of the device to be initialized. For multispindle devices, this
ordinal must be the first of the consecutive units in the multispindle chain.
FM The 1- to 7-character family name. Specifies the permanent file family in
which the initialized device is to be included. All devices must have a
family name or pack name. The name 0 (single character zero) is reserved
and cannot be used. This option cannot be used to change the family name
of the link device in a multimainframe environment. If you specify TY=X,
this option specifies a 1- to 7-character packname to be associated with an
auxiliary device. To clear an existing entry, enter FM=NULL.
DN The 2-digit (octal) logical device number (from 1 to 77s) that uniquely
identifies the device in its permanent file family. This option cannot be
entered if you specify TY=X.
U N T h e 1 - t o 7 - c h a r a c t e r u s e r n a m e . T h i s o p t i o n i s s p e c i fi e d o n l y w h e n " )
initializing an auxiliary device (TY=X). If specified, the device is
considered to be a private auxiliary device. Only the user name specified
will be allowed to create files on the device (use SAVE, REPLACE, or
DEFINE commands). To clear an existing entry, enter UN = NULL.
TY=F Initialized device may contain direct and indirect access permanent files.
However, if you specify DM=0, only direct access files can reside on the
device. If you specify SM=0 and DM=0, the device can contain only
special system permanent files. Indirect access files can reside only on a .A*ms
master
device
(that
is,
DM=£0).
)
TY=X Initialized device is an auxiliary device. This is a mass storage device that
is not part of a permanent file family. An auxiliary device is a
supplementary permanent file storage device that may be privately owned
(UN option specified) or can be shared by many users (UN not specified).
Auxiliary devices can contain direct or indirect access permanent files.
LA Lower limit for the access level of the device. This establishes the lowest
access level of files that can be stored on the device (must not be less than .-*ms
the lower limit for the access level of the device as given in its EST '
entry).
UA Upper limit for the access level of the device. This establishes the highest
access level of files that can be stored on the device (must not be greater
than the upper limit for the access level of the device as given in its EST
entry).
DM The 3-digit (octal) device mask (from 0 to 377s). This option is required
whenever a permanent file master device is being initialized. It defines
which users will have this device as their master device. This option
cannot be entered if you specify TY=X.
1. Device initialization options may be changed only if the total initialization level
(AL) is specified in the INITIALIZE command.
(Continued)

8-10

NOS

Version

Analysis

Handbook

Revision

INITIALIZE K Display
/uSSS*^

Table 8-2. Device Initialization Options (Continued)
Option2 Description
SM The 3-digit (octal) secondary device mask (from 0 to 377s) used to control
the residence of direct access files. This option cannot be entered if you
specify TY=X.
NC Octal number of catalog tracks (from 0 to 200s; must be a power of 2).
This option is used only if the number of catalog tracks specified as the
system default for the device type is not satisfactory.
NP Number of physical units to be included in a multispindle device. The
default value is 1. Each unit to be included in the multispindle chain must
be defined as removable in the current disk status display (E,M).
2. Device initialization options may be changed only if the total initialization level
(AL) is specified in the INITIALIZE command.
Table 8-3. Track Flawing Options
Option1 Description2
SPF Sets the track reservation table (TRT) entry for the specified physical
block (track) address(es) in extended memory or disk to indicate that the
block is unavailable for use.
CPF Clears the TRT flaw entry for the specified physical address(es) in
extended memory or disk to indicate that the block is available for use.
SLF Sets the TRT flaw entry for the specified logical track to indicate that
the track is unavailable for use.
CLF Clears the TRT flaw entry for the specified logical track to indicate that
the track is available for use.
1. Flawing of 881 and 883 disk packs is automatic; only flaws additional to the
current flaw information in the utility sector should be entered.
A0&\

2. Refer to the APRDECK description in section 3, Deadstart Decks, for entry
formats.
3. Enter the INITIALIZE command for each additional device to be initialized. This
can also be done before activating the K display. In either case, only the first
device specified will be listed (by EST ordinal) in the K display. Thus, to update
the K display to show additional devices, enter the following command:
K.RERUN.

If more than one device is listed, they are initialized one at a time as they
appear in the list from left to right. Multispindle devices (more than one EST
ordinal) are considered one device.

Revision

K-Display

Utilities

8 - 11

INITIALIZE K Display

Aem
is

The system has already checked the label on each mass storage device. If the
label was found to be good, it is necessary to enter device initialization options
(requested in messages that appear in the K display) to identify the device. This
is to ensure that the device selected is indeed the correct device to be initialized.
The messages appear automatically and are displayed until the correct options are
entered. If an incorrect option is entered, it is ignored. Refer to table 8-2 for a
description of each option.
Examine the family status display (E,F) to determine the current option values.
The following messages may be displayed and the appropriate response should be
entered. If none of these messages appears, the device label was not recognized or
was found to be bad. In this event, proceed to step 5.
Message

Description

ENTER OLD DEVICE
NUMBER

This message appears if the device to be initialized is a
permanent file family device. Enter the following
response:
K.DN=dev i cenumber.

ENTER OLD FAMILY
NAME

This message appears only if more than one family of
permanent file devices is currently active in the
system. Enter the following response:
K.FM=familyname.

ENTER OLD PACK
NAME

This message appears only if the device to be
initialized is an auxiliary device. Enter the following
response:
K.PN=packname.

ENTER OLD USER
NAME

This message appears only if the auxiliary device to be
initialized is a private auxiliary device (associated with
a specific user name). Enter the following response:
K.UN=username.

The user name is written to the account dayfile when
the device is mounted.
If you discover that the wrong device was specified in
the INITIALIZE command, you can clear the initialize
status for that device by entering:
K.CLEAR.

The device to be processed by the clear entry must be
a valid device. That is, the device cannot have a device
number that conflicts with another device in its family
name or a pack name that duplicates one already in
the system. Its mask bits must meet standard
requirements. The leftmost device in the list of devices
to be initialized is cleared: One of the preceding
messages will then be displayed for the next device to
be initialized (if any) providing the label on that device
is good.

8-12 NOS Version 2 Analysis Handbook

Revision M

INITIALIZE K Display

5. When the following message appears on the K display, enter the options that
specify the new characteristics to be associated with the device when it is
initialized (refer to tables 8-2 and 8-3).
ENTER PARAMETERS

The new options can be entered as a string or one at a time. For example:
K.optioni=valuei,...,optionn=valuen.

or
K.optioni=valuei.
K.option2=value2.
K.optionn=valuen.

If flaw entries are to be specified (refer to table 8-3), they must be entered singly,
as shown in the last example. If the label on the device being initialized was
good, all current flaws on that device are normally recovered. However, if the
label was not recognized or was bad, the flaw entries cannot be recovered and
must be entered (if necessary) using this mechanism. A maximum of 14 flaw
entries are permitted. In addition to the SLF, CLF, SPF, and CPF entries, the
flaw information recorded in the utility sector on an 881, 883, or 885 disk pack is
read during initialization of 844 equipment, and the appropriate areas are
reserved by the system automatically.
If the NP option is specified (NP > 1), the device is to be initialized as a
multispindle device. In this case, the number of packs specified by NP indicates
the number of spindles to be linked. This is the next n number of devices waiting
to be initialized. Each device must be defined as removable and mounted on
consecutive physical unit numbers. To determine if a device is defined as
removable, examine the disk status display (E,M). If the units are configured
correctly, the label on each unit is checked. If any label is not recognized or is
bad, that unit is free for initialization and chaining. However, if the label is good,
the message
ENTER IDENTITY OF EQest

appears in the K display (est is the EST ordinal of the device). Enter one of the
following responses.
K.DN=devi cenumber.
K.FM=fami 1yname,DN=devicenumber.
K.PN=packname.
K.PN=packname,UN=username.

This is a precautionary measure to ensure that the devices specified are the
correct devices to be chained.
6. After all the necessary options have been entered for a specific device, enter the
following command to proceed with the initialization.
K.GO.

If more devices are waiting to be initialized, repeat steps 4 through 6 of this
procedure for each device.

Revision

K-Display

Utilities

8-13

INITIALIZE K Display

Example 1:
Suppose you want to create and initialize a multispindle device by linking spindles
from two separate units. Assume your EQPDECK has the following entries:
EQ40=DL,ST=OFF,UN=4,CH=27/30.
EQ41=DL,ST=OFF,UN=5,CH=27/30.

and you want to initialize multispindle device EQ40, which consists of units 4 and 5.
Enter the following commands:
ON,40.
ON,41.

INITIALIZE.AL,40,41.
MOUNT,40.
MOUNT,41.
K.CMS.

Enter device initialization options as described in steps 4 and 5.
K.NP=2.

When the message ENTER IDENTITY OF EQest appears in the K display, respond as
described in step 5.
K.GO.

8-14

NOS

Version

Analysis

Handbook

Revision

INITIALIZE K Display

0ms
Example 2:
Assume that you want to initialize a multispindle device and your EQPDECK already
defines the device as a multispindle device:
EQ40=DL,ST=OFF,UN=4/5,CH=27/30.

In this case, enter the following commands:
ON.40.

INITIALIZE,AL,40.
MOUNT,40.
K.CMS.

Enter device initialization options as described in steps 4 and 5.
K.GO.

Example 3:
Suppose you want to initialize a single-spindle device and your EQPDECK defines the
device as a multispindle device:
E04ODL,ST=OFF,UN=4/5,CH=27/30.

Mount the pack you want to initialize on unit 4 and enter the following commands:
ON,40.

INITIALIZE.AL.40.
MOUNT,40.
K.CMS.

Enter device initialization options as described in steps 4 and 5.
K.PN=1.
K.GO.

0ms
Revision

K-Display

Utilities

8-15

Machine Recovery (MREC) Utility K Display

Machine Recovery (MREC) Utility K Display
When a machine that has been in a multimainframe configuration has a malfunction
that requires a level 0 deadstart, before you can begin the deadstart, the machine
recovery utility program (MREC) must be run on every machine that shares devices
with the machine that is not working properly. MREC releases local mass storage
space on the shared devices and clears interlocks set before the malfunction occurred.
For example, assume that machines A and B share disk unit 12 and machines B and
C share disk unit 13 as shown in figure 8-5.

MACHINE
B

MACHINE
A

DISK
UNIT
12

MACHINE
C

DISK
UNIT
13

Figure 8-5. Machine Configurations
If machine A must be deadstarted using a level 0 deadstart, MREC must be run on
machine B to recover disk unit 12. Machine C need not be involved since it is not
aware of the existence of disk unit 12. However, if machine B must be deadstarted
using a level 0 deadstart, MREC must be run on machine A to recover disk unit 12
and on machine C to recover disk unit 13.
NOTE
Once MREC has been run for an inoperative machine, any level of deadstart on the
machine other than 0 is not possible.

8-16 NOS Version 2 Analysis Handbook

Revision M

MREC Procedures

/#^V

MREC Procedures
The MREC utility can be used through keyboard entry to a K display or by direct
keyboard entry under DSD or DIS control without using the K display.

Using MREC with the K Display
The following procedure describes K-display usage for MREC operations.
1. Call the MREC utility by entering this DSD command:1
X.MREC.

2. Examine the DSD system status display (B,0). When MREC is scheduled to a
control point, it is indicated on the B,0 display. The message
REQUEST *K* DISPLAY

appears in the message field for that control point.
3. Activate the K display for that control point by entering:
K.jsn.

jsn

Description

jsn MREC job sequence name.
The K display for MREC (figure 8-6) appears on the left console screen.
The MREC left screen K display lists all of the devices that are shared by the
machine on which MREC is being run. The machine identifier (MID) of this
machine is also given. Information describing the shared devices is given in the
following format.
eq type un dn fm/pn mids sharing device
Header

Description

eq EST ordinal of the shared device,
type

Device

type,

un Unit number of the device,
dn

Device

number,

fm/pn Family name/pack name.
mids sharing Machine identifiers of other machines that are currently
device accessing the device. If there is an * by the machine
identifier, the machine is determined to be down.

1. Under DIS control, the command MREC calls the MREC utility.

Revision

K-Display

Utilities

8-17

Using MREC with the K Display

K. MREC.

jsn

hh.mm.ss . yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA
NOS version
LVLO
LVL7
MACHINE RECOVERY UTILITY

TYPE UN

10
11
12
13
14
15
16
17
20

DJ
DJ
DJ
DJ
DL
DI
DI
DI
DJ

30
40

PAGE 1 OF 1
MIDS SHARING DEVICE

FM/PN
PACKV2

MAINTV2
SYS606
SYST06

73
73
73

72
72
72

71
71
71

70
70
70

R4IAE

y^^lt

ID OF DOWNED MACHINE = 72
EQ(S) TO RECOVER = ALL

Figure 8-6. MREC K Display (Left Screen)

8-18 NOS Version 2 Analysis Handbook

Revision M

Using MREC with the K Display

4. The MREC right screen K display contains the parameters and commands that
may be selected. Refer to table 8-4 (MREC parameters) and table 8-5 (MREC
commands) for more information. To activate the MREC right screen K display
(figures 8-7 and 8-8), enter:
KK.

5. Enter the MREC parameters in the following format:
K.parami=valuei,param2=value2 paranv1=valuen.

The parameters entered (and error messages, if any) are displayed on the lower
portion of the MREC left screen K display.
6. If you want to reset the parameters to their default values or refresh the device
descriptions on the MREC left screen K display, enter:
K.RERUN.

The parameters can then be reentered.
7. Enter the desired parameters and initiate MREC processing by entering:
K.GO.
When processing is complete, the message
PROCESSING COMPLETE
appears at the bottom of the left screen.
8. After all MREC operations are complete, end the MREC utility by entering:
K.STOP.

Revision

K-Display

Utilities

8-19

Using MREC with the K Display

Table 8-4. MREC Parameters
Parameter Description
ID=id

The 1- or 2-character machine identifier of the inoperative machine that
is to be processed. This parameter must be entered before processing can
take place.

EQ=est

EST ordinals of the devices to be processed. Only devices shared between
the machine that is down and the machine on which MREC is running
are processed. The form of the entry is:
EQ=esti,est2,....estn.

If you omit this parameter, EQ=ALL is assumed. In this case, all
devices shared between this machine and the inoperative machine are
processed.
OP = x

You can enter this parameter only when using the K display (that is, it
cannot be used if the MREC utility is called by a command) and then,
use it only if a unit or controller cannot be accessed by MREC due to
physical hardware reservations. Its use is invalid if a unit reservation is
not in effect.
x Description
R Directs the MREC utility to release all unit reservations (using the
GRENADE function; refer to section 2, Deadstart) for 844-41/44
equipment.
I Directs the MREC utility to ignore certain functions on the
equipment for which the reservation message was issued. Functions
that do not require the unit to be accessed are still performed.

Table 8-5. MREC Commands
Command Description
GO. Directs the MREC utility to proceed with processing the entered
parameters.
RERUN. Reinitializes the device descriptions and parameters on the K display and
reruns the MREC utility.
STOP. Terminates the MREC utility and ends the K-display interaction.
+ Pages the left screen K display forward to the next screen.
Pages the left screen K display backward to the first screen.
) Pages the right screen K display forward to the next screen.
( Pages the right screen K display backward to the previous screen.

8-20 NOS Version 2 Analysis Handbook

Revision M

■«*^ii\

Using MREC with the K Display

/$m\

MREC.

jsn

MREC

PAGE 1 OF 2

PARAMETER DESCRIPTIONS
ID
EQ

O
P

MID OF DOWNED MACHINE TO PROCESS.
EST ORDINALS OF DEVICES SHARED BETWEEN THIS MACHINE
AND DOWNED MACHINE TO PROCESS. ENTER AS
EQ=XXX,XXX XXX. THE DEFAULT IS EQ=ALL.
MAY BE ENTERED IF 844 RESERVE SITUATIONS OCCUR.
THE RESPONSE APPLIES ONLY TO THE CURRENT SITUATION.
OP=I IGNORE CURRENT DEVICE.
OP=R CLEAR ALL UNIT RESERVES ON THAT CONTROLLER

K DISPLAY COMMANDS
G
O
RERUN
STOP
+

INITIATE PROCESSING OF DEVICES SPECIFIED.
REINITIALIZE K-DISPLAY AND RERUN PROGRAM.
TERMINATE PROGRAM.
PAGE LEFT DISPLAY FORWARD.
PAGE LEFT DISPLAY BACKWARD.
PAGE RIGHT DISPLAY FORWARD.
PAGE RIGHT DISPLAY BACKWARD.

Figure 8-7. MREC K Display (Right Screen) (Page 1 of 2)
MREC

PAGE 2 OF 2

DESCRIPTION OF TABLE ENTRIES.
EQ
UN
DN
FM/PN
MIDS SHARING DEVICE
* (BESIDE MID)

EST ORDINAL OF EQUIPMENT.
UNIT NUMBER.
DEVICE NUMBER.
FAMILY OR PACK NAME.
MACHINE ID-S OF OTHER MACHINES
CURRENTLY SHARING THE DEVICE.
THE MACHINE IS DOWN. IT CANNOT BE
DETERMINED IF MACHINES RUNNING IN
SHARED RMS MODE ARE DOWN.

Figure 8-8. MREC K Display (Right Screen) (Page 2 of 2)

0ms

Revision M

K-Display Utilities 8-21

Using MREC without the K Display

Using MREC without the K Display
You can also call the MREC utility and specify the appropriate parameters without
using the K display. You can do this by making a single keyboard entry (under DSD
or DIS control) in the following format:
X.MREC(param1=valuei,param2=value2 paramn=valuen)

The parameters (parami = valuei) are described in table 8-4. The ID = id parameter must
be entered.
When the MREC command is entered with parameters, the K display is not activated
and processing occurs automatically. If an error occurs using this procedure, the
message
REQUEST *K* DISPLAY

appears on the DSD B,0 display. Activate the K display and continue as described
under Using MREC With the K Display earlier in this

8-22

NOS

Version

Analysis

Handbook

Revision

section.

MREC Unit and Controller Reservations

MREC Unit and Controller Reservations
When attempting to access a device, MREC may find the controller access or unit
reserved by another machine. When this occurs, the following message appears on the
left screen K display.
EQest,CHCC, CONTROLLER RESERVED.
or
EQest,UNUU, UNIT RESERVED.

Va r i a b l e D e s c r i p t i o n
est EST ordinal of the device.
cc
0ims

Channel

number.

uu Physical unit number (from 0 to 778).
Assuming the inoperative machine is the machine holding the reservation, you can
clear the reservation or direct MREC to clear it by using the following procedures:
To clear a controller reservation, initiate deadstart on the machine that is down.
To clear a unit reservation, perform one of the following procedures:
• On a device that is connected to a 7155 controller, initiate deadstart on the
machine that is down.
• On a device that is not connected to a 7155 controller, toggle the OFF LINE/ON
LINE switch on the back of the drive to OFF LINE and then back to ON LINE.
• If none of the preceding procedures can be performed, select the OP = R parameter
to clear an 844 device reservation.

/0ms

Revision

K-Display

Utilities

8-23

MREC Unit and Controller Reservations

NOTE
Do not select the OP=R parameter unless the other reservation clearing procedures
cannot be performed. It is recommended that all machines in a multimainframe
environment be put in IDLE status or put in STEP mode when you select the OP=R
parameter.
Once the correct action has been taken, enter
K.GO.

to continue processing. If the reservation is still not cleared, the appropriate reserved
message reappears on the left screen K display. Repeat one of the reservation clearing
procedures described above or enter:
K.OP=I.

This directs the MREC utility to ignore certain functions on the device. Processing may
then continue.
If a device or controller in an independent shared device multimainframe environment
is reserved by a down machine, the previously mentioned messages appear on the
system 'status display (B,0) instead of on the K display. Use the procedures already
described to clear the reservation.

8-24 NOS Version 2 Analysis Handbook

Revision M

Mass Storage Extended Subsystem (MSE) K Display

00ms

Mass Storage Extended Subsystem (MSE) K Display
MSE uses the K display to present messages that require your action. You can use the
MSE K display to reply to these messages and to open and close staging/destaging
operations. You can also use the MSE K display to display a specific storage module's
ON/OFF status, the number of DRDs within the storage module for staging/destaging,
and other information including the job sequence name, file name, user index, and
PRU count for the files being processed. In addition, you can set the maximum number
of DRDs to be used for staging/destaging operations within a specified storage module.
When MSE enters messages into the K display, a request for the K display appears
on the B,0 display. Enter K,MSE to activate the display for MSE. After you have
responded to all K-display messages, the request for the K display terminates.
The MSE K display provides space for two messages with up to three lines per
message. If you request information about a specific storage module, the message
area is replaced by the information concerning the storage module. Figures 8-9 and
8-10 show the message and storage module formats of the MSE K display.
Valid MSE commands are:
Command

Description

K.m.GO.

Enters a GO response to the message at message ordinal m.

K.STAGE.

Toggles staging operations between open and close. Staging is
normally open (permitted).

K.DESTAGE.

Toggles destaging operations between open and close. Destaging
is normally open (permitted).

K.SMi.

Displays information for storage module i (i is an SM identifier
A through H). The display shows SM ON/OFF/MAINTENANCE
status, the number of DRDs for staging/destaging, and DRD
activity including the job sequence name, file name, user index,
and PRU count for the files being processed.
The display also shows if a DRD is being used for staging or
destaging, a DRD is under control of a utility, or the state of a
DRD is maintenance mode, off, or idle.

K.SMi,DRD=ST=s.

Sets the maximum number of DRDs to be used for staging
within storage module i (i is an SM identifier A through H). s
is an integer 0 through 2; an entry of 0 turns off staging for
SMi.

K.SMi,DRD=DS=d.

Sets the maximum number of DRDs to be used for destaging
within storage module i (i is an SM identifier A through H). d
is an integer 0 through 2; an entry of 0 turns off destaging for
SMi.

MSE clears a message when an acceptable action is taken. Usually this action is
entering a GO response to the message at message ordinal m. However, for actions
such as emptying the exit tray on a storage module, the message is cleared when the
hardware status indicates the action has occurred and you enter the GO response.
Refer to appendix B of the NOS Version 2 Operations Handbook for the appropriate
action for each message.
0^S.

Revision M

K-Display Utilities 8-25

Mass Storage Extended Subsystem (MSE) K Display

- MSE SUBSYSTEM - OPEN STAGE

RTRQ*

A ^ S

OPEN DESTAGE -

1 . - # — —-Message ordinal

VALID COMMANDS
K .X.GO.
CLEARS ORDINAL *X*
K .STAGE OR K.DESTAGE TOGGLES OPEN/CLOSE
K.SMI
SELECTS SM • I* INFORMATION
K.SMI.DRD°ST"X
SETS MAX »X* STAGE DRDS
K.SMI,DRD=DS=Y
SETS MAX •¥• DESTAGE DRDS

*Number of
stage requests
Malting to
become active
within SSEXEC

Figure 8-9. MSE K Display (Message Format)
- MSE SUBSYSTEM - OPEN STAGE

RTRQ=

OPEN DESTAGE -

SMI STATUS ON
X MAX DRDS FOR STAGING
Y MAX DRDS FOR DESTAGING

JSN
DRDO STAGE - WXYZ
DRD1 DESTAGE - ABCD
VALID COMMANDS
K.X.GO.
K.STAGE OR K.DESTAGE
K.SMI
K.SMI,DRD=ST=X
K.SMI,DRD=DS=Y

FILE
UI
FILENAM USRIDX
FILENAM USRIDX

PRU-S
PRUCNT
PRUCNT

CLEARS ORDINAL *X*
TOGGLES OPEN/CLOSE
SELECTS SM *I* INFORMATION
SETS MAX *X* STAGE DRDS
SETS MAX *Y* DESTAGE DRDS

Figure 8-10. MSE K Display (Storage Module Format)

8-26 NOS Version 2 Analysis Handbook

Revision M

Network Access Method (NAM) K Display

Network Access Method (NAM) K Display
The NAM K display provides a common, centralized interface by which network
applications (CS, NS, NVF, or NETOU) can communicate with the host operator (HOP).
Figure 8-11 shows the format of the NAM K display. Table 8-6 explains the fields
that appear on the NAM K display.

data area

message
Alert Line
HOP Message Line
Response Line

ALERTS

appl app2 app3
hop message 1i ne
appname operator entry

app4 app5

HOP

repeat message

Figure 8-11. NAM K-Display Format
Table 8-6. NAM K-Display Fields
Field

Description

data area

The portion of the screen that receives the output or diagnostic
message as a result of a command that you entered. This portion of
the NAM K display is operated as a scrollable paged device. Each
line of data enters the display at the bottom of the data area and
forces the previous lines to shift up by one line. The previous top
line is lost. However, whenever you turn the page-wait status on
and more than a screen full of information is written to the data
area, the prompt MORE DATA., is displayed on the bottom line of
the data area. The display remains fixed until you enter the +
character to display the next page of information (refer to Display
Control Characters later in this section).

message

The system prompt READY., indicates that you can make
additional keyboard entries. The system prompt MORE DATA.,
indicates that you can enter + to see more data.

appl...app5 The alert line is a list of applications requesting your attention,
hop message line This field contains a message received from another host,
appname

The name of the application (CS, NS, NAM, NVF, or NETOU) with
which you are currently interacting.

operator entry

This field contains up to 40 characters of the last command that
you entered. Commands of more than 40 characters are truncated.

repeat message

Whenever a command cannot be accepted because the system was
not done processing a previous command, you get the system
prompt REPEAT., in this field. Repeat the command.

Revision M

K-Display Utilities 8-27

Network Access Method (NAM) K Display

NAM supports both the right and left screen K displays. The right K display provides
help
information.

"**%.

The NAM K display is available at all times during NAM execution, the message
REQUEST K DISPLAY appears on the B,0 display when the K display is not
assigned to NAM and some application has requested operator intervention. You must
assign the K display to NAM to interact with NAM or an application.
You assign the K display to NAM by entering:
K.NAM.

Figure 8-12 shows the NAM K display as it appears when you initially assign it.
READY..
ALERTS
NAM

Figure 8-12. NAM K Display
The NAM K display has two operating modes:
• NAM mode.
• Application mode.
Initially, the display is in NAM mode. The appearance of NAM indicates that you are
interacting directly with NAM.

8-28

NOS

Version

Analysis

Handbook

Revision

Display Control Characters

Display Control Characters
You can use the following four characters to control the NAM K display. They are
valid in both NAM mode and application mode. Each of the following characters must
be entered in the first character position after K.
Character Description
When in application mode, the * character causes the display to revert
to NAM mode. The last command is aborted and any information
generated by the application, after the asterisk is entered, is discarded
by NAM. The page-wait status is automatically turned on. The *
character is ignored if the display is already in NAM mode.
When in application mode, the / character aborts the last command
without altering the assignment of the NAM K display. The / character
always results in a READY., prompt.

When in NAM mode, the / character is ignored.
When in application mode, the + character turns the page-wait status
on, if the current page-wait status is off. If the current page-wait status
is on, then the command K.+ displays the next available page of
information. The page-wait status is always on in NAM mode. The
page-wait status is initialized to off each time you enter application
mode. Therefore, whenever you select an application, the page-wait
status automatically changes from on to off and you can set it as
desired.
The - character turns off the page-wait status. The - character is
ignored if entered in application mode while the page-wait status is off.
Any attempt to turn the page-wait status off while in NAM mode is
ignored without sending any diagnostic message.

Revision

K-Display

Utilities

8-29

NAM K-Display Operation

NAM K-Display Operation
Initially, the display is in NAM mode. The application mode is invoked by a NAM
mode command that indicates the application with which you wish to interact. The
application mode is indicated by the appearance of the name of that application in the
appname portion of the response line (refer to figure 8-10). In application mode, all
entries except the asterisk are passed by NAM to a previously designated application.
An asterisk character returns the display to NAM mode.
Entering any command (processed either by NAM or by an application) immediately
causes the command to appear in the operator entry field. When processing of the
command completes, the prompt READY., appears in the bottom line of the data
area. If you key something in, other than one of the display control characters *, /,
+ , or - before the prompt READY., appears, the character is displayed in your entry
field but the command is not acted upon and the message REPEAT., appears to the
right of your entry.
Table 8-7 describes the commands for assigning the K display to one of the
applications CS, NS, NVF, or NETOU, and other frequently used commands. If
appname or the remote host number are invalid or the application is not currently
active, you will receive a diagnostic message. These commands are available in NAM
mode only.
Table 8-7. NAM Mode Commands
Command

Description

K.AP = appname

Assigns the NAM K display to the specified application. The
application name appears in the appname portion of the
response line (refer to figure 8-10). appname is one of the
supervisory programs CS, NS, NVF, or NETOU. The
command satisfies any alert request posted by the application.
When you type the application name, that application name
is removed from the alert line, the page-wait status is turned
off, and the last page of the application's recent history buffer
appears in the data area of the display (refer to Recent
History Command in section 15, Network Operations.

K.AP

Assigns the NAM K display to the application whose name
appears in the leftmost position of the alert line. The
page-wait status is turned off and the last page of the
application's recent history buffer appears in the data area of
the display.

K.HELP

Displays information about the NAM mode commands on the
right K display.

K.IG=appname

Causes NAM to ignore all alert requests from the specified
application. If the application had an alert request pending,
its name is removed from the alert list. NAM informs the
application that its alert request was acknowledged and
ignored. The rest of the display remains unaltered. This
command is cancelled automatically when you enter the
AP = appname command. The assignment of the NAM K
display is not altered by the IG=appname command.
(Continued)

8-30 NOS Version 2 Analysis Handbook

Revision M

.A^m\

NAM K-Display Operation

Table 8-7. NAM Mode Commands (Continued)
Command

Description

K.IG

Causes NAM to ignore all alert requests from the application
whose name appears in the leftmost position of the alert line.
NAM informs the application that its alert request was
acknowledged and ignored. The rest of the display remains
unaltered. This command is cancelled automatically when you
enter the AP=appname command.

K.END

Clears the NAM K display. It causes the data area of the
display to go blank but leaves the alert line and response
line unaltered. The END command is used to stop the
generation of the status display (figure 8-12). Otherwise, if
the K display is dropped, NAM automatically ends after 60
to 90 seconds.

K.SEND,rrr,string.

Causes NAM to send the message text if a logical link exists
between the specified remote host and this host. This
command applies only to hosts that are connected using 255x
NPUs, since no logical link exists between hosts that are
connected through either a public data network or a
CDCNET network. Use the NAM ST command to determine
which hosts are connected.
Parameter Description
rrr Host node number of the remote host (from 1
to 255).
string

Message text of no more than 40 characters.

The following message is displayed on the specified remote
host's NAM K display after the alert line.
hh.mm.ss. FROM sss string

Va r i a b l e D e s c r i p t i o n

0*^S

K.ST

Revision M

hh.mm.ss

Time the message is received.

sss

Host node number of the sending host (from 1
to 255).

string

Message text of no more than 40 characters.

Causes the NAM status display to appear on the K-display
screen.

K-Display Utilities 8-31

NAM Mode Maintenance Commands

NAM Mode Maintenance Commands
While in NAM mode, the HOP can enter the following network maintenance
commands. The commands are sent to NAM or to applications to determine the status
of the network and aid in the debugging of network problems. The HOP may select
NAM or a single network supervisory application or NAM and all network supervisory
applications using the following commands:
Command Description
DB2 Activates the online debugging code.
DE2 Deactivates the online debugging code.
DU2 Causes NAM to dump its field length and/or request an application to
dump its field length.
FL Changes NAM's maximum field length.
/ * ' ^ % k

LB2 Begins the logging of network traffic in the debug log file.
LE2 Ends the logging of network traffic in the debug log file.
L R R e l e a s e s t h e d e b u g l o g fi l e .
RS Dumps the statistics data to a permanent file, resets the statistics
counters to 0 (zero), and continues gathering statistics.
ST Causes the NAM status display to appear on the K-display screen (refer
to figure 8-13).
DB Command
The debug begin (DB) command causes NAM to turn on its online debugging code
and/or request an application to turn on its online debugging code.
The command format is:
DB=mode.

mode Description
ALL NAM turns on its online debugging code and requests all applications to
turn on their online debugging code.
appname NAM requests the specified application to turn on its online debugging
code. The specified application must be accessing the network or you will
receive a diagnostic message.
NAM NAM turns on its online debugging code.

2. These commands are supported by the network supervisory applications CS, NS, and NVF. They are
ignored by IAF, TAF, and many other network applications.

8-32

NOS

Version

Analysis

Handbook

Revision

DE Command

DE Command
The debug end (DE) command causes NAM to turn off its online debugging code and/or
request an application to turn off its online debugging code.
The command format is:
DE=mode.

mode Description
ALL

NAM turns off its online debugging code and requests all applications to
turn off their online debugging code.

appname NAM requests the specified application to turn off its online debugging
code. The specified application must be accessing the network or you will
receive a diagnostic message.
NAM NAM turns off its online debugging code.
DU Command
The dump (DU) command causes NAM to dump its field length and/or request an
application to dump its field length.
The command format is:
DU=mode.

mode Description
ALL

NAM dumps its field length and requests all applications to dump their
field length.

appname NAM requests the specified application to dump its field length. The
specified application must be accessing the network or you will receive a
diagnostic message.
NAM

Revision M

NAM dumps its field length.

K-Display Utilities 8-33

FL Command

FL Command
y*^^?\

The field length (FL) command changes NAM's maximum field length to the specified
value. If the field length specified is less than NAM's current maximum field length or
NAM's running field length plus 10008, you will receive a diagnostic message.
If NAM reaches its maximum field length, use the FL command to increase NAM's
maximum field length. If the K display is in application mode when NAM reaches its
maximum field length, NAM automatically switches the K display to the NAM mode.
Until you enter the FL command, all other NAM commands are rejected and NAM
stops servicing the network. Frequent need for this command indicates that the initial
field length for NAM is inadequate and should be increased by changing the MAXFL
parameter of the NIP command described in the NOS Version 2 Installation
Handbook.
The command format is:
F L = fl .

Parameter

Description

fl Specified maximum field length in octal, fl must not exceed 3600008. If
it does, NAM issues a diagnostic message to the K display.
LB Command
The log begin (LB) command causes NAM to begin logging network traffic in its debug
log file and/or request an application to begin logging network traffic in its debug log
file (refer to the NAM Version 1 Host Application Programming Reference Manual for
information on creating the application's log file).
The command format is:
LB-mode.

mode

Description

ALL NAM begins logging network traffic in its debug log file and requests all
applications to begin logging network traffic in their debug log files.
appname NAM requests the specified application to begin logging network traffic in
its debug log file. The specified application must be accessing the network
or you will receive a diagnostic message.
NAM NAM begins logging network traffic in its debug log file. NAM must be
installed with the network trace option or this command is ignored. Refer
to the NOS Version 2 Installation Handbook for more information.
To release the debug log file, enter the log release (LR) command.

<**^
''**%.

8-34

NOS

Version

Analysis

Handbook

Revision

LE Command

LE Command
The log end (LE) command causes NAM to end logging network traffic in its debug log
file and/or request an application to end logging network traffic in its debug log file.
The command format is:
LE=mode.

mode Description
ALL NjAJVI ends logging network traffic in its debug log file and requests all
applications to end logging network traffic in their debug log files.
appname NAM requests the specified application to end logging network traffic in
its debug log file. The specified application must be accessing the network
or you will receive a diagnostic message.
NAM NAM ends logging network traffic in its debug log file.
To release the debug log file, enter the log release (LR) command.
LR Command
The log release (LR) command causes NAM to release its debug log file (if one exists)
and/or request an application to release its debug log file. When the local debug log
file is released, its contents are copied to a permanent file. Logging continues on a new
local debug log file.
The command format is:
LR=mode.

mode Description
ALL NAM releases its debug log file and/or requests all applications to release
their debug log files.

appname NAM requests the specified application to release its log debug file. The
specified application must be accessing the network or you will receive a
diagnostic message.
NAM NAM releases its debug log file.

Revision M

K-Display Utilities 8-35

RS Command

RS Command
The reset statistics (RS) command causes NAM to dump its statistics to a permanent
file and restart gathering statistics and/or request an application to dump its statistics
to a permanent file and restart gathering statistics (refer to the NAM Version 1 Host
Application Programming Reference Manual for descriptions of the network statistics).
You can use this command to help analyze NAM and/or application performance.
The command format is:
RS=mode.

mode Description
ALL NAM dumps its statistics to a permanent file, resets the statistics
counters to 0 (zero), and continues gathering statistics and/or requests all
applications to dump their statistics to permanent files, reset their
statistics counters to 0 (zero), and continue gathering statistics.
a p p n a m e N A M r e q u e s t s t h e s p e c i fi e d a p p l i c a t i o n t o d u m p i t s s t a t i s t i c s t o a ]
permanent file, reset its statistics counters to 0 (zero), and continue
gathering statistics. The specified application must be accessing the
network or you will receive a diagnostic message.
NAM NAM dumps its statistics to a permanent file, resets the statistics
counters to 0 (zero), and continues gathering statistics.

8-36

NOS

Version

Analysis

Handbook

Revision

ST Command

ST Command
The status (ST) command causes the NAM status display (figure 8-13) to appear on the
K-display screen.
The command format is:
S T.

The NAM status display provides status information regarding all applications,
couplers, and logical links currently active in the host. This display is refreshed
periodically to display the current conditions of the applications and logical links.
The first line of the NAM status display contains the network invocation number
(NIN), host regulation level (REG LVL), the number of applications accessing the
network, and the maximum field length of NAM.
NIN = 014

REG LVL =

NO OF APPLS = 5

MAXFL = 100000

JSN
IAF
RBF
TAF

STATUS

NCN AC

NDM

AABA
AAAM

001000

HN
01

NSM NHM

LOG- LINK

HN
01

TN
01

0^ms
APP
IAF
RBF
TAF
TVF
NVF

EST
054

oooooo
oooooo
oooooo

NSM

30
10

oooooo

H
0

NLM

IVTSTAT
0000

S T NCN
S
44

PRUST
46125

TIME UP
07.54.35
08.10.00
08.25.46
08.04.00
09.09.45

NPUREJ

NHDQ

NLDQ TIME UP
08.01.30

Figure 8-13. NAM Status Display

Revision M

K-Display Utilities 8-37

ST Command

The NAM status display shows the application status entries in the following format:
app

jsn

status 1

ncn ac nsm ndm timeup

Header Description
app

Name of the application. The application name may be one of the following
CDC-written applications or a site-written application.
app

Description

C S C o m m u n i c a t i o n s S u p e r v i s o r.
I A F I n t e r a c t i v e F a c i l i t y.
I T F I n t e r a c t i v e Tr a n s f e r F a c i l i t y.
MCS Message Control System.
N J F N e t w o r k J o b E n t r y F a c i l i t y.
NETFS Network File Server.
NETLS Network Log Server.
NLTERM Network Log Terminator.
NETOU Network Operator Utility.
N S N e t w o r k S u p e r v i s o r.
N V F N e t w o r k Va l i d a t i o n F a c i l i t y.
PLATO Plato-NAM Interface.
P S U P r i n t e r S u p p o r t U t i l i t y.
PTF Permanent File Transfer Facility.
PTFS Permanent File Transfer Facility Server.
QTF Queued File Transfer Facility.
QTFS Queued File Transfer Facility Server.
R B F R e m o t e B a t c h F a c i l i t y.
TA F T r a n s a c t i o n F a c i l i t y.
T C F Te r m i n a l C l u s t e r F a c i l i t y.
T L F Ti e L i n e F a c i l i t y.
T V F Te r m i n a l Ve r i fi c a t i o n F a c i l i t y.
VEIAF NOS/VE Interactive Facility.

/J^tK

jsn

Job sequence name of the executing job table entry.

status

Status of the application in octal. Each of the 18 bits (numbered left to
right) represents the following condition:
Bit Number

Description

0
1
2
3
4-5
6
7-14
15-17

Force flag.
Wait flag.
Rollout flag.
ON flag.
Swap flag.
IN flag.
Reserved.
NVF response flags.

8-38 NOS Version 2 Analysis Handbook

Revision M

ST Command

Header Description
^ms

Ignore alert flag. If set to Y, NAM ignores an alert request from the
application. If set to N, NAM accepts an alert request from the application.
This field is blank if the application is not allowed to use the NAM K
display.
ncn

Number of current connections to the application.

Reserved.

nsm

Number of asynchronous supervisory messages currently queued for the
application.

ndm

Number of data messages and synchronous supervisory messages queued for
the application.

timeup Time, in. the format hh.m.ss, that the application became active.
The NAM status display shows the coupler status for all NPU and MDI/MTI coupler
entries in the EST currently being serviced by NAM. These entries have the following
format:
est em hn

nsm

nhm nlm Ivtstat prust npurej

Header Description
est Equipment status table ordinal of the front end NPU or MDI/MTI.
em Equipment mnemonic NP for the NPU or ND for the MDI/MTI.
hn Host node number of the coupler.
nsm Number of asynchronous supervisory messages currently queued for the
coupler.
nhm Reserved.
nlm Reserved.
ivtstat Number of characters transferred downline on interactive connections in
the last 30 seconds.
prust Number of characters transferred downline on PRU connections in the last
30 seconds.
npurej Number of times data was rejected by the NPU.

0§ms.

Revision M

K-Display Utilities 8-39

ST Command

The NAM status display shows the logical link entries in the following format,
hn tn h n s t ncn ac nhdq nldq timeup
Header Description
hn Node number of the NPU or MDI/MTI coupler.
tn Terminal node number of the NPU or MDI/MTI on host-to-network logical
links, or host node number of the remote host on host-to-host logical links.
h Logical link regulation level as reported by the host.
n Regulation level as reported by the NPU or MDI/MTI. n can have the
following values:
n Description
0 Logical link is down or disabled for data.
1 Only asynchronous supervisory messages are allowed.
2 Only asynchronous supervisory messages and high priority connections
are allowed.
3 All network connections are allowed.
s Supervision indicator. If CS is using this logical link to send supervisory
messages, the field is set to S; otherwise, it is blank.
t H o s t - t o - h o s t l o g i c a l l i n k i n d i c a t o r. I f t h i s l o g i c a l l i n k i s b e t w e e n t w o h o s t s , " )
the field is set to H; otherwise, it is blank.
ncn Number of current connections on the logical link.
ac Reserved.
nhdq Reserved.
nldq Reserved.
timeup Time, in the format hh.mm.ss., that the logical link became active.

8-40

NOS

Version

Analysis

Handbook

Revision

Queue File Transfer Facility (QTF) K Display

Queue File Transfer Facility (QTF) K Display
The QTF utility provides a multistreaming capability for transferring queued files
between mainframes using connections through RHF or NAM. QTF allows you to
specify which files are to be transferred. You do this by defining a set of selection
classes. You can define or modify values for selection classes using the CLASS
command described later in this subsection. You can specify a range of file sizes and
the maximum number of simultaneous connections allowed. You can also specify a
number of reserved connections that cannot be used by lower-priority selection classes.

QTF Selection Classes
Selection classes are designated by a single letter in the range from A to L. Selection
class A is the highest priority, and L is the lowest priority.
QTF uses selection classes to find files to assign to the PIDs (physical identifiers) for
remote hosts. Associated with each PID is one or more LIDs (logical identifiers). The
/^N system PID/LID table is created by system program CLDT from the LID configuration
file LIDCMid (refer to LID Configuration File in section 10) and is viewed and
modified using the L-display utility LIDOU (refer to LIDOU L Display in section 9).
QTF reads the system PID/LID table to determine which PIDs have connections
through RHF or NAM and which LIDs are associated with each PID.
File Selection Process
Each copy of QTF has a fixed number of connection slots available. The goal of the
QTF file. scheduling algorithm is to find files for as many of these connection slots as
possible within the constraints of the selection class definitions. On each pass through
its file selection process, QTF proceeds through all defined selection classes from the
highest priority A to the lowest priority L. For each selection class, QTF attempts to
find one file for each available PID that does not already have a file assigned. The file
selection process continues until one of the following occurs:
• All connection slots are in use, or
• All PID/selection class combinations have been checked and
- Are in use, or
- Are unavailable (disabled or the maximum number of connections per selection
class has been reached), or
- No files were found.
• The sum of the reserved connections for higher-priority selection classes is equal
to or exceeds the number of free connection slots.

Revision

K-Display

Utilities

8-41

Visualizing the File Selection Process
A^^S

Visualizing tbe File Selection Process
To visualize the file selection process, imagine that selection classes and PIDs form a
two-dimensional matrix of jacks on a telephone switchboard with PIDs assigned across
the columns and selection classes assigned down the rows. Above each jack is a light.
When a light is flashing, a queued file is available for the corresponding PID/selection
class combination. The plug cables represent the connection slots. A jack can have only
one plug inserted at a time. Inserting a plug into a jack establishes a connection and
causes the light to stop flashing and a file transfer to begin. A plug is removed from a
jack after one or more files have been transferred or a connection error occurs.
Figure 8-14 shows the connection slot array (plugs) and the PID/selection class matrix
(switchboard).
Connecti on
Slots
12
3
4
X

PID
n

SeLecti on
Class

PID
1

PID
2

PID
3

• s a

Figure 8-14. Connection Slot Array and PID/Selection Class Matrix
On each file selection cycle, QTF looks for a free plug cable (an unused connection
slot) and, starting at the upper left corner of the PID/selection class switchboard,
searches across each row in turn looking for a flashing light (queued file matching the
PID/selection class combination). When the plug is inserted into the jack, that
connection is established. If another plug cable is free, the search continues from the
current jack until QTF runs out of plugs or the bottom right corner of the switchboard
is reached.

8-42 NOS Version 2 Analysis Handbook

Revision M

Visualizing the File Selection Process

For each selection class row for which a reserved number of connections is defined,
QTF checks the number of plugs inserted in that row when the rightmost jack for the
row is reached. If the number of plugs inserted is less than the number of reserved
connections, QTF places enough plugs in unused jacks in that row until the number of
reserved jacks is filled, only one free plug remains, or the row is filled; whichever
occurs first.
For each selection class row for which a maximum number of connections is defined
and the maximum is reached, QTF continues searching at the leftmost jack of the
next row down.
You can minimize the number of different operating system calls QTF must make to
cover all of the switchboard jacks. Do this by either minimizing the number of
selection classes (number of rows) or by defining overlapping selection criteria for
selection classes. For example, if selection classes A, B, and C all have the same file
size index range, and QTF does not find a file for a PID in selection class row A,
QTF can consider selection class rows B and C checked as well. If selection class D
has a different, nonoverlapping file size index range, QTF must call the operating
system to check the jacks in selection class D regardless of the results of the checks
for selection classes A, B, and C (assuming that the file selection process has not yet
terminated).

Revision

K-Display

Utilities

8-43

Queued File Size Index

Queued File Size Index
QTF file size selection criteria are specified in terms of a queued file size index. The
NOSTEXT symbols FSI1 through FSI6, defined in NOS common deck PPCOM (refer to
the NOS Version 2 Installation Handbook), allow you to completely and uniquely
partition the range of queued file sizes into seven subranges. Each subrange is
identified by an integer value in the range from 1 to 7, known as a file size index.
The FSIn values define end points for each file size subrange in units of PRUs (640
6-bit characters).
FSI File size subrange
1
2
3
4
5
6
7

0 ^ size < FSI1
FSI1 ^ size < FSI2
FSI2 ^ size < FSI3
FSI3 ^ size < FSI4
FSI4 as size < FSI5
FSI5 ^ size < FSI6
FSI6 ^ size

Each NOS queued file is assigned a file size index value based on its size. This value
is displayed on the DSD Q displays (refer to the NOS Version 2 Operations Handbook).
You can examine the NOS common deck PPCOM to determine the default values for
the FSIn symbols. However, to modify the current values, you need to rebuild
NOSTEXT, the NOS operating system, and QTF under RHP. For each FSIn symbol,
the value of FSIn must be less than the value of FSIn+1.
T h e fi l e s i z e r a n g e s a r e d i s p l a y e d o n t h e Q T F h e l p d i s p l a y ( fi g u r e 8 - 1 5 ) . A - m ^

Queued File Size and Transfer Times
Given a typical set of file size index values, the following shows the approximate file
transfer time in minutes for various line speeds. The time is based on typical line
utilization and only one transfer active through the line. NAM line speed is shown in
minutes.
FSI
1
2
3
4
5
6

8-44

FUe Size
(PRUs)

1200
bps

9600
bps

19.2k
bps

56k
bps

RHF/
LCN

319
21
1.5
<1.0
<1.0
<0.5
34
4.2
2.5
<1.0
<0.5
511
6
8
8.5
4.2
1.5
<0.5
1023
17.0
3.0
<0.5
2047
136
8.5
4095
272
34.0
17.0
6.0
<0.5
<0.5
8191
544
68.0
34.0
12.0
999999 >544 >68.0 >34.0 >12.0 >0.5

NOS

Version

Analysis

Handbook

Revision

QTF K-Display Usage

0$ms

QTF K-Display Usage
The following procedures describe DSD K-display usage for QTF operations. QTF is
used by both the RHF and NAM subsystems.
QTF Operation Under RHF
Normally, QTF is defined as an autostart application in the RHF configuration file
(refer to RHF Configuration Files in section 10). That means a QTF job starts
automatically when the RHF subsystem is initiated. The RHF application table K
display shows how many copies of QTF are defined and how many copies are currently
active.
QTF terminates when the K.IDLE command terminates the RHF subsystem. To
manually terminate a copy of QTF, bring up the RHF application table display by
entering the following commands:
K.RHF.
K.APPL.

When the display appears, enter:
DISABLE,ord.

where ord is the ordinal of an active QTF in the RHF application table display. The
message QTF, NETWORK IDLEDOWN IN PROGRESS should appear in the QTF job
dayfile. QTF completes any files in progress and then ends. If QTF does not terminate
within a reasonable amount of time, use the DSD DROP command to terminate QTF.
If a fault condition occurs, QTF normally restarts itself. To manually restart QTF,
bring up the RHF application table display by entering the following commands:
K.RHF.
K.APPL.

When the display appears, enter:
ENABLE,ord.

where ord is the QTF ordinal in the RHF application table display.
You can determine the jsn of QTF by using the DSD system status display (B,0) and
the RHF application table display. When QTF is active at a control point, it is
indicated on the B,0 display.
Activate the K display for that QTF by entering:
K.jsn.

where jsn is the job sequence name for QTF. The QTF transfer display appears on the
left screen.

Revision

K-Display

Utilities

8-45

QTF Operation Under NAM

QTF Operation Under NAM
Normally, QTF is started by NAMI during NAM subsystem initiation. The NAM status
K display shows how many copies of QTF are currently active.
QTF terminates automatically when the NAM subsystem is terminated. To manually
terminate a copy of QTF, use the NVF IDLE or DISABLE commands (refer to NVF
Control Commands in section 15) to either idle QTF or immediately terminate QTF.
Enter the following commands:
K.NAM.
K.*.
K.AP=NVF.
K.IDLE,AP=QTF. or K.DISABLE,AP<=QTF.

The message QTF, NETWORK IDLEDOWN IN PROGRESS or QTF, NETWORK
SHUTDOWN should appear in the QTF job dayfile. If the IDLE,AP=QTF command is
used, QTF completes any files in progress and then ends. If QTF does not terminate
within a reasonable amount of time, use the DISABLE,AP=QTF command or DSD
DROP command to terminate QTF.
If a fault condition occurs, QTF normally restarts itself. To manually restart QTF,
enter the following command (refer to the NAMI command in section 16):
X.NAMI(RS=QT)

You can determine the jsn of QTF by using the NAM status K display. Bring up the
NAM status K display by entering the following commands:

,-/^^.

K.NAM.
K.*.
K.ST.

Activate the K display for that QTF by entering the following command:
K.jsn.

where jsn is the job sequence name for QTF. The QTF transfer display appears on the
left screen.

.A^m^

8-46

NOS

Version

Analysis

Handbook

Revision

QTF K Display Commands

QTF K Display Commands
QTF commands have the same general format whether they are entered through the K
display or read from an input file using the INCLUDE command.
• Each QTF command must be on one line and only the first 80 columns of a
command line are significant.
• A command consists of a command verb followed by 0 to 10 parameters.
• A command verb and parameters are separated by one or more spaces or a
comma.
• A command is terminated by a single period.
• Most command verbs and parameters can be abbreviated. The exceptions are IDLE
and STOP.
QTF accepts the following K display commands:
Command Description
CLASS Define or modify QTF selection class values.
DISABLE Change the status of QTF elements from enabled to disabled.
ENABLE Change the status of QTF elements from disabled to enabled.

HELP Displays information about the available QTF commands.
IDLE Begins the idle-down process of QTF.
INCLUDE Causes QTF commands to be read from an input file.
SCHED Modify QTF scheduling parameters.
STATUS Displays information about the status of file transfers in progress, PIDs,
or QTF selection classes.
STOP Causes an immediate termination of QTF.
+ Page forward to the next screen of a multipage display.
Page backward to the previous screen of a multipage display.
Comment line (anything following a period is ignored).

/$pn

Revision M

K-Display Utilities 8-47

CLASS Command

CLASS Command
The CLASS command allows you to define or modify QTF selection class values.
The command format is:
K.CLASS,SC=selclass,FSI=fs1,MAXIMUM=max,RESERVE=res.

Parameter Description
selclass Selection class name; specify one character in the range from A to L.
Selection class A is the highest priority class and L is the lowest
priority class. This parameter is required.
fsi

File size index; specify the file size index or range of indexes using
one of the following formats:
Format

Description

fsi File size index in the range from 1 to 7.
fsil..fsiu , File size index range, where fsil ^ fsiu.
* An * specifies all file sizes. It is equivalent to entering
1..7. If FSI is omitted, the default is FSI=*.
max Maximum connections; specify the maximum number of simultaneous
connections for files in this selection class in the range from 0 to the
maximum available connections (specified by the MAXCONS parameter
in the QTF SCHED command) or specify *. If 0 or * is specified, all
connections can be used for files in this selection class. However, only
one connection per PID per selection class is permitted. Default
is 0 or *.
res Reserved connections; specify the number of connections reserved for
files in this selection class in the range from 0 to the maximum
available connections (specified by the MAXCONS parameter in the
QTF SCHED command). If zero is specified, no connections are
reserved for this selection class. For each selection class, the number
of available connections is reduced by the sum of reserved connections
for all higher-priority selection classes. To prevent a possible
overcommitment of connections, QTF allows only mxcons-1 connections
to be reserved. Default is zero.
The following default selection class is defined at QTF initiation:
CLASS,SC=A,FSI»•,MAXIMUM**,RESERVE=0.

which allows one file transfer to any one remote host with no restrictions on file size
and no reserved connections. To modify the default selection class or define other
classes, use additional CLASS commands.

8-48 NOS Version 2 Analysis Handbook

Revision M

z«*^^.

DISABLE Command

DISABLE Command
The DISABLE command changes the status of the selected QTF elements from enabled
to disabled.
The command format is:
K.DISABLE,element.

Parameter Description
element One of the following:
PID=pid
SC = selclass
SC = selclass,PID=pid
Option

Description

pid Physical identifier of a given mainframe. Specify PID = * to
disable all PIDs.
selclass Selection class in the range from A to L. Specify SC = * to
disable all selection classes.
ENABLE Command
The ENABLE command changes the status of the selected QTF elements from disabled
to enabled.
The command format is:
K.ENABLE,element.

Parameter Description
element One of the following:
PID=pid
SC = selclass
SC = selclass,PID=pid
Option

Description

pid Physical identifier of a given mainframe. Specify PID=* to
enable all PIDs.
selclass Selection class in the range from A to L. Specify SC = * to
enable all selection classes.

Revision M

K-Display Utilities 8-49

HELP Command

HELP Command
The HELP command displays the available QTF K display commands, file size ranges
in decimal PRUs, and the parameters for the QTF SCHED command.
The command format is:
K.HELP.

The HELP K display (figure 8-15) appears on the right screen.
HELP
COMMANDS

CLASS,SC=A,FSI=N..N, MAXIMUMS, RESERVED.
DISABLE,ELEMENT.
ENABLE.ELEMENT.
IDLE.
INCLUDE,FILE=PFN.
SCHED,PARAMETERS.
STATUS,TYPE. (TYPE=PID,SC,OR TRANSFER)
STOP.
+ OR
PARAMETERS =
SELSECS=N
ELEMENT = ONE OFMAXCONS=N
SC=X OR *
TIMEOUT=N
PID=XXX OR *
DISABLED
RETRY=N
SC=X,PID=XXX
LDTRFSH»N
X=A,B,C L.

FSI

PAGE 1 OF 1
SIZE 1RANGE

0.
320.
512.
1024.
2048.
4096.
8192.

319
511
1023
. 2047
. 4095
. 8191
.999999

(FILE SIZE RANGES
IN DECIMAL PRUS)

Figure 8-15. QTF HELP K Display (Right Screen)
IDLE Command
The IDLE command causes QTF to idle down and terminate. The message QTF,
NETWORK IDLEDOWN IN PROGRESS appears in the QTF job dayfile and
IDLEDOWN appears on the B,0 display. QTF completes any file transfers in progress
and then ends.
The command format is:
K.IDLE.

QTF does not accept an abbreviation for this command.
To restart QTF, enter the following command:
X.NAMI(RS=QT)

•^585\

8-50 NOS Version 2 Analysis Handbook

Revision M

INCLUDE Command

INCLUDE Command
The INCLUDE command causes QTF to rewind the specified input file and begin
processing QTF commands from that file.
The command format is:
K.INCLUDE,FILE=infile.

Parameter Description
infile File name from which QTF commands are to be processed. QTF
searches for a local file with name infile. If the local file is not found,
QTF attempts to GET or ATTACH permanent file infile from user
name SYSTEMX. If QTF performs a GET or ATTACH, it returns the
file after processing all of the commands. This parameter is required.
A file of QTF commands processed by using the INCLUDE command can itself contain
another INCLUDE command. Upon executing the second INCLUDE command, QTF
switches to the new file and does not read anything following the INCLUDE command
in the old file.

Revision

K-Display

Utilities

8-51

SCHED Command
.-^%.

SCHED Command
The SCHED command allows you to modify QTF scheduling parameters.
The command format is:
K.SCHED,SELSECS=se1 sees,MAXCONS=mxcons,TIME0UT=tmom1 ns,
DISABLE=d1sm1ns,RETRY=maxrtry,LDTRFSH=1dtm1ns.

Parameter Description
selsecs File selection recall period in the range from 1 to 4095 seconds;
specifies the minimum amount of time between attempts to acquire
new queued files. Whenever QTF is unable to fill all connection slots
with files, it waits selsecs seconds before again attempting to acquire
files for unused slots. Default is 20 seconds.
mxcons Maximum simultaneous connection slots (to all hosts) in the range
from 1 to 4. Default is 4 connections.
tmomins Timeout period in the range from 1 to 60 minutes; specifies the
maximum amount of time QTF waits for a reply from a remote host or
access method. For the RHF variant of QTF, tmomins also specifies
how long QTF waits for NAD code conversion resources when
applicable. Default is 2 minutes.
dismins Disable period in the range from 1 to 60 minutes; specifies the amount
of time for which QTF will not attempt transfers to a PID after an
error occurs. You can use the ENABLE command to clear the error
disabled condition. Default is 2 minutes.
maxrtry Maximum retries in the range from 1 to 50 retries; specifies the
maximum number of immediate retries that QTF attempts to complete
a file transfer before error disabling the PID. When QTF cannot
complete a connection request (the connection is rejected by the local
or remote access method or QTFS), QTF disables the PID without any
immediate retrys. Once the PID is disabled, QTF returns the file to
the local queue and does not attempt to acquire any files for LIDs
associated with the PID until either dismins minutes have elapsed or
you use the ENABLE,PID command to enable the PID. Default is 2
retries.
ldtmins PID/LID table refresh period in the range from 1 to 60 minutes;
specifies how often QTF updates its internal tables from the system
PID/LID table. Default is 2 minutes.

8-52 NOS Version 2 Analysis Handbook

Revision M

STATUS Command

STATUS Command
The STATUS command displays the status of selected QTF elements or file transfers.
The command format is:
K.STATUS,display.

display Description

PID Selects the QTF physical identifier K display which shows the status
of PIDs, selection classes for each PID, and the number of queued files
transferred.
SC Selects the QTF selection class K display which shows the selection
class definitions and the number of files transferred.
TRANSFER Selects the QTF transfer K display which shows transfers in progress
and the number of files already transferred.
Each QTF status display consists of a two-line display header and a variable number of
display items. The lower portion of the screen contains a QTF command and message
area. Figure 8-16 shows the general format for the QTF status displays. The display
fields are described following the figure.

S TAT U S , t y p e n n n n n n F I L E S S E N T x x x PA G E n O F m
display header
display item 1
display item 2

display item k
COMMANDIdledown
<

<
<

last
last
opr

cmd
cmd

(1-50)
(51-80)
msg

>
>
>

Figure 8-16. General Format of QTF Status K Display

Revision

K-Display

Utilities

8-53

STATUS Command

Field

Description

type Display type; PID, SC, or TRANSFER.
nnnnnn Number of queued files transferred.
xxx Access method; RHF or NAM.
n C u r r e n t p a g e n u m b e r.
m M a x i m u m p a g e n u m b e r.
last cmd The last QTF command processed. If the command is incorrect, an asterisk
(*) appears in the line above the command to show the approximate
position of the character or parameter in error. If the error is in the
second part of the command (positions 51 to 80), a plus sign (+) appears
instead of an asterisk.
idledown This field contains the message *IDLEDOWN* if QTF is in idle-down
mode; otherwise, this field is blank.
opr msg This field contains an operator message about the last QTF command
processed. Refer to the NOS Version 2 Operations Handbook for message
descriptions.

8-54 NOS Version 2 Analysis Handbook

Revision M

,,>=^S\

STATUS Command

QTF Physical Identifier K Display
Figure 8-17 shows a sample QTF STATUS.PID K display.
STATUS,PID
PID STATUS

nnnnnn FILES SENT RHF
SC DISABLED SC IN-USE

M01 ENABLED
M02 DISABLED
M03 NO LIDS
M04 NO PATH
M05 REJECTING

i\———————\_

PAGE 1 OF 1

—————

Figure 8-17. QTF STATUS.PID K Display
Each entry in the QTF physical identifier display appears in the following format:
pid status sc disabled sc in-use
Header Description
pid

Physical identifier of the remote host specified in the NOS system LID
table.

status

Status of the PID; status can be one of the following:
status

Revision M

Description

DISABLED

The PID was disabled by the QTF DISjABLE
command. Use the QTF ENABLE command to change
the PID status to ENABLED.

ENABLED

The PID is available for file selection for enabled
selection classes.

NO LIDS

No enabled LIDs are associated with this PID in the
system LID table or the PID is disabled. Use the
LIDOU L-display utility to display and modify the
system LID table.

NO PATH

The system LID table does not define a path in
service to this PID through the access method (RHF
or NAM) that is available to this copy of QTF. Use
the LIDOU L-display utility to determine whether an
RHF or NAM path to the PID is defined and its
status. If the path status is OUT OF SERVICE, use
the RHF network path table display or the NAM
status display to display the status of the network
elements linking the two hosts.

K-Display Utilities 8-55

STATUS Command

Header

Description

status

(Continued)
status

Description

REJECTING

QTF has temporarily disabled file transfers to the PID
because QTF was unable to establish a connection to
the PID or was unable to successfully transfer a file
after the maximum number of retries. QTF returns the
PID to ENABLED status after the specified disable
period has elapsed. (Refer to the QTF SCHED command
for descriptions of the RETRY and DISABLE
parameters.) You can use the QTF ENABLE command
to immediately return the PID to ENABLED status. If
the PID returns to REJECTING status, examine the
QTF dayfile to determine whether a connection reject
or a particular file is causing the problem.
Currently, for RHF paths and for some types of NAM
paths, the path status in the system LID table does not
reflect the status of the remote PID or access method
but rather the status of the local host network elements
used to access the PID. Thus, a remote host may be
out-of-service (due to scheduled maintenance, for
example), yet the local system LID table shows the
path status as IN SERVICE. Each time the disable
period elapses, QTF attempts to send files to the PID.
If the access method rejects the connection, QTF
returns the PID to REJECTING status.

sc disabled

Selection classes that are unavailable for this PID. They were disabled
by the QTF DISABLE command. Use the QTF ENABLE command to
enable a particular PID and selection class combination.

sc m-use

Selection classes currently in use for this PID. The QTF transfer display
shows the ordinals for connection slots and the selection class associated
with each slot.

8-56 NOS Version 2 Analysis Handbook

Revision M

STATUS Command

QTF Selection Class K Display
Figure 8-18 shows a sample QTF STATUS,SC K display.
STATUS,SC
SC STATUS FSI RANGE
A ENABLED
B ENABLED
C DISABLED
D UNDEFINED
E UNDEFINED
F UNDEFINED
G UNDEFINED
H UNDEFINED
I UNDEFINED
J UNDEFINED
K UNDEFINED
L UNDEFINED

nnnnnn FILES SENT
MAXIMUM RESERVED

.. 6
.. 6
.. 7

NAM PAGE 1 OF 1
IN-USE AVAILABLE
1
1

2
2

Figure 8-18. QTF STATUS,SC K Display
Each entry in the QTF selection class display appears in the following format:
sc status fsi range maximum reserved in-use available
Header Description
sc

Selection class.

status

Status of the selection class; status can be one of the following:
status

Description

DISABLED The selection class was disabled by the QTF
DISABLE command. Use the QTF ENABLE command
to change the selection class status to ENABLED.
ENABLED The selection class is available for file selection for
enabled PIDs.
UNDEFINED The selection class has not been defined. Use the QTF
CLASS command to define or modify a selection class.
fsi range

File size index range. This field shows the inclusive range of file size
index values that are allowed for this selection class.

maximum

Maximum number of connection slots allowed for files in this selection
class. This field contains dashes (—) if no maximum is specified.

reserved

Number of connection slots reserved for files in this selection class.
This field contains dashes (—) if no connection slots are reserved.

Revision M

K-Display Utilities 8-57

STATUS Command

Header
m-use

Description
Number of connection slots that have been assigned files in this
selection class. This field contains dashes (—) if no connection slots are
in use.

available Number of free connection slots available for assigning files in this
selection class. This field contains dashes (—) if no connection slots are
available.

^■a^v

""^\

8-58 NOS Version 2 Analysis Handbook

Revision M

STATUS Command

QTF Transfer K Display
Figure 8-19 shows a sample QTF STATUS,TRANSFER K display.
STATUS,TRANSFER nnnnnn FILES SENT RHF PAGE 1 OF 1
ACN SC FILE
LID/PID DC DD PRUS STARTED STATUS
1 A ABCD

SV6 M03 PR C8 1234 11.03.45 *START XFR
CONNECTION ESTABLISHED TO M03.

2 A AAED

MFF MFF IN US 22 11.10.00 WAIT REM
ACQUIRED DC=IN, ST=MFF, D0=MA2.

4
Figure 8-19. QTF STATUS/TRANSFER K Display
00ms

Each entry in the QTF transfer display appears in the following format:
a c n s c fi l e l i d1/ pid/pid
i d d cdc d d p r u s s t a r t e d s t a t u s
message

Header Description

acn

Application connection number; this is the ordinal of the connection slot.

Selection class associated with this connection slot.

file

Job sequence name associated with the queued file assigned to this
connection slot.

lid

Logical identifier of the host associated with this connection slot.

pid

Physical identifier of the remote host to which this slot is connected or is
being connected.

Disposition code of the queued file. Refer to the ROUTE command in the
NOS Version 2 Reference Set, Volume 3 for a list of disposition codes
and their meanings.

Data declaration. This field defines the format of the file data during
transfer. Values of C6 and C8 indicate that the file is to be sent in
code-conversion mode. Values of UH, US, and UU indicate that a binary
transfer is to be used.

Revision M

K-Display Utilities 8-59

STOP Command

Header Description
prus

Size of the file in physical record units (PRUs) in decimal. One PRU
contains the equivalent of 640 6-bit characters.

started

This field shows the time (hh.mm.ss) at which the connection to the remote
host was initiated. The time is updated when the connection* is established
and at the beginning of each file transfer sequence.

status

Status of the connection or file transfer; status can be one of the following:
status

Description

ACQ FILE File has been acquired.
CONNECT Issuing connect request.
END CONN Connection terminating.
FILE XFR File transfer in progress.
IDLE Connection established.
QUEUED File transfer successful.
START XFR Initiating file transfer.
STOP XFR File transfer completing.
WAIT ACQ Waiting for acquire queued file response.
WAIT REM Waiting for response from remote host or access method.
message

This field contains the last dayfile message issued by QTF for this
connection slot. Refer to the NOS Version 2 Operations Handbook for
message descriptions.

STOP Command
The STOP command causes QTF to terminate immediately. The message QTF,
NETWORK SHUTDOWN appears in the QTF job dayfile. QTF abandons any file
transfers in progress, returns files to the system I/O queues, and ends.
The command format is:
K.STOP.

QTF does not accept an abbreviation for this command.

8-60 NOS Version 2 Analysis Handbook

Revision M

REDEFINE K Display

REDEFINE K Display
Use the REDEFINE utility to reconfigure 844 and 885-11/123 disk drives online and
thereby logically eliminate a unit that is malfunctioning without performing a level 0
initial deadstart. A single unit or multiunit device4 that fails can be replaced with an
unused unit. Unused units must be available or made available across channels or on
the same channel as the failing unit by physically moving the disk pack from the
failing unit to the replacement unit. Table 8-8 gives the equipment requirements for
reconfiguration.
Table 8-8. Equipment Requirements for Reconfiguration
Operation
To Be
Performed

Special
Considerations

Current Equipment

Replacement

Equipment

Must be unloaded,
removable

Must be in
EST

Must be
unloaded,
removable

Add or
Return a
Unit

Yes

Equipment must
have less than
eight units.

Delete a Unit

Must be removable;
if not unloaded, the
unit must be in the
EST

Equipment must
have at least
one unit.

Replace a
Unit

Not necessary

Yes, if in
EST

The system does
not perform
label verification
on packs that
are unloaded
before the
failing unit is
replaced. If the
unloaded pack is
not moved from
the failing unit
or the wrong
pack is moved,
the system
issues an error
message when
the replacement
unit is accessed.

Recable a
Unit

None.

3. When reconfiguring an 885-11/12 disk drive, a customer engineer must be present.
4. When reconfiguring a multiunit device, all units of the device must be on the same controller(s).

Revision M

K-Display Utilities 8-61

REDEFINE K Display

■'*^%k

NOTE
There are special cases when you cannot perform an online reconfiguration. In these
cases, you must perform a level 0 deadstart and define the failing device to another
drive. The special cases are:
• Reconfiguring an 885-11/12 disk drive that is the only system device defined.
• Reconfiguring an 844 or 885-11/12 disk drive that is the only temporary device
defined.
• Reconfiguring a device designated as an independent shared device.
• Reconfiguring an 819 or 885-42 disk drive.
The reconfiguration sequence follows:
1. Request the reconfiguration of the disk device defined by EST ordinal est by
entering:
REDEFINE,est.

The.message REQUEST *K* DISPLAY appears at the appropriate control point on
the system status display (B,0). You can reenter the REDEFINE command as
many times as there are devices to be reconfigured. Multispindle devices that
include two or more units are considered to be one device.
If an INITIALIZE command is being processed, the REDEFINE entry is not
processed until the initialization is complete.
2. Bring the initial REDEFINE K display (see figure 8-20) to the left console screen
by entering:
K.jsn.

jsn

Description

jsn Job sequence name of the requesting job.
To

bring

the

right

console

screen

d i s p l a y,

KK.

As shown in the left screen of figure 8-20, the current EST description of the
device being reconfigured appears under the heading CURRENT EQUIPMENT
CONFIGURATION. The EST description of the device as changes are made
appears under the heading REQUESTED EQUIPMENT CONFIGURATION. Any
devices listed under IDLED EQUIPMENTS are devices that have been previously
selected by your REDEFINE command but have yet to be processed in the
reconfiguration run.
The left screen K display may not list all relevant devices. If more than one
device is listed, they are processed one at a time as they appear in the list with
one exception: all shared devices are processed prior to nonshared devices.

8-62

NOS

Version

Analysis

Handbook

Revision

enter:

/*^\

REDEFINE K Display

You are guided through the reconfiguration process in two ways. First, by the list
of commands and parameters shown on the right screen K display of figure 8-21,
and second, by the system responses and error messages.
CMS

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
LV L O - LV L 7 M I D = A A N O S v e r s i o n
MASS STORAGE FAILURE RECOVERY
CURRENT EQUIPMENT CONFIGURATION
011 DJ-1 CH24.01 UL=01

REQUESTED EQUIPMENT CONFIGURATION
011 DJ-1 CH24.01 UL=01
CHANGED UNITS

yd^ptoSV,

IDLED EQUIPMENTS
010 DJ-1 CH01.24 UL=00

ST = I

ST « I

Figure 8-20. REDEFINE K Display (Left Screen)
K DISPLAY COMMANDS
CLEAR CLEAR IDLE AND SUSPEND ON CURRENT EQUIPMENT.
END CLEAR ALL DEVICE IDLES AND END *CONFIG*.
GO INITIATE PROCESSING OF ENTERED CONFIGURATION.
RERUN RESTART *CONFIG* UTILITY PROCESSING.
RESET RESET CURRENT EQUIPMENT TO DEFAULT PARAMETERS.
SUSPEND SUSPEND SYSTEM OPERATION ON CURRENT EQUIPMENT.
CH=C1,C2 C1 AND OPTIONALLY C2-ARE NEW ACCESS CHANNELS.
EQ=EEE SET EST ORDINAL EEE TO BE PROCESSED.
UL=U1,U2,... SET UNIT LIST AS SPECIFIED.
UR=UU UNIT UU IS TO BE RECABLED WITH A NEW DRIVE.

Figure 8-21. REDEFINE K Display (Right Screen)

Revision M

K-Display Utilities 8-63

REDEFINE K Display

3. Enter all of the valid parameters (refer to table 8-9) that define the
reconfiguration characteristics for the specified device. Parameters are entered ^^v
s i n g l y. P a r a m e t e r s a r e p r o c e s s e d l e f t t o r i g h t ; n o t e r m i n a t o r i s n e c e s s a r y. ?
If you enter an incorrect parameter (for example, the wrong channel number), the
error can be corrected by entering the correct parameter.
4. Enter
K.GO

to initiate processing of the parameters when all parameters and commands (refer
to table 8-10) have been entered for the specific device. Enter this command after
each set of parameters to signal the system to go ahead with the reconfiguration
you have defined. If more devices remain to be reconfigured, repeat steps 3 and 4.
5. Enter
K.END

to end a reconfiguration run when there are no more devices to be processed.

8-64

NOS

Version

Analysis

Handbook

Revision

REDEFINE K Display

Table 8-9. Reconfiguration Parameters
Parameter Description
CH=ci,C2 Specifies the channel numbers (ci and, optionally, C2) to be used
under the new device definition.
Use this parameter when the entire device is to be redefined to
alternate channel number(s). You can also use it to add or delete
channels from an equipment definition. New channels can be
added by specifying new channel numbers for a defined
equipment. Channels can be deleted by specifying CH = . when
deleting a unit. Acceptable values for ci and C2 are from 0 to 13s
for systems having 10 or less PPs; from 0 to 13s and from 20s to
338 for systems having more than 10 PPs. Leading zeros can be
omitted.
EQ=est Specifies the equipment with EST ordinal est is to be processed.
Enter this parameter when the processing of equipments is order
dependent; for example, when a device must first be made
available before it can replace a failing device. The system
ignores all parameters not processed before you enter the EQ = est
parameter. Parameters entered after EQ=est refer to the
specified equipment until you enter another EQ = est or a
command that causes the next equipment in the list to be
selected for processing.
UL=ui,u2,...,Un Specifies the unit list for the new configuration.
When a unit is to be replaced, added, or deleted, the entire unit
configuration must be entered with this parameter. The
equipment must be unloaded (multimainframe mode) or otherwise
have an unavailable status if a unit is to be added or deleted.
Any number of units can be changed. By specifying UL = . the
current unit configuration is deleted.
NOTE
If the unit number specified in the UL= parameter represents a
unit that is not defined in the EST, the unit number is accepted
without validation. Ensure that the unit number entered
represents a valid device.

0$ms.

UR=un Specifies that the device with unit number un is to be recabled.
This parameter is used when a device is to be physically replaced
by a new device with the same unit number. More than one
device can be specified for recabling at the same time.

jtg^S.

Revision

K-Display

Utilities

8-65

REDEFINE K Display

Table 8-10. Reconfiguration Commands
Command Description
ABORT Discontinues processing of the current command. It is entered only in
response to a detected error condition and is used to initiate error
recovery procedures. This command cannot be followed immediately by
an END command.
CLEAR Clears the suspend and redefinition request status for the current
equipment. Label and read/write verification of the device is performed.
This command should be entered only when no further processing is
desired for the current equipment.
END Terminates the reconfiguration processing. The K-display parameters are
set to the default values as control is returned. This command cannot be
entered immediately after an ABORT command.
GO Initiates the processing of specified reconfiguration parameters previously
entered.
IGNORE Informs the system on which the command was entered to ignore
processing on this device (multimainframe mode only). This command
should be entered during an add or delete unit reconfiguration run on
the machine(s) within the multimainframe complex which, for control
reasons, cannot add to or delete from the specified equipment. Also, you
can use this command to ignore an error message pertaining to a
marginally unacceptable servo timing check, which is performed
automatically when reconfiguring an 885-11/12 disk drive.
NEXT Enter this command in response to an 885-11/12 disk drive servo timing
check that meets requirements. This command causes processing to
continue with the next device or the next step of processing. This
command is valid only when reconfiguring 885-11/12 disk drives.
RECHECK Retries a verification/diagnostic process that previously gave an error.
Only the commands RECHECK, ABORT, and IGNORE are accepted by
the system when an error message is issued.
RERUN Sets the parameters to default values and updates the list of equipment
to be reconfigured.
RESET Resets the parameters to default values.
SUSPEND Causes system processing on the specified device to be suspended
indefinitely while the device is in a not ready state. Only diagnostic
access to the device is allowed. All other jobs accessing the device will
be unable to continue until the device is returned to a ready state. More
than one equipment can be suspended at the same time.

8-66 NOS Version 2 Analysis Handbook

Revision M

REDEFINE K Display

You can stop the reconfiguration procedure by entering either the K.ABORT command
/#^ or the K.CLEAR command (depending on which command is posted in the list of valid
*• commands on the K display). In either case, processing advances to the next device in
the list of devices under IDLED EQUIPMENTS (see figure 8-20).
If the device specified is a shared device in a multimainframe environment and
reconfiguration is not desirable on one or more of the mainframes, use the following
procedure:
1. Enter at the console of each mainframe for which reconfiguration of the shared
device is not desired.
REDEFINE,est.

est

Description

est EST ordinal of the shared device.
*s^

Enter
K.jsn.

jsn

Description

jsn Job sequence name of the job requesting the REDEFINE K
display.
3. Enter
K.IGNORE

and processing on the shared device in the list is ignored by that mainframe. The
machine must wait until the shared device is done with its processing.
4. Enter
K.END

to end the reconfiguration procedure.
Enter either the RERUN or RESET command to clear the IGNORE command.
Figure 8-22 shows the output for a sample reconfiguration run.

/^N

Figure

ORD

TYPE

CHANNELS

UNITS

06
07
10
11
12
13
14

DJ-1
DJ-1
DJ-1
DJ-1
DI-1
DI-1
DI-1

CH26.32
CH26.32
CH32
CH13
CH26
CH32
CH26,32

UL=06
UL=07
UL=01
UL=02
UL=03
UL=11
UL=04

8-22.

Revision

R e c o n fi g u r a t i o n

Run

K-Display

STATUS
ST =
ST =
ST =
ST =
ST =
ST =
ST = I

Output

Utilities

8-67

REDEFINE K Display

Following are examples of the reconfiguration of disk devices and how their status
changes
in
the
REDEFINE
K
d i s p l a y.
Example 1:
This example illustrates returning a unit to the system.
Assume the unit of est ordinal 7, the system's spare disk drive, was used to replace a
failing disk drive. Now that the defective unit has been repaired, it is to be returned
as the unit of the spare disk drive.
Disk configuration before the REDEFINE:
EST Equipment Channel Unit
Ordinal Type Number(s) Number Status
7

DJ-0

I--

Enter the following commands:
Command Description
REDEFINE,7. 7 is the EST ordinal of the shared device.
K,jsn. jsn is the job sequence name of the job requesting the REDEFINE K
display.
K.CH = 32,26 32 and 26 are the channel numbers to be used by est ordinal 7.
K.UL=7 7 is the unit number of the device being returned.
K.GO Initiates the processing of all the parameters and commands entered
for EST ordinal 7.
The system responds with the message:
EQ 7 REDEFINITION COMPLETE.

To end the reconfiguration, enter:
K.END

Disk configuration after the REDEFINE:
EST Equipment Channel Unit
Ordinal Type Number(s) Number Status
7

8-68

DJ-1

NOS

32,

Version

Analysis

Handbook

Revision

/*=%

REDEFINE K Display

0$ms.

Example 2:
This example illustrates reconfiguring a failing unit.
Assume EST ordinal 10 and EST ordinal 11 are defined in the EST display.
Equipment 10 is a spare unit currently not being used. Equipment 11 has a pack
mounted and is the failing device. Before the failing device can be reconfigured, the
spare unit must be removed from the EST. The following stipulations apply when
deleting a unit from the EST:
• If the EST ordinal is defined in a single mainframe environment or if it is not
shared in a multimainframe environment, then having device unavailable status
(U status in the E,M display) for that EST ordinal is sufficient.
• If the EST ordinal is shared in a linked shared device multimainframe
environment, then that EST ordinal must have device unavailable status and be
globally unloaded (U and N status in the E,M display) before a reconfiguration
can be performed.
Disk configuration before the REDEFINE:
EST Equipment Channel Unit
Ordinal Type Number(s) Number Status
10
11

DJ-1
DJ-1

32
13

1
2

I—

To perform the reconfiguration, enter the following commands:
Command Description
REDEFINE,10. 10 is the EST ordinal of the spare device.
REDEFINE,11. 11 is the EST ordinal of the failing device.
KJsn. jsn is the job sequence name of the job requesting the REDEFINE K
display.
K.CH = . Deletes the channel number(s) assigned to EST ordinal 10 from the
EST.
K.UL=. Deletes the unit number of EST ordinal 10 from the EST.
K.GO Initiates the processing of all the parameters and commands entered
for EST ordinal 10.
The system responds with:
EQ 10 REDEFINITION COMPLETE.

Enter the reconfiguration commands for the failing device as follows:
Command Description
K.CH = 32 32 is the channel number that was assigned to EST ordinal 10.
K.UL = 1 1 is the unit number that was assigned to EST ordinal 10.
K.GO Initiates the processing of all the parameters and commands entered
for EST ordinal 11.

Revision

K-Display

Utilities

8-69

REDEFINE K Display

The system responds with:
SPIN DOWN UNIT 02.

02 is the unit number of EST ordinal 11.
After the unit is spun down, the system responds with:
MOVE PACK FROM UNIT 02 TO UNIT 01 AND SPIN UP.

After the pack is moved and the new unit is spun up, the system responds with:
EQ 11 REDEFINITION COMPLETE.

To end the reconfiguration, enter:
K.END

Disk configuration after the REDEFINE:
EST Equipment Channel Unit
Ordinal Type Number(s) Number Status
10
11

DJ-0
DJ-1

00
32

Example 3:
This example illustrates reconfiguring devices across channels.
Units may be reconfigured across channels with the REDEFINE command. Assume )
that EST ordinal 12 is the failing unit (or possibly the failing channel) and is on
channel 26. EST ordinal 13 is the spare unit on channel 32. The following commands
illustrate a reconfiguration across channels.
Disk configuration before the REDEFINE:
EST Equipment Channel Unit
Ordinal Type Number(s) Number Status
12
13

DI-1
DI-1

26
32

3
11

Enter the following commands:
Command Description
REDEFINE,12. 12 is the EST ordinal of the failing device.
REDEFINE,13. 13 is the EST ordinal of the spare device.
K,jsn. jsn is the job sequence name of the job requesting the REDEFINE K
display.
K.EQ=13 Selects the spare unit to be processed first.
K. SUSPEND Suspends the spare unit to clear it from the EST.

8-70

NOS

Version

Analysis

Handbook

Revision

REDEFINE K Display

The system responds with:
/g^v
SYSTEM USAGE OF EQ 13 SUSPENDED.

To continue with the reconfiguration on EST ordinal 12, enter:
K.EQ=12 Selects the failing unit for processing.
K.CH = 32 Assigns the old channel number of EST ordinal 13 to EST ordinal 12.
K.UL=11 Assigns the old unit number of EST ordinal 13 to EST ordinal 12.
K.GO Initiates the processing of all the parameters and commands entered
for EST ordinal 12.
The system responds with:
EQ 12 REDEFINITION COMPLETE.

Disk configuration at this point in example 3.
EST Equipment Channel Unit
Ordinal Type Number(s) Number Status
12
13

DI-1
DI-1

32
32

11
11

I—
IS-

All SUSPEND status flags must be cleared before a reconfiguration run can be ended.
The system therefore automatically selects EST ordinal 13 again for the next EST
ordinal to be processed.
To continue with the reconfiguration, enter:
Command Description
K.CH = 26 Assigns the old channel number of EST ordinal 12 to EST
ordinal 13.
K.UL=3 Assigns the old unit number of EST ordinal 12 to EST ordinal 13.
K.GO Initiates the processing of all the parameters and commands entered
for EST ordinal 13.
The system responds with:
EQ 13 REDEFINITION COMPLETE.

To end the reconfiguration, enter:
K.END

Disk configuration after the REDEFINE:
EST Equipment Channel Unit
Ordinal Type Number(s) Number Status
12
13

DI-1
DI-1

32
26

11
3

J^^S.

Revision

K-Display

Utilities

8-71

Remote Batch Facility (RBF) K Display

Remote Batch Facility (RBF) K Display
Whenever RBF is in operation, user connections and activity are shown in the RBF K
display (refer to figure 8-23).
RBF Version PSR Level of Number of Terminals Number of Batch
Number RBF Software Active (Decimal) Devices Active (Decimal)

REMOTE BATCH TERMINAL STATUS.
RBF VER 1.2- 525 TERMINALS = 1 DEVICES - 2
TERM. DEV. TCLASS. USR/JSN. FAMILY/.
N A M E . T Y P. / S T A T E . F I L E S I Z E . E R R O R S .

FORMS
CODE

L O E T 1 C O . 2 0 0 U T. A A D C N Z D G T Y R .
CR1. STOP.
LP1. GO . AJZA 40

Figure 8-23. RBF K Display
Select the RBF K display with this DSD command:
K.RBF.

Data on the RBF display is updated periodically to reflect the current status of batch
terminals connected to RBF.
Terminals are identified by termname, a unique name defined by the site. Terminals
are displayed in alphabetical order. There are multiple lines on the K display per
terminal; one line for the terminal console, and one line for each batch device (card
reader, line printer, card punch, or plotter).
If there are more terminals and devices active than can be displayed on one screen,
the message
MORE LINES FOLLOW.

appears at the lower left corner of the display. You can display additional screens by
entering:
K.+

The K.+ command advances the display page-by-page and end-around from the last
page to the first. All screens are displayed in a forward direction. Use of the console
input K.- does not move the screen back to the previous display.
Entries in the display have the following format:
term dev tclass usr/jsn family/
name
typ
/state
fi l e s i z e

8-72 NOS Version 2 Analysis Handbook

errors

forms
code

Revision M

Remote Batch Facility (RBF) K Display

Header

Description

term name

Name of the terminal. A unique name, termname, assigned by the
installation during network startup. This field is used for console
devices only.

dev typ

Device type. The device type code is one of the following: •
Code Description
CO

Console device.

CPi

Card punch.

CRi

Card reader.

LPi

Line printer.

PLi

Plotter.

The ordinal number, i, of the device can range from 1 to 7.
tclass/state

If this field is in the same line as the termname, the contents of the
field is the terminal class mnemonic (refer to the Remote Batch
Facility Reference Manual). If this field occurs in a line not
containing a termname, the device status code is one of the following:
Code

Description

ABRT File in transmission is to be discarded.
CONN Device is connected (initial state).
END Device stops transmission at EOI.
ENDA File being aborted; device will stop at EOI.
ENDC End connection.
ENDI Device will stop at EOI; idle down requested.
GO Device is ready for input.
NULL Console is not connected, but RBF devices are. This code
appears only when the device type is a console (device type
code CO).
PREC Preconnect status (device connection not complete).
STOP Device is not ready for transmission of data.
STPA Device is stopped; current file to be aborted.
STPE Device is stopped.
STPI Device is stopped due to idle down request.

Revision M

K-Display Utilities 8-73

Remote Batch Facility (RBF) K Display

Header

Description

usr/jsn

If a file transfer is in progress, jsn is displayed in this field. If no file
is being transferred, then the user name appears in this field.

family/filesize

If this field is in the same line as the termname, the content of this
field is the family associated with the username. The user index and
family combination determine the terminal identifier used by the
system for routing jobs. Otherwise, the contents of this field is the
size of the output file in PRUs.

errors

Contents of this field, if present, is one of the following error
messages:
Message

Description

DISK Data has been lost due to an unrecoverable disk
ERROR failure.
DISK FULL A disk-full indication was received while RBF was
attempting to write to disk.
NOT The device the user specified is not available (for
READY example, the line printer is out of paper or the card
reader has a card jam).
QUEUE The system input queue has reached its limit of jobs
FULL waiting to begin execution.
forms code

Forms code for output devices as specified by the user and defined by
the site.

8-74 NOS Version 2 Analysis Handbook

Revision M

Remote Host Facility (RHF) K Display

Remote Host Facility (RHF) K Display
The Remote Host Facility (RHF) links NOS to a loosely coupled network (LCN)
providing transfer of permanent files, queued files, and maintenance facilities for the
LCN hardware. Each system in an LCN configuration is connected to one or more LCN
trunks by network access devices (NADs). Several types of NADs are available,
allowing the connection of various types of computer systems to an LCN. Each system
has an RHF that provides some or all of the following capabilities.
RHF runs at a control point and contains an operator interface package, control
tables, network application code, and the PP routines that drive the RHF network
hardware.
The following applications are also available as part of RHF:
Application Description
/fpSN

PTF, PTFS Permanent File Transfer Facility (PTF) and Permanent File Transfer
Facility Servicer (PTFS). PTF and PTFS provide users access to remote
permanent files. A local user activates PTF with the MFLINK
command (refer to the NOS Version 2 Reference Set, Volume 3). When
a remote user enters the MFLINK command, RHF activates a PTFS
application on the local host to service the remote request.
MHF Maintenance Host Facility (MHF). MHF automatically loads
controlware of local NADs during RHF initiation and performs
maintenance logging. If a local NAD fails while RHF is active, MHF
automatically dumps the NAD's memory to a permanent file and
reloads the controlware, for a description of LNAD statement
parameters that control automatic NAD dumping and loading (refer to
section 10, LID/RHF Configuration Files).
MHF also periodically checks all local NADs and any remote NADs
enabled for logging (refer to the network path table display described
later in this section) and copies new NAD error log entries to the
binary maintenance log (BML).
MHF starts automatically when RHF is initiated and remains active
until RHF terminates.
QTF, QTFS Queue File Transfer Facility (QTF) and Queue File Transfer Facility
Servicer (QTFS). QTF and QTFS allow you to transfer input and
output files to a remote system. When RHF is initiated, the system
automatically activates QTF. When a remote host QTF application has
a file to transfer, RHF initiates QTFS on the local host to service the
remote request.
The following subsections describe the initiation, operation, control, and termination of
the RHF.

Revision M

K-Display Utilities 8-75

RHF Initiation

RHF Initiation
Before network operation can begin, you must initiate RHF using the DSD RHFffff
command (refer to section 5, DSD Commands).
When RHF is initiated, it starts all enabled applications defined by the network
configuration as autostart applications (refer to RHF Configuration Files in
section 10). These applications are typically MHF and QTF.
Application MHF loads controlware into all local NADs that are defined in RHF's
configuration with AUTOLOAD=YES and have an EST status of ON.

Operator Interface
The operator interface for RHF consists of using the following displays:
Display

Description

Application

table

Lists

all

active

applications.

Network path table Shows how the remote hosts are connected to the local host.
An example of each display is shown later in this section. To understand how to use
the information provided in the displays it is helpful to understand the sample LCN
network shown in figure 8-24.

8-76

NOS

Version

Analysis

Handbook

Revision

'*s^\

Operator Interface

MFA

NOS

EST 31

EST 32

EST 33

EST 34

NAD

TCU
1 I 2

TCU
0 I 1 I 2 | 3

TCU
0|1 I 2 I 3

TCU
0 | 1 | 2 | 3

t - *

Oil I 2 I 3
TCU
NAD
ND-3F

■©•

MFB
LIDs: BBB. XYZ
NOS

0 I 1 | 2 | 3
TCU
NAD
ND-4A

0 | 1 | 2 | 3
TCU
NAD
ND-G2

MFC
LID: CCC
NOS

0 I 1 | 2 I 3
TCU
NAD
ND-F1

MFD
LIDs: EEE, BBB. DDD
NOS

Figure 8-24. Sample LCN
MFA is the local NOS host and MFB, MFC, and MFD are the remote NOS hosts. MFA
has four EST ordinals set up during installation (EST 31, 32, 33, and 34) to be used
with the three remote hosts. Each NAD can connect to a maximum of four channels
that can be used to communicate with NADs. These trunk control units (TCUs) are
represented by the numbers 0, 1, 2, and 3 in the diagram (refer to A in figure 8-24).
The horizontal lines between the NADs of the local mainframe (MFA) and the NADs
of the remote mainframes (MFB, MFC, and MFD) depict the connections between the
NADs. For example, the top horizontal line shows the connections between the
channels starting at TCU 0 of the local host and TCU 3 of the remote host (refer to
B in figure 8-24).
Also during the installation process, each remote NAD is given a remote NAD
address to uniquely identify that particular NAD. For example, the remote host MFB
has two NADs associated with it. Their remote NAD addresses are 3F and 4A (refer
to C in figure 8-24).

Revision M

K-Display Utilities 8-77

RHF Commands Under K display

RHF Commands Under K display
Use the RHF K display to communicate with RHF. Bring up this display with this
DSD command:
K.RHF.

Two K displays are available under RHF, the application table display (see figure 8-25)
and the network path table display (see figure 8-26). When you first enter K,RHF, the
application table display appears. The next time and subsequent times you enter
K,RHF, the display that appears will be either the application table or the network
path table, whichever was displayed last.
The following commands are available under the RHF K display:
Command

Function

APPL

Displays the application table (see figure 8-25).

IDLE

Begins the idle-down process of RHF and all its associated
applications.

PATH

Displays the network path table (see figure 8-26).

ord,ND=rna,AC = mac,
DD=dd,RT=rteb,
LT=lteb,LOG=status

Modifies entries associated with the network path table
display ordinal ord.

Pages the current display forward.
Pages the current display backward.

.jj££f?$£iV

8-78 NOS Version 2 Analysis Handbook

Revision M

Application Table Display

Application Table Display
The application table display (see figure 8-25) lists all active applications. In this
figure, USRAP represents an application written by the site.
MAX
ORD
1
2
3
4
5
6

APPL

ENABLED

QTF
QTFS

PTF
PTFS
USRAP

MHF

COPIES

MAX

ACTIVE
COPIES

CONNECTS

YES
YES
YES
YES
YES
YES

ACTIVE APPLICATIONS (NETON PERFORMED)

JOB

NAME

JOBORD

ABCA
AAQT
ACXQ

26
31
24

CONNECTS

NAME
AARM
ACAL
ACXY

JOBORD CONNECTS

22
33
27

Figure 8-25. Application Table Display

/^^V

Revision M

K-Display Utilities 8-79

Application Table Display

Each entry in the display appears in the following format:
ord appl enabled maxcoples actlvecopies maxconnects

jobname jobord connects
Header Description
ord Application table display ordinal.
appl Name of the application.
enabled Specifies whether the application communicates with RHF.
maxcopies Maximum number of copies of the application that can
simultaneously communicate with RHF.
activecopies Number of copies of the application that are currently
communicating with RHF.
maxconnects Maximum number of network connections allowed by each copy of
the application.
jobname Job sequence name of the application.
jobord Executing job table ordinal of the application.
connects Number of network connections currently used by this copy of the
application.

8-80 NOS Version 2 Analysis Handbook

Revision M

Network Path Table Display

Network Path Table Display
The network path table display, illustrated in figure 8-26, shows how the remote hosts
are connected to the local host. In this figure, A 1 means that a TCU is enabled. A 0
means that a TCU is not enabled. The leftmost digit of these entries corresponds with
TCU 0, the next with TCU 1, and so forth. For example, if a NAD has TCUs 1 and 2
enabled, the corresponding entry should be 0110. Refer to figure 8-24.
LOCAL
TRUNK
ORD PID EST CH ENABLED ENABLES

REMOTE
TRUNK
ENABLES

ADDR

1 M F B 031

2
3
4

032
033
034

033

DEST

ACCESS CON
CODE
COUNT

LOG
ERRS

0110
0001
0001
0100

0110
1000
0100
1000

3F
4A
3F
4A

F0F0
F0F0
F0F0
F0F0

NO
NO
NO
NO

10
11

NO
NO
YES
YES

0110
0001
0101
1000

0110
1000
1010
0001

62
62
62
62

F0F0
F0F0
F0F0
F0F0

NO
NO
NO
NO

YES
YES

0010
0001

0010
0010

F1
F1

F0F0
F0F0

NO
NO

9 M F D 031

NAD

YES
YES
NO
YES

032
033 10
033 10

5 M F C 031

6
7
8

REMOTE

Figure 8-26. Network Path Table Display

Revision M

K-Display Utilities 8-81

Network Path Table Display

Each entry in the display appears in the following format:
ord pid

est

enabled local remote remote
trunk trunk nad
enables enables addr

dest

access con log
code count errs

Header

Description

ord

Network path table display ordinal.

pid

Physical identifier of the remote mainframe for which the path is
defined.

est

EST ordinal of the NAD that defines the local end of the path.

Channel number of the NAD that defines the local end of the path.

enabled

Specifies whether RHF uses the path for starting new connections. For
example, if a customer engineer wants to run diagnostics on a trunk
connecting two NADs (local and remote), you would disable the
appropriate path. When the connection count on that path falls to zero,
the customer engineer can run concurrent diagnostics on that trunk
without disturbing the operation of RHF.

local trunk
enables

Bit pattern specifying which TCUs to use on the local NAD for
communications with the remote NAD.

remote
trunk
enables

Bit pattern specifying which TCUs the remote NAD uses in returning
communications to the local NAD.

remote nad
addr

Hardware address (hexadecimal) of the remote NAD.

dest

Destination device address (hexadecimal).

access code

Access code of the remote NAD; the software access code is the two
leftmost characters and the hardware access code is the two rightmost
characters.

con count

Number of connections currently using this path.

log errs

Specifies whether the MHF application logs trunk errors (detected by
the remote NAD) into the binary maintenance log (BML).

8-82 NOS Version 2 Analysis Handbook

Revision M

Network Path Table Display

When the network path table is displayed, you can enter the following command to
make changes.
ord,ND=rna,AC=rnac,DD=dd.RT=rteb,LT=lteb,LOG=status.
Parameter Description
ord Network path table display ordinal.
rna New remote NAD address in hexadecimal.
rnac New remote NAD access code in hexadecimal.
dd New remote NAD destination device address in hexadecimal.
rteb New remote trunk enable bit pattern (nonzero 4-bit binary number
with the leftmost bit representing TCU 0).
lteb New local trunk enable bit pattern (nonzero 4-bit binary number with
the leftmost bit representing TCU 0). The same number of bits must
be set for both RT and LT or the command will be rejected.
status Status of error logging for the specified remote NAD. Enter YES to
have MHF periodically copy the trunk errors occurring on the specified
remote NAD to the binary maintenance log (BML). MHF does not copy
trunk errors when you enter NO.
ord is the only required parameter and it must come first. All other parameters are
optional and can appear in any order, but at least one, besides ord, must be present.
NOTE
Any change to rna, dd, or status for a given path results in an equivalent change for
all paths using that remote NAD. This is because rna, dd, and status are associated
with the remote NAD rather than the path to the remote NAD.
When RHF finds a faulty local NAD, it turns off the NAD's EST entry, activates the
MHF application, and issues the following job dayfile message:
RHF, NAD ON EST est HAS BEEN TURNED OFF

MHF dumps the NAD's memory, reloads the NAD's controlware, and turns on the
NAD's EST entry.
When RHF finds a path configured to use a faulty or nonexistent local NAD trunk
control unit (TCU), it disables the path and notifies you with the following message
on the B,0 display:
RHF,BAD TCU ON PATH XXX, PATH TURNED OFF.

Use the GO,RHF command to acknowledge the message.

Revision

K-Display

Utilities

8-83

RHF Commands Available Under Application or Network Path Display

RHF Commands Available Under Application or Network Path Display
When the application table or network path table is displayed, you can enter the
following commands to enable or disable the application or network path.
ENABLE,ord.
or
DISABLE,ord.

Parameter Description
ord Ordinal of the application or network path on the current display.
For example, if the application table display is up, EN ABLE,ord enables the application
specified by the display ordinal ord.
If an application is being enabled (whether currently enabled or disabled) and that
application is defined as an autostart application, RHF initiates a copy of that .^^s
application. This feature may be used, for example, if the MHF application is
normally disabled and you want to start logging NAD errors. It may also be used if
the copy of the QTF application has been dropped accidentally and a new copy of the
QTF application must be started.

RHF Termination
You can terminate an RHF operation using the IDLE command.
The command format is:
IDLE.

When you enter the IDLE command the system waits for applications to stop and the
message IDLE-DOWN IN PROGRESS appears on the system status display. When
activity stops, the system drops RHF and the message RHF ENDED appears. The
IDLE command allows a gradual shutdown of RHF activities. No new connections are
allowed.

8-84

NOS

Version

Analysis

Handbook

Revision

SCOPE 2 Station Facility (SSF) K Displays

SCOPE 2 Station Facility (SSF) K Displays
The following commands control operation of the SSF Subsystem. Initiate the SSF
Subsystem before issuing any commands. SSF can be initiated automatically when the
system is brought up, either manually by entering an SSFffff command, or by entering
the ENABLE,SSF command.

Operator Interface
The SSF uses the K display for operator communications; therefore, the K display must
be assigned to SSF before any other SSF Subsystem commands can be entered. Use the
following command to assign the K display to SSF.
K.SSF.

Station Login
After SSF is assigned to a control point, SSF searches the equipment status table
(EST) for a SCOPE 2 communication coupler. If SSF finds an available coupler, it asks
the SCOPE 2 mainframe to establish communications. If no coupler is found, a message
appears at the console indicating that SSF is ready to log in to a SCOPE 2 mainframe.
To log in, first enter an ON command (refer to section 5, DSD Commands, for a
description of the ON command), then enter the following command:
K.LOGIN.

Enabling and Disabling File Transfers
File transfers between NOS and SCOPE 2 must be enabled before actual file transfers
can begin; however, this occurs automatically when the SSF Subsystem is logged in.
You can disable file transfers by entering the following command:
K.OFFSTAT.X.

Parameter Description
x S p e c i fi e s t h e S C O P E 2 m a i n f r a m e P I D .
When you enter a K.OFFSTAT command, file transfers in progress are completed, but
no new file transfers are initiated. This command does not affect command, display, or
message processing.
File transfers can be reenabled using the following command:
K.ONSTAT.x.

Parameter Description
x S p e c i fi e s t h e S C O P E 2 m a i n f r a m e P I D .

5. Refer to appendix C for more information on the SSF Subsystem.

Revision

K-Display

Utilities

8-85

Station Recovery

Station Recovery
If NOS fails, follow the SSF initiation procedure as described in section 5, DSD
Commands, to recover the station. SSF does not require reinitiation if SCOPE 2 fails
or if there is an FLPP failure that results in a reload of the FLPP.

Station Disconnection and Logout
Station disconnection refers to the termination of communications between SSF and
SCOPE 2 as a result of a hardware or software error or as a result of an operator
command. When the disconnection occurs, all pending requests to the SCOPE 2
mainframe (such as screen refreshes, messages, and acknowledgments) are dropped.
Before entering an operator command to disconnect SCOPE 2, you should perform the
following steps:
1. Idle down the file transfers by entering the K.OFFSTAT command. The station is
idle when all staging SPOT jobs are finished and the spooling SPOT job has been
swapped out.
2. If the system is in restricted or privileged mode, enter the CLROP command to
relinquish operator control of SCOPE 2. Refer to the SCOPE 2.1 Operator's Guide
for a description of the CLROP command.
To disconnect the SCOPE 2 mainframe, you can either drop the station control point by
issuing a STOP or IDLE Subsystem command as described in section 5, DSD
Commands, or you can log out of a specific SCOPE 2 mainframe by using the following
command:
K.LOGOUT.
or
K.LOGOUT,p1d.

Parameter Description
pid PID of the mainframe you want to disconnect (required only in a
multimainframe environment).

8-86

NOS

Version

Analysis

Handbook

Revision

File Transfer Limit Commands

File Transfer Limit Commands
The following commands allow you to set limits on the number of file transfers that
can be in progress concurrently for various types of file operations. The system default
value for each of the following commands is 2; however, the default values can be
changed, as an installation option, when SSF is installed. Refer to the NOS Version 2
Installation Handbook for more information on the default values for file transfer limit
commands.

Staged File Transfer Commands
The following commands control the number of concurrent SPOT jobs performing staged
file operations:
Command

Description

K.PURGE,pid,n.

Specifies the maximum number of concurrent SPOT jobs allowed
to purge files from a NOS permanent file device, pid is the PID of
the SCOPE 2 mainframe, n is the maximum number of purge
operations (0 ^ n^ 7).

K.READTP,pid,n.

Specifies the maximum number of concurrent SPOT jobs allowed
to read tape files from NOS to SCOPE 2. pid is the PID of the
SCOPE 2 mainframe, n is the maximum number of read
operations (0 ^ n ^ 7).

K.WRITETP,pid,n.

Specifies the maximum number of concurrent SPOT jobs allowed
to write tape files from SCOPE 2 to NOS. pid is the PID of the
SCOPE 2 mainframe, n is the maximum number of write
operations (0 ^ n ^ 7).

K.GETPF,pid,n.

Specifies the maximum number of concurrent SPOT jobs allowed
to read permanent files from NOS to SCOPE 2. pid is the PID of
the SCOPE 2 mainframe, n is the maximum number of permanent
file read operations (0 ^ n ^ 7).

K.SAVEPF,pid,n.

Specifies the maximum number of concurrent SPOT jobs allowed
to write files from SCOPE 2 to a NOS permanent file device, pid
is the PID of the SCOPE 2 mainframe, n is the maximum number
of permanent file write operations (0 ^ n ^ 7).

V^Sfflfv

Revision M

K-Display Utilities 8-87

Spooled File Transfer Commands

Spooled File Transfer Commands
The following commands control the number of I/O files that the spooling SPOT job
xSTA can transfer concurrently. Separate limits can be defined for both input and
output files; however, the system limits the combined total of input and output files to
four concurrent transfers.
Command Description
K.INPUT,pid,n. Specifies the maximum number of concurrent input file transfers
from NOS terminals to SCOPE 2. pid is the PID of the SCOPE 2
mainframe, n is the maximum number of input files (0 ^ n ^ 4).
K.OUTPUT,pid,n. Specifies the maximum number of concurrent output file transfers
from SCOPE 2 to NOS terminals, pid is the PID of the SCOPE 2
mainframe, n is the maximum number of output files
(0 ^ n ^ 4).
■

8-88

NOS

Version

Analysis

Handbook

Revision

Transaction Facility (TAF) K Displays

Transaction Facility (TAF) K Displays
The following commands control operation of the TAF Subsystem. Initiate the TAF
Subsystem by using the TAFffff command before issuing these commands.

TAF Initialization K Display
When the transaction executive is brought to a control point, the message
REQUEST *K* DISPLAY appears at the control point if a DISPLAY,ON command is
specified in the TAF configuration file. Respond with the entry:
K . TA F.

The TAF initialization K display appears on the system console as shown in
figure 8-27.
TAF
hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
TAF INITIALIZATION OPTIONS
OPTION

DESCRIPTION

SCP = 31 SUB CONTROL POINTS (2 - 31).
CMB = 40 COMMUNICATION BLOCKS (19 - 40).
REC = NO RECOVERY MODE (YES OR NO).
MFL = 376500B MAXIMUM FIELD LENGTH (40000B - 376500B).
ECS = OK EXTENDED MEMORY FIELD LENGTH (OK - 400K).
TLF = TASKLIB TASK LIBRARY FILE (1-7 CHARACTERS).
INITIALIZE CRF RECOVERY FILES (NONE,ALL OR
1-7 DIGITS).
INT = CRM,NONE INITIALIZE CRM RECOVERY FILES (NONE OR ALL)
ERO = CRF,NO ERROR OVERRIDE (YES OR NO).
INT = CRF,NONE

BFL = 70000B CMM BASE FL (20000B - 200000B).
EFL = OB CMM EXPANDABLE FL (0 - 100000B).
TFL = 30000B CMM TARGET FL (10000B - 100000B).

Figure 8-27. TAF Initialization K Display (Left Screen)

r
Revision M

K-Display Utilities 8-89

TAF Initialization K Display

Any of the following initialization commands can then be entered. If no values are to
be changed, enter the command:
K.END

Values are decimal unless otherwise indicated.
Command Description
K.BFL=n Changes the starting and minimum field length allocated by TAF to
CRM (200008 ^ n ^ 200000s). Default is 70000s.
K.CMB=n Changes the maximum number of communication blocks allowed to
the TAF Subsystem (19 ^ n ^ 40). Default is 40.
K.ECS=n Sets the extended memory field length to be used by the
transaction executive; n is octal thousands of words. Default is 0.
K.EFL=n Changes the maximum additional central memory field length made
available to CRM for buffers and capsules (0 ^ n ^ 100000s).
Default is 0.
K.END Ends input of the transaction executive initialization parameters.
Initialization is completed when the TAF status K display appears
(figure 8-28).
K.ERO=CRF,op Specifies whether to override certain I/O and logic errors when
processing the communication recovery files (CRF).
op

Description

NO Aborts if I/O or logic errors are encountered while
processing the communication recovery files. This is the
default setting.
YES I/O or logic errors encountered on a run unit header
record result in the loss of that run unit with no
indication to the terminal user. The loss is noted on the
recovery report.
A ^ S

I/O or logic errors encountered on a message record
within a run unit result in a loss of that run unit. A
status field is set in the run unit header, allowing TAF to
inform the terminal user of the run unit loss.
I/O or logic errors encountered on the CRF header record
result in an unconditional abort of the TAF Subsystem.

8-90

NOS

Version

Analysis

Handbook

Revision

TAF Initialization K Display

Command

Description

K.GO

Ends input of the transaction executive initialization parameters.
Initialization is complete when the TAF status K display appears
(figure 8-28).

K.INT=typ,fileid

Specifies which communication recovery files (CRF) are to be
initialized. This is the only way to initialize a CRF. Files specified
on a RECOVER command in the TAF configuration file and
specified in this command are initialized. Files specified on a
RECOVER command but not specified in this command are used for
recovery.
This command also specifies whether CYBER record manager
(CRM) data base recovery files are initialized or recovered. For
CRM recovery files, this command is valid regardless of TAF
assembly parameters.
typ

Description

CRF

Communication recovery files. This parameter is valid
only if the installation parameter IPTAR equals 1.

CRM

CYBER Record Manager after-image and before-image
recovery files.

fileid

Description

n A digit from 1 to 7 that defines a CRF to be initialized.
The digit corresponds to the ID parameter on the
RECOVER command in the TAF configuration file. This
parameter is not valid for CRM recovery files.
ALL If typ is CRF, all communication recovery files defined by
RECOVER commands in the TAF configuration file are
initialized. If typ is CRM, all CRM recovery files are
initialized.
This parameter must be used with caution when typ is
CRM since the CRM update history currently on the
after-image recovery files is lost.
NONE If typ is CRF, communication recovery files are
initialized; all communication recovery files specified in
RECOVER commands in the TAF configuration file are
recovered. If typ is CRM, all CRM data bases are
recovered based on information in the existing recovery
files. No CRM recovery files are initialized. This fileid is
the default for both typ=CRF and typ=CRM.

Revision M

K-Display Utilities 8-91

TAF Initialization K Display

Command

Description

K.MFL=n

Sets the maximum field length to be used by the transaction
executive (400008 ^ n ^ 376500s). Default is 376500s.

K.REC=a

Specifies whether to set the recovery bit in the user area of each
terminal status table entry (YES or NO). If YES, the user recovery
bit is set. If NO, the value of the user recovery bit is not changed
from what it was before the command was issued. Default is NO.

K.SCP=n

Changes the number of subcontrol points (2 ^ n < 31). Default
is 31.

K.STOP

Aborts the TAF Subsystem initialization unconditionally.

K.TFL=n

Changes the value used as the upper bound for TARGET. This is
the amount of memory CRM uses for data and index blocks
(100008 ^ n ^ 1000008). Default is 300008. For more information,
refer to the CYBER Record Manager Advanced Access Methods
Version 2 Reference Manual.

K.TLF=filename

Changes the name of the system task library file (any valid file
name). Default is TASKLIB.

8-92 NOS Version 2 Analysis Handbook

Revision M

Restarting TAF K Display

Restarting TAF K Display
On a level 3 recovery deadstart, or if the TAF Subsystem aborts, the TAF procedure
file will automatically restart TAF by transferring control to the TAF automatic
recovery program, if sense switch 4 is set. The TAF automatic recovery program
recovers the central memory pointers and variables defined during TAF initialization.
If a DISPLAY,ON command is in the TAF configuration file, the automatic recovery
program brings up the K display on the left console screen. This display is identical
to the TAF initialization K display, except that values specified by the TAF
initialization commands replace any default values that were in the TAF initialization
K display.

TAF Status K Display
When the TAF Subsystem is executing, the TAF status K display (figure 8-28)
indicates the:
• Latest transaction sequence number.
• Number of words of unused memory.
• Maximum field length.
• Global task dump limit.
• Subsystem default values for memory dump parameters.
The subsystem default values are used to control memory dumps when parameters are
not included in the CMDUMP or DSDUMP command. Any of these default values can
be changed by specifying the corresponding parameter in the K.DSDUMP command.

0ms

Revision

K-Display

Utilities

8-93

TAF Status K Display

TAF
hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
TAF STATUS
TRANSACTION SEQUENCE NUMBER 5
UNUSED FIELD LENGTH 7700
MAXIMUM FIELD LENGTH 376000
G L O B A L TA S K D U M P L I M I T 0
CMDUMP/DSDUMP DEFAULT VALUES
OPTION

DESCRIPTION

FW = 0 FWA OF TASK MEMORY TO BE DUMPED.
LW = 100000 LWA OF TASK MEMORY TO BE DUMPED.
EP = 1 IF EP=1, DUMP EXCHANGE PACKAGE.
IF EP»0, DO NOT DUMP EXCHANGE PACKAGE
OQ = BC OUTPUT QUEUE.
QD « 0 QUEUE DESTINATION.

Figure 8-28. TAF Status K Display (Left Screen)
/■SS8|v

>*ffi%v

8-94 NOS Version 2 Analysis Handbook

Revision M

TAF Status K Display

The default parameter values for the CMDUMP and DSDUMP commands are given on
the TAF status K display shown in figure 8-28.
Parameter Description
EP Exchange package:
EP Description
0 Do not dump the exchange package.
1 Dump the exchange package.
FW First word address of the task memory to be dumped.
LW Last word address of the task memory to be dumped.
OQ6 Output queue:
OQ Description
BC Local batch.
RB Remote batch.
P F P e r m a n e n t fi l e .
QD6 Queue destination:
Printer identifier (if OQ=BC).
User name (if OQ=RB).
Permanent file name (if OQ=PF).

6. The functioning of this parameter is described in the TAF Version 1 Reference Manual.

Revision

K-Display

Utilities

8-95

TAF K-Display Commands

TAF K-Display Commands
When the transaction executive is at its control point, the following commands can be
entered from the system console or submitted from tasks using the KPOINT request.
Any task can issue the K.DUMP command. Only tasks that reside on the system task
library can issue the other K-display commands. (Refer to the TAF Version 1 Reference
Manual for additional information on the KPOINT request and the system task
library.)
Command

Description

K.ASSIGN.est
or
K.ASSIGN,est,db,n

Assigns a magnetic tape unit to be used for a journal file,
est is the EST ordinal of the tape unit. The first form of the
command makes unit est available for the transaction
executive to assign to the next tape journal file that
encounters end of reel. Two tape units may be preassigned.
If a tape has not been preassigned in this manner, an
end-of-reel on a journal file causes subsequent entries for
that file to be placed on disk.
The second form of the command forces journal file n (n = l,
2, or 3) for data base db, defined as a tape file, from disk to
tape. The transaction executive copies the data from the
disk journal file to tape est and places all subsequent
entries for that file on the tape. This command is necessary
after the transaction executive initialization to assign tape
units to the tape journal files or after an end-of-reel on a
tape journal file when no tape had been preassigned to the
transaction executive. All data residing on the disk for the
tape journal file must fit on the tape assigned by this
command or the transaction executive will unload the tape
and issue the message *UNABLE TO USE TAPE*.

K.DEBUG

Turns on the application interface program (AIP) debug
option, which logs all messages on trace file ZZZZZDN. Use
this command only when TAF is installed with the DEBUG
option.

K.DROP,n

Drops an executing task at subcontrol point n.

K.DSDUMP,FW=addr,
LW=addr,EP=pkg,
OQ=outq,QD = qdest,
DB=db

Allows you to modify the standard system default
parameters controlling memory dumps. The command does
not directly cause a dump. Rather, it sets default values to
be used when a subsequent CMDUMP request is received or
when abort conditions occur. Refer to TAF Status K Display,
earlier in this section, for explanations of the parameters.

8-96 NOS Version 2 Analysis Handbook

z<^\

Revision M

TAF K-Display Commands

Command

Description

K.DUMP,fwa,lwa

Dumps all or part of the field length of the Transaction
Facility from the first word address (fwa) to the last word
address (lwa) of the area to be dumped. The default value
for fwa is 0 and for lwa is 377777s. The default base is
octal. If no parameters are specified, the entire field length
is dumped. The output is routed to a printer that has an ID
of 0.
Unlike other K-display commands, the K.DUMP command
can be issued from any task. Other K-display commands can
be issued by tasks only if they are on the system task
library (refer to the TAF Version 1 Reference Manual).
Since secure information may be contained in a dump of the
Transaction Facility, the following safeguards have been set
up to protect dumped information; however, the installation
must take the ultimate responsibility for the protection of
dumped information.
• The global task dump limit (GTDL) can be set by the
K.DUMPLIM command to limit the number of times the
K.DUMP command can be issued from tasks. The initial
value of the GTDL is 0 (zero), so the K.DUMP command
is disabled from use by a task by default.
• For all dumps of the Transaction Facility, whether you
initiated it or a task did, a one-page header precedes the
dump. This header page indicates the output is secure
and should be given only to the TAF central site systems
analyst.

J$3zm^\

• When the Transaction Facility is dumped, the message
TAF FIELD LENGTH DUMP RELEASED is issued to
the system dayfile, the Transaction Facility dayfile, and
line one of the control point.
0nms

Revision M

K-Display Utilities 8-97

TAF K-Display Commands

Command

Description

K.DUMPLIM,n

Sets GTDL to value n (0 ^ n ^ 9999999). If n is not
specified, the GTDL is set to 0.

^®^Si

The GTDL is the number of times the K.DUMP command
can be issued from tasks. This value is displayed on the
TAF status K display shown in figure 8-28. The initial value
of the GTDL is 0. When the GTDL is 0, no dumps of the
Transaction Facility can occur from tasks. Thus, the
K.DUMP command is disabled from tasks by default.
To enable the K.DUMP command for tasks, issue the
K.DUMPLIM command to set the GTDL to a value greater
than zero. Each time a task issues a K.DUMP command,
the GTDL is decreased by one until it equals zero. When
the first K.DUMP command is issued from a task with the
GTDL equal to zero, the message
GLOBAL TASK DUMP LIMIT EXHAUSTED

is issued to the Transaction Facility dayfile, the system
dayfile, and line one of the control point. Also, the message
DUMPS.LOST

is displayed on the K display in place of the value of the
GTDL. This message remains until the value of GTDL is set
to a value greater than or equal to zero. The K.DUMPLIM
command should be used with care in system tasks, since
this might allow unauthorized users to alter the GTDL.
K.IDLE

Idles down the transaction control point. Once idle down has
been initiated, no new transactions will be permitted but
currently executing transactions will be allowed to finish.

K.JEND,db,n

Forces end-of-reel processing (writes an EOI and rewinds the
file) on tape journal file n of data base db. If n is not a
tape journal file, the command is ignored.

K.MAXFL,n

Alters the transaction executive maximum field length. The
transaction executive does not attempt to obtain more than
n words of storage. This command is rejected if the value
for n is more than 376500s or less than the field length
currently required for TAF.

K.MESSAGE,TN=b.
message

Directs the transaction executive to send message to a
terminal specified by terminal name b.

>^^^V

8-98 NOS Version 2 Analysis Handbook

Revision M

TAF K-Display Commands

Command

Description

K.NODEBUG

Turns off the application interface program (AIP) debug
option, which logs all messages on trace file ZZZZZDN. Use
this command only when TAF is installed with the DEBUG
option.

K.OFFTASK,a,db

Disables the use of task a, where a is the task name in the
data base db task library directory (dbTASKL). The data
base name db is not specified for tasks in the system task
library.

K.ONTASK.a.db

Reverses the effect of a previous OFFTASK command for the
specified task a in the data base db task library directory
(dbTASKL). The data base name db is not specified for tasks
in the system task library (TASKLIB).

K.ROLLTIM,nnnnnn

Changes the amount of time that TAF will retain its field
length between communication input messages; nnnnnn is
specified in units of milliseconds. Refer to the installation
parameter ITRTL in the NOS Version 2 Installation
Handbook.

K.SWITCH

Causes the console K display to change to a display listing
all allowable TAF K display commands. When K.SWITCH is
entered a second time, the previous K display returns. This
command activates task KDIS and forces TAF to remain
rolled in.

K.TBCON,nn

Changes the number of TAF/CRM batch concurrency users;
nn is less than or equal to the value specified on the
TBCON command in TAF's configuration file (TCF).

K.TST,TN = a,DB=db,
UU = nnnn,UL=mmmm,
NN = b

Changes entries in the terminal status table for terminal a.
The following entries can be changed: data base name db,
user area upper 12 bits (nnnn), user area lower 12 bits
(mmmm), and new terminal name b. The changes do not
affect the network and simulation files. Do not use this
command if the terminal is logged in.

Revision M

K-Display Utilities 8-99

TAF/CRM Status K Displays and Commands

TAF/CRM Status K Displays and Commands
You can use the K display to monitor the status of CRM, CRM data bases, or CRM
data base permanent files while TAF/CRM is running if CRMTASK is present on the
system task library. To get the CRMTASK K display enter:
K.DIS,CRMTASK.

After the K display is assigned to the task, the display in figure 8-29 is brought to the
left screen.
TAF
hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
CRMTASK COMMANDS
CRMSTAT SEE ALL CRM DATA BASES.
CRMSTAT.DB SEE CRM DATA BASE DB.
CRMSTAT,DBPFN SEE CRM DATA BASE FILE DBPFN.
DBDOWN,DB DOWN DATA BASE DB.
DBDOWN,DBPFN DOWN DATA BASE FILE DBPFN.
DBUP.DB UP DATA BASE DB.
DBUP,DBPFN UP DATA BASE FILE DBPFN.
E N D E N D C R M TA S K P R O C E S S I N G .
M E N U S E E T H I S D I S P L A Y.
+ PA G E L E F T S C R E E N F O R W A R D .
PAGE LEFT SCREEN BACKWARD.

Figure 8-29. CRMTASK Commands K Display (Left Screen)
■^Sfev

8-100 NOS Version 2 Analysis Handbook

Revision M

TAF/CRM Status K Displays and Commands

0m^-..
The following commands are available under CRMTASK.
Command

Description

K.CRMSTAT

Selects the CRM status K display (figure 8-30). This display
shows the status of all CRM data bases.

K.CRMSTAT,db

Selects the CRM data base status K display (figure 8-31). This
display shows the status of the specific CRM data base with
identifier db. It also shows the file name and status of the
before-image files.

K.CRMSTAT,dbfile

Selects the CRM file status K display (figure 8-32). This display
shows the status of the specific permanent file in a CRM data
base with file name dbfile.

K.DBDOWN,db

Makes a specific CRM data base with identifier db unavailable
for processing. When this command executes, the CRMTASK
command directory appears on the K display.

K.DBDOWN,dbfile

Makes a specific permanent file in a CRM data base with file
name dbfile unavailable for processing. When this command
executes, the CRMTASK command directory appears on the K
display.

K.DBUP,db

Makes a specific CRM data base with identifier db available for
processing. When this command executes, the CRMTASK
command directory appears on the K display.

K.DBUP,dbfile

Makes a specific permanent file in a CRM data base with file
name dbfile available for processing. When this command
executes, the CRMTASK command directory appears on the K
display.

K.END

Ends CRMTASK K-display processing.

K.MENU

Returns to the CRMTASK commands K display (figure 8-29).

K.+

Pages the left screen forward to the next screen.

K -

Pages the left screen backward to the first screen.

Revision M

K-Display Utilities 8-101

TAF/CRM Status K Displays and Commands

TAF

./, DT AND TD ARE USED ONLY FOR INTERACTIVE JOBS.

Figure 9-14. SDSPLAY-CLASS Display (Page 3 of 3)

Revision M

L-Display Utilities 9-15

SDSPLAY Commands

SDSPLAY Commands
You can enter the following SDSPLAY commands from either the HELP or CLASS
displays and from any screen.
Command Description
L.CLASS=xx

Selects the CLASS display and displays the system attributes for the
service class specified by xx, where xx is any service class defined on
the HELP display.

L.END

Terminates the SDSPLAY utility. If you made changes to system
attributes, the changes will not be saved unless you issue a L.GO
command before issuing the L.END command.

L.HELP *

Selects the HELP display and displays the first screen.

L.GO

Saves any changes you made to system attributes using the
L.keyword=value commands by entering the new values into the
system tables. The current display remains on the screen.

L.RESET

Clears any changes you made to system attributes using the
L.keyword=value commands since you issued the last L.GO command.
The current display remains on the screen. Following a L.RESET
command, the CLASS displays will display values from the system
tables.

L.+

Pages the HELP or CLASS display forward to the next screen. When
the last screen is being displayed, the next L.+ command advances the
display to the first screen. You cannot page from one display (CLASS
or HELP) to the other display; nor can you page from one service class
to another service class within the CLASS displays.

L.-

Pages the HELP or CLASS display backward to the previous screen.
When the first screen is being displayed, this command has no effect on
the display.

9-16 NOS Version 2 Analysis Handbook

Revision M

" " >

Changing System Attributes

Changing System Attributes
To alter system attributes using the SDSPLAY utility, you select the CLASS display
and specify the service class using the L.CLASS command. Next, you make changes
using L.keyword = value commands. The values you enter apply only to the service
class being displayed. You can enter multiple keyword=value pairs separated by
commas in one command line. The only limit is the L display input line length
restriction.
When you change system values, the updated values are displayed immediately if the
corresponding screen is being displayed. If your changes affect a different screen, the
updated values will be displayed when you page to that screen. Your changes will not
be entered into the system tables until you enter a L.GO command. You can cancel
your changes and reset the system values by entering a L.RESET command, but it
must be entered before you enter the L.GO command.

y#flfl$£Vv

You can change system values for a different service class by entering another
L.CLASS command followed by more L.keyword=value commands.
Lukeyword = value Commands
You can enter the following L.keyword = value commands from a CLASS display.
Although you can enter numeric values in either octal or decimal, most of the values
are displayed in octal. Octal is the input default; you specify decimal values with a
radix of D following the number. Also, numbers containing an 8 or 9 are interpreted as
decimal.
The keywords are listed in the same order as they appear in the CLASS display.
Keyword Description
INLP Priority assigned to a file entering the input queue. The value of INLP
can range from 0 to 7777s, but must be less than the value of INUP.
INUP Highest priority a file can reach in the input queue; aging stops when
this priority is reached. The value of INUP can range from 0 to 7777s,
but must be greater than the value of INLP.
OTLP Priority assigned to a file entering the output queue. The value of OTLP
can range from 0 to 7777s, but must be less than the value of OTUP.
OTUP Highest priority a file can reach in the output queue; aging stops when
this priority is reached. The value of OTUP can range from 0 to 77778,
but must be greater than the value of OTLP.
EXLP Lowest priority for a job in the execution queue. The value of EXLP can
range from 0 to 7777s, but must be less than the value of EXUP.

Revision M

L-Display Utilities 9-17

L.keyword=value Commands

| Keyword Description
| EXUP

Priority assigned to a job when initially assigned to a control point.
However, online interactive jobs with terminal I/O available are scheduled
at EXTP priority. The value of EXUP can range from 0 to 7777s, but
must be greater than the value of EXLP.

J EXIL

Priority a job receives when it initially exhausts its CM or CPU time
slice. Thereafter, whenever the time slice is exhausted the job's priority
will be set to the value of EXLP. The value of EXIL can range from 0 to
77778, but must be in the range of values for EXLP and EXUP.

j EXIP

Initial scheduling priority for an executing job. The value of EXIP can
range from 0 to 7777s, but must be in the range of values for EXLP and
EXUP.

| EXTP

Terminal job priority assigned to a terminal job that has terminal input or
output available. The value of EXTP can range from 0 to 7777s, but must
be in the range of values for EXLP and EXUP.

| INWF

Weighting factor for input queue priority calculations. The value of INWF
must be a power of 2 in the range 1 to 4000s.

| EXWF

Weighting factor for execution queue priority calculations. The value of
EXWF must be a power of 2 in the range 1 to 4000s.

j OTWF

Weighting factor for output queue priority calculations. The value of
OTWF must be a power of 2 in the range 1 to 4000s.

| AM

Maximum field length divided by 100s for all jobs of the specified service
class. Refer to the SERVICE command in section 3.

I CB

Upper and lower bound CPU priorities. Refer to the SERVICE command
in section 3.

1 CM

Central memory time slice in seconds. Refer to the SERVICE command in
section 3.

I CP

Control point slice priority. Refer to the SERVICE command in section 3.

j CS

Cumulative size in PRUs allowed for all indirect access permanent files.
Refer to the SERVICE command in section 3.

I CT

Control point time slice (seconds). Refer to the SERVICE command in
section 3.

IDS

Size in PRUs allowed for individual direct access permanent files. Refer to
the SERVICE command in section 3.

I DT

Service class to which a detached job is assigned. Refer to the SERVICE
command in section 3.

1 EC

Maximum user-accessible extended 'memory field length in words divided
by UEBS for any job of the specified service class. Refer to the SERVICE
command in section 3.

I EM

Maximum extended memory length in words divided by UEBS for all jobs
of the specified service class. Refer to the SERVICE command in section 3.

9-18 NOS Version 2 Analysis Handbook

Revision M

/***%.

L.keyword=value Commands

Keyword Description
FC Number of permanent files allowed. Refer to the SERVICE command in
section 3.
FL Maximum field length divided by' 100s for any job of the specified service
class. Refer to the SERVICE command in section 3.
FS Size in PRUs allowed for individual indirect access permanent files. Refer
to the SERVICE command in section 3.
NJ Maximum number of jobs. Refer to the SERVICE command in section 3.
SD CPU job switch delay (milliseconds). Refer to the SERVICE command in
section 3.
TD Suspension timeout delay. Refer to the SERVICE command in section 3.

Revision

L-Display

Utilities

9-19

SUBSYST L Display

SUBSYST L Display
The SUBSYST L-display utility displays information about all the subsystems supported
by NOS. To begin the SUBSYST utility enter one of the following commands:
SUBSYST,L=out f11e,LO=opt1on.
or

SUBSYST,outfile,opt ion.

Parameter Description
outfile Output file name. This parameter is valid only if a list option is
specified. The default outfile is file OUTPUT.
option List option. Enter one of the following:
option Description
D Formats the data for the DSD L display. This is the
default list option if the parameters outfile and option
are not specified.
L F o r m a t s t h e d a t a f o r a l i n e p r i n t e r.
If you do not specify outfile and option, the data is written to the L display.
Refer to the NOS Version 2 Operations Handbook for further information regarding
the SUBSYST L display.

9-20 NOS Version 2 Analysis Handbook

Revision M

L I D / R H F C o n fi g u r a t i o n F i l e s 1 0
LID
C o n fi g u r a t i o n
File
10-1
Creating
the
LIDCMid
File
10-1
NPID
Statement
10-2
NLID
Statement
.
."
10-3
Equipment
C o n fi g u r a t i o n
Example
10-4
Specifying
the
Size
of
the
LID
Ta b l e
10-6
B u i l d i n g o r R e b u i l d i n g t h e L I D Ta b l e . . . . : 1 0 - 6
Listing
the
LID
Ta b l e
10-7
Changing LIDS Using the LIDOU Display 10-7
Specifying Requirements for Running NOS/VE in Dual-State Mode 10-8

RHF
C o n fi g u r a t i o n
Files
RCFGEN
Utility
RCFGEN
Input
Statement
Order
Network
C o n fi g u r a t i o n
Statements
LNDR
Statement
APPL
Statement
NPID
Statement
PAT H
Statement
,
LNAD
Statement
RNAD
Statement
DEBUG
Statement
CHARGE
Statement
,
LCN
Examples
...

10-9
10-9
1 0 - 11
10-12
10-13
10-13
10-13
10-15
10-15
10-16
10-18
10-18
10-19
10-20

QTF
C o n fi g u r a t i o n
Requirements
RHF
C o n fi g u r a t i o n
File
Directives
NAM
C o n fi g u r a t i o n
File
Directives
QTF
Procedure
File
...
v.
Procedure
File
Example

10-23
10-23
10-24
10-25
10-26

L I D / R H F C o n fi g u r a t i o n F i l e s 1 0
This section contains information about LID configuration files, RHF configuration files,
and QTF configuration requirements.

LID Configuration File
You create a LID configuration file to define the physical and logical machines
available for your system. After a level 0 deadstart, the system program CLDT
searches for the LID configuration file on user index 377777s. It will use the
information in this file to generate a logical identifier table (LDT) in central memory.
This section describes how to create and maintain the LID configuration file
(LIDCMid). Specifically, how to:
• Create the LIDCMid file using NPID and NLID configuration statements.
• Specify the size of the LID table using the CMRDECK LDT entry.
• Build or rebuild the LID table using the X.CLDT command.
• List the current LID table using the LISTLID command.
• Change LIDs and LID attributes using the LIDOU display.
• Specify the requirements for running NOS/VE in dual-state mode.
j r f f fi P & V

Creating the LIDCMid File
The first line of the LIDCMid file should be a 1- to 7-character name for the LID
configuration file. Use this format for naming the file:
LIDCMid

Va l u e

Description

i d 2 - c h a r a c t e r m a c h i n e i d e n t i fi e r f o r t h e m a i n f r a m e .
You can place comment lines in the file by putting an asterisk in column 1 or by
putting the word COMMENT beginning in column one.
Example:
LIDCM64
•LIDCMID FILE FOR MAINFRAME 64.

You should define each PID (physical identifier) and all the LIDs (logical identifiers)
associated with the PID by using NPID and NLID statements.

Revision

LID/RHF

C o n fi g u r a t i o n

Piles

10-1

NPID Statement

NPID Statement
Use one NPID statement to define each physical mainframe available to your system.
Use this format for the NPID statement:
NPID,PID=p1d,ENABLED=statUS,MFTYPE=type,AT=at,NETDIS=SUb.

Parameter

Description

PID=pid

Physical identifier; pid is the 3-character physical identifier for
the mainframe. For NOS, pid should be Mid, where id is the
2-character machine identifier defined by the MID=id
CMRDECK entry. Required.

ENABLED=status

Specifies whether the mainframe identified by PID is available.
You can enter YES or NO. Default is YES.

MFTYPE=type

Mainframe type; type is any 1- to 7-character string specifying
the mainframe type or mainframe identifier (for example,
NOSBE, NOS, CY200, NOSMF2, CLSH1). Required.

AT=at

Specifies the attribute associated with the mainframe identified
by PID. You can specify multiple attributes by using a slant
separator (AT=VALID/NLIST) or by repeating the parameter
(AT=VALID.AT=NLIST).
at

Description

VALID

Specifies that USER command prevalidation is
required. This parameter causes the local host to
verify that a user is authorized. This prevalidation
is performed in addition to the normal user
validation performed at the remote host.

NVALID

Specifies that USER command prevalidation is not
required.

NLIST

Specifies that this PID is not available to the end
user through the LISTLID command.

The default attributes are: USER command prevalidation is not
required and PID is listable using the LISTLID command.
NETDIS=sub

Specifies which network accesses to the mainframe identified by
PID are disabled. By default, all network accesses are enabled.
You should not specify NETDIS for the host PID. Any
combination of network accesses may be used (for example,
NETDIS=RHF/SSF).
sub

Description

NAM

Network Access Method.

RHF

Remote Host Facility.

SSF

SCOPE Station Facility.

10-2 NOS Version 2 Analysis Handbook

Revision M

y<^KT^k

NLID Statement

NLID Statement
j^pKsy

Use NLID statements after each NPID statement to define the relationship between
each PID and its associated LIDs and the attributes of the LIDs. Use this format for
the NLID statement:
NLID,LID=1i d,ENABLED=Stat US,AT=at

Parameter

Description

LID=lid

Logical identifier; lid is the 3-character logical identifier for the
mainframe identified by the last NPID statement. One lid entry
must be the same as the last pid. Required.

ENABLED=status

Specifies whether the mainframe identified by LID is available.
You can enter YES or NO. Default is YES.

AT=at

Specifies the attribute associated with the mainframe identified
by LID. You can specify multiple attributes by using a slant
separator (AT=STOREF/VALID) or by repeating the parameter
(AT=STOREF,AT=VALID).
at

Description

LOOPB

Loopback capability for RHF testing. This testing
can be performed on one mainframe with one
NAD. The attribute of LOOPB is valid only for
LIDs defined for the host (local) mainframe.

00$S

You should not specify the LOOPB attribute if the
STOREF attribute is specified.
STOREF

Store and forward capability indicating that the
specified mainframe will act as part of the
network in store and forward mode. Data will
pass through the machine and into the network.
You should not specify the STOREF attribute if
the LOOPB attribute is specified.

Revision M

VALID

Specifies that USER command prevalidation is
required and can be specified only if the STOREF
attribute is specified. This parameter causes the
mainframe defined as being in store and forward
mode (AT=STOREF) to verify that a user is
authorized. This prevalidation is performed in
addition to the normal user validation performed
at the remote host that processes the job.

NVALID

Specifies that USER command prevalidation is not
required and can be specified only if the STOREF
attribute is specified.

NLIST

Specifies that this LID is not available to the end
user through the LISTLID command. LIDs with
this attribute might be reserved for onsite
maintenance purposes.

LID/RHF Configuration Files 10-3

Equipment Configuration Example

Equipment Configuration Example
Figure 10-1 shows an equipment configuration consisting of six mainframes. Figure
10-2 shows the LIDCMid files for the three NOS mainframes in the configuration:
LIDCM64, LIDCM42, and LIDCM05.

SCOPE 2
PID-MF2
LID-SC2
LID-MF2

7683
>*SS^v

C120
PID«120
LID-120

6683

2S5X NPU NETWORK
OR
CDCNET NETWORK

NOS

M I D- 64
PID-M64
LID-M64
LID" AAA
LID-AAB

NAD

MID-42
PID-M42
LID=M42
LID=BBB
LID=BBC

NOS

NAD

NOS/BE
PID=NBE
LID=NBE
LID=CCC

MID°05
PID-M05
LID«M05
LID»DDD

Figure 10-1. Equipment Configuration

10-4 NOS Version 2 Analysis Handbook

Revision M

Equipment Configuration Example

LIDCM64
•LIDCM64 LIDCMID FILE FOR MAINFRAME 64. NOTE THAT LID=LBK IS
• DEFINED AS A LOOPBACK LID AND THAT THE NAM NETWORK IS
DISABLED TO NOS PID=M42.
NPID,PID=M64,MFTYPE=NOSHOST,AT=VALID.
NLID.L1D=M64.
NLID,LID=AAA.
NLID.LID=AAB.
NLID.LID=LBK,AT=LOOPB.
NPID.PID=M42.MFTYPE=NOS42,NETDIS=NAM.
NLID.LID=M42.
NLID,LID=BBB.
NLID.LID=BBC.
NLID.LID=NBE,AT=STOREF/NLIST.
NLID,LID=CCC,AT=STOREF.
NPID,PID=MF2,MFTYPE=SC0PE2,AT=NVAL1D.
NLID,LID=MF2.
NLID,LID=SC2.
NPID.PID=120,MFTYPE=C120,AT=NVALID.
NLID,LID=120.
NPID,PID=M05,MFTYPE=NOS05.
NLID.LID-M05.
NL1D.LID=DDD.
NLID.LID=NBE,AT=STOREF.
NLID.LID=CCC,AT=STOREF.
LIDCM42
•LIDCM42 LIDCMID FILE FOR MAINFRAME 42. NOTE THAT LID=NBE IS
DEFINED AS A STORE AND FORWARD LID FOR THE NOS/BE MAINFRAME.
NPID.PID=M42,MFTYPE=NOSHOST.
NLID,LID=M42.
NLID.LID=BBB.
NLID.LID=BBC.
NLID,LID=M64,AT=STOREF.
NLID.LID=CCC.AT=STOREF.
NLID,LID=NBE.AT=STOREF.
NLID,LID=LBK.AT=LOOPB.
NPID,PID=M64,MFTYPE=N0S64,NETDIS=NAM.
NLID.LID=M64.
NLID,LID=AAA.
NLID.LID=AAB.
NPID.PID=NBE,MFTYPE=NOSBE,AT=NVALID.
NLID,LID=NBE.
NLID,LID=CCC.
NPID,PID=120,MFTYPE=C120.AT=NVALID.
NLID.LID=120.
LIDCM05
•LIDCM05 LIDCMID FILE FOR MAINFRAME 05. AGAIN, NOTE THAT
LID=NBE IS DEFINED AS A STORE AND FORWARD LID FOR THE
NOS/BE MAINFRAME.
NPID,PID=M05,MFTYPE=M05.
NLID.LID=M05.
NLID.LID=LBK,AT=LOOPB.
NLID,LID=M64,AT=STOREF.
NLID,LID=CCC.AT=STOREF.
NLID,LID=NBE,AT=STOREF.
NPID,P1D=NBE,MFTYPE=N0SBE,AT=NVALID.
NLID,LID=CCC.
NLID.LID=NBE.
NPID.PID=M64,MFTYPE=N0S64.
NLID.LID=M64.

Figure 10-2. LIDCMid Files for Example Equipment Configuration

Revision

LID/RHF

C o n fi g u r a t i o n

Files

10-5

Specifying the Size of the LID Table

Specifying the Size of the LID Table
You should specify the size of the LID table (LDT) in central memory with this
CMRDECK entry:
LDT=nnnn.

Va l u e

Description

nnnn Number of central memory words allocated to the LDT
(default=1, minimum=0, maximum=11008).
You can calculate the value for nnnn by using this formula:
(3+lid)*p1d

Va l u e

Description

lid Maximum number of LIDs allowed per PID.
p i d To t a l n u m b e r o f P I D s i n a l l n e t w o r k s .

Building or Rebuilding the LID Table
When you deadstart the system, the system program CDLT automatically looks for the
LIDCMid file under user index 377777s. It will use the file to automatically create the
LID table in central memory.
If the system cannot find the file, or if there are errors in the file, an error message ^^
will be displayed in the dayfile. You can then create or correct your LIDCMid. file ^)
and execute the X.CLDT command to build or rebuild the LID table in central
memory.
To build or rebuild the LID table in central memory, follow these steps:
1. Create or correct your LIDCMid file and ensure that the file is stored as an
indirect access file on user index 377777s.
2. Ensure that all subsystems that access the LID table (NAM, RHF, and SSF) are
not active.
3. Enter this command:
X.CLDT

The system will build or rebuild the LID table in central memory.

10-6

NOS

Version

Analysis

Handbook

Revision

Listing the LID Table

Listing the LID Table
You can use the LISTLID command to list the configuration of the LID table. The
LISTLID command can be executed through an interactive or batch environment. Use
this format for the command:
LISTLID,LID=lid.PID=p1d,L=l1st

Parameter Description
LID = lid

List the attributes of PIDs in which LID lid exists. LID lid
must be enabled and it must be a listable LID. If the LID
keyword is specified, a LID value lid must also be specified. If
the LID keyword is omitted, the default is to list all listable
LIDs.

PID or PID=pid

List the attributes of a given LID (LID=lid specified) or all
LIDs (LID omitted) under a given PID (PID=pid specified) or
all PIDs (PID specified). If the PID keyword is omitted, the
default is to list all listable LIDs specified by the LID
parameter.

L=list

Specifies the local file to which all listable output is to be
written. If the L keyword is omitted, the default is file
OUTPUT.

Changing LIDS Using the LIDOU Display
You can change LIDs by using the LIDOU display. Refer to section 9, L-Display
Utilities, for information about the LIDOU display.

00S

Revision M

UD/RHF Configuration Files 10-7

Specifying Requirements for Running NOS/VE in Dual-State Mode

Specifying Requirements for Running NOS/VE in Dual-State Mode
You must create the appropriate configuration files before users can route batch jobs
from the NOS side of a dual-state system to the NOS/VE side.
You must define the LIDs for NOS/VE batch jobs in the LIDCMid file. You can
define a maximum of 30 NOS/VE LIDs.
Create the indirect access file LIDVEid (id is a 2-character machine identifier for the
mainframe) on user index 377777s. The LIDVEid file is used by the dual-state IRHF
job. This file contains the LIDs to be used for NOS/VE batch jobs, in the following
format:
nvelld 1
nvelid 2
nvelld 30

Each

LID

must

separate

line.

In the LIDCMid file used by CLDT, you should use an NPID statement to define a
PID for the NOS/VE side of your dual-state system and include NLID statements for
each of the LIDs in the LIDVEid file. The PID value used is not significant but must
be unique. In a QTF network environment, you should also define the NOS/VE LIDs
as store and forward (AT=STOREF) under the NOS host PID to allow storing and
forwarding of batch jobs from other hosts through the NOS side of a dual-state
system to the NOS/VE side.

10-8

NOS

Version

Analysis

Handbook

Revision

■' ^ \

RHF Configuration Files

RHF Configuration Files
You must define the RHF configurations including all NADs, applications, and physical
identifiers (PIDs) to be used by or accessible to RHF. You may define multiple
configurations. Each RHF in the network must have its own definition of the
configuration; each definition will be different from the definition of the configuration
for other RHFs in the network. Use the RCFGEN utility to define these configurations.

RCFGEN Utility
The RCFGEN utility reads network configuration statements to create the RHF
configuration record, which RHF uses to define the network and determine proper
access.
Each configuration record has a name of one to seven letters or digits, starting with
a letter. The default name set by RCFGEN when creating a record (and used by RHF
when searching for a record) is RCFpid, where pid is the three-character physical
^^ identifier of the host. You can use the RN=recname parameter on the RCFGEN and
RHF commands to specify a different configuration record name.
When RHF is initiated, it searches for the specified configuration record first on local
file RCFILE, then on permanent file RCFpid (user name SYSTEMX, direct or indirect
access), and finally on the system library.
By default, RHF searches for configuration record name RCFpid. If you provide a
subsystem procedure file for RHF, you can use the command RHF.RN = recname to
specify a different name. Refer to the NOS Version 2 Installation Handbook for
[^ information about creating a procedure file for RHF.

Revision

LID/RHF

C o n fi g u r a t i o n

Files

10-9

RCFGEN Utility

The following command calls the RCFGEN utility.
RCFGEN,1=i nput,L=1i st,O=out put,RN=recname,LO=opt i on.comment s
The parameters are order independent and optional; if omitted, the defaults are used.
Parameter Description
I=input

Specifies the local file from which the network configuration
statements are to be read. The default is file INPUT. If only the
keyword I is specified, file COMPILE is used.

L=list

Specifies the local file to which all listable output is to be
written. The default is file OUTPUT.

0=output

Specifies the local file to which the configuration tables are to
be written. The default is file RCFILE.

RN = recname

Specifies the name given to the configuration record being
generated. The default name, RCFpid, is used if RN is omitted,
if only the keyword RN is specified, or if recname is 0.

L0=option

Specifies the list options used when generating listable output. If
LO is omitted or option is 0, only the network configuration
statements and diagnostics are listed. If only the keyword LO is
specified, macro definitions and table-generating definitions are
also listed. LO=ALL specifies all list options. (The non-default
list options may help analysis of RCFGEN or RHF problems.)

comments

Specifies an optional 1- to 70-character string that is placed in
the prefix table of the configuration record being generated.
(During initiation, RHF displays the string in the job dayfile.)

10-10 NOS Version 2 Analysis Handbook

Revision M

RCFGEN Input

RCFGEN Input
The input to RCFGEN consists of network configuration statements. The syntax of
these statements conforms to COMPASS statements. Configuration statements (except
LNAD and RNAD statements) must not start before character position 3.
Use the following network configuration statements.
Statement Description
LNDR

Defines the maximum number of local NAD drivers (NDRs)
allowed to execute at one time.

APPL

Defines application programs that are allowed to access RHF.

NPID

Defines the physical identifier of a remote mainframe.

PATH

Defines the paths to a remote mainframe through the LCN
network.

LNAD

Defines information necessary to address local NADs.

RNAD

Defines the addressing information necessary to access a
remote NAD.

DEBUG

Defines debug parameters.

CHARGE

Defines the charge that is transferred to a user control point
for each RHF call.

Revision M

LID/RHF Configuration Files 10-11

Statement Order

Statement Order
/*^%

Network configuration statements must be specified in the following order to properly
define a network.
1. LNDR statement (if necessary).
2. APPL statement to define application programs.
3. Sets of NPID and PATH statements that define all portions of the network. The
PATH statement must be associated with a given physical mainframe (NPID
statement). The following structure is required of these statements when defining
a network:
a. NPID statement.
b. All paths (PATH statement) associated with the preceding NPID.
4. LNAD statements to define local NADs.
5. RNAD statements to define hardware addressing of remote NADs.
6. DEBUG and CHARGE statements (order independent).
At least one of each configuration statement is required in the configuration file with
the exceptions of the LNDR, DEBUG, and CHARGE statements. Defaults are specified
in the individual statement descriptions.

10-12

NOS

Version

Analysis

Handbook

Revision

Network Configuration Statements

Network Configuration Statements
The network configuration statements are described in the order that they must be
specified to define a network.
LNDR Statement
The maximum number of NAD drivers is the maximum number of PPs that may
contain a NAD driver at one time, regardless of the number of NADs and the number
of drivers allowed per NAD.
To define the maximum NDRs allowed for all NADs, enter:
LNDR MAXNDRS=nn

Parameter Description

MAXNDRS=nn

Maximum number of PPs that may contain NDRs at any one
time. Default is 4. The maximum value is the number of PPs
available for NAD drivers, nn must not be less than the
largest value specified for MAXNDRS on any LNAD statement.

APPL Statement
Each application definition uses additional RHF field length. This additional field
length is equal to mxcopys*(5 + 3*mxcons) central memory words (mxcopys and mxcons
are defined below). To define an RHF application, enter:
0^s

APPL NAME=name,ENABLED=statUS,MXC0NS=mxcons,MXCOPYS=mxcopys,SVR=status,
ASTART=stat us,SYS0RG=st at us

Parameter

Description

NAME=name

Application name; name is 1- to 7-alphanumeric characters,
where the first character must be alphabetic. Required.

ENABLED=status

Availability of the application when RHF is initiated,
status may be YES or NO. Default is YES.

MXCONS=mxcons

Maximum simultaneous connections that are allowed for
this application. The maximum value for mxcons is 127.
Default is 1.

MXCOPYS=mxcopys

Maximum number of simultaneously active copies of this
application that are allowed. The maximum value for
mxcopys is 127. Default is 1.

Revision M

LID/RHF Configuration Files 10-13

APPL Statement
/*^!\

Parameter

Description

SVR=status Servicer program status; specifies if the application is a
servicer, that is, an application program that is started
automatically by RHF upon request of an application
program on another host, status may be YES or NO.
Default is NO.
ASTART=status

Application startup status; specifies whether the application
is started when RHF is initiated or when the operator
enables the application, status may be YES or NO. If NO is
specified, the application is started by the user, or for a
servicer application, by a request from a remote application.
Default is NO.

SYSORG=status

System origin status; specifies whether the application must
have privileged application status to gain access to RHF.
status may be YES or NO. If status is YES, the application
must have an SSJ= entry point and be loaded from the
system library. If status is NO, the application need not
reside on a system library; however, the user must have
CUCP (system control point) validation. Default is YES.

In determining the number of allowed connections and copies of an application, note
that each NAD has a maximum of 127 active connections. This number is restricted to
35 during NAD controlware loading but may be increased by modifying the appropriate
NAD controlware load parameters in LOADBC.
When defining the APPL statements you must follow certain restrictions for
system-supplied applications QTF, QTFS, PTF, PTFS, and ITF. The maximum
simultaneous connections should be set to one (default) for QTFS, PTF, and PTFS.
The maximum number of simultaneously active copies should be set to one (default)
for QTF and ITF. The maximum simultaneous connections for QTF should be set to
four unless installation parameters ACNMAXC for QTF and MAXFILEXFR for FIP
are changed. The SVR=YES parameter must be specified for QTFS and PTFS and
must not be specified for QTF, PTF, or ITF. ASTART=YES should be specified for
QTF.
For ITF, the maximum simultaneous connections should be equal to the value of the
PI parameter on the ITF command in the JOBITF record on the NAMI startup
master file. The released default is 2.
The MHF application is defined by default in RHF's configuration file; no separate
definition is needed. If you choose to define MHF, you must specify ASTART=YES to
allow initial loading of controlware into local NADs.

■^^k

10-14 NOS Version 2 Analysis Handbook

Revision M

NPID Statement

NPID Statement
Each remote mainframe definition requires three words in RHF's field length. To define
a remote mainframe, enter:
NPID PID=pid,ENABLED=statUS,MFTYPE=type
Parameter

Description

PID=pid

Physical identifier of the remote mainframe; pid must be a
unique 3-character physical identifier. Required.

ENABLED = status

Availability of the mainframe identified by PID. status
may be YES or NO. Default is YES.

MFTYPE=type

Mainframe type; type is any 1- to 7-character string
specifying the mainframe type or mainframe identifier. For
example, you could use NOS1, NOS2, NOS/BE, or CY200.
Required.

yms
PATH Statement

Every path defined for a remote mainframe requires two words in RHF's field length.
To define a path for a remote mainframe, enter:
PATH ENABLED=status,LT=tttt,RT=rrrr,RNAD=raddr,LNAD=laddr,AC=aaaa
Parameter

Description

ENABLED = status

Availability of the path when RHF is initialized, status
may be YES or NO. Default is YES.

LT=tttt

Local trunk control units (TCUs) enabled; tttt is a 4-digit
nonzero binary number indicating the network trunk
connections for the local NAD. Required.

RT = rrrr

Remote TCUs enabled; rrrr is a 4-digit nonzero binary
number indicating the network trunk connections for the
remote NAD. Required.

RNAD=raddr

Symbolic address of the remote NAD entry for this path
referenced in the RNAD statement. Required.

LNAD=laddr

Symbolic address of the local NAD entry for this path
referenced in the LNAD statement. Required.

AC = aaaa

Access code; aaaa is a 4-digit hexadecimal access code for
the remote NAD. Default is 0.

At least one PATH statement is required for each PID defined

jA&$&S

Revision M

LID/RHF Configuration Files 10-15

LNAD Statement

LNAD Statement
Each local NAD definition requires five words in RHF's field length. To define a local
NAD, enter:
laddr LNAD CH=ch,MAXNDRS=n,DEDICATE=status,CMPATHS=nn,CMBUFFS=nn,
AUTODUMP=statUS,AUTOLOAD=StatUS,TRACE=t rw,LOG=statUS

Parameter

Description

laddr

Symbolic address referenced in a preceding PATH
statement. This parameter is required and must begin in
character position 1 or 2.

CH=ch

Channel number; ch is a 2-digit octal number of the
channel to which the NAD is connected.

MAXNDRS=n

Maximum number of NAD drivers that may be assigned at
one time to this NAD. n can be from 1 to 3. Default is 1.

DEDICATE = status

Dedicated channel status; specifies whether the driver will
always hold the NAD channel reservation between
consecutive blocks of one I/O request, status may be YES
or NO. Default is YES. YES should be specified unless
some non-CDC driver requires high-performance access to
the NAD channel.

CMPATHS=nn

Maximum number of convert mode paths. You can specify
a number from 0 to 63. The default is 0. If nn is 0, then
code conversion is done in the CPU. Refer to table 10-1
for additional information.

CMBUFFS=nn

Maximum number of convert mode buffers. You can specify
a number from 0 to 63. The default is 0. Refer to table
10-1 for additional information.

AUTODUMP=status

Automatic dump status; specifies whether RHF will
automatically dump the NAD's memory if the NAD fails,
status may be YES or NO. Default is NO. (YES is
intended for fault analysis along with
TRACE = YES/FULL).

AUTOLOAD = status

Automatic load status; specifies whether RHF will
automatically load the NAD's controlware during
initialization and reload the NAD if it fails, status may be
YES or NO. Default is YES.

10-16 NOS Version 2 Analysis Handbook

Revision M

LNAD Statement

Parameter

Description

TRACE=trw

NAD trace word; controls the value of trace word in the
NAD microcode initialization parameters used by MHF when
loading the NAD (refer to the 380-170 Network Access
Device Reference Manual for a complete description), trw
may be NO (no trace), YES (standard trace buffers), or
FULL (maximum trace buffers). Default is NO.
Because TRACE decreases NAD performance, TRACE should
be specified only for fault analysis. AUTODUMP=YES
should be specified along with TRACE = YES or FULL to
capture the NAD memory dump. TRACE = YES or FULL
produces a trace word value of 2954 or 529F hexadecimal,
respectively.

LOG=status
00&S

Error logging status; specifies if local NAD trunk errors are
to be transmitted by MHF to the mainframe's binary
maintenance log. status may be YES or NO. Default is YES.

The software relies on the NAD to determine the actual number of paths and buffers
reserved for code conversion. The algorithm used by the NAD is:
Paths reserved = the smaller of (paths requested) or (buffers reserved * 2/3).
Buffers reserved = the smaller of (buffers requested) or (total buffers - 2).
The code conversion parameters should be adjusted according to the average number of
concurrently active connections doing code conversion and the average size of the files
being converted. Table 10-1 gives some suggested values for the code conversion
parameters. In this table, the term average connection implies four conversion
connections. The term average file size is a file approximately 500 PRUs long.
Table 10-1. Suggested Code Conversion Parameters
Connections

96K-Byte

NAD

128K-Byte

Less than average connections, average file size 2 paths
3 buffers

2 paths
3 buffers

Less than average connections, large file sizes 2 paths
5 buffers

2 paths
5 Duffers

4 paths
5 Duffers

6 paths
8 buffers

Average connections, average file sizes

Greater than average connections, average file 6 paths
sizes
9
buffers

7 paths
11 buffers

Greater than average connections, large file 5 paths
sizes
9
buffers

6 paths
13 buffers

NAD

r
Revision M

LID/RHF Configuration Files 10-17

RNAD Statement
,>e'^%\

RNAD Statement
Every remote NAD defined requires four words in RHF's field length. To define a
remote NAD, enter:
raddr RNAD ND=nn,DD=d,LOG=status
Parameter

Description

raddr

Symbolic address referenced in a preceding PATH
statement. This parameter is required and must begin in
character position 1 or 2.

ND=nn

Remote NAD address; nn is a 2-digit hexadecimal address
of the remote NAD. Default is 0.

DD=d

Remote NAD exit port; d is a 1-digit hexadecimal address
of the exit port of the remote NAD. Default is 0.

LOG=status

Error logging status; specifies if remote NAD trunk errors
are to be recorded by MHF in the mainframe's binary
maintenance log. status may be YES or NO. Default is
NO. Do not specify LOG=YES if the defined NAD is a
local NAD (as in the case of a loopback path). Instead, use
the LOG parameter on the LNAD statement to control
error logging.

DEBUG Statement
The DEBUG statement controls the manner in which RHF uses queue entries.
DEBUG TRACE=statUS

Parameter

Description

TRACE = status

RHF trace status; specifies whether the RHF trace is on
or off. status may be YES or NO. Default is NO. NO
specifies that RHF trace is off and queue entries freed by
RHF are placed at the top of the empty queue and reused
immediately. RHF uses a slightly smaller amount of
processing time when the RHF trace is off. Default is NO.
YES specifies that RHF trace is on and a queue entry is
reused only after all queue entries ahead of it have been
used. Also, when the RHF trace is on, you can use it for
analysis of an RHF dump and resolution of the associated
RHF problem.

T ^ S

10-18 NOS Version 2 Analysis Handbook

Revision M

CHARGE Statement

CHARGE Statement
The CHARGE statement specifies the amount of system resources a user control point
is charged for an RHF call. RHF distinguishes two different types of calls; those that
require a large amount of processing time and those that require a small amount of
processing time.
CHARGE TYPE=type,CPA=cpa,CPB=cpb,IO=io,CMFL=cm,PP=pp

Parameter Description
TYPE=type

Type of call for which the charge is being specified.
Type Description
Requires small amount of RHF processing time.
Requires large amount of RHF processing time.

CPA=cpa

Time to be charged for central processor cpa (decimal
milliseconds). Default is 2 milliseconds for a type 1 call; 10
milliseconds for a type 2 call.

CPB = cpb

Time to be charged for central processor cpb (decimal
milliseconds). Default is 0.

IO=io

Input/output time to be charged (decimal milliseconds). Default
is 0.

CMFL=cm

Central memory field length to be charged, cm is the field
length in octal divided by 100s. Default is 10s.

PP=pp

PP time to be charged (decimal milliseconds). Default is 0.

A CHARGE statement is not required. You may, however, enter two CHARGE
statements: one for type 1 calls, a second for type 2 calls.

J^^8\

10-22 NOS Version 2 Analysis Handbook

Revision M

QTF Configuration Requirements

QTF Configuration Requirements
You must create the appropriate configuration files before you can perform queued file
transfers using RHF or NAM.

RHF Configuration File Directives
For each copy of QTF that you want RHF to start automatically on a NOS host, you
must include the following network configuration statement in the RCFGEN input file
for that host:
APPL NAME=QTF.MXC0NS=4,ASTART=YES

Refer to the APPL statement under RHF Configuration Files earlier in this section.
Each copy of QTF will establish at most four simultaneous connections. For most
RHF configurations, a single copy of QTF should be sufficient.
To allow a NOS host to receive queued files, you must include the following network
configuration statement in the RCFGEN input file for that host:
APPL NAME=QTFS,SVR=YES,MXCOPYS=n

where n is the maximum number of QTFS servers you want to have active. Each copy
of QTFS services one connection.
Refer to the appropriate reference manuals for other RHF implementations for
information on how to configure non-NOS QTF and QTFS applications and
connections.

0$*S

008S,

0^S.

Revision

LID/RHF

C o n fi g u r a t i o n

Files

10-23

NAM Configuration File Directives

NAM Configuration File Directives
In the NDLP input file, you must include QTFS OUTCALL statements for each PID to
which you want to transfer queued files and one APPL statement for QTF:
QTF: APPL,PRIV,PRU,NETXFR,MXCOPY=n.

where n is the maximum number of QTF initiators you want to have active.
Parameter records in the NAMI job record file NAMSTRT specify which applications
NAM automatically starts. Each default parameter record produced when QTF is
installed includes one JOB(JOBQTF,QT) directive. To automatically start more than
one copy of QTF, you can add additional job records to the NAMSTRT file and must
add additional JOB directives to each parameter record desired. Refer to the NAM5 Network Access Methods Version 1 subsection of the Special Product Installation
Information section of the NOS Version 2 Installation Handbook for more information
on NAMI job records.
Each copy of QTF will establish at most four simultaneous connections for file
transfers. For many NAM configurations, a single copy of QTF should be sufficient.
You might consider using more than one copy of QTF if you expect a large number
of queued file transfers over slow communication lines.
To allow a NOS host to receive queued files, you must include in the NDLP input
file for that host one or more QTFS INCALL statements and one APPL statement for
QTFS:
QTFS: APPL,RS,PRIV,PRU,NETXFR,MXC0PY=n.

where n is the maximum number of QTFS servers you want to have active. Each copy
of QTFS services one connection. Refer to the Network Access Method Network
Definition Language Reference Manual for more information on APPL, INCALL, and
OUTCALL statements.
The default NAMI parameter records include a JOB(JOBQTFS,QS) directive. The
JOBQTFS job record creates or modifies permanent file ZZQTFS, which contains the
job file submitted by NAM to start a new copy of QTFS when necessary.

10-24

NOS

Version

Analysis

Handbook

Revision

QTF Procedure File

QTF Procedure File
The QTF procedure file contains a set of default initialization commands for each of
the two QTF variants, RHF and NAM. You can edit the commands in the procedure
and capture the modified procedure in a new system file without rebuilding QTF, or
you can include UPDATE modifications in the USER file for the RHP installation
procedure. The QTF procedure is deck QTFPROC on the RHPlpsrin program library
file (refer to the NOS Version 2 Installation Handbook).
For the NAM variant, another option is to modify the JOBQTF record (on file
NAMSTRT), which is used to start QTF at NAM initiation.
Format of the call to the QTF procedure file is:
QTF,variant,I=inflie.
Parameter Description
variant

RHF or NAM, identifies which QTF variant to initiate. The
default is RHF.

infile

File name from which initialization commands are to be
processed. Default is to use the commands for the variant
included in the QTF procedure file. QTF reads the
initialization commands until end-of-record. Each command on
the file is a separate line (equivalent to a K-display entry
without the K. prefix). Specifying I = infile is equivalent to
entering the command K.INCLUDE,FILE = infile.

00^S

/SS*V

Revision M

LID/RHF Configuration Files 10-25

Procedure File Example

Procedure File Example
A^m$\

Figure 10-6 shows some typical sets of initialization commands that you can include in
the QTF procedure file. The example assumes you started with the default QTF
procedure file.
,PROC,QTF*I, ...

DATA,XXDEFI
IF,$NAM$.EQ.$NO$.L1.

*
* DEFAULT DIRECTIVES FOR NOS RHF VARIANT
*

SCHED,MAXCONS=4.MAXIMUM OF FOUR CONNECTIONS.
CLASS,SC=A. DEFINE THREE SELECTION CLASSES
CLASS,SC=B. WITH IDENTICAL CRITERIA,
CLASS,SC=C. ALLOWS UP TO 3 CONNECTIONS PER PID.
.ELSE.L1.
^•
.* DEFAULT DIRECTIVES FOR NOS NAM VARIANT
•

A^ms

SCHED,MAXC0NS=4.
CLASS.SC=A,FSI=1..4.
CLASS,SC=B,FSI=1..6.
CLASS,SC=C,FSI=1..6.
CLASS, SC=D, FSI =7, MAXIMUMS. AT MOST ONE LARGE FILE.
DISABLE,SC=D,PID=M03. NEVER ALLOW LARGEST FILES TO M03.
.IF,(TIME.GT.0700).AND.(TIME.LT.1700),PRIME.
INCLUDE,F=PRIME. MUST BE LAST DIRECTIVE
.ELSE,PRIME.
INCLUDE,F«=OFF. MUST BE LAST DIRECTIVE
.ENDIF,PRIME.
.ENDIF,Ll.
.DATA,PRIME
. PRIME-HOURS PARAMETERS
. ENTER "K.INCLUDE,F=PRIME." TO CHANGE NAM PARAMETERS
DISABLE,SC=D. NO LARGE FILES DURING PRIME TIME.
ENABLE,SC=B,PID=M03. PERMIT MEDIUM FILES TO M03.
ENABLE,SC=C,PID=M03.
.DATA,OFF
. OFF-HOURS PARAMETERS
. ENTER "K.INCLUDE,F=OFF." TO CHANGE NAM PARAMETERS
ENABLE,SC=D. ALLOW LARGE FILES EXCEPT TO M03.
DISABLE,SC=B,PID=M03. DISALLOW MEDIUM FILES TO M03.
DISABLE,SC=C,PID=M03.

■^^s

Figure 10-6. Procedure File Example

10-26 NOS Version 2 Analysis Handbook

Revision M

Mass Storage Extended Subsystem (MSE) 11
Introduction
MSE
Utilities
Utility
Description
Te r m i n o l o g y
Cartridge
SM
Map
..
7990
Catalog
,
7990
Files
SSEXEC
Subfamily
....
Group
..
Volume

.'.

MSE
Utilities
SSDEF
SSLABEL
SSLABEL
Directives
OP=AS
—
Add
SMs
OP=RS
—
Remove
SMs
OP=AB
—
Add
Cubicles
:..
OP=RB
—.
Remove
Cubicles
OP-AM
—
Add
Cartridges
.
.
OP=RM
—
Remove
Cartridges
OP=RC
—
Restore
Lost
Cartridges
OP=FX
—
Fix
Cartridge
Labels
OP=IB — Control Cartridge Allocation
OP=FC
—
Free
Cartridge
Files
Parameters
for
SSLABEL
Directives
SSLABEL
Update
Sequence
..
Restrictions
to
SSLABEL
SSLABEL
Example
SSMOVE
■
...
SSMOVE
Directives
S p e c i fi c
File
(SF)
Directives
Va l u e
S p e c i fi e r
Directives
Excluding
Destage/Release
Processing
Selection
Algorithms
.
Destage
and
Release
Algorithms
...
Decision
Algorithm
Hierarchy
Disk
Space/Dump
Ta p e
Management
Restrictions
to
SSMOVE
Output
Example
S S VA L
Release
Processing
..
Problem
Reporting
Error
Detection
and
C l a s s i fi c a t i o n
SM
Map
Analysis
7990
Catalog
Analysis
PFC
Analysis
Release Processing and Problem Fixing
Va l i d a t i o n
Report
Error
Types
1
and
2
Error
Types
3
and
4
Error
Types
5,
6,
and
7

11 - 1
11 - 2
11 - 3
11 - 3
11 - 3
11 - 5
11 - 11
11 - 1 2
11 - 1 2
11 - 1 2
11 - 1 2
11 - 1 3
11 - 1 3
11 - 1 4
11 - 1 5
11 - 1 6
11 - 1 6
11 - 1 6
11 - 1 6
11 - 1 7
11 - 1 7
11 - 1 7
11 - 1 8
11 - 1 8
11 - 1 8
11 - 1 9
11 - 2 2
11 - 2 3
11 - 2 3
11 - 2 4
11 - 2 7
11 - 2 7
11 - 2 8
11 - 3 2
11 - 3 2
11 - 3 3
11 - 3 4
11 - 3 5
11 - 3 5
11 - 3 6
11 - 4 0
11 - 4 2
11 - 4 3
11 - 4 3
11 - 4 3
11 - 4 4
11 - 4 5
11 - 4 6
11 - 4 7
11 - 4 7
11 - 4 7
11 - 4 7

Intersections
,...
■. . . . —
•
11 - 4 8
Va l i d a t i o n
Report
Example
11 - 4 8
Typical
S S VA L
Runs
11 - 4 9
Restrictions
to
S S VA L
.....
....
H-50
SSUSE
•
H-51
Basic
Usage
Report
................
.
11 - 5 3
Optional
Report
A
11 - 5 6
Optional
Report
B
,
..
11 - 5 7
Optional
Report
C
. . . . . .■
.
H-58
Optional
Report
D
...
11 - 5 9
SSDEBUG
H-60
SSDEBUG
Directives
11 - 6 1
OP=RS.—
Read
AUs
11 - 6 1
OP=RF
—
Read
File
,
11 - 6 1
O P - R P — R e l e a s e F r o z e n C h a i n S p a c e , . . . . . . . 11 - 6 1
OP=RL — Remove Cartridge Entry From 7990 Catalog 1.1-61
O P = R C — R e m o v e C a r t r i d g e E n t r y F r o m S M M a p 11 - 6 1
OP-CF — Change Flag in SM Map or 7990 Catalog 11-61
P a r a m e t e r s f o r t h e S S D E B U G D i r e c t i v e s . . . 11 - 6 2
Using
SSDEBUG
.............
11 - 6 5
Restrictions
to
SSDEBUG
,.
11 - 6 6
y, z R e l a t i o n s h i p w i t h S M M a p O r d i n a l 11 - 6 6
Format of Disk Files Read From 7990 by SSDEBUG 11-67
7990
Stripe
Header
and
Trailer
11 - 6 9
7990
Block
Header
and
Trailer
11 - 7 0
SSBLD
..
H-71
SSBLD
Statements
....
11 - 7 1
Node/Path
Linkage
Statements
11 - 7 1
SM/CU
Linkage
Statements
11 - 7 3
SSBLD
Example
.,
11 - 7 3
7 9 9 0 E q u i p m e n t C o n fi g u r a t i o n C o n s t r a i n t s 1 1 - 7 4
S S A LT E R
11 - 7 5
Console
Input
11 - 7 5
MSE
Operational
Procedures
....
11 - 7 8
Initialization
11 - 7 8
Disk
Space
Management
—
11 - 7 9
7990
Space
Management
11 - 8 0
Backup
and
Recovery
—
11 - 8 2
File
Dumping
■. . . ...
11 - 8 2
Full
Dumps
,,
11 - 8 2
Incremental
Dumps
..
11 - 8 3
Dump
Ta p e
Management
11 - 8 3
SM
Map/7990
Catalog
Backup
11 - 8 4
File
Reloading
.......
.............
..,
11 - 8 5
E r r o r C o n d i t i o n s a n d C o r r e c t i v e A c t i o n s 11 - 8 6
C l e a r i n g P e r m a n e n t F i l e E r r o r F l a g s . . . . . . . . . . 11 - 8 6
Permanent
File
Recovery
......
11 - 8 6
Cartridge
Restoration
and
Reuse
11 - 8 7
R e m o v a l o f F a u l t y o r M i s s i n g C a r t r i d g e s 11 - 8 8
7990
Catalog/SM
Map/PFC
Problems
11 . - 8 9
7 9 9 0 C a t a l o g / S M M a p M i s m a t c h . . . . . . 11 - 8 9
7990
Catalog
Chain
Problems
11 - 9 0
PFC/7990
Catalog
Mismatch
11 - 9 0

~ )

^ %

Mass Storage Extended Subsystem (MSE) 11
Introduction
The Mass Storage Extended Subsystem (MSE) is the product consisting of the 7990
hardware, the channel interface, the diagnostics, and the operational software.
The 7990 hardware is a large-capacity online mass storage device, which is a
cost-effective extension to the disk file storage system and an alternative to
conventional magnetic tape storage. Storing files on the 7990 retains the security, data
integrity, and online access capabilities provided by disk and reduces the operational
and data integrity problems caused by storing, retrieving, and mounting tape volumes.
You can use both the 7990 and magnetic tapes to protect files from hardware and
system failures.
The 7990 hardware is composed of the following components:
Component Description
Cartridge

A plastic housing that encloses magnetic tape on which data is
stored under program control. This cartridge is compatible with an
IBM 3850 cartridge.

7991 Storage
Module (SM)

The hardware unit that houses up to 312 usable data cartridges.
The SM also consists of the cartridge accessor unit, which picks
cartridges from and puts cartridges in their cubicles, and one or
two data recording drives (DRD), which read data from and write
data to the cartridges. The cubicles are assigned coordinate
locations that are identified by the ordered pair (y,z), where the z
axis is horizontal and the y axis is vertical.

7990 Control
Unit (CU)

The hardware unit that is the controller for up to four 7991 SMs.
The CU acts like a tape controller for up to four IBM channel
interfaces and includes one or two data recording controllers
(DRCs). The MSE software supports up to two IBM channel
interfaces per CYBER mainframe.

r
Revision M

Mass Storage Extended Subsystem (MSE) 11-1

MSE Utilities

MSE Utilities
The basic function of MSE is to store data on the 7990 and move it to disk upon
request for access by an authorized user. Control of file movement between a disk and
a 7990 is transparent to the applications programmer; however, there are operational
changes and additions that site personnel should note. These include modifications to
operational procedures in the areas of permanent file backup, permanent file recovery,
and disk space management. In addition, new MSE utilities are introduced. Detailed
information about the call and operation of each MSE utility, listed next, is included in
this section.
Utility

Description

SSDEF

Creates the system files (SM maps and 7990 catalogs) necessary for
MSE processing.

SSLABEL

Manages allocation of cubicles and assignment of cartridges in
the SM.

SSMOVE

Controls the destaging of files (creating 7990 images) and the
release of disk space.

SSVAL

Controls the release of 7990 space and analyzes the SM maps, 7990
catalogs, and PFC entries to identify and flag discrepancies within
these three components.

SSUSE

Provides reports on the assignment and availability of cartridges
and cubicles within an SM.

SSDEBUG

Corrects error conditions detected by SSVAL and recovers data from
7990 cartridges.

SSBLD

Builds the unit device table (UDT) for SSEXEC. The UDT describes
the 7990 hardware configuration.

SSALTER

Provides dynamic modification of the 7990 hardware configuration.

11-2 NOS Version 2 Analysis Handbook

Revision M

Utility Description Terminology

Utility Description Terminology
Review the following terms; they are defined as used in the descriptions of the MSE
utilities later in this section.
Cartridge
A cartridge is the 7990 storage component consisting of magnetic tape. The 7990
hardware always writes or reads 6652 8-bit byte records, called stripes, to or from the
magnetic tape. Each cartridge has 27,087 stripes. The first 20 stripes contain a
manufacturer's label. The second 20 stripes contain a 7990 cartridge label written by
the SSLABEL utility. The remaining 27,047 stripes are organized into software-defined
allocation units (AUs) of 14 stripes each for a total of 1931 AUs per cartridge.
An allocation unit is the smallest allocatable portion of a cartridge. One or more AUs
may be allocated to contain data for a single file. The allocated AUs for each file are
organized into volumes (definition follows), which are chained together in the 7990
catalog to identify the sequence of AUs that must be accessed in order to read a file.
A head-of-chain (HOC) flag identifies the first volume in the chain, a link field
identifies the next volume in the chain, and an end-of-chain (EOC) flag identifies the
last volume in the chain.
The addition, removal, and reassignment of cartridges are managed by the MSE
utilities. The cartridge labels, and also the 7990 catalogs and SM maps (definitions
following), contain information concerning the location and content of the cartridges.
The descriptions of the MSE utilities later in this section contain further information
on cartridge management.
SM Map
An SM map is a direct access permanent file that contains information indicating how
cubicles in an SM are assigned to a family and identifying the cartridges that reside in
the SM. There is one SM map for each SM in the configuration. The permanent file
name of the SM map is SMMAPi, where i is the SM identifier (a letter from A to H);
its user index is 377760s; and its family is the default family on the mainframe on
which SSEXEC executes (refer to the definition of SSEXEC later in this section).
An SM map contains an entry for each possible coordinate pair (y,z) that identifies a
cubicle in the SM, from (0,0), which is bottom left, to (21,15), which is upper right.
Certain coordinate pairs are reserved for customer engineering use, system use, and
diagnostic purposes.

0ms

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 3

SM Map

Each entry in an SM map has this format:
59

ord

code
6

'///A

sub
family

familyname
id

unused
csn

Field

Description

code

Number from 0 to 6 indicating how the cubicle is assigned.
code Description
Unassigned.
Reserved for customer engineer.
Reserved for system use.
Reserved for a different SM map.
Assigned to the cartridge scratch pool.
Assigned to a subfamily.
No cubicle exists at these coordinates.

ord

Ordinal for this cubicle in the 7990 catalog of the subfamily to
which the cubicle is assigned. This ordinal is referred to as the
FCT ordinal (refer to the definition of 7990 catalog, next). This
field is meaningful only if code = 5.

familyname

The 7-character name, in 6-bit display code, of the family to which
the cubicle is assigned. This field is meaningful only if code = 5.

Linkage error flag that is set by the SSVAL utility when an SM
map entry of a cubicle assigned to a family has no corresponding
entry in the 7990 catalog.

subfamily

Number from 0 to 7 identifying the subfamily to which the cubicle
is assigned. This field is meaningful only if code = 5.

Letter from A to H identifying the SM.

Cartridge manufacturer code.
cm

csn

Description

A-

Cartridge manufacturer is IBM.

B-

Reserved for future cartridge manufacturer.

The 8-character cartridge serial number of the cartridge assigned to
the cubicle. If no cartridge is assigned, this field contains spaces.

1. The pool is an area of the SM that stores scratch cartridges managed by the SSLABEL utility.

11-4 NOS Version 2 Analysis Handbook

.^^\

Revision M

7990 Catalog

The zero entry in the SM map is the map header entry. In this entry the code field is
6, the leftmost 6 bits of the second word contain the SM identifier, and the remaining
bits contain the permanent file name of the SM map.
The SM map is updated whenever the SSLABEL, SSVAL, or SSDEBUG utility causes
a change in cubicle or cartridge assignment. It is recommended that the SM map be
backed up after every update to avoid problems such as:
• Mismatches between SM map and 7990 catalog entries
• Lost SM maps because of a disk failure or other problem
• Attempts to access cartridges that are no longer available
• Attempts to store cartridges in cubicles that are no longer empty
Thus, you should make a copy of the SM map on tape or another device or family in
order to retain the latest version of the SM map. If a device containing SM maps is
reloaded, the latest version of the SM maps should be recovered from the backup copy
after the reload is completed. After recovering the SM maps, you should run the
SSVAL utility to check that the entries in the SM maps and 7990 catalogs match. If
there are inconsistencies, corrective action should be taken as described under Error
Conditions and Corrective Actions later in this section.
7990 Catalog
A 7990 catalog is a disk-resident direct access permanent file that contains information
describing which allocation units of each cartridge assigned to a particular subfamily
are allocated to 7990 files and which AUs are available for allocation. There is one
7990 catalog for each subfamily of a family that can have 7990-resident files, and it
resides on the master device for the subfamily. The permanent file name of the 7990
catalog file is SFMCATi and its user index is 37776is, where i is the subfamily
identifier (a number from 0 to 7). For example, file SFMCAT3 and user index 377763s
identify the 7990 catalog for subfamily 3.
A 7990 catalog is partitioned into subcatalogs, one subcatalog for each SM used by
the subfamily. The maximum number of subcatalogs in a 7990 catalog is eight (the
maximum number of SMs in a configuration). Each subcatalog consists of two parts,
the file and cartridge table (FCT) and the allocation summary table (AST). The FCT
has an entry for each cartridge assigned to the subfamily from the given SM. The
maximum number of FCT entries in a subcatalog is 312 (the maximum number of
cartridges in an SM). The AST contains information used by the allocation algorithm
to select the cartridges on which a file will reside.

y<^\

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 5

7990 Catalog

The first part of the 7990 catalog contains a header and at most eight subcatalog
entries. The header identifies the family and subfamily of the 7990 catalog. Each
subcatalog entry contains the length and location of its FCT and AST, the SM
identifier, unallocated AUs available for small and large files, and the date and time of
the last SSVAL run that resulted in the release of 7990 space assigned to orphan files.
The format of the header is:
59

17
11
sub
family

2 0

W////A id

familyname
unused
unused

Field

Description

familyname

The 7-character name, in 6-bit display code, of the family for this
7990 catalog.

subfamily Number from 0 to 7 identifying the subfamily for this 7990 catalog,
id Number identifying this file as a 7990 catalog file, id is set to 1.
The format of the subcatalog entry is:
59

411

FCT loc

length
unused

AUs small

AST loc

11
unused

date time
AUs large

AUs group

unused

Field

Description

SM identifier for the subcatalog (a letter from A to H).

length

Number of FCT (and AST) entries in the subcatalog.

FCT loc

Location (beginning PRU number) of the FCT.

AST loc

Location (beginning PRU number) of the AST.

date time

Date and time of the last releasing of orphan files on the SM
identified by id.

AUs small

Total number of free AUs available for small files on all cartridges
in this SM.

AUs large

Total number of free AUs available for large files on all cartridges
in this SM.

AUs group

Maximum number of free AUs available within one group in
this SM.

s*^S,

11-6 NOS Version 2 Analysis Handbook

Revision M

7990 Catalog

Each cubicle from the given SM assigned to the subfamily has an entry in the FCT of
the subcatalog. This entry contains the coordinates (y,z) of the assigned cubicle. If a
cartridge has been assigned to the cubicle, the FCT entry also contains the csn of the
cartridge, usage information, status flags, and information about each of the AUs of the
assigned cartridge. The format of each FCT entry is:
59

55 53 51

32 29

2 0

csn
y
ocU ocl2

z
OCl.|

first AU large
first
stripe stripe

cm
first AU small
max AUs

pru

ord

flags
cdp

oclu

unused
unused

flawed AU

read stripe count

write stripe count

soft read error

soft write error

hard read error

demarked stripe

load count

cartridge link

load error

cartridge link

•
•
•
cartridge link

cartridge link

Field

Description

csn

The 8-character cartridge serial number, in 6-bit display code, of
the cartridge assigned to this cubicle. If no cartridge is assigned,
this field contains spaces.

Cartridge manufacturer code.
cm

Description

A- Cartridge manufacturer is IBM.
B- Reserved for future cartridge manufacturer.
y

y coordinate of this cubicle.

z coordinate of this cubicle.

first AU large

First free AU available for large files in this cartridge.

first AU small

First free AU available for small files in this cartridge.

Revision M

Mass Storage Extended Subsystem (MSE) 11-7

7990 Catalog

Field

Description

fl a g s O n e o f t h e f o l l o w i n g fl a g s :
Bit

Description

17 Inhibit allocation flag indicating that space from the
cartridge assigned to this cubicle is not to be allocated
to a file. This flag is set or cleared by a directive to
the SSLABEL utility.
16 Lost cartridge flag indicating that the cartridge assigned
to this cubicle was not there the last time SSEXEC
tried to pick it. This flag can be cleared by a directive
to the SSLABEL utility.
15 Excessive write parity error flag set by SSEXEC when
an error threshold has been passed. Space from this
cartridge is not to be allocated. This flag can be cleared /tmk^
b y a d i r e c t i v e t o t h e S S D E B U G u t i l i t y. )
14 Linkage error flag indicating that the SM map entry for
the location (y,z) is inconsistent with the FCT entry.
This flag is set by the SSVAL utility and cleared by the
SSDEBUG utility.
13 Free cartridge flag. When this flag is set, SSEXEC
inhibits further allocation. Files can be removed by
running the SSVAL utility. This flag is set or cleared
by a directive to the SSLABEL utility.
12

Reserved.

ord Ordinal of the FCT entry in the subcatalog.
ocli Off-cartridge link specifying the ordinal of the FCT entry for the
cubicle containing the next cartridge on which the file on the
cartridge assigned to this cubicle resides. If a file does reside on
m u l t i p l e c a r t r i d g e s , t h e e n t i r e fi l e m u s t b e c o n t a i n e d w i t h i n a ^ s ^
16-cartridge group. Also, since there are only three off-cartridge j
link fields, if a cartridge contains several files, only three can be
contained on other cartridges.

11 - 8

NOS

Version

Analysis

Handbook

Revision

7990 Catalog

Field

Description

first stripe

First usable stripe following the cartridge label. This field is set
to 40.

stripe

Number of stripes in each AU. This field is set to 14.

pru

Number of PRUs that can be written on each stripe. This field is
set to 13.

max AUs

Maximum number of AUs in a cartridge. This field is set to 1931.

cdp

Cartridge division point between small and large files kept on the
same cartridge. The cartridge division point is defined with the
B=n parameter to an SSLABEL directive. The default is B = 600,
specifying that the first 600 AUs of a cartridge are available for
small files.

oclu

Off-cartridge link usage field. When an ocli field is used, a
corresponding bit is set in this field. Bit 0 is set for ocli, bit 1 is
set for ock, and bit 2 is set for ocl3.

flawed AU

Number of flawed AUs on this cartridge.

read stripe count

Accumulated number of stripes read from this cartridge.

write stripe
count

Accumulated number of stripes written to this cartridge.

soft read error

Accumulated number of soft read errors detected on this cartridge.

soft write error

Accumulated number of soft write errors detected on this cartridge.

hard read error

Accumulated number of hard read errors detected on this cartridge.

demarked stripe

Accumulated number of stripes demarked on this cartridge.

load count

Accumulated number of times this cartridge has been loaded for a
read/write operation.

load error

Accumulated number of cartridge load errors detected using this
cartridge.

r
Revision M

Mass Storage Extended Subsystem (MSE) 11-9

7990 Catalog

Field

Description
j*S$S

cartridge link There is a 30-bit cartridge link field for each AU in the cartridge. j
The bits are divided into the same fields and represent the same
information for each AU.
Bit(s) Description
29 Free/busy flag indicating whether or not this AU is
currently allocated to a file.
28

Unused.

27 AU conflict flag indicating an allocation conflict
involving this AU. This flag is set by the SSVAL utility
or by SSEXEC.
26 Frozen chain flag indicating a problem with this
allocation chain. This flag is set by the SSVAL utility
or by SSEXEC. This AU is not reused until this flag is '^
cleared by a directive to the SSDEBUG utility.
25 Start of fragment flag indicating this AU is the
beginning of a chain fragment.
24 Flawed AU flag indicating this AU is not to be
allocated to a file.
23 Continuation AU flag indicating whether or not this AU
is the first AU of a volume. If this flag is clear, the "'^^
AU is the first AU of the volume; if set, the AU is not
the first AU of the volume.
22-21 Off-cartridge link field indicating that the next volume
of the file is on another cartridge. The next cartridge is
identified by one of the ocli fields. The value of the
off-cartridge link flag (1, 2, or 3) specifies which ocli
field to use. The link field specifies the number of the
first AU on the next volume of the file. This field is ^^
meaningful only if the chain control field indicates that ]
this volume is the first or middle volume of the file.
20-19 Chain control field indicating whether this volume is
the first (1), last (2), only (3), or middle (0) volume of
the file.
18-12 File length field indicating the number of AUs in the
file following the first accessed AU.
11-0 Link field indicating the first AU on the next volume of
the file. If the continuation AU flag is clear, this field
contains the ordinal of the first AU of the volume. If
the continuation AU flag is set, this field contains the
ordinal of the first AU within the volume.

11 - 1 0

NOS

Version

Analysis

Handbook

Revision

7990 Files

j^ms

The 7990 catalog is updated whenever the SSLABEL, SSMOVE, SSVAL, or SSDEBUG
utility causes a change in cartridge or cubicle assignment that affects the subfamily.
Because the 7990 catalog for a subfamily resides on its master device, it will be
backed up by PFDUMP whenever the master device for the subfamily is dumped.
Consequently, when PFLOAD reloads all files, the 7990 catalogs are automatically
recovered and all 7990-resident files as indicated in a recovered PFC will also have
entries in the recovered 7990 catalog. Thus, no special operational procedures are
needed to back up a 7990 catalog. It is possible, however, that the 7990 catalog will be
inconsistent with the SM maps or cartridge labels. If such inconsistencies do exist,
corrective action will have to be taken as described under Error Conditions and
Corrective Actions later in this section.
7990 Files
In an MSE environment, permanent files can be categorized according to whether or
not they reside on 7990. A disk file is a permanent file that resides on disk but not on
7990. A 7990 file is a permanent file that resides on 7990 and may or may not also
reside on disk, depending on how the disk space is managed (refer to Disk Space
Management later in this section). Depending on backup requirements (BR parameters),
both disk and 7990 files can also have backup images on tape (refer to the NOS
Version 2 Reference Set, Volume 3).
When a user defines a direct access file, initially it is a disk file. A disk file becomes
a 7990 file when it is destaged to 7990; that is, an image of the file is created on
7990. Files are destaged through use of the SSMOVE utility, which is run periodically
to manage disk space. When SSMOVE is run, files are destaged to 7990 and/or their
disk space released depending on certain file characteristics (refer to SSMOVE later
in this section). Thus, after an SSMOVE run a file can reside on disk, on 7990, or on
both. If the file does have a 7990 image, the asa field in the PFC entry for the file
indicates the location of the 7990 copy.
When a user attaches a 7990 file, it is staged to disk from 7990 (that is, a disk
image is created) if the file is not on disk. If a direct access file is attached in write
mode, the AFOBS flag is set in the PFC entry for that file. The current version of
the file resides on disk only. If an indirect access file is replaced or appended to, the
asa field is cleared in the PFC entry for that file. Setting the AFOBS flag or clearing
the asa in the PFC ensures that the current version of the file will be copied to 7990
when that file is again selected for being released from disk.
If the file is purged, its disk space, but not its 7990 space, is immediately released.
The SSVAL utility must be run to release 7990 space allocated to purged files. Thus,
because a purged file has no PFC entry linking to its 7990 catalog entry, the 7990
image that still exists before SSVAL is run is called an orphan file. However, a user
can never access an orphan file.
When a file is destaged to 7990, control information is written on each stripe to
which the file data is written. This information is sufficient to identify the file.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 11

SSEXEC

SSEXEC
SSEXEC is the main processing program that is responsible for controlling MSE
activities. The MSE utilities issue requests to SSEXEC to destage files from disk to
7990, purge unneeded 7990 files, label or relabel cartridges, update SM maps and 7990
catalogs, and so forth. In a multimainframe environment, two versions of this program
exist: the mainframe to which the 7990 device is physically connected (the master
mainframe) has a program called SSEXEC, and all other mainframes (the slave
mainframes) have a program called SSSLV. Refer to section 13, Multimainframe
Operations, for more information.
Subfamily
Each permanent file family consists of eight subfamilies, subfamily 0 through
subfamily 7. The lower 3 bits of the user index identify the subfamily to which a user
belongs. For example, a user whose index ends in 3 (or Oil in bit notation) belongs to
subfamily 3. When the SSDEF utility is run to create MSE system files, the SM maps
are created on the master device under user index 377760s (subfamily 0) and one 7990
catalog is created under each user index 37776is (subfamily i), i=0,1,2,...,7. When the
SSLABEL utility is used to assign an SM, cubicle, or cartridge to a family, it is
possible to specify assignment to particular subfamilies of the family.
Group
A group is a software-defined structure for allocating cartridges within a subfamily. A
group of cartridges is a number of cartridges (up to 16) in which files belonging to a
subfamily can reside. Any file can overflow from one cartridge in a group to any other
cartridge in the same group. However, no file can overflow from a cartridge in one
group to any cartridge in another group. Cartridges are placed in or removed from
specific groups by using the SSLABEL utility. The SSVAL utility compares the 7990
catalogs (for each subfamily) with the same information obtained from the PFC entries.
Volume
A volume is a software-defined structure used to simplify the allocation and access of
large 7990 files. Up to 128 consecutive AUs in a cartridge that have the same status
(either allocated or hot allocated) are considered to belong to the same volume. These
consecutive AUs are composed of stripes that all have the same volume serial number
(a physical identifier that is written to the tape on the cartridge). The MSE software
fills cartridges (unallocated volumes) from the beginning to the end with no rewinding.
This action minimizes repositioning of the tape in a cartridge for multivolume files.
When a file is staged back to disk, the control information on each stripe is verified.
If a discrepancy is detected, an error message is issued, the file stage is aborted, an
error flag is set in the PFC entry to indicate that the 7990 file could not be accessed,
and the AU conflict flag is set in the 7990 catalog entry for the particular
cartridge(s) and AU(s).

<^ES3s

11 - 1 2

NOS

Version

Analysis

Handbook

Revision

MSE Utilities

0^\.

MSE Utilities
MSE utilities are described next. All of these utilities must be run from system origin
jobs. In a multimainframe environment, the SSDEF, SSUSE, and SSBLD utilities can
be run on any mainframe that has access to the family being processed. However, the
remaining utilities must be run on the mainframe on which SSEXEC executes.

SSDEF
SSDEF creates the system files (SM maps and 7990 catalogs) that are necessary for
MSE processing. If an SM is added to the 7990 hardware configuration, SSDEF is used
to create the SM map for that SM. If a family is to be permitted to have 7990-resident
files, SSDEF is used to create the eight 7990 catalogs for that family (one catalog for
each subfamily).
NOTE
If the SM parameter is specified, SSDEF will create an SM map for the specified SM
(refer to the definition of SM map earlier in this section). It is recommended that the
SM map be copied on tape or on another device or family immediately after it is
created.
The format of the SSDEF command is:
SSDEF,Pi,P2-

Description

FM=familyname Family for which 7990 catalogs are to be created, one catalog for
each subfamily.
F M S a m e a s F M = s y s t e m d e f a u l t f a m i l y.
FM omitted No 7990 catalogs are to be created. SM = id or SM must be
specified.
SM=id SM identifier of the SM for which an SM map is to be created; id
is a letter from A to H.
SM

Same

SM=A.

SM omitted No SM map is to be created. FM = familyname or FM must be
specified.
Example:
SSDEF,SM=B.

SMMAPB, the SM map for SM B, is created, and its entries are as described in the
previous definition of SM map earlier in this section. However, since SSDEF does not
assign cubicles, the entries for cubicles available for use initially indicate that the
cubicles are unassigned.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 1 3

SSLABEL

SSLABEL
SSLABEL manages cartridge assignment and cubicle allocation in an SM. The following
functions are performed through use of directives to SSLABEL.
Add an SM to a subfamily (AS directive).
Remove an SM from a subfamily (RS directive).
Add cubicles to a subfamily, the pool, or the reserved area (AB directive).
Remove cubicles from a subfamily, the pool, or the reserved area (RB directive).
Add cartridges to a subfamily or the pool (AM directive).
Remove cartridges from a subfamily or the pool (RM directive).
Restore an abnormally removed cartridge (RC directive).
Repair a cartridge label or overwrite a family label (FX directive).
Inhibit or allow further allocation of files to a cartridge (IB directive).
Initiate freeing all files from an existing cartridge (FC directive).
Input to SSLABEL is via a directive file. SSLABEL reads the appropriate SM maps
and 7990 catalogs to determine how to process each directive and then issues requests
to SSEXEC to read and/or write cartridge labels and to update the SM maps and 7990
catalogs. SSLABEL generates a report detailing the action taken for each input ^^
directive. If the assignment information or cartridge label is not appropriate or conflicts j
with data in the SM map or 7990 catalog, the cartridge label information is included
on this report and the cartridge is put into the exit tray. It may be possible to restore
such a cartridge, as described under Cartridge Restoration and Reuse later in this
section.
NOTE
SSLABEL updates the SM map for the specified SM (refer to the definition of SM map
earlier in this section). It is recommended that the SM map be copied on tape or on
another
device
or
family
immediately
after
each

11 - 1 4

NOS

Version

Analysis

Handbook

Revision

update.

SSLABEL Directives

The format of the SSLABEL command is:
SSLABEL,Pi,P2.

Description

I=filename File containing the directives to SSLABEL.
I

Same

I N P U T.

I o m i t t e d S a m e a s I = I N P U T.
L=filename File on which listable output is to be written.
L

Same

L = O U T P U T.

L = 0 N o o u t p u t fi l e i s t o b e g e n e r a t e d .
L o m i t t e d S a m e a s L = O U T P U T.
V Z Directives are contained on the SSLABEL command. The I
parameter is ignored.
Z omitted Directives are contained on the file specified by the I parameter.
SSLABEL Directives
The directives to SSLABEL can be specified on a separate file (specified by the I
parameter) or after the SSLABEL command (Z specified). If on the input file, each
^ directive must be specified on a separate line using the OP=directive option.
Parameters for a directive are on the same line, are separated by commas, and end
with a period:
0P=directive,Pi,P2,...,pn.

Example 1:
SSLABEL,I=DIRFILE.

/^ DIRFILE is the directive file; it contains the following directives:
0P=AM,N=4,PK=D.
OP=RM,CN=44455566,FM,SB=1,PK=F.

Two directives to SSLABEL are specified. OP=AM adds four cartridges to the pool of
SM A (SM parameter not specified). OP=RM removes the cartridge whose csn is
44455566 from subfamily 1 of the default family. (Refer to the following descriptions of
directives and parameters.)
If the directives are contained on the command, they follow the command terminator.
The first character following the terminator is the separator. Any character that does
not appear in any of the directives can be used as the separator character. Each
directive must be preceded by the separator and terminated by a period.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 1 5

SSLABEL Directives

Example 2:
SSLABEL,Z./0P=AM,N=4,PK=D./0P=RM,CN=44455566,FM,SB=1,PK=F.

The slant is used as the separator. This command performs the same functions as those
in the preceding example.
The following directives are available with SSLABEL. Some of these directives cause
cartridges to be physically moved to and from cubicles and the input or exit tray
(refer to OP=AM, OP=RM, OP=RC, and OP=FX in the following paragraphs). The
remaining directives cause only logical operations to occur, updating the MSE system
files. Descriptions of the parameters for these directives follow the directives.
OP=AS — Add SMs
OP=AS adds an SM to a subfamily. The 7990 catalog for the specified subfamily is
updated to reflect that cartridges and permanent files for the subfamily can reside on
the specified SM. This directive, however, does not manipulate cartridges or cubicles.
OP=RS — Remove SMs
OP = RS removes an SM from a subfamily. The 7990 catalog for the specified subfamily
is updated to reflect that cartridges and permanent files for the subfamily cannot
reside on the specified SM. Before OP=RS can be specified, all cubicles in the specified
SM must have been removed previously from the family (refer to the OP=RB
directive). This directive, however, does not manipulate cartridges or cubicles.
OP=AB — Add Cubicles
OP=AB adds an unassigned cubicle within an SM to a subfamily (PT=F), the pool
(PT=P), or the reserved area of the SM (PT=R). More than one cubicle (N = n) can be
added at a time. Specific cubicles (YI and Zl parameters) can be added, but they must
be currently unassigned. For PT=R, YI and Zl must be used to add multiple cubicles;
N=n is not valid. The SM map is updated to reflect the new assignment of cubicles.
When PT=R is specified, the cubicle is reserved to a different SM map. Cubicles
reserved for system use, storage module maintenance, or customer engineering use are
reserved at compile time. Cubicles assigned to the pool are not assigned to a family or
subfamily.
OP=RB — Remove Cubicles
OP=RB removes an assigned empty cubicle from a subfamily (PK=F), the pool
(PK=P), or the reserved area of the SM (PK=R). More than one cubicle (N = n) can be
removed at a time. SSLABEL reads the SM map and selects the first empty cubicle
assigned to the subfamily, pool, or reserved area to be removed. Specific cubicles (YI
and Zl parameters) can be removed, but they must be empty. The SM map is updated
to reflect that the cubicles are unassigned.

11 - 1 6

NOS

Version

Analysis

Handbook

Revision

SSLABEL Directives

OP=AM — Add Cartridges
OP=AM adds a cartridge to either a specific subfamily (PT=F) or the pool (PT = P).
SSLABEL selects the first empty cubicle assigned to the subfamily or pool as the new
location for the cartridge. More than one cartridge (N=n) can be added at a time or a
specific cartridge (CN=csn) from the pool can be added to a subfamily. The SM map,
7990 catalog, and cartridge label are updated to reflect the new assignment of the
cartridge. Cartridges added to a subfamily may be added to a specific group using the
GR=n parameter. If cartridges are added to the pool, the GR=n parameter is not
valid. The small and large boundaries for file size are specified by the B=n parameter
with the OP=AM option. Default is B = 600, implying that the first 600 AUs of the
cartridge are available for small files. Cartridges added to the pool are not assigned to
a family or subfamily. A customer engineer cartridge can be stored into location (0,0)
or (0,15) by using the CC = loc parameter.
OP=RM — Remove Cartridges
OP=RM either removes an empty cartridge from a subfamily (PK = F) and moves the
cartridge to the pool (PT=P) or it moves any cartridge from the pool (PK=P) and
moves it to the exit tray (PT=D). Any cartridge currently assigned to a subfamily
cannot be removed unless it is empty; that is, all AUs must be unallocated. To remove
a cartridge that is not empty, first use the OP = FC directive to free up the cartridge.

0ms

If the cartridge specified by the CN = csn parameter is lost (does not reside in its
assigned cubicle) and if the cartridge is assigned to a family, the LT parameter should
be specified. This allows the appropriate entries in the SM map and 7990 catalog to be
deleted even though the cartridge is not available to have its label updated. If LT is
not specified, an error message is issued and SSLABEL aborts. SSLABEL will not
update the SM map and 7990 catalog with the LT parameter unless the lost cartridge
flag is set in the 7990 catalog. SSLABEL will set the lost cartridge flag if SSLABEL is
run to remove a cartridge that is not present.
If the cartridge specified by the CN=csn parameter is lost and it is in the pool, then
the LT parameter should not be used. Rather, SSDEBUG must be run to remove the
SM map entry and SSLABEL must be run to reassign the cartridge to the pool.
A specified number (N = n) of cartridges may be removed from a group of a subfamily
by using the GR=n parameter.
OP=RC — Restore Lost Cartridges
OP=RC restores to its proper cubicle a cartridge that was inadvertently removed from
an SM. If restoration is successful, the lost flag in the 7990 catalog is cleared. If data
recorded on the cartridge label does not agree with the information in the 7990 catalog
and the SM map entry for the cubicle to which the cartridge is to be restored, the
cartridge label information is reported and the cartridge is put into the exit tray for
use in further processing of the cartridge.
NOTE
Not more than one lost cartridge can be restored at a time using the OP = RC
directive. Also, since customer engineer cartridges do not exist in the SM map,
OP=RC will not restore a cartridge to a customer engineer cartridge cubicle.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 1 7

SSLABEL Directives

OP=FX— Fix Cartridge Labels
y^^.

OP=FX writes a scratch label on a cartridge identified by the CN=csn parameter and
adds the cartridge to the pool. This directive is intended for use when a cartridge label
has been destroyed, but the cartridge itself is not physically damaged and can be
reused. It can also be used when a cartridge with a family label is to be assigned to a
different subfamily using the OP=AM directive, but it is not feasible to first remove
the cartridge normally using the OP=RM directive. For example, if SSLABEL is run
to add a cartridge to a subfamily, and a system failure occurs before the 7990 catalog
and SM map are updated but after the cartridge is relabeled, then the cartridge label
does not match the corresponding entries in the 7990 catalog and SM map. Hence,
OP=RM cannot be used to remove the cartridge from the subfamily, but OP=FX can
be used to rewrite the cartridge label and then OP=AM can be used to add the
cartridge to a subfamily. However, if a family label is to be overwritten, the
FM=familyname and SB = subfamily parameters must identify the family and subfamily
to which the cartridge was assigned. The SM map and 7990 catalog are updated to
reflect the new cartridge label.
OP=RM cannot be used with the LT parameter to remove pool cartridges. SSLABEL
sets the SM map error flag because no 7990 catalog entries exist for pool cartridges.
Use SSDEBUG to remove pool cartridges.
OP=IB — Control Cartridge Allocation
OP=IB sets or clears the inhibit allocation flag in the 7990 catalog entry for the
specific cartridge (CN=csn). If the flag is set (ON), SSEXEC does not allocate new
7990 files to this cartridge. If the flag is cleared (OF), allocation of files to this
cartridge is enabled.
OP=FC — Free Cartridge Files
OP=FC sets or clears the free cartridge flag in the 7990 catalog entry for the specified
cartridge (CN = csn). If the flag is set (ON), SSEXEC will inhibit further allocation.
Files can be removed by running the SSVAL utility. Refer to the free cartridge
discussion under SSVAL later in this section. If the SM map entry is missing,
SSDEBUG must be used to set the free cartridge flag. Refer to the discussion under
SSDEBUG later in this section.

^^\

11 - 1 8

NOS

Version

Analysis

Handbook

Revision

Parameters for SSLABEL Directives

Parameters for SSLABEL Directives
The descriptions of the parameters to the SSLABEL directives follow. Not all
parameters are valid with all directives, as indicated.
Pi

Description

B=n

Number of AUs on this cartridge to be used to store small files.
The remaining AUs (1931-n) are reserved for large files. The
distinction between small and large files is controlled by an
assembly parameter. B=n is valid only with OP=AM.

B omitted

Same as B=600.

CC=loc

Location into which the cartridge is to be stored.
loc

Description

A Store cartridge into location (0,0).
B Store cartridge into location (0,15).
Any value of CC other than A or B is not accepted.
CM=A-

Cartridge manufacturer code is A-, indicating IBM.

Same as CM=A-.

CM omitted

Same as CM=A-.

CN=csn

Cartridge serial number of the cartridge to be added, removed, or
repaired; not valid if PK=pkloc is specified. If CN = csn is specified,
n must be 1 if N = n is specified.

Cartridge serial number of the cartridge is not specified.

CN omitted

Same as CN.

FM=familyname Family to which SSLABEL adds or from which it removes a
cartridge or SM. With OP=FX, this parameter specifies the family
to which the cartridge was assigned.
F M S a m e a s F M = s y s t e m d e f a u l t f a m i l y.
FM omitted Same as FM = system default family.
GR=n Group to which SSLABEL adds or from which it removes a
cartridge; 1 ^ n ^ 20. With OP=AM, this parameter is ignored if
PT=P is specified. GR=n is valid only with OP=AM or OP=RM.
GR

Not

permitted.

GR omitted Default groups are chosen sequentially. SSVAL runs most efficiently
if SSLABEL chooses the default groups.

Revision M

Mass Storage Extended Subsystem (MSE) 11-19

Parameters for SSLABEL Directives

Description

SM map and 7990 catalog entries are to be updated, even though
the cartridge is lost and its label cannot be updated; valid only
with OP = RM.

LT omitted

If the cartridge is lost and OP=RM is specified, an error message
is issued and SSLABEL aborts.

N=n

Number of cartridges or cubicles to be added, removed, or repaired;
1 ^ n ^ 100; not valid if PT=R is specified. If CN = csn is
specified, n must be 1.

Same as N = l.

N omitted

Same as N = l.

The inhibit allocation flag or free cartridge flag in the 7990 catalog
is to be cleared; valid only with OP=IB or OP=FC.

The inhibit allocation flag or free cartridge flag in the 7990 catalog
is to be set; valid only with OP=IB or OP=FC.

PK=pkloc

Location from which the cartridge or cubicle is to be picked; not
valid if CN=csn is specified.
pkloc

Description

Cartridge is to be picked from the input tray. PK = D is
valid only with OP=AM, OP=RC, or OP=FX.
Cartridge or cubicle is to be picked from the specified
family (FM=familyname) and subfamily
(SB = subfamily). PK=F is valid only with OP=RM or
OP=RB.
Cartridge or cubicle is to be picked from the pool.
PK=P is valid only with OP=AM, OP=RM, or
OP=RB. PK=P is not valid if PT=P is specified.

Cubicle is to be picked from the reserved area of the
SM. PK=R is valid only with OP=RB.

Same as PK=P.

PK omitted

Same as PK=P.

'*a^\

11-20 NOS Version 2 Analysis Handbook

Revision M

Parameters for SSLABEL Directives

Description

PT=ptloc

Location into which the cartridge or cubicle is to be put.
ptloc Description
D

Cartridge is to be put into the exit tray. PT=D is valid
only with OP=RM.
Cartridge or cubicle is to be put into the specified
family (FM=familyname) and subfamily
(SB=subfamily). PT=F is valid only with OP=AM or
OP=AB.
Cartridge or cubicle is to be put into the pool. PT=P is
valid only with OP=AM, OP=RM, or OP=AB. PT=P
is not valid if PK = P is specified.

Cubicle is to be put into the reserved area of the SM.
PT=R is valid only with OP=AB.

Same as PT=P.

PT omitted

Same as PT=P.

SB = subfamily

Subfamily to which SSLABEL adds or from which it removes a
cartridge or SM; 0 ^ sub ^ 7. With OP=FX, this parameter
specifies the subfamily to which the cartridge was assigned.

Same as SB = 0.

SB omitted

Same as SB = 0.

SM=id

SM identifier of the SM to be used by SSLABEL; id is a letter
from A to H.

Same as SM=A.

SM omitted

Same as SM=A.

YI=yi

Row of the SM to be added or removed; 0 ^ yi ^ 21; valid only
with OP=AB or OP = RB.

ZI=zi

Column of the SM to be added or removed; 0 ^ zi *£ 15; valid
only with OP=AB or OP=RB.

YI=yi,ZI = zi

y and z coordinates of the cubicle to be added or removed;
0 ^ yi ^ 21, 0 ^ zi ^ 5; valid only with OP=AB or OP=RB.
The following coordinates (y,z) are reserved for customer
engineering and/or diagnostic programming purposes: (0,0), (0,6),
(0,15), (11,0), (11,1), (11,15), (15,0), (15,1), (21,6), and (21,15). The
following coordinates are reserved for system use: (0,1), (0,14),
(21,0), and (21,14).

Revision M

Mass Storage Extended Subsystem (MSE) 11-21

SSLABEL Update Sequence

Description

YI=yi,ZI = zi, Rectangle of cubicles to be added or removed; cubicles with y
YF=y2,ZF=z2 coordinates between yi and y2 and z coordinates between zi and Z2
are included; valid only with OP=AB or OP=RB. At most, 100
cubicles can be included in the rectangle. YF and ZF must both be
specified, if either is specified. YF and ZF cannot be specified
unless both YI and ZI are specified. If a reserved cubicle is
included in the rectangle, the directive will be accepted even
though the reserved cubicle cannot be added or removed. zi = 6 and
Z2 = 6 are not valid.
YI and ZI With OP=AB, the next available cubicle closest to the top (for
omitted assignment to a family) or the bottom (for assignment to the pool)
is to be selected. With OP=RB, the first empty assigned cubicle is
to be selected.
SSLABEL Update Sequence
Each directive to SSLABEL updates SM maps, 7990 catalogs, and cartridge labels,
whichever are appropriate, to reflect the changes in cartridge, cubicle, or SM
assignment. Because the 7990 catalog is a disk-resident permanent file, it will be
backed up on a dump tape whenever PFDUMP dumps the master device for its
particular subfamily. Thus, it is not necessary for the analyst to back up the 7990
catalogs immediately after an SSLABEL run. However, the backup and recovery of SM
maps do require special operational procedures, which should be performed immediately
after an SSLABEL run (refer to the definition of SM map earlier in this section).
i

When SSLABEL is run to change the assignment of a cartridge, the update sequence
consists of a series of steps to delete the old assignment information from the MSE
system files, relabel the cartridge, and add the new assignment information to the MSE
system files. If an interruption such as a system failure, SSLABEL abort, or SSEXEC
abort prevents SSLABEL from completing the update sequence, the location of the
affected cartridge and the status of the SM maps and 7990 catalogs depend on the
point of interruption, as follows:
• If the cartridge label, 7990 catalog, and SM map do not all match, then the
cartridge is put into the exit tray. The OP=RC directive cannot be used to restore
the cartridge because of the inconsistency. However, OP=FX can be used to
overwrite the cartridge label and add the cartridge to the pool, if the FM and SB
parameters specify the family and the subfamily on the cartridge label.
• If the cartridge label, 7990 catalog, and SM map do match, then the cartridge may
be returned to its original location, the new location, or the exit tray, depending on
the exact point of interruption. If the cartridge is in the input tray, OP=RC can be
used to restore the cartridge to the location indicated on the cartridge label.
Cartridge Restoration and Reuse, later in this section, describes the procedure for
restoring cartridges found in the exit tray.

y*J*S^.

11 - 2 2

NOS

Version

Analysis

Handbook

Revision

Restrictions to SSLABEL
^Px

Restrictions to SSLABEL
The following restrictions apply to the SSLABEL utility.
• SSEXEC must be running when SSLABEL is run.
• Only one copy of SSLABEL can be run at a time.
• SSLABEL, SSVAL, and SSDEBUG cannot be run at the same time.
SSLABEL Example
Figure 11-1 shows the format of an SSLABEL report. The cartridge label information
is included on the report because of a mismatch with the SM map. An error message
is issued for the first directive on the command (in this case, the only directive).

SSLABEL REPORT FILE
SSLABEL,Z./0P=RC,PK=D,SM=B.
1 OP=RC,PK=D,SM=B.
1 0P=RC,PK=D,SM=B.
CM=ACSN = 66157234
FAMILY = SYSTST
SUBFAMILY = 0
SM = B
Y = 2
Z = 6
*** ERROR 8 DIRECTIVE 1
UNEXPECTED SM, Y, Z, FAMILY OR SUBFAM.***

Figure 11-1. SSLABEL Report File

Revision M

Mass Storage Extended Subsystem (MSE) 11-23

SSMOVE

SSMOVE
SSMOVE manages disk and 7990 residence. That is, SSMOVE determines which files
should be left on disk, which files should be released from disk and moved to 7990,
and which files should be resident both on disk and on 7990.
The selection process includes algorithms that weigh certain file characteristics, as
follows:
• Files are selected for destaging to 7990 based on file length, time since the last
update, and the preferred residence specified by the user.
• Files are selected for release from disk based on time since the last access and the
backup requirement specified by the user.
SSMOVE reads the PFC entries for a particular family and calculates release and
destage values (refer to Selection Algorithms later in this section) for each file to
determine its residence. If a file has both disk and 7990 images but is to reside only
on 7990, SSMOVE releases the disk space for the file. For files that do not have a J^\
7990 image, SSMOVE creates entries on the SSMOVE/SSEXEC communication file,
MVOCOM, to identify the files to be destaged and to specify whether or not the file's
disk space is to be released upon completion of the destage. SSEXEC then processes
each destage and destage/release request on MVOCOM.
SSMOVE generates an output report that includes a list of input directives to
SSMOVE, site-defined values used in the destage/release decision-making process, files
selected for processing, and a summary of the number of files expected to reside on
each device after destage/release processing.

11 - 2 4

NOS

Version

Analysis

Handbook

Revision

SSMOVE

0am\.

The format of the SSMOVE command is:
SSMOVE,pi,p2...

• .Pn-

Description

DN=device

Device number of the only disk from which files are to be
destaged/released.

SSMOVE destages and releases files from all devices in a specified
family.

DN omitted

Same as DN.

FM=familyname

Family to be used by SSMOVE.

Same as FM = system default family.

FM omitted

Same as FM = system default family.

I=filename

File containing the directives to SSMOVE.

Same as I = INPUT.

1=0

No input directives file exists. SSMOVE uses the default
parameters.

I omitted

Same as I = INPUT.

L=filename

File on which listable output is to be written.

Same as L=OUTPUT.

L=0

No output file is to be generated.

L omitted

Same as L=OUTPUT.

LB = n

Large file boundary is used when sorting files for destaging. All
files smaller than n PRUs are small files.

Same as LB = 365.

LB omitted

Same as LB = 365.

LO = F

All files selected for staging, destaging, or releasing are to be
included in the report file.

LO = P

Only files actually processed are listed in the report file. Refer to
the PX parameter.

Individual files are not to be listed in the report file.

LO omitted

Same as LO.

Revision M

Mass Storage Extended Subsystem (MSE) 11-25

SSMOVE

Description

No wait. SSMOVE will not wait for completion of destage and
release processing by SSEXEC.

NW omitted

SSMOVE will wait for completion of destage and release processing
by SSEXEC.

PX=xxx

xxx is a character string that specifies which types of SSMOVE
processing should not be done.
xxx

Description

Exclude file archiving or releasing disk space.

Exclude creating a backup copy by destaging a file from
disk to the 7990.

Exclude direct access files.

Exclude freeing a file from the 7990 by clearing its asa
value from the file's PFC entry.

Exclude indirect access files.

Exclude staging a file from the 7990 to disk.

For example, the PX=ABFS parameter could be used to obtain a
report of the results of an SSMOVE run using a given set of
parameters without actually performing any of the selected actions.
PX

All selected SSMOVE processing is to be done.

PX omitted

Same as PX.

UI=userindex

Destage and release processing is restricted to files having user
index userindex.

All user indexes are processed.

UI = 0

All user indexes are processed.

UI omitted

All user indexes are processed.

11-26 NOS Version 2 Analysis Handbook

Revision M

SSMOVE Directives

SSMOVE Directives
The directives to SSMOVE are specified on a separate file. Each directive must be
specified on a separate line. Three types of input directives can be included in an
SSMOVE directive file. They are: comment directives, specific file directives, and value
specifier directives.
Comment directives have an asterisk (*) in the first column followed by any message
or comment the user wishes to enter.
The specific file and value specifier directives are described in the following
paragraphs:
Specific File (SF) Directives
SSMOVE uses SF directives to select a given file or set of files on which to perform
the specified processing action. The format of the SF directive is:
SF,FN=filename,UI=userindex,PO=process.

Parameter Description
FN=filename The 1 to 7 characters that specify a permanent file or set of
permanent files. Asterisks in the file name are wild card
characters.
UI=userindex User index of the file specified by the FN=filename parameter.
PO=process Processing action to be performed on the file specified by the
FN=filename parameter.
process Description
A A r c h i v e t h e s p e c i fi e d fi l e .
B . Create a backup copy by destaging the specified file
from disk to the 7990.
F Free the specified file from the 7990 by clearing its asa
value in the file's PFC entry.
S Stage the specified file from the 7990 to disk.
For example, the following SF directive selects all permanent files with a maximum of
two characters in the file name beginning with Z from user index 002622s to be staged
to disk.
SF,FN=Z*,UI=2622,PO=S.

The SF directive can be used without specifying the FN parameter to establish default
values for the UI and/or PO parameters. These default values will be used for
subsequent SF, FN=filename directives that are missing UI and/or PO parameters.
Default values for UI and/or PO parameters can be redefined by using another SF
directive without specifying the FN parameter.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 2 7

SSMOVE Directives

Value Specifier Directives
SSMOVE uses the value specifier directives to redefine the values of the weight factors
or thresholds (installation parameters) used in the algorithms that select files to be
destaged or released. The site analyst uses these value specifiers to increase or
decrease the importance of certain file characteristics used to determine which files are
to be destaged and/or released. For example, specifying a large MN parameter prohibits
SSMOVE from selecting small files for destage/release processing.
The general format of a value specifier directive statement is:
directive,qualifier(s).parameter(s).

Variable

Description

directive

2-character value specifier directive keyword.
directive

qualifier(s)

Description

Keyword for backup requirement directive.

Keyword for file requirement directive.

Keyword for preferred residence directive.

Keyword for site management directive.

Keyword for weight adder directive.

Keyword for weight multiplier directive.

One or more qualifier keywords that specify the file type
(direct/indirect access) and decision type (destage/release) to be
used in the selection process. If all qualifier keywords are
omitted, all four combinations of file types and decision types
are used in the selection process.
qualifier(s)

Description

Keyword for indirect access files.

Keyword for direct access files.

Keyword for destage decisions.

Keyword for release decisions.

11-28 NOS Version 2 Analysis Handbook

Revision M

SSMOVE Directives

Variable

Description

parameter(s)

Parameter keyword and a value (positive integer) for the
specified directive keyword. Multiple parameter=value
combinations can be entered in the same value specifier
directive statement.
parameter(s)

Description

With BR
Directive:
N=wf

Weight factor to be used as the backup
requirement value for decisions involving
files with a BR=N attribute (no backup).2

Y=wf

Weight factor to be used as the backup
requirement value for decisions involving
files with a BR=Y attribute (tape backup).

MD = wf

Weight factor to be used as the backup
requirement value for decisions involving
files with a BR=MD attribute (media
dependent, tape, or 7990 backup).

With FR
Directive:

/ffllSP*^

/f!$"X

MN = min

Minimum file size in PRUs.

MX=max

Maximum file size in PRUs.

DD=dd

Number of days since the file was last
accessed or updated.

TH = th

Destage or release threshold. If a file's
calculated value is less than the specified
threshold, the file is not a candidate for
destage or release processing. TH = 0 allows
all files to be candidates for destage and
release processing unless they are excluded
by FR directive parameters or by other
run-time parameter values.

2. The file owner specifies the backup requirement attribute using the BR parameter on the DEFINE or
CHANGE command (refer to the NOS Version 2 Reference Set, Volume 3).

Revision M

Mass Storage Extended Subsystem (MSE) 11-29

SSMOVE Directives

Variable

Description

parameter(s)

(Continued)
parameter(s)

^S^X

Description

With PR
Directive:
L = wf

Weight factor to be used as the preferred
residence value for decisions involving files
with a PR=L attribute (locked to disk
preference).

D = wf

Weight factor to be used as the preferred
residence value for decisions involving files
with a PR=D attribute (disk preference).3

M=wf

Weight factor to be used as the preferred
residence value for decisions involving files
with a PR=M attribute (7990 preference).3

N=wf

Weight factor to be used as the preferred
residence value for decisions involving files
with a PR=N attribute (no preference).3

With SM
Directive:
MG=mg

Master goal specifying the percent of master
device disk space not to be exceeded.

SG=sg

Secondary goal specifying the percent of
secondary device disk space not to be
exceeded.

Available for site use.

3. The file owner specifies the preferred residence attribute using the PR parameter on the DEFINE or
CHANGE command (refer to the NOS Version 2 Reference Set, Volume 3).

11-30 NOS Version 2 Analysis Handbook

Revision M

SSMOVE Directives

Variable

Description

parameter(s)

(Continued)
parameter(s)

Description

With WA
Directive:
AG=wa

Weight adder to be added to the weighted
file age.

LN = wa

Weight adder to be added to the weighted
file length.

AC = wa

Weight adder to be added to the weighted
file access count.

DV=sf

Scaling factor given to the divisor when
calculating destage and release values.

With WM
Directive:

/i^\

AG=wf

Weight factor given to the file age (days
since the file was last accessed or updated).

LN = wf

Weight factor given to the file length.

AC = wf

Weight factor given to the file access count.

For example, the following value specifier directive specifies that the minimum size for
an indirect access file to be destaged is three disk PRUs.
FR,IA,DS,MN=3.

The following value specifier directive requires that all files to be destaged or released
must be less than 98765 PRUs long.
FR,MX=98765.

If a directive error is detected on the directive input file, SSMOVE ignores the
incorrect directive and continues to run in report mode. A message is issued to the job
dayfile and no processing is done.

Revision M

Mass Storage Extended Subsystem (MSE) 11-31

Excluding Destage/Release Processing

Excluding Destage/Release Processing
SSMOVE uses FR directives to select candidates for destage and release processing.
After selecting the candidates and making the final processing decisions, SSMOVE
checks the PX parameter to determine if any processing should be excluded.
If FR,RL,MN=9999999 is specified, all files less than 9999999 PRUs will be given a
negative release value. Any file less than 9999999 PRUs will not be released unless
the file has been specifically selected for releasing with an SF directive.
IF PX=A is specified, SSMOVE selects files for processing without considering that
release processing is prohibited. When the final processing decisions have been made,
any files selected for releasing will not be processed. That is, files selected for
releasing only will not be processed; and files selected for both destaging and releasing
will not be processed.
If PX=B is specified, destage processing is excluded just as release processing was in
the previous description.
Destaging cannot be excluded with an FR,DS,MN = 9999999 directive as releasing can.
Even though all files less than 9999999 PRUs will be given a negative destage value
and not selected for destaging, they will be made candidates for destaging in case any
of them are selected for releasing. When the final processing decisions are made, any
file that is a candidate for destaging and has been selected for releasing will be
destaged and released. However, any destaging candidate not selected for releasing will
not be destaged.
Selection Algorithms
SSMOVE determines which files to destage and/or release according to the following
algorithms. Files that reside only on 7990 are not considered because they have been
destaged and released previously. For all other files, SSMOVE checks the file length
and excludes from further consideration any file whose length in PRUs is less than the
minimum length threshold (refer back to the MN parameter) or greater than the
maximum length threshold (refer back to the MX parameter).
If the current image of the file resides on both disk and 7990, SSMOVE uses the
release algorithm to determine whether or not to release disk space; the destage
algorithm is not used. If the current file resides on disk only, SSMOVE uses the
destage algorithm to determine whether or not to destage the file. If the file is to be
destaged to 7990, SSMOVE also determines via the release algorithm whether or not to
release the file's disk space.

>^^v

11 - 3 2

NOS

Version

Analysis

Handbook

Revision

Selection Algorithms

Destage and Release Algorithms
An analyst uses the FR directive to establish file requirements on files that are to be
eligible for destage and/or release processing. These requirements include file length
(minimum and maximum) and file age. A file's age is the number of days since the file
was last updated (for destaging) or accessed (for releasing). Separate requirements can
be established for the various combinations of file types (direct/indirect) and decision
types (destage/release).
Files that meet the eligibility requirements are assigned separate destage and release
values. SSMOVE calculates these values for each eligible file according to the following
equation, which considers various file attributes from the file's PFC entry (length, age,
access count, preferred residence, and backup requirements). These file attributes are
weighted according to site-defined values (refer to Value Specifier Directives earlier in
this section).
(ai+a2* length) •(b1+b2*age)*(res)*(bkup)

value =
(ci+C2*access)»sf

Variable

Description

Site-defined length weight adder specified by the WA directive LN
parameter.

Site-defined length weight factor specified by the WM directive LN
parameter.

length

Length of the file in PRUs.

Site-defined age weight adder specified by the WA directive AG
parameter.

Site-defined age weight factor specified by the WM directive AG
parameter.

age

Number of days since the file was last updated (for destage) or
accessed (for release).

res

Site-defined preferred residence weight factor specified by the PR
directive. The PR directive parameter depends on which preferred
residence attribute the file owner specified.

bkup

Site-defined backup requirement weight factor specified by the BR
directive. The BR directive parameter depends on which backup
requirement attribute the file owner specified.

Site-defined access count weight adder specified by the WA directive
AC parameter.

Site-defined access count weight factor specified by the WM
directive AC parameter.

access

Number of times the file was accessed.

Site-defined scaling factor specified by the WA directive DV
parameter.

Revision M

Mass Storage Extended Subsystem (MSE) 11-33

Selection Algorithms

If a file's destage/release value exceeds a site-defined threshold (FR directive TH
parameter), the file is selected for destage/release processing. Conversely, if the file's s^s
destage/release value does not exceed the threshold, the file is not considered for )
destage/release processing.
Files eligible for releasing are sorted according to their release values. The files on
each disk with the greatest release values are selected to be released. When enough
files have been selected and released, the site-defined disk space availability goals will
be achieved.
Decision Algorithm Hierarchy
Several different functions of SSMOVE can lead to apparent contradictory processing
decisions. The decisions are made using the following rules, which are listed in order
of precedence.
1. SSMOVE does not consider any files for processing if they are excluded by the
PX=I, PX = D, or UI parameters to SSMOVE or if the file has a PR=L attribute.
2. Files identified for specific processing using the SF directive are selected for the
specified processing regardless of the file requirements controlled by the FR
directive.
3. If DN = 0, all files that meet the destage requirements are selected to be destaged.
Otherwise, only files on the specified device are destaged.
4. No file with a BR=Y attribute will be selected to be released (including files
specified for processing with an SF directive) if the file data has not been included
in a full or incremental dump using PFDUMP.
5. If DN = 0, all files that meet the release requirements are selected to be released, if
needed, to meet the disk space availability goals. Otherwise, only files on the
specified device are released.
6. If a file is selected for a specific processing action (such as destage) and the
corresponding action is precluded by a PX parameter (in this case, PX=B), then the
selected action is not performed. In all cases, however, the SSMOVE device status
report is based on which files were selected for processing rather than whether the
PX parameter actually allowed the selected processing to occur.

0^^\

11 - 3 4

NOS

Version

Analysis

Handbook

Revision

Disk Space/Dump Tape Management

Disk Space/Dump Tape Management
As more disk-resident files are created and more 7990-resident files are staged to disk,
it will be necessary to monitor the availability of disk space. It is recommended that
SSMOVE be used as a periodic disk space management procedure to avoid frequent
disk-full conditions (refer to Disk Space Management later in this section). SSMOVE
can also be used to reduce the amount of data written on dump tapes and thereby
avoid mamtaining large numbers of dump tapes. This is accomplished by destaging to
7990 and/or releasing disk space of files that need not be on the dump tape (refer to
Dump Tape Management later in this section).
An analyst can specify what percent of disk space is to contain indirect access files
and what percent is to contain direct access files. For direct access files, the analyst
can further specify the percent of master device and/or secondary device disk space.
These percent values are applied to all devices in the family on which SSMOVE is
run or a specific device can be managed by using the DN parameter to SSMOVE.
The specified percentages of disk space are considered to be goals in that other
site-defined constraints and file-busy conditions may make it impossible to achieve
these goals.
Restrictions to SSMOVE
The following restrictions apply to the SSMOVE utility.
• Only one copy of SSMOVE can be run at a time when it is in the process of
destaging files. A second SSMOVE aborts if the first one has not completed.
• SSMOVE and PFDUMP should not be run at the same time.
• SSMOVE cannot be run when SSVAL is running.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 3 5

Output Example

Output Example
The SSMOVE report consists of the following five sections:
1. A list of directives (figure 11-2) from the input directive file plus any diagnostic
messages.
2. A list of run-time parameter values (figure 11-3) used in the release and destage
decision-making process. These values consist of the site-defined, assembly-time
values as modified by the value specifier directives.
3. An optional list of the files (figure 11-4) selected for processing. This list shows the
file name, file type, user index, length, date, access count, processing action, and
destage and release values.
4. A device status report (figure 11-5) that includes a summary of the number of files
and total file length expected to reside on each device as a result of release
processing. Also, a subfamily report that includes a summary (for each subfamily) of
the number of files and file length for files to be destaged, files that reside only on
7990, and files that reside on 7990 and disk.

,^*fe\

5. A destage abandonment report (figure 11-6) that is not produced if the NW
parameter is specified. This report provides a list of the number of files not
destaged and an optional list of the abandoned files. It also provides an updated
device status report reflecting only the files that were destaged.

A ^ S

11-36 NOS Version 2 Analysis Handbook

Revision M

Output Example

/ffty

yy/mm/dd. hh.mm.ss. PAGE
SSMOVE REPORT.
SSMOVE,I=B1GO.LO* F.FM=MTST.
1 FR,MN=0,DD=0.
2 SM,MG=0.SG=0.

Figure 11-2. SSMOVE Report: List of Directives
yy/mm/dd . hh.mm.ss. PAGE
SSMOVE REPORT.
RUN-TIME PARAMETER VALUES
« O E S T A G E «
DIRECT
INDIRECT

• R E L E A S E *
INDIRECT
DIRECT

FILE REQUIREMENTS
FR

MN
0
MX 9999999
DD
0
TH
1

9999999
0
1

100
1
1

1000
1
1000

100
10

WEIGHT MULTIPLIER
WM AG
LN
AC

WEIGHT ADDER
WA AG
LN
AC
DV

PREFERRED RESIDENCE
PR L
D
M
N

BACKUP REQUIREMENT
BR N
Y
MD

SITE MANAGEMENT
SM MG
SG
PI
P2

Figure 11-3. SSMOVE Report: Run-time Parameter Values

yms

Revision M

Mass Storage Extended Subsystem (MSE) 11-37

Output Example

yy/mm/dd. hri . m m . s s . PA G E 4
SSMOVE REPORT.
NAME
DIR301
DIR305
DIR302
DIR303
DIR304
IND3020
IND3019
IND3018
IND3017
IND3016
IND3015
1ND3014
IND3013
IND3012
IND3011
IND3010
IND309
IND308
IND307
IND306
IND305
IND304
1^303
IND302
IND301
DIR313
DIR314
DIR312
DIR315
DIR311
IND3120
1ND3119
IND3118
IND3117
IND3116
IND3115
IND3114
IND3113
IND3112
IND3111

TYPE
DIR.
DIR.
DIR.
DIR.
DIR.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
DIR.
DIR.
DIR.
DIR.
DIR.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.
IND.

LENGTH

30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
30
31
31
31
31
31
31
31
31
31
31
31
31
31
31
31

1200
1200
1200
1200
1200

619
618
617
616
615
614
613
612
611
610
609
608
607
606
605
604
603
602
601
600
1200
1200
1200
1200
1200

619
618
617
616
615
614
613
612
611
610

DATE

ACC-CT ACTION{« = NOT DONE PER »PX* OPTION)

84.09.1 1
84.09.1 1
84.09.1 1 .
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09,1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1
84.09.1 1

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.
DESTAGE AND RELEASE.

DES-VAL
6005
6005
6005
6005
6005
3100
3095
3090
3085
3080
3075
3070
3065
3060
3055
3050
3045
3040
3035
3030
3025
3020
3015
3010
3005
6005
6005
6005
6005
6005
3100
3095
3090
3085
3080
3075
3070
3065
3060
3055

REL-VAL
• 22000
22000
22000
22000
22000
16190
16180
16170
16160
16150
16140
16130
16120
16110
16100
16090
16080
16070
16060
16050
16040
16030
16020
16010
16000
22000
22000
22000
22000
22000
16190
16180
16170
16160
16150
16140
16130
16120
16110
16100

Figure 11-4. SSMOVE Report: Optional list of Files

11-38 NOS Version 2 Analysis Handbook

Revision M

Output Example

y y / m / d d . h h . u a . s s . PA G E 6
SSKOVE REPORT.
(BEFORE) DEVICE STATUS (AFTER) MR CENTS
E O B l l D T - N T Y P E F I L E S / P R U F I L E S / P R U E X P. G O A L F L A 6 .
2

DK-1

IKS.

MC-1

DIR.

36952
2542*

0
y

1008

0
0

••

•* - DEVICE SPACE GOAL NOT KET

SU8FANILT REPORT
SUB
FA M I LY

FILES
DIRECT
MKSER
PSU

TO
D E S TA G E
FILES
O N LY
ON
7990
INDIRECT
DIRECT
INDIRECT
NWBER
PRU
NUMBER
PRU
NWtBER
PRU

o
t

6000
MOO
0

2
0
0
0
1
0

12190
12190
1201

0
0
0

3050

20
20

6363
6352
10357
12362
6357
6357
27915

69
0

FILES
ON
DIRECT
NUMBER
PRU

12190
12190
1201
3010
3010
3010
56298

I(8
3
]
I
:
2

7990
INDIRECT
NUN9ER
PRU

20
20

6363
6352
10S57
12362
6357
6357
27919

12190
12190
1201
3010
3010
3010
56298

69
0

Figure 11-5. SSMOVE Report: Device Status Report
y y / a a / d d . h h . c a . s s . PA G E
SSKOVE REPORT.
DESTAGE ABANDONMENT REPORT
FILENAME

1
2
3

0
0
0
0
0
0
0
0
0

*
5
«

yRrS

7
8
9
10
11

NO SPACE
NO STORAGE NODULE AVAILABLE
KO CARTRIDGE OR GROUP AVAILABLE
FILE ALREADY DESTAGED
FILE BUST / PFN PROBLEM
CATALOG ACCESS ERROR
OVERFLOW NOT LEGAL
GROUP FULL
01SK READ ERROR
CARTRIDGE LOST
CLOSED DESTAGE

(BEFORE) DEVICE STATUS (AFTER) PERCENTS
E O D N D T - N T Y P E F I L E S / P R U F I L E S I P R U E X P. G O A L F L A G .
2

DK-1

IND.

7 DK-1 DIR.

62
2542*

36952

1008

** - DEVICE SPACE GOAL NOT NET
SUBFAMILY REPORT
SUB
FA M I LY

FILES
DIRECT
NUMBER
PRU

NOT
D E S TA G E D
FILES
O N LY
ON
7990
INDIRECT
DIRECT
INDIRECT
NUMBER
PRU
NUMBER
PRU
NUMBER
PRU

38
37
37
42
37
37
19
0

6363
6352
10357
12362
6357
6357
27915

20
20
2
5
5
5
69
0

12190
12190
1201
3010
3010
3010
56298

FILES
ON
DIRECT
NUMBER
PRU

38
37
37
42
37
37
19
0

7990
INDIRECT
NUMBER
PRU

6363
6352
10357
12362
6357
6357
27919

20
20
2
5
5
5
69
0

-12190
12190
1201
3010
3010
3010
56298

Figure 11-6. SSMOVE Report: Destage Abandonment

Revision M

Mass Storage Extended Subsystem (MSE) 11-39

SSVAL

SSVAL
SSVAL either performs release processing or reports on problems with the current MSE
system files. When release processing, SSVAL makes 7990 space available that is
presently allocated to files that are no longer needed, or flags files to be staged to disk
in order to free up cartridges. When problem reporting, SSVAL reports on irregularities
or discrepancies found in the current 7990 catalogs and PFC entries for the specified
family and, optionally, in certain SM maps. The function to be performed is determined
by whether or not the RF parameter is specified, as described next.
NOTE
SSVAL updates the SM map for the specified SM. (Refer to the definition of SM map
earlier in this section.) It is recommended that the SM map be copied on tape or on
another device or family immediately after every update of the SM map.
The format of the SSVAL command is:
SSVAL,pi,P2,...
Pi

Description

The SM map for the SM specified by the SM = id parameter is to
be analyzed in addition to the 7990 catalogs; not valid if
RF=filename or RF is specified.

AM omitted

SM maps are not to be analyzed.

FM=familyname

Family to be analyzed; not valid if the RF parameter is specified.

Same as FM = system default family; not valid if the RF
parameter is specified.

FM omitted

Same as FM = system default family if the RF parameter is not
specified. The family on the release data file is used if the RF
parameter is specified.

FX=n

Error threshold. If the total error count is greater than n, neither
release processing nor problem fixing is performed.

Same as FX=0.

FX omitted

Same as FX=0.

L=filename

File on which listable output is to be written.

Same as L= OUTPUT.

L=0

No output file is to be generated.

L omitted

Same as L=OUTPUT.

'*=%.

11-40 NOS Version 2 Analysis Handbook

Revision M

SSVAL

Description

RF=filename

File that contains the release data file.

Same as RF=ZZZZRDF.

RF omitted

Current versions of the 7990 catalogs are to be analyzed.

Release processing is to be performed; valid only if the RF
parameter is specified.

RL omitted

No release processing is to be performed.

SB = subfamily

Subfamily to be processed. Up to eight subfamilies can be selected
by the numbers 0 through 7. For example, SB = 723 selects
subfamilies 2, 3, and 7.

Same as SB=01234567.

SB omitted

Same as SB = 01234567.

SM = id

SM identifier of the SM to be used. Up to 8 SMs can be selected
by the letters A through H. For example, SM = ACG selects SM A,
C, and G.

Same as SM=ABCDEFGH.

SM omitted

Same as SM=ABCDEFGH.

ST=n

Scattered file criterion. Files are indicated as scattered if they are
contained on at least n more cartridges than the minimum number
needed to contain them.

Same as ST=1. That is, files are scattered if they are contained on
more than the minimum number of cartridges needed to contain
them.

ST omitted

Same as ST=1.

Revision M

Mass Storage Extended Subsystem (MSE) 11-41

Release Processing

Release Processing
If RF=filename or RF is specified, SSVAL determines which 7990 files are no longer /
needed and issues a request to SSEXEC to purge these files so their 7990 space can be
reused. The procedure is for SSVAL to analyze copies of the 7990 catalogs and PFC
entries for the specified family that are contained on the release data file (RDF)
specified by the RF parameter. Those 7990 files described in a 7990 catalog but not
having a PFC entry (that is, orphans) can be purged. During the analysis (refer to
both 7990 Catalog Analysis and PFC Analysis later in this section), SSVAL keeps track
of the error conditions it discovers, and if the error count is less than or equal to the
threshold specified by the FX parameter, release processing is performed if RL is
specified. That is, trouble-free orphans are purged and their 7990 space is made
available for reuse. The current 7990 catalog is updated to reflect that these files no
longer exist. A validation report is issued that lists the errors encountered, the number
of trouble-free orphans, and the amount of released 7990 space. If RL is not specified,
no release processing is performed but the validation report is issued, which lists the
errors encountered, the number of trouble-free orphans, and the amount of releasable
7990

space.

xs?v

The RDF used for this analysis is a file produced during a previous PFDUMP run
and it contains versions of the 7990 catalogs and PFC entries that were current at
the time of the dump. The site analyst chooses which RDF to use depending on how
long after a file was purged he/she wants to wait before releasing 7990 space. For
example, the site analyst might run SSVAL every week for release processing
purposes and use the RDF from the previous week's full dump. There are some
restrictions as to which RDFs can be used (refer to 7990 Space Management later in
this section).
Unlike the purging of disk-only files, where the file space on disk is immediately 1
made available for reassignment, the MSE software will not immediately free up a
permanent file's 7990 space following a purge of the associated disk copy of the
permanent file (assuming both a 7990 and a disk permanent file image). The reason
for not freeing up the subject 7990 space is that a subsequent PFLOAD, following a
disk failure, could reload the PFC entry for the associated permanent file. Therefore,
7990 space for purged permanent files that were resident on the 7990 must not be
made available for reuse until the possibility of such a recovery action cannot occur.
The site analyst determines which dump tapes can and cannot be used for reloading /*^
files and PFC entries following a disk failure. When a PFDUMP is taken, two files
are normally produced: the actual dump file used with PFLOAD to perform a
recovery, and the RDF file to be used with SSVAL to make 7990 space available after
purging files.
Using an RDF file allows the corresponding dump tape to be used (later dump tapes
are also allowable), but earlier dump tapes are not allowed. Because the MSE
software cannot control which dump tapes actually are used in reloading, it is the
site analyst's responsibility to observe the above restriction.
The concurrent execution of PFDUMP with OP=S not specified and SSVAL with RL
specified causes SSVAL to run very slowly. PFDUMP acquires and keeps the PF
utility interlock for its duration, and this gives the appearance that SSVAL is hung,
when it is actually just waiting. Therefore, operations personnel should not attempt to
run both of these utilities with the above options at the same time.
If the RF parameter is not specified, SSVAL will set the free file flag for all files }
that totally or partially reside on all cartridges on which the free cartridge flag is
set.

11 - 4 2

-sbv

NOS

Version

Analysis

Handbook

Revision

Problem Reporting

Problem Reporting
If RF=filename or RF is not specified, SSVAL reports on problems with the current
7990 catalogs and PFC entries for the specified family. If AM is specified, problems
with SM maps are also included in the report. SSVAL examines the MSE system files
and PFC entries and searches for problem chains and fragments, problem asa values,
and SM map/7990 catalog mismatches. The procedures SSVAL uses to detect and
classify inconsistencies and discrepancies are described next, under Error Detection and
Classification. SSVAL keeps track of the error conditions, if any, and if the error count
is less than or equal to the threshold specified by the FX parameter, problem fixing is
performed. That is, SSVAL sets flags in the appropriate entries of the SM map, 7990
catalog, and/or PFC entries to prevent propagation of errors due to the inconsistencies
or discrepancies found and to permit error recovery by the SSDEBUG utility. A count
of the errors is recorded in the job dayfile. A validation report is issued, which lists
the errors encountered, the number of trouble-free orphans, and the amount of
releasable 7990 space.
NOTE
For release processing or problem fixing, SSVAL predicts what it expects to happen
(if no problems occur) prior to doing the releasing or fixing. If SSVAL encounters
problems, the reports may not reflect the actual status of the cartridges. In this case,
run SSVAL in report mode following the release processing or problem fixing to
verify the actual status of the 7990 catalogs and cartridges.
Error Detection and Classification
SSVAL detects and classifies errors according to the following procedures. During the
SM map analysis, SSVAL detects and classifies errors in the SM map. During the 7990
catalog analysis, SSVAL detects errors with chains of AUs; during the PFC analysis,
SSVAL classifies these errors. Whenever an error is encountered, the total error count
is increased by 1. The action taken for each type of error is discussed under Release
Processing and Problem Fixing later in this section.
SM Map Analysis
If the AM option is specified, SSVAL attempts to locate problems with SM map entries
by comparing the 7990 catalogs and the SM map. For each coordinate pair (y,z) in a
7990 catalog entry, SSVAL locates the corresponding SM map entry. A type 1 error
exists if the code field in the SM map entry is not 5 (assigned to a subfamily), or if
the family, subfamily, or csn fields in the SM map entry do not match those in the
corresponding 7990 catalog entry. SSVAL also scans the SM map for all other entries
assigned to the subfamily and reports as a type 2 error any of these entries that does
not have a corresponding 7990 catalog entry.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 4 3

Error Detection and Classification

7990 Catalog Analysis
The 7990 catalog analysis locates problems with chains of AUs (refer to the definition
of cartridge earlier in this section) and identifies on each HOC whether any of the
following problems exist or whether any part of the 7990 files resides on a cartridge
that is lost or has excessive write parity errors.
SSVAL scans the 7990 catalog for HOC entries that are allocated and follows each
chain until it terminates. Normal termination occurs with an EOC entry. Abnormal
termination occurs when no EOC is found, an AU links to an unallocated AU, or an
AU links to an AU previously found in the chain being followed (looping chain).
During the chain scans, the following types of chains can be encountered; they are
linkage problems that are identified on the HOC entry.
Chain

Description

Intersecting More than one chain links to the same AU.
Scattered file The number of cartridges used for the file exceeds the value
specified by the ST parameter.
SSVAL also locates any AUs that are allocated but were not on any chain being
followed. Such AUs are linked together to form partial chains without an HOC. These
partial chains are called fragments and the first AU in a fragment is designated as the
start of fragment. Each fragment chain is followed until it terminates. The abnormal
termination conditions previously listed can also occur with fragments. Intersections can
occur, but a fragment chain that intersects the start of another fragment chain is not
an intersection; rather, one is the tail end of the other.

•*^^\

>^*S\

11-44 NOS Version 2 Analysis Handbook

Revision M

Error Detection and Classification

PFC Analysis
ymm*\

The PFC analysis is performed to classify the errors encountered on chains during the
7990 catalog analysis. For each PFC entry with asa=£0 (the file has a 7990 image and
the asa value identifies the first AU in the chain containing the file), SSVAL classifies
the following errors. Error type 3 exists if the asa value is invalid. Error type 4 exists
for any of the following reasons:
• The AU specified by the asa value is not allocated or is not an HOC entry.
• The chain does not terminate normally.
• The chain intersects with another chain or fragment.
• More than one PFC entry points to the chain.
• The chain includes a cartridge for which the lost or excessive parity error flag is
set.
SSVAL also classifies the following error conditions:
• Error type 5 exists if an orphan chain terminates abnormally or intersects with
other chains or fragments. Trouble-free orphans (chains without a PFC entry
pointing to them and without linkage problems) are not classified as errors.
• Error type 6 exists if an orphan is a fragment.
• Error type 7 exists if a chain or fragment points to an unallocated AU.
SSVAL generates informational report messages if either of the following conditions is
true.
• The system error flag is set in the PFC.
• The read error flag is set in the PFC.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 4 5

Release Processing and Problem Fixing

Release Processing and Problem Fixing
If the total error count calculated during the analyses described previously exceeds the
value specified by the FX parameter, then neither release processing nor action to flag
or fix the detected error conditions is performed. The validation report, however, is
produced. Otherwise, action taken depends on the parameter specified and the type of
errors found, as follows.
If SSVAL was run for release processing purposes (RF=filename or RF specified),
SSVAL issues a request to SSEXEC to release trouble-free orphans if RL was
specified. If RL was not specified, no release processing is performed. If SSVAL was
run for problem reporting purposes (RF omitted and FX=n, where n is greater than
the number of validation errors), the following action is taken.
• For error type 1, the linkage error flag is set in the 7990 catalog entry.
• For error type 2, the linkage error flag is set in the SM map entry.
• For error type 3, there are three alternatives:
- If the file also has a disk image, the asa field in the PFC entry is cleared.
Thus, the good disk image will not be released and the file is accessible even
if the 7990 image cannot be retrieved.
- If the file does not have a disk image, no action is taken.
- However, if the disk image can be reloaded from tape, it is recommended that
the file be reloaded using PFLOAD with OP=Z so that the asa field will be
cleared.
• For error type 4, the action taken is both that taken for error type 3 and that
taken for error type 5, 6, or 7.
• For error type 5, 6, or 7, the frozen flag is set in the 7990 catalog entry for the
initial AU on the problem chain or fragment. This enables the problem
chain/fragment/AU to be made available to the SSDEBUG utility, but prevents
these AUs from being overwritten until then. Thus, the SSDEBUG utility can be
used to inspect or save data from the corresponding AUs or cartridges. If the AUs
are not allocated, the inhibit flag is also set in the 7990 catalog for that cartridge
so that no new files will overwrite any data that might be on the cartridge.

11 - 4 6

NOS

Version

Analysis

Handbook

Revision

Validation Report
jf^v

Validation Report
The validation report consists of a report heading and a series of report groups for
each subfamily and SM being reported on. The heading identifies the subfamily, the
SM, whether or not there are any problems, and the last purge date and time for the
SM (the last time orphans on this SM were released). There is one report group for
each error detected, and the actual information recorded in a report group depends on
the type of error, as described next. Each report group, however, contains the following
items:
• Error type (a number from 1 to 7).
• Identification (refer to the particular error type, described next).
• Chain information (7990 catalog ordinal, AU number, A or U designation for
allocated or unallocated, H or E designation for HOC or EOC).
• Error description.
0ims

After the last report group, the validation report lists the number of trouble-free
orphans, the amount of released or releasable 7990 space, the total number of errors
detected, and whether or not the MSE system files were updated.
Error Types 1 and 2
Error types 1 and 2 identify mismatches between the SM map and the 7990 catalog. In
the validation report, the identification field lists the 7990 catalog ordinal, the y and z
coordinates, and the csn of the cartridge in error. The chain field is blank because
problem chains are not identified as either error type 1 or 2. The analyst should run
the SSUSE utility to produce a detailed report of the appropriate SM map and 7990
catalog entries to determine the exact problem.
Error Types 3 and 4
Error types 3 and 4 identify problem chains and problem asa values. In the validation
report, the identification field lists the permanent file name and user index of the
affected file; the dump control date and time (from the PFC entry for the file) to
identify the backup file, if any; and the letter N (no) or Y (yes) to indicate whether or
not the file has a disk image. The chain field lists the 7990 catalog ordinal and volume
number for all AUs in the affected chain. An A or U indicates whether each AU is
allocated or unallocated, and an H or E identifies the HOC or EOC. An error
description is printed for each error detected; one chain can have several errors.
Error Types 5, 6, and 7
Error types 5, 6, and 7 identify problem orphans, fragments, and problem unallocated
AUs. In the validation report, the information reported is the same as for error types 3
and 4, except for the identification field. Instead of the permanent file identification,
the word ORPHAN (error type 5), FRAGMENT (error type 6), or UNALLOCATED
(error type 7) is printed. Error type 7 is an unallocated AU that is pointed to by a
chain or fragment. Each such AU is also reported with the chain for the corresponding
orphan or fragment.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 4 7

Validation Report

Intersections
Intersections occur when more than one chain links to the same AU; they are classified
as either error type 4 or 5. Thus, they are reported as explained previously.
Intersections are also reported in a separate entry consisting of a heading and
additional information identifying the 7990 catalog ordinals and AU numbers of the
intersecting chains. Therefore, when intersections are reported, there are two entries
for the affected subfamily and SM: one lists only the intersections and the other lists
all the errors encountered.
Validation Report Example
Figure 11-7 shows the format of a validation report. SSVAL was run for problem
reporting purposes (RF not specified), and no errors were detected.
SSVAL - VALIDATION REPORT

SSVAL - VER •.*

FAMILY = MTST

SSVAL,FM=MTST,SB =0,SM=A.

L
RF
A
M
S
M
FM
FX
RL
SB
ST

= OUTPUT
= 0
= 0
= A
= MTST •
= 0
= 0
= 0
= 0

SUBFAMILY =0 SM = A

— GOOD ~

RELEASABLE 7990 FILES

RELEASABLE 7990 AUS

^S^S

LPDT - * * * * * * * * * * * * * * * *

= 800

TOTAL VALIDATION ERRORS
CATALOGS NOT MODIFIED
••REPORT COMPLETE**

Figure 11-7. SSVAL Validation Report

11-48 NOS Version 2 Analysis Handbook

Revision M

Typical SSVAL Runs

Typical SSVAL Runs
As described previously, SSVAL is run either to make 7990 space available for reuse or
to report on problems with the current MSE system files and/or PFC entries. The
following examples show typical SSVAL runs that may be used periodically for these
purposes.
Example 1:
The following SSVAL command causes 7990 space to be made available for reuse.
SSVAL,RF=DUMP1,RL.

DUMP1 is the release data file produced by a previous PFDUMP run from which
SSVAL can identify all the 7990 files that were orphans at the time of the dump. If no
error conditions are detected in the 7990 catalog and PFC entries contained on file
DUMP1 (FX=0 by default), the orphans are purged and the 7990 space assigned to
them is released. The last purge date and time field in the subcatalog (in the 7990
catalog) for each SM for each subfamily is updated to the time of the SSVAL run if
any file from that SM is purged. This is to ensure that a subsequent SSVAL run does
not release the same space a second time, as the 7990 space may be reallocated to a
new file.
If errors were detected, they are listed on the validation report and release processing
is not performed. This is indicated by the CATALOGS NOT MODIFIED message at
the end of the validation report. The analyst can rerun SSVAL with the following
command to ensure that release processing is performed (n is the number of errors
detected during the previous SSVAL run).
SSVAL,RF=DUMP1,RL,FX=n.

After this SSVAL run has completed, an analysis of the current version of the SM
map, 7990 catalog, and PFC entries should be made to determine whether or not the
errors detected in the first SSVAL run exist in the current MSE system files and PFC
entries. This is accomplished using the command:
SSVAL,FM=fam i1yname.AM.

familyname is that on the release data file, DUMP1.
Example 2:
Upon completion of any device reload that includes recovery of a 7990 catalog and/or
SM map, SSVAL should be run to determine whether any SM map/7990 catalog
mismatches exist. The following call accomplishes this.
SSVAL ,FM=f ami 1 yname, SB=ni,n2 nh,AM.

familyname is that for which recovery was done; ni,n2,...,nhare the affected subfamilies
if just some of the devices of the family were reloaded.

0ms

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 4 9

Restrictions to SSVAL

SSVAL analyzes the SM map, 7990 catalog, and PFC entries for the subfamilies
specified by the SB parameter and reports any discrepancies or inconsistencies. For ^^
example, if the recovery was not scheduled and SSLABEL was run to add or remove '
cartridges or cubicles from one of the affected subfamilies after the last incremental or
full dump for these subfamilies, then the SM map will reflect the results of the
SSLABEL run but the 7990 catalog will not. Such mismatches will be reported on the
validation report.
If the following SSVAL command is then made, the errors detected during the
previous run will be flagged, as described previously under Release Processing and
Problem Fixing.
SSVAL, FM=f am il yname ,SB=ni,n2,... ,nh,AM,FX=n.

familyname and m,n2,...,nhare the same as in the previous SSVAL run; n is the
number of errors detected during the previous run. After investigating the cause of
these errors, the analyst can run the SSDEBUG utility to correct the error conditions
(refer to SSDEBUG later in this section).
If a device reload includes recovery of all SM maps (default family, user
index=3777608), the latest SM maps should be recovered from backup copies. Then
each family that has 7990-resident files should be analyzed using the following
command to detect SM map/7990 catalog mismatches.
SSVAL, FM=f ami 1 yname, AM.

It is recommended that the previous SSVAL run be made periodically to check whether
any unexpected error conditions exist. As the site analyst becomes more familiar with
M S E p r o c e s s i n g , t h e s e p e r i o d i c S S VA L r u n s c a n b e d o n e l e s s f r e q u e n t l y. " ^ )
Restrictions to SSVAL
The following restrictions apply to the SSVAL utility.
• SSVAL cannot be run when SSMOVE is in the process of destaging files.
• Only one copy of SSVAL can be run at a time.
• S S VA L , S S L A B E L , a n d S S D E B U G c a n n o t b e r u n a t t h e s a m e t i m e . ^ ^

11 - 5 0

NOS

Version

Analysis

Handbook

Revision

SSUSE

0$ms

SSUSE
SSUSE reads data in the 7990 catalogs and SM maps and produces reports on the
availability of space on 7990 cartridges and the allocation of cubicle space within an
SM. The reports may not be completely up to date because the 7990 catalogs and SM
maps can be updated while the reports are being generated.
The types of reports that SSUSE generates are:
Report

00b\

Description

Basic usage report

Usage report that lists general information about the use of
each SM in a subfamily.

Optional report A

SM map report that lists the contents of an SM as described
in the SM map.

Optional report B

Cartridge summary report that lists general status information
for each cartridge entry in the 7990 catalog. The report
identifies the available AUs and flags set for each cartridge in
the 7990 catalog.

Optional report C

Detailed cartridge report that lists cartridge usage information
for each cartridge entry in the 7990 catalog.

Optional report D

Detailed AU status report that lists AU status information for
each entry in the 7990 catalog plus cartridge usage
information.

The format of the SSUSE command is:
SSUSE,p,,p2 Pn-

Description

CM=A-

Cartridge manufacturer code is A-, indicating IBM.

Same as CM=A-.

CM omitted

Same as CM=A-.

CN=csn

Cartridge serial number of a specific cartridge. The CN = csn
parameter is valid only if the OP=D parameter is specified.

Cartridge serial number is not specified.

CN omitted

Same as CN.

FM=familyname

Family to be reported on.

Same as FM = system default family.

FM omitted

Same as FM = system default family.

L=filename

File on which listable output is to be written.

Same as L=OUTPUT.

Revision M

Mass Storage Extended Subsystem (MSE) 11-51

SSUSE

Report

Description

L=0

No output file is to be generated.

L omitted

Same as L=OUTPUT.

OP=op

Type of report to be generated. Multiple options can be specified
(for example, OP=AB).
op

Description

Optional report A and basic usage report.

Optional report B and basic usage report.

Optional report C and basic usage report.

Optional report D and basic usage report.

»^5S\

MTST
MTST
MTST
MTST
SF

Figure 11-9. SSUSE Optional Report A

11-56 NOS Version 2 Analysis Handbook

Revision M

Optional Report B

Optional Report B
Optional report B includes a title line identifying the subfamily, family, and SM being
reported on. There is one line of output per cartridge within a subfamily and storage
module. The report includes the following cartridge information about entries in the
7990 catalog.
• Group and ordinal in group.
• y and z coordinates.
• Cartridge manufacturer code and CSN of the cartridge.
• Free AUs for small and large files.
• Cartridge flags.
• Error conditions.
0^S

Figure 11-10 shows the format of optional report B.
yy/mm/dd. hh.mm.ss. PAGE
SSUSE REPORT FILE

SSUSE OPTIONAL REPORT B - CARTRIDGE SUMMARY REPORT SM » A SUBFAMILY = 6 FAMILY = MTST
NOTES:
FA = FLAWED AND ALLOCATED
FU = FLAWED AND UNALLXATED
SF = START OF FRAGMENT
FC = FROZEN CHAIN
AC = AU CONFLICT
GPORD = ORDINAL IN GROUP

GP GPORD
1
1
1

0
1
2

21
20
19

CM CSN
7
7
7

CARTRIDGE FLAGS:
M = MISSING
I = INHIBIT
F = FREE CARTRIDGE
L = LINK(FREE AU EXIST, NO OFF CARTRIDGE LINK)
P = EXCESSIVE WRITE ERRORS
E = MAP ERROR(DETECTED BY SSVAL)
FREE AU
SMALL LARGE

A-13268794
A-51329412
A-51328839

1800
1800
1800

0
3
4

CART
FLA6S
I L

-ERROR CONDITIONS
—NUMBER OF AU
FA
FU
SF
FC

0
0
0

Figure 11-10. SSUSE Optional Report B

/Gw&H&'X,

Revision M

Mass Storage Extended Subsystem (MSE) 11-57

Optional Report C

Optional Report C
Optional report C is the detailed cartridge report. It lists the group and FCT ordinal
for each 7990 catalog entry and the y and z coordinates and CSN for each cartridge.
The report also includes the AU numbers of the first AUs for small and large files and
the division point for each cartridge.
Figure 11-11 shows the format of optional report C.
yy/mm/dd. hh.mm.dd. PAGE 33
SSUSE REPORT FILE
SSUSE OPTIONAL REPORT C - DETAILED CARTRIDGE REPORT SM = A SUBFAMILY = 6 FAMILY = MTST
FLAGS:

M= M I S S I N G P = E X C E S S I V E PA R I T Y E R R O R S
X L = AVAILABLE LINK COUNT FCTORD = SFM CATALOG ORDINAL

I = INHIBIT ALLOCATION
E = MAP ERROR

A
U
Y
21
20
19

CM CSN
A-13268794
A-51329412
A-51328839

GROUP

FCTORD

1
1
1

16
17
18

FLAGS
I
I

FIRST
SMALL
1
1
1

CARTRIDGE
FIRST DIVISION
LARGE POINT
0
1801
1916
1801
1832
1801

CCL
0
2
0

Figure 11-11. SSUSE Optional Report C

11 - 5 8

NOS

Version

Analysis

Handbook

Revision

Optional Report D

0^S
Optional Report D
j ^ s

Optional report D is the detailed AU status report. It lists the group and FCT ordinal
of the cartridge, the CSN, the y and z coordinates of the cartridge, and the number of
available off-cartridge links. The report also includes the octal numbers of the AUs
with flawed AU, start of volume, and error flags noted. This report also specifically
notes when a cartridge is empty (for use in determining the status of a cartridge that
is to be made available).
Figure 11-12 shows the format of optional report D.
yy/mm/dd. hh.mm.ss. PAGE

SSUSE REPORT FILE

SSUSE OPTIONAL REPORT D - DETAILED AU STATUS REPORT SM = A SUBFAMILY = 1 FAMILY = MTST
F = FLAWED AU (DEMARK FAILURE)
V = START OF VOLUME
E = ONE OF THE ERROR FLAGS SET (AU CONFLICT, FROZEN CHAIN. START OF FRAGMENT)
0$$k®\

FCTORD Y
16
21

A
U

100X
101X
102X
103X
104X
105X
106X
107X
110X
111X
112X
113X
114X
115X
116X
117X
120X
121X
122X
123X
I24X
125X
126X
127X
130X
131X
132X
133X
134X
135X
136X
137X

Z
1

XXXO
0041300731
0041200731
0041100731
0041000731
0040700731
0040600731
0040500731
0040400731
0040300731
0040200731
0040100731
0040000731
0040531131
0040431131
0040331131
0040231131
0040131131
0040031131
0041731214
0041631214
0041531214
0041431214
0041331214
0041231214
0041131214
0041031214
0040731214
0040631214
0040531214
0040431214
0040331214
0040231214

CM CSN GROUP
A-51328833 1
XXX1
0041270731
0041170731
0041070731
0040770731
0040670731
0040570731
0040470731
0040370731
0040270731
0040170731
0040070731
V0000621214
0040521131
0040421131
0040321131
0040221131
0040121131
0040021131
0041721214
0041621214
0041521214
0041421214
0041321214
0041221214
0041121214
0041021214
0040721214
0040621214
0040521214
0040421214
0040321214
0040221214

XXX2
0041260731
0041160731
0041060731
0040760731
0040660731
0040560731
0040460731
0040360731
0040260731
0040160731
0040060731
0040611131
0040511131
0040411131
0040311131
0040211131
0040111131
0040011131
0041711214
0041611214
0041511214
0041411214
0041311214
0041211214
0041111214
0041011214
0040711214
0040611214
0040511214
0040411214
0040311214
0040211214

XXX3
0041250731
0041150731
0041050731
0040750731
0040650731
0040550731
0040450731
0040350731
0040250731
0040150731
0040050731
0040601131
0040501131
0040401131
0040301131
0040201131
0040101131
0040001131
0041701214
0041601214
0041501214
0041401214
0041301214
0041201214
0041101214
0041001214
0040701214
0040601214
0040501214
0040401214
0040301214
0040201214

XXX4
0041240731
0041140731
0041040731
0040740731
0040640731
0040540731
0040440731
0040340731
0040240731
0040140731
0040040731
0040571131
0040471131
0040371131
0040271131
0040171131
0040071131
V0001771414
0041671214
0041571214
0041471214
0041371214
0041271214
0041171214
0041071214
0040771214
0040671214
0040571214
0040471214
0040371214
0040271214
0040171214

XXX5
0041230731
0041130731
0041030731
0040730731
0040630731
0040530731
0040430731
0040330731
0040230731
0040130731
0040030731
0040561131
0040461131
0040361131
0040261131
0040161131
0040061131
0041761214
0041661214
0041561214
0041461214
0041361214
0041261214
0041161214
0041061214
0040761214
0040661214
0040561214
0040461214
0040361214
0040261214
0040161214

XXX6
0041220731
0041120731
0041020731
0040720731
0040620731
0040520731
0040420731
0040320731
0040220731
0040120731
0040020731
0040551131
0040451131
0040351131
0040251131
0040151131
0040051131
0041751214
0041651214
0041551214
0041451214
0041351214
0041251214
0041151214
0041051214
0040751214
0040651214
0040551214
0040451214
0040351214
0040251214
0040151214

XXX7
0041210731'
0041110731
0041010731
0040710731
0040610731
0040510731
0040410731
0040310731
0040210731
0040110731
0040010731
0040541131
0040441131
0040341131
0040241131
0040141131
0040041131
0041741214
0041641214
0041541214
0041441214
0041341214
0041241214
0041141214
0041041214
0040741214
0040641214
0040541214
0040441214
0040341214
0040241214
0040141214

Figure 11-12. SSUSE Optional Report D

<0$s
Revision M

Mass Storage Extended Subsystem (MSE) 11-59

SSDEBUG

SSDEBUG
SSDEBUG allows the analyst to update appropriate entries in the SM maps and/or
7990 catalogs and thereby resolve inconsistencies reported by the SSVAL utility.
SSDEBUG can also copy data from selected 7990 files or cartridges to disk. This
function of SSDEBUG is intended for use when errors such as unrecoverable read
errors do not allow successful staging of a 7990 file.
NOTE
SSDEBUG updates the SM map for the specified SM. (Refer to the definition of SM
map earlier in this section.) It is recommended that the SM map is copied on tape or
on another device or family immediately after every update of the SM map.
Input to SSDEBUG is via a directive file. Refer to SSLABEL, earlier in this section,
for a description of the directive file format.
The format of the SSDEBUG command is:
SSDEBUG, pi, P2.P3-

pi
I=filename

Description
File on which directives are written.

Same as I=INPUT.

I omitted

Same as I = INPUT.

L=filename

File on which listable output is to be written.

Same as L=OUTPUT.

L=0

No output file is to be generated.

L omitted

Same as L=OUTPUT.

Directives are contained on the SSDEBUG command. The
I parameter is ignored.

Z omitted

Directives are contained on the file specified by the I parameter.

11-60 NOS Version 2 Analysis Handbook

Revision M

SSDEBUG Directives
/^p^\

SSDEBUG Directives
The following directives are available with SSDEBUG. The descriptions of the
parameters for these directives follow this listing of directives.
OP=RS — Read AUs
OP=RS reads selected AUs of a cartridge identified by its csn (CN=csn) or y and z
coordinates (YI and ZI parameters). The SM parameter specifies the SM where the
cartridge resides. The range of AUs to be read is specified by the SL and SU
parameters. The AUs are written to the file specified by the PF parameter. All CYBER
data plus 7990 and CRC data, including header and trailer information, is returned.
The analyst can write an application program to reconstruct the permanent file by
stripping off all CYBER or 7990 related control information. Refer to Format of Disk
Files Read From 7990 by SSDEBUG later in this section for a description of the
control information written to disk along with the disk file contents.
OP=RF — Read File
OP = RF reads the file whose alternate storage address is specified by the FO, SB, SM,
and ST parameters. The file is written to the file specified by the PF parameter. All
data, including header and trailer information, is returned (refer to Format of Disk
Files Read From 7990 by SSDEBUG later in this section).
OP=RP — Release Frozen Chain Space
OP=RP clears flags in the 7990 catalog and releases 7990 space for the chain whose
alternate storage address is specified by the FO, SB, SM, and ST parameters.
OP=RL — Remove Cartridge Entry From 7990 Catalog
OP=RL removes a 7990 catalog entry that is not linked properly to the SM map. The
FO, SB, and SM parameters identify the 7990 catalog entry to be removed.
OP=RC — Remove Cartridge Entry From SM Map
OP=RC removes an SM map entry that does not have a corresponding FCT entry in
the 7990 catalog. The SM, YI, and ZI parameters identify the SM map entry to be
removed. The cartridge at the particular location (y,z) is put into the exit tray and the
SM map entry is changed to unassigned. The SM map should be backed up
immediately after the SSDEBUG run to ensure consistency with cartridge labels and
7990 catalogs (refer to the definition of SM map earlier in this section).
A scratch label is written on the cartridge prior to it being replaced in the exit tray,
but the cartridge history information remains intact.
OP=CF — Change Flag in SM Map or 7990 Catalog
OP = CF sets or clears flags in the SM map or 7990 catalog. The FL and ON or OF
parameters indicate the flag type and the action to be taken. The appropriate FCT
entry or SM map entry is determined from the CN, FO, or YI and ZI parameters. For
FCT flags (FL=AC, FC, or SF), the analyst can specify either a single AU using the
ST parameter or a range of AUs using the SL and SU parameters.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 6 1

Parameters for the SSDEBUG Directives

Parameters for the SSDEBUG Directives
.•^tf^V

The descriptions of the parameters to the SSDEBUG directives follow. Not all
parameters are valid with all directives, as indicated.
Pi

Description

CM=A-

Cartridge manufacturer code is A-; indicating IBM.

Same as CM=A-.

CM omitted

Same as CM=A-.

CN=csn

Cartridge serial number of the cartridge to be used; not valid for
OP=RS if YI=y or ZI = z is specified; and not valid for OP=CF if
FO=ord, YI=y, or ZI=z is specified.

CN omitted

YI=y and ZI = z must be specified for OP=RS. FO=ord or YI=y
and ZI = z must be specified for OP=CF.

FL=flag

Name of flag in SM map or 7990 catalog to be set or cleared.
Valid only for OP=CF.
fl a g

Description

A C A U c o n fl i c t fl a g .
EW Excessive write parity error flag.
F C F r o z e n c h a i n fl a g .
FE Linkage error flag (in 7990 catalog FCT).
I B I n h i b i t a l l o c a t i o n fl a g .
L C L o s t c a r t r i d g e fl a g .
ME Linkage error flag (in SM map).
S F S t a r t o f f r a g m e n t fl a g .
FL omitted

FL=flag must be specified for OP = CF.

FM=familyname

Family to be processed.

Same as FM = system default family.

FM omitted

Same as FM = system default family.

11-62 NOS Version 2 Analysis Handbook

^^v

Revision M

Parameters for the SSDEBUG Directives

Description

FO=ord

7990 catalog ordinal indicating the file to be read or the chain
whose space is to be released. Not valid for OP=CF if CN = csn,
YI=y, or ZI=z is specified.

FO omitted

FO=ord must be specified for OP = RF, OP = RP, and OP = RL.
CN = csn or YI=y and ZI=z must be specified for OP=CF.

Flag specified by FL=flag is to be cleared. Valid only with
OP = CF.

Flag specified by FL=flag is to be set. Valid only with OP=CF.

PF=filename

File to which the 7990 image is to be copied. This file is defined
under the user's current family and user index.

Same as PF=MMMMBUG.

PF omitted

Same as PF=MMMMBUG.

SB = subfamily

Subfamily to be used; 0 ^ subfamily ^ 7.

Same as SB = 0.

SB omitted

Same as SB = 0.

SL=i

AU where OP=RS begins copying or OP = CF begins changing
flags; 1 ^ i ^ 1931; i ^ j (refer to SU=j).

Same as SL=1.

SL omitted

Same as SL=1.

SM=id

SM identifier of the SM to be used by SSDEBUG; id is a letter
from A to H.

Same as SM=A.

SM omitted

Same as SM=A.

ST=s

AU where OP = RF begins reading files or fragments or OP = RP
begins releasing frozen chain space. If specified with OP=CF,
ST=s specifies the AU number of an FCT flag to be changed and
takes precedence over the range of AUs specified by the SL and SU
parameters. AU numbers are meaningful with OP = CF only for
flags FL=AC, FC, or SF.

r
Revision M

Mass Storage Extended Subsystem (MSE) 11-63

Parameters for the SSDEBUG Directives

Description

ST omitted

ST=s must be specified for OP=RF and OP=RP.

SU=j

AU where OP=RS ends copying or OP=CF ends changing flags;
1 ^ j ^ 1931; i ^ j (refer to SL=i).

Same as SU=1.

SU omitted

Same as SU = 1.

YI=y

y coordinate of the cubicle where the cartridge to be read resides;
0 *£. y *s 21. ZI=z must also be specified. CN=csn must not be
specified with OP=RS. FO=ord or CN=csn must not be specified
with OP=CF.

YI omitted

CN=csn must be specified for OP=RS. FO=ord or CN=csn must
be specified for OP=CF. YI=y and ZI=z must be specified for
OP=RC.

ZI=z

z coordinate of the cubicle where the cartridge to be read resides;
0 ^ z ^ 15 and z*6. YI=y must also be specified. CN=csn must
not be specified with OP=RS. FO=ord or CN = csn must not be
specified with OP=CF.

ZI omitted

CN=csn must be specified for OP=RS. FO=ord or CN = csn must
be specified for OP=CF. YI=y and ZI=z must be specified for
OP=RC.

11-64 NOS Version 2 Analysis Handbook

Revision M

Using SSDEBUG

Using SSDEBUG
Suppose the following validation report (figure 11-13) was generated by running SSVAL
for problem reporting purposes.

SUBFAMILY =4 SM =
ERR IDENTIFICATION

TYP
5 ORPHAN

7 UNALLOCATED

PROBLEMS
LPD1 = yy/mm/dd. hh.mm.ss
-CHAINERROR DESCRIPTION
FCT - AU -- A/U - H/E
017-1737 AH-

ILL-FORMED CHAIN
SCATTERED FILE (INFO)

017-1738
017-1739
017-1740
017-1741
017-1742
017-1743
017-1930
017-1931
019-0000

A—
A—
A ~
A—
A—
A—
A—
A—

START OF FRAGMENT

019-0000

u
—

START OF FRAGMENT

Figure 11-13. SSDEBUG: Executing SSVAL in Problem-Fixing Mode
This partial validation report shows an error type 5 identified by ORPHAN with an
error description of ILL-FORMED CHAIN (frozen chain). You can use SSDEBUG to set
(OP=CF) and release (OP=RP) the frozen chain space or you can execute SSVAL in
problem-fixing mode to set the frozen chain flag.
Enter the following SSDEBUG command to set the frozen chain flag for the range of
AUs specified by the SL and SU parameters.
SSDEBUG,Z./OP=CF,FL=FC,ON,FM=SMD,SB=4,SL=1737,SU=1931,F0=17.

When the SSDEBUG or SSVAL command is processed, enter the following command to
release the frozen chain space.
SSDEBUG,Z./0P=RP,SB=4,SM=A,ST=1737,FO=17.

When this command is processed, you can verify that the frozen chain has been set by
running SSVAL again to generate another validation report.

0$m\.

Revision M

Mass Storage Extended Subsystem (MSE) 11-65

Restrictions to SSDEBUG

Restrictions to SSDEBUG
The following restrictions apply to the SSDEBUG utility.
© SSEXEC must be running when SSDEBUG is run.
• Only one copy of SSDEBUG can be run at one time.
© SSDEBUG, SSVAL, and SSLABEL cannot be run at the same time.
y,z Relationship with SM Map Ordinal
A one-to-one functional mapping exists between coordinate pairs and the ordinal entries
within the SM map. To determine the coordinate pair (y,z) from the SM map ordinal
(ord), use the following equations:
y = (352-ord)/l6
z = 352-ord-16y

To determine the SM map ordinal (ord) from the coordinate pair (y,z), use the following
equation:
ord=352-z-16y

A^Sl.

11-66 NOS Version 2 Analysis Handbook

Revision M

Format of Disk Files Read From 7990 by SSDEBUG

0ms
Format of Disk Files Read From 7990 by SSDEBUG
A local disk file created by SSDEBUG with the OP=RS or OP=RF option includes all
CYBER and 7990 header and trailer information. Figure 11-14 shows the format of a
disk file created when SSDEBUG reads a full stripe; figure 11-15 shows the format of
a disk file created when SSDEBUG reads a partial stripe.

word o
12c

7990 READ RAW DATA MESSAGE (64 BYTES)
(PACKED 6 BYTES PER 60-BIT WORD, LEFT-JUSTIFIED
ZERO-FILLED)
7990 STRIPE HEADER (32 BYTES) © ©

7990 BLOCK HEADER LABEL (16 BYTES)
(PACKED 7.5 BYTES PER WORD WITH 1 BYTE LEFTJUSTIFIED IN THIRD WORD)
CYBER HEADER LABEL (150 BYTES) ©

CYBER DATA © \

© BYTES ARE 8-BIT ASCII BYTES PACKED 7.5 BYTES PER 60-BIT WORD IN A CONTINUOUS BIT STREAM.
© FOR FULL STRIPES, THE BLOCK TYPE IN THE 7990 BLOCK HEADER IS 01.
(f) FOR CYBER DATA. EVERY 255TH BYTE IS A CRC BYTE. THE LAST BYTE IS ALWAYS A CRC BYTE TO
TAKE CARE OF SHORT DATA BLOCKS. FULL CYBER DATA BLOCKS HAVE 26 CRC BYTES.

Figure 11-14. Full Stripe Disk File Format

yi$RS

Revision M

Mass Storage Extended Subsystem (MSE) 11-67

Format of Disk Files Read From 7990 by SSDEBUG
A^^S.

WORD 0
12c

7990 READ RAW DATA MESSAGE (64 BYTES)
(PACKED 6 BYTES PER 60-BIT WORD, LEFT-JUSTIFIED,
ZERO-FILLED)
7990 STRIPE HEADER (32 BYTES) ©

7990 BLOCK HEADER LABEL (16 BYTES) ©
(PACKED 7.5 BYTES PER WORD WITH 1 BYTE LEFTJUSTIFIED IN THIRD WORD)
CYBER HEADER LABEL 1150 BYTES) ©
CYBER DATA ©
n PRUs OF CYBER DATA (n < 13) ©
(483 BYTES PER PRU)

7990 BLOCK TRAILER LABEL (16 BYTES)
(SAME FORMAT AS 7990 BLOCK HEADER LABEL)

UNUSED BYTES ©

© BYTES ARE 8-BIT ASCII BYTES PACKED 7.5 BYTES PER 60-BIT WORD IN A CONTINUOUS BIT STREAM.
© FOR PARTIAL STRIPES, THE BLOCK TYPE IN THE 7990 BLOCK HEADER IS 01 FOR DATA BLOCKS AND
1016 FOR TAPE MARK BLOCKS.
(3) FOR CYBER DATA, EVERY 255TH BYTE IS A CRC BYTE. THE LAST BYTE IS ALWAYS A CRC BYTE TO
TAKE CARE OF SHORT DATA BLOCKS.
0 A TAPE MARK HAS A 7990 BLOCK HEADER AND TRAILER, BUT NO DATA BLOCK.

Figure 11-15. Partial Stripe Disk File Format

11-68 NOS Version 2 Analysis Handbook

Revision M

Format of Disk Files Read From 7990 by SSDEBUG

7990 Stripe Header and Trailer
The 7990 stripe header is a 32-byte block that occupies the first 32 bytes of the stripe;
the 7990 stripe trailer occupies the last 32 bytes. The 7990 stripe header and trailer
have the same format.
Bytes

Description

0-5

Volume serial number. A 6-character string specifying the volume
serial number of the stripe.

6-7

Version number. Two characters specifying the version number
associated with the volume serial number.

8-9

File number. Two characters specifying the number of the file
within the volume.

A-B

Logical stripe number. Relative stripe number within the volume.
The logical stripe number may not correlate with the physical
stripe number due to demarked stripes.

C-D

Address of last block trailer. Byte number, within the stripe, of the
first byte of the last block trailer.

E-1D

Reserved.

1E-1F

Checksum. Chosen such that the sum, modulo 65536, of all bytes in
the header equals zero.

0ms
Revision M

Mass Storage Extended Subsystem (MSE) 11-69

Format of Disk Files Read From 7990 by SSDEBUG

7990 Block Header and Trailer
^*<^x

Each 7990 block has a 16-byte header that precedes each block and a 16-byte trailer
that follows each block, or partial block, of data on the stripe. The 7990 block header
and trailer have the same format.
Byte(s)

Description

0-1

Block type. The following block types are valid.
Block
Type

Description

A complete block is contained in this stripe.

First block segment of a multistripe block.

Intermediate block segment of a multistripe block.

Last block segment of a multistripe block.

1016

Tape mark.

2-3

Block length. The number of bytes in a data block excluding the
block header and trailer. The block length of a tape mark is zero.

4-7

Block sequence number. The number of a given data block within a
file.

8-9

Block segment number. For complete blocks, the segment number is
0 (zero). For multistripe blocks, the segment number is the
sequence number of the block segment within the data block.

A-E

Reserved.

Checksum. Chosen such that the sum, modulo 256, of all bytes in
the header equals zero.

i < ^ ^ \

<>^53Sv

11-70 NOS Version 2 Analysis Handbook

Revision M

SSBLD
0^iu_

SSBLD
SSBLD reads a specified direct access permanent file that contains SSBLD statements.
These statements consist of 7990 component-oriented mnemonics that define the logical
mapping from component to component within the 7990 configuration. SSBLD processes
these statements and generates a direct access permanent file which SSEXEC uses as
its unit device table (UDT).
The format of the SSBLD command is:
SSBLD,CF=confile,BF=bldfile.

Parameter Description
CF=confile Configuration file on which SSBLD statements are written under
user index 377760s.
CF

Same

C F = S U D T.

CF omitted Same as CF=SUDT.
BF=bldfile Build file on which SSBLD generates the UDT for SSEXEC. The
build file is under user index 377760s.
BF

Same

B F = B U D T.

BF omitted Same as BF = BUDT.

SSBLD Statements
The 7990 hardware consists of a number of 7990 control units (CU) and a number of
7991 storage modules (SM). SSBLD uses two types of statements: those that link
individually controllable nodes and paths within each CU, and those that link SMs to
CUs. SSBLD statements must be processed in the following sequence or SSBLD aborts.
1. Statements that define the linkage between nodes and paths within each CU.
2. Statements that define the linkage between SMs and CUs.
NodelPath Linkage Statements
These SSBLD statements are order-dependent. There are seven types of statements for
a given CU and they must appear together in the following sequence and format:
1. CUest=da,CH01=st,CH02=st,CH03=st,CH04=st.

est EST ordinal of the CU (10s through 777s).
da Device address of CUest.
st Channel status (ON or OFF).

/#^V

The CYBER channel number is associated with the 7990 channel interface (CIF)
number. The position (first, second, and so on) of the channel in the CU
statement minus 1 defines the CIF number wired to that channel. For example,
CH02 is wired to CIF1. Also, if a single digit channel is used to connect to a
7990, it must have a leading 0 in the CU statement. For example, channel 3 is
entered as CH03.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 7 1

SSBLD Statements

2. CIFn=DTIO=St,DTI1=St,DTO0=St,DT01=St.

n Device address of CIF (0 through 3).
DTI Data transfer input.
DTO Data transfer output.
st Data transfer status (ON or OFF).
3. DTIn=DIF0=St,DIF1=St.

n Device address of DTI (0 or 1).
DIF Device interface.
st Device interface status (ON or OFF).
4. DTOn=DIF0=st,DIF1=st.

n Device address of DTO (0 or 1).
st Device interface status (ON or OFF).
5. DIFn=DRC0=st,DRC1=st.

n Device address of DIF (0 or 1).
DRC Data recording controller.
st Data recording controller status (ON or OFF).
If two DRCs exist in a CU, their device addresses must be paired as 0 and 1 or 2
and 3.
6. DRCn=DRDO=st DRD7=st. or DRCm=DRD8=St....,DRD15=St.

n Device address of DRC (0 or 1).
m Device address of DRC (2 or 3).
DRD Data recording driver.
st Data recording driver status (ON or OFF).
DRCs 0 and 1 can link only to DRDs 0 to 7, and DRCs 2 and 3 can link only to
DRDs 8 to 15.
7. AIFn=ACO=st,AC1=St,AC2=st,AC3=St. or AIFn=AC4=st,AC5=St,AC6=St,AC7=st.

AIF
Accessor
n Device address of AIF (0 or 1).
AC Accessor.
st Accessor status (ON or OFF).

A^m\

interface.

)

An AIF can link to either ACs in the range 0 to 3 or 4 to 7, but not to ACs
from both ranges.

11 - 7 2

NOS

Version

Analysis

Handbook

Revision

SSBLD Statements

SMICU Linkage Statements
yffl^Bfc^

The SM statement defines the linkage between SMs and CUs; its format is:
SMi d=st,ACn,CUest,CUest,DRDa=st,DRDa=st,DS=d,ST=s.
Parameter

Description

i d S M i d e n t i fi e r ( A t h r o u g h H ) .
st Status (ON or OFF).
n Device address of AC (0 through 3).
est EST ordinal of the CU(s) connected to SMid.
a Device address of the DRD(s) connected to ACn.
d Number of DRDs for destaging per storage module (0 to 2).
Default is 1.
s Number of DRDs for staging per storage module (0 to 2). Default
is 2.
SSBLD and SSEXEC use the common deck COMBUDT to define the amount of
memory to reserve within SSEXEC for the unit device tables. Any attempt to change
the number of SMs or CUs specified in the common deck will cause SSBLD to abort.
SSBLD Example
The first two SSBLD statements specify the total number of CUs and SMs in the
following configuration. The first statement specifies CUs and the second statement
specifies SMs. The rest of the statements define the 7990 configuration.
1
1
CU41=0,,CH23=ON,f.
CIF1=DTI0=ON,,DTO0=ON,.
DTI0=DIF0=ON,DIF1=ON.
DTO0=DIF0-ON,DIF1=ON.
DIFD=DRC0=ON,DRC1=ON.
DIF1=DRC0=ON,DRC1=ON.
DRC0=DRD0=ON,DRD1=ON
DRC1=DRD0=ON,DRD1=ON,,,,,,.
AIF0=AC0=ON,,,.

SMA=ON,ACO,,CU41,DRD0=ON,DRD1=ON,DS=1,ST=2.
•COMMENT.

An asterisk (*) in the first column of an SSBLD statement specifies a comment
statement. Comment statements are not sent to the dayfile.

0$ms

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 7 3

7990 Equipment Configuration Constraints

7990 Equipment Configuration Constraints
Control paths and data paths within the 7990 configuration have certain constraints
placed upon the allowable device addresses of the accessors and DRDs. The accessor
numbers and corresponding DRD numbers are:
Accessor
Number

DRD Numbers

0 or 1

2 or 3

4 or 5

6 or 7

Accessors and DRDs that are to be coupled to two controllers must have the same path
numbers assigned from each controller. For example, if an accessor is plugged into ^^
accessor path 2 of CU1, then a DRD on the same storage module must be coupled to a ^^
DRC path of 4 or 5 from CU1. If a second controller is to be attached to this same
storage module, then the other accessor port must also be plugged into accessor path 2
of CU2 and a DRD must be coupled to a DRC path of 4 or 5 from CU2.

11 - 7 4

NOS

Version

Analysis

Handbook

Revision

SSALTER

SSALTER
SSALTER displays the current 7990 hardware configuration and allows an analyst to
change the status of certain elements in the 7990 configuration. SSALTER works with
SSEXEC to make the specified changes to the existing 7990 configuration.
The initial 7990 configuration file is built by the SSBLD utility and stored as a
permanent file (default file name is BUDT) under user index 377760s on the default
family. This configuration file is the unit device table read by SSEXEC during
initialization.
SSALTER can be run at SSEXEC initialization time or at any time after SSEXEC
has been initialized. SSALTER aborts if SSEXEC is not executing.
Console Input
SSALTER can be executed only from the system console. Input from the console
requires the following sequence of entries and responses:
1. Call SSALTER by entering:
X.SSALTER.

The B,0 display indicates the job sequence name (jsn) of SSALTER. To the right
of the entry appears the message:
REQUEST *K* DISPLAY

2. Activate the K display for that control point by entering:
K, jsn.

In this entry, jsn is the job sequence name of SSALTER as specified on the B,0
display.
3. Select the desired K display by entering one of the following:
K.SM=id.

This entry selects the SM K display (figure 11-16), which shows the 7990
configuration of the storage module and DRDs complete with status information
(id is the SM identifier, A through H).
K.CUest.

This entry selects the CU K display (figure 11-17), which shows the status of
various paths/nodes in the specified control unit (est is the EST ordinal of the
CU).

yam**.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 7 5

Console Input

7990 SUBSYSTEM - SSALTER

PCU
ST
SM

42U

DRD

SCU
ST

SM/DRD

U
,A*^S\

VALID COMMANDS ARE K.SMI ,CUNN=S.
K.SMI ,DRDN,CUNN=S.

K.+
I = SM IDENTIFIER
N = DRD DEVICE ADDRESS
N = CU EST ORDINAL
S = STATUS - U FOR ONLINE
F FOR OFFLINE
M FOR MAINTENANCE
+ = DISPLAY NEXT SM

Figure 11-16. SM K Display
When a DRD's status is changed to online, any cartridges in the DRD are placed in
service cells if space is available; otherwise, they are ejected from the storage module.
A clear cartridge is then loaded into the DRD, its cartridge label and CSN are
checked, and it is unloaded. The same cartridge is reloaded, its label and CSN are
checked again, and the cartridge is returned to its cubicle. The service cells are then
checked for cartridges. If a cartridge is found, it is either returned to the cubicle
matrix or ejected from the storage module, depending on the cartridge label's contents.
When a SM's status is changed to online, the accessor is first cleared of any
cartridge it may contain. The cartridge is stored in a service cell if one is empty;
otherwise, the cartridge is ejected from the storage module. The accessor then picks a
clear cartridge from its cubicle, and immediately puts it back. If the SM's status is
changed to online after SSEXEC has been initialized, the service cells are then
checked for cartridges. Any cartridges found are ejected from the storage module.

11-76 NOS Version 2 Analysis Handbook

Revision M

Console Input

7990 SUBSYSTEM - SSALTER

ORD

C
U
ST

CU42

CIF1

DTIO

DTOO

DIFO

DRCO

DTIOU

DIFOU

DRCOU

DRDOU

DTI1U

DIF1U

DRC1U

DTOOU

DTI1

DT01

DIF1

DT01U

DIFOU

DRCOU

AIF1

DIF1U

DRC1U

SMAOU

DRC1

AIFO

SMAOU

DRD1U

00&S

CH ST

CIF

24 ON

Figure 11-17. CU K Display

Revision M

Mass Storage Extended Subsystem (MSE) 11-77

MSE Operational Procedures

MSE Operational Procedures
Next is a summary of the operational procedures used in an MSE environment. These
procedures include modifications to existing procedures and new MSE procedures,
especially in the areas of permanent file backup and reloading and disk space
management. Refer to the descriptions of the appropriate utilities for details about
these operational procedures.

Initialization
MSE processing is initiated when the SSDEF utility is run to create the system files
necessary to allow storage of files on 7990. SSDEF creates both an SM map for each
SM that is to store file data on cartridges and eight 7990 catalogs (one for each
subfamily) for each family that is to have 7990-resident files. Once these system files
have been created, the SSLABEL utility can then be run to allocate portions of the SM
to each subfamily and to initialize cartridges for use by files belonging to these
subfamilies. Note that SSEXEC need not be executing when SSDEF is run, but
SSEXEC
must
be
executing
when
SSLABEL
is

run.

When permanent files are defined, they reside on disk until the SSMOVE utility is
run. Depending on the parameters specified, SSMOVE can destage files to 7990 and
release the disk space assigned to files so that it is available for general use.

^tfSx&V

11 - 7 8

NOS

Version

Analysis

Handbook

Revision

Disk Space Management

Disk Space Management
The availability of disk space must be managed more frequently in an MSE
environment than in a non-MSE environment. This is necessary because 7990-resident
files must be staged to disk before a user can access them, and their disk space is not
immediately released upon completion of the jobs that attached the files. Consequently,
disks are apt to approach a disk-full condition unless the SSMOVE utility is used
periodically to release disk space.
The SSMOVE utility destages selected files to 7990 and optionally releases their disk
space. It is recommended that the site analyst use SSMOVE as part of a periodic disk
space management procedure and also just prior to a full dump to reduce the amount
of data dumped to tape. (Refer to Dump Tape Management later in this section.)
The E,M display can be used to monitor the tracks on a device or set of devices.
When too few tracks (as defined by the installation) are available on the direct access
devices for a family or subfamily, the SSMOVE utility should be run. SSMOVE reads
the PFC entries for the specified family, selects certain files to reside on 7990, and
decides which files should be released from disk.
Files can be destaged to 7990 without their disk space being released. This
destage-only feature can be used prior to a routine backup dump to create 7990
images for files with the BR=MD attribute and thereby eliminate the need to include
them on a backup dump tape. (Refer to Dump Tape Management later in this
section.) Having a 7990 image also provides backup for the file in special cases where
the permanent file is being updated at the same time PFDUMP is being run.
The destage-only feature can also be used to allow disk space to become available
immediately when SSMOVE is run again. That is, SSMOVE can directly release disk
space of files that have both disk and 7990 images but are to reside on 7990 only.
However, for files that have no 7990 image, there is a delay before the disk space
can be released because these files must first be destaged to 7990.
Permanent file PFGMSE1 contains sample procedures FREEDSK and DESTAGE to
show how a site may use SSMOVE for disk space management. FREEDSK waits in
the rollout queue for a low disk space threshold flag to be set. FREEDSK is then
rolled in for execution and calls SSMOVE to release disk space. The DESTAGE
procedure calls SSMOVE at set times to destage files to 7990 whose file size in PRUs
falls within the range specified by the MN = min and MX=max parameters. Each site
can change the SSMOVE parameters and directives in the sample procedures to
satisfy their requirements.
NOTE
Before using the FREEDSK and DESTAGE procedures, you must call the SSCONTL
procedure to build the programs necessary to monitor the low disk space threshold
and the time.

j*W"S

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 7 9

7990 Space Management

7990 Space Management
T h e a v a i l a b i l i t y o f 7 9 9 0 s p a c e m u s t b e m a n a g e d b e c a u s e 7 9 9 0 s p a c e i s n o t ■>
automatically released when a permanent file is purged. This allows you to perform a
permanent file recovery to a time prior to the purging of the file. On a typical dump
tape, the entry for a 7990-resident file includes the PFC and permit entries, but not
the file data. A subsequent reload operation recovers only what was dumped; the PFC
and permit information, but not the file data. Thus, 7990 space for a purged permanent
file cannot be released until you no longer need to recover the file data, because the
file data resides on 7990 only and typically not on any dump tape.
A 7990-resident file is stored only on the cartridges within the cubicles of SMs
assigned to a subfamily. When destaging a file to 7990, SSEXEC selects the SM with
the most space available. If no SM has enough free space to store the file being
destaged, SSEXEC abandons that destage request, issues a message to the dayfile,
and continues to destage other files that fit on the available 7990 space. To avoid
this problem, use the SSVAL utility periodically to release 7990 space for purged
fi l e s ,
thereby
making
it
available
for
reuse.

^s^
"i

When you want to reuse 7990 space currently allocated to files that have been
purged, he/she runs SSVAL with the RF and RL parameters specified. The RF
parameter specifies an RDF, which is an auxiliary file produced by the permanent
file utility PFDUMP and which contains versions of the 7990 catalogs and PFC
entries that were current at the time of the dump. SSVAL examines the RDF to
identify unneeded 7990 files (those without PFC entries) and their 7990 space is
released. Choose which RDF to use based on the date and time of the dump that
produced it. That is, a particular RDF is used only if there is no need for a
p e r m a n e n t fi l e r e c o v e r y t o a t i m e p r i o r t o t h e d u m p t h a t p r o d u c e d t h e R D F. * * ^
Once an RDF is used by SSVAL to release 7990 space, you should discard it and any
other RDFs for the same set of devices. These RDFs cannot be used as input to
SSVAL in any future run. The MSE software does not permit an RDF to be specified
by the RF parameter on an SSVAL call, unless it was produced by PFDUMP after
the last SSVAL run that released 7990 space was completed. This prevents the
inadvertent release of 7990 space that was previously released and reassigned to a
file.

11 - 8 0

NOS

Version

Analysis

Handbook

Revision

7990 Space Management

Example 1:
Assume that two PFDUMPs were run a week apart producing two release data files,
RDF1 and RDF2. Assume, also, that according to both RDF1 and RDF2, file AFILE
is an orphan (it has been purged but still resides on 7990). If the following call to
SSVAL is made, the 7990 space assigned to AFILE is released and made available for
reuse, if no errors were encountered.
SSVAL,RF=RDF1,RL.

Now, suppose that a new file, BFILE, which did not exist when RDF1 and RDF2 were
produced, is assigned to the 7990 space on which AFILE has resided. If SSVAL were to
accept either RDF1 or RDF2 on a subsequent SSVAL call, the 7990 space allocated to
file AFILE (which is now the space where BFILE resides) is released. However, any
RDF created after the SSVAL run that purged AFILE would not have an entry for
AFILE and, hence, SSVAL would not inadvertently release the 7990 space presently
allocated to BFILE.
After SSVAL uses a release data file to release 7990 space, the corresponding backup
tape from PFDUMP is the oldest tape that should be used for the first reel of a
future incremental load. The first reel determines which files are to be reloaded
according to the CIR on the tape (refer to PFLOAD in section 17, Permanent File
Utilities). Use of an older tape as the first reel can allow the PFC entry for a purged
file to be restored even though its 7990 space may have been reassigned. The MSE
software does not prevent loading from the wrong dump tape, but does detect as an
error an attempt to stage a file whose data was overwritten (see Example 2).
0^S

Example 2:
Assume that RDF1 and RDF2 are as in the previous example, and that file CFILE is
an orphan according to RDF2, but not according to RDF1. The following SSVAL call
releases 7990 space allocated to CFILE.
SSVAL,RF=RDF2,RL.

Now suppose that the dump tape created by the PFDUMP run that produced RDF1 is
used as the first reel of an incremental PFLOAD. Then the PFC and permit entries for
file CFILE are reloaded, but, in fact, file CFILE does not exist on 7990. This will be
detected as an error when a user attempts to attach CFILE.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 8 1

Backup and Recovery

/*^K

Permanent file backup and recovery methods in an MSE environment are similar to
those in a non-MSE environment. It is assumed that most sites with disk-resident
permanent files have a file backup procedure consisting of a full dump followed by a
series of incremental dumps. The assumed reload procedure is to load from tapes
starting with the most recent incremental dump tape and continuing through older
incremental dump tapes until the most recent full dump tape is processed. These
procedures can be modified as follows to accommodate 7990-resident files.
File Dumping
The normal backup dump procedure is to dump files based on the modification date
field in the PFC entries for the files. New parameters to PFDUMP provide the
capability to dump files that have been modified during a certain interval, which is
useful in recycling old dump tapes (refer to Dump Tape Management later in this
section). For files that reside only on 7990, you can either stage the file to disk and
thereby include it in the dump or suppress staging and include only the file's PFC and
permit information on the dump tape. If the device or family being dumped has
7990-resident files, the following procedures should be included with the normal
dumping procedures.
Full Dumps
Full dumps should be performed as usual, but OP=S should be specified on the call to
PFDUMP to suppress staging. Thus, all files on disk are dumped but only the PFC and
permit entries for 7990 files without disk images are included in the dump. It is
unnecessary and not feasible to dump the files that reside only on 7990. Specify OP=S
and SD on the call to PFDUMP; use the RD=filename parameter at your own
discretion.
Parameter

Description

OP=S

Selects no staging. If the SD option was inadvertently used on any
previous nonincremental dump, an incremental dump should be
taken prior to the full dump.

Updates the dump date/time field on each master device dumped to
permit files created or modified prior to this dump to be released
when SSMOVE is run again. Refer to Destage and Release
Algorithms earlier in this section.

RD=filename

Specifies that PFDUMP is to write a release data file to be used
later by SSVAL. RD=filename is included or excluded on a call to
PFDUMP depending on how often you want to purge unneeded
7990 files.

.<^s£v

11-82 NOS Version 2 Analysis Handbook

Revision M

File Dumping

Incremental Dumps
Incremental dumps should be performed as usual. No staging should occur because any
files that were created or modified since the last dump will still be on disk if a tape
backup is required. The following parameters should be specified on the call to
PFDUMP.
Parameter Description
OP=M Selects incremental dumps.
SD Updates the date/time field on each master device dumped, as
previously described for full dumps.
AD=yymmdd Selects the date just prior to the previous incremental or full dump
and of the device. Hence, all files not included in the last dump are
AT = h h m m s s d u m p e d .
The following parameters should be used with caution.
Parameter Description
OP = S Selects no staging. If the SD option was inadvertently used on any
recent partial dump, OP=S should not be specified so any file with
a BR=Y attribute that had its disk space inadvertently released
will be included in the dump.
RD=filename Specifies that PFDUMP is to write a release data file to be used
later by SSVAL, as previously described for full dumps.
Dump Tape Management
In a non-MSE environment, it is possible to make all previous dump tapes available for
use after a full dump is completed. However, in an MSE environment, such dump tape
recycling cannot occur because files that have resided only on 7990 for some time are
probably not included on any recent dump tape. When a low percentage of files on a
tape are active files, it is possible to redump any remaining files in order to recycle
the tape by running PFDUMP and specifying OP=M, BD, and BT parameters, but not
specifying the OP = S parameter.4 This performs a dump of all files that were last
dumped before the date and time specified on the PFDUMP call. If necessary, files will
be staged in from 7990; after the dump is completed, the disk space for these staged
files is released. Thus, files that might not be on any dump tape made after the date
specified by the BD parameter are dumped and tapes created before this date can be
recycled.

0$m\
0m*s

4. It is possible to specify the AD and AT parameters also, thereby dumping files that were dumped during
an interval after the date and time specified by AD and AT and before the date and time specified by BD
and BT (refer to parameters for PFDUMP). This performs a dump of all files last dumped during the
interval specified (including 7990-resident files) and allows your site to recycle all dump tapes created
during this interval.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 8 3

File Dumping

The number of dump tapes created can be reduced by using SSMOVE to reduce the
amount of data written on these dump tapes. If SSMOVE is run prior to an
incremental dump, files with the BR=MD attribute can be destaged to 7990 and
excluded from the dump. That is, the incremental dump will exclude the files with a
BR=MD attribute that are on both 7990 and disk. If SSMOVE is run prior to a full
dump, disk space for files that do not have to be on disk can be released and these
files are not written on the dump tape. The following procedure involving dumps and
SSMOVE runs can be used for efficiency.
1. Run SSMOVE to destage files with the BR=MD attribute.
2. Take an incremental dump to back up files with the BR=Y attribute.
3. Run SSMOVE to release the disk images of files backed up in step 2.
4. Take a full dump to reduce the number of dump tapes involved if a reload is
required.
/^^s\

SM Map/7990 Catalog Backup
An SM map is created for each SM in an MSE environment and is updated by the
SSLABEL, SSVAL, and SSDEBUG utilities. (Refer to the definition of SM map earlier
in this section.) It is recommended that the SM map be copied on tape or on another
device or family immediately after every update of the SM map. PFDUMP can be used
to do this by dumping user index 377760s with FM equal the default system family
name, but only if SSEXEC is not running. When SSEXEC is executing, it has the SM
map files attached in modify mode; hence, PFDUMP will not dump the SM maps.
If the device containing subfamily 0 of the default family is reloaded, the latest SM
maps should be recovered from the backup copies. After recovering the SM maps, run
the SSVAL utility with the AM and FM parameters specified to ensure that the SM
map and 7990 catalog entries match. If they do not, corrective action should be taken
as described in Error Conditions and Corrective Actions later in this section. Failure
to retain or recover the latest SM maps can cause problems with future SSLABEL
runs (refer to the definition of SM map earlier in this section).
A 7990 catalog is created for each subfamily of a family that can have 7990-resident
files and is updated by the SSLABEL, SSMOVE, SSVAL, and SSDEBUG utilities.
When PFDUMP copies permanent files to tape for a master device or all devices in a
family, it ensures that corresponding 7990 catalogs are also dumped. (If SSEXEC has
a 7990 catalog attached in modify mode, PFDUMP interfaces with SSEXEC so that
the 7990 catalog is included on the dump tape. While PFDUMP is accessing the 7990
catalog, any file destage requests for that subfamily are delayed.) Consequently, if
PFLOAD is used to reload all files, the 7990 catalogs are automatically recovered and
entries for all 7990-resident files reflected in recovered PFC entries will exist in the
recovered 7990 catalog.

A^ms

If PFLOAD is run after the SSLABEL utility has updated the 7990 catalog and SM
map but before the 7990 catalog has been backed up, the recovered 7990 catalog will
not match exactly the corresponding SM map. In this case, recovery procedures (as
described in 7990* Catalog/SM Map Mismatch later in this section) must be taken to
bring the SM map, 7990 catalog, and cartridge label information into agreement.
r-c%\

11 - 8 4

NOS

Version

Analysis

Handbook

Revision

File Reloading

File Reloading
PFLOAD runs should be made as usual. PFLOAD reads the CIR records from the most
recent incremental dump tape to control loading of file data and PFC and permit
information. For 7990-resident only files, PFLOAD reloads only the PFC and permit
information (if PFDUMP dumped only this information). The following situations
involve PFLOAD in an MSE environment.
• If one device needs to be reloaded, the DN or TD parameter specifies the device.
The OP=Z and UD parameters should not be specified.
• If PFLOAD is used for other than a device recovery, both OP=Z and UD should
be specified. The OP = Z parameter ensures that the PFC entry does not link to a
7990 file that may no longer exist, and UD ensures that the file is included in
the next incremental or full dump.
• If a file has a nonzero asa value in its PFC entry (indicating that the file has a
7990 image), the SSCVER flag in the PFC entry will be set when the PFC and
permit information are reloaded. If the file is successfully staged to disk when it
is attached, this flag is cleared. Otherwise, the flag remains set. This can be used
to indicate the possibility of an operational error, such as omitting OP=Z when a
file or set of files is reloaded from an obsolete dump tape.
• If any unscheduled device reload that includes recovery of a 7990 catalog and/or
SM map is made, SSVAL should be run with the AM and FM parameters
specified. SSVAL examines the PFC entries for 7990-resident files, the 7990
catalog, and the SM map to detect any error conditions that exist.
• If dumping a file to tape from one user and then reloading the file to a different
user, you must use the OP=Z parameter on the PFLOAD utility. Otherwise the
PFC entry still points to the old SFMCAT, which causes an error indication for
the file.

0^\\

Revision M

Mass Storage Extended Subsystem (MSE) 11-85

Error Conditions and Corrective Actions

Error Conditions and Corrective Actions
It is possible for operational, hardware, or software malfunctions to cause a variety of
error conditions to exist or appear to exist in the 7990 catalogs, SM maps, PFC
entries, or cartridge labels. The SSVAL utility can analyze the 7990 catalogs, SM maps,
and PFC entries to detect these errors, and the SSLABEL utility can identify problems
with cartridge labels. The following paragraphs describe some specific error conditions
and the actions that should be taken to correct them. Most of the errors are caused
either by incorrect operational procedures that result in the recovery of the wrong
version of an MSE system file, or by abnormal termination of SSEXEC or MSE utility
processing, which can interrupt the updating of an MSE system file.
Clearing Permanent File Error Flags
The permanent file error flags that have been set by SSEXEC in the PFC can be
cleared by the CE parameter of the CHANGE command. The job must be of system
origin.
Permanent File Recovery
If a permanent file cannot be accessed or is included by SSVAL on the validation
report, try the following procedures to recover a copy of the file.
1. Attach the file. If the file has a disk image or can be staged in from 7990, the
file data will be available on disk and can be copied to another file. SSVAL
should then be run as described in step 2.
2. If the file cannot be attached, reload the file from a dump tape using PFLOAD ^"^%
with OP=Z. To identify the PFDUMP run that saved a backup copy of the file,
check the output from SSVAL or PFCAT, which includes date and time fields from
the PFC entry for the file. Depending on the BR attribute (backup requirement) of
the file, a backup copy on a dump tape may not exist.
If the file can be reloaded to disk, SSVAL should be run as follows:
SSVAL,FM=fami 1yname,SB=subfamily,FX=n,AM.

familyname and subfamily identify the family and subfamily of the recovered file
and n is sufficiently large that the fixing/flagging will be done. SSVAL sets the
obsolete flag in the PFC entry because the file now has a disk image; thus the
file is disassociated from the error condition. The error condition may still exist in
the 7990 catalog or SM map, but you can analyze it and correct the error by
using the SSDEBUG utility. Before using SSDEBUG to correct the error, you
should take an incremental dump so the old PFC entry with an asa value
pointing to a problem 7990-resident file will not be reloaded if a device reload
occurs before the next scheduled backup dump.
3. If steps 1 and 2 fail, try to regenerate the file. Depending on the particular
problem and status of the cartridges to which the file was destaged, the OP=RF
or OP=RS directive to SSDEBUG might recover the file data.
4. If the file cannot be recovered, purge it so there is no PFC entry pointing to a
problem 7990-resident file.

11 - 8 6

NOS

Version

Analysis

Handbook

Revision

Cartridge Restoration and Reuse

Cartridge Restoration and Reuse
If a cartridge is unexpectedly found anywhere outside its assigned cubicle, follow these
steps to restore the cartridge so it can be used again:
1. Put the cartridge in the input tray of the SM to which it is assumed to belong
and run SSLABEL with the OP=RS directive. If the cartridge label information
agrees with the SM map entry for the cubicle with the coordinates (y,z) written
on the cartridge label, the cartridge will be restored to that cubicle and the 7990
catalog entry for the cartridge is updated to clear the lost flag. Otherwise, the
cartridge is put in the exit tray and the cartridge label information is included in
the output from SSLABEL.
2. If the cartridge was not restored to its SM cubicle, examine the label information
reported by SSLABEL. If the cartridge is assigned to a different SM, repeat step 1
using the correct SM. If the family name is blank, the cartridge has a scratch
label and can be assigned normally with the OP = AM directive to SSLABEL.
3. If steps 1 and 2 fail, examine the SM map entry for the cubicle with the
coordinates (y,z) written on the cartridge label to see how the cubicle is assigned.
Examine the cartridge, if any, in this cubicle. Also, it might be useful to run
SSVAL to ensure the SM map and 7990 catalog entries for the cartridge match or
to identify affected permanent files, if any, if they do not match.

J$$™&\

4. If step 3 does not produce any useful information and the cartridge cannot be
restored, use the OP=FX directive to SSLABEL to rewrite the cartridge label and
thereby make a scratch cartridge. It might be useful to first run SSDEBUG with
the OP = RS directive to preserve the data on the cartridge.

0$&S,

Revision M

Mass Storage Extended Subsystem (MSE) 11-87

Removal of Faulty or Missing Cartridges

Removal of Faulty or Missing Cartridges
Follow these steps to remove a cartridge that has unrecoverable errors, or to release
the SM map entry for a cartridge that is missing.
For unallocated cartridges:
1. Attempt to remove the cartridge with the SSLABEL OP=RM directive.
2. If CARTRIDGE NOT FOUND is reported, repeat step 1 specifying the LT
parameter.
3. If CARTRIDGE NOT EMPTY is reported, at least one AU on the cartridge is still
allocated.
For allocated cartridges:
1. Use the SSLABEL OP=FC directive to inhibit further allocation of the cartridge.
2. Run SSVAL specifying the AM parameter. Examine the report for possible
discrepancies between the SM map, 7990 catalog, and PFC entries related to this
cartridge.
3. If no 7990 catalog entry corresponds to the SM map entry, use the OP = RC
directive to SSDEBUG to remove the map entry.
4. If no discrepancy is reported by SSVAL, the affected files should be attached in
write mode (if possible), reloaded using PFLOAD with the OP=Z parameter, or
purged. Then SSVAL release processing should be done to release the 7990 space
on the cartridge, and the cartridge can be removed with the SSLABEL OP=RM
directive.

>c^.

11-88 NOS Version 2 Analysis Handbook

Revision M

7990 Catalog/SM Map/PFC Problems

7990 Catalog/SM Map/PFC Problems
If error conditions exist in the 7990 catalogs or SM maps, the recovery procedure is to
correct the appropriate entry rather than reload the entire file. Reloading other than
the latest copy of the SM map is not feasible because it can contain entries for several
families and these entries would not be up to date. Reloading an old copy of the 7990
catalog is not desirable because any permanent file that was destaged and released
from disk since the last incremental dump will be lost. The following paragraphs
describe corrective action for specific problems with 7990 catalogs, SM maps, or PFC
entries.
7990 CatalogISM Map Mismatch
The following examples of 7990 catalog/SM map mismatches can appear as error type 1
or 2 on the SSVAL output report, which identifies the mismatch and the permanent
files or orphans affected. Before taking any corrective action, the analyst should ensure
that operational errors did not result in loading the wrong version of the SM map or
7990 catalog.
• If a cartridge has a 7990 catalog entry indicating that all AUs on the cartridge
are available for allocation but is not identified in any SM map entry (type 1
mismatch), use the OP = RL directive to SSDEBUG to remove the 7990 catalog
entry for the cartridge.
• If a cartridge is identified in an SM map entry but has no 7990 catalog entry
(type 2 mismatch), use the OP=RC directive to SSDEBUG to update the SM map
entry to unassigned and empty status. This directive will write a scratch label for
the cartridge, if any, and place the cartridge in the exit tray.
• If a cartridge has a 7990 catalog entry indicating that at least one AU on the
cartridge is allocated, recover the disk space for the affected permanent file, if
any, or purge the file. Run SSVAL to purge unneeded 7990 files and thereby
make the cartridge unallocated. Use the OP = RL directive to SSDEBUG to remove
the 7990 catalog entry for the cartridge.
NOTE
It sometimes takes two SSVAL/SSDEBUG runs to completely clear up type 1 or type
2 errors. Therefore, it is recommended that SSVAL be rerun with the AM parameter
after an SSDEBUG run using OP=RC or OP=RL.

Revision

Mass

Storage

Extended

Subsystem

(MSE)

11 - 8 9

7990 Catalog/SM Map/PFC Problems

7990 Catalog Chain Problems
AUs that are allocated to a 7990-resident file are chained together in the 7990 catalog
to identify the sequence of AUs that contain the file. (Refer to the definition of
cartridge earlier in this section.) For most files, the AUs in the chain reside on the
same cartridge. Hence, one disk access is sufficient to update information for the entire
chain at one time. However, a 7990-resident file can reside on several cartridges, and
several disk accesses may be necessary to update its chain. If SSEXEC is interrupted
during such an update, the resultant chain will be incomplete. SSVAL identifies
incomplete chains as error type 4, 5, or 6 on the validation report. The following are
types of incomplete chains.
• If an incomplete chain is produced while a 7990-resident file is being purged, it is
a chain fragment (one without an HOC entry).
• If an incomplete chain is produced while a file is being destaged to 7990, it is an
ill-formed chain (one without an EOC entry).
• If an ill-formed chain is not corrected, the AU that should have been linked to it -^%,
may be reused and become part of a good chain. Although the ill-formed chain
may appear to be complete, the ill-formed chain and the good chain are
intersecting.
The corrective action for any of these bad chain conditions is:
1. Run SSVAL with the FM parameter specified and use a sufficiently large FX=n
value so that SSVAL updates the 7990 catalog entries affected by the problem
chains.
2. Recover the permanent files, if any, that have 7990 images potentially affected by
these error conditions. (The SSVAL report identifies these files.) Use the procedure
described under Permanent File Recovery earlier in this section.
3. Take an incremental or full backup dump. This prevents PFC entries with
inaccurate asa values or problem 7990 chains from being recovered if a device
reload is necessary.
4. Run SSDEBUG with the OP=RP directive to make each AU on the problem chain
available for allocation. Thus, the AUs can be included in a new chain without /SiB%
any problems. In the case of intersecting chains, all chains that have an AU in '
common with another chain should be released before any further destage
attempts; otherwise, errors will occur when a user tries to attach a file that is
contained on an intersecting chain.
PFC/7990 Catalog Mismatch
It is possible that an old version of a 7990 catalog can be reloaded because of incorrect
operational procedures. If so, the asa value in the PFC entry for a file can be invalid
according to the obsolete 7990 catalog or can point to a problem chain. If the correct
version of the 7990 catalog is available on tape, it should be reloaded. If it is not
available, the following action is appropriate. If the file also has a disk image, SSVAL
should be run to clear the asa field in the PFC entry. If there is no disk image, the
analyst should reload the file from tape, if possible, and then run SSVAL to clear the
asa value.

11 - 9 0

NOS

Version

Analysis

Handbook

Revision

Ta p e

Alternate

Storage

Introduction...........
12-1
Ta p e
Alternate
Storage
Te r m i n o l o g y
12-1
O r g a n i z a t i o n a n d M a n a g e m e n t o f D e s t a g e D u m p Ta p e s 1 2 - 3
Ta p e
Characteristics
12-3
Ta p e
Data
Format
12-3
Destaging
Files
to
Ta p e
12-3
Releasing
Disk
Space
12-5
Restoring Destaged Files to Disk Residence 12-6
Modifying
Destaged
Files
....
,
12-7
Recycling
Destage
Dump
Ta p e s
12-7
MAGNET

# ^

0^*.

0m^-

Command

GENPFD
Utility
Calling
the
GENPFD
Utility
GENPFD
Input
Directives
File
Selection
Processing
...:
..
Limitations

12-8
12-9
12-9
12-10
12-13
12-13

j0^ahjix\

Ta p e

Alternate

Storage

Introduction
This section describes the use of magnetic tape as an alternate storage medium for
NOS permanent files.

Tape Alternate Storage Terminology
The following terms apply to the use of tape alternate storage.
Alternate Storage
The storage of permanent file data on external media other than mass storage
such as tape alternate storage or MSE. When a file resides on alternate storage,
the file's permanent file catalog (PFC) entry and permit data still reside on disk,
but the disk space occupied by the file data can be released.
Alternate Storage Address (ASA)
The pointers in a file's PFC entry that point to the location of the file data on
tape alternate storage or MSE.
Destage Dump Tapes
Tapes that contain files that were destaged from disk using the PFDUMP utility
with the DT parameter specified.
Destaging
The process of creating an alternate storage copy of a file on tape alternate
storage or MSE. Files are destaged to tape alternate storage when the site
executes PFDUMP with the DT parameter specified. Files are destaged to MSE
when the site executes SSMOVE with the appropriate parameters.
Permanent File Catalog (PFC)
The system catalog containing the file name, owner identification, disk pointers,
alternate storage pointers, and other attributes of a permanent file. Refer to
Permanent File Catalog Entry in section 17, Permanent File Utilities, for the
format of the PFC entry.
Primary VSN
The volume serial number (VSN) of a single reel destage dump tape or the VSN
of the first reel of a multireel set of destage dump tapes. The VSN must be two
alphanumeric characters followed by a four-digit decimal number; the number
must be in the range 0000 through 4095.

Revision

Ta p e

Alternate

Storage

12-1

Tape Alternate Storage Terminology

Secondary VSN
The VSN of a single reel destage dump tape or the VSN of the first reel of a
multireel set of destage dump tapes having a sequence number (the last four
characters of the VSN) in the range 5000 through 9095. The existence of a
secondary VSN assumes the existence of a primary VSN having the same
two-character prefix and a sequence numbeF of 5000 less. The primary and
secondary VSN tapes, or multireel sets of tapes, are assumed to contain identical
data although the individual reels of multireel sets cannot be assumed to be
identical.
Staging
The process of restoring file data to disk residence from a copy on alternate
storage. Staging is initiated when a user executes an APPEND, ATTACH, GET, or
OLD command for a file that is not currently disk resident.

,/*®^\

12-2 NOS Version 2 Analysis Handbook

Revision M

Organization and Management of Destage Dump Tapes

0^S

Organization and Management of Destage Dump Tapes
The tape characteristics and data format required for destage dump tapes are described
below, followed by some of the procedures required to manage destage dump tapes.
Tape Characteristics
Destage dump tapes must be labeled, I format, and nine track. The tapes can be
written at any nine-track tape density. It is possible to have multireel sets of tapes,
but normally single reels are created whenever possible to avoid the overhead of reel
switching when restoring files to disk. The VSN of the first reel of a set of destage
dump tapes must be in the following format:
ppnnnn

0i^s

where pp is a prefix consisting of any two alphanumeric characters and nnnn is a
decimal sequence number in the range from 0000 through 4095 or in the range from
5000 through 9095. If the sequence number is 5000 or greater, the secondary tape set
is assumed to be a duplicate of a primary tape set that has the same prefix and a
sequence number of 5000 less.
Tape Data Format
All destage dump tapes are written by PFDUMP and have exactly the same format as
other tapes written by PFDUMP including file permits. However, no PFC-only files are
present on destage dump tapes. It is also possible to load, copy, or list files from a
destage dump tape using the PFLOAD, PFCOPY, or PFATC utility, respectively.
Destaging Files to Tape
Destage dump tapes are created by executing PFDUMP with the DT (destage to tape)
parameter specified. When the DT parameter is used, PFDUMP verifies the following:
• The dump file specified by the T parameter must be assigned to a nine track, I
format, labeled tape. The VSN must be in the format ppnnnn as described earlier
(refer to Tape Characteristics) and the sequence number must be in the range
from 0000 to 4095.
• If a verify file is specified (VF parameter), it too must be assigned to a nine
track, I format, labeled tape and its VSN must have the following relation to the
VSN for the primary dump tape: the two-character prefix must be the same and
the sequence number must be greater by 5000.
After the dump tape or tapes are successfully written, PFDUMP enters the primary
dump tape VSN in the PFC entries of the dumped files. If a verify file is written, a
flag is also set in the PFC entry indicating the existence of the secondary VSN. At
this point, the disk space of the dumped files can be released, if necessary, if the file's
backup requirements are satisfied.

0ms.

Revision

Ta p e

Alternate

Storage

12-3

Destaging Files to Tape

Although general PFDUMP selection parameters can be used to directly select files for
a destage dump, sites will normally use a separate file selection utility such as
GENPFD to perform this function. (The GENPFD utility is described later in this
section.) This procedure has the following advantages:
• Files can be prioritized by the time since they were last accessed or modified.
• Special user index or file name patterns can be special cased according to site
requirements.
• The GENPFD selection utility can select files that will reasonably fill a single
tape reel without overflowing to additional reels. The creation of single reel tapes
is desirable because it avoids the overhead of reel switching when files are
restored to disk.
When a file selection program such as GENPFD is used for destage processing, the
following sequence of events should be followed:
1. Execute PFDUMP with the IP (inhibit processing) and DT (destage to tape) **%,
parameters specified and the summary file selected with the S parameter.
Specifying PFDUMP parameters such as LS, US, BD, BT, etc., can be used to
screen out desired classes of files. The TA=N and CA=N parameters can be used
to exclude files that already have current alternate storage copies (from previous
destage dumps).
2. Execute the file selection program (GENPFD) using the PFDUMP summary file as
input. The file selection utility writes UI and PF utility directives for the selected
files to the utility directives file.

SWt$K

3. Reexecute PFDUMP (with the same parameters as specified in step 1, but without
specifying the IP parameter) using the utility directives file generated in step 2 as
an input file.
When a destage dump is performed, files on user name SYSTEMX and on the MSE
catalog user names SUBFAMO through SUBFAM7 are unconditionally excluded even if
they meet the selection criteria.
Example:
Destage enough files to fill one tape (alternate storage) with files from family TEST
whose data has not been modified since 87/07/01 and have not already been destaged.
PFDUMP,FM=TEST,DT,OP=T,BD=870701,TA=N,IP,S.
REWIND,SUMMARY.
RETURN,UDIR.
GENPFD,PO=D.
REWIND,UDIR.
PFDUMP,FM=TEST,DT,OP=T,BD=870701,TA=N,I=UDIR.

In this destaging example, if GENPFD does not find enough files to fill a 2400-foot
tape at GE density, the utility will not generate a UDIR file. This will cause the
second PFDUMP to abort without dumping any files.

y**«^V

12-4

NOS

Version

Analysis

Handbook

Revision

Releasing Disk Space

Releasing Disk Space
The disk space of a file that resides on tape alternate storage or MSE can be released
if the file's backup requirements are met. The BR parameter on the DEFINE, SAVE,
and CHANGE commands allows a user to specify a backup requirement of Y (yes), MD
(media dependent), or N (none).
Parameter
Option Description
BR=Y The disk space of a file with a backup requirement of BR=Y can be
released if either of the following conditions is satisfied:
• At least two copies of the file data exist on alternate storage media.
This could be one copy on MSE and one copy on tape or two copies
(primary and secondary VSNs) on tape.
• One copy of the file data exists on an alternate storage medium
(either MSE or tape) and the release inhibit date/time of either the
file's master device or the file's residency device (as set by a
PFDUMP with the SD parameter specified) is greater than the file's
utility control date/time.
BR=MD The disk space of a file with a backup requirement of BR=MD can be
released if the following condition is satisfied:
• One copy of the file data exists on MSE or tape alternate storage.
0^S.

The PFREL utility is used to perform the releasing of disk space. As with PFDUMP,
PFREL can be used with a file selection utility such as GENPFD in the following
sequence of steps:
1. Execute PFREL with the IP (inhibit processing) parameter specified and the
summary file selected with the S parameter. Files can be excluded by specifying
selection parameters. In particular, OP=A can be used with the BD and BT
parameters to exclude files that have been accessed recently.

2. Execute the file selection program using the PFREL summary file as input. The
0^^ file selection utility writes UI and PF utility directives for the selected files to the
utility directives file.
3. Reexecute PFREL (with the same parameters as specified in step 1, but without
specifying the IP parameter) using the utility directives file generated in step 2 as
an input file.
The PFREL utility can be used to release the disk space of files that reside on MSE as
well as those files that reside on tape alternate storage. However, the MSE utility
SSMOVE performs release processing only for MSE resident files. PFREL does not
release the disk space of files cataloged on user name SYSTEMX or on the MSE
catalog user names SUBFAMO through SUBFAM7 even if the selection criteria are met.

Revision

Ta p e

Alternate

Storage

12-5

Restoring Destaged Files to Disk Residence
,/«8^.

Example 1:
The following example illustrates releasing disk space for destaged files.
Release the disk space for all files from family TEST that have not been accessed
since 87/07/01 and for which backup requirements have been met.
PFREL,FM=TEST,OP=A,BD=870701.

Example 2:

Using the same file selection criteria as in example 1, release enough files so that
10008 tracks are available on device number 40 and 12008 tracks are available on
device number 41.
PFREL,FM=TEST,OP=A,BD=870701,S,IP.
REWIND,SUMMARY.
RETURN,UDIR.
GENPFD,PO=R,Z./RL,40,1000/RL,41,1200
REWIND,UDIR.
PFREL,FM=TEST,I=UDIR.

Restoring Destaged Files to Disk Residence
A file that does not reside on disk is restored to disk residence (staged) when a user
accesses the file with an APPEND, ATTACH, GET, or OLD command. If the RT (real
time) parameter is specified on an ATTACH, GET, or OLD command and staging is
required, the job continues executing without waiting for the staging operation to
complete. In this case, the caller must subsequently reissue the ATTACH, GET, or
OLD command to access the file after the staging operation completes.
NOTE
In order to allow staging of files from tape alternate storage to disk, the site must
enter the ENABLE,TAPE PF STAGING command (via DSD or IPRDECK) and must
specify the SJ parameter on the MAGNET command in the MAG subsystem startup
procedure.

12-6

NOS

Version

Analysis

Handbook

Revision

Modifying Destaged Files

Modifying Destaged Files
When you modify a file having a copy or copies on alternate storage media, the data
on alternate storage is no longer current. Therefore, when a direct access file is
attached in a writable mode or an indirect access file is saved or replaced, the system
removes the pointers to all alternate storage copies in the file's PFC entry. At this
point, the file has to be destaged again (to tape or MSE) if it is to reside on alternate
storage.
Recycling Destage Dump Tapes
As files are modified and purged over a period of time, new destage dump tapes are
created and the percentage of active files on older destage dump tapes decreases.
Destage dump tape recycling consists of procedures to move the remaining active files'
data on old destage dump tapes to new destage dump tapes so that the old tapes can
be reused. Performing a destage PFDUMP (DT parameter) with staging enabled (OP=S
not specified) of all files on a tape or set of tapes copies all file data to a new tape
and changes all alternate storage references from the old tapes to the new tape.
Since only a subset of the files on tapes selected for recycling are typically active, a
site normally wants to include other files to fill a new tape. The following example
illustrates this procedure.
PFDUMP,IP,S,DT,FM=TEST,TA=N,TA=AB0005,TA=AB0006.
GENPFD,OP=D,Z./SV,AB0005/SV,AB0006/DL,2200/DT,0
REWIND,UDIR.
PFDUMP,DT,FM=TEST,I=UDIR.

The TA parameters on the first PFDUMP command select files residing on VSNs
AB0005 and AB0006 (the tapes being recycled) and files not residing on tape alternate
storage as candidates for destage. The SV directives cause GENPED to select all files
residing on VSNs AB0005 and AB0006 regardless of the priority of the modification
date derived priority and priority group. GENPFD selects other files using the normal
priority criteria to satisfy the destage limit specified by the DL directive. The DT
(destage threshold) directive performs a recycle dump even if there are not enough files
selected to fill the tape.
To help determine which destage dump tape VSNs should be recycled, you may want
to write a program that reads the PFCAT summary file and generates a list of how
many files are still active on each destage dump tape VSN.
You can determine if any current files reside on a particular destage dump tape VSN
by executing PFCAT with the TA=vsn parameter specified.
After you perform a recycle dump for a tape or a set of tapes, the tapes cannot be
reused until a full or incremental PFDUMP has been performed on the affected
devices. Without this PFDUMP, a permanent file reload could cause some of the
reloaded PFC entries to refer to tapes that no longer exist. To prevent this problem,
a tape recycling operation should always be immediately followed by a full or
incremental PFDUMP.

y fl $ ^ \

Revision

Ta p e

Alternate

Storage

12-7

MAGNET Command

MAGNET Command
The MAGNET command has two parameters that must be used in a tape alternate
storage environment. The SJ parameter controls the maximum number of staging jobs
that can be active concurrently to stage files to disk from tape alternate storage; and
the SV parameter controls the maximum number of staging request VSNs that can be
displayed on the DSD E,P display. Refer to the NOS Version 2 Operations Handbook
for a description of the DSD E,P display.
The MAGNET command has the following format:
MAGNET,SJ=msj,SV=mvd.

Parameter Description
SJ=msj Specifies the maximum number of staging jobs that can be active at
the same time (0 ^ msj ^ 30s). The default is SJ = 0; staging is not
allowed.
NOTE
The SJ parameter must be specified or staging from tape alternate
storage to disk will not be allowed.
SV = mvd Specifies the maximum number of requests for staging tape VSNs to
display on the DSD E,P display (1 ^ mvd ^ 77s). The default is
SV = 178. Requests for staging tape VSNs will appear first on the E,P
display (before the normal tape requests) and can be distinguished by -'frmh
h a v i n g a J S N o f S Y S a n d a u s e r n a m e o f ( S TA G E ) . '

12-8

NOS

Version

Analysis

Handbook

Revision

GENPFD Utility

GENPFD Utility
The GENPFD utility controls file selection processing. It reads a summary file created
by one of the permanent file utilities and uses the information to generate file
selection directives for subsequent permanent file utility operations.

Calling the GENPFD Utility
You call the GENPFD utility by executing the GENPFD command. The format of the
command is:
GENPFD,I=i nput,S=summary,UD=udi r,PO=opt,Z.di rect i ves

Parameter Description
I = input

The 1- to 7-character name of the file from which directives are read.
The default file name is INPUT.

S=summary

The 1- to 7-character name of the summary file previously created by
a permanent file utility. The default file name is SUMMARY. This file
is used as input to GENPFD.

UD = udir

The 1- to 7-character name of the utility directives file to be created.
This file is used for subsequent permanent file utility operations such
as destaging files and releasing disk space. The default file name is
UDIR.

PO = opt

The processing option that specifies whether to select files for destage
processing or releasing disk space. Acceptable values for opt are:
opt

Description

D Select files for destage processing.
R Select files for releasing disk space.
Input directives are contained on the GENPFD command following the
terminator. If the Z parameter is specified, the I parameter is ignored.
This eliminates the need to use a separate input file for the directives
when only a few directives are needed.
directives

When input directives appear on the GENPFD command, the first
character following the command terminator is the separator character
for all directives on the command. Any display code character that is
not used in any of the directives, including a space, can be used as the
separator character. Each directive must be preceded by a separator.
The directives can extend to column 72 on the command. Continuation
lines are not permitted.
For example, (slant used for separator):
GENPFD, POD, Z. /D=PE/DL, 2200/SF, 3456

Revision M

Tape Alternate Storage 12-9

GENPFD Input Directives

GENPFD Input Directives
The GENPFD input directives provide the capability to selectively choose files for
processing. The GENPFD utility accepts the following input directives:
Directive

Description

D=density

Density of the destage dump tape that will be written by the
destaging operation. Acceptable values for density are:
density

Description

800 cpi

1600 cpi

6250 cpi

1600

1600 cpi

6250

6250 cpi

The default density is 6250.
DL.limit

Destage size limit in feet of tape used with the PO=D option. (1to 10-digit number, assumed decimal unless a B radix is specified).
This directive specifies the maximum combined size of all selected
files. It is intended to prevent writing beyond the end of reel when
selecting files for destaging with the PFDUMP utility. If selection
of a file causes the limit to be exceeded, the file is skipped and
the next lowest priority file is examined. The default limit is 2200;
this allows for a significant number of tape errors on a 2400 foot
reel of tape.

DT,threshold

Destage size threshold in feet of tape used with the PO = D option.
(1- to 10-digit number, assumed decimal unless a B radix is
specified). Specifies the minimum combined size of all selected
files. If the combined size of all selected files is less than the
threshold, no utility directives file will be generated. This directive
is used to ensure that enough files can be selected on a destage
dump to reasonably fill a tape reel. The default value is 90
percent of the limit specified for DL.

PG,pi,p2,p3

Define preferred residence priority groups. The default is T,MN,D.
The parameters pn are strings of preferred residence mnemonics
which define the priority groups used in file selection. The groups
are defined in order of decreasing priority. The default value
defines three groups: 1) a high priority group consisting of files
with PR=T (tape alternate storage residence preferred); 2) a
medium priority group consisting of files having PR=M (alternate
storage residence preferred) and PR=N (no preferred residence);
and 3) a low priority group consisting of files having PR=D (disk
residence preferred). Files having PR=L (file locked to disk) are
excluded from selection.

12-10 NOS Version 2 Analysis Handbook

Revision M

GENPFD Input Directives

Directive

Description

PG,pl,p2,p3 (Continued)
It is possible to define other than three groups. For example, the
following entry:
PG.TMNDL

places all files in one group, effectively causing preferred residence
to be ignored. The following entry defines four groups.
It is possible to define other than three groups. For example, the
following entry:
PG.TMNDL

places all files in one group, effectively causing preferred residence
to be ignored.
PG.T.M.N.D

If a preferred residence type is not specified, files having that value
are excluded from selection unless they are selected explicitly with
an SF or SV directive. The following entry causes files with PR=D
or PR=L to be excluded:
PG.TMN

RL,dn,tracks Define the track release limit for device number dn or device
RL,dt,tracks type dt. A device type is specified as a mass storage equipment
mnemonic followed by a unit count. Files residing on a device are
not released unless you enter an RL directive specifying either the
device number or the device's type. A device number entry takes
precedence over a device type entry if both apply. Files residing on
the applicable device or devices are released until the number of
available tracks reaches the specified limit. No release processing is
performed for the device if the number of available tracks is equal
to or greater than the specified limit. For example, the following
device number entry:
RL.40,300

specifies that files should be released on device 40 until there are
300 available tracks. If 300 tracks are already available, no files
will be released.
The following device type entry:
RL.DQ2.250

specifies a release limit of 250 tracks for each two-spindle 885
device for which a limit has not been specified by device number.

n
Revision M

Tape Alternate Storage 12-11

GENPFD Input Directives

Directive Description
SF,ui,fi,f2,...,fn Unconditionally select the specified files cataloged under
SF,ui user index ui, if found in the summary file. If no file names are
specified, select all files cataloged under user index ui.
SV,Vi,V2 vn Unconditionally select any files found in the summary file with
alternate storage VSNs that match the specified VSNs. This
directive is intended to be used when recycling destage dump tapes
as part of destage processing. Specifying the VSNs of tapes to be
recycled prevents files residing on those tapes from being excluded
by the priority selection process.1
XF,ui,fi,f2,...,fn Exclude the selection of the specified files cataloged under
XF,ui user index ui. If no file names are specified, exclude all files
cataloged under user index ui.

1. The SF and SV directives cause GENPFD to treat the specified files as higher priority than others in the
selection process. In some cases, GENPFD satisfies the specified destage or release limits without selecting
all
of
the
files.

12-12

NOS

Version

Analysis

Handbook

Revision

•>*^\

File Selection Processing

File Selection Processing
The GENPFD utility sorts the candidate files into preferred residence priority groups
as determined by the PG directive. Within each group, each file is assigned a priority
based on the time elapsed since the last access (if PO = R) or last data modification (if
PO=D) with older files receiving higher priorities. Files selected with SF directives or
files residing on VSNs selected with SV directives are given a higher priority than
other files to force selection.
For destage processing, files are selected beginning with the highest priority until the
destage limit is reached. The permanent file utility parameters UI and PF are
written to the utility directives file for each selected file unless the combined length
of the selected files is less than the destage threshold (either the default or an
explicit nonzero value specified in the DT directive).
For release processing, files residing on devices specified by RL directives are selected
for release until the defined limit for each device is reached. The permanent file
utility parameters UI and PF are written to the utility directives file for all files
selected for release.

Limitations
GENPFD can process a maximum of 80 RL directives and a total of 1000 SF, SV, and
XF directives. Each directive counts as one entry, whether or not it contains a file
name or VSN. Each file name or VSN on a directive after the intial one counts as an
additional entry.
0Xts

Revision

Ta p e

Alternate

Storage

12-13

Multimainframe Operations 13
^

Introduction

13-1

Linked
SDM
Operation
Deadstart
Shared
Mass
Storage
C o n fi g u r i n g S h a r e d M a s s S t o r a g e D e v i c e s
Device
Access
Ta b l e s
Mass
Storage
Recovery
Ta b l e s
Device
Initialization
Device
Unload
Device
Recovery
..
Device
Checkpoint
MSE
Processing

13-2
13-3
13-6
13-6
13-6
13-7
13-7
13-8
13-8
13-9
13-9

Independent
SDM
Operation
13-10
Deadstart
,
13-10
Shared
Mass
Storage
13-12
C o n fi g u r i n g S h a r e d M a s s S t o r a g e D e v i c e s 1 3 - 1 3
Device
Index
Ta b l e s
,...
13-14
Mass
Storage
Recovery
Ta b l e s
13-14
Device
Initialization
13-14
Device
Unload
13-15
Device
Recovery
,
13-15
Device
Checkpoint
13-16
MSE
Processing
.-....'
13-16

Multimainframe Operations 13
Introduction
Multimainframe operation provides mechanisms by which more than one computer can
share mass storage devices. Each mainframe in a multimainframe configuration has
access to the shared mass storage devices and their preserved files. Preserved files are
those files that are retained across a level 0 deadstart (nonsystem recovery). Types of
preserved files are permanent files, queued files, and system dayfiles.
There are two types of multimainframe configurations:
• Linked shared device multimainframe (SDM).
• Independent shared device multimainframe.
The main difference between the two SDM configurations is their method of
maintaining the critical device tables necessary to control shared mass storage and
intermainframe communications. Linked SDM configurations maintain the critical
device tables in extended memory, while independent SDM configurations maintain the
tables on each shared mass storage device. Because the independent SDM
configurations maintain the tables on the shared devices, it causes some performance
degradation.
Each mainframe in a multimainframe configuration can operate in multimainframe
mode or in standalone mode; however, two machines may not access the same device
unless both are in multimainframe mode. A device is considered shared if it can be
accessed by more than one of the mainframes; it need not be accessible to all
mainframes in the complex.
The fact that a computer is operating as part of a multimainframe complex is not
apparent to the user, except for some degrading of performance for the independent
SDM. However, there are operational changes and additions that the operator should
note. These include deadstart commands, displays, online commands necessary in the
event of an interruption on one of the sharing mainframes, and the UNLOAD/MOUNT
process for removable devices.
Recovery allows a machine to either join other machines operational in a
multimainframe complex or to operate in a standalone mode. The standalone system is
not allowed to use the same mass storage devices as other machines. In the event of a
system interruption to one machine, it is possible to operate the remaining machines in
a multimainframe environment.
Automatic detection of extended memory is not provided, because it is not possible to
determine its absence and continue to run on all machine types. For example, a 6600
will hang if an attempt is made to execute an extended memory instruction without
extended memory. Extended memory status is checked during deadstart when
processing an extended memory entry in the EQPDECK.
Except where explicitly specified that controllers and/or equipment can be shared
between mainframes, assume they cannot be shared. For example, NOS does not
support sharing a two-channel tape controller between mainframes; nor does it support
sharing mass storage controllers except as specified in this section.

Revision

Multimainframe

Operations

13-1

Linked SDM Operation

Linked SDM Operation
In a linked SDM complex, up to seven computers can access mass storage devices. Any
combination of 1 to 7 model 71, 72, 73, 74, 171, 172, 173, 174, 175, 176, 720, 730, 740,
750, 760, 865, 875, CYBER 180-class machines or 6000 Computer Systems mainframes
can be used. Most mainframes require one CPU port connected to extended memory.
The exception is CYBER 180-class machines which must be connected to extended
memory through a low-speed port (LSP) or a distributive data path (DDP) instead of a
CPU port. Shared mass storage devices supported are: 844 (single and double density),
885-11/12, and extended memory.
Extended memory is the means for controlling shared mass storage and intermainframe
communications. Each mainframe has a port into extended memory through which
system activity is controlled. In order to control shared mass storage devices, several
extended memory resident tables are required. The device access table (DAT) contains
the logical description (family name/pack name and device number) of each mass
storage device (shared or nonshared) that is accessible by any machine in the linked
SDM complex. For each device in the DAT that is to be accessed by more than one
machine, a corresponding MST (image of central memory resident MST) and TRT also
reside in extended memory. In addition, a machine recovery table (MRT) exists in
extended memory for each machine and device (that is, there are as many MRTs for
each shared device as there are mainframes in the complex).
If MSE is used, one mainframe in the linked SDM complex is physically connected to
7990 and is called the master mainframe; all other mainframes in the complex can
access 7990 files and are called slave mainframes. SSEXEC runs on the master
mainframe and is the main processing program that controls MSE activity. SSSLV runs
on each slave mainframe and communicates with SSEXEC to retrieve files from 7990
in response to ATTACH requests by jobs running on the slave mainframes.

j^^S,

13-2 NOS Version 2 Analysis Handbook

Revision M

Deadstart

0m*.

Deadstart
A linked SDM environment is defined at deadstart by CMRDECK and EQPDECK
entries in each machine. Use the following entries to do this.
CMRDECK Entry

Description

MID=id.

2-character machine identification. This
identification is used to associate a specific machine
with its access to a shared device. It is required,
however, even if no devices are shared during
system operation. This id must be unique for each
machine in the complex. If id is omitted, the
default value is MID=AA.

EQPDECK Entry

Description

SHARE=esti ,est2,...,estn.

EST ordinals of the mass storage devices that will
be shared with other machines in the linked SDM
complex. The MST/TRT for each device resides in
extended memory.

PRESET,n.

Total number of devices to be shared by all
mainframes in the complex. You can specify this
entry only at the system console. You must specify
the PRESET entry on a level 0 deadstart on the
first machine to be deadstarted in the linked SDM
complex. This entry initializes the flag register and
extended memory resident tables. If n is omitted,
the default value is the number of shared devices
defined for the particular machine.

These entries are also described in section 3, Deadstart Decks.
Because in a linked SDM complex two or more machines can utilize the same mass
storage devices, the device assignments and EQPDECKs of all machines are
interrelated. Care must be taken to ensure proper EQPDECK settings for each machine
to obtain the desired device configuration. The following items are important in
obtaining this proper device configuration.
• Each machine must specify a unique machine identification (using the MID entry in
the CMRDECK). This identification associates a particular machine with its files on
a shared device. There are no external characteristics associated with this
identification. However, if the machine identification specified on a machine
deadstarting into a multimainframe complex is identical to a machine identification
on a machine already operating, the deadstart process halts and an appropriate
message is displayed.
• The assignment of shared mass storage devices should be made properly to ensure
the recoverability of the device and the proper operation of the system (refer to
Shared Mass Storage later in this section).
• If SHARE EQPDECK entries are present, an extended memory entry (DE or DP
equipment type) must also be present in the EQPDECK. If none is found, an error
message is given to the operator indicating that no link device has been defined.

Revision M

Multimainframe Operations 13-3

Deadstart

• The first machine deadstarted (level 0 only) must specify the PRESET EQPDECK
entry. This command causes tables to be preset in extended memory, and in so
doing, assures that no other machine has arrived at the same point in the
deadstart sequence and is attempting the same thing. These other machines
should not have the PRESET entry specified during deadstart. All other machines
that arrive at that point in the deadstart process display a message indicating
that they are waiting for deadstart on the preset machine. A machine that does
not preset extended memory has no means of detecting whether extended memory
has been preset previously by another machine. Therefore, the operator must
ensure that extended memory has been preset by a prior deadstart before
deadstarting another machine that is to be in the multimainframe complex.
• If extended memory is initially placed in maintenance mode (half of extended
memory used for online diagnostics), the first machine deadstarted in a complex
must have the INITIALIZE and PRESET EQPDECK entries specified when
deadstarting (level 0 only). The remaining machines must have the extended
memory size correspondingly reduced in their EQPDECKs.
When a mainframe joins a linked SDM complex, it is associated with an identification
that it utilizes during system operation but which is independent of the machine
identification. This association is done during deadstart, when the machine investigates
the multimainframe tables residing on the link device and places its machine
identification in an empty slot of the seven that are available. Associated with each
slot is a unique machine index and a unique machine mask, which the machine uses
either to index itself into various MMF tables or to identify itself in these tables.
When performing a level 0 recovery deadstart on one of the machines, the MREC
utility should be run on some or all of the remaining machines before the deadstart
proceeds. The purpose of this utility is to clear interlocks held by the machine to be
deadstarted that have not been cleared by CPUMTR. It can also recover mass storage
space on a shared device that is currently not accessible because of a machine
interruption (necessitating a level 0 deadstart). MREC may have to be run from more
than one machine since it affects only shared devices (that is, devices specified on the
SHARE EQPDECK entry) of the machine on which MREC is run. If the interrupted
machine shares different devices with different machines, MREC must be run from
enough machines to account for all devices shared with the interrupted machine. The
interface to the MREC utility is described in section 8, K-Display Utilities.
If a level 3 recovery deadstart will be performed, extended memory must be intact as
well as CMR. For a level 1 or 2 recovery in a linked SDM environment, extended
memory must be intact.
Figure 13-1 illustrates the steps generally needed to deadstart a machine in a
multimainframe complex.

13-4

NOS

Version

Analysis

Handbook

Revision

Deadstart

A LEVEL 0
DEADSTART
IS REQUIRED

DETERMINE THE
LEVEL OF RECOVERY
DEADSTART

LEVEL 1,
2. OR 3

LEVEL 0

RUN THE MREC UTILITY
ON THE NECESSARY
MACHINES

ENSURE THE PROPER
EQPDECK SETTING
FOR SHARE DEVICES

DETERMINE THE
TYPE OF MMF
ENVIRONMENT

INDEPENDENT
SDM

IS THIS
MACHINE SHARING'
A DEVICE THAT HAS
JOT BEEN PRESET?.

YES

ENTER. DURING DEADSTART.
THE PRESET EQPDECK ENTRY

PROCEED WITH THE
DEADSTART PROCESS

PROCEED WITH SYSTEM
OPERATIONS

Figure 13-1. Deadstarting a Machine in a Multimainframe Complex

Revision M

Multimainframe Operations 13-5

Shared Mass Storage

Shared Mass Storage
A major reason for operating a multimainframe complex is to be able to share mass
storage devices between machines. Thus, the users of two systems may be able to
utilize the same files if these files reside on a shared mass storage device. Having the
ability to share files between systems also means that several additional procedures are
required when operating a multimainframe complex. Additional consideration must also
be given when configuring mass storage devices. This material, which is unique to
multimainframe operation, is discussed in the following paragraphs.

Configuring Shared Mass Storage Devices
Some consideration should be given as to which devices should be made shared devices
and which ones should not. Since a shared device contains preserved files that can be
accessed by more than one machine, it must be physically connected to and logically
defined (as shared) by each machine sharing the device. If one device of a family is
defined as shared, then normally all devices in the family should be defined as shared
for accessibility. If a removable device will be treated as shared, it must be defined as
removable in each machine sharing it. If a shared device is not removable, additional
use of the device (beyond preserved files) is defined by each machine, independently of
any other machine definition (that is, each machine specifies whether the device is to
contain such things as a copy of the system or temporary files).
There is no real advantage to having nonpreserved files on a shared device, unless
spreading them across shared devices outweighs having them on a dedicated device. A
key factor is drive and controller contention. Another factor is whether or not enough
drives and accesses to those drives are available to warrant spreading temporary files ^^^
across several devices from all systems. Also, additional overhead is incurred by the *^)
system for each shared device. This includes additional CMR space for each device
(1008 CM words) and additional time that is required to maintain the device-related
tables (such as the MST or the TRT) on the link device. These factors must be
weighed to determine how best to configure shared devices.

Device Access Tables
In a linked SDM complex, mainframes use DATs to determine device usage. The DATs
identify the status of all shared and nonshared devices for the mainframes in the "^
complex. One DAT for each machine resides in extended memory.
In order to minimize configuration problems, shared removable equipment should be
configured the same way on all machines in the complex. For example, if one system
defines three shared units as three single-unit devices and another system defines the
same units as one three-unit device, the first system can accommodate a two-unit
device on these units, whereas the second system would consider it an error. Unless
the configurations are the same on all machines, any devices mounted on those drives
may not necessarily be recoverable on all machines.
NOTE
RESEX considers only the configuration of the machine on which it is executing in
its overcommitment algorithm.

13-6

NOS

Version

Analysis

Handbook

Revision

Mass Storage Recovery Tables

0im\

Mass Storage Recovery Tables
One problem that is created by having more than one machine sharing a mass storage
device is that of recovering the mass storage space and interlocks of a machine, if it
requires recovery processing. This problem is solved by defining a table that provides
the information needed to recover the mass storage space of a machine and by having
a machine recovery utility that performs the recovery. The table is called the mass
storage recovery table (MRT). There is one MRT for each mainframe per device. It tells
which tracks are interlocked and which tracks are first tracks of files local to a
particular machine. The MRT is utilized by CPUMTR on another machine to clear
track interlocks and by the MREC utility on another machine to recover the mass
storage space of the interrupted machine. For specific information on the MRT, refer to
the NOS Version 2 Systems Programmer's Instant.

Device Initialization
To initialize a mass storage device, it is necessary first to prevent any new activity
from starting up on the device, then to wait until all current activity has completed,
and finally to interlock the device and proceed with initialization. To accomplish this
on shared mass storage devices in a linked SDM environment, follow these steps:
1. Enter the DSD UNLOAD command. All machines sharing the device must unload
it to prevent any new activity. (This command can be used for both removable
and nonremovable shared devices.)
2. Enter the DSD INITIALIZE command on the machine from which the
initialization is to take place. If you enter the INITIALIZE command from another
machine, an error message is displayed. Refer to the NOS Version 2 Operations
Handbook for error messages.
3. The machine from which the INITIALIZE command was entered monitors the
status of the other machines that are sharing the device. Once they have unloaded
the device and user activity has ceased, the device tables are updated and the
device is checkpointed.
4. To activate the device on the other machines, enter the DSD MOUNT command
from each machine. This command clears the UNLOAD status. If initialization is
still in progress on another machine when you enter a MOUNT command, the
MOUNT process is terminated with an error. Refer to the NOS Version 2
Operations Handbook for error messages.

Revision

Multimainframe

Operations

13-7

Device Unload

Device Unload
In a linked SDM environment, unloading a device involves more than it does under a
one-machine system. A device can be unloaded from a machine (referred to as a local
unload), or it can be unloaded from the entire multimainframe complex (referred to as
a global unload). A device can be physically removed from the complex only after a
global unload has been accomplished. This is the general procedure to complete a
global unload:
1. Enter the UNLOAD command from each machine. This is an indication to the
machine that no new accesses should be initiated. You must enter this command
from each machine sharing the device.
2. When all local unloads are set and user access has ceased, global unload status is
set if the device is a removable device. This global unload status is displayed on
all machines, indicating that there is no activity on the device from any machine
and that the device may be physically unloaded.
3. You can then switch packs and enter the MOUNT command at the console to ^^
initiate recovery of the device. The MOUNT command clears the global unload
status and the local unload status on the machine from which it was entered and
indicates that this machine is now accessing the device. All other machines
continue to ignore the device until you enter the MOUNT command on each
machine. The MOUNT command does nothing if local unload status is not set on
the machine.

Device Recovery
Deadstart and online recovery methods are similar in logic for recovering mass storage
devices.
When a device is recovered in a linked SDM complex, the DAT in extended memory
is interlocked while a check is made to see if an entry exists for this device. The
presence of an entry indicates that another machine is also accessing the device. If
an entry is found and the machine recovering the device has not been instructed to
share it, an error is indicated and recovery halts with an appropriate message
displayed. If the machine already accessing the device is not allowing it to be shared, ^^
the same error condition occurs. Therefore, if a device is being accessed, another '^^S
machine can recover that device only if the recovering machine and the accessing
machine use the device in a multimainframe mode.
NOTE
If two devices recovered on separate machines have the same family name/device
number or pack name, there is no method of determining whether or not they are the
same device if both are shared. If they are different devices, they are both destroyed
when used.

13-8

NOS

Version

Analysis

Handbook

Revision

Device Checkpoint

Device Checkpoint
Local MST information for each machine that shares a mass storage device is
maintained on the device. MST information for other machines may also be present on
the device. The information for each machine is kept in one sector on the label track
following the TRT sectors. Entries for up to 31 unique machine identifiers can exist.
During checkpoint, only the local MST information of the machine performing the
checkpoint is updated. Since local MST information for many machines is kept on the
device, updating of all these areas by one machine could cause a loss of information
needed if the device were to be used with another system.
For shared devices in a linked SDM complex, duplication of checkpointing by more
than one machine is prevented. If a machine attempts to checkpoint a shared device
and determines that a second machine is performing the checkpoint (a checkpoint
request bit is set in the local MST area of the second machine), no action is taken.
Only one checkpoint bit is set at any given time for a device.

MSE Processing
Unlike most other mass storage devices, the 7990 is not shared by mainframes. Rather,
7990 is physically connected to and driven by one mainframe called the master
mainframe. All other mainframes that share permanent files with the master
mainframe are called slave mainframes. The disks to which 7990-resident files are
staged must be shared devices and accessible by all mainframes.
/^•N

SSEXEC runs on the master mainframe and is the main program that controls MSE
processing activities. You can activate SSEXEC by entering the following DSD
commands at the system console.
L.SUBSYST.
ENABLE,MASTER MSE.
L.END.
MSEffff.

0Bto\

SSSLV runs on each slave mainframe and is the program that supports file retrieval
from a 7990 for jobs running on a slave mainframe. You can activate SSSLV by
entering the following DSD commands at the system console.
L.SUBSYST.
DISABLE,MASTER MSE.
L.END.
MSEffff.

When a job running on a slave mainframe attaches a 7990-resident file that has no
disk image, SSSLV is requested to stage the file to disk. However, SSSLV cannot access
7990 directly. SSSLV must communicate with SSEXEC, which stages the file to a
shared disk and then notifies SSSLV when the file is available. SSSLV then causes the
requesting job to be resumed so that the file ATTACH can complete.
The permanent files used for communication between SSEXEC and SSSLV are
initialized and recovered automatically and require no backup or recovery processing.
The name of the permanent file used by SSSLV running on mainframe i (i = l, 2, 3,
4) to send requests to SSEXEC is STBMNOi. The name of the permanent file used by
SSEXEC to respond to all requests by all SSSLVs is MTBSPFN. These files belong to
the family that contains extended memory and are saved under the user index
3777608.

Revision

Multimainframe

Operations

13-9

Independent SDM Operation
J,*^%v

Independent SDM Operation
In an independent SDM complex, up to 16 computers can access shared mass storage
devices. Any combination of from 1 to 16 model 71, 72, 73, 74, 171, 172, 173, 174, 175,
176, 720, 730, 740, 750, 760, 865, 875, CYBER 180-class machines, or 6000 Computer
Systems mainframes can be used. Shared mass storage devices supported are 844
(single and double density) and 885-11/12 (single and double density).
Each shared device contains in its label track all of the tables necessary to control
multimainframe access. These tables include the MST, TRT, device index table (DIT),
and MRT for each mainframe sharing the device. Whenever a mainframe needs to
access a shared device, it is necessary for the mainframe to ensure its copies of these
tables are up-to-date.
One or more of the mainframes can have extended memory, but each mainframe's
extended memory must be used as a nonshared device.
If MSE is used, one mainframe in the independent SDM complex is physically ^^^
connected to 7990 and only that mainframe can access it. 1

Deadstart
An independent SDM environment is defined at deadstart by CMRDECK and
EQPDECK entries in each machine. Use the following entries to do this.
CMRDECK

Entry

Description

M I D = i d . 2 - c h a r a c t e r m a c h i n e i d e n t i fi c a t i o n . T h i s
identification is used to associate a specific
machine with its access to a shared device. It is
required, however, even if no devices are shared
during system operation. This id must be unique
for each machine in the complex. If id is omitted,
the default value is MID=AA.
EQPDECK

Entry

Description

ISHARE = esti,est2,...,estn. EST ordinals of the mass storage devices that will ^^)
be independently shared with other machines in
the multimainframe complex. The ISHARE entry
must precede the PRESET entry. The MST/TRT
resides on each shared device.
PRESET=esti,est2,...,estn. EST ordinal of the shared mass storage device to
be preset. You can specify this entry only at the
system console. Several machines at level 0
deadstart may need the PRESET entry. The
PRESET entry is specified only on a level 0
deadstart by the first machine accessing the device
and must follow the ISHARE entry. PRESET
initializes the tables residing on the label track of
the shared devices.
These entries are also described in section 3, Deadstart Decks.

13-10

NOS

Version

Analysis

Handbook

Revision

Deadstart

Since in an independent SDM complex two or more machines can utilize the same
interrelated.
must assignments
be taken to ensure
EQPDECK
for eachare
machine
rmass storage devices,
theCare
device
and proper
EQPDECKs
of settings
all machines
to obtain the desired device configuration. The following items are important in
obtaining this proper device configuration.
• Each machine must specify a unique machine identification (using the MID entry
in the CMRDECK). This identification associates a particular machine with its
files on a shared device. There are no external characteristics associated with this
identification. However, if the machine identification specified on a machine
deadstarting into a multimainframe complex is identical to a machine
identification on a machine already operating, the deadstart process halts and an
appropriate message is displayed.
• The assignment of shared mass storage devices should be made properly to ensure
the recoverability of the device and the proper operation of the system (refer to
Shared Mass Storage, next).
Each machine must specify the ISHARE=est EQPDECK entry to inform the
system that devices will be shared in the independent shared device mode.
If you need to deadstart an interrupted mainframe in an independent SDM
environment, you should put the nonfailing mainframes in STEP mode before
deadstarting the interrupted mainframe.
•

On a level 0 deadstart, any shared device that has not been shared prior to this
deadstart must include the PRESET entry in its definition.
On a level 0 deadstart, if a device was previously shared by the deadstarting
machine, the MRT and DIT device resident tables must be zeroed out.
- If the machines that share the device are not currently running, the device
must be preset or initialized to zero out the tables.
- If any machine that shares the device is running, the machine recovery utility
(MREC) must be run from a running machine to remove the machine
identification of any machines that are not currently running and to clear all
interlocks held by these machines.
On a level 0 deadstart, if a device was previously shared by a machine other than
the deadstarting machine, the MRT and DIT device resident tables may or may
not have to be zeroed out.
- If another machine that is sharing the device is running, the device must not
be preset.
- If no machines that will be sharing the device are running and one or more of
them will be deadstarted at a level 1, 2, or 3, the device must not be preset.
- If all machines that will be sharing the device are not currently running and
all will be deadstarted at level 0, the device can be preset or initialized.

Revision

Multimainframe

Operations

1 3 - 11

Shared Mass Storage

When performing a level 0 recovery deadstart on one of the machines, the MREC
utility should be run on some or all of the remaining machines before the deadstart
proceeds. The purpose of this utility is to clear interlocks held by the machine to be
deadstarted that have not been cleared by CPUMTR. It can also recover mass storage
space on a shared device that is currently not accessible because of a machine
interruption (necessitating a level 0 deadstart). MREC may have to be run from more
than one machine since it affects only shared devices (that is, devices specified on the
ISHARE EQPDECK entry) of the machine on which MREC is run. If the interrupted
machine shares different devices with different machines, MREC must be run from
enough machines to account for all devices shared with the interrupted machine. The
interface to the MREC utility is described in section 8, K-Display Utilities.
In an independent SDM complex, as in a standalone system, critical tables that reside
on the device must be intact for a level 1, 2, or 3 deadstart recovery.
Figure 13-1 illustrates the steps generally needed to deadstart a machine in a
multimainframe complex.

/^at^y

13-12

NOS

Version

Analysis

Handbook

Revision

Configuring Shared Mass Storage Devices

Configuring Shared Mass Storage Devices
Some consideration should be given as to which devices should be made shared devices
and which ones should not. Since a shared device contains preserved files that can be
accessed by more than one machine, it must be physically connected to and logically
defined (as shared) by each machine sharing the device. If one device of a family is
defined as shared, then normally all devices in the family should be defined as shared
for accessibility. If a removable device will be treated as shared, it must be defined as
removable in each machine sharing it. If a shared device is not removable, additional
use of the device (beyond preserved files) is defined by each machine, independently of
any other machine definition (that is, each machine specifies whether the device is to
contain such things as a copy of the system or temporary files).
There is no real advantage to having nonpreserved files on a shared device, unless
spreading them across shared devices outweighs having them on a dedicated device. A
key factor is drive and controller contention. Another factor is whether or not enough
drives and accesses to those drives are available to warrant spreading temporary files
across several devices from all systems. Also, additional overhead is incurred by the
system for each shared device. This includes additional CMR space for each device
(1008 CM words) and additional time that is required to maintain the device-related
tables (such as the MST or the TRT) on the link device. These factors must be
weighed to determine how best to configure shared devices.
In an independent SDM complex, where device-related tables are maintained on the
device itself, system performance degradation can occur if the shared devices are not
properly configured. Since the device must be accessed every time its tables in CMR
are not up to date, drive and controller contention is increased and system
performance is affected. To reduce the impact on system performance you can:
• Put the system and temporary files on nonshared devices.
• Put only those fast-attach files that must be global on shared devices.
• Use multiple channels and multiple controllers to improve performance and
provide additional paths to shared devices.

Revision

Multimainframe

Operations

13-13

Device Index Tables

Device Index Tables
In an independent SDM complex, mainframes use DITs to determine device usage. The
DITs contain the MIDs of the mainframes that can access the shared device. The
shared device maintains a DIT for each mainframe that shares it. The DITs reside on
each shared device within the MST on the device's label track.

Mass Storage Recovery Tables
One problem that is created by having more than one machine sharing a mass storage
device is that of recovering the mass storage space and interlocks of a machine, if it
requires recovery processing. This problem is solved by defining a table that provides
the information needed to recover the mass storage space of a machine and by having
a machine recovery utility that performs the recovery. The table is called the MRT.
There is one MRT for each mainframe per device. It tells which tracks are interlocked
and which tracks are first tracks of files local to a particular machine. The MRT is
utilized by CPUMTR on another machine to clear track interlocks and by the MREC
utility on another machine to recover the mass storage space of the interrupted ■/*ss\
machine. For specific information on the MRT, refer to trie NOS Version 2 Systems
Programmer's Instant.

1. Enter the DSD UNLOAD command. All machines sharing the device must unload
it to prevent any new activity. (This command can be used for both removable
and nonremovable shared devices.)
2. Enter the DSD INITIALIZE command on the machine from which the
initialization is to take place. Each entry of the INITIALIZE command toggles
INITIALIZE on and off. If two machines in the complex enter the INITIALIZE
command, the INITIALIZE command is toggled off and no error message is /*=%,
displayed.
'

3. The machine from which the INITIALIZE command was entered monitors the
status of the other machines that are sharing the device. Once they have unloaded
the device and user activity has ceased, the device tables are updated.
4. To activate the device on the other machines, enter the DSD MOUNT command
from each machine. This command clears the UNLOAD status. If initialization is
still in progress on another machine when you enter a MOUNT command, the
machine waits for INITIALIZE to finish and then continues with the MOUNT
process.

13-14

NOS

Version

Analysis

Handbook

Revision

Device Unload

Device Unload
In an independent SDM environment, unloading a device involves more than it does
under a one-machine system. A device can be unloaded from a machine (referred to as
a local unload), or it can be unloaded from the entire multimainframe complex
(referred to as a global unload). A device can be physically removed from the complex
only after a global unload has been accomplished. This is the general procedure to
complete a global unload:
1. Enter the UNLOAD command from each machine. This is an indication to the
machine that no new accesses should be initiated. You must enter this command
from each machine sharing the device.
2. When all local unloads are set and user access has ceased, global unload status is
set if the device is a removable device. This global unload status is displayed on
all machines, indicating that there is no activity on the device from any machine
and that the device may be physically unloaded.
3. You can then switch packs and enter the MOUNT command at the console to
initiate recovery of the device. The MOUNT command clears the global unload
status and the local unload status on the machine from which it was entered and
indicates that this machine is now accessing the device. All other machines
continue to ignore the device until you enter the MOUNT command on each
machine. The MOUNT command does nothing if local unload status is not set on
the machine.
4. A pack that has not been previously mounted in this system must be preset with
a MOUNT,est,P command.

Device Recovery
Deadstart and online recovery methods are similar in logic for recovering mass storage
devices.
For a machine to recover a device in an independent SDM complex, the MID of the
machine must be in the device's DIT. If the MID is not in the DIT, an error message
is issued and recovery is impossible. When recovering a device in a standalone
environment, the device is not checked if it is/was an independent shared device.

Revision

Multimainframe

Operations

13-15

Device Checkpoint

Device Checkpoint
Local MST information for each machine that shares a mass storage device is
maintained on the device. MST information for other machines may also be present on
the device. The information for each machine is kept in one sector on the label track
following the TRT sectors. Entries for up to 31 unique machine identifiers can exist.
During checkpoint, only the local MST information of the machine performing the
checkpoint is updated. Since local MST information for many machines is kept on the
device, updating of all these areas by one machine could cause a loss of information
needed if the device were to be used with another system.
In an independent SDM complex, the MST and TRT information is maintained on the
device. If the MST and/or TRT information changes during a device access, the
system updates the MST and/or TRT information making it unnecessary for the
system to periodically checkpoint the device.

MSE Processing
Unlike most other mass storage devices, the 7990 is not shared by mainframes. Rather,
7990 is physically connected to and driven by one mainframe. The only machine that
can access the 7990-resident files is the physically connected independent SDM. MSE
processing is the same in an independent SDM environment as it is in a single
mainframe environment. Refer to section 11, Mass Storage Extended Subsystem.

13-16 NOS Version 2 Analysis Handbook

Revision M

NAD Maintenance Utilities 14
Dump

NAD

Memory

Maintenance

Host

Listing

NAD

(DMPNAD)

Facility

(MHF)

Dumps

14«1
14-3
I4.3

v..

NAD Maintenance Utilities

This section describes utilities that are used to maintain network access devices
(NADs).

Dump NAD Memory (DMPNAD)
DMPNAD is a utility program that uses data obtained either directly from NAD
memory or from a binary dump file (produced previously by MHF or DMPNAD) to
generate a print file showing each NAD word in both hexadecimal and 7-bit ASCII
code.
The format of the DMPNAD command is:
DMPNAD,plfp2 pn.

Pi is a parameter consisting of a keyword or a keyword equated to a value. All
parameters are order independent.
Description

AC = aaaa The 4-digit hexadecimal number specifying the remote NAD's access code
(refer to the RHF K display in section 8, K-Display Utilities). The
default is AC = 0000.
B=binfile The 1- to 7-character name of the file on which the binary output is to
be written. The default is no binary output file.
B

Same

B = B I N O U T.

CH = ch The 1- or 2-digit octal number specifying the channel number of the
local NAD (defined in the NAD's EST entry).
I = infile The 1- to 7-character name of the file containing binary input data.
DMPNAD dumps only one record from the file. The default is no binary
input file.
I Same as I = BININ.
L=outfile The 1- to 7-character name of the file on which the list output is to be
written. The default is L=OUTPUT.
LT=totit2t3 The 4-digit binary bit pattern specifying the TCUs that connect a local
NAD to a remote NAD. tn = l enables TCUn. For example, LT=1100
indicates that local TCUs 0 and 1 are enabled.
ND=nn The 2-digit hexadecimal number specifying the remote NAD's address
(refer to the RHF K display in section 8, K-Display Utilities).

0$^S^

Revision M

NAD Maintenance Utilities 14-1

Dump NAD Memory (DMPNAD)

The DMPNAD utility can be called from the console or a batch job. The calling job
must be of system origin or you must be validated for system origin privileges. You ^\
normally include the channel number on the DMPNAD command to specify which local
NAD is to be dumped. The dump can also be saved as a binary output file (B
parameter) which can be listed later.
DMPNAD can dump either a local NAD (380-170 NAD connected to the host
mainframe using a channel and configured in the EST) or a remote NAD (any 380
NAD accessible to a local NAD using a loosely-coupled network trunk). For a local
NAD dump, the EST entry associated with the local NAD's channel number must be
OFF or the controlware-not-loaded flag must be set. Since the local NAD dumping
process stops all NAD activity, the NAD controlware must be reloaded using
LOADBC (refer to section 1, Controlware Utilities) before the local NAD can be used
by the operating system.
Remote NAD dumping is selected by specifying the remote NAD to be dumped (AC
and ND parameters), the local NAD's channel number used to access the remote
NAD (CH parameter), and the TCU used to connect the local NAD to the remote ^~
NAD (LT parameter). For remote NAD dumping, the local NAD must be loaded and 1
running and its EST entry must be ON.
Remote NAD dumping operations can occur concurrently with RHF use of the local
NAD. However, extreme care should be exercised when performing a remote NAD
dump to ensure that the correct remote NAD is being dumped and that the remote
NAD is not being used by the mainframe to which it is connected. After the remote
NAD dumping operation, the NAD controlware must be reloaded into the remote
NAD before it can be used by the remote mainframe.
When the I parameter is specified, DMPNAD will list a binary file that was saved
earlier. Since no NAD access is required, no special privileges are required by the
calling job.

14-2

NOS

Version

Analysis

Handbook

Revision

Maintenance Host Facility (MHF)

yams

Maintenance Host Facility (MHF)
™i" is a utilitv Program that executes while RHF is active. MHF periodically copies
t>£t?
•er-1.r l0gS
the binary
loads
microcode
local
NADsofduring
RHF initiation,
andtodumps
andmaintenance
reloads localkg.
NADs
that
fail. MHFinto
uses
a copy
the
network description table obtained directly from RHF to determine which NADs to loe
dump,
and/or
load.
6'
You control MHF operation by setting the AUTOLOAD, AUTODUMP TRACE and
LOG parameters in the LNAD and RNAD directives for RCFGEN, which generates
the RHF configuration file (refer to section 10, LID/RHF Configuration Files) You
can control the remote NAD LOG parameter on RHF's network path table display
(refer to section 8, K-Display Utilities). If you specify AUTODUMP = YES for local
S^5.^?J
dumPs
as Celled
records
on permanent
ND* Mid -SaVeS
(id is theNA°
hostmemory
mainframe
identifier)
underbinary
user name
SYSTEMX
Each file
record label contains the record name NDMPLch (ch is the NAD's channel number)
record number, and the date and time of the dump. MHF puts this dump information
in the following sequence of job dayfile messages:
MHF, NAD DUMP RECORD NAME = NDMPLch
MHF, RECORD NO.0000 TIME = hh.nm.ss
MHF, FILE = NDFMid DATE = yy/mn/dd

When loading a local NAD, MHF obtains the controlware from the system and uses a
default set of controlware initialization parameters that it adjusts to suit the NAD's
memory size.

Listing NAD Dumps
To list a NAD dump, you must be validated to obtain access to the NAD dump
permanent file NDFMid (id is the host mainframe identifier).
You can either use ITEMIZE to locate a particular record on permanent file NDFMid
or obtain the record number from MHF's dayfile, and then use DMPNAD to list the
dump record. (ITEMIZE shows the record name, record number, date, and time
corresponding to MHF's dayfile messages.)
The following example lists dump record 4 of permanent file NDFM64:
ATTACH,NDFM64/UN=SYSTEMX.

ITEMIZE,NDFM64. Check ITEMIZE output for the record number
SKIPR,NDFM64.3. Skip to the fourth record.
dmpnad,i=ndfm64,l=list. List the fourth record on file LIST.
RETURN,NDFM64..

A0$S,

Revision

NAD

Maintenance

Utilities

14-3

f^)

Network

Operations

Network

Organization

15
15.1

NAM
Startup
X5.5
Initiating NAM Without Operator Intervention 15.5
Altering
the
Memory
File
15_6
NAM

f**

^ v

Shutdown

15.3

Network
Control
by
HOP
15.9
Disabling
and
Enabling
of
Couplers
15-9
Status
Message
Formats
for
HOP
15-9
Unsolicited
Status
Reports
for
HOP
15-10
HOP
Commands
1 5 - 11
NS
Control
Commands
1 5 - 11
C a n c e l A l t e r n a t e N P U L o a d F i l e C o m m a n d . . 1 5 - 11
Change
NPU
Load
File
Command
15-12
NPU
Load
Status
Command
-15-12
S p e c i fi c
NPU
15-12
All
NPUs
15-13
Status
Response
15-13
NS
Recent
HISTORY
Command
15-14
NVF
Control
Commands
15-15
Disable
Host
Element
Command
,
15-15
Enable
Application
Command
15-16
Idle
Host
Element
Command
15-16
NVF
Recent
HISTORY
Command
15-18
Status
Host
Element
Command
15-18
Particular
Host
Element
..
15-18
Network
Applications
15-19
Active
Network
Applications
15-19
Te r m i n a l
Devices
15-19
Users
( S p e c i fi e d
Application)
15-20
Network
Control
by
NOP
..
Becoming
a
NOP
."
Status
Message
Formats
for
NOP
Unsolicited
Status
Reports
for
NOP
NOP
Commands
ALERT
Command
CONTROL
Command
Disable
Network
Element
Command
Single
Element
Trunk
...
SVCs
DISABLE
Processing
Enable
Network
Element
Command
Single
Element
Trunk
Disabled
Elements
Disabled
Elements
(All
NPUs)
Disabled
Te r m i n a l s
SVCs

ENABLE
NPU

Processing
Command

15-21
15-21
15-23
15-25
15-26
15-26
15-27
15-29
15-29
15-30
15-31
15-31
15-33
15-33
15-34
15-34
15-35
15-35

15-36

15-36
15-37

NPU
LOAD
Command
....
....
S p e c i fi e d
NPU
..
All NPUs ....,.............................;.............
NPU
Memory
DUMP
Command
,
S p e c i fi e d
NPU
All
NPUs
Send
Message
Command
.....

15-38
15-38
15-39
15-40
15-40
15-40
15-41

Network
Control
by
D O P.
*
Becoming
a
DOP
...
Status
Message
Formats
for
DOP
Unsolicited Status Reports for DOP .-.....-...
DOP
Commands
,
,
CS
Information
Command
NPU
Diagnostic
Te s t
Command
.......
TST
Drop
Option..
TST
Message
Option
•
•
•
. - .■>
TST
Request
Option
,

15-43
15-43
15-45
15-48
15-48
15-48
15-50
15-50
15-51
15-51

Recent

HISTORY

15-52

Report

Unsolicited

Send

Message

Command
Status
Command

Command
•

•

15-53

•

15-54

Status
Network
Element
Command
Particular
Element
..-...
All
Elements
Te r m i n a l
Devices
NPUs
SVCs

15-55
15-55
15-56
15-57
15-57
15-58

Summary of Network Operation Commands ..—
Control
Commands
for
HOP
NAM
K
Display
NAM
Startup
NAM
Shutdown
NAM
Mode
Commands
NS
Control
Commands
.........
NVF
Control
Commands
Control
Commands
for
HOP
and
NOP
C o n t r o l C o m m a n d s f o r H O P, N O P, a n d D O P
Control
Commands
for
COP
.

15-59
15-59
15-59
15-59
15-59
15-60
15-61
15-61
15-62
15-62
15-62

Network

Operations

^^_^

The commands described in this section are used when the network access method
(NAM) is being initialized or is active. They initialize and control the network
processing units (NPUs), device interfaces (DIs), trunks, lines, terminals, and
application programs under network supervision.
NAM supports two types of networks: the 255x NPU network and the CDCNET
network. Throughout this section, the term network refers to the 255x NPU network.
However, whenever a statement is applicable to both network types, both types are
named explicitly.
NAM controls the CDCNET network by sending commands to an application called
Network Operator Utility (NETOU). This NAM application is also known as the
network operations server. For further information on controlling the CDCNET
network, refer to the CDCNET Network Operations Manual and the CDCNET
Network Analysis Manual.

Network Organization
Initiating NAM (refer to the DSD NAM command in section 5, DSD Commands) causes
NAM, and the communications supervisor (CS), network supervisor (NS), network
validation facility (NVF), and terminal verification facility (TVF) to be loaded and
initiated at control points. Refer to the NAM/CCP 3 Terminal Interfaces Reference
Manual for more information on TVF. CS provides control and status of the NPUs and
all of their communication lines and terminals. NS loads and dumps all of the NPUs
in the communication network. NVF validates terminal users and applications, as they
attempt to access the network.
Multiple hosts may belong to the network. Hosts may assume one or more
supervisory roles in the network. Each host will have a copy of NVF that will
validate users connecting to and applications executing in that host. NVF provides
these services for both the 255x NPU network and the CDCNET network. The
supervisors CS and NS may execute in any or all of the CYBER hosts. Whenever an
NPU needs to be loaded, it may request any copy of NS to perform the load (not
always the same copy). Once an NPU is running, it may request any copy of CS to
supervise it. Each NPU will have a preferred copy of CS, but it may request
supervision from an alternate copy of CS if its preferred CS is not available. In any
case, the network is always capable of functioning without any one or more of its
hosts.

yzms.

Revision

Network

Operations

15-1

Network Organization

Whenever a CDCNET mainframe device interface (MDI) or mainframe terminal
interface (MTI) must be loaded, it requests the services of a CDCNET job called
INITMDI, which is responsible for loading and dumping the MDIs and MTIs. NAM
automatically starts INITMDI upon demand.
Whenever a terminal device interface (TDI) or a network device interface (NDI) must
be loaded, the MDI helping in the load process establishes a connection through NAM
to the NAM application called the Network File Server (NETFS), which controls the
loading and dumping of TDIs and NDIs.
The 255x NPU network consists of channels, couplers, lines, logical links, NPUs,
terminals, and trunks (refer to figure 15-1) connected to the host computer.
• A channel is a data path on which a peripheral device controller can be accessed.
• A coupler is a hardware element that links an NPU to a channel.
• A line is the circuit that connects a terminal to an NPU.
• A logical link is a logical path connecting a coupler and an NPU or two couplers.
• An NPU is the communications controller that transmits data between terminals
and a host computer or between two host computers.
• A public data network is an X.25 packet switching network (PSN). Terminals,
NPUs, and foreign hosts can be connected to a PSN to exchange data.
• A terminal is a device by which a user supplies input messages to, and accepts
output messages from, an application program.
• A trunk is the communication line connecting two NPUs.
The CDCNET network consists of channels, couplers, lines, logical links, device
interfaces (MDIs/MTIs/NDIs/TDIs), terminals, and trunks. For definitions of CDCNET
terminology, refer to the CDCNET Conceptual Overview Manual.

.«*SJ!Sy

15-2 NOS Version 2 Analysis Handbook

Revision M

Network Organization

r~s

ill
zJu ffm xs

a.
O

0 ^ 1
j cc

o ui a

2£5
ft.
•o

0^S

Figure 15-1. Sample 255x NPU Network

Revision M

Network Operations 15-3

Network Organization

Network host products (NHP) is the network software residing on the CYBER host.
NHP recognizes four types of network operators: the host operator, the NPU operator,
the diagnostic operator, and the CDCNET operator. A host operator (HOP) resides at
the system console, initiates NAM, and can control 255x NPU network and CDCNET
network elements being supervised by this host. An NPU operator (NOP) resides at a
terminal and controls 255x NPU network elements (such as lines, logical links, NPUs,
terminals, and trunks). A diagnostic operator (DOP) resides at a terminal and monitors
and tests communication lines on the 255x NPU network.
A CDCNET operator (COP) resides at either the system console or a terminal and
controls CDCNET network elements (such as lines, terminals, trunks, and DIs
associated with CDCNET).
The HOP can always perform COP, NOP, and DOP functions regardless of the
existence of COPs, NOPs, and DOPs. NOPs can perform all DOP functions regardless
of the existence of DOPs. CS supports up to 10 concurrent NOP and DOP connections
in addition to one HOP connection. NS and NVF support only the HOP connection.
The HOP can communicate with NAM and any of the supervisors (CS, NS, NETOU,
or NVF) executing in its host. COPs can communicate only with NETOU. Refer to
the CDCNET Network Operations Manual for additional information. NOPs and DOPs
can communicate with any CS executing in any host to which the operator has
access. However, a NOP or DOP can communicate with only one CS at a time. A
NOP or DOP can monitor and control only those elements owned by NPUs being
supervised by their CS.
Each NPU in the network is controlled by the HOP and, optionally, one NOP
connected to its supervising CS. A HOP controls all NPUs supervised by CS. Each
NOP connected to CS can control one or more NPUs.

15-4 NOS Version 2 Analysis Handbook

Revision M

NAM Startup

0m\

NAM Startup
If the NPUs in the network were running version 3.5 or earlier Communications
Control Program (CCP), you must master clear all local NPUs before initiating NAM.
If the NPUs were running version 3.6 or 3.7 of CCP, then master clear NPUs only if
the running version is not the desired version.
You initiate NAM by entering:
NAM.

or
NAMNOGO.

NAM1 and NAMNOGO are names of procedure files that are called when the HOP
initiates NAM.
The first time the network is initiated the NAMNOGO procedure must be used to
create a memory file (refer to the NOS Version 2 Installation Handbook). The
memory file contains the name of the master file, the last parameter record, and the
network invocation number (NIN) used. The NIN is incremented by 1 every time
NAM is started. The NIN is displayed in the NAM K display. If the network has
been previously initiated, a memory file exists and the NAM procedure file may be
used.

Initiating NAM Without Operator Intervention
If you initiate NAM by entering
NAM.
o

NAM is brought up without further operator action. This results in starting the
network using the previously specified master file and the parameter record RESTRT.

1. Any procedure file of the form NAMffff is allowed.
2. Any procedure file of the form NAMffff is allowed.

Revision

Network

Operations

15-5

Altering the Memory File

Altering the Memory File
If you initiate NAM by entering
NAMNOGO.

NAM displays the message:
ENTER DESIRED OPTION

You reply to this message with a CFO command in this format:
CFO,NAM.Pi,p2,...Pn.

pi is a parameter consisting of a keyword equated to a value. All parameters are order
independent.
Pi

Description

MFN=filename

Permanent file name of the master file to be used. The master
file contains all the information needed to initiate the network.
Once this parameter is specified all subsequent network
initiations use this master file until a new master file is
specified. The master file resides in the system default family
and must be permitted to SYSTEMX. If this parameter is not
specified, NAMSTRT is assumed. Refer to NAM Procedure File
in the NOS Version 2 Installation Handbook for further
information about file NAMSTRT.

UN = username

User name for the master file. If this parameter is not specified,
NETOPS is assumed.

PW=password

Password associated with the master file user name.

-*mcy^.

15-6 NOS Version 2 Analysis Handbook

Revision M

Altering the Memory File

Description

RN = recordname3 Name of the parameter record on the master file that is used
for this network initiation. If this parameter is not specified, the
previously specified parameter record is used. The parameter
record specifies the characteristics of any particular network
initiation.
You can select one of the parameter record names listed in
table 15-1 to obtain the given combination of features.
OIN=xx Previous network invocation number. All network dump and
trace files with a network invocation number less than or equal
to the value specified by the OIN parameter are collected. If this
parameter is not specified, the current network invocation
number minus 1 is used.
You can enter all desired parameters with a single entry or enter several CFO
commands. In this way you add (if the file is empty) or replace entries in the NAM
memory file.
When you have finished adding or replacing data, enter the command:
CFO,NAM.GO.

After entering this command, you cannot add or replace additional parameters during
this NAM initiation.
Table 15-1. Parameter Record Feature Descriptions
F e a t u r e D e s c r i p t i o n s I N I T R E S T RT R E C O V R M U LT I M I N I T M R E C O V
This
feature
dumps/traces on tape
before startup

collects

This
feature
NPUs at startup.

stops

local

^■ T N
h iPs U fse a ut u
oa
ca
p ro en s at ob pn so r lm
l l
NHP termination.
This
feature
dumps before initial
load.4

takes

NPU

NNN

1. N indicates that the parameter record name causes the action not to occur.
2. Y indicates that the parameter record name causes the action to occur.
3. Dumps/traces are collected for NHP, 255x NPU, and CDCNET whenever present.
4. This feature has no effect on MDIs and MTIs.

3. Specifying a record name changes recordname only for this initiation.

Revision

Network

Operations

15-7

NAM Shutdown

NAM Shutdown
NAM is idled by assigning the K display to the application NVF, followed by entering
the DISABLE,HOST or IDLE,HOST command.
The sequence of commands is:
K.AP=NVF.
K. DISABLE,HOST.
or
K.IDLE,HOST.

Use the IDLE command for a graceful shutdown, and the DISABLE command for an
immediate shutdown.

15-8

NOS

Version

Analysis

Handbook

Revision

Network Control by HOP

^psv

Network Control by HOP
The commands described next are available only to the HOP. The HOP can perform all
functions of the NPU operator, CDCNET operator, and diagnostic operator as well as
those unique to the HOP. The commands unique to the HOP are processed by NS and
NVF.

Disabling and Enabling of Couplers

The HOP enables either an NPU or MDI/MTI coupler using the DSD ON command
and disables the coupler using the DSD OFF command. You can examine the NP
equipment entry on the E,A display to determine the EST ordinal. When an active
coupler is turned OFF, NAM stops communicating with that coupler. The coupler is not
used again until it is turned ON while NAM is executing. When a coupler is turned
ON, NAM automatically begins to communicate with the NPU or MDI/MTI connected
across the coupler.

Status Message Formats for HOP
The HOP commands cause various status messages to be displayed at the system
console. The normal response to a STATUS command consists of a single status line for
each referenced element.
Following are the general formats for these status messages.
Message

0ms

Type

Format

Application status line

APPL: name,status,conncount.mxcopies,jsn,restart.

Terminal status line

TERM: name,username,hh.mm.ss,app1name/acn,ah.am.as,dt

User status line

USER: name,termname,hh.mm.ss,app1name/acn,ah.am.as,dt

In the preceding status message general formats the following variables are used.
Va r i a b l e D e s c r i p t i o n
acn Connection number for the connected application.
ah.am.as Time of the connection to the application (hours, minutes, and seconds).
applname Name of the connected application.
conncount Count of the active connections to this application.
dt

Device

type.

hh.mm.ss Time of the system or host login (hours, minutes, and seconds).
jsn Job sequence name of the application.
mxcopies Maximum number of copies of this application that can be running at
one time.

0Z3S.

Revision M

Network Operations 15-9

Unsolicited Status Reports for HOP
yrt^^.

Va r i a b l e D e s c r i p t i o n
name

Name of the specified element.

restart

If the characters RS are present, they indicate that NVF will
automatically start up a copy of this application to complete a
connection request for it.

status

Status of the application. The application program is initially set to
either an enabled or disabled state. Enabled application programs
become active when they start executing. The application program is in
one of these states:
status

Description

Application is active (you can establish a connection to the
application).

Application is disabled.

Application is down (the application failed; NAM tables are
being cleared up).

Application is enabled.

termname

Name of the terminal at which the user resides.

username

Unsolicited Status Reports for HOP
Each time a significant event occurs, CS, NS, or NVF updates its recent history buffer
(refer to Recent HISTORY Command later in this section) and logs the event in the
NAM dayfile. CS, NS, or NVF then sends a report about the event, called the
unsolicited status report, to the HOP. The HOP can get unsolicited status reports from
CS, NS, or NVF by assigning the NAM K display to that particular application. Refer
to section 8, K-Display Utilities, for information on how to assign the NAM K display.
Unsolicited status reports are time-stamped whereas solicited status reports are not
time-stamped.
If an unsolicited status report is important enough to require alerting the operator or
system analyst, NS, CS, or NVF will display its application name on the alert line of
the NAM K-display unless the NAM K-display is already assigned to that application.
The operator or system analyst should then assign the NAM K-display to the
application and follow the procedures indicated in the NOS Version 2 Operations
Handbook for the appropriate alert message.
Refer to the CDCNET Network Operations Manual for NETOU's treatment of
unsolicited information for the CDCNET operator.

15-10 NOS Version 2 Analysis Handbook

Revision M

HOP Commands

HOP Commands
The HOP must assign the NAM K display to a supervisory application (CS, NS, or
NVF) before entering any of the following commands. Refer to section 8, K-Display
Utilities, for information on how to assign the NAM K display. CS, NS, and NVF
support both the right and left K-displays. The right K-display provides help
information.
All HOP commands consist of a command verb and, sometimes, one or more
parameters. The commands must begin in the first character position after K. and
contain no blanks. The terminator (.) is optional. Some command verbs and
parameters can be shortened to a 2- or 3-character abbreviation. You can mix
abbreviated and unabbreviated command verbs and parameters in all network
commands. Parameters are order independent except where noted.

NS Control Commands
The HOP assigns the NAM K display to NS to enter the following commands. The NS
control commands do not apply to the CDCNET network.
Cancel Alternate NPU Load File Command
After using a FILE command, the HOP can instruct NS to return to the use of the
default NPU load file for loading all NPUs by specifying the NOFILE command.
The command format is:
NOFILE.

or
NO.

Revision

Network

Operations

1 5 - 11

Change NPU Load File Command

Change NPU Load File Command
The HOP can assign an alternate load file to NS for loading a specific NPU with the
FILE command.
The command format is:
FILE,NPU=npuname,NLF=loadfile,UN=username,PW=password.
or
FI,NP=npuname,NL=1oadf ile,UN=username,PW=password.

Parameter Description
npuname Name of the NPU.
loadfile Name of the alternate load file loadfile.
username Username of the user to which file loadfile belongs.
password Password for the username to which file loadfile belongs.
The next load of the specified NPU will be from the alternate load file. You can return
to the default NPU load file by using the NOFILE command.
NPU Load Status Command
The HOP can request the current load/dump status of a specific NPU or all NPUs
using
the
S TAT U S
command.

There are two forms of the STATUS command.
Specific NPU
The first form requests the current load/dump status of a specific NPU.
The command format is:
S TAT U S .

NPU=npuname.

"*^

or
ST,NP=npuname.

15-12

NOS

Version

Analysis

Handbook

Revision

NPU Load Status Command

All NPUs
The second form requests the current load/dump status of all NPUs.
The command format is:
STATUS,NPUS.

or
ST.NPS.

Status Response
The normal status response consists of four lines of information for each NPU, as
shown below.
npuname NN=nid NBS=nid,n1d,nid,nid,nid,nid EC=errcnt
L D S = 1 d c n t L D = y y / m m / d d LT = h h . m m . s s
dflag dmpfile HALT ffff DD=yy/mm/dd DT=hh.mm.ss
message

^^m^\

Status

Description

npuname

Name of the network processing unit.

NN=nid

Node number of the NPU identified by npuname.

NBS=nid,...,nid

Node numbers of up to six neighboring NPUs or couplers.

EC = errcnt

Protocol error count. Number of dump/load service messages
received from the NPU that violated the NPU dump/load
protocol.

LDS=ldcnt

Number of attempted loads of this NPU.

LD = yy/mm/dd

Date in year, month, and day when the most recent load
attempt of this NPU occurred.

LT = hh.mm.ss

Time in hours, minutes, and seconds when the most recent load
attempt of this NPU occurred.

dflag

NPU memory dump indicator; one of the following:
d fl a g

Description

DUMP Dump NPU before a load.
NODUMP No NPU dump before a load.
blank NPU is not currently being loaded.
dmpfile

Name of the most recent NPU dump file.

ffff

Halt code (halt codes are described in the CCP 3 Diagnostic
Handbook).

0jms

Revision M

Network Operations 15-13

NS Recent HISTORY Command

Status

Description

DD=yy/mm/dd

Date in year, month, and day when the most recent dump of this
NPU occurred.

DT=hh/mm/ss

Time in hours, minutes, and seconds when the most recent dump
of this NPU occurred.

message Message is the NS activity and its associated status (table 15-2).
Table 15-2 describes NS activity and its associated status.
Table 15-2. NS Activity
Activity

Status

Description

SAMLOAD

STARTED
COMPLETED
ABORTED - error

error is any of the messages listed in
table 15-3.

DUMP/LOAD
DUMP

REQUESTED
STARTED
COMPLETED
ABORTED-error

error is any of the messages listed in
table 15-3.

LOAD

modname
COMPLETED
ABORTED - error

modname is the name of the system module
being loaded, error is any of the messages
listed in table 15-3.

Table 15-3 lists the error messages associated with NS activity status.
Table 15-3. Load/Dump Status Messages
Error Message

Description

TIMEOUT

No response was received from the NPU during a preset
time-out period.

RETRY TIMEOUT

Only abnormal responses were received from the NPU during a
preset time-out period.

FILE ERRORS

Irrecoverable I/O error occurred on the network configuration file
or network load file.

PREEMPTED

An incomplete SAM load or dump/load sequence was interrupted
by a request from the same NPU to initiate a new SAM load.

NS Recent HISTORY Command
The HISTORY command requests a display of recent unsolicited status reports from NS
(refer to Recent HISTORY Command later in this section for further information).

15-14 NOS Version 2 Analysis Handbook

Revision M

NVF Control Commands
Jfpp>*\

NVF Control Commands
The HOP assigns the NAM K display to the network validation facility (NVF) to enter
the following commands.
Disable Host Element Command
The HOP uses the DISABLE command to force immediate termination of a particular
application or all host network operations.
The command format is:
DISABLE,operat1on.
or

DI.operation.
Parameter Description
operation One of the following:
operation

Keyword
Abbreviation

APPL=
applicationname

HOST

Description
applicationname is the name of the
application to be disabled. If more
than one copy of an application is
allowed, then applicationname can
be a 1- to 5-character root name
specifying that all copies of the
named application are affected.

Results of using the DISABLE,APPL command:
• The status of the named application is changed from enabled (EN), active (AC), or
down (DN) to disabled (DI), thereby prohibiting the application from accessing the
255x NPU network or CDCNET network.
• If the application is active at the time the command is entered, NAM requests the
application to immediately terminate access to the 255x NPU network or
CDCNET network. If the application remains active for an undue period of time
after entering this command, the HOP can resort to the DSD DROP or STOP
command (refer to section 5, DSD Commands).

Revision M

Network Operations 15-15

Enable Application Command

Results of using the DISABLE,HOST command:
• NAM requests that all active applications in the host immediately terminate their
access to both the 255x NPU network and CDCNET network.
• When all applications (including CS, NS, and NETOU) terminate their access to
the corresponding network, NAM and NVF also terminate.
• If NAM or NVF do not terminate, enter the STATUS,APPL command to
determine which application has not terminated. You can then use the DSD DROP
or STOP command to drop the application.
Enable Application Command
The HOP uses the ENABLE command to change the status of a network application
from disabled (DI) to enabled (EN). The application status becomes active (AC) when
the application begins to access the network.
The

command

format

is:

/f^\

ENABLE,APPL-app1i cat i onname.
or
EN,AP-app1i cat i onname.

Parameter Description
applicationname Name of the application to be enabled. If more than one copy of
an application is allowed, then applicationname can be a 1- to
5-character root name specifying that all copies of the named
application are affected.
Idle Host Element Command
The IDLE command terminates execution of an individual application or all host
network operations.
The command format is:
IDLE,operation.

or
ID,operation.

15-16

NOS

Version

Analysis

Handbook

Revision

Idle Host Element Command

Parameter Description
operation

One of the following:
operation
APPL=
applicationname

HOST

Keyword
Abbreviation

Description
AP applicationname is the name of the
application to be idled. If more than
one copy of an application is
allowed, then applicationname can
be a 1- to 5-character root name
specifying that all copies of the
named application are affected.
HO

Results of using the IDLE,APPL command:

• The application is warned of an imminent shutdown.
• The application completes any operations in progress but does not allow any new
connections.
• When all users are disconnected, the application terminates normally.
Results of using the IDLE.HOST command:
• Applications are warned of an imminent shutdown.
• New application requests to access either the 255x NPU network or CDCNET
network are rejected.
• New application to application connections are rejected.
• New terminal connections to the host from either the 255x NPU network or the
CDCNET network are rejected by NAM.
• CS warns all connected NOPs and DOPs that shutdown of the network is
imminent. CS terminates when all NOPs and DOPs end their connections to CS.
COPs must be warned separately using CDCNET network operator commands.
• NS ignores any new dump or load requests from NPUs. Any ongoing dump and
load processes are completed normally before NS terminates,
• Requests for MDI/MTI loads and dumps continue to be honored and NAM
continues to start INITMDI. However, requests for loading and dumping other DIs
are rejected, since connection requests from MDIs to NETFS are refused.
• When all applications (including NS, CS, and NETOU) terminate their access to
the network, NAM and NVF also terminate. If an application does not terminate,
use the DISABLE command to request immediate termination of network activity
in the host.

Revision M

Network Operations 15-17

NVF Recent HISTORY Command

NVF Recent HISTORY Command
The HISTORY command requests a display of recent unsolicited status reports from
NVF (refer to Recent HISTORY Command later in this section for further information).
Status Host Element Command
Host elements are the applications associated with the host, terminals currently
connected to the host, and users currently logged in to the host. With the STATUS
command a HOP can status a single application, terminal device, or user name; or all
applications, terminal devices, or users connected to a given application.
There are five forms of the STATUS command. Refer to Status Message Formats for
HOP, earlier in this section, for the format of the status line returned.
Particular Host Element
The first form requests the status of a particular host element.
The command format is:
STATUS,element.
or
ST,element
Parameter Description
element One of the following. (If the following elementname is the name of an
application and more than one copy of the application is allowed, then
elementname can be a 1- to 5-character root name specifying that all
copies of the named application are affected.)
element

Keyword
Abbreviation

Description

APPL=
elementname

elementname is the name of the
element whose status is desired.

TERM=
elementname4

elementname is the name of the
element whose status is desired.

UNAME=
elementname

elementname is the name of the
element whose status is desired.

4. elementname may be the terminal name of a CDCNET terminal. Terminal names for CDCNET are
assigned dynamically and are not associated with terminal names specified in the network configuration file.

15-18 NOS Version 2 Analysis Handbook

Revision M

Status Host Element Command

Network Applications
The second form requests the status of all network applications in the host.
The command format is:
STATUS.APPLS.

or
ST,APS.

Active Network Applications
The third form requests the status of all active network applications in the host.
The command format is:
0$ms

STATUS.APPLS,AC.
or
ST,APS,AC.

Terminal Devices
The fourth form requests the status of all terminal devices connected to the specified
application or logged in under the specified user name.
The command format is:
STATUS.TERMS,termelement.
or
ST,TES,t erme1ement.

Parameter Description
termelement One of the following:
termelement

Revision M

Keyword
Abbreviation Description

APPL=
elementname

elementname is the name of the
desired application or user.

UNAME =
elementname

elementname is the name of the
desired application or user.

Network Operations 15-19

Status Host Element Command

Users (Specified Application)
The fifth form requests the status of all users connected to the specified application.
The command format is:
STATUS,UNAMES,APPL=app1i cat i onname.

or
ST,UNS,AP=app1i cat i onname.
Parameter Description
applicationname Name of the desired application.

15-20

NOS

Version

Analysis

Handbook

Revision

Network Control by NOP

Network Control by NOP
The commands described later in this section are available to both HOPs and NOPs.
The NOPs can perform all functions of the diagnostic operators as well as those uniaue
to NOPs.
The controlling NOP (refer to CONTROL command later in this section) is
responsible for controlling one or more NPUs and its associated couplers, lines,
logical links, terminal devices, and trunks.
A controlling NOP can control any of the NPUs supervised by a CS and shares that
responsibility with the HOP. The controlling NOP and HOP must, therefore,
coordinate their activities.
CS does not control or report the status of CDCNET network elements; therefore,
none of the following commands apply to CDCNET.

Becoming a NOP
To become a NOP, you must be authorized by site personnel to access the CS
application and to become a controlling NOP.
After initiation of the network, you become a NOP as follows:
1. Log in as described in the NOS Version 2 Reference Set, Volume 2.
2. In response to the APPLICATION: prompt, enter:
CS

3. The system responds:
HELLO, YOU ARE NOW AN NPU OPERATOR
This message is followed by the prompt:
READY..

You can now enter the NOP commands described later in this section.
You can cancel a command that results in a large volume of output by entering the
interruption or termination sequence (refer to the NOS Version 2 Reference Set,
Volume 3).
NOTE
Use caution when cancelling output because unsolicited status messages could also be
discarded.

Revision

Network

Operations

15-21

Becoming a NOP

When you cancel output, the message
OUTPUT DISCARDED
READY..

or
OUTPUT DISCARDED..

appears at the terminal at the point from which the data was discarded.
If the terminal is in page wait mode,5 you must press CR after every page of output
before more output can be sent to the terminal.
To relinquish NOP status, enter one of the following.
• To log out and end the terminal connection to the host, enter:
GOODBYE

or
BYE

or
LOGOUT

• To initiate a new login dialog, enter:
HELLO

or
LOGIN

• To remain logged in and be prompted for another application, enter:
END

• To remain logged in and be switched automatically to the application named '^S
applname, enter:
END,app1 name

5. Use a hardcopy device for NOP terminals; this prevents the paging problem and provides a permanent
log
of
network
events.

15-22

NOS

Version

Analysis

Handbook

Revision

'*ss%.

Status Message Formats for NOP

Status Message Formats for NOP
Some of the NOP commands cause various status messages to be displayed on your
terminal. The normal response to a STATUS command is one line of text returned
when status is requested for a coupler, line, NPU, or terminal device. Two text lines
can be returned when status is requested for logical links or trunks (if the CS to
which you are connected is supervising NPUs at each end of the element, a line of text
is returned for each end of the logical link or trunk). For multiple element status
commands, a response is generated for all elements expressed or implied in the
command. For example, a status request for all terminals on an NPU begins with a
status report (text line) for the NPU. This is followed by a status report for the first
active (AC) line on the NPU. A status report for each terminal device configured on
the line follows. This is followed by a status report of the next active line and so on.
The response to the ENABLE or DISABLE command is a status report for each
element affected by that command.
Following are the general formats for these status messages.
Message

Type

Format

Coupler status line

CPLER: name,stat us,nodenum,npuname1/cp1num.

Line status line

LINE: name,status,1inetype,npuname1/port.

Logical link status line

LLINK: name,status,RL=n,loglinktype,npuname1/nodenum,
npuname2/nodenum.

NPU status line

NPU: name,status,nodenum,gostatus,dump.

Archetype switched virtual
circuit (SVC) status line

SVC: atname.EN=ennum,DI=dinum,AC=acnum,stip.

Terminal device status line

TERM: name,status,dt/tc,/hostnid,linename/al/a2,ldstat.

Trunk status line

TRUNK: name,status,1inetype.npunamel/port,npuname2/port

Revision M

Network Operations 15-23

Status Message Formats for NOP

In the preceding status message general formats the following variables are used.
Va r i a b l e D e s c r i p t i o n
acnum Number of SVCs of the element that are in an active state
(from 0 to 255).
atname Name of the archetype SVC element.
al First level address (cluster address, configuration ordinal).
a2 Second level address (terminal address, stream number).
cplnum Coupler number for the indicated NPU.
dinum Number of SVCs of the element that are in a disabled state (from 0
to 255).
dt Device type (CON, CR, LP, CP, PL).
dump NPU dump flag (ON or OFF).
ennum Number of SVCs of the element that are in an enabled state (from 0
to 255).
gostatus Go status of the NPU (if waiting for GO, NEEDGO appears).
hostnid Host (coupler) node number of the host to which the terminal is currently
connected.
ldstat Load status of the trunk (LDDI means the trunk is disabled for loading;
LDEN means the trunk is enabled for loading).
linename Name of the line to which the terminal device is connected.
linetype Line type (refer to the NDL Reference Manual).
loglinktype Logical link type (H-N for host to NPU, H-H for host to host).
name Name of the element.

>ea^s\

nodenum Node number of a coupler or NPU.
npunamel Name of an NPU that supports or is connected to the element (also the
name of the NPU that reported the status).
npuname2 Name of the NPU at the other end of the logical link or trunk.
port Port number of the line or trunk on the indicated NPU.

15-24 NOS Version 2 Analysis Handbook

Revision M

Unsolicited Status Reports for NOP

Va r i a b l e D e s c r i p t i o n
X^^y

RL=n

Regulation level currently in effect.

status

Network elements are initially set to either a disabled or enabled state.
Initially enabled elements automatically become active during the course
of normal network operation. Every network element (such as line, logical
link, NPU, or trunk) is in one of the following states.
status

Description

Network element is active. An element becomes active when it
is enabled and is handling network data traffic.

Network element is disabled. The element cannot become active
unless enabled by an operator command.

Network element is down. A failure was detected that
terminated data traffic for the element. If the failure condition
ceases, the element returns to an enabled status.

Network element is enabled. It was enabled by the operator
and is in a physically operative condition.

Network element is not configured. The NPU does not
recognize the element.

stip

SubTIP type (PAD or APPL).

Terminal class.

Unsolicited Status Reports for NOP
Each time a significant event occurs, CS updates its recent history buffer (refer to
Recent HISTORY Command later in this section) and logs the event in the NAM
dayfile. CS then sends a report about the event, called the unsolicited status report, to
all NOPs who have selected to receive unsolicited status reports from the NPU (refer
to Report Unsolicited Status Command later in this section). Unsolicited status reports
are time-stamped whereas solicited status reports are not time-stamped.
A single unsolicited status report occurs as a result of an element recovery or failure.
An unsolicited status message is sent when an NPU joins the network. Batches of
unsolicited status reports can occur as a result of an operator command to enable all
elements of a given type (refer to Enable Network Element Command later in this
section).

Revision M

Network Operations 15-25

NOP Commands

NOP Commands
All NOP commands consist of a command verb and, sometimes, one or more
parameters. The commands must begin in the first character position and contain no
blanks. The terminator (.) is optional. Some command verbs and parameters can be
shortened to a 2- or 3-character abbreviation. You can mix abbreviated and
unabbreviated command verbs and parameters in all network commands. Parameters
are order independent except where noted. You can enter commands pertaining only to
the NPUs supervised by the CS to which you are connected.
To enter the following commands you must control the NPU (refer to CONTROL
Command later in this section).
ALERT Command
The ALERT command changes the threshold that CS uses for alerting the HOP and
the controlling NOP of NPU saturation.
The command format is:
ALERT,CP=cpuse,BU=buff.element.

or
AL,CP=cpuse,BU=buff.element
Parameter Description

cpuse

Percent of the NPU central processor currently in use (from 50 to 100
percent).

buff

Number of available NPU data buffers (from 0 to 500).

element

One of the following:
element

Keyword
Abbreviation Description

NPU = npuname NP
NPUS

npuname is the name of the NPU
supervised by your CS.

NPS

If the CPU usage reported to CS by the NPU is greater than cpuse, the HOP and the
controlling NOP are alerted. If the buffer availability reported to CS by the NPU is
less than buff, the HOP and the controlling NOP are alerted. To turn off all messages,
set CP=100 and BU = 0.

15-26 NOS Version 2 Analysis Handbook

Revision M

CONTROL Command

CONTROL Command
/ms.

After establishing communication with a CS, you can gain or lose control of one or
more NPUs supervised by your CS with the CONTROL command.
The command format is:
CONTROL,opt ion,status.
or

CO,opt ion,status.
Parameter Description
option

status

One of the following:
option

Keyword
Abbreviation

NPU=npuname

NPUS

NPS

AUTO

Description
npuname is the name of the
NPU.

ON or OFF.

The NPU = npuname option allows you to gain control of a specific NPU. The NPUS
option allows you to gain control over all uncontrolled NPUs currently supervised by
your CS. The AUTO option allows you to gain control over all uncontrolled NPUs
currently supervised by your CS and all other uncontrolled NPUs that may later come
under the supervision of your CS. The AUTO option can be cancelled by entering any
valid CONTROL command with the OFF status specified.

Revision M

Network Operations 15-27

CONTROL Command
y^>k

Example:
Suppose there are four NPUs (1, 2, 3, and 4) available to be controlled in the
network. The first NOP logs in to CS and controls NPU 1. The second NOP
establishes a connection to CS and enters the CONTROL,AUTO,ON command. The
second NOP becomes the controlling NOP and controls all of the uncontrolled NPUs
(in this example 2, 3, and 4). When the first NOP relinquishes control of NPU 1,
that NPU is then controlled by the second NOP. The second NOP also controls all of
the new NPUs joining the network automatically.
If no other NOP exists for the NPUs specified, the response to a request for control
consists of a list of the NPUs you now control followed by a READY., prompt;
otherwise, you receive a diagnostic messsage.
Since a HOP automatically controls all NPUs being supervised by a CS, the
CONTROL commands are not used by the HOP. Whenever a NOP loses control of an
NPU for any reason (including ending the connection to CS or the failure of some
network element that was supporting the connection to CS), CS informs the HOP and
all other connected NOPs by sending an unsolicited status report.
If any NOP has AUTO control status, the operators are informed of the identity of
the controlling NOP. Whenever a CS gains supervision of a new NPU, the HOP, all
NOPs, and all DOPs are informed that the NPU is being supervised.

,^53^.

15-28 NOS Version 2 Analysis Handbook

Revision M

Disable Network Element Command

Disable Network Element Command
The controlling NOP changes the status of a network element from enabled (EN),
active (AC), or down (DN), to disabled (DI) by the DISABLE command.
There are three forms of the DISABLE command. Refer to Status Message Formats
for NOP, earlier in this section, for the format of the status line returned.
Single Element
The first form disables a single element in a network.
The command format is:
DISABLE,element.
or

DI,element.
Parameter Description
element

One of the following:
element

Keyword
Abbreviation

Description

LINE =
elementname

elementname is the name of the
element to be disabled.

LLINK =

elementname is the name of the
element to be disabled.

TERM =
elementname

elementname is the name of the
element to be disabled.

TRUNK=
elementname

elementname is the name of the
element to be disabled.

elementname

For a logical link or trunk, if the element is active when the command is entered, all
data traffic through the element is terminated and the affected host application
programs and terminal users are notified. For a line or terminal, if the element is
active when the command is entered, all data traffic through the element is terminated
and only the affected host application programs are notified.

Revision M

Network Operations 15-29

Disable Network Element Command

Trunk
The second form disables a trunk for loading.
The command format is:
DISABLE,TRUNK=trunkname,LD.
or
DI,TRUNK=trunkname,LD.

Parameter Description
trunkname Name of trunk to be disabled for loading.
If the trunk is enabled, it will still be enabled after this command is issued, but it will
be disabled for loading.

15-30

NOS

Version

Analysis

Handbook

Revision

Disable Network Element Command

SVCs
The third form disables archetypical switched virtual circuits (SVCs) that are in an
enabled state.
The command format is:
DISABLE,SVC=atname,NCIR=numcir.

or
DI,SV=atname,NC=numc1r.

Parameter Description
atname Archetypical SVC name,
numcir Number of SVCs to change from an enabled state to a disabled state.
DISABLE Processing
This form of the DISABLE command allows you to decrease the number of enabled
SVCs for a particular X.25 subTIP type. If the number of enabled SVCs is greater than
or equal to numcir, then the number of disabled SVCs is increased by numcir and the
number of enabled SVCs is decreased by numcir. If the number of enabled SVCs is less
than numcir, then the number of disabled SVCs is increased by the number of
available enabled SVCs and the number of enabled SVCs is set to zero. Disabling SVCs
has no effect on active SVCs. If, for a particular SVC element, the command could not
be executed, an unsolicited status report is sent to you giving the reason the command
was not executed.
The NPUs affected by the command send an unsolicited status report indicating the
new status for the element.

Revision

Network

Operations

15-31

Disable Network Element Command

Trunks and logical links can have two owning NPUs (one at each end of the trunk or
logical link). When two NPUs are involved and both are supervised by your CS, the
DISABLE,TRUNK and DISABLE,LLINK commands are processed as follows:
• If one of the NPUs is local and one is remote, the command is forwarded to the
local NPU.
• If both of the NPUs are local or both are remote, the command is forwarded to
the NPU with the lower node number.
• If your CS supervises only one of the NPUs, the command is forwarded to that
NPU.
In either case, the trunk or logical link enters the disabled (DI) state at the owning
NPU that receives the DISABLE command and is detected as being down (DN) by the
other NPU. Both of these changes are reported to CS, which informs all operators of
the changes by sending unsolicited status reports.
If a single NPU owns both ends of the link, the command is forwarded to that NPU.
This status change is also reported by sending unsolicited status reports.
Disabling a trunk can cause one or more logical links to go down. The owning NPUs
report the failure of these links by sending unsolicited status reports.
NOTE
No attempt is made to protect you from disabling network elements that support your
connection to CS. You may lose contact with CS as a result of such a command.
When this happens, you may need to use another terminal or the host console to
enable the disabled network element.

"=Sf%v

15-32 NOS Version 2 Analysis Handbook

Revision M

Enable Network Element Command
/$*N

Enable Network Element Command
The controlling NOP changes the status of one or more network elements from disabled
(DI) to enabled (EN), allowing the element(s) to become active for data traffic by the
ENABLE command.
There are six forms of the ENABLE command. Refer to the Status Message Formats
for NOP, earlier in this section, for the format of the status line returned.
Single Element
The first form enables a single element in the network.
The command format is:
ENABLE,element.
or
EN,element.

Parameter Description
element

One of the following:
element

jf^S

Revision M

Keyword
Abbreviation

Description

LINE =
elementname

elementname is the name of the
element to be enabled.

LLINK =
elementname

elementname is the name of the
element to be enabled.

TERM =
elementname

elementname is the name of the
element to be enabled.

TRUNK=
elementname

elementname is the name of the
element to be enabled.

Network Operations 15-33

Enable Network Element Command

Trunk
The second form enables a trunk for loading. It will also enable the trunk if it is
disabled.
The command format is:
ENABLE,TRUNK=trunkname,LD.

or
EN,TRUNK=t runkname,LD.

Parameter Description
trunkname Name of the trunk to be enabled for loading.
Disabled Elements
The third form enables all disabled elements of the specified type on an NPU.
The command format is:
ENABLE,e1ement,NPU=npuname.
or
EN,e1ement,NP=npuname.

Parameter Description
element One of the following:
element Keyword Abbreviation
LINES

LIS

LLINKS

LLS

TERMS

TES

TRUNKS

TRS

>cC®%.

npuname Name of an NPU.

->s%.

15-34 NOS Version 2 Analysis Handbook

Revision M

Enable Network Element Command

Disabled Elements (All NPUs)
The fourth form enables all disabled elements of the specified type on all NPUs.
The command format is:
ENABLE,element,NPUS.
or
EN,element,NPS.

Parameter Description
operation One of the following:
element Keyword Abbreviation
LINES

LIS

LLINKS

LLS

TERMS

TES

TRUNKS

TRS

j0$8%5!\

Disabled Terminals
The fifth form enables all disabled terminals on a line.
The command format is:
ENABLE,TERMS,LINE=termline.

or
EN,TES,LI=termline.
Parameter Description
termline Name of the line to which terminals are connected.

Revision

Network

Operations

15-35

Enable Network Element Command

SVCs
The sixth form enables SVCs that are in a disabled state.
The command format is:
ENABLE,SVC=atname,NCIR=numci r.
or
EN,SV=atname,NC=numcir.

Parameter Description
atname Archetype SVC name.
numcir Number of SVCs to change from a disabled state to an enabled state.
ENABLE Processing
The ENABLE,TRUNK and ENABLE.LLINK commands are forwarded to both of the
owning NPUs (one at each end of the trunk or logical link) if both are supervised by
your CS. Enabling a trunk can cause one or more logical links with a down status to
become enabled or active. Status changes resulting from enabling a trunk or logical
link are reported by the owning NPUs by sending unsolicited status reports.
Enabling a trunk can cause CS to become available to an NPU and, therefore, allow
CS to gain control of an NPU.

••"*%

The ENABLE command allows you to enable all lines or terminal devices on an
NPU. When you enable all lines or terminal devices of a given type on an NPU or
all terminals on a line, the NPU or line affected by the command sends an
unsolicited status report telling you how many elements of the given type are
curently disabled. The NPU then sends unsolicited status reports telling the new
status of each element for which the command was executed. If, for a particular
element, the command could not be executed, an unsolicited status report is sent to
you giving the reason the command was not executed.
The ENABLE,SVC command allows you to increase the number of enabled SVCs for
a particular X.25 subTIP type. If the number of disabled SVCs is greater than or
equal to numcir, then the number of enabled SVCs is increased by numcir. If the
number of disabled SVCs is less than numcir, then the number of enabled SVCs is
increased by the number of disabled SVCs and the number of disabled SVCs is set to
zero. Enabling SVCs has no effect on active SVCs. If, for a particular SVC element,
the command could not be executed, an unsolicited status report is sent to you giving
the reason the command was not executed.

15-36

NOS

Version

Analysis

Handbook

Revision

/4*iSX

NPU GO Command
yf^SSi^

NPU GO Command
After establishing a connection with CS, the newly supervised NPU may ask for a GO
command from the controlling NOP.
The GO command format is:
GO,NPU=npuname.
or
GO.NP-npuname.

Parameter Description
npuname Network defined name of the NPU.
If there is a controlling NOP for the NPU when CS receives a GO request, the GO
request is relayed to the controlling NOP and to the HOP. If there is no controlling
NOP, the GO request is relayed to the HOP and to all currently connected NOPs. The
HOP or controlling NOP (if there is one) can, as needed, request status information or
enable/disable network elements. Thus, the controlling NOP can control the initial
status or the network elements connected to or supported by a given NPU prior to that
NPU beginning terminal operations.
The GO request message is repeated periodically until an operator takes control of
the NPU and enters the GO command.
/ ^ S

Upon entry of the GO command the NPU proceeds to activate lines and accept
terminal connections.

Revision

Network

Operations

15-37

NPU LOAD Command

NPU LOAD Command
.j^s\

The LOAD command causes an active (AC) NPU or all active NPUS to be stopped, 1
reloaded, and reactivated.
There are two forms of the LOAD command.
Specified NPU
The first form causes the specified NPU to be stopped, reloaded, and reactivated.
The command format is:
LOAD,NPU=npuname,dumpopt i on.
or

LO,NP=npuname,dumpopt ion.
Parameter Description
npuname Name of the NPU.
dumpoption Optional dump parameter; one of the following:
dumpoption Keyword Abbreviation
DUMP

NDMP

If the DUMP option is specified, a memory dump of the NPU is taken prior to
reloading. If the NDMP option is specified, the NPU is reloaded without taking a
memory dump. If the dump status is not specified, taking a memory dump depends
upon the setting of the dump flag. Refer to NPU Memory Dump Command, next, for
more information. The DUMP or NDMP option is in effect only for the immediate load.
It has no permanent effect on the NPU memory dump flag.
When an NPU executes a LOAD command, the CS connection to that NPU is lost
during the dump/load process. The trunks and logical links supported by the NPU are r*^s
detected as down (DN) by the NPUs at the other ends of the trunks and logical )
links. All of the appropriate operators receive corresponding unsolicited status reports.

15-38

NOS

Version

Analysis

Handbook

Revision

NPU LOAD Command

All NPUs
The second form causes all active NPUs to be stopped, reloaded, and reactivated.
The command format is:
LOAD,NPUS,dumpopt i on.
or
LO,NPS,dumpopt i on.

Parameter Description
dumpoption Optional parameter; one of the following:
dumpoption Keyword Abbreviation
DUMP

NDMP

If the DUMP option is specified, a memory dump of all active NPUs (supervised by
this host) is taken prior to reloading. If the NDMP option is specified, the NPUs are
reloaded without taking a memory dump. If the dump status is not specified, taking a
memory dump depends upon the setting of the dump flag. Refer to NPU Memory Dump
Command, next, for more information. The DUMP or NDMP option is in effect only for
the immediate load. It has no permanent effect on the NPUs memory dump flag.
When all of the NPUs execute LOAD commands, the corresponding CS connections to
the NPUs are lost during the dump/load process. The trunks and logical links
supported by the NPUs are detected as down (DN) by the NPUs at the other ends of
the trunks and the logical links. The appropriate operators receive corresponding
unsolicited status reports.

Revision

Network

Operations

15-39

NPU Memory DUMP Command

NPU Memory DUMP Command
The DUMP command causes the memory dump flag to be reset for the specified NPU
or NPUs. Initially, this reset condition is set independently for every NPU in the
network and is specified on the NPU statement (refer to the NDL Reference Manual
for more information on the NPU statements).
There are two forms of the DUMP command.
Specified NPU
The first form causes a memory dump of the specified NPU to be taken.
The command format is:
DUMP,NPU=npuname,stat us.
or
DU,NP=npuname,status.

Parameter Description
npuname Name of the NPU.
s t a t u s O N o r O F F.
All NPUs
The second form causes a memory dump of all NPUs to be taken.
The command format is:
DUMP,NPUS.status.

or
DU.NPS,status.

Parameter

Description

'^^

s t a t u s O N o r O F F.
If status is ON, a memory dump will be taken the next time the NPU is reloaded
(unless overridden by the LOAD command). If status is OFF, a memory dump will not
be taken the next time the NPU is reloaded (unless overridden by the LOAD
command).

15-40

NOS

Version

Analysis

Handbook

Revision

Send Message Command

Send Message Command
A controlling NOP can send a message to the HOP or any terminal device user or
group of terminal device users using the SEND command. The NOP can address the
message to a single user or to all users on the specified line, logical link, NPU, or all
NPUs under the supervision of the CS.
The HOP cannot use the HOST element to send a message.
The command format is:
SEND,e1ement,MSG=message.

or
SE,e1ement,MS=message.

Parameter Description

element One of the following

y^P*S

element

Keyword
Abbreviation

LINE =
elementname

elementname is the name of the
element to which the message is
addressed.

LLINK =
elementname

elementname is the name of the
element to which the message is
addressed.

NPU=
elementname

elementname is the name of the
element to which the message is
addressed.

TERM=
elementname

elementname is the name of the
element to which the message is
addressed.

HOST

NPUS

NPS

Description

message Text message of no more than 50 characters. If more than 50
characters are entered, a diagnostic message is issued. The
MSG=message parameter is order dependent and must appear as the
last parameter of the command.

Revision M

Network Operations 15-41

Send Message Command

CS, upon accepting a SEND command, does not issue the READY., prompt until
processing of the SEND command has completed, to prevent an NPU from being /^
flooded with operator messages. CS sends a message to you as each NPU receives the /
SEND command. When processing is complete, CS sends the READY., message.
If a terminal is specified as the network element, it must be an interactive terminal
device. Otherwise, an error message is issued to the sender.
If the element referenced by a SEND command is not currently active or enabled,
you receive an error message. This error message is followed by a status line for the
element; the operator is thus informed why the message could not be delivered. The
status text line is followed by the READY., prompt.

15-42

NOS

Version

Analysis

Handbook

Revision

Network Control by DOP

0ms.

Network Control by DOP

0$ms

The commands described next are available to the HOPs, NOPs, and DOPs, but not
COPs. All DOPs can obtain unsolicited status reports and use status and diagnostic
commands.

Becoming a DOP
To become a DOP you must be authorized by site personnel to access CS.
After initiation of the network, you become a DOP as follows:
1. Log in as described in the NOS Version 2 Reference Set, Volume 2.
2. In response to the APPLICATION: prompt, enter:
CS

The

system

responds:

HELLO, YOU ARE NOW A DIAGNOSTIC OPERATOR

This message is followed by the prompt:
READY..

You can now enter the DOP commands described later in this section.
/^ You can cancel a command that results in a large volume of output by entering the
interruption or termination sequence (refer to the NOS Version 2 Reference Set,
Volume 3).
NOTE
Use caution when cancelling output because unsolicited status messages could also be
discarded.
0$m\

When you cancel output, the message
OUTPUT DISCARDED
READY..

or
OUTPUT DISCARDED..

appears at the terminal at the point from which the data was discarded.

Revision

Network

Operations

15-43

Becoming a DOP

If the terminal is in page wait mode,6 you must press CR after every page of output
before
more
output
can
be
sent
to
the
terminal.

To relinquish DOP status, enter one of the following:
• To logout and end the terminal connection to the host, enter:
GOODBYE

or
BYE

or
LOGOUT

• To initiate a new login dialog, enter:
HELLO

S^?sS

or
LOGIN

• To remain logged in and be prompted for another application, enter:
END

• To remain logged in and be switched automatically to the application named
appmame,
enter:

}

END,appiname

6. Use a hardcopy device for DOP terminals; this prevents the paging problem and provides a permanent
log of network events.

15-44

NOS

Version

Analysis

Handbook

Revision

Status Message Formats for DOP

Status Message Formats for DOP
Some of the DOP commands cause various status messages to be displayed on your
terminal. The normal response to a STATUS command is one line of text returned
when status is requested for a coupler, line, NPU, or terminal device. Two text lines
can be returned when status is requested for logical links or trunks (if the CS to
which you are connected is supervising NPUs at each end of the element, a line of text
is returned for each end of the logical link or trunk). For multiple element status
commands, a response is generated for all elements expressed or implied in the
command. For example, a status request for all terminals on an NPU begins with a
status report (text line) for the NPU. This is followed by a status report for the first
active (AC) line on the NPU. A status report for each terminal device configured on
the line follows. This is followed by a status report of the next active line and so on.
The following are the general formats for these status messages.
Message

Type

Format

Coupler status line

CPLER: name,status,nodenum,npuname1/cpinum.

Line status line

LINE: name,status, 1 Inetype,npunamel/port.

Logical link status line

LLINK: name,status,RL=n,loglinktype,npuname!/nodenum,
npuname2/nodenum.

NPU status line

NPU: name,stat us,nodenum,gostat us,dump.

Archetype switched virtual
circuit (SVC) status line

SVC: atname,EN=ennum,DI=dinum,AC=acnum,stip.

Terminal device status line TERM: name,status,dt/tc,/hostnid, 1 inename/a 1 /a2.
Trunk status line TRUNK: name,status,1inetype,npunamel/port,npuname2/port

Revision M

Network Operations 15-45

Status Message Formats for DOP

In the preceding status message general formats the following variables are used.
Variable

Description

acnum Number of SVCs of the element that are in an active state (from 0
to 255).
atname Name of the archetype SVC element.
al First level address (cluster address, configuration ordinal).
a2 Second level address (terminal address, stream number).
cplnum Coupler number for the indicated NPU.
dinum Number of SVCs of the element that are in a disabled state (from 0
to 255).
d t D e v i c e t y p e ( C O N , C R , L P, C P, P L ) .
d u m p N P U d u m p fl a g ( O N o r O F F ) .
ennum Number of SVCs of the element that are in an enabled state (from 0
to 255).
gostatus Go status of the NPU (if waiting for GO, NEEDGO appears).
hostnid Host (coupler) node number of the host to which the terminal is
currently connected.
A*^S

linename Name of the line to which the terminal device is connected.
linetype Line type (refer to the NDL Reference Manual).
loglinktype Logical link type (H-N for host to NPU, H-H for host to host).
name Name of the element.
nodenum Node number of a coupler or NPU.
npunamel Name of an NPU that supports or is connected to the element (also
the name of the NPU that reported the status).
npuname2 Name of the NPU at the other end of the logical link or trunk.
port Port number of the line or trunk on the indicated NPU.
RL=n Regulation level currently in effect.

15-46 NOS Version 2 Analysis Handbook

Revision M

Status Message Formats for DOP

Variable

Description

status

Network elements are initially set to either a disabled or enabled
state. Initially enabled elements automatically become active during
the course of normal network operation. Every network element (such
as line, logical link, NPU, or trunk) is in one of the following states.
status

Description

Network element is active. An element becomes active
when it is enabled and is handling network data traffic.

Network element is disabled. The element cannot become
active unless enabled by an operator command.

Network element is down. A failure was detected that
terminated data traffic for the element. If the failure
condition ceases, the element returns to an enabled
status.

Network element is enabled. It was enabled by the
operator and is in a physically operative condition.

Network element is not configured. The NPU does not
recognize the element.

stip

SubTIP type (PAD or APPL).

Terminal class.

Revision M

Network Operations 15-47

Unsolicited Status Reports for DOP

Unsolicited Status Reports for DOP
Each time a significant event occurs, CS updates its recent history buffer (refer to
Recent HISTORY Command later in this section) and logs the event in the NAM
dayfile. CS then sends a report about the event, called the unsolicited status report, to
all DOPs who have selected to receive unsolicited status reports from the NPU (refer
to Report Unsolicited Status Command later in this section). Unsolicited status reports
are time-stamped whereas solicited status reports are not time-stamped.

DOP Commands
All DOP commands consist of a command verb and, sometimes, one or more
parameters. The command must begin in the first character position and contain no
blanks. The terminator (.) is optional. Some command verbs and parameters can be
shortened to a 2- or 3-character abbreviation. You can mix abbreviated and
unabbreviated command verbs and parameters in all network commands. Parameters
are order independent except where noted. You can enter commands pertaining only to
the NPUs supervised by the CS to which you are connected. '*s%

CS Information Command
You can access information about all operators and NPUs connected to and supervised
by your CS with the INFO command.
The command format is:
INFO.

or
IN.

The response lines are an operator information line and an NPU information line for
each operator (DOP and NOP) and for each NPU supervised by a CS, respectively.
The format of the operator information line is:
DOP:

termname,username,acn.

'^^%

NOP: termname,username,acn,auto.

15-48

NOS

Version

Analysis

Handbook

Revision

CS Information Command

The format of the NPU information line is:
NPU: npuname,status,nodenum,go-status,nopname.
In the preceding information line formats the following variables are used.
Va r i a b l e D e s c r i p t i o n
a c n C S a p p l i c a t i o n c o n n e c t i o n n u m b e r.
auto Control status of the NOP (if the NOP is an auto control NOP, AUTO
appears). Refer to the NOP CONTROL command described earlier in
this section.
nodenum Node number of the NPU.
nopname Terminal name of the NOP that is controlling the NPU. If the NPU
has no controlling NOP, the field is blank.
npuname Name of the supervised NPU.
status Status of the NPU. (AC if the NPU is active, MI if the NPU is in a
mismatch condition).
termname Name of the terminal at which the DOP or NOP resides.
username User name of the DOP or NOP.
go-status If the NPU is waiting for GO, NEEDGO is displayed.

Revision M

Network Operations 15-49

NPU Diagnostic Test Command

NPU Diagnostic Test Command
The TST command allows any operator to request, interact with, or terminate the
diagnostic program within any NPU supervised by a CS.
The command format is:
TST,NPU=npuname,opt i on.

or
TS,NP=npuname,option.
Parameter Description
npuname

Name of the NPU containing the diagnostic program with which the
operator wants to communicate.

option

One of the following
option

Keyword
Abbreviation

DROP

MSG=
message

REQUEST

,yrfiepRj\

Description

message is the command that
controls the execution of the
diagnostic program in the NPU.

CS keeps track of which NPUs are currently running diagnostic tests and which
operators are using them. A single operator is permitted to perform diagnostic tests in
several different NPUs simultaneously. All operators can interact with the diagnostics
in a single NPU, but only one operator can run the diagnostics.
TST Drop Option
The DROP parameter cancels your diagnostic program reservation in the specified
NPU. All diagnostics currently being performed by you in the specified NPU are
terminated. If the diagnostic program is not executing, the TST command is ignored
and an error message is returned.

15-50 NOS Version 2 Analysis Handbook

Revision M

TST Message Option

TST Message Option
The MSG=message parameter allows you to interact with an NPU diagnostic program.
It allows you to send a command message in the form of a text string to the diagnostic
program in the specified NPU. A typical use of the message option is to initiate and
terminate diagnostic tests. The option is accepted only if you previously entered and
confirmed a REQUEST option; otherwise, an error message is received. Refer to the
CCP 3 Diagnostic Handbook for more information.
The diagnostic program sends text messages through CS to you. The message is an
unsolicited status report with this format:
FROM npuname/DIAGNOSTIC: TO termname:
messagetext

Va r i a b l e D e s c r i p t i o n
npuname Name of the NPU.
f

termname

Name

your

terminal.

messagetext Message from the diagnostic program.
TST Request Option
The REQUEST parameter allows you to initiate interaction with an NPU diagnostic
program. An NPU diagnostic program is assigned to you until one of these events
occurs:
• You drop the diagnostic program (by sending a TST command with the DROP
option).
• The connection between you and CS is terminated for any reason.
• Supervision of the NPU is lost by CS.

Revision

Network

Operations

15-51

Recent HISTORY Command

Recent HISTORY Command
The HISTORY command requests a display of the recent unsolicited status reports from
aCS.
The command format is:
HISTORY,ALL.

or
HI,ALL.

If the ALL option is not used, only the last (most recent) page (based on your
terminal's page size) of the unsolicited status reports is displayed.
Any DOP or NOP can enter the HISTORY command to obtain reports from CS.
A HOP can enter the HISTORY command to obtain reports from CS, NS, or NVF ^%
after assigning the NAM K display to the desired application (refer to section 8,
K-Display Utilities, for more information on the NAM K display).
Each application maintains a separate record of the most recent significant NPU load,
DOP, NOP, or HOP events. The occurrence of these various significant events
prompts the sending of an unsolicited status report to all appropriate operators. All
reports are temporarily available through the HISTORY command and are
permanently recorded in the NAM dayfile.
A CDCNET operator can enter the DISPLAY_ALARM_HISTORY command to obtain ^%
reports from NETOU. Refer to the CDCNET Network Operations Manual for more '
information about this command.

15-52

NOS

Version

Analysis

Handbook

Revision

Report Unsolicited Status Command

Report Unsolicited Status Command
The REPORT command requests a CS to report all unsolicited status messages from an
NPU.
The command format is:
REPORT,e1ement,opt i on

or
RE,element.option
Parameter Description
element

One of the following:
element

/0m\.

Keyword
Abbreviation

NPU = npuname NP
NPUS
option

Description
npuname is the name of the
NPU.

NPS

ON or OFF. If option is not specified, OFF is assumed. If option is
ON, CS reports all unsolicited status messages until you turn
reporting off.

Initially, HOPs do not receive reports for any NPUs supervised by a CS, but
controlling NOPs receive reports for the NPUs they control. Other NOPs and DOPs do
not receive any reports. However, any operator can use this command to request
unsolicited status reports from any NPU supervised by a CS.

Revision M

Network Operations 15-53

Send Message Command

s^mK

A DOP can send a message to any of the other operators (HOP, NOPs, and other
DOPs) connected to the same CS using the SEND command.
The command format is:
SEND,element,MSG=message
or
SE,e1ement,MS=message

Parameter Description
element

One of the following:
element

Keyword
Abbreviation

TERM=termname TE

HOST

Description
termname is the name of the
terminal to which the message
is addressed.

message Text message of no more than 50 characters. If more than 50
characters are entered, an error message is issued. The
MSG=message parameter is order dependent and must appear as the
last parameter of the command.
If a terminal device is specified as the network element, it must be an interactive
terminal device currently connected to your CS. Otherwise, an error message is issued
to the sender.
If you specify HOST, the message is sent to the HOP of the host to which you are
connected.
If the element referenced by a SEND command is not currently connected to a CS,
you receive a diagnostic message. The diagnostic message is followed by the READY.,
prompt.

15-54 NOS Version 2 Analysis Handbook

Revision M

Status Network Element Command

Status Network Element Command
You request a CS to display status information on the various 255x NPU network
elements (such as couplers, NPUs, and trunks) with the STATUS command.
There are five forms of the STATUS command. Refer to the Status Message Formats
for DOP, earlier in this section, for the format of the status line returned.
Particular Element
The first form requests the status of a particular element in the network.
The command format is:
STATUS,element.

or
ST,e1ement.
Parameter Description
element

One of the following:
element

Keyword
Abbreviation

Description

CPLER=
elementname

elementname is the name of the
element whose status is desired.

LINE =
elementname

elementname is the name of the
element whose status is desired.

LLINK =
elementname

elementname is the name of the
element whose status is desired.

NPU =
elementname

elementname is the name of the
element whose status is desired.

SVC=
elementname

elementname is the name of the
element whose status is desired.

TERM =
elementname

elementname is the name of the
element whose status is desired.

TRUNK=
elementname

elementname is the name of the
element whose status is desired.

/A^S

Revision M

Network Operations 15-55

Status Network Element Command

All Elements
The second form requests the status of all of the elements of a particular type on one
or all NPUs.
The command format is:
STATUS,1inkelement npue1ement,statuscode.
or

ST,1inkelement,npue1ement,st at uscode.
Parameter Description
linkelement

One of the following

npuelement

linkelement

Keyword
Abbreviation

CPLERS

CPS

LINES

LIS

LLINKS

LLS

SVCS

SVS

TERMS

TES

TRUNKS

TRS

One of the following
npuelement

Keyword
Abbreviation

NPU = npuname

Description
npuname is the name of the
NPU.

NPUS
statuscode Optional. If specified, only the elements with that status are
reported.
statuscode

Description

Active

Down

Disabled

Enabled

15-56 NOS Version 2 Analysis Handbook

Revision M

Status Network Element Command
0imu..

Terminal Devices
The third form requests the status of all terminal devices on a line or a logical link.
The command format is:
STATUS,TERMS,mode,st at uscode.

or
ST,TES,mode,st at uscode.
Parameter Description
mode

statuscode

One of the following
mode

Keyword
Abbreviation Description

LINE =
elementname

LI elementname is the name of
the specified element.

LLINK =
elementname

LL elementname is the name of
the specified element.

Optional. If specifiedi only the elements with that status are
reported.
statuscode

Description

Active

Down

Disabled

Enabled

NPUs
The fourth form requests the status of all NPUs supervised by the CS.
The command format is:
STATUS,NPUS.

or
ST,NPUS.

Revision M

Network Operations 15-57

Status Network Element Command

SVCs
The fifth form requests the status of all archetype SVCs on a line.
The command format is:
STATUS,SVCS,LINE=line.

or
ST,SVS,LI=line.

Parameter Description
l i n e N a m e o f t h e s p e c i fi e d l i n e .
A CS does not keep track of the status of the various network elements. NPUs supply
the information required to satisfy the STATUS commands by sending messages to CS.
In the case of a multiple-element status request, the number of messages sent can
become significant. You cannot enter another command until all the messages are ^^
delivered and a READY., prompt is displayed. A controlling NOP, other NOPs, or the
DOPs can cancel a STATUS command by entering the interruption or termination
sequence (refer to the NOS Version 2 Reference Set, Volume 3 for details). A HOP can
cancel a STATUS command by using the slant (/) key.
When status is requested for a coupler, line, NPU, or terminal the normal response
to the STATUS command is one line of text. When status is requested for logical
links or trunks, two text lines may be returned (if the CS to which you are connected
is supervising NPUs at each end of the element, a line of text is returned for each /rt?_
end of the logical link or trunk). When status is requested for archetype SVCs on a j
line, a text line with the line status is returned and a text line for each active
archetype SVC is returned.

A&e&S

_,*33gv

15-58

NOS

Version

Analysis

Handbook

Revision

Summary of Network Operation Commands

j/p^?V

Summary of Network Operation Commands
Following is a summary of the network operation commands.

Control Commands for HOP
The following commands are available only to the HOP.
NAM K Display
Assign the NAM K display by using one of the following (refer to section 8, K-Display
Utilities, for additional information):
Command Description
K.AP=CS. Assigns the NAM K display to the communication supervisor (CS).
K.AP = NS. Assigns the NAM K display to the network supervisor (NS).
K.AP = NVF. Assigns the NAM K display to the network validation facility
(NVF).
K.AP = NETOU. Assigns the NAM K display to the network operator utility
(NETOU).
K.* Assigns the NAM K display back to NAM mode after it has been
assigned to CS, NS, NVF, or NETOU.
NAM Startup
Initiate NAM by entering NAM.
NAM Shutdown
The sequence of commands used to shutdown NAM is:
K.AP=NVF.
K.DISABLE,HOST.
or
K.IDLE,HOST.

Revision

Network

Operations

15-59

NAM Mode Commands

NAM Mode Commands
The HOP assigns the NAM K display to NAM mode before entering any of the
following commands:
Command

Description

DB'

Activates the inline debug code.

DE7

Deactivates the inline debug code.

DU7

Activates field length dump.

END

Clears the NAM K display.

Changes NAM's maximum field length.

HELP

Displays information about the NAM mode commands on the right
K-display screen.

Causes NAM to ignore alert requests.

LB7

Begins logging of the network traffic on the debug log file.

LE7

Ends logging of the network traffic on the debug log file.

LR7

Releases the debug log file.

RS7

Dumps the statistics data to the statistics file, resets the counters
to 0 (zero), and continues gathering statistics.

SEND

Sends a message to another HOP.

Causes the NAM status display to appear on the left K-display
screen.

7. These commands are supported by the network supervisory applications CS, NS, NVF, and NETOU. They
are ignored by IAF, TAF, and many other network applications.

15-60 NOS Version 2 Analysis Handbook

Revision M

/*^^\

NS Control Commands

0ms

NS Control Commands
The HOP assigns the NAM K display to NS before entering any of the following
commands:
Command

Description

FILE Assigns an alternate load file to NS for loading the specified NPU.
HISTORY Requests a display of the recent unsolicited status reports.
NOFILE Instructs NS to use the default NPU load file for loading all NPUs.
STATUS Requests the current load/dump status of NPUs.
NVF Control Commands
The HOP assigns the NAM K display to NVF before entering any of the following
commands:
Command Description
DISABLE Disables an application or all host network operations for both the
255x NPU network and CDCNET network.
ENABLE Enables an application.
IDLE Terminates an application or all host network operations for both the
255x NPU network and CDCNET network.
HISTORY Requests a display of the recent unsolicited status reports.
STATUS Requests the status of network elements.

8. To use the abbreviated form of commands, you can type the first two letters of the command. For
example, FI for FILE.

Revision M

Network Operations 15-61

Control Commands for HOP and NOP

Control Commands for HOP and NOP
The HOP assigns the NAM K display to CS before entering any of the following
commands. The NOP can enter these commands by logging into CS.
Command

Description

ALERT Changes the threshold that CS uses for alerting the NOP and HOP of
NPU saturation.
CONTROL Allows you to gain or give up control of NPUs.
DISABLE Changes the status of the specified elements to disabled.
DUMP Causes the memory dump flag to be reset for the specified NPU.
ENABLE Changes the status of the specified elements to enabled.
GO Activates the lines and accepts terminal device connections on an
NPU.
LOAD Causes active NPUs to stop, reload, and reactivate.
SEND Sends a message of no more than 50 characters to users.

Control Commands for HOP, NOP, and DOP
The HOP assigns the NAM K display to CS before entering any of the following
commands. The DOP and NOP can enter these commands by logging into CS.
Command

Description

INFO Accesses information about all operators and NPUs connected to CS.
HISTORY Requests a display of the recent unsolicited status reports.
REPORT Requests CS to report all unsolicited status messages from NPUs.
SEND Sends a message of no more than 50 characters to the HOP or
another NOP or DOP.
STATUS Requests the status of network elements.
TST Allows you to control interaction with an NPU diagnostic program in
the specified NPU.

Control Commands for COP
Refer to the CDCNET Network Operations Manual for information about control
commands intended for the CDCNET operator.

9. To use the abbreviated form of commands, you can type the first two letters of the command. For
example, IN for INFO.

15-62 NOS Version 2 Analysis Handbook

Revision M

,^*^n

Network
NAM

Utilities

Initialization

Network

Dump

Load

File

Input
Network
Summary

(NAMI)

Collector

(COLLECT)

Generator

(LFG)

Directives
Load
Listing

16-6
lg_9
16-10
1 6 - 11
1 6 - 11

File

NPU
Dump
Analyzer
(NDA)
Input
Directives
..'..
0
—
Comments
1
—
File
1
Register
,
2
—
Macromemory
Word
3 — Contiguous Block Data Structure
4
—
Circular
Buffer
Data
Structure
7
—
Page
Registers
8
—
File
1
Registers
,
9
—
Macromemory
Words
A
—
LCB
and
TCB/CCB
B.—
Port
Ta b l e s
and
MUXLCB
NDA
Output
File
Content
NPU
Dump
Files
Dump
Interpretation

16-12
16-14
16-14
16-14
16-14
16-15
16-15
16-16
16-16
16-16
16-17
16-18
16-29
16-30
16-30

PIP

16-31

AIP
IAFTM
IAFTR
Network

Dump

Analyzer

Trace

(LISTPPM)

With

Description

IAF

Files

16-32
16-32
16-33
,

IAF
Stimulator
STIMULA
..
Session
File
Construction
Dynamic
Login
Optional
Think
Time
S p e c i fi c a t i o n
Ta s k
D e fi n i t i o n s
Session
File
Processing
Multiple
Sessions
Parameter
Output
Format
,
Postprocessing

ig_2

16-34
16-36
16-37
16-37
16-42
16-43
16-44
16-45
16-50
16-50
16-52

Network

Utilities

NAM supports two types of networks: the 255x NPU network and the CDCNET
network. Throughout this section, the term network refers to the 255x NPU network.
However, whenever a statement is applicable to both network types, both types are
named explicitly.
This section describes the following utilities and files involved in the operation of the
networks and interactive subsystems of NOS.
• NAM Initialization (NAMI). This utility controls the network software startup
process.
9 Network Dump Collector (COLLECT). This utility produces tape files from the
various NPU, CDCNET device interface, and host dump, trace, statistics, and list
files that were generated by any abnormal termination of either the 255x NPU
network or the CDCNET network.
• Load File Generator (LFG). This utility produces a direct access file used by the
Network Access Method (NAM) to perform the downline load of network
processing units (NPUs).
• NPU Dump Analyzer (NDA). This utility produces readable listings from dump
files produced when NAM dumps NPUs.
• PIP Dump Analyzer (LISTPPM). This utility program converts binary records from
the peripheral interface package (PIP) memory dump file into a report listed in
byte format.
• Application Interface Program (AIP) Trace. This utility produces a trace file of the
messages transferred between an application program and NAM. The information
contained in this trace can be useful in tracking network problems and in
debugging application programs.
•

Network description files. Network description files are used by the Transaction
Facility (TAF) to describe user access characteristics defined by terminal definition
directives.

•

IAF stimulator. The IAF stimulator is a collection of programs that artificially
loads the system to analyze the effects of such a load on system performance and
reliability.

0$ms

Other utilities used with the CDCNET network are documented in the CDCNET
Network Analysis Manual.

Revision

Network

Utilities

16-1

NAM Initialization (NAMI)

NAM Initialization (NAMI)
The NAMI utility controls the network software startup process. The network software
consists of the NAM Subsystem and several rollable jobs (NS, CS, NVF, TVF,
COLLECT) and network applications (IAF, TAF, RBF, MCS, PTF, QTF, ITF). The
NAMI utility starts NAM and the programs NS, CS, NVF, TVF, COLLECT, and other
applications desired at the site such as RBF, QTF, and ITF by submitting jobs to the
input queue. The NAMI utility can also start the NAM CDCNET applications NETOU,
NETLS, and NETFS, although they are usually started by a connection request. The
skeletons of these jobs are contained on a master startup file along with parameter
records containing directives telling the NAMI utility what parameters to substitute in
the job skeletons and what jobs to start. Refer to the NOS Version 2 Installation
Handbook for descriptions of the master startup file, parameter records, and job
skeleton records.
The advantage of having the NAMI utility start up the network software is that
parameters that are common to more than one job or that change from one network
startup to the next can be changed easily.
The console operator enters the procedure call NAM or NAMNOGO to call procedure
file NAM or NAMNOGO respectively (refer to the NOS Version 2 Operations
Handbook). These procedure files (saved under the SYSTEMX user name) contain the
NAMI command, which calls the NAMI utility. The format of the NAMI command is:
NAMI.P1.P2 pn.

pi is a parameter consisting of a keyword or a keyword equated to a value. All
parameters are order independent.
Pi

Description

This parameter initiates the network startup process without
operator intervention.

MFN=filename

The permanent file name of the master file to be used. Once this
parameter is specified, subsequent network startups use this
master file until a new master file is specified. If this parameter
is omitted, the previously selected master file is used. The
master file must reside on the system default family.

OIN=nnn

The previous network invocation number (nnn) for which the
dumps/traces will be collected during this run. If this parameter
is omitted, the current network invocation number minus 1 is
used.

PW=password1

The password assigned to the user name where the master file is
stored. If this parameter is omitted, the previously selected
password is used. This parameter is not required if
UN=NETOPS is specified.

1. This parameter must be specified for the initial network software startup. It can be specified either on a
NAMI command or by an operator entry using the NAMNOGO procedure.

16-2 NOS Version 2 Analysis Handbook

Revision M

NAM Initialization (NAMI)

0ms
Pi

Description

RN = recordname 2

The name of the parameter record on the master file that is used
for this network initiation. Once this parameter is specified,
subsequent network startups use this same parameter record until
a new parameter record is specified. The following recordnames
can be specified.
recordname

Description

INIT

Purge existing dumps/traces, stop but do not
dump local NPUs at network startup, and stop
local NPUs at abnormal host termination. Use
INIT for the initial startup of single host
networks.

MINIT

Purge existing dumps/traces, stop local NPUs at
network startup, do not take NPU dumps before
initial loading of NPUs, and do not stop local
NPUs at abnormal host termination. Use MINIT
for the initial startup of multihost networks.

MRECOV

Purge existing dumps/traces, do not take NPU
dumps before initial loading of NPUs, and do not
stop local NPUs at network startup or abnormal
host termination. Use MRECOV for recovery
startup of multihost networks after a failure.

MULTI

Collect dumps/traces on tape before network
startup, take NPU dumps before initial loading of
NPUs, and do not stop local NPUs at network
startup or abnormal host termination. Use MULTI
for the normal restart of multihost networks.

RECOVR

Purge existing dumps/traces, do not stop NPUs at
network startup or termination, and do not dump
NPUs before initial load. Use RECOVR for
recovery startup of single host networks after a
failure.

RESTRT

Collect dumps/traces on tape before network
startup, take NPU dumps before initial loading of
NPUs, stop local NPUs at abnormal host
termination, and do not stop local NPUs before
network startup. Use RESTRT for the normal
restart of single host networks.

2. This parameter must be specified for the initial network software startup. It can be specified either on a
NAMI command or by an operator entry using the NAMNOGO procedure.

Revision M

Network Utilities 16-3

NAM Initialization (NAMI)

Description

RS=appldes

The 2-character application designator of the application to start
up. (appldes can be more than two characters, but only the first
two characters are used.) This parameter allows the specified
application to be started when the network is already operational.
It is not valid at network initiation. The application's startup job
skeleton must reside on the parameter record/master file specified
for this network initiation.
The following applications can be specified.
Application
appldes Name

UN = username 3

Description

Communication Supervisor

NETFS

CDCNET Network File Server

NETLS

CDCNET Network Log Server

Network Supervisor

NETOU

CDCNET Network Operator Utility

PSU

Printer Support Utility

PTFS

Permanent File Transfer Facility Server

QTFS

Queued File Transfer Facility Server

QTF

Queued File Transfer Facility

RBF

Remote Batch Facility

FTPI

File Transfer Protocol Interpreter

FTPS

File Transfer Protocol Server

TVF

Terminal Verification Facility

The user name where the master file is stored. If this parameter
is omitted, the previously selected user name is used.

3. This parameter must be specified for the initial network software startup. It can be specified either on a
NAMI command or by an operator entry using the NAMNOGO procedure.

16-4 NOS Version 2 Analysis Handbook

Revision M

NAM Initialization (NAMI)
jP^v

The first time the network startup process is executed, a permanent file is created
using a network invocation number of 1 and parameters from the NAMI command. The
initial call to NAMI must specify the filename, password, and username of the master
file and parameter record to be used or the console operator must enter them using
NAMNOGO.
On subsequent network startup operations, a permanent file exists and contains the
names of the last used master file, parameter record, and network invocation number.
Parameters from this permanent file will be used to start up the network unless
overridden by parameters from the NAMI command or parameters entered by the
console operator using NAMNOGO. The NAMI command parameters take precedence
over the permanent file parameters, and operator entries take precedence over
parameters from either the NAMI command or the permanent file.

Revision

Network

Utilities

16-5

Network Dump Collector (COLLECT)

Network Dump Collector (COLLECT)
The COLLECT utility is a program that produces three local files: one of the various
host dump, trace, statistics, and list files that result from any abnormal termination of
the network, one of any NPU dump files, and one of any MDI/MTI/NDI/TDI dump files.
The collected files may be copied to the three local files and then purged, or copied
and not purged. The local files will then be copied to tapes. There is also an option to
purge the collected files without copying them to the local files. The format of the
COLLECT command is:
COLLECT,NIN=nnn,NOPURGE,NOSAVE.

Parameter Description
NIN=nnn The 1- to 3-character network invocation number that indicates the
upper limit of the invocation numbers to be collected. All files with an
NIN value from 1 to nnn are copied to the local file. If NIN = nnn is
omitted, the default value is 1.
NOTE
NPUs that stop when the host network software terminates are
dumped during the subsequent network invocation. Therefore, the
network invocation number of these dumps is 1 greater than the
dumps of the host programs taken at the time of the termination.
NOPURGE Specifies that no purging activity will take place after the collected
files are copied to the local files. If NOPURGE is omitted, the collected ^%
fi l e s a r e p u r g e d a f t e r t h e y a r e c o p i e d t o t h e l o c a l fi l e s . N O P U R G E '
should not be specified if NOSAVE is specified.
NOSAVE Specifies that the collection process is not performed and the files
indicated by NIN=nnn are purged. NOSAVE should not be specified if
NOPURGE is used.
The COLLECT utility is automatically initiated by the network startup job (NAMI)
upon each invocation of the network. (COLLECT may not be automatically initiated if
the master file has been modified.) The utility receives an NIN value of the last
network invocation number. The current network will be initiated with an incremented
value of NIN. For example, on the fifth initiation of the network the COLLECT utility
has a command call of
COLLECT,NIN=004.

and the network is initiated with an NIN of 005.

•"*=%\

16-6

NOS

Version

Analysis

Handbook

Revision

Network Dump Collector (COLLECT)

The COLLECT utility processes all dump, trace, statistics, and list files whose file
names are in the form:
pptsnnn

Variable Description
pp 2-character product prefix.
PP
CS

Description
Communication

Supervisor

DI,...,DR,DS,...,D9 MDI/MTI/NDI/TDI Dumps
FS
IA
/^

Network

File

Interactive

Facility

INITMDI

Program

Interactive

Network

NI
NP

Network

Transfer
Log

Facility

Server

Interface

Network

Server

Package

Processing

Network

Unit

Supervisor

Network

Va l i d a t i o n

Network

Operator

Printer

Support

Facility
Server
Utility

PS Permanent File Transfer Facility Server
QS Queued File Transfer Facility Server
QT
RB
TI
TS
TV

Queued
Remote
File

File

Batch

Transfer

File

Transfer

Te r m i n a l

Transfer

Facility

Protocol
Protocol

V e r i fi c a t i o n

Interpreter
Server
Facility

y^fr^rj^

Revision

Network

Utilities

16-7

Network Dump Collector (COLLECT)

Variable Description
t

Type of file.
t

Description

Dump file.

List file.

Statistics file.

Trace file.

Subtype 0, 1, 2, or 3 for the file.

nnn

Network invocation number in the range 000 through 999.

In the case of NPU dumps (pp=NP), ts is a unique hexadecimal number identifying
the dump. In the case of DI dumps (pp = DI to DZ, or DI to D9), ts is a unique
character string identifying the dump. This character string is in the range from AA to
99. In the case of dayfile dumps, ts is DA. The files produced by the COLLECT utility
each have one file with many records. Each dump, trace, statistics, or list file is copied
to a local file as one or more records, where the first record copied is preceded by a
2-word record containing the original file name. This format enables an ITEMIZE or
CATALOG of a COLLECT utility local file to show which collected files were copied to
the local file.
The COLLECT utility assigns each file a file name of the form:
Form Description
DUMPnnn For host dump, trace, statistics, or list files, nnn is the network
invocation number from the COLLECT command.
DUNPnnn For NPU dump files, nnn is the network invocation number from the
COLLECT command.
DMDInnn For DI dump files, nnn is the network invocation number from the
COLLECT command.
The local files are copied to magnetic tape (or other operator-assigned equipment) if the
RESTRT or MULTI startup procedure is selected. Once the files are successfully copied,
COLLECT will be executed again to purge the collected files.
The COLLECT utility purges all dump and trace files without collecting them on a
local file if the INIT, MINIT, MRECOV, or RECOVR startup procedure is selected.

16-8 NOS Version 2 Analysis Handbook

Revision M

Load File Generator (LFG)

Load File Generator (LFG)
LFG is a utility program that reformats Communications Control Program (CCP) files
for subsequent use by the network supervisor of NAM to load NPUs. LFG accepts one
or more input files in single or multifile format and produces a single network load file
(NLF) for use by the network supervisor.
LFG is invoked with this command:
LFG,p1tP2 Pn-

pi is a parameter consisting of a keyword or a keyword equated to a value. All
parameters are optional and order independent.
pi

Description

BC-nn This parameter specifies the maximum number of load service
messages in a network load file record. It is used to optimize
NPU loads. 1 ^ nn ^ 64.
BC omitted Same as BC = 64.
I = infile The 1- to 7-character name of the file on which the input
directives are written.
I o m i t t e d S a m e a s I = I N P U T.
L = outfile The 1- to 7-character name of the file on which the summary
listing is to be written.
L=0 Suppress the summary listing. If an error is detected an error
message is written to file OUTPUT.
L o m i t t e d S a m e a s L = O U T P U T.
NLF = loadfile The 1- to 7-character name of the network load file.
NLF omitted Same as NLF = NLF.
Z An input directive is contained on the command after the
terminator. The I parameter is ignored. This eliminates the need
to use a separate input directive file when there are only a few
input directives.
When the input directive appears on the LFG command, the first
character following the command terminator is the separator
character. Any character that is not used in the input directive
can be used as the separator character. The input directive must
be preceded by a separator and terminated by a blank, period, or
the end of the input line (column 72).
For example, (slant used for separator):
LFG,Z./*FILE,PFILE1.PFILE2.

Z omitted Input directives are not contained on the command. The system
uses the I parameter.
0^S

Revision

Network

Utilities

16-9

Input Directives

Input Directives
Input directives have this format:
♦FILE.filenamei.filename2,... .filenamen.

An input" directive begins with an asterisk followed by the directive identifier FILE and
a string of file names. The directive identifier and file names are separated by
commas. If a specified file is empty, LFG ignores it. LFG scans a directive until it
detects a terminator or the end of the directive line (column 72). A directive is
terminated by a blank, period, or the end of the line. If an asterisk is not specified,
LFG assumes *FILE and proceeds to read file names. LFG continues to read input
directives until the end of the record.
Each file specified by filename contains a load partition or a program initiation
control block (PICB) for LFG to reformat. These files are created by the CCP
installation process (refer to the NOS Version 2 Installation Handbook). A load
partition is any loadable software module that can be loaded into an NPU during one
operation. For example, all of the software for CCP can be loaded into an NPU as
one load partition. A PICB consists of a sequence of commands that controls the load
or dump operations. For each step in a PICB that specifies a load operation there is
a corresponding load partition.
The names of the input files can be specified on the LFG command (Z parameter) or
in a separate file (I = infile parameter). In either case, these files must be local to the
job that runs LFG. LFG does not rewind the input files.
If the input directives are written on a separate record in a batch job (I = INPUT),
the job format is:
ujn.
USER,username,password,fami 1yname.
LFG,I=INPUT.
—EOR-•FILE,AFILE1,
.AFILEn.
file INPUT
•FILE,BFILE1,
.BFILEn.
•FILE.CFILE1,
.CFILEn.
—EOI—

"^55\

16-10 NOS Version 2 Analysis Handbook

Revision M

Network Load File

Network Load File
The network load file produced by LFG is a random access file with the local file
name specified by the NLF parameter of the LFG command. The default network load
file name is NLF.

Summary Listing
The summary listing produced by LFG is a summary of the network load file contents.
The summary is written on the file specified by the L parameter of the LFG command.
The default summary file name is OUTPUT. Error messages produced by LFG are also
written on this file. The summary listing format is:
N O . PA R T I T I O N N A M E I N P U T F I L E R E C O R D S
1
2
3
Field

PN1
PN2
PN3

AFILE1
AFILE2
AFILE3

3
7
2

Description

NO. Line number of the summary listing.
PARTITION Name of the load partition or PICB for LFG to reformat.
NAME
INPUT FILE Name of the input file on which the load partition or PICB
resides.
RECORDS Number of records in the load partition or PICB.

Revision

Network

Utilities

1 6 - 11

NPU Dump Analyzer (NDA)

NPU Dump Analyzer (NDA)
NDA is a utility program that produces a readable printout from the NPU dump file.
The NPU dump file may contain one or more dump records, which are created by the
network supervisor during the initiation or reloading of a failed NPU. NDA reports
depict the state of an NPU at the time a dump is generated. NDA uses the following
local scratch files during its processing: NEUFILE, ZZZZINP, and FDMP.
NDA is accessed by a command that allows selection of:
• Dumps from/to specific NPU macromemory addresses.
• Listing options.
• The input directive file.
• The output file.
The

format

the

command

for

the

NPU

Dump

Analyzer

is:

NDA.PLP2.. ...Pn-

Each parameter is a keyword or a keyword equated to a value. All parameters are
optional and order independent. If a parameter is not specified, a default value is
assumed. If the same keyword is specified more than once, the last (rightmost)
occurrence of the keyword overrides all previous ones. Invalid or undefined parameters
cause the run to terminate.
pi

Description

A H
3 «si-

M M M
M »H

ess
8 S

• b b . n o
O k> «
O O O

§ss

Figure 16-1. Sample NDA Output File

16-20 NOS Version 2 Analysis Handbook

(Continued)

Revision M

B — Port Tables and MUXLCB

(Continued)

■
«* » h. « <
S
o
o »S aS>oeu« >o oo «* >
A O O u n a n n m
^ O o n o I- «m
v o
n o
k» « •»

SS:

> «i o o r>

o o Or - -m
O
<*PPP©««Oh.
0
0
o pop
« <«* >o>o0 **< >
S
f oQ
5 o
5O
n
© «oaOo9Mn
* Ch
h.
B
o o o n m o o n
o S 00 o o o
fO
0 O
0 H
0 O
0 O
0 S
0O
0
o o o « o o o o
OO
o O
o O
o O
o O
o O
o O
o O
o
§ o
0 o
0 «0 O
0 0o 0
o 0
o
o o o o o o o o o
80o no
a o©p p© oo o
o o < « o o o o
g o o o N a o o B
8 O
0 0
O 0
ri p0 O0 O
0 O
0
O O O V O O O O

0 < < o » i o n « o o o
O Mo O
n po o
O
o tbb Oo m
o oo

r - > Q 0 4 r " O p p O O Q O Q Q O O > - O O p O « O O O r 4

o o S p i o 5 5 o o o o o o o c M n o o o Q o a o Q O « t
8 OO OO OO OOQOOOO OO OO OQ O
O O
O O O O
O IO0 NO O
O O
O O 9O >B »OO OO Oa *»

O k l O O t n O O O

p 0 > OOOOOO( O
- lO
OO
QO
OQ
0
O
p p o
p opo oo oo ooo o
fn
o

3-1 S:SSSloSSiSSSl§iSSSSiSSSSS§SS8
S ot oo po po oo oo p5pop5popoooooooo op oo oo op oo oo oo oo oo oo oo oo o
oo
o
<
09 O

! o a o O M O . o - 4 ( x n « m « r > ( o o > < c a u O

A
Z
N
T
A
O
L
ITIN

0
w nOpC of t o
nt pt ion O
pO
oO
o
H
O
O UOUf O
OOO
O
5
o«««o«ooo

o t

D O H N n « i n i I > N

O
P

3
tm

Figure 16-1. Sample NDA Output File

Revision M

(Continued)

Network Utilities 16-21

B — Port Tables and MUXLCB

(Continued)

Z*6^^

n u o t p o o m o r )
o
h O 3 o«n ■>
m 8«u «
Sen
o
O w
M .3

s>
o e 9 9 •>• © o o 90o po ooo oo oo6 po oog oo o9 o ©
m p p o5 o5 o5 9
o o 5 55 oSp5o 5o pr*p op p9 pg' -99
9 0 9 9 9 9 © © 2o

5
g »52 55 2
SS
5 o 5 35 5 oQoo oo »
o «o noHoo «o oo N5 Oo p00
6 20 2oS oS pS o
o

° « 8giii88S8ss:iisii§siiiiii8
K« * ufi«hS3SS:S25SS52ilS3!:8SK5SS!558Si5S8S8ft

Figure 16-1. Sample NDA Output File

Revision

Network

Utilities

(Continued)

16-23

B — Port Tables and MUXLCB

(Continued)

O m O O O N O p O O O O O O O i o m o o o o o o o o o o o o
ox a O
US Sr - aki oO. >OOePOo OoH o»po9Oa<>MO. . o p p
. . p m. o
- j oo pop o©p oo p©o oo poo oo ooo pp p00>D
o 8 8 h . o S 8 8 S 8 e © 8 8 8 S 8 8 8 8 S 8 o o o '

g (0

_ §a

D
MB
o» o o- •

8S£!
ggg!

§ 0 0 0 0 0 0 0 0 0 0 0
_
9 O
9 P
9 O
9 O
0O
0O
0O
0
'9
O9
O9
O9
OO

8 g
gmta
n 8 °• fn p p 2p 2«Q0 9' *r 0i 9' 4< i>-ni n« n0 oo oo p5 eoo o
0c a
0 a- o
0 o0 o0 <0^ 04 0p *o 0p 9
0

• H
©888gC

M X I
M F
ac m 1

go♦
•O O
1'

g§
O O O

§ O
9 o
o o o o Po Po O
o po O
o
_
O nO op oO or >
o <
o o o o o e > o o o o © o o o o o o o o ooo oo oo ooooo op oo ooo ©o oo gog oo e
H

'OHnn«m«NB»oon«r>-992
SH« I «Coo

S rc» uo S
o ro» oo »n - og og go
S
2 om» nN £3 «c o
H «SaNn 0o 9
o

SsssssKggg
& n « N R H « M O O

§h. 9 o
2 e» o o

» N a o « o n o o

i swgogogpgp go gwgogogogo go gg go go go gp

o m o « M o o o * o o o o o o o o o o

8
C
a
o
0

-E

S h O p n i t N O O O
5r.*Qor«c«o99
e»r«a>o«Of»oo

MlbOO^UOpOO
tCVOOr^OOa
OO
S dt0f o
o
> Oo Op Oh« oO a
OOO

ca
o a « « Q o e « o o o o o o o o o

&
:OHMn«m * « n 4 > r > c a o « « c a u O H h .

b. o

Figure 16-1. Sample NDA Output File

(Continued)

^*s
16-26 NOS Version 2 Analysis Handbook

Revision M

B — Port Tables and MUXLCB

(Continued)

2 ~

0 C '
S .O
U B
ri
o. OO

3
o>8
oi

°88S

O O <
O O CO
O 9 03
O O O

a
o 8
8 u
n yi o8
no o
o

> HcoOm O
o
a o co

8
o8
58
o

£ 3 8 8 §82

o
o
p
5

•a co

r. O r4

ill

n © a

l> «n

iss

o o

■> o i i f c . f c . . - < O t f » o o g r .
oogx
g ca o p© oo p> po po o o* i. Mo no o pr no oo o i obc O
o
OO©9fc>fc.©an«4*©h.aOP-C0
■n u n m O O O O O U O H O U H
§ 0N> < Co DoOo> o
UO
« Oo Oo OoO HO Ii Mg M« I M
a O
B

IM © ri

< m 9
eu
5

M
©

ta
O O O O O O O O O O O O O O O O O O
M
c
o
o
o

O
u
o
o
o

~4*ino
o o o o o o o
o o p p o o
o o o o o o
o o o o o o

rg
o
o
o

B
o
o
o
o

O«S

Revision M

Network Utilities 16-27

B — Port Tables and MUXLCB

(Continued)
OV

t-l-V

CO.

•-

O fc. O h. fc. o
O fc. O fc. fc. o

8 0
o r ja;
O * O CO O O 1
O O f * M f c . C 0 O O O © O O O 9 O O O O O 9 O * l g f c . 0 > © g O f c . f c . f c < O O p p p O p P O < f c . h . t ] . t ] . h . © f c . O b . h . O fc. b.
o < - > p h . o i H p « o o o o o o o o o o i - i o > * e o h . h < g o g f c . & t a . o o © © 9 g 9 o o o f c . i b f c . h . b . o f c . o b . i b
8 1 b . 0b0.
§ oo gO f f cc .. p5 -© 45 po »5 p
o o oo O
g H
g i* n* m
* *« gn cS no g
O oo *a go to bn m
o og og og t Ci .b h t . >o . o g ©g o g o o© g o gO o f o- io on o o f fc c. ih D. tb > M. b
| i . . i b b . *O bb . . *o ( f bc f. cbf c. . O f c . f c .

o o o r>
a oo oo o o o o p r H p i M p g o g
m
o o o o o o o o o o o S o O

8 OOpUa}pb.fc.pOOfc.fc.fc.pOp5ppC
9 fbcP. O
9 0OUOOOf O
c .Oi >
- ©C9M9 p f c . f c . o o o 9 © o b . -o o i M 9 9 9 o O
o oO
o ©Oo o©o- o
CM
H
*O
0 0 « - > 0 < * 0 f c > m o o o c i . t b 0 0 0 0 p 9 0 p 0 r ) 0 < - i 0 r v 0 ( 0 0 0
o © © o p
0 0 0 0 * 0 0 0 0
o o o o o
v w i x * x * * * r . B . r t
t> n CM m O <0 tt rt

.
OOtbCbOOSCfcSfc'
O
- fO
c .CpM
l -a- 3
0<
O f c . o o g g g f c . o o o f c . o g <
OU
O fOc O
< «
o o o o -o © o o f c . o o o b . o 5 '

gO
O ni «
>O
> O
N O
i Hr N
U U
OM
l l Cl «M Or -Op Oi bt C
i Ob O
OO
OO
O
- pl *i pO OU OOOOOOf O
c .O« eC o t n » o © o o g g g g g g © g g £ . - < g i " i o f c . i n o g g g f c < o o o © o o o o © o o * g ' C M O o o
o o o g < o p o p o p o o o o o g o o o o f c i o p * < M o p o o o f c . p o u 9 o o o o o o o c o o p o o o
O O O O O O O O O O O O O O O O O O O O r ) ^ O O « 0 O O O O O O t b 0 O b . O O 0 O O « n O C 0 O O O O O
0 0 0 * - H p O o
0 © 0 < n © © i n H
o o p o o o o o

OOO99*C0OO6OOpOO
(OOOOOOf-pOOppOOO

ooooooo5oo55ooo

§ gO gO o « >O 4 O. O4 O
l -O i 0c 0M O o Oo Co Mo O
o *o *g Ov O> Ot nO or -o Og ao f r c« . or o. Oh C
< ao .. 0o 0> Oa f > c o. gO oO f Oc C. hg O
p O
o uO of co .o Ou Oo Oo O
r -© o( oM oO o* oO oO oO o Oo Oo Oo Oo O
o
m o g o o o g g o g o o oO o Oo Ou CM
c > oo o * p0 - 0 r r H- O. 0O 0r .H 0 o 0< 0 C 0 D O o o b . o o p o t i . o f c . o o r H o o O ' - o e d r - i o c o o o o o o
O O O O D b O O O O f c . O h . O O O O O O « O I M U O C 0 O O O O O

888

0 0 0 0 0 0 0
u O O O O O i —
* O O O O O 1

fc.fc.fc.fc.b.tbfc.b.b.fa.b.0

O r 4 0 r i * < H O » . H r 4 f c . b . O O U f c . l

o g a g g g h . o o o o o © © © o o f c . < - . o © © o o o o o o o o o
O C 0 b . O O O b . O O O O O O 9 P O O r i l M O * O O O O O O O O O O
O O o 5 h . O O f c . O 8 Uf pc U
. Oh C
. Cb 0b p. rO 4 OO * « Or M
H O
U C
O 0O OO r O4 O
O O
O O
O O O

..00©fc.fc.OOOOOOO©OUO
O r - 0 * C M O C M M H p U f c . p O O O O O p © m b . C M _
O _O
. O
O- 0~0' «~ o ~
« mCbb. O
0 0P »C*M
0 f0c0>0g0g0g0«0* i«n«opo^r <. o< _O iCnl O
_o O
_p O
._ff c.c .. bf .c O. pOp_O9_O
_g «o Dp »f cO. p_p f_f cc .. bt .b hb -. 0,hff fcc. c..- bO.. ._fffcc.c.f..fchct ...b_bt fb.. bc_f c..iO.O**f_b—
c .i O
*
. pOn n
o fUc h. >
g b
g_o
0_ O
9_ 0O
.*
> f c . O O O f c . O O O . - l i n . - i i n o O O O « O O O O O O O h . f c . b . b < O O O O O O O b . O
fc.li.h.b.fc.B-rb.b.Ob.0

O l-l ©
_ O rt I
__
O _ 0 0 0 f c . O O O O * * * 0 g 0 g U 0 0 O O O r 4 «
M 0 0 0 C M t _ . i - . PO 0 O1 _
0 « O < C M
§ 0 O f fc.
c. b . O O © O r . O O O O O 0 _ O
sa
«
c o o o o o o o o o o o o o o o o o o o o o o o

_pd«*0Ufc>0OO0O0Opr>b.UO«**OOpOfc.r'-fc.fc.UQO0fc.000000QO9©O0OOOOO
0 i n O O O f c . f c i f c . b . f c . O O O O 0 0 O U O O O O O 0 0 O 0 0 0 O 0
i n a n O h . O O O f c . h . f c . O U O 0 O O U O * C D O ^ O C 0 O r H O C M O O O 0 O
o o o o o o
U b . 0 h . 0 0 0 0 f c . 0 0 < 0 0 0 0 0 C C > 0 * 0 0 0 0 0
«
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o

fc)0>-lbOr4CMfn*inor.ininnmninn 1

0$m*\

FORTRAN
NEW.MATH
10 PROGRAM MATH
20 1 CONTINUE
30 READ 10,A
40 IF(A.EQ.O) STOP
50 B=A*A
60 C=SQRT(B)
70 IF(A.LT.O) D= -C**3
80 IF(A.GT.O) D=C**3
90 PRINT 20,A
100 PRINT 30,B
110 PRINT 40,D
120 GO TO 1
130 20 FORMAT (' A EQUALS ',F15.3)
140 30 FORMATC A SQUARED = '.F15.3)
150 40 FORMATC A CUBED = '.F15.3)
160 10 FORMAT(F15.3)
170 END
>>
RUN
2.0
0.0
25 PRINT 50
155 50 FORMATC ENTER VALUE ')
LIST
RUN
1.0
2.0
3.0
4.0
0.0
160 10 F0RMAT(F12.1)

Source 11ne 1nput

Program Input

Figure 16-3. Sample Session for Use by STIMULA

Revision M

(Continued)

Network Utilities 16-39

Session File Construction

(Continued)
LIST
RUN

10.0
11.1
13.3
0.0
160 10 FORMAT(F12.3)
LIST
RUN
15.555
40.0
50.0
0.0
LIST
RUN
10.0
20.0
30.0
40.0
0.0
ENQUIRE,T
DAYFILE
BYE

Figure 16-3. Sample Session for Use by STIMULA

16-40

NOS

Version

Analysis

Handbook

Revision

Session File Construction

ANSWERBAC
FAMILY,USERNAM,PASSWRD
BASIC
OLD
TESTB
LIS,294
RUN
01000
REPLACE
BYE
•E-O-R*
additional
sessions
•E-O-F*

Figure 16-4. Sample Session File for Internal Stimulation
K.

STM

hh. mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
STIMULA
PARAMETER

DESCRIPTION

F = STPTEST SESSION FILE NAME (1-7 CHARACTERS).
UI «= 137 USER INDEX (0-377777B).
N = 1 NUMBER OF FILE ON SESSION FILE (0-377777B).

r
ENTER K.GO T
O BEGIN PROCESSING OF SESSION FILE.

Figure 16-5. STIMULA K Display (Left Screen)

y^WSy

Revision M

Network Utilities 16-41

Dynamic Login

Dynamic Login
If each of the terminals to be analyzed is logged into the system with a unique user
name and password, a unique session record for each terminal is stored in central
memory at the IAF stimulator control point. Thus, a large amount of central memory
could be unavailable to other components of the system. To alleviate this condition,
dynamic login is possible, whereby one session record is generated with a unique user
name and password that are dynamically translated into unique user names and
passwords for each terminal at run time. The generated user names and passwords are
then validated via system validation files. The format choices are:
username$$$
or
username$$$,password$$$
Parameter Description
username User name; 1 to 4 alphabetic characters.
password Password; 1 to 4 alphabetic characters.
$ Special symbol 12/8/6 (6-bit display code 76s), 1 (6-bit display code 34s)
punch; that is, 12/8/6 punch in one column and 1 punch in next
column.
NOTE
The $ denotes the special symbol previously described, not the
character itself. The $ character is translated into the IAF stimulator
terminal numbers at run time.
Example:
P$$$,P$$$ is translated into P000,P000 for the first terminal, into P001,P001 for the
second terminal, and so forth.

16-42 NOS Version 2 Analysis Handbook

Revision M

<^®5\

Optional Think Time Specification

Optional Think Time Specification
Think time is the number of seconds that each line is delayed before it is sent through
the interactive system. A random think time can be specified with a session file
command. The format of the command is:
> number
Parameter Description
number Think time (octal): number ^ 1778.
To return the terminal to the initial think time (refer to figure 16-6), enter this
command:

STM

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID*AA NOS version
STIMULA
PA R A M E T E R

DESCRIPTION

NT = 310B NUMBER OF TERMINALS TO STIMULATE (1-310B).
LS = 15 LINE SPEED IN CHARACTERS/SECOND (1-1000).
IS = 15 INPUT SPEED IN CHARACTERS/SECOND (1-1000).
TT = 10 THINK TIME DELAY IN SECONDS (0-127).
TI = 8 RANDOM THINK TIME INCREMENT (A POWER OF 2 0-64).
THINK TIME WILL VARY BETWEEN TT AND TT+TI.
AC = 4 NUMBER OF TERMINALS ACTIVATED EVERY AD SECS (1-64)
AD = 10 ACTIVATION DELAY IN SECONDS (1-127).
RC = 0 NUMBER OF TIMES TO REPEAT STIMULATION (0-31).
LD = 0 LOGOUT DELAY (0-4095).
RO = ON OUTPUT RECOVERY (ON OR OFF).
LF = NO LOPP ON SESSION FILE (YES OR NO).

Figure 16-6. STIMULA Parameters (Left Screen)

Revision

Network

Utilities

16-43

Task Definitions

A*ms

A task is a predefined set of interactive commands designated by a task name and a .)
task usage parameter. Tasks can be called throughout a session, and the task usage
parameter is used to determine which task is the next most eligible task (that is, the
task to be called next).
An I character (6-bit display code 70s) in the session calls the next most eligible task
in the session file, which is determined by the following equation.
Total initiations of task*
fi a t

(Total Initiations of all tasks)(Task usage parameter for taski)

For each taski defined in the session file, the IAF stimulator calculates fi, and the task
with the smallest f value is the next most eligible task. Multiple \ characters are
permitted on one line and are treated as if they occurred on separate lines. For
example, ttt ca^s the ^rs^ three most eligible tasks, where eligibility is recalculated
after each initiation of a task. If a task is called and the IAF stimulator cannot a^^s
determine the next most eligible task in the time allotted, the first task defined in the
session file is used.
Tasks for the IAF stimulator are defined in the session file as task records following
the session records. Tasks are not permitted in the file before session records. The
tasks should be defined in descending order according to the task usage parameter.
This facilitates use of the first task defined as the default next most eligible task in
situations where the IAF stimulator fails to calculate the next most eligible task on
time.
The first line in a task record must be:
$task nnn

Parameter Description
$ Denotes the beginning of a new task (character position 1).
task The 1- to 6-character task name.
nnn Task usage percentage; 0 ^ nnn ^ 100 (character positions 8, 9, 10).
The task usage percentages of all tasks in the session file must total
100.
The last line in a task record must be a I character (6-bit display code 71s), which
returns control to the calling session. An example of a session file with tasks defined
is shown in figure 16-2.

16-44

NOS

Version

Analysis

Handbook

Revision

Session File Processing

Session File Processing
The IAF stimulator software is used to process the interactive session file following
this procedure:
1. Ensure that an IAF stimulator entry is present in the EQPDECK and that the
IAF stimulator has an ON status (refer to the section 3, Deadstart Decks). ON
status must be set before IAF is active at a control point. If the status has been
changed to OFF, idle IAF and then set ON status and reactivate IAF. The IAF
stimulator entry must be on a channel that is not used by any other equipment
that currently has a status of ON.
2. Use DSD to activate the IAF stimulator.
Enter STMflff, where ffff is 0 to 4 alphanumeric characters. This entry calls a
procedure file STMffff, which must be a permanent indirect access file stored
under the system user index (377777s). The procedure file STM is called when you
enter STM. The IAF stimulator is invoked by a STIMULA command within the
STM procedure file. The IAF stimulator requests the K display.
3. Enter K,STM. Figure 16-5 appears on the left screen.
4. Enter the session file parameters individually as listed in the following format
column or as a group on the same line in the format.
K.F=f1lename,UI=userindex,N=n,GO.

Format
K.F=filename

Default
None

Description
filename is the indirect permanent file name of
the session file.

K.UI=userindex 0

userindex is the user index of file filename.
The default family is assumed.

K.N=n

n is the number of files to be skipped on file
filename before data is read from the session
file; range is from 0 to 377777s.

K.GO

None

Indicates to the IAF stimulator that all the
parameters have been entered or that none are
to be entered.

Figure 16-6 appears on the left screen.
To display the mixed mode parameters, enter:
KK.

Figure 16-7 appears on the right screen. Then, enter:
K.MIXED.

Figures 16-8 (left screen) and 16-9 (right screen) appear.

Revision M

Network Utilities 16-45

Session File Processing

K DISPLAY COMMANDS
G O B E G I N S T I M U L AT I O N .
MIXED DISPLAY PARAMETER MATRIX AND ENTER MIXED MODE
PARAMETER ASSIGNMENT.

Figure 16-7. STIMULA K-Display Commands (Right Screen)
6. Enter the parameters (refer to figure 16-6) individually as listed in the following
format column or as a group on the same line in the format.
K.NT=n,LS=s,IS=s,TT=n,TI=1,AC=m,AD=d,RC=n,LD=d,RO=o,GO.
Enter any mixed mode parameters (refer to figure 16-9) before the GO entry.
Format

Default

K.NT=n

Current EST n is the current maximum number of
value terminals on which the Interactive Subsystem
is initialized. It must be less than or equal to
the number specified in the EST entry; the
range is from 1 to 10008.

K.LS=s

15 s is the line speed in characters per second at
which you want to run the terminals; the
range is from 1 to 1000. Any value above 60
characters per second causes a line speed of
approximately 60 characters per second. If
many terminals (6008, for example) are run,
the maximum realizable line speed is
determined by the overhead of 1TD and ITS.
The worst case can be determined by checking
the 1TD cycle time dayfile message, which is
issued when IAF is dropped.

K.IS=s

15 s is the typing speed in characters per second
at which you want to run the terminals; the
range is from 1 to 1000.

K.TT=n

10 seconds n is the number of seconds (think time) that
each line is to be delayed before it is sent to
IAF; the range is from 0 to 127 seconds.

K.TI=i

8 i is the number of seconds by which the think
time will vary; the range is from 0 to 64 and i
must be a power of 2. If i is nonzero, the
think time varies between n (the value of TT)
and n+i.

K.AC = m

4 m is the number of terminals that are to be
logged in every d seconds (the value of AD);
the range is from 1 to 64. The AC and AD
parameters provide a method to stagger the
I/O commands and data to IAF.

16-46 NOS Version 2 Analysis Handbook

Description

Revision M

Session File Processing

00&\

Format

Default

Description

K.AD=d

10 seconds

d is the number of seconds of delay time until
the login of another terminal is allowed; the
range is from 0 to 127 seconds.

K.RC=n

n is the number of sessions that will be
executed for each terminal; the range is from 0
to 31.

K.LD=d

0 seconds

d is the number of seconds of delay time after a
logout is completed until the next login of the
terminal is allowed; the range is from 0 to 4095
seconds.

K.RO=o

When RO=ON, the output from IAF is
recovered on file STIMOUT. The format of this
file is:
69

Terminal Each byte is an ASCII character if
number. less than 4000s; otherwise, it is the
running-second time.

j0*M^\

When RO=OFF, the output is not recovered.
K.LF=o

NO When LF=NO, looping occurs on the session
assigned to the terminal. When LF=YES, the
subsequent session is the next session in the
session file.

K.MIXED

No mixed Specifies that mixed mode parameter
mode assignments are required for specific input
parameters sessions. This command displays the stimulation
entered parameter matrix (refer to figure 16-8) whose
values can be changed as described in the right
screen K display (refer to figure 16-9).

K.MX=si-s2,
ttys,ls,is,
tt,ld,rc

Current Mixed mode input, si is the number of the first
value session to be changed, and S2 is the number of
the last session to be changed. S2 is optional; the
default is si. (Refer to figure 16-9 for other
parameter descriptions.)

y^s

00ms

Revision M

Network Utilities 16-47

Session File Processing

Format

Default Description

K.CF=filename None

Matrix change file. Indirect access file filename is
accessed for mixed mode input directives, and must
be saved under the same user index as the session
file.

K.+

None

Page matrix display forward to the next screen.

K -

None

Page matrix display backward to the previous
screen.

K.GO

None

Indicates that all parameters have been entered.
Stimulation is initiated.

Example:
K.MX=2-4,3,30,30.,,1.

Three terminals will be assigned to sessions 2, 3, and 4. The line speed and input
speed for these terminals will be 30 characters per second. The think time and logout
delay will not be changed from the current value. The terminals will have a repeat
count of 1.

16-48 NOS Version 2 Analysis Handbook

Revision M

/*""*8S\

Session File Processing

Xp^^y

STM

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA
NOS version
STIMULATION PARAMETER

MATRIX

NUMBER OF TTYS ASSIGNED
MAXIMUM TTYS PERMITTED

200
200

CF = CHANGE MATRIX CHANGE FILE (1-7 CHARACTERS).
SCRPT

TTYS

1
2
3
4
5

40
40
40
40
40

LS
15
15
15
15
15

IS
15
15
15
15
15

R
C

10
10
10
10
10

Figure 16-8. Parameter Matrix (Left Screen)
K DISPLAY COMMANDS
GO BEGIN STIMULATION.
+ PAGE DISPLAY FORWARD.
PAGE DISPLAY BACKWARD.
MIXED MODE PARAMETERS
MX=SCRIPT,TTYS,LS,IS,TT,LD,RC.
SCRIPT SCRIPTS WHICH THE PARAMETERS WILL AFFECT.
SCRIPT(N) OR SCRIPT(N)-SCRIPT(N+X).
TTYS NUMBER OF TTYS ASSIGNED TO SCRIPTS.
LS LINE SPEED ASSIGNED TO SCRIPTS.
IS INPUT SPEED ASSIGNED TO SCRIPTS.
TT THINK TIME ASSIGNED TO SCRIPTS.
LD LOGOUT DELAY ASSIGNED TO SCRIPTS.
RC REPEAT COUNT ASSIGNED TO SCRIPTS.
NULL PARAMETER WILL KEEP CURRENT VALUE.
CF=XXX CHANGE MATRIX VIA PREDEFINED PARAMETERS.
XXX = PERMANENT FILE CONTAINING CHANGE DIRECTIVES IN FORMAT
MX=SCRIPT,TTYS,LS,IS,TT,LD,RC.
Figure 16-9. Mixed Mode Parameters (Right Screen)

Revision M

Network Utilities 16-49

Multiple Sessions

Multiple Sessions
Each session on the session file is allocated to each terminal line. When each session
has been allocated, the IAF stimulator goes to the first session and reallocates the
session to the next group of terminals. This procedure is repeated until all the
terminals are allocated to a session. If a repeat count is not designated (RC
parameter), the line is shut off when the session is finished. When the session
completes, the repeat count is checked.
The repeat count corresponds to the number of sessions to be executed on a given
terminal. The current session is completed, and the LF parameter determines the
next session to be executed. If LF=NO, the session currently assigned to the
terminal is repeated. If LF=YES, the next session in the session file is executed. For
example, if the repeat count is 4, the session currently assigned to the terminal is
repeated four times (LF=NO), or the next four sessions on the session file (with
repetition, if necessary) are executed (LF=YES).

Parameter

Output

Format

""^

The parameter information (shown in figure 16-10) is placed on the output file for
printing upon completion of the IAF stimulator run (refer to Session File Processing
earlier in this section).

16-50

NOS

Version

Analysis

Handbook

Revision

Parameter Output Format

STIMULATOR PARAMETERSSESSION FILE NAMEUSER INDEXNUMBER OF THE FILENUMBER OF TERMINALSLINE SPEEDINPUT SPEEDTHINK TIMERANDOM THINK TIMEACTIVATION COUNTACTIVATION DELAYREPEAT COUNTLOGOUT DELAYOUTPUT RECOVERYLOOP ON SESSION FILEMATRIX CHANGE FILE-

SSCC1

UI =

N=
NT=
LS=
IS=
TT=

100B

30
10

TI =

AC=
AD=
RC=
LD=
RO=
LF=
CF=

ON
NO

STIMULATION PARAMETER MATRIX
SCRPT

TTYS

1
2
3

22
21
21

LS
30
30
30

IS TT
10
10
10

LD RC

NUMBER OF TTYS ASSIGNED = 64
MAXIMUM TTYS PERMITTED = 64

0ms.

TASK CALLS COMPLETE DESIRED % ACTUAL %
TASK0
TASK1
TASK2

848
509
340

818
492
327

50.000
30.000
20.000

49.970
29.994
20.035

T O TA L S 1 6 9 7 1 6 3 7 1 0 0 . 0 0 0 9 9 . 9 9 9
DEFAULT TASK CALLS = 15

Figure 16-10. Output Statistics

Revision M

Network Utilities 16-51

Postprocessing

Postprocessing
The postprocessing of the IAF stimulator output is accomplished by reading the file
STIMOUT and sorting the data according to terminal number. Use the DEMUX
command to do this. As DEMUX sorts STIMOUT, it assigns an encounter number
(starting at 1) to the output from each terminal session. DEMUX includes this number
in the final line of each sorted terminal session output. The data for each terminal is
separated by a page eject and an end-of-line indicator. The terminal data appears as it
would on a terminal page. If the ASCII character on the STIMOUT file is 4000s or
greater, the lower 10 bits are assumed to be time of a carriage return or the first
character of output. If STIMOUT will be processed at a later time, you should save it.
Figure 16-11 shows an example of output from DEMUX.
ANSWERBAC

WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978, 19XX.

A^^S,

yy/mm/dd.hh.mm.ss.

END

THE

LINE

(Page Eject)
ANSWERBAC

Figure 16-11. Postprocessing Example
In figure 16-11, *****TTT.TTT is optional output, and the n in the previous listing is
the decimal encounter number.

^*^^\

/"^S\

16-52 NOS Version 2 Analysis Handbook

Revision M

Postprocessing

The format of the DEMUX command is:
DEMUX,P!,p2 Pn-

pi is either a keyword or a keyword equated to a value.
pi

Description

I=filename

Name of the file containing IAF stimulator data.

I omitted

Same as I=STIMOUT.

Specifies that the input and output files are not to be
rewound.

NT=n

Number of terminals to be processed (0 < n < 512). This
tells DEMUX how much memory to allocate to process the
input file. If no post radix is specified, octal base is
assumed.

0=filename

Name of the file to receive translated session output.

O omitted

Same as 0=OUTPUT.

SL=terminalnumber

Selective terminal number (within the range specified by
the NT=n parameter) to be processed, terminalnumber is
the terminal number minus 1 in the T display. If SL is
omitted, all terminals within the range specified by the
NT=n parameter are processed.
Specifies that the time of each carriage return and first
output character is written with the processed data.
Subtracting the two time values gives the response time.
The time values can also be used to correlate data between
each terminal's input and output.

Revision M

Network Utilities 16-53

Postprocessing

Example 1:
Following is an example of a procedure file called when STM. is entered at the
console. It executes the STIMULA command and performs postprocessing of the IAF
stimulator output. The procedure file must be stored as a permanent indirect access
file under the system user index (377777s).
.PROC,STM.
STIMULA.
DEMUX,NT=310,0=NOS,T.
GET,RESB/UN=username.
RESB.

Procedure file name.
The IAF stimulator is executed.

ASSIGN,NE.TRASH.
DFD,OP=I,L=TRASH.

The system dayfile is dumped to null equipment.

REQUEST(T) IDLE IAF.

Processing stops until IAF is idled. Also, ASSIGN,STM,2
should be performed.
A partial dayfile dump is performed that includes IAF
statistics.

DFD,OP=I.
ATTACH,ERRDATA/M=W.
COPYEI,ERRDATA,OUTPUT.
EVICT,ERRDATA.
RETURN,ERRDATA.
EXIT.
DIS.

RESB is a user-created program to analyze DEMUX
output.

Output of all failing jobs is copied to output.

In the previous procedure file, output from failing jobs is copied from the file
ERRDATA. In order for ERRDATA to contain this information, another procedure file is
necessary to collect data on jobs that fail and place this data in ERRDATA. This
procedure file (called ERRCHEK in the next example) should be called in the following
manner after each IAF stimulator session.
GET,ERRCHEK/UN=username.
ERRCHEK.

16-54 NOS Version 2 Analysis Handbook

Revision M

Postprocessing

yms

Example 2:
Following is an example of this procedure file.
.PROC,ERRCHEK*I.
IF.EF.NE.O.EXIT.

DISPLAY,EF.
ASSIGN,MS,OUTPUT.
ENQUIRE,A.
DAYFILE.

/!^^\

ATTACH,ERRDATA/UN=USername,M=W,NA.
SKIPEI,ERRDATA.
REWIND,OUTPUT.
COPYEI,OUTPUT,ERRDATA.
RETURN,OUTPUT,ERRDATA.
COMMENT.FAIL*
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
COMMENT.FAIL
EXIT.
REQUEST,FAIL. ERRCHECK FAILED.

If certain jobs normally cause compilation
errors, additional procedure should be included
to allow for these special cases.

Data is gathered on which program and which
statement caused the error.
This data is placed on file ERRDATA, which is
used later during postprocessing.

These comments warn users that failures have
been encountered.

If serious problems have been encountered, DIS
could be brought up at this point.

ENDIF,EXIT.

Revision M

Network Utilities 16-55

Postprocessing

Care should be taken when comparing response times between different versions of the
operating system with the IAF stimulator. Other factors may have a significant impact /*^\
on response time. Be aware of these factors:
• The entire parameter set should be the same for each IAF stimulator run. The
rate of activation of terminals, for example, can significantly impact response
time.
• The hardware configurations must be identical. If an attempt is made to measure
small differences, all devices that cannot be restored to their original state
(normally temporary devices) should be deadstarted and fully initialized.
• If the possibility exists that permanent files have been destroyed, these files
should be restored before each run. This can be accomplished easily by
maintaining a copy of all required files under a user name not used during the
stimulation. A procedure file can then be called to restore the files before each
IAF stimulator run. This is important when stimulation loads are causing
abnormal job failures. A REPLACE shortly after an unexpected abort may cause ^^
incorrect
information
to
be
written,
for
example.
'"^^
• Job processing must be the same for each IAF stimulator run. When many
terminals are to be analyzed, random job failures may be overlooked. These
failures may, however, affect the entire results of the IAF stimulator run. To
minimize this problem, it is necessary to check errors in all sessions quickly and
easily. This can be done by using the procedures described earlier in this section.
By using the preceding techniques and procedures and observing the restrictions, it
becomes easier to use the IAF stimulator to check performance and reliability and to /*s^
obtain
meaningful
data
from
the
system.
)

16-56

NOS

Version

Analysis

Handbook

Revision

Permanent

File

Utilities

Introduction
.mmm-«Utility
Description
Te r m i n o l o g y
...
17-2
Archive
File
"
]
'
y,
«
Alternate
Storage
'
'V»
«
Destaging and Staging Files .■.......'.'!!."!!.'!!..'!.'!.".'!!!!!!!!! 17-3
User
Index
...
...".
17-4
Device
Masks
m
17-5
Device
Mask
.
17-5
Secondary
Mask
..;
..................
17-7
Mass
Storage
Ta b l e
17-9
Catalog
Track
[[[["
..............
17.9
Permanent
File
Catalog
Entry
1 7 - 11
Track
Reservation
Ta b l e
(TRT)
17-22
Family • .'.'.'.'.'.'.'.'.'.'.'.'.'.'.'..'.'.'.'.'..'. 17-25
Summary
File
17-29
Calling
Console
DIS
Batch
Te r m i n a l
Procedure

the
Input

Utilities
.t
.....
Input
Input
Input
Files

17-37
17-37
17-44
17-44
17-45
17-45

Parameters for the Permanent File Utilities 17-46
Description of Permanent File Utility Parameters 17-48
Preassigning
the
Archive
File
.
17-60

4^*

Permanent
File
Utility
Routines
17-61
Catalog
Archive
File
( P FAT C )
17-66
C a t a l o g P e r m a n e n t F i l e D e v i c e ( P F C AT ) 1 7 - 6 6
Copy
Archive
File
(PFCOPY)
.
'.
17.72
Dump
Permanent
File
(PFDUMP)
17-72
PFDUMP
in
a
Secured
System
17-73
Incremental Permanent File System Dump 17-73
Partial
Permanent
File
System
Dump
17-74
Full
Permanent
File
Dump
17-74
PFDUMP
File
Interlocking
.-.,
17-74
PFDUMP in an MSE or Tape Alternate Storage Environment 17-74
PFDUMP
Protected
Files
17-76
Load
Permanent
File
(PFLOAD)
17-77
Catalog
Image
Record
17-79
PFLOAD
Selection
Process
17-80
Family
R e c o n fi g u r a t i o n
17-82
PFLOAD in an MSE or Tape Alternate Storage Environment 17-83
PFDUMP/PFLOAD
Example
.,..-..
17-84
Release
Disk
Space
(PFREL)
17-92

Permanent File Utilities

Introduction
Five utility processors maintain the NOS permanent file system. They control the
processes of dumping and loading permanent files, cataloging permanent files in the
system and on backup storage (archive) files, copying archived files to a job as local
files, and releasing the disk space of files that reside on tape or cartridge alternate
storage.
The utility processors are overlays under the control of the permanent file supervisor
(PFS). PFS processes the parameters in the utility command and loads the correct
processing overlay. The overlays interact with the permanent file utility (PFU)
routine, which manages the catalogs, permits, data allocation on a device, and the
data transfer between the device and the overlay. Figure 17-1 is an overview of this
procedure.

PERMANENT FILE SUPERVISOR (PFS)
LOADS THE CORRECT OVERLAY FOR
PERMANENT FILE PROCESSING

z^m^s.

PFDUMP1

PFLOAD1

PFCAT 1

PFAM

PFDM1

OVERLAY FOR
DUMP

OVERLAY FOR
LOAD

OVERLAY FOR
DEVICE
CATALOG

OVERLAY FOR
ARCHIVE
FILE
MANAGEMENT

OVERLAY FOR
DISK
MANAGEMENT

PERMANENT FILE UTILITY (PFU)
PERFORMS VARIOUS UTILITY
FUNCTIONS FOR THE PERMANENT
FILE UTILITY OVERLAYS

Figure 17-1. Functional Overview of the Permanent File Utility Overlays

Revision M

Permanent File Utilities 17-1

Utility Description Terminology

The names and functions of the permanent file utilities follow. Detailed information
about the call and operation of each utility is contained in this section. "^\
Utility Description
PFATC Produces a cataloged directory of file information derived from an
archive file.
PFCAT Produces a cataloged directory of file information derived from catalog
tracks on a permanent file device.
PFCOPY Copies files from an archive file to a job as local files.
PFDUMP Dumps files from a permanent file device to an archive file. Files
created by this dump can be reloaded by the PFLOAD utility.
PFLOAD Loads files from an archive file (created by PFDUMP) to a permanent
file device.
PFREL Releases disk space of files that reside on tape or cartridge alternate
storage.

Utility Description Terminology
The descriptions of the permanent file utilities in this section include some terms you
should be familiar with. These terms are defined next.
Archive File
All or some of the permanent files accumulated on mass storage can be dumped to a
backup tape (or other type of backup medium) to protect the files from loss in case of
a device malfunction or to free a device for temporary use during preventive
maintenance. Each dump of permanent files is made to a file called an archive file;
each permanent file dumped is called an archived file. Each archive file is a
multirecord file in which each logical record is an archived file. If two or more dumps
are made on one type of backup device, these archive files constitute a multifile
archive file (refer to figure 17-2).
The archive file can be loaded back onto the permanent file system as a whole or in
part and can also be used to generate reports. The individual archived files can be
referenced for selective use. Refer to each utility for more information on how it uses
the archive file.
Alternate Storage
The storage of permanent file data on external media other than mass storage (such as
magnetic tape or MSE) is called alternate storage. When a file resides on alternate
storage, the PFC entry and permits must reside on disk but the disk space occupied by
the file data can be released.

,<^S^v

17-2

NOS

Version

Analysis

Handbook

Revision

Destaging and Staging Files

0ms

FILE1
EOR
PERMANENT
FILE SYSTEM

ARCHIVE FILE A
(3 LOGICAL RECORDS)

FILE1
FILE2

EOR
FILE3

UUMr A -————'

EOR
EOF

FILE 3
FILE4

FILE2

FILE 4

DUMP B

FILE5

MULTI FILE
ARCHIVE
FILE

EOR
+ ARCHIVE FILE B
(2 LOGICAL RECORDS)

FILES
EOR
EOF
EOF

Figure 17-2. Example of Multifile Archive File Structure
Destaging and Staging Files
The process of copying file data to tape alternate storage or MSE from disk residence
is called destaging the file. File destaging to tape is initiated by using the PFDUMP
utility; destaging to MSE is initiated by using the SSMOVE utility.
The process of restoring file data to disk residence from a copy on alternate storage
is called staging the file. File staging is initiated by entering an ATTACH, GET,
OLD, or APPEND command for a file that is not currently disk resident.

Revision M

Permanent File Utilities 17-3

User Index

User Index
A 17-bit user index is associated with each user name created on the user validation
file. This index is entered through MODVAL (refer to User Validation in the
Administration Handbook) with the UI parameter on the user name input directive
(/username,UI=userindex) or MODVAL, by default, supplies the next available index.
Whenever you submit a job, the related user index is placed in the control point area
along with the user name and other parameters that link hardware, files, and job.
The permanent file manager (PFM) identifies the master device and catalog track for
you by performing two masking operations that involve the user index and two sets
of device parameters (device mask and number of catalog tracks) obtained from the
mass storage table in central memory resident (CMR). One operation correlates the
rightmost octal digit in the user index (bits 0 through 2) with the bit settings of the
device mask for each device in the configuration to determine which device is your
master device (refer to the device mask definition next). The other operation performs
a logical AND between the remaining portion of the index and the number of catalog
tracks on the master device to determine which track contains your catalog (refer to
the catalog track definition later in this section).
The lower 3 bits (rightmost octal digit) of the user index are used to group users
together into subfamilies. Each permanent file family (refer to the definition of family
later in this section) consists of eight subfamilies, subfamily 0 .through subfamily 7.
Any user whose index ends in 0 belongs to subfamily 0, any user whose index ends
in 1 belongs to subfamily 1, and so forth. The concept of subfamily is important in a
Mass Storage Extended Subsystem (MSE) environment.

17-4

NOS

Version

Analysis

Handbook

Revision

Device Masks

Device Masks
Two types of device masks exist for each device, the device mask (or primary mask)
and the secondary mask.
Device Mask
The device mask is an 8-bit quantity used to identify the group of users that has the
particular device as its master device; that is, it identifies the device that contains the
group's file catalogs, all its indirect access files, and possibly some or all of the group's
direct access files. (Assigning direct access files to a device is described next, under
Secondary Mask.)
If bit i is set in the mask of the device, any user whose index ends in i has this
device as a master device.
Example 1:
The device identified by the mask 2618 is the master device for any user whose index
ends in 0, 4, 5, or 7, because these bits are set in the mask.
7
1

0
0

When masks are assigned at device initialization time, the following rules must be
observed.
• Within a family, the sum of all the device masks must be exactly 377s.
• Each bit position (0 through 7) must be set exactly once for the masks of the
devices in one family.
Example 2:
For a family of three devices, 221s, 042s, and 114s are valid device masks because
their sum is 377s and each bit is accounted for only once.
10 0 10 0 0 1= 2218
0 0 10 0 0 10= 0428
0 10 0 1 1 0 0 = 1148
11111111 =

3778

If the sum of the device masks is less than 377s, then at least 1 bit is not set in any
of the device masks. Any user index ending in such a bit-position value does not
reference a device. Therefore, if such a user tries to create a permanent file, the
system issues an error message.

r
Revision M

Permanent File Utilities 17-5

Device Masks

Example

For a family of four devices, 1428, 0208, 0108, and 2048 are not valid device masks
because their sum is less than 3778. Any user whose index ends in 0 would have no
master device and could not create a permanent file.
0 110 0 0 10= 1428
00010000° 0208
00001000= 0108
10 0 0 0 10 0= 2048
1111111 0 =

3768

If the sum of the device masks is greater than 3778, then at least 1 bit is set for
more than one device mask. Any user index ending in such a bit-position value
references more than one master device.
Example

)

For a family of four devices, 2128, 1068, 0408, and 0218 are not valid device masks
because their sum is greater than 3778. Bit 1 is set twice, which indicates that any
user whose index ends in 1 would have two master devices, one with mask 212s and
one with mask 106810 0 0 10 10= 2128
0 10 0 0 110= 1068
00100000= 0408
0 0 0 10 0 0 1= 0218
11111111 =
1

4018

It is a necessary but not sufficient condition that all masks for one family total 3778.
It is possible, but not allowable, that in one family the device masks total 377s but
some bit is set in more than one device mask.
Example

For a family of three devices, 2618, 1158, and 0018 are not valid device masks because
bit 0 is accounted for three times and bit 1 is not set at all. Any user whose index
ends in 0 would have three master devices. Any user whose index ends in 1 would
have no master device.
10 110 0 0 1= 2618
0 1 0 0 1 1 0 1 = 1158
00000001= 0018
111111 0 1 = 4 0 1 8
1
1

/rfSSV

17-6

NOS

Version

Analysis

Handbook

Revision

Device Masks

Secondary Mask
The secondary mask of a device is an 8-bit quantity used to identify groups of users
who can place direct access files on the particular device. If bit i is set in the
secondary mask of the device, any user whose index ends in i can place direct access
files on this device.
Example 1:
A device whose secondary mask is 0728 can contain direct access files of any user
whose index ends in 1, 3, 4, or 5. because these bits are set in the mask.
6
0

3
111 0

tmXXXmXXXXXaSrOaXmXmXmXX^T'

^M^^^^^^^^^^^^^^^*

1
10
^^^^^y^M"**^

Direct access files may or may not reside on a master device, depending on the user
index and secondary mask. The appropriate bit must be set in the secondary mask of
the device on which the user's direct access files are to reside. A direct access file is
placed on a valid device with the most space available unless the user specifies a
particular device.
Example 2:
The following situations occur for a device whose mask is 2618 and secondary mask
is 0728.
754

1 0 11 0 0 0 1

5431
0 0 111 0 1 0

• This device is the master device for, and can contain direct access files of, any
user whose index ends in 4 or 5 (bits 4 and 5 are set in both the device mask
and the secondary mask).
• This device is the master device for, but cannot contain direct access files of, any
user whose index ends in 0 or 7 (bits 0 and 7 are set in the device mask but not
in the secondary mask).
• This device is not the master device for, but can contain direct access files of, any
user whose index ends in 1 or 3 (bits 1 and 3 are set in the secondary mask but
not in the device mask).
• This device is not the master device for, and cannot contain direct access files of,
any user whose index ends in 2 or 6 (bits 2 and 6 are not set in either the device
mask or the secondary mask).

Revision M

Permanent File Utilities 17-7

Device Masks

Existing files can be defined as direct access permanent files, regardless of the
secondary mask, for user indexes above 377700s (AUIMX). However, PFLOAD will ^
enforce the secondary mask check when loading these files. Direct access files for MSE
subfamily user indexes (377760 through 377767s) are always loaded to their master
devices regardless of previous residence or secondary mask values.
There are no restrictions on the number of devices in one family that can have the
same bits set in the secondary mask or regarding the sum of the secondary masks for
devices in the same family. The secondary mask must be a number between 0 and
3778.
Example 3:
For a family of three devices, 000, 131s, and 326s are possible secondary masks. Any
user whose index ends in 0, 3, 4, or 6 can place direct access files on the device
whose secondary mask is 1318. Any user whose index ends in 1, 2, 4, 6, or 7 can
place direct access files on the device whose secondary mask is 3268. No user can
place direct access files on the device whose secondary mask is 000. Any user whose ^^^
index ends in 4 or 6 can place direct access files on two devices, and any user whose ^)
index ends in 5 cannot use direct access files.
0 0 0 0
0 1 0 1
11 0 1
11 0 1
1
1

17-8

NOS

= 000s
= 1318
= 3268
= 3378

Version

Analysis

Handbook

Revision

Mass Storage Table

Mass Storage Table
The configuration of mass storage devices currently available to the system is defined
by the CMR mass storage table (MST). Each logical device in this configuration has an
entry in this table. Refer to the NOS Version 2 Systems Programmer's Instant for the
MST format.
Catalog Track
Your catalog track is a track on your master device containing the catalog entries
(definition follows) that define and specify the location of each permanent file you have
created. Users are assigned by groups to catalog tracks according to their user index
and number of catalog tracks on their master device.
The number of catalog tracks on a device is established when the device is initialized
or by default. Default values are:
Type of Device
Extended

Default Number of Catalog Tracks
memory

(DE)

834

(DD)

408

836

(DG)

408

844

(DI,

DJ,

8 8 5 - 11 / 1 2

(DM,

885-42
887
895
819
9853

DK,

DL)
DQ)

(DB)
( D F,

DH)

(DC)
( D V,

40s
10s
10s
10s
10s

DW)
(DN)

10s
10s

DDP path to extended memory (DP) 4
Private

device

The number of catalog tracks is always a power of 2; the maximum number is 200s.
Therefore, the possible numbers of catalog tracks on a device are:
1, 2, 4, 108, 208, 408, 1008, 2008

Revision M

Permanent File Utilities 17-9

Catalog Track

Reducing these numbers by 1 produces the following numbers, referred to as track
masks.
0, 1, 3, 7, 17s, 378, 77s, 177s
The track masks in binary form are:
0

1
11
1 1 1
1 1 1 1

These track masks, except the first one, have all bits set; when bits 3 through 9 of
the user index for a particular user are ANDed with the track mask for his/her
master device, the user's catalog track number on that device is produced.
Example:
For a family of two devices, the following device masks, number of catalog tracks,
and track masks are valid.
Device

Number of Corresponding
Catalog Tracks Track Mask

Device
Mask
2218 or

10 010 001 408

408-1 = 378 or 11 111

01 101 110 208
11 111 111

208-1 = 178 or 1 HI

1568
3778

A user whose index is 14224s is assigned device 1 as his master device because bit 4
(last digit in 14224s) is set in the device mask for device 1. Therefore, device 1
contains this user's catalog track.
The binary form of 14224s is 001 100 010 010 100.
Therefore, the catalog track number for this user is 22s (on device 1) because the
logical AND of bits 3 through 9 of the user index with the track mask for device 1
is:

AND

10 0 0 10 0 10
1 1 1 1 1
10 0 10 or 228

The end of a catalog track is indicated by an end-of-information (EOI) on the device.
All catalog tracks are linked in the track reservation table (TRT) and appear as one
logical chain. When catalog entries exceed the logical track, a continuation track is
reserved at the end of the catalog track chain in the track reservation table. The
disk linkage bytes for the overflowed track point to the continuation track.

17-10 NOS Version 2 Analysis Handbook

Revision M

Permanent File Catalog Entry

Permanent File Catalog Entry
Files in the permanent file system are referenced by dynamically updated permanent
file catalog (PFC) entries on the catalog tracks of master devices. Whenever you create
a permanent file, a catalog entry that specifies the characteristics of the file (access
information about the file and its location) is entered on a catalog track on your
master device. When you modify the file, the PFC entry is updated to reflect the
modification.
The format of the PFC entry follows. The 4-character names to the right of each
word are symbols used by the system to reference the PFC entry fields. These
symbols are defined in common deck COMSPFM.
59

47 44 41

word 0
1
2

P« r m i t r a n d o n i n d e x

mode

track

FCFN.FCUI

sector

FCLF, FCBT, FCBS
FCRI, FCCD

/>>^>>%^^<^^>^
pr

control modification date and time

*i «• wwzmiA
cat

FCRS, FCBR.FCFS, FCAP,
FCUD

utility control date and time

file password

-**» WaVa.

FCAC, FCMD
FCCT, FCAM.FCEF, FCEC.
FCEO, FCAD
FCKD

last access dote and time

data modification date and time

creation date and time

access count

userindex

w//y//A

file length

filename

expiration date

FCPW, FCXD

cartridge alt. storage address

v///y//y//yy//yyA%z* V/a.

FCAF, FCAT, FCAA

access categories

FCAL, FCFC

charge number

FCCN

project number

FCP1

project number

taf lags \20fli f^Le seq* nLaaber

FCP2
tape alt. storage VSN

FCTF, FCTS, FCTV

tieer central word

FCUC

reserved for installation

FCIW

Field

Word Bit(s) Description

fi l e n a m e

59-18 Permanent file name.

userindex

17-0 User index of file creator.

fi l e

59-36 Length of the file in PRUs.

track

23-12 Beginning track of the file.

sector

11-0 Beginning sector of the file.

length

permit random 2
index

59-36 Random disk address of first permit sector.

creation date and 2
time

35-0 yymmddhhmmss in octal when this file was
first entered on the permanent file system.
The year (yy) is biased by 70.

access

59-36 Total number of times this file has been
accessed.

Revision M

count

Permanent File Utilities 17-11

Permanent File Catalog Entry

Field

Word Bit(s) Description

data modification
date and time

35-0 yymmddhhmmss in octal when data in this
file was last modified. The year (yy) is biased
by 70. For direct access files this field is
updated only when the file is attached in a
modifiable mode.

59-54 File category:
0 Private.
1 Semiprivate.
2

mode

Public.

53-48 Mode of access for semiprivate and public
files:
0 Write, read, execute, append, modify,
and/or purge.
1 Read and/or execute.
2 Append.
3 Execute.
4 Negate previous permission.
5

M o d i f y.

6 Read and/or execute, allow modify.
7 Read and/or execute, allow append.
10 Update.
11 Read and/or execute, allow update.
ef

47-45 Error flag:
0 No error.
1 EOI changed by recovery.

~*)
17-12 NOS Version 2 Analysis Handbook

Revision M

Permanent File Catalog Entry

Field

Word

Bit(s)

Description

44-42

Error code:
0

No error.

Error in file data.

Error in permit entries for file.

Error in data and permit entries.

Error in file length.

Reserved.

41-36 Device number (1 through 77s) of the device
on which the direct access file resides if
other than the user's master device. If the
file resides on the master device, dn is 0.

last access date 4
and time

35-0 yymmddhhmmss in octal when this file was
last accessed. The year is biased by 70.

control modification 5
date and time

35-0 yymmddhhmmss in octal when this file's
control information (catalog entry and permit
record data) was last modified.

59-57 Preferred residence1 for this file:
1 File locked to disk (PR=L specified by
file owner with validation).
2 Disk residence preferred (PR=D specified
by file owner).
3 MSE residence preferred (PR=M
specified by file owner).
4 No preferred residence (PR=N specified
by file owner).
5 Tape alternate storage residence
preferred (PR=T specified by file owner).

1. Refer to Permanent File Commands in the NOS Version 2 Reference Set, Volume 3 for details on the PR
and BR parameters.

Revision M

Permanent File Utilities 17-13

Permanent File Catalog Entry

Field
br

Word Bit(s) Description
56-54 Backup requirement for this file:
1 Two backup copies required (BR=Y
specified by file owner).
2 One backup copy required (BR=MD
specified by file owner).
3 No backup copy of file required. (BR=N
specified by file owner).

53-48 Subsystem code for this file:
0 Null Subsystem.
1 BASIC Subsystem.
2 FORTRAN Subsystem.
3 FTNTS Subsystem.
4 Execute Subsystem.
5 Batch Subsystem.

47 Alternate CATLIST permission:3
0 Alternate users cannot obtain CATLIST
information about the file (AC=N
specified by file owner).
1 Alternate users can obtain CATLIST
information about the file (AC=Y
specified by file owner).

utility control date
and time

35-0 yymmddhhmmss in octal set by PFM and PF
utilities and used by PFDUMP in
determining whether to dump the file when
the OP=M option is specified. This field is
updated when the data modification date and
time field is updated or PFDUMP finds a file
busy (attached in modifiable mode). This
ensures that the file is selected on
subsequent dumps even if the data
modification date and time field does not
change.

file password

59-18 Optional password.

expiration date

17-0 yymmdd in octal when this file's password
expires. The year is biased by 70.

2. Refer to Permanent File Commands in the NOS Version 2 Reference Set, Volume 3 for details on the PR
and BR parameters.
3. Refer to Permanent File Commands in the NOS Version 2 Reference Set, Volume 3 for details on the AC
parameter.

17-14 NOS Version 2 Analysis Handbook

Revision M

Permanent File Catalog Entry

Field

Word Bit(s) Description

cafiags

10 59-48 Cartridge alternate storage flags; refer to
section 11, MSE, for details.
Flag

Bit

Description

A F L O K 5 9 L o c k t o d i s k fl a g :
0 is an indirect access
permanent file is not
being destaged to MSE.
1 is an indirect access
permanent file is being
destaged to MSE.
A F F R E 5 4 F r e e u p c a r t r i d g e fl a g :
0 means do not remove
file from cartridge.
1 means remove file from
cartridge.
A F T M P 5 3 Te m p o r a r y e r r o r fl a g :
0 indicates that no
temporary error
conditions have been
detected.
1 indicates that a
temporary error condition
prevented the MSE image
of the file from being
staged to disk. After the
error condition is
detected, this flag is
cleared so that the file
staging can be retried on
the next request for the
file.

jg^ss.

Revision M

Permanent File Utilities 17-15

Permanent File Catalog Entry

Field

Word

Bit(s)

Description

caflags (Continued)

Flag

Bit

Description

A F V E R 5 2 V e r i fi c a t i o n fl a g :
0 means that if the
cartridge alternate
storage address is not
zero, a successful stage/
destage operation has
occurred and system
control errors should not
be encountered.
1 means that the PFC
entry containing the
cartridge alternate a*s®s
storage
address
was
)
reloaded and a stage
attempt has not yet been
made. If a system control
error is detected, the
probable cause is that the
cartridge alternate
storage address is
obsolete, probably because
an obsolete dump tape "^
was used during the
reload.

17-16

NOS

Version

Analysis

Handbook

Revision

Permanent File Catalog Entry

00ms,

Field

Word Bit(s) Description

caflags (Continued)
Flag

Bit

Description

A F P D R 5 1 P s e u d o r e l e a s e fl a g :
0 means that the file can
be attached immediately
if it has a disk image.
1 means that the file has
a disk image that cannot
be attached until the
MSE image of the file is
staged to disk. After the
stage attempt (whether or
not it is successful), this
flag is cleared.
A F P D E 5 0 D a t a e r r o r fl a g :
0 means that no
unrecoverable read errors
have been detected.
1 means that an
unrecoverable read error
prevented the MSE image
of the file from being
staged to disk.
A F P S E 4 9 S y s t e m c o n t r o l e r r o r fl a g :
0 means that no system
error conditions have
been detected.
1 means that a system
error condition prevented
the MSE image of the
file from being staged to
disk.

Revision M

Permanent File Utilities 17-17

Permanent File Catalog Entry

Field

Word Bit(s) Description

caflags (Continued)

Flag

Bit

Description

AFOBS 48 Obsolete flag; set to 1
whenever the file is
attached in write mode.
0 means that MSE image
is a current version of
the file.
1 means that disk image
is the current version of
the file; the MSE image
is obsolete.
cat

41-36

Cartridge alternate storage type:
0 File resides on disk only.
1 Reserved.
2 File has an MSE image.

cartridge alt.
storage address

35-0

Cartridge alternate storage address:
0 A n M S E i m a g e o f t h e fi l e d o e s
not exist.
Nonzero Specifies the location of the
beginning of the file on MSE.
The AFOBS flag indicates
whether or not this MSE image
is current.

38-36

File security access level:
0 Access level 0.
1 Access level 1.
7 Access level 7.

4. The 8 access levels and 32 access categories are referenced by names defined by or in micros in system
common deck COMSMLS. The default names are LVLO through LVL7 for access levels and CATOO through
CAT31 for access categories. Each site determines what the access levels and categories mean, and can
change the corresponding names to clarify that relationship. For example, access level 3 may be defined as
meaning secret, so the name for access level 3 can be changed from LVL3 to SECRET. If any of the
COMSMLS micros are changed, all decks calling COMSMLS must be reassembled.

17-18 NOS Version 2 Analysis Handbook

Revision M

Permanent File Catalog Entry

0ms
Field

Word Bit(s) Description

access categories

11 31-0 File security access categories:
Each bit indicates whether the file has the
corresponding access category as part of its
category set. Bit 0 corresponds to access
category 0; bit 1 to access category 1, and so
forth. A file's category set can be any, all, or
none of the 32 available categories.

charge number

59-0

Charge number to which this file is billed.

project number

13-14 59-0

Project number to which this file is billed.

taflags

Tape alternate storage flags; refer to
section 12, Tape Alternate Storage, for
details.

59-48

Flag
TFLOK

Bit
59

Description
Destage to tape flag:
0 means the permanent
file is not being destaged
to tape.
1 means the permanent
file is being destaged to
tape.

Revision M

TFESV

Data error on secondary
VSN flag.

TFEPV

Data error on primary
VSN flag.

TFSVN

Secondary VSN not
accessible flag.

TFPVN

Primary VSN not
accessible flag.

Permanent File Utilities 17-19

Permanent File Catalog Entry

Field

Word

Bit(s)

Description

taflags (Continued)

Flag

Bit

Description

TFSVS 49 Secondary VSN exists
flag:
0 indicates a secondary
VSN does not exist.
1 indicates a secondary
VSN does exist.
T F V E R 4 8 P F L O A D v e r i fi c a t i o n fl a g :
0 means that if the tape
alternate storage VSN
pointer is not zero, a /X_
successful stage/destage ]
operation has occurred
and system control errors
should not be
encountered.
1 means that if the PFC
entry containing the tape
alternate storage VSN
pointer was reloaded and s*ss
a stage attempt has not )
yet been made. If a
system control error is
detected, the probable
cause is that the tape
alternate storage VSN
pointer is obsolete,
probably because an
obsolete dump tape was
used during the reload. <-a%

17-20

NOS

Version

Analysis

Handbook

Revision

Permanent File Catalog Entry

Field

Word Bit(s) Description

file seq. number

41-24

Sequence number of the file on the dump
tape produced by PFDUMP.

tape alt. storage
VSN

23-0

Tape alternate storage VSN pointer in the
following format:
12/cc, 12/nnnn

where cc is any two alphanumeric characters
and nnnn is a 12-bit binary integer.
The tape's primary VSN is cc followed by
nnnn converted to a decimal integer in the
range of 0000 to 4095 with leading zeros.
The secondary VSN, if it exists, is derived by
adding 5000 to the primary VSN.
user control word

59-0

User control information.

igp>>\

Revision M

Permanent File Utilities 17-21

Track Reservation Table (TRT)

Track Reservation Table (TRT)
Every device in a permanent file system has a label track (usually track 0) that
contains a label sector describing the device (family name, device mask, secondary
mask, location of permit information, catalog information, and indirect files) and a
number of physical record units (PRUs) containing the track reservation table (TRT).
The TRT describes the physical layout of data on the device and is the key to
allocating information on the device.
The TRT contains single-word entries that define track linkage and bit-setting
controls for those tracks (refer to figure 17-3). Each word has four 12-bit linkage
bytes and three sets of 4-bit control settings that match the 4 bytes (refer to figure
17-4). Linkage format is given in figure 17-5.
The numbering of the 12-bit linkage bytes or cells corresponds to the numbering of
tracks on the device, with the first track starting at 4000. The entry in a cell
references the next cell and its associated track. This next track either continues the
information or starts a new sequence depending on the first-track bit setting.
Figures 17-3 and 17-4 show a sequential linkage of tracks (in figure 17-4, from track
4000 to track 4001 to 4002 to 4003). This numerical sequence is purely illustrative.
The linkage could just as well have been:
4000 — 4002 — 4015 — 4012

47
Track Link

35
Track Link

23
Track Link

Track Link

t
\
To next
TRT word

Figure 17-3. Track Reservation Table Word
Each track reservation table word contains the following entries:
Entry
Track Link

Description
Address of the next track that is a logical continuation of this file.
(The track links are shown as sequential within a word, but this is
not a requirement.)
Bit settings for identifying the first track of a preserved file
(permanent file chain or queued file).
Bit settings for establishing interlock of a track.
Bit settings for track reservation.

17-22 NOS Version 2 Analysis Handbook

Revision M

y ^ ^ k

Track Reservation Table (TRT)

The first group of control settings (bits 8 through 11) is used to identify those tracks
that begin a sequence of file information. If any one of these bits is set, the associated
track is the first track of a chain that may extend across a number of tracks. This
chain can be a direct access file, an indirect access file data chain, a catalog chain, a
permit chain, a system dayfile, or a queued file.
The second group of control settings (bits 4 through 7) is used to interlock tracks. If
any one of these bits is set, the associated track cannot be accessed as long as this
bit remains set. Whenever a file is accessed, the system automatically interlocks the
catalog track containing the file. The interlocking capability is necessary because
PFM may be processing several requests directed at one file simultaneously. Without
interlock, these requests could overlap.
The third group of control settings (bits 0 through 3) is used to identify reserved
tracks. A track is reserved either because it has data written on it or it is a flawed
track. A flawed track is removed from availability by reservation at deadstart, by
subsequent initialization, or by reformatting with the FORMAT utility for 844
devices.
Figure 17-4 shows matching of four reserve track bit settings with corresponding
track link bytes. The same correspondence holds for the interlock bits (4 through 7)
and the first-track bits (8 through 11).

Figure 17-4. Bit Settings for Track Link Bytes

Revision M

Permanent File Utilities 17-23

Track Reservation Table (TRT)

4XXX

INDICATES WHICH
BYTE IN THE WORD
IS BEING REFERENCED

OCTAL INDICATION
OF THE NEXT WORD
IN THE CHAIN

LINKAGE
BYTE

XXX

IF THIS BIT IS SET, THIS IS A LINK BYTE;
IF IT IS NOT SET, THIS IS THE LAST TRACK
IN THE CHAIN AND THE NUMBER IS THE SECTOR
NUMBER OF A SECTOR CONTAINING THE EOI (END
OF INFORMATION).

EXAMPLE : THIS ILLUSTRATES THE SEQUENTIAL LINKAGE

4075

4053

• 4 0 7 7 —▶O I O O

BYTE 0 BYTE
4050
4051

BYTE 2 BYTE 3
4052
4053

4075

WORD I28

100

III

101

f
f

BYTE 0 BYTE I BYTE 2
4074
4075
4076
4077

WORD I78

I
I 00 00 0 I I I I I I

BYTE 3
4077
OIOO

LAST

SECTOR
(EOI)

Figure 17-5. Linkage Format With Example
a ^ S

17-24 NOS Version 2 Analysis Handbook

Revision M

Family

00ms

Family
A family is a collection of from 1 to 63 logical devices identified by a 1- to 7-character
family name. Users and their files are grouped together according to the family
available to them. Usually, the grouping is within the configuration on which these
users normally run jobs. However, a family can be connected to any configuration and
still relate to the same users and files.
An auxiliary device, identified by a 1- to 7-character pack name, is a single device
that is not included in any family and can be accessed by validated users from any
family. An auxiliary device provides users with an alternative to the master devices
for storing and accessing permanent files. Use of auxiliary devices enables an analyst
to provide special sets of permanent files for selected users or for designated periods.
For example, an auxiliary device could be made available from 1200 to 1700 every
day for any properly validated user.

A permanent file device is either a member of a family or an auxiliary device.
-p^ Permanent files on a family device are accessed through user catalogs contained on a
( master device within the family. The user catalogs that reference permanent files on
an auxiliary device are contained on that device; that is, an auxiliary device is a
self-contained entity.
Families and auxiliary devices are defined at initialization time by the PF entry in
the EQPDECK or by the DSD INITIALIZE command. Normally, a configuration has
one family available. Additional families can be defined or introduced (on removable
devices) in the same configuration. If more than one family is available in a
configuration, you supply the family name at login or on the USER command. The
default family is used if no family name is supplied.5 Any job can change its
associated family name by using the USER command to specify the new family
name. 6 A system origin job can use the FAMILY command to change the family
name associated with the job. If the FAMILY command is included in any nonsystem
origin job, the job aborts.
The FAMILY command is valid for unsecured systems only.
The format of the FAMILY command is:
FAMILY,fami 1yname.

Parameter Description
familyname The 1- to 7-character name of a family of permanent file devices. If
omitted, the default family name specified at deadstart is assumed.

0@ms

5. The default family name is specified at deadstart time with the EQPDECK FAMILY entry and cannot be
changed dynamically.
6. Refer to the IPRDECK entry in section 2, Deadstart Decks, and to the DSD command ENABLE,
SECONDARY USER COMMANDS in section 5, DSD Commands; also refer to the USER command in the
NOS Version 2 Reference Set, Volume 3.

Revision

Permanent

File

Utilities

17-25

Family

If an alternate family of permanent file devices is introduced into the configuration
without a user validation file, the job to create the user validation file could include a
FAMILY command to identify the alternate family. If the familyname parameter is
omitted, the default family name is assumed.
Figure 17-6 is an example of a typical set of configurations.
Example:
One configuration with six permanent file devices [equipment status table (EST)
ordinals 6 through 13] is identified as system A. Three of the devices are grouped
into a family with the name FAMA. They have device numbers 40, 41, and 42. The
remaining three EST ordinals have been defined as removable. This means that the
system will allow family and auxiliary devices to be introduced on this equipment
during system operation.
SYSTEM B

SYSTEM A

EST
OROINAL

DEVICE
NUMBER

} FAMB

FAMA

AUXILIARY
DEVICES

AUX1
EQUIPMENT
DEFINED AS
REMOVABLE

EQUIPMENT
}DEFINED AS
REMOVABLE

Figure 17-6. Example of Families in Two Configurations

17-26 NOS Version 2 Analysis Handbook

Revision M

Family

A second configuration with six permanent file devices is identified as system B. Three
of the devices have been grouped into a family with the name FAMB. They also have
device numbers 40, 41, and 42. The remaining three pieces of equipment have been
defined as removable.
Two auxiliary devices are available to both systems. These have the pack names
AUX1 and AUX2.
Users of FAMA would normally run jobs on system A. Users of FAMB would
normally run jobs on system B.
The removable equipment on system A (EST ordinals 11, 12, and 13) could be used
for two purposes:
•

0$ms.

To mount auxiliary devices AUX1 and/or AUX2 as required by users of FAMA.
If users of FAMB need access to AUX1 and/or AUX2, these auxiliary devices
will have to be mounted on some combination of equipment defined by EST
ordinals 11, 12, and 13 on system B.
To mount FAMB devices when they are no longer accessible through system B.
In this case, users of FAMB will have to transfer their access to system A. This
transfer could involve moving disk packs from equipment defined by EST
ordinals 6, 7, and 10 in system B to equipment defined by EST ordinals 11, 12,
and 13 in system A, or system A could already have alternate channel
connections to equipment defined by EST ordinals 6, 7, and 10 in system B but
would define them as EST ordinals 11, 12, and 13 in its own system. If the
users of FAMB access their files through system A, they submit their jobs to
system A or dial into system A using a different telephone number. (They would
dial the same number if communication gear is switched.) The ISF command
must be used to make the validation file from FAMB available on system A.
Assuming that access to all of FAMB is transferred from system B to system A,
the new array of system A will be as illustrated in figure 17-7. System A now
has two families, its original default family FAMA and the newly attached
family FAMB whose devices now have the EST ordinals 11, 12, and 13. Its
device numbers (40, 41, and 42) remain the same. The device numbers happen
to be the same as those used within FAMA but device numbers provide
uniqueness only among devices within a family. Accordingly, total uniqueness of
a device is provided by the combination of family name and device number.
Users of FAMA will still be able to access their files without specifying the
family name since FAMA is still the default for system A. However, users of
FAMB will have to specify to system A that they belong to FAMB either at
login or on the USER command.
If another equipment (EST ordinal 14) were available on system A, either
auxiliary pack AUX1 or AUX2 could be mounted on it and users from either
family could access files on this pack.

00m\

Revision

Permanent

File

Utilities

17-27

Family

SYSTEM B

SYSTEM A

1 noTTn '
1 operation 1
EST
ORDINAL

'DEVICE
NUMBER

6 | h ^ 1 flO

•8"

7 1 r—H 1 ^1

' ^ J .

10 1 1 1 1 41

♦/
/ / AUX1

FAMB

| (^J |

10 Y\ «

FAMB

FAMA

EST
ORDINAL1

DEVICE
NUMBER

. g .j;8
/

AUX2

»j8! 1
■ I

EQUIPMENT
DEFINED AS
REMOVABLE

-LSI

Figure 17-7. Example of Transferring Family Access

17-28 NOS Version 2 Analysis Handbook

Revision M

Summary File

Summary FUe
Any of the permanent file utilities can create a summary file containing utility
processing information. The summary file is a machine-readable version of the
information available on the utility output file. This summary file is used as input by
the utility GENPFD; however, a site-written utility could use this information to
generate selection directives for permanent file utility operations such as destaging files
and releasing disk space, or to obtain permanent file statistics for billing, and so forth.
The summary file consists of a prefix table followed by a system identifier block, a
device status block, an archive file identifier block, CIR entries block(s), and PFC
entries block(s). The format of the prefix block allows you to use the CATALOG
command (refer to the NOS Version 2 Reference Set, Volume 3) to display some
information about the contents of the summary file and the environment in which the
summary file was created.
Additional block types may be added in future releases of NOS; thus, any site-written
utility should be coded to skip (and ignore) any block types other than the ones
documented here.
The format of the summary file follows:

Revision

Permanent

File

Utilities

17-29

Summary File

Prefix Table (all utilities)
59
Word 0
1

[ 7700B

47
0016B
record name

yy/ram/dd

hh.mm.ss

comment

Field

Word Bits Description

record name 1 59-18 Name of the record recognized by common deck
COMCSRT. The default value is the current date
in the format yymmdd. You can use the SR
parameter to specify the record name, if desired.
y y / m m / d d 2 5 9 - 0 S t a r t d a t e o f t h e u t i l i t y.
h h . m m . s s 3 5 9 - 0 S t a r t t i m e o f t h e u t i l i t y.
comment 10-16 59-0 Text indicating the utility name, the family or
pack name (if applicable), and the system title
from CMR words SYTL through SYTL+3.

17-30 NOS Version 2 Analysis Handbook

Revision M

/*S5Sv

Summary File

System Identifier Block (all utilities)
59

Word 0

17
len

SYSTEM

utility name

max block length

yy/mm/dd

hh.mm.ss

system title (SYTL)

7
10

system version (SVNL)

12 IIIIIIIIIUIIIIIIIIIIHI

packed date and time

1 3 t i l l / I fl l l l l l l l l l l l l l l l l / l l l l l l l l l i i i i i / i i

Field

Word Bits

len
utility

0-17

name

59-18

max block length 1 17-0

system level

Description
Length of this block excluding the control
word (138).
Name of the permanent file utility that
created the file.
Maximum length of subsequent data blocks
(10008). This value can be used by a
program interpreting the file to allocate
memory.

yy/mm/dd

59-0

Start date of the utility.

hh.mm.ss

59-0

Start time of the utility.

system title

4-7

59-0

Contents of CMR words SYTL through
SYTL+3.

system version 10-4 59-0

Contents of CMR words SVNL and
SVNL+1.

packed date and 12 35-0
time

Start date and time of the utility in
packed format.

system level

Revision M

17-0

Value of tag NOSLVL defined in
COMSVER.

Permanent File Utilities 17-31

Summary File

Device Status Block (PFCAT, PFDUMP, PFLOAD, and PFREL utilities only)

Word 0

[

D E V S TAT

track size

/////////////////
/////////////////

user name
type

len

family/pack name

2
3

tracks av

'//////////////////////////

net

tracks
///////

dn
dm

Device Status entry n
(n < 638)

/•"^SsK

Word Bits Description

I Field
len

11-0 Length of this block excluding the control word.
Block length = (number of device status
entries)*2+2.

family/pack name 1

59-18 Name of the family or auxiliary device to which
the information pertains. For an auxiliary device,
there will be only one device status entry and
the device number will be zero.

user name 2

59-18 User name if this block is for a private auxiliary
device; otherwise, this field is 0.

type

59-48 Equipment mnemonic from the device's EST
entry.

track size 3

47-36 Number of sectors per track. This field allows
computation of the space occupied by direct
access files.

tracks

35-24 Number of tracks available on this device. This
field is used in disk space release processing.

23-12 Number of tracks on this device.

tracks

17-32 NOS Version 2 Analysis Handbook

Revision M

esSSjv

Summary File

Field

Word

Bits

Description

u 3 8-6 Number of units on this device.
dn

0-5

Device

number.

net 3 32-24 Number of catalog tracks on this device.
sm

7-4

Secondary

device

mask.

dm 4 0-3 Device mask. The residency device number of a
file that resides on a master device can be
determined by matching the file's user index to a
device mask.

Revision

Permanent

File

Utilities

17-33

Summary File

Archive FUe Identifier Block (PFATC, PFCOPY, and PFLOAD utilities only)
59

len

ARCFILE

Word 0

family name

/////////////////

pack name

////////////////)

nilllllllllllllllllllll

packed date and time

Field

Word Bits Description

len

0 17-0 Length of this block excluding the control word
(3).

family name

1 59-18 Name of the family to which the archive file
belongs.

pack name

2 59-18 Name of the auxiliary device to which the
archive file belongs.

packed date and
time

3 35-0 Date and time from the archive file label in
packed format.

If the permanent file utility does not find the archive file label or if an error is
detected in the archive file label, a 3-word block is written with all fields zero.

17-34 NOS Version 2 Analysis Handbook

Revision M

' ^ ^

Summary File

Catalog Image Record Entries Block (PFATC, PFDUMP, and PFLOAD utilities
only).

CIR entry n
c^

Terminal Input

Terminal Input
y * s ^
1. PFDUMP,FM=familyname.
2. Initialize all devices in the family.
3. PFLOAD,OP=L,FM =familyname.

17-82

NOS

Version

Analysis

Handbook

Revision

PFLOAD in an MSE or Tape Alternate Storage Environment
0^S

PFLOAD in an MSE or Tape Alternate Storage Environment
In an MSE or tape alternate storage environment, an incremental load as described
previously is the typical reload procedure. PFLOAD uses the CIR from the first
incremental dump file to control the loading of file data and PFC and permit entries.
For files with alternate storage copies, the files' data may not have been copied to the
dump tape (refer to PFDUMP in an MSE or Tape Alternate Storage Environment
earlier in this section for more information on how PFDUMP decides whether to dump
a file's data or to dump only the file's PFC entry and permits). PFLOAD reloads only
what was dumped by PFDUMP. Thus, if the file data was included on the dump tape,
it will be reloaded to disk. If the file data was omitted from the dump tape, only the
PFC and permit information for the files will be reloaded. Refer to section 11, MSE, or
to section 12, Tape Alternate Storage, for further information on how the PFLOAD
utility is used in an MSE or tape alternate storage environment.

0$ms

Revision

Permanent

File

Utilities

17-83

PFDUMP/PFLOAD Example

>»^K

In this example, permanent files created and modified on three devices are dumped
nine times. The action runs from March 1, 1982 (82.3.1) to March 10, 1982 (82.3.10).
To keep things simple, the time of day is not shown. Before the last dump, one of the
devices becomes inoperable. The example then shows how this device can be loaded
from the archive tapes. Following are the three devices.
Device Description
40

A master device containing indirect access files only. Users with this
master device have their direct access files written on 41 or 42.

A master device containing indirect and direct access files. Direct access
files cataloged on this device may be written on 42 or this device.

A nonmaster device containing direct access files only. All files written on
this device will be cataloged on 40 or 41.

File names consist of a letter and a number. The letter identifies which device contains
the catalog entry for this file (A=device 40 and B=device 41). The number is the
same as the device on which the file is written.
Each file name is followed by a date in parentheses. This indicates either the day on
which the file was created or when it was last modified.
Figure 17-21 outlines the creation, modifications, and dumps that were made. There
is one particular action per column. The top of the column identifies the action and
the key parameters used by the utility. If an archive tape is produced, it is shown at
the bottom of the column. All files in the system are listed in each column. Those
files affected by the action are underscored.

-"^v

17-84 NOS Version 2 Analysis Handbook

Revision M

PFDUMP/PFLOAD Example

•8
•3

|S iff

•

¥<

a
a ' ^
Xi

fcEE

><5

IUCOO

Scot

><£
uJSo
O

ui
Ct

>S££
u Z q

Figure 17-21. PFDUMP/PFLOAD Example (Sheet 1 of 3)

Revision M

Permanent File Utilities 17-85

PFDUMP/PFLOAD Example
/-^K

^^S
in

<
•*
CM
00

«
?
cn

^
2

T *

*.
00

1*
C
M

e
o

s. ^O)^-

r*
2
3

ejen
CM CM
oooo

izn

oooo
tn tn
CM CMCD 00

o
«*»«•

(4
eo

«M
00

™uj
UjUllU

ujUjO

UJCOO

><£

>SE
uiZO

O ui

C
E

Figure 17-23. PFDUMP/PFLOAD Example (Sheet 3 of 3)

s$&s

Revision M

Permanent File Utilities 17-87

PFDUMP/PFLOAD Example

Actions during the 10 days in March in which the dumps and modifications were made
run
as
follows:
Date

Action

82.3.1 Five permanent files are created on this date.
File A40 (indirect) is written on device 40 and cataloged on device 40.
File A42 (direct) is written on device 42 and cataloged on device 40.
File A41 (direct) is written on device 41 and cataloged on device 40.
File B41 (indirect) is written on device 41 and cataloged on device 41.
File B42 (direct) is written on device 42 and cataloged on device 41.
82.3.2 DUMP 1. A full permanent file system dump. No CIR is written on the
archive file.
82.3.3 Three files (A40, B41, and B42) are modified on this date. This is
indicated by the modification date in parentheses following the file
name.
82.3.4 DUMP 2. This is an incremental dump of device 40 that specifies
permanent files modified after 82.3.3. The files for this device are the
ones listed on its catalog track. The utility scans this catalog which
contains entries for files A40, A42, and A41. File A40 is on device 40
and the other two are on the devices indicated by their names. Only file
A40, which was modified on 82.3.3, qualifies for this dump. It is written ^^
on an archive tape after a CIR for this date (82.3.4). The CIR gives a
current description of all five files in the permanent file system.
82.3.4 DUMP 3. This is an incremental dump of device 41 that specifies all
files modified after 82.3.2. The catalog for this device contains entries
for files B41 and B42. Both files were modified on 82.3.3 and qualify for
this dump. They are written on an archive file after a CIR for this date.
8 2 . 3 . 4 D U M P 4 . T h i s i s a n i n c r e m e n t a l d u m p o f d e v i c e 4 2 t h a t s p e c i fi e s a l l ^ ^
files modified after 82.3.2. The PFDUMP utility scans the catalogs on J-^
devices 40 and 41 to locate the files on 42. One file, B42 (82.3.3), falls
in this category.
82.3.5 Three files are modified on this date.
82.3.6 DUMP 5. This is an incremental dump of each of the three devices. All
files modified after 82.3.4 are specified by the AD option. Since no DN
is specified, all devices are dumped in turn, producing a dump tape with
three archive files.
82.3.7 DUMP 6. This incremental dump of device 42 specifies all files modified
after 82.3.4. Since 42 is nonmaster, the dump routine scans the catalogs
of the other two devices.
82.3.8 Four files are modified on this date.

17-88

NOS

Version

Analysis

Handbook

Revision

PFDUMP/PFLOAD Example

yims
Date

Action

82.3.9 DUMP 7. An incremental dump of device 40 is made with AD=82.3.7.
Two files qualify.
82.3.9 DUMP 8. An incremental dump of device 41 is made with AD=82.3.7.
The catalog on device 41 contains entries for files B41 and B42. File
B41 is an indirect access file located on device 41, and file B42 is a
direct access file located on device 42. Both files were modified after
82.3.7 and are dumped.
82.3.10 DUMP 9. An incremental dump of devices 40, 41, and 42 is specified,
but device 42 becomes inoperable before the dump is made.
To reestablish permanent files on device 42 with the most recent modifications
available, the device is first initialized and then incrementally loaded, beginning with
the most recent incremental dump tape. Archive dump 8 is the most recent incremental
dump tape and accordingly contains the most recent CIR. This reel is assigned first
and then the CIR read onto a random file. The dump tapes are read in reverse order
with each file on each tape being checked against the CIR. Dump tapes 2 and 3 are
omitted since they do not involve device 42.
For each catalog track on device 42 that is to receive file entries, PFLOAD builds
and maintains an index file. Before each file can be loaded, PFLOAD checks the
index file to see if the file has already been loaded. If it has, the archive duplicate is
skipped; if not, the archive file is loaded and another entry goes into the index file.

Revision

Permanent

File

Utilities

17-89

PFDUMP/PFLOAD Example

After initialization of device 42, the loading runs as follows:
Archive File
DUMP8 tape

Action
The analyst assigns DUMP8 tape and enters the command:
PFLOAD,T=DUMP8,DN=42.

CIR(82.3.9)
B41(82.3.8)
BA2(82.3.8)

The utility reads the CIR from this tape onto a random file. It
then looks for files for device 42 on this tape. B42 qualifies,
and its entry in the CIR is removed. The file B42 is loaded on
device 42. The catalog of this file on device 41 is created.
After loading this file, the utility makes an entry in the index
file as follows:
B42

DOMP7 tape
CTR(82.3.9)

userindex

The utility then requests the next reel.
The analyst assigns this tape, and the utility reads the archive
file and checks it against the CIR loaded from DUMP8 above.
No match is found. The next reel is requested.

A40(82.3.8)
A41(82.3.8)

DUMP6 tape
CIR(82.3.7)

This tape is assigned and then compared with the CIR. B42 is
a file from device 42. However, its entry in the CIR was
removed when it was read from DUMP8.

B42(82.3.5)

DUMP5 tape
CIR(82.3.6)

This tape is assigned and then compared with the CIR. B42 is
from device 42 but it has already been removed from the CIR
and the utility skips this version.

A40(82.3.5)
B4K82.3.5)
B42(82.3.*5)
DUMP4 tape
CIR(82.3.4)

This tape is assigned and compared with the CIR originally
read from DUMP8 tape. It has been removed from the CIR
and this file is skipped.

B42(82.3.3)

17-90 NOS Version 2 Analysis Handbook

Revision M

PFDUMP/PFLOAD Example

Archive File
DUMP1 tape
A40(82.3.1)

Action
This tape, produced by a full dump, contains all the files that
were on the permanent file system when the dump was made
(82.3.1). These files are checked against CIR (82.3.9). A match
is found with A42. This file is loaded.

A42(82.3.1)
A41(82.3.1)
B41(82.3.1)
B42(82.3.1)
Device 42 now has the same files with the same update status
that they had on 82.3.9 when the last incremental dump was
made.

Revision M

Permanent File Utilities 17-91

Release Disk Space (PFREL)

Release Disk Space (PFREL)
The PFREL utility releases the disk space of files that reside on tape alternate storage
or MSE if the files' backup requirements are met.20 PFREL can be called directly or
used with a file selection utility such as GENPFD in the following sequence.
First, execute PFREL with inhibit processing (IP parameter) and the summary file (S
parameter) selected. Files can be excluded by specifying selection parameters. In
particular, OP=A can be used with BD and BT to exclude files that have been
recently accessed. For this example, enter the following command.
PFREL, IP, S, OP=A, BD=yymmdd, BT=hhmmss, FM=f ami 1 yname.

Second, execute the file selection utility GENPFD using the summary file generated
in step 1 as input. A utility directives file will be generated containing the UI and
PF parameters for the selected files. Refer to section 12, Tape Alternate Storage, for
a description of the GENPFD utility.
Third, reexecute PFREL without specifying the IP parameter and using the utility
directives file generated in step 2 as input. For this example, enter the following
command.
P F R E L , I = d i r fi l e .

The PFREL utility will not release the disk space of files cataloged on user name
SYSTEMX or on the MSE user names SUBFAMO through SUBFAM7 even if the
selection criteria are met.

20. Refer to PFDUMP in an MSE or Tape Alternate Storage Environment earlier in this section for a
discussion
of
backup
requirements.

17-92

NOS

Version

Analysis

Handbook

Revision

>-3B%.

Q u e u e d / D a y fi l e

a^m\

/#•*■*<

Utilities

Queued
File
Utilities
....
Calling
the
Queued
File
Utilities
.•
Console
Input
Batch
Input
....
Te r m i n a l
Input
Parameters for the Queued File Utilities
Description of Queued File Utility Parameters
File
Preassignment
Active
and
Inactive
Queued
Files
Queued
File
Utility
Routines
DFLIST
DFTERM
LDLIST
...'....'.
Q A LT E R
,
QDUMP
.
QFTLIST
QLIST
QLOAD
QMOVE
QREC

18-1
18-2
18-2
1 8 - 11
1 8 - 11
1 8 - 11
18-14
18-26
18-26
18-27
is-27
18-27
18-31
18-31
18-37
18-41
18-41
18-42
18-46
18-50

D a y fi l e

18-56

Dumping

Utilities

'**\

Queued/Dayfile Utilities

Several utility programs control queued input and output files and system, account,
error log, and binary maintenance log dayfiles. The utility programs are divided into
the following two groups, according to the type of selective processing they do.
• The queued file utilities are 10 utilities under the control of the queued file
supervisor program QFSP. These utilities select for processing queued files or
dayfiles that share certain characteristics you specify such as device residence, file
destination, and job sequence name.
• The dayfile dumping utilities are five independent utilities that dump all or selected
parts of the active system dayfile, account dayfile, error log, or binary maintenance
log. These utilities each process the contents of a single file according to criteria
you specify.

Queued File Utilities
The names and functions of the queued file utilities follow. The rest of this section
includes detailed information about the call and operation of each utility.
Utility

Description

DFLIST Lists dayfiles that have been made permanent files by the DFTERM
utility.
DFTERM Terminates an active or inactive dayfile and retains it as a direct
access permanent file.
LDLIST Lists queued files present on a QDUMP dump tape.
QALTER Alters routing information associated with active queued files; purges
active queued files.
QDUMP Dumps queued files to a tape or disk.
QFTLIST Lists detailed information about active queued files.
QLIST Lists inactive queued files.
QLOAD Loads files dumped by QDUMP as queued files.
QMOVE Moves queued files from one disk device to another.
QREC Deactivates or activates selected queued files; purges inactive queued
files.

Revision M

Queued/Dayfile Utilities 18-1

Calling the Queued File Utilities

Calling the Queued FUe Utilities
All queued file utility operations, except DFLIST, LDLIST, and QLIST, can be initiated
through console input to a K display. All queued file utilities except DFLIST,
DFTERM, QALTER, and QFTLIST can be initiated through entries made at the system
console (under DIS or DSD control, including procedure files), card input (batch), or
terminal entries. DFTERM, DFLIST, QALTER, and QFTLIST operation can be initiated
only through entries made at the system console. However, in all cases, for batch and
terminal input, you must be validated for system origin privileges, the system must be
in debug mode, and you must observe certain parameter order dependencies. Since
LDLIST, QDUMP, and QLOAD require preassignment of the dump file, only DIS,
batch, or terminal input is appropriate for these utilities. DFLIST, DFTERM, LDLIST,
QDUMP, QFTLIST, and QLIST can access files on an inaccessible device. QMOVE can
read files from an inaccessible device, but the job may get rolled out if QMOVE
attempts to move files to another inaccessible device. If this happens, drop the job and
attempt a QDUMP.

Console Input
Input from a console through a K display requires the following sequence of entries
and responses. These procedures do not apply to DFLIST, QLIST, or LDLIST, because
K displays are not available for these utilities.
1. Call QFSP by entering:
X.QFSP.

The B,0 display indicates the job sequence name of QFSP. To the right of the entry
this message appears:
REQUEST *K* DISPLAY

2. Activate the K display for that control point by entering:
K.jsn.

Parameter Description
Job sequence name of QFSP as specified on the B,0 display. "^S

jsn

The QFSP K display shown in figure 18-1 appears on the left screen. Instructions
on the display describe how to select the desired utility.

18-2

NOS

Version

Analysis

Handbook

Revision

Console Input

K. QFSP.

jsn

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
QUEUED FILE SUPERVISOR

ENTER K . UTILITY.
UTILITY
QDUMP
QLOAD
QMOVE
QREC
DFTERM
QFTLIST
QALTER

yams.

DESCRIPTION
QUEUED FILE DUMP PROCESSOR.
QUEUED FILE LOAD PROCESSOR.
QUEUED FILE MOVE PROCESSOR.
PROCESS QUEUED FILES.
TERMINATE DAYFILES.
LIST ACTIVE QUEUED FILES.
ALTER ACTIVE QUEUED FILES.

Figure 18-1. QFSP K Display (Left Screen)

0«^S

r
Revision M

Queued/Dayfile Utilities 18-3

Console Input

3. Select the desired utility by entering:
K.utility

Parameter Description
utility One of the utilities shown in the K display, figure 18-1.
The parameters available under the chosen utility appear on the left screen as the
initial K display for the utility. Figures 18-6, 18-14 through 18-16, 18-19 through
18-21, 18-23 through 18-25, and 18-28 through 18-30 exhibit initial K displays for
the various utilities. Different parameters are available with the different utilities.
(Refer to Description of Queued File Utilities later in this section.)
It is also possible to call each utility directly by substituting the following
procedure for steps 1, 2, and 3.
a. Call the desired utility by entering:
s&Ss

X.utility

Parameter Description
utility One of the utilities shown in figure 18-1.
The B,0 display indicates the job sequence name of the chosen utility. This
message also appears:
REQUEST *K* DISPLAY

b. Activate the initial K display for the chosen utility by entering:
K.jsn.

Parameter Description
jsn. Job sequence name as specified on the B,0 display.
c. Commands and directives are available to aid in the use of the utilities and
direct processing. A right screen display lists and defines the commands and
directives. Activate this K display by entering:
KK.

Figures 18-2 through 18-5 show the resultant QFSP K display on the right
screen.

18-4

NOS

Version

Analysis

Handbook

Revision

Console Input

utility

jsn

K DISPLAY C O M M A N D S

PA G E

G
O
OUT
RESET
STOP

PROCEED WITH PROCESSING.
RELEASE FILE SPECIFIED BY *L* PARAMETER TO PRINTER.
RESET PARAMETERS TO DEFAULT VALUES.
TERMINATE INPUT, END RUN.

PAGE LEFT SCREEN FORWARD.
PAGE LEFT SCREEN BACKWARD.
PAGE RIGHT SCREEN FORWARD.
PAGE RIGHT SCREEN BACKWARD.

(
)

Figure 18-2. QFSP K Display (Right Screen) (Page 1 of 4)

K DISPLAY COMMANDS

PAGE 2 OF 4

CLEAR SET BOTH SCREENS TO FIRST PAGE OF K DISPLAY.
(QREC, DFTERM, QFTLIST, QALTER).
ERROR TOGGLE STATUS OF ERRORED FILE PROCESSING.
(QDUMP, QLOAD, QMOVE).
FAMILY IF ENTERED, ENTRIES WILL BE MADE IN THE FOT FOR
THE INACTIVE FAMILIES AND THE FILES WILL BE QUEUED,
(QREC, QLOAD, QMOVE).
LID IF ENTERED, ENTRIES WILL BE MADE IN THE LID TABLE
FOR THE INACTIVE LIDS AND THE FILES WILL BE QUEUED
(QREC, QLOAD, QMOVE).
LIST DISPLAY JSN-S OF ACTIVE/INACTIVE QUEUED FILES ON
RIGHT SCREEN. (QREC, DFTERM, QALTER, QFTLIST).
REWIND IF ENTERED, DUMP/LOAD FILE WILL BE REWOUND WHEN
•GO* COMMAND IS ENTERED. (QDUMP AND QLOAD).

Figure 18-3. QFSP K Display (Right Screen) (Page 2 of 4)

Revision M

Queued/Dayfile Utilities 18-5

Console Input

>)
DIRECTIVE FORMATS

PAGE 3 OF 4

DA=YYMMDD
DA=YYMMDD-YYMMDD
DA=ALL

PROCESS THIS DATE ONLY.
PROCESS ALL DATES IN SPECIFIED RANGE.
PROCESS ALL DATES.

UI=XXXXXX
UI=XXXXXX-YYYYYY

PROCESS THIS UNDER INDEX ONLY.
PROCESS ALL INDICES IN SPECIFIED RANGE.

TUI=XXXXXX
TUI=XXXXXX-YYYYYY

PROCESS THIS USER INDEX ONLY.
PROCESS ALL INDICES IN SPECIFIED RANGE.

FS=XXXXXX
FS=XXXXXX-YYYYYY

PROCESS THIS FILE SIZE ONLY.
PROCESS ALL SIZES IN SPECIFIED RANGE.
777777B INCLUDES ALL LARGER SIZES.

ID=XX
ID=XX-YY

PROCESS THIS ID ONLY.
PROCESS ALL ID-S IN SPECIFIED RANGE.

FC=F1

PROCESS THIS FORMS CODE ONLY.
PROCESS ALL FORMS CODES IN LIST.
PROCESS ALL FORMS CODES IN THE RANGE

FC=F1/F2/F3
FC=F1-F2

Figure 18-4. QFSP K Display (Right Screen) (Page 3 of 4)
PAGE 4 OF 4

DIRECTIVE FORMATS
DS=DT FILE DESTINATION=DISPOSITION TYPE.

DESCRIPTION

BC
RB

BATCH.
REMOTE BATCH.

DESCRIPTION

IN
PL
P2
LS
LX
W
T
ALL

INPUT.
PLOT.
512 PRINTER.
580-16 PRINTER.
5870 NIP.
WAIT QUEUE.
ALL QUEUES.
NO QUEUES.

PU
PR
LR
LT
LY
SF

PUNCH.
ANY PRINTER.
580-12 PRINTER.
580-20 PRINTER.
5970 NIP.
SPECIAL QUEUE TYPES.
ALL PRINT QUEUES.

NONE

Figure 18-5. QFSP K Display (Right Screen) (Page 4 of 4)

■^^s

18-6 NOS Version 2 Analysis Handbook

Revision M

Console Input
j^3*-

Following is a list of the queued file utility commands included on the first two
pages of the QFSP K display (refer to figures 18-2 and 18-3) and a description
of each.
Command

Description

CLEAR

Used in conjunction with the LIST command; returns the right
screen K display to the list of processing commands initially
displayed (refer to figure 18-2) and returns the left screen K
display to the first page.

ERROR

If the QDUMP utility is active, enabling this command causes
files on which unrecoverable read errors were encountered to be
dumped with the errors listed on the output file. Disabling this
command causes these files to be ignored. The default under
QDUMP is enabled.
If the QLOAD utility is active, enabling this command causes
such files to be loaded with the errors listed on the output file.
Disabling the command causes such files to be ignored. The
default under QLOAD is disabled.

If the QMOVE utility is active, enabling this command causes
such files to be moved with errors listed on the output file.
Disabling this command causes such files to be ignored. The
default under QMOVE is disabled.
Entry of this command toggles setting of this command.
FAMILY

Specifies whether or not files are queued when creation or
destination families are not active [not in family ordinal table
(FOT)]. Default is not to queue these files. When the FAMILY
command is specified, entries are made in the FOT for inactive
families and the files are queued. This command applies only to
the QLOAD, QMOVE, and QREC utilities.

Directs the active utility to proceed with the processing of the
entered parameters. When the processing is complete, the left
screen K display is reset to the default values.

LID

Specifies whether or not files are queued when the creation
logical identifier (LID) is not in the LID table. Default is not to
queue these files. When the LID command is specified, entries
are made in the LID table and the files are queued. This
command applies only to the QLOAD, QMOVE, and QREC
utilities.

yflTJP^\

Revision M

Queued/Dayfile Utilities 18-7

Console Input
j&*®$S

Command

Description

LIST

If the DFTERM utility is active, this command displays a list
of all permanent dayfiles (refer to figure 18-7). The list of files
displayed is also written on the output file specified by the
DFTERM L parameter.
If the QALTER or QFTLIST utility is active, this command
displays a list of active queued files on the right screen K
display (refer to figure 18-11). The list of files is also written
on the output file specified by the QALTER or QFTLIST L
parameter.
If the QREC utility is active, this command displays a list of
inactive queued files on the right screen K display (refer to
figure 18-31). The list of files displayed is also written on the
output file specified by the QREC L parameter.

LIST=qft

Displays detailed information about the active queued file at
QFT ordinal qft on the right screen K display (refer to figure
18-12) and writes the information to the output file specified by
the QALTER or QFTLIST L parameter. This form of LIST is
accepted only by QALTER and QFTLIST.

OUT

Sends the output file specified by the L option of each utility to
the print queue for immediate printing. Any information that
has been or is currently displayed on the right screen K display
via the LIST command is also included with the disposed
output. In addition, if the LIST command is currently active,
the list displayed on the right screen is disposed, and the
initial right screen K display shown in figure 18-2 is returned
automatically.

RESET

Resets all options displayed on the left screen K display to
their default values.

REWIND

Rewinds the load or dump file specified by the FN parameter
before processing. This command applies only to the QLOAD
and QDUMP utilities.

STOP

Terminates the active utility and ends the K-display interaction.

Pages the left screen forward.
Pages the left screen backward.
Pages the right screen forward.

)

Pages the right screen backward.

The third and fourth pages of the QFSP K display (refer to figures 18-4 and 18-5)
show directive formats. These directives are described in detail under Parameters for
the Queued File Utilities later in this section.

18-8 NOS Version 2 Analysis Handbook

Revision M

f-*ms

Console Input
0$0S

5. Select the desired parameters by entering:
K.opt1=vali,opt2=val2,•..,optn=valn

The opti = vali are selected from the parameter list on the initial K display for the
chosen utility.
The option parameter entries are issued to the job dayfile, which is included in the
output file specified by the L parameter for each utility (refer to Parameters for the
Queued File Utilities later in this section).
If the FM parameter is specified for QDUMP, QMOVE, or QREC (indicating the
processing of queued files for only the specified family of devices), the initial left
screen display (refer to figures 18-14 through 18-16, 18-23 through 18-25, and 18-28
through 18-30) is replaced by the secondary left screen display (refer to figures
18-17, 18-26, and 18-32). This display closely resembles the initial left screen for
the utility but restricts processing to the family of devices specified. Each device in
the specified family containing inactive queued files is indicated. In addition, any
parameter entered for the utility is reflected in this display. Parameters not entered
remain at default values.
If the FM parameter is not specified, the initial K display remains on the left
screen. However, the display is modified to reflect the parameters entered.
Parameters not entered remain at the default values.
The displays are modified in this manner to provide an opportunity to double-check
the entry. If it is necessary to modify the entry, reenter those parameters that are
to be changed. Entry of incorrect data causes an error message to appear at the
bottom of the left screen K display. In this case, the portion of the entry up to the
point where the error was encountered is processed; the remainder of the entry
(from left to right) is ignored.
6. Initiate execution by entering:
K.GO.

When processing is complete, the left screen K display is reset to default values,
the message
utility COMPLETE (utility is the name of the utility processed)
appears at the bottom of the screen, and the right screen returns to the original
display.
7. Terminate use of the chosen utility and end K-display interaction by entering:
K.STOP.

An output file is generated indicating the queued files or dayfiles processed and any
charges that were made to these files. Examples of output files generated by each
utility are shown in figures 18-7, 18-18, 18-22, 18-27, and 18-33.

Revision

Q u e u e d / D a y fi l e

Utilities

18-9

Console Input

It is also possible to call each utility and specify appropriate parameters without using
K displays; this is the only way to call DFLIST. You do this using a single keyboard •■"sss?\
entry
in
the
following
format.
■'
X.utility(opti=vali,opt2=val2 optn=va ln, I=fl lename, PO=N)

Parameter Description
u t i l i t y A n y q u e u e d fi l e o r d a y fi l e u t i l i t y.
opti=vali Parameters (refer to Parameters for the Queued File Utilities later in
this section).
I=filename Name of alternate input file (optional). This file may contain
K-display utility commands (GO, STOP, RESET, and so on) and
parameters.
PO=N Specifies that no K-display input is allowed. The use of the PO = N
parameter and proper parameter selection allows the utility to run
without additional operator intervention. This parameter is not needed
and should not be entered for QLIST, LDLIST, and DFLIST.
The specified utility processes parameters on the command before the alternate input
file, if any. If the utility is QLIST, LDLIST, or DFLIST or if PO=N is specified, the
requested queued file/dayfile processing proceeds after all command and alternate input
file parameters have been processed (unless a STOP command is encountered on the
alternate input file). If PO=N is omitted from the command and the utility is not one
previously mentioned, the utility requests the K display after processing the command
and alternate input file (unless a STOP command is encountered on the alternate input
file). The K display then reflects the status of all parameters after processing of the
command and alternate input file is complete. If the utility encounters an error while
processing the command or alternate input file, a request for the K display appears on
the DSD B,0 display (except for QLIST, LDLIST, and DFLIST). You may then activate
the K display, enter the correct parameters, and continue processing. However, if
errors are encountered and the utility was invoked by a nonsystem origin job, a
message is issued to the dayfile, and utility processing is terminated.

18-10

NOS

Version

Analysis

Handbook

Revision

Batch Input

Batch Input
To call the utilities from a batch job, you must be validated for system origin
privileges, and the system must be in debug mode. Use the following sequence of
commands to call a utility.
ujn.
USER,username,password,fami 1yname.
uti 1 Ity,opti=vali,opt2=val2,... ,optn=valn,I=fi lename,PO=N.

Parameter Description
utility Any of the following utilities: QREC, QDUMP, QLOAD, QMOVE,
QLIST, or LDLIST.
opti = vali Parameters (refer to Parameters for the Queued File Utilities later in
this section).
I=filename Name of alternate input file (optional). This file may contain
K-display utility commands (GO, STOP, RESET, and so on) and
parameters.
PO=N Specifies that no K-display input is allowed. The use of the PO=N
parameter and proper parameter selection allows the utility to run
without additional operator intervention. This parameter is not needed
and should not be entered for QLIST or LDLIST.
The DFLIST, DFTERM, QALTER, and QFTLIST utilities cannot be called from a batch
job. They must be initiated from the system console.
Terminal Input
The format of terminal input for calling the queued file utilities is substantially the
same as that for batch input. You must be validated for system origin privileges, and
the system must be in debug mode. At login, you enter the batch subsystem, call the
desired utility, and enter the appropriate parameters with the command:
util1ty,opti=vali,opt2=val2, • • • ,optn=valn,I=f 1 lename,PO=N

The utility, opt=val, I=filename, and PO = N parameters are the same as described for
batch input.

Parameters for the Queued File Utilities
Tables 18-1 and 18-2 specify the parameters accepted by each queued file utility.
(DFLIST is not included because it does not accept any parameters.) An X indicates
that a parameter is accepted; a blank indicates that a parameter is not accepted. Refer
to the descriptions of parameters following the table for more information.

Revision

Q u e u e d / D a y fi l e

Utilities

1 8 - 11

Parameters for the Queued File Utilities

Table 18-1. Queued File Utility Parameters (DFTERM through QFTLIST)
Parameter DFTERM LDLIST QALTER QDUMP QFTLIST
BC
DA
DD
DF
DN
FC
FM
FN
FS
FT
FU
ID
JSN
L
LA
LD
LO
MI
NAL
NDC
NDF
NEC
NF
NFC
NID
NLD
NM
NPR
NRC
NUN
OP
PO
RB
SC
TF
TP
TUI
UA
UI
UJN
UN

18-12

NOS

Version

Analysis

Handbook

Revision

Parameters for the Queued File Utilities

Table 18-2. Queued File Utility Parameters (QLIST through QREC)
Parameter

^pfcs

QLIST

QLOAD

QMOVE

QREC

BC
DA
DD
DF
DN
FC
FM
FN
FS
FT
FU
ID
JSN
L
LA
LD
LO
MI
NAL
NDC
NDF
NEC
NF
NFC
NID
NLD
NM
NPR
NRC
NUN
OP
PO
RB
SC
TF
TP
TUI
UA
UI
UJN
UN

Revision M

Queued/Dayfile Utilities 18-13

Description of Queued File Utility Parameters

Description of Queued File Utility Parameters
Parameter Description
BC=dt Queued files destined for local batch devices can be selected for
processing by disposition type (dt).
dt

Description

ALL

Files of all disposition types.

Input files.

580-12 printer files.

580-16 printer files.

580-20 printer files.

5870 printer files.

5970 printer files.

NONE

No files.

PH,PU

Punch files.

Plot files.

Files that can print on any printer.

All printer files.

512 printer files.

Installation-defined special files; cai
QALTER or QFTLIST.

**-**^!?\

WT Queued files with a wait disposition.
The BC entry can be specified more than once, with each successive
entry reversing the previously established condition. By default, all
disposition types are selected; so any entry actually clears the
automatic selection. For example, BC = PU means local
batch-destined punch files are not to be processed. However, a
second BC = PU entry reenables processing of local batch-destined
punch files.
If BC=ALL or BC = NONE is specified, processing of all disposition
types is either enabled or disabled, respectively. If all disposition
types are currently enabled, entering BC = ALL has no effect.
Likewise, entering BC=NONE has no effect if all disposition types
are disabled.

18-14

NOS

Version

Analysis

Handbook

Revision

Description of Queued File Utility Parameters

Parameter

Description

DA=yymmdd

Processing date in the form year month day. If one date is
specified, only queued files created on that day are processed. If two
dates, separated by a hyphen, are specified (for example,
820130-820213), all queued files created within the specified range
(including the end dates) are processed. If DA=ALL is specified, all
queued files are processed. If this parameter is omitted with
utilities other than QLIST, queued files created five days prior to
the current date are processed. If this parameter is omitted with
QLIST, all inactive queued files, regardless of creation date, are
processed.

DD=dn

Destination device to which files are to be loaded or moved. The
DF parameter must be specified before the DD parameter. If DF is
specified, DD must also be specified. Since QMOVE requires DF,
DD must also be specified.

DF=familyname

Family of devices to which files are to be loaded or moved. With
QMOVE, this parameter must be specified.
With QALTER or QFTLIST, DF must be used with the UN
parameter. The utility will process files belonging to the remote
terminal identified by these parameters.

DN=dn
0$ms

The 1- or 2-digit device number (0 through 77s). With utilities other
than DFTERM, this parameter specifies the device to be processed,
dumped, or loaded. The FM parameter must be specified before the
DN parameter. Default is all devices.
With DFTERM, this parameter specifies the device on which the
inactive dayfile resides or on which the new dayfile will reside if
the active dayfile is terminated. Default is the device on which the
current dayfile resides. If the FM parameter is specified, the default
for DF is zero.

i fi ^ N

/$m\

Revision M

Queued/Dayfile Utilities 18-15

Description of Queued File Utility Parameters

Parameter

Description

FC=fc

Forms code for output files considered for processing. This
parameter does not deselect input files.
fc

Description

ALL

All files are considered for processing regardless
of forms codes.

fci/fC2/fC3

fci is 2 alphanumeric characters or **, indicating
null forms codes. Up to three forms codes or **
can be specified; files with the specified forms
code(s) are considered for processing.

fci-fC2

fci is 2 alphanumeric characters or **. The 6-bit
display code value of fci must be less than or
equal to the 6-bit display code value of fc2. fc2
can be ** only if fci is also **. Files in the range
fci through fc2 are considered for processing; if fci
equals **, files with no forms code are (also)
considered for processing.

A subsequent FC entry replaces any FC entry previously made.
Default is to consider all files for processing regardless of forms
codes.
FM=familyname

Name of family to be processed. Default is to process all queued
files on all devices in all families.
With DFTERM, this parameter specifies the family of devices on
which the inactive dayfile resides or on which the new dayfile will
reside if the active dayfile is terminated. If an active dayfile is
terminated, default is the same family as that in which the dayfile
being terminated resides.

FN=filename

File name of dump or load file. Default is FN = QFILES.

FS=x

File size in PRUs. The value can be entered as a single file size
(FS=100) or as a range of file sizes (FS=10-400). x ^ 777777s.
Default is to consider all files for processing regardless of file size.

18-16 NOS Version 2 Analysis Handbook

Revision M

/ C ^ >

Description of Queued File Utility Parameters

Parameter

Description

FT=t

Type of dayfile to be terminated by the DFTERM utility.
t

Description

ACCOUNT Account dayfile.
D AY F I L E S y s t e m d a y fi l e .
ERRLOG Error log.
MAINLOG Binary maintenance log.
This parameter causes the FM and DN parameters to be updated to
reflect the current family and device number of the dayfile specified
by FT. Default is FT = DAYFILE.
FU=familyname

Name of family under which the queued files to be processed were
created. Queued files created by users of one family can reside on
nonremovable devices of another family. The FM parameter
specifies the family of devices that will be searched for queued files
created by users validated in the family specified by the FU
parameter. Default is to process queued files created by users in all
families.

ID = id

The 1- or 2-digit octal number (0 through 67s) specifying that only
local batch-destined queued files assigned to that identifier are to
be processed. This parameter does not deselect remote
batch-destined files. If two identifiers, separated by a hyphen, are
specified (for example, ID = 6-30), any queued file with an identifier
in the specified range (including the end points) is processed.
Default is to process all queued files regardless of identifier.

JSN = jsn

The 4-character job sequence name of queued files to be processed,
dumped, loaded, or moved. At most, five job sequence names can be
specified. If a job sequence name is specified more than once, it is
removed from the list. Default is to process all queued files
regardless of job sequence name.

L=outfile

The 1- to 7-character name of the file to receive output. Default is
L=OUTPUT. Specify L=0 if no output file is needed.

LA = level

The 1- to 7-character name that specifies the lower limit of the
range of access levels to process. If this parameter is specified, the
UA parameter must also be specified. If neither LA nor UA is
specified, the default is that all access levels are selected.

LD = lid

The 3-character logical identifier of the mainframe with which the
file is associated. LD = 0 means process all files without LIDs. A
subsequent LD entry replaces any LD entry previously made.
Default is to process all queued files regardless of logical identifier.

iffP^^

Revision M

Queued/Dayfile Utilities 18-17

Description of Queued File Utility Parameters

Parameter

Description

LO=opt

List option associated with the output file specified by the L
parameter.
opt

Description

F All routing information for each file.
S Condensed listing of each selected queued file.
MI = id

The 2-character machine identifier indicating the mainframe on
which the queued files to be processed currently reside. If
MI=ALL is specified, any queued file residing on any mainframe
is processed. The MI entry is cleared if previously specified; that
is, specifying two identical MI entries is the same as not
specifying any at all. If the MI entry is cleared on the K display,
the id is not checked. Default is the machine identifier of the
mainframe where the utility is being run.

NAL=level

QALTER can change the access level of a queued file. The new
access level must be within the origin type limits for the file and
within the device limits of the device on which the file resides.
This parameter is restricted to users with security administrator
privileges.

NDC=dt

QALTER can change a print file's disposition type while the file
is in the queue. New disposition types that can be selected
include the following.

NDF=familyname

Description

Any printer.

580-12 printer.

580-16 printer.

580-20 printer.

5870 printer.

5970 printer.

NONE

No device code specified.

Any printer.

512 printer.

New destination family name associated with selected output
files. This parameter is meaningful only when altering files
routed to or changed to remote batch. A subsequent NDF entry
replaces any previous NDF entry. Default is no change in
destination family name.

18-18 NOS Version 2 Analysis Handbook

Revision M

Description of Queued File Utility Parameters

Parameter Description
NEC=ex QALTER can change an output file's external characteristics. New
external characteristics that can be selected include the following.
For print files:
ex Description
A41 ASCII graphic 48-character set.
A6 ASCII graphic 63/64-character set.
A9 ASCII graphic 95-character set.
B41 CDC graphic 48-character set.
B6 CDC graphic 63/64-character set.
For punch files:
ex Description
AS

Punch ASCII.

Punch system binary.

Punch 026 mode.

Punch 80-column binary,

Punch 029 mode.

For plot files:
ex Description
T 6 Tr a n s p a r e n t 6 b i t .

T 8 Tr a n s p a r e n t 8 b i t .
NF=n Decimal number of media files to skip. A media file contains all
queued files that are dumped by one QDUMP operation. Each of
these dumped queued files exists as a record on the media file. If
two QDUMP operations are performed, the dumped queued files
exist as records on two files. This parameter can be used in
conjunction with the SC parameter. Default is 0.
NFC=fc Two alphanumeric characters or ** (null forms code) specifying the
new forms code associated with selected output files. The NFC
entry is cleared if previously specified; that is, specifying two
identical NFC entries is the same as not specifying any at all.
Default is no change in forms code.

1. Not supported. Provided for NOS/BE compatibility.

Revision

Q u e u e d / D a y fi l e

Utilities

18-19

Description of Queued File Utility Parameters

Parameter

Description

NID=id

The 1- or 2-digit number (0 through 67s) specifying the new file
identifier associated with selected output files. This parameter is
meaningful only when altering files routed to or changed to local
batch. The NID entry is cleared if previously specified; that is,
specifying two identical NID entries is the same as not specifying
any at all. Default is no change in file identifier.

NLD=lid

The 3-character logical identifier specifying the new logical
identifier associated with selected files. NLD=0 will remove the
LID from selected files. A subsequent NLD entry replaces any NLD
entry previously made. Default is no change in logical identifier.

NM=filename

The 1- to 5-character name of the direct access permanent file on
which DFTERM writes the terminated dayfile. DFTERM adds a
2-character prefix indicating the type of dayfile being terminated
(AC, DF, ML, or ER). Default is automatic naming of the file by
DFTERM as follows:
• The first two characters indicate the type of dayfile being
terminated (AC, DF, ML, or ER).
• The third character is a sequence number (A through 9).
• The next two characters indicate the month.
• The last two characters indicate the day of the month.

NPR=p

The 1- to 4-digit number (0 through 7777s) specifying the new
queue priority associated with selected output files. The NPR entry
is cleared if previously specified; that is, specifying two identical
NPR entries is the same as not specifying any at all. Default is no
change in queue priority.

NRC=c

The 1- or 2-digit number (0 through 77s) specifying the new repeat
count associated with selected output files. The NRC entry is
cleared if previously specified; that is, specifying two identical NRC
entries is the same as not specifying any at all. Default is no
change in repeat count.

NUN=username

New destination user name associated with selected output files.
This parameter is meaningful only when altering any files routed to
or changed to remote batch. The NUN entry is cleared if previously
specified; that is, specifying two identical NUN entries is the same
as not specifying any at all. Default is no change in destination
user name.

18-20 NOS Version 2 Analysis Handbook

Revision M

Description of Queued File Utility Parameters

Parameter Description
OP=opt Processing option specifying the function to be performed by each
utility.
With QREC, opt can be any of the following. Default is OP=RI.
opt Description
DI Selected active queued files are made inactive and the
remaining active queued files are ignored.
PI Selected inactive queued files are purged, and the remaining
inactive queued files are ignored.
RI Selected inactive queued files are activated (requeued), and
the remaining inactive queued files are ignored.
RP Selected inactive queued files are activated (requeued), and
the remaining inactive queued files are purged.
With QALTER, opt specifies the destination to which the selected
queued files should be changed; it can be one of the following.
Default is OP=NC.
opt Description
BC Change to local batch.
NC Do not change file destination.
P R P u r g e fi l e s .
RB Change to remote batch.
With DFTERM, opt specifies whether active or inactive dayfiles will
be terminated. With QLOAD and QMOVE, opt specifies whether the
loaded or moved queued files will be active or inactive. With these
utilities, opt can be one of the following. Default is OP=A.
opt Description
A Active queued files/dayfiles are specified.
I Inactive queued files/dayfiles are specified.

0A**\

Revision

Q u e u e d / D a y fi l e

Utilities

18-21

Description of Queued File Utility Parameters

Parameter

Description

PO=opt

Processing option specifying the function to be performed.
opt Description
E Errored file processing status is toggled. Default conditions
for queued file utilities include:
QDUMP Dump file.
QLOAD Do not load file.
QMOVE Do not move file.
F Entries are made in FOT for inactive families and the files
are queued.
I Activate inactive input queued files when the owner family
is not active.
L Entries are made in the LID table for inactive LIDs and the
files are queued.
N Only command directives are processed. The K display is
available to monitor utility progress, but no K-display input
is allowed. The N option is implied on all nonsystem origin
jobs.
R The dump or load file is rewound before processing begins.
U Unconditionally dump, load, recover, or move files (the only
restrictions are device security access limits).

/^?\

18-22 NOS Version 2 Analysis Handbook

Revision M

Description of Queued File Utility Parameters

Parameter

Description

RB=dt

Queued files destined for remote batch devices can be selected for
processing by disposition type (dt).
dt

Description

ALL Files of all disposition types.
IN

Input

fi l e s .

L R 5 8 0 - 1 2 p r i n t e r fi l e s .
L S 5 8 0 - 1 6 p r i n t e r fi l e s .
L T 5 8 0 - 2 0 p r i n t e r fi l e s .
L X 5 8 7 0 p r i n t e r fi l e s .
L Y 5 9 7 0 p r i n t e r fi l e s .
N O N E N o fi l e s .
P H , P U P u n c h fi l e s .
PL

Plot

fi l e s .

PR Files that can print on any printer.
P R I N T A l l p r i n t e r fi l e s .
P 2 5 1 2 p r i n t e r fi l e s .
SF Installation-defined special files; cannot be used with
QALTER or QFTLIST.
WT Queued files with a wait disposition.
The RB entry can be specified more than once, with each successive
entry reversing the previously established condition. By default, all
disposition types are selected; so any entry actually clears the
automatic selection. For example, RB = PU means remote
batch-destined punch files are not to be processed. However, a
second RB = PU entry reenables processing of remote batch-destined
punch files.

If RB = ALL or RB = NONE is specified, processing of all disposition
types is either enabled or disabled, respectively. If all disposition
types are currently enabled, entering RB = ALL has no effect.
Likewise, entering RB = NONE has no effect if all disposition types
are disabled.

Revision M

Queued/Dayfile Utilities 18-23

Description of Queued File Utility Parameters

Parameter

Description

SC=n

Decimal number of queued files (and hence records on the dump
file) to be skipped before the queue selection begins. Skipping
begins at the point on the dump file indicated by the NF
parameter. This parameter allows a restart load to begin from the
last aborted queue loaded by QLOAD. Default is SC = 0.

TF=familyname

Name of family for remote batch-destined files to be selected. By
using the TF parameter with the TUI parameter, files destined for
a particular remote batch terminal can be selected. Local
batch-destined files are not deselected by this parameter. Default is
all families selected.

TP = t

Type of files to move or dump. Default is TP=ALL.
t

Description
Active files.

ALL

Active and inactive files.

Inactive files.

TUI = userindex

The 1- to 6-digit value plus a radix that specifies the destination
terminal user index for remote batch destined output files. If one
userindex is specified (xxxxxx), only that user index is processed. If
a range is specified (xxxxxx-yyyyyy), all indexes in the specified
range are processed. If TUI = 0, no terminal user index is specified.
Default is TUI = 0.

UA=level

The 1- to 7-character name that specifies the upper limit of the
range of access levels to process. If this parameter is specified, the
LA parameter must also be specified. If neither LA nor UA is
specified, the default is that all access levels are selected.

UI = userindex

User index under which queued files to be processed were created.
If two user indexes, separated by a hyphen, are specified (for
example, 75-162), all queued files created by all users having
indexes within this range (including the end points) are processed.
Default is to process all queued files regardless of user index.

18-24 NOS Version 2 Analysis Handbook

Revision M

- ^ ^ i .

Description of Queued File Utility Parameters
r0^

Parameter

Description

UJN = ujn

The 1- to 7-character user job name specified on Job commands
associated with queued files being listed or altered. Only one name
can be specified. A subsequent UJN entry replaces any UJN entry
previously made. This parameter in conjunction with the JSN
parameter uniquely describes which files are to be processed.
Default is no UJN specified.

UN=username

Destination user name within the family specified by the DF option.
UN and DF must be specified together. The utility (QALTER or
QFTLIST) will process files belonging to the remote terminal
identified by these parameters. The UN entry is cleared if
previously specified; that is, specifying two identical UN entries is
the same as not specifying any at all.

NOTE
If the currently displayed value for JSN, NFC, NID, NPR, NRC, NUN, or UN is
reentered, the value for the specified parameter is cleared.

Revision M

Queued/Dayfile Utilities 18-25

File Preassignment

File Preassignment
When using the LDLIST, QDUMP, and QLOAD utilities, the dump or load file must be
preassigned. This can be done by using a LABEL or an ASSIGN command. For
example, the following commands can be used.
LABEL,QFILES,VSN=DMP1,D=HY.
or
ASSIGN,MS,QFILES.

If no dump file is present, QDUMP will write on a local mass storage file; LDLIST
and QLOAD will attempt to read an empty file and terminate.
Active and Inactive Queued Files
A queued file can be active or inactive. All queued files are originally active upon
entering a queue. A queued file is deactivated (made inactive) when its entry is
removed from the queued file table (QFT) and a corresponding entry is created in the
inactive queued file table (IQFT) on the mass storage device where the queued file
resides. An inactive queued file is activated when the entry from the IQFT is removed
and a corresponding entry is created in the QFT. Inactive queued files are not
considered for processing (other than by the queued file utilities), nor do they appear
on any DSD display.
Three queued file utilities can deactivate or activate queued files (QLOAD, QMOVE,
and QREC). QLOAD and QMOVE each transfer queued files from either tape or disk to
a disk device. Upon completion of the transfer, the utility leaves the queued files active
or inactive according to the parameters you have specified. QREC does not perform any
file transfer but only adjusts table entries as described in the preceding paragraph.
These three utilities have uses other than deactivation and activation of queued files
(refer to the description of the appropriate utility and parameters).
Queued files are also deactivated when they are recovered during a level 0 deadstart.
Such files can be activated automatically by an IPRDECK entry that invokes QREC
during a level 0 deadstart. Refer to section 3, Deadstart Decks, for further information
on IPRDECK.

'^St

18-26 NOS Version 2 Analysis Handbook

Revision M

Queued File Utility Routines

Queued File Utility Routines
The queued file utility routines are described next. The parameters available for each
of the routines are listed in table 18-1. The K displays (if any) for each utility are
shown and contain lists of applicable parameters. Output formats for each utility are
also shown.
DFLIST
DFLIST generates a printer listing of all permanent files created by the DFTERM
utility.
DFLIST can be initiated only from the system console directly through this command:
X.DFLIST.

The output generated by DFLIST is the same as that produced by the LIST command
available under the DFTERM utility (refer to figure 18-7).
DFTERM
DFTERM terminates an active or inactive dayfile and retains it as a direct access
permanent file on user name SYSTEMX for later interrogation or processing. When an
active dayfile (that is, the current system dayfile, account dayfile, error log, or binary
maintenance log) is terminated, information in the central memory buffer for that
dayfile is written to mass storage to be included with the permanent file, and a new
active dayfile is started. The new dayfile can reside on the same device, or a new
^ * * d e v i c e c a n b e s p e c i fi e d .
Terminating an inactive dayfile has no effect on the currently active dayfiles. Inactive
dayfiles are not used by the system. Furthermore, the presence of an inactive dayfile
in the system is possible only under unusual conditions. For example, if the system is
deadstarted and the device that previously contained the account dayfile is turned off, a
new account dayfile is started on another device. Two devices in the system now
contain account dayfiles. If both devices are turned on when the system is next
deadstarted, two account dayfiles are recovered. The most recent account dayfile is
made active and is used by the system. The remaining account dayfile is made
inactive.
The DFTERM utility can be initiated only from the system console through a K
display or directly through the DFTERM command. No batch or terminal input is
allowed.
When DFTERM is selected at the system console, the DFTERM K display appears on
the left screen. This display contains a list of all applicable options associated with
DFTERM, their default values, and a short description of each (refer to figure 18-6).

Revision

Q u e u e d / D a y fi l e

Utilities

18-27

DFTERM

A list of the permanent dayfiles is displayed on the right screen when you enter this
command:
K.LIST.

When this command is processed, the right screen K display is automatically replaced
with the DFTERM dayfile list K display (refer to figure 18-7). The information
presented in this display is the same as that generated by the DFLIST utility.
If there are more files than can be displayed on one screen, a message appears at the
bottom of the screen indicating that more files exist. When the LIST command is
entered, a complete list of permanent dayfiles is written to the output file specified by
the DFTERM L parameter; thus, a complete printer listing is provided when the
DFTERM utility is terminated. If it is necessary to obtain the output listing
immediately, enter this command:
K.OUT.

When this command is processed, the initial right screen K display (a list of the "eS^
queued file utility commands) is automatically returned. However, if the OUT command
is not entered, the original right screen K display can be returned by entering the
CLEAR command.
After DFTERM processing is completed, an output file indicating the results of this
processing is generated if the LIST command has been entered at any time during
DFTERM operations. (Refer to figure 18-7, which shows essentially the same format.) If
the LIST command was not entered, no output file is generated.

18-28

NOS

Version

Analysis

Handbook

Revision

DFTERM

K. DFTERM.

jsn

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
DFTERM
ACTIVE
TYPE
DAYFILE
ACCOUNT
ERRLOG
MAINLOG
OPTION

D AY F I L E S — I N A C T I V E D AY F I L E S
FA M I LY D N T Y P E FA M I LY D N
SYST06 2B
SYST06 2B
SYST06 2B
SYST06 2B
DESCRIPTION

^PVs

FT = DAYFILE FILE TYPE TO BE TERMINATED
(DAYFILE, ACCOUNT, ERRLOG, MAINLOG).
FM = SYST06 FAMILY NAME OF NEW DEVICE (1-7 CHARACTERS).
DN = 2B DEVICE NUMBER OF NEW DEVICE (0-77B).
OP = A OPTION (A=ACTIVE or I=INACTIVE).
NM = DAYF PERMANENT FILE NAME OVERRIDES AUTOMATIC NAMING
(1-5 CHARACTERS).
L = OUTPUT OUTPUT FILE (1-7 CHARACTERS).

yam*..

Figure 18-6. DFTERM K Display (Left Screen)

Revision M

Queued/Dayfile Utilities 18-29

DFTERM

K. DFTERM.

jsn

PERMANENT DAYFILE CATALOG '
CATALOG OF PERMANENT DAYFILES (377777). 85/01/16 09.25.43
NUM TYPE
FM/PN
DN PFNAME DATE TIME LENGTH

1
2
3
4
5
6
7
8
9
10
11
12
13
14

DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE

SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06
SYST06

02
02
02
02
02
02
02
02
02
02
02
02
02
02

DFA0116
D F B 0 11 6
D F C 0 11 6
D F D 0 11 6
D F E 0 11 6
D F F 0 11 6
D F G 0 11 6
D F H 0 11 6
D F I 0 11 6
D F J 0 11 6
D F K 0 11 6
D F L 0 11 6
D F M 0 11 6
D F N 0 11 6

85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
85/01/16
08/01/16

08.00.04 20
08.00.34 1
08.01.14 1
08.01.54 1
08.02.33 1
08.03.13 1
08.03.53 1
08.04.33 1
08.05.12 1
08.05.52 1
08.06.45 1
08.07.34 1
08.08.13 1
08.08.30 1

MORE PERMANENT DAYFILES.
ENTER * OUT* FOR A FULL LIST.

Figure 18-7. DFTERM Dayfile list (Right Screen)

y^®^V

18-30 NOS Version 2 Analysis Handbook

Revision M

LDLIST
vgpSN.

LDLIST
LDLIST generates a printer listing of queued files present on a QDUMP dump tape.
Since LDLIST requires a QDUMP dump tape to be preassigned, it should be entered
from DIS or in a batch or terminal job in the form
LDLIST,opti=vali,opt2=val2,...,optn=valn.

opti=vali are parameters available for LDLIST.
The output generated by LDLIST is the same as that produced by QLOAD (refer to
figure 18-22).
QALTER
QALTER displays, lists, and/or alters routing and other information about active
queued files. The utility selects files for processing according to criteria you specify.
QALTER purges selected files from the system when you specify OP = PR.
You may alter the following information associated with the selected files.
File destination.
Access level (requires security administrator privileges).
Print file disposition type (device code).
External characteristics.
Destination LID.
Destination family (remote batch-destined files).
Destination user name (remote batch-destined files).
File identifier (local batch-destined files).

Forms code.
Priority of a queued file.
Repeat count.
Disposition type.

Revision M

Queued/Dayfile Utilities 18-31

QALTER

When QALTER is selected at the system console, the QALTER/QFTLIST K display (3
pages) appears on the left screen. This display contains a list of all applicable ^^
parameters associated with QALTER, their default values, and a short description of
each (refer to figures 18-8 through 18-10). Follow this procedure to alter active queued
files:
1. Enter the selection criteria specifying which files are to be altered (parameters FM,
DN, DF, UN, ID, FC, UJN, LD, LA, UA, BC, RB, and JSN).
2. Ensure that the desired files are selected by inspecting the list of files produced by
the K-display commands LIST or OUT (refer to figures 18-11 through 18-13). If the
file produced by OUT is to be other than OUTPUT or contain a detailed listing of
the selected files, specify such with the L and/or LO parameters before entering
K.OUT.
3. Enter the new information to be associated with the selected files (parameters OP,
NAL, NDC, NEC, NLD, NDF, NUN, NID, NFC, NPR, and NRC). QALTER changes
only information specified via parameter entry.
4. Enter K.GO. QALTER makes the requested changes, issues the message *QALTER
COMPLETE.*, and resets the K-display parameters to their default values.
5. Repeat steps 1 through 4 to alter additional files, or enter K.STOP. to terminate
QALTER activity. After QALTER activity has completed, an output file is generated
indicating the changes made to the queued files (see figure 18-13).
Example:
Use the QALTER utility to divert output files from the local printers to a remote
terminal. The following command alters the routing of all batch output files with a
forms code of AD. "These files are routed to a remote terminal with family name FAM1
and user name USRNAM. The BC and RB parameters explicitly disable input file
selection.
QALTER,PO=N,BC=IN,RB=IN,FC=AD, OP=RB,NDF=FAM1,NUN=USERNAM.

The QFTLIST utility can be used in conjunction with QALTER to ensure that the files
were properly altered. The following command generates a list of all active queued files
belonging to the remote terminal with family name FAM1 and user name USRNAM. ^^\
QFTLIST,PO=N,L0=F,DF=FAM1,UN=USRNAM,BC=NONE.

.^ttfaV

18-32

NOS

Version

Analysis

Handbook

Revision

QALTER

QALTER.

jsn

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version •
PAGE 1 OF 3

QALTER
OPTION

DESCRIPTION
FAMILY FOR DEVICES (1-7 CHARACTERS).
DEVICE NUMBER (0-77B, *ALL*).
DESTINATION FAMILY (1-7 CHARACTERS).
DESTINATION USER (1-7 CHARACTERS).
FILE TO RECEIVE OUTPUT (1-7 CHARACTERS).
LIST OPTION (S=SHORT, F=FULL).

FM =
DN =
DF =
UN »
L =
LO =

ALL
ALL

ID »

O
B
67B

ID RANGE OF FILES TO PROCESS (0-67B).

FC =
UJN =
LD =
LA =
UA =

11/22/33
JOB02

FORMS CODE (2 CHARACTERS OR ••).
USER JOB NAME (1-7 CHARACTERS).
DESTINATION LID (3 CHARACTERS).
LOWER SECURITY ACCESS LEVEL (1-7 CHARACTERS)
UPPER SECURITY ACCESS LEVEL (1-7 CHARACTERS)

SYS06
DEST01
OUTPUT

M06
LVL2
LVL6

Figure 18-8. QALTER/QFTLIST K Display (Left Screen) (Page 1 of 3)
PAGE 2 OF 3

QALTER
OPTION
BC = (DT)
RB = (DT)
0$ms.

DESCRIPTION
DISPOSITION TYPE FOR LOCAL BATCH DEVICES.
DISPOSITION TYPE FOR REMOTE BATCH DEVICES.
SIPPPPLLLLLW
FNULR2RSTXYT
BC
****
-*
* = OPTION SELECTED.
OPTION WILL BE CLEARED IF PREVIOUSLY SELECTED

JSN = AAAA
AAAB
AAAC

JOB SEQUENCE NAME (1-4 CHARACTERS).
JSN WILL BE CLEARED IF PREVIOUSLY ENTERED.

Figure 18-9. QALTER/QFTLIST K Display (Left Screen) (Page 2 of 3)

Qnono^/notrfilo TItilit.ipR 18-33

QALTER
> ^ | y

QALTER

PAGE 3 OF 3

OPTION

DESCRIPTION

OP = NC
NAL = LVL3
NDC = NONE
NEC = A9
NLD = M06
NDF = SYST06

OPTION (BC, RB, NC, PR).
NEW ACCESS LEVEL (1-7 CHARACTERS).
NEW DEVICE CODE (2 CHARACTERS OR NONE).
NEW EXTERNAL CHARACTERISTICS (2 CHARACTERS)
NEW DESTINATION LID (3 CHARACTERS).
NEW DESTINATION FAMILY (1-7 CHARACTERS).

NUN = SYSTEM
NID = 67B
NFC = **
NPR = 7777B
NRC = 30D

NEW DESTINATION USER (1-7 CHARACTERS).
NEW FILE IDENTIFIER (0-67B).
NEW FORMS CODE (2 CHARACTERS OR ••).
NEW PRIORITY FOR OUTPUT (0-7760B).
NEW REPEAT COUNT (0-31D).

Figure 18-10. QALTER/QFTLIST K Display (Left Screen) (Page 3 of 3)

/*^^V

2. Page 3 of 3 of this K display is present for QALTER, but not QFTLIST.

18-34 NOS Version 2 Analysis Handbook

Revision M

QALTER

ACTIVE QUEUE FILE LIST

ORD

JSNS

1
2
3
4
5
6
7
10
11
12
13
16
17
20

AAAOS
AAAPB
AAAQR
AAARB
AAASB
AAATR
AAAUR
AAAVB
AAAWR
AAAXB
AAAYR
AABBR
AABCB
AABDB

DT LID FAMILY
PL
LS
LP
LS
LS
LP
LP
LP
LP
LS M01
LP
LP LBK
LS
LS

USERNAM TUI/ID

EC
T6
A9
LP
A9
A9
LP
LP
LP
LP
A9
LP
LP
A9
A9

55
22
SYST01

ABC1234

1234

22
22
SYST01
SYST01

ABC1234
ABC1234

1234
1234

SYST01

ABC1234

1234

AX
AX

55
AX

22
SYST01
SYST01

ABC1234
ABC1234

1234
1234

LENGTH

AX
AX

22
22

41
41
41
41
41

END OF DISPLAY.

Figure 18-11. QALTER/QFTLIST LIST Command Display (Right Screen)
ACTIVE QUEUE LIST
JSN = AAAD
SERVICE = SYSTEM

ORDINAL =
QUEUE = PRINT

DESTINATION

CREATION
FAMILY = SYST03
LID = M03

FAMILY

LID = M01
USER
TUI/ID
FORMS
DISPOSITION CODE
EXTERNAL CHAR.
INTERNAL CHAR.

USER
USER INDEX
USER JOBNAME
DATE
LENGTH
REPEAT

= 0
= AX
= LP
= LP
= DIS

=
=
=
=
=

0
DIS
85/01/16
2
0

RESIDENCE
FAMILY = SYST01
DEVICE = 2
ACCESS LEVEL

INTERRUPT = NO
PRIORITY = 7110

Figure 18-12. QALTER/QFTLIST LIST=qft Command Display (Right Screen)

Revision M

Queued/Dayfile Utilities 18-35

QALTER
A*^S

QALTER - ALTER/PURGE ACTIVE OUEUED FILES.

OPTION =
NEW FORMS CODE =
NEW PRIORITY =
NEW REPEAT COUNT =

N
C
—N/A-5103
--N/A--

NEW DESTINATION FAMILY NAME
NEW DESTINATION USER NAME
NEW DISPOSITION CODE
NEW DESTINATION LID

PAGE

NEW EXTERNAL CHAR = --N/A—
NEW FILE ID
-N/A—
NEW ACCESS LEVEL = --N/A—

--N/A---N/A---N/A---N/A-REATION

RESIDENCE

i i i i i > i i i i t i t i i » i i t t t i i i i i i i u i i

l I I > I I I I I I I I I < » l t » « » t l » » t I I I I I I U I

I O I I I I I 1 I I I I I I I I

CURRENT
I I I I I I I I I I U I I I I I I

yy/mm/dd. hh.mm.ss.

DESTINATION

1. JSN
SERVICE
QUEUE
ORDINAL

« AAC6
= 1CLASS2
= PRINT
=3

FAMILY = SYS964
= BMS4247
USER
TUI/1D = 4247
DLID

FORMS
= LP
DEVICE
EXT.CHR. = LP
INT.CHR. = DIS

FAMILY
USER
USR INDX
SLID

SYS964
BMS4247
4247

2. JSN
SERVICE
QUEUE
ORDINAL

« AACI
FAMILY ■ SYS964
= TIMESW USER
= BMS4247
= PRINT
TUI/ID = 4247
=5
DLID

FORMS
= LP
DEVICE
EXT.CHR. = LP
INT.CHR. = DIS

FAMILY
USER
USR INDX
SLID

FAMILY = SYST64
SYS964
USR JOBNM= DIS
BMS4247 DATE = 83/07/07 DEVICE =
PRIORITY = 55
4247
INTERRUPT= NO
LENGTH =
REPEAT = 0
ACCESS LV=

3. JSN
SERVICE
QUEUE
ORDINAL

= AACJ
= REMOTE
= PRINT
=6

FAMILY
USER
TUI/ID
DLID

= SYS964
= BMS4247
= 4247

FORMS
= LT
DEVICE
EXT.CHR. = LP
INT.CHR. = DIS

FAMILY
USER
USR INDX
SLID

SYS964
BMS4247
4247

FAMILY = SYST64
USR JOBNM= DIS
DATE = 83/07/07 DEVICE =
INTERRUPT= NO
PRIORITY = 56
LENGTH = 15
REPEAT = 0
ACCESS LV=

4. JSN
SERVICE
QUEUE
ORDINAL

= AACW
= BATCH
= PRINT
= 23

FAMILY
USER
TUI/ID
DLID

= SYS964
FORMS
FAMILY
= LP USER
= BMS4247 DEVICE
= 4247
=
LP
EXT.CHR.
USR INDX
INT.CHR. = DIS SLID

SYS964
BMS4247
4247

FAMILY = SYST64
USR JOBNM= DIS
DATE = 83/07/07 DEVICE =
PRIORITY = 56
1NTERRUPT= YES
LENGTH = 13
REPEAT = 0
ACCESS LV=

SYS964
BMS4247
4247

FAMILY = SYST64
USR JOBNM= DIS
DATE = 83/07/07 DEVICE =
INTERRUPT= YES
PRIORITY = 56
REPEAT = 0
LENGTH =
ACCESS LV=

= AACY
FAMILY = SYS964
FORMS
5. JSN
= BMS4247 DEVICE
= LP
SERVICE = T1MESHR USER
=
4247
= PRINT
EXT.CHR. = LP
QUEUE
TUI/ID
DLID
INT.CHR. = DIS
ORDINAL1 = 25

FAMILY
USER
USR INDX
SLID

FAMILY = SYST64
USR JOBNM= DIS
DATE = 83/07/07 DEVICE =
PRIORITY = 55
INTERRUPT= NO
REPEAT = 0
LENGTH = 13
ACCESS LV=

JSN
SERVICE
QUEUE
ORDINAL

AACZ FAMILY
ICLASS2 USER
PRINT TUI/ID
26
DLID

SYS964 FORMS
BMS4247 DEVICE
4247 EXT.CHR.
INT.CHR.

FAMILY
LP USER
LP USR INDX
DIS SLID

SYS964 USR JOBNM= DIS FAMILY = SYST64
BMS4247 DATE = 83/07/07 DEVICE = 2
4247 INTERRUPT" YES PRIORITY = 56
R E P E AT = 0 L E N G T H = 1 3
ACCESS LV=

JSN
SERVICE
QUEUE
ORDINAL

AADB FAMILY
REMOTE USER
PRINT TUI/ID
30
DLID

SYS964 FORMS
BMS4247 DEVICE
4247 EXT.CHR.
INT.CHR.

FAMILY
LT USER
LP USR INDX
DIS SLID

SYS964 USR JOBNM= DIS FAMILY = SYST64
BMS4247 DATE = 83/07/07 DEVICE = 2
4247 INTERRUPT* YES PRIORITY = 56
R E P E AT = 0 L E N G T H = 1 5
ACCESS LV=

8. JSN
SERVICE
QUEUE
ORDINAL

AADF FAMILY
BATCH USER
PRINT TUI/ID
34
DLID

SYS964 FORMS
BMS4247 DEVICE
4247 EXT.CHR.
INT.CHR.

FAMILY
LP USER
LP USR INDX
DIS SLID

SYS964 USR JOBNM=
BMS4247 DATE
4247 INTERRUPT'
REPEAT '-

/^^\

D I S FA M I LY = S Y S T 6 4
83/07/07 DEVICE " 2
NO PRIORITY = 57
0 LENGTH = 13
ACCESS LV=

Figure 18-13. QALTER Printer listing/Output File

A*ms

18-36 NOS Version 2 Analysis Handbook

Revision M

QDUMP

QDUMP
QDUMP dumps selected queued files from a single device, a family of devices, or all
devices on the system. These queued files can be dumped to a tape or disk. When
active queued files are dumped, the QFT is searched to obtain the proper file. When
inactive queues are dumped, the IQFT is searched. QDUMP also provides a listing of
all files dumped with information about each file processed.
For a secured system, QDUMP determines the maximum range of access levels that
can be dumped. If the LA and UA parameters have been used to select access level
limits, these limits will be used. If no access level limits were selected, QDUMP uses
the device limits determined by taking the lowest lower access limit and the highest
upper access limit of all the devices to be processed. If this range of access levels is
not within the system access level limits, QDUMP issues a diagnostic message.
When QDUMP is selected at the system console, the initial QDUMP K display (3
pages) appears on the left screen. This display contains a list of all applicable options
associated with QDUMP, their default values, and a short description of each (refer to
figures 18-14 through 18-16).
If the FM parameter is specified, indicating dumping of queued files from a specified
family of devices, the initial QDUMP left screen K display is replaced by the secondary
QDUMP K display (refer to figure 18-17). This display closely resembles the initial
QDUMP display but restricts QDUMP processing to the family of devices specified.
Each device in the specified family containing inactive queued files is indicated. In
addition, any parameter entered for the QDUMP utility is reflected in this display.
Parameters not entered remain at default values. Only the first screen of the secondary
QDUMP K display is shown, since the second and third screens have the same format
as the corresponding screens of the initial QDUMP K display.
After QDUMP processing has been completed and K-display interaction has been
terminated by
K.STOP.

a QDUMP output file is generated, indicating all files dumped. Figure 18-18 is an
example of this output.

Revision

Q u e u e d / D a y fi l e

Utilities

18-37

QDUMP

jsn

QDUMP.

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
QDUMP

PAGE 1 OF 3

INACTIVE QUEUES RESIDE ON FOLLOWING FAMILIES.
SYST06 PACKV2 FEATURE
(ERRORED FILE DUMPING SET)
OPTION
MI = 06
FM = ALL
DN = ALL
DA = 85/01/11
85/01/16

DESCRIPTION
MACHINE ID (1-2 CHARACTERS, »ALL*).
FAMILY FOR DEVICES (1-7 CHARACTERS)
DEVICE NUMBER (0-77B, *ALL*).
DUMP DATE RANGE (YYMMDD, *ALL*).

•*"*—«fcE~ Tp«gCC!IV[! OUIHtfF-f'
FN'* QFILES DUMP/TILE NAME (1-7 CHARACTER
NF = OD NUIBER OF MEDIA FILES TO SKIP.
TP~'-AM_ TYPrMA^AeT-iVE^ I=INACTIVEr-*ALL-*} r

Figure 18-14. Initial QDUMP K Display (Left Screen) (Page 1 of 3)
QDUMP

PAGE 2 OF 3

OPTION
FU =
UI »

ALL
OB
377777B

TF = ALL
TUI = OB
377777B
FS = OB
777777B
ID = OB
67B
FC = ALL
LA = LVL2
UA = LVL6
LD = M42

DESCRIPTION
FAMILY FOR USER INDEX (1-7 CHARACTERS).
USER INDEX RANGE (0-377777B).
FAMILY FOR TERMINAL (1-7 CHARACTERS).
DESTINATION TERMINAL UI RANGE (0-377777B).
FILE SIZE RANGE IN PRU-S (0-777777B).
ID RANGE OF FILES TO PROCESS (0-67B).
FORMS CODE (2 CHARACTERS OR ••).
LOWER SECURITY ACCESS LEVEL (1-7 CHARACTERS).
UPPER SECURITY ACCESS LEVEL (1-7 CHARACTERS).
DESTINATION LID (3 CHARACTERS).

Figure 18-15. Initial QDUMP K Display (Left Screen) (Page 2 of 3)

/•"Sgv

18-38 NOS Version 2 Analysis Handbook

Revision M

QDUMP

PAGE 3 OF 3

OPTION
BC = (DT)
RB = (DT)

DESCRIPTION
DISPOSITION TYPE FOR LOCAL BATCH DEVICES.
DISPOSITION TYPE FOR REMOTE BATCH DEVICES.
S I P P P P L L L L L W
F N U L R 2 R S T X Y T
BC
**•*-------*
pg
••-*««_*»*•*
• = OPTION SELECTED.
OPTION WILL BE CLEARED IF PREVIOUSLY SELECTED.

JSN = AAAA
AAAB

JOB SEQUENCE NAME (1-4 CHARACTERS).
JSN WILL BE CLEARED IF PREVIOUSLY ENTERED.

Figure 18-16. Initial QDUMP K Display (Left Screen) (Page 3 of 3)
K. QDUMP.

jsn

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
PAGE 1 OF 3

QDUMP

INACTIVE QUEUES RESIDE ON FOLLOWING DEVICES IN FAMILY - FEATURE

40
(ERRORED FILE DUMPING SET)
OPTION

DESCRIPTION

MI = 06
FM = ALL
DN = 40B
DA = 85/01/11
85/01/16

MACHINE ID (1-2 CHARACTERS, *ALL*).
FAMILY FOR DEVICES (1-7 CHARACTERS).
DEVICE NUMBER (0-77B, *ALL*).
DUMP DATE RANGE (YYMMDD, *ALL»).

L = OUTPUT
FN = QFILES
NF = OD
TP = ALL

FILE TO RECEIVE OUTPUT (1-7 CHARACTERS).
DUMP FILE NAME (1-7 CHARACTERS).
NUMBER OF MEDIA FILES TO SKIP.
TYPE (A=ACTIVE, I=INACTIVE, *ALL*).

Figure 18-17. Secondary QDUMP K Display (Left Screen)

Revision M

Queued/Dayfile Utilities 18-39

QDUMP

QDUMP PROCESSOR.

NO.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.

yy/mm/dd. hh mm.ss. PAGE

*»* DUMPED QUEUE FILE DISPOSITION • **

JSNS MID FAMILY
AABAB
AABBB
AABDB
AABGT
AABJS
AABOB
AABCB
AABE2
AABFT
AABHR
AABIS
AABK2
AABLB
AABPB

64
64
64
64
64
64
64
64
64
64
64
64
64
64

SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64

DN DT DS DATE
2
2
2
2
2
2
3
3
3
3
3
3
3
3

PR
LS
LT
LT
PR
PR
PR
PR
PR
LT
LT
LT
PR
PR

BC
BC
BC
BC
BC
BC
RB
RB
RB
RB
BC
BC
BC
BC

83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.

LENGTH ACCESS
(PRUS) LEVEL DISPOSITION ERRORS

12
13
14
15
17
13
13
15

ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE

Figure 18-18. QDUMP Output File
QDUMP does not purge files upon completion. If you want to purge files, the following
sequence of commands is recommended.
Command

Description

QREC,OP=DI.

Dequeues the files.

QDUMP,TP = I.

Dumps the inactive files. The dump file (default name = QFILES)
should be preassigned before issuing this command.

QREC,OP=PI.

Purges the files.

S**€?2>s

18-40 NOS Version 2 Analysis Handbook

Revision M

QFTUST
jfms

QFTLIST
QFTLIST displays and/or lists routing and other information about active queued files.
Its operation is similar to that of QALTER, except file alteration or purging is not
allowed. When QFTLIST is selected at the system console, the QFTLIST K display
appears on the left screen. This display contains a list of all applicable parameters
associated with QFTLIST, their default values, and a short description of each (refer to
figures 18-8 through 18-10). The output generated by QFTLIST LIST and OUT
K-display commands (both printed and right screen K display) is similar or identical to
that produced by QALTER.
Example 1:
Use the QFTLIST utility to determine what actions are necessary to get queued files
processed by the RBF or BIO Subsystems. The following QFTLIST entry generates a
detailed list of queued files, from which forms code, id, and other destination routing
information can be determined. This information indicates what action must be taken
to have the files processed.
X.QFTLIST(PO=N,LO=F)

Example 2:
Use the QFTLIST utility to determine what queued files are routed to a particular
device. The following QFTLIST entry generates a list of all print files with forms code
of AA that are routed to a 580-20 (LT) printer. Input file selection is explicitly
disabled.
X.QFTLIST(PO=N,FC=AA,RB=IN,BC=NONE,BC=LT)

QLIST
QLIST lists inactive queued files, which may include all inactive queued files in the
system or a selected subset based on parameters specified when the utility is called.
The QLIST utility is not restricted to use from the system console. However, from the
system console, QLIST must be called directly with the following command. No
K-display interaction is available.
x.QLIST(opti=vali,opt2=val2, ■.-,optn=valn)

The applicable parameters associated with QLIST are the same as those used with the
QREC utility, except for the OP parameter. The OP parameter is not valid with
QLIST.
If all current inactive queued files are to be listed, no parameters need be specified. In
this case, the format of the QLIST call is:
X.QLIST.

The output generated by QLIST is the same as that produced by the LIST command
available under the QREC utility (refer to figure 18-31).

y^s

r
Revision

Q u e u e d / D a y fi l e

Utilities

18-41

QLOAD

QLOAD
QLOAD processes the dump files generated by QDUMP or other utilities using the
same format. QLOAD can selectively load the queued files from these dump files.
QLOAD can also list the contents of a dump file without loading any files.
For secured systems, the access level for each file selected to be loaded must be within
the file's origin type limits and the file must be assigned to an appropriate mass
storage device. If a selected file cannot be loaded, QLOAD issues a diagnostic message
and skips that file.
When QLOAD is selected at the system console, the QLOAD K display (3 pages)
appears on the left screen. This display contains a list of all applicable parameters
associated with QLOAD, their default values, and a short description of each (refer to
figures 18-19 through 18-21).
After QLOAD processing has been completed and K-display interaction has been
terminated by

A^msx

K.STOP.

a QLOAD output file is generated, indicating all queued files which were contained on
the dump file, and whether they were loaded or not. Figure 18-22 contains an example
of this output.
Example:
Use the QDUMP and QLOAD utilities to dump queued files from one machine and
load them onto another. The following commands dump all punch files from machine ^*ms
AA. The QREC utility is used to dequeue the files and then purge them, because '
QDUMP does not purge files.
QREC,PO=N,I=DIRCTVS,OP=DI.
REWIND,DIRCTVS.
LABEL,QFILES,VSN=QUEUE,MT.
QDUMP,PO=N,I=DIRCTVS,TP=I.
REWIND,DIRCTVS.
QREC,PO=N,OP=PI,I=DIRCTVS.

File DIRCTVS is the input directive file that contains the following directives.
BC=NONE,BC=PH.
RB=NONE,RB=PH.

The following commands load the files dumped by the previous QDUMP onto another
machine.
LABEL,QFILES,VSN=QUEUE,MT.
QLOAD,PO=N,MI=AA,OP=A,DF=ALL.

18-42

NOS

Version

Analysis

Handbook

Revision

QLOAD

QLOAD,

jsn

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
QLOAD

PAGE 1 OF 3
(ERRORED FILE DUMPING SET)

OPTION

DESCRIPTION

MI = 06
DF » ALL
DD = ALL
DA = 85/01/11
85/01/16

MACHINE ID (1-2 CHARACTERS, *ALL*).
DESTINATION FAMILY (1-7 CHARACTERS)
DESTINATION DEVICE (0-77B, *ALL*).
LOAD DATE RANGE (YYMMDD, *ALL»).

L = OUTPUT
FN = QFILES
NF = OD
SC = OD
OP = A

FILE TO RECEIVE OUTPUT (1-7 CHARACTERS)
LOAD FILE NAME (1-7 CHARACTERS).
NUMBER OF MEDIA FILES TO SKIP.
NUMBER OF QUEUED FILES TO SKIP.
LOAD OPTION (A=LOAD/ACTIVATE,
I=LOAD/INACTIVATE).

Figure 18-19. QLOAD K Display (Left Screen) (Page 1 of 3)

QLOAD

PAGE 2 OF 3

OPTION
FU =
UI =

ALL
OB
377777B

TF = ALL
TUI = OB
377777B
FS = OB
777777B
ID = OB
67B
FC = ALL
LA = LVL2
UA = LVL6
LD = M42

DESCRIPTION
FAMILY FOR USER INDEX (1-7 CHARACTERS).
USER INDEX RANGE (0-377777B).
FAMILY FOR TERMINAL (1-7 CHARACTERS).
DESTINATION TERMINAL UI RANGE (0-377777B).
FILE SIZE RANGE IN PRU-S (0-777777B).
ID RANGE OF FILES TO PROCESS (0-67B).
FORMS CODE (2 CHARACTERS OR •*).
LOWER SECURITY ACCESS LEVEL (1-7 CHARACTERS).
UPPER SECURITY ACCESS LEVEL (1-7 CHARACTERS).
DESTINATION LID (3 CHARACTERS).

Figure 18-20. QLOAD K Display (Left Screen) (Page 2 of 3)

ypOB?5ky

Revision M

Queued/Dayfile Utilities 18-43

QLOAD

PAGE 3 OF 3

QLOAD
OPTION

DESCRIPTION

BC = (DT)
RB = (DT)

DISPOSITION TYPE FOR LOCAL BATCH DEVICES.
DISPOSITION TYPE FOR REMOTE BATCH DEVICES.
S I P P P P L L L L L W
F N U L R 2 R S T X Y T
BC
****-------*
PQ
•*_«*•_*•***
* = OPTION SELECTED.
OPTION WILL BE CLEARED IF PREVIOUSLY SELECTED.

JSN = AAAA
AAAB

JOB SEQUENCE NAME (1-4 CHARACTERS).
JSN WILL BE CLEARED IF PREVIOUSLY ENTERED.

Figure 18-21. QLOAD K Display (Left Screen) (Page 3 of 3)
QLOAD/LDLIST PROCESSOR.

NO.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.

JSNS MID FAMILY
AABAB
AABBB
AABDB
AABGT
AABJS
AABOB
AABCB
AABE2
AABFT
AABHR
AABIS
AABK2
AABLB
AABPB

64
64
64
64
64
64
64
64
64
64
64
64
64
64

SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64
SYST64

PAGE 1 .
yy/mm/dd. hh mm.ss.
LENGTH ACCESS
D
N DT DS DATE
(PRUS) LEVEL DISPOSITION ERRORS

PR
LS
LT
LT
PR
PR
PR
PR
PR
LT
LT
LT
PR
PR

BC
BC
BC
BC
BC
BC
RB
RB
RB
RB
BC
BC
BC
BC

83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.
83/07/07.

12
13
14
15
17
13
13
15

ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE

Figure 18-22. QLOAD Output File

-^^S\

18-44 NOS Version 2 Analysis Handbook

Revision M

QMOVE

QMOVE
f QMOVE moves queued files from one disk device to another. It also produces a listing
of all files moved with information about each file processed.
For secured systems, the destination device for each file selected to be moved must
have access level limits that are appropriate to accept the file. If the file is being
reactivated as well as moved, its access level must be within the file's origin type
limits. If a selected file cannot be moved, QMOVE issues a diagnostic message and
skips that file.
When QMOVE is selected at the system console, the initial QMOVE K display
(3 pages) appears on the left screen. This display contains a list of all applicable
parameters associated with QMOVE, their default values, and a short description of
each (refer to figures 18-23 through 18-25).
If the FM parameter is specified, indicating the loading of queued files to a specified
family of devices, the initial QMOVE left screen K display is replaced by the secondary
/^ QMOVE K display (refer to figure 18-26). This display closely resembles the initial
QMOVE display but restricts QMOVE processing to the family of devices specified.
Each device in the specified family containing inactive queued files is indicated. In
addition, any parameter entered for the QMOVE utility is reflected in this display.
Parameters not entered remain at default values. Only the first screen of the secondary
QMOVE K display is shown, since the second and third screens have the same format
as the corresponding screens of the initial QMOVE K display.
After QMOVE processing has been completed and K-display interaction has been
terminated by
K.STOP.

a QMOVE output file is generated, indicating all files moved. Figure 18-27 contains an
example of this output.

Revision

Q u e u e d / D a y fi l e

Utilities

18-45

QMOVE

Example 1:
If there are inactive queued files residing on a removable device, you can activate
these files but must first move them to a nonremovable device. This example shows
how to use the QMOVE utility to move queued files from the removable device with
family name SYSTEM and device number 45 to the nonremovable device with family
name FAM1 and device number 5. The following entries are made from DSD.
X.QFSP.

K . j s n . j s n i s t h e j o b s e q u e n c e n a m e o f Q F S P.
K.QMOVE.
K.FM=SYSTEM,DN=45.
K.DF=FAM1,DD=5.

K-OP=A.
K.GO,STOP.

The

moved

fi l e s

are

active.

Example 2:
This example exhibits the relationships among the ID, TF/TUI, and FC parameters. "^
(Refer to the descriptions of these parameters for the types of files affected by them.)
The following command moves all local batch-destined output files with ID=6 and all
remote batch-destined output files to device 3 in family SYS. The BC and RB
parameters explicitly disable input file processing.
QMOVE,PO=N,DF=SYS,DD=3,ID=6,BC=IN,RB=IN.

The following command performs the same function as the previous command except
that no remote batch files are moved.
QMOVE,PO=N,DF=SYS,DD=3,ID=6,BC=IN,RB=NONE.

18-46

NOS

Version

Analysis

Handbook

Revision

QMOVE

K. QMOVE.

jsn

hh.mm.ss. yy/mm/dd. CDC NETWORK OPERATING SYSTEM
MID=AA NOS version
PAGE 1 OF 3

QMOVE

INACTIVE QUEUES RESIDE ON FOLLOWING FAMILIES.
SYST06
PACKV2 FEATURE
(ERRORED FILE MOVING NOT SET)
OPTION

r
J^N

DESCRIPTION

MI = 06
FM = ALL
DN = ALL
DF = FEATURE
DD = 40B

MACHINE ID (1-2 CHARACTERS, *ALL*).
FAMILY FOR DEVICES (1-7 CHARACTERS).
DEVICE NUMBER (0-77B, *ALL*).
DESTINATION FAMILY (1-7 CHARACTERS).
DESTINATION DEVICE (0-77B).

DA =85/01/11
85/01/16
L = OUTPUT
TP = ALL
OP = A

DATE RANGE (YYMMDD, *ALL*).
FILE TO RECEIVE OUTPUT (1-7 CHARACTERS).
TYPE (A=ACTIVE, I=INACTIVE, *ALL*).
OPTION (A=LEAVE ACTIVE, I=LEAVE INACTIVE).

Figure 18-23. Initial QMOVE K Display (Left Screen) (Page 1 of 3)
PAGE 2 OF 3

QMOVE
OPTION
FU =
UI =

ALL
OB
377777B

TF = ALL
TUI = OB
377777B
FS = OB
777777B
ID = OB
67B
FC = ALL
LA = LVL2
UA = LVL6
LD = M42

DESCRIPTION
FAMILY FOR USER INDEX (1-7 CHARACTERS).
USER INDEX RANGE (0-377777B).
FAMILY FOR TERMINAL (1-7 CHARACTERS).
DESTINATION TERMINAL UI RANGE (0-377777B).
FILE SIZE RANGE IN PRU-S (0-777777B).
ID RANGE OF FILES TO PROCESS (0-67B).
FORMS CODE (2 CHARACTERS OR *•).
LOWER SECURITY ACCESS LEVEL (1-7 CHARACTERS).
UPPER SECURITY ACCESS LEVEL (1-7 CHARACTERS).
DESTINATION LID (3 CHARACTERS).

Figure 18-24. Initial QMOVE K Display (Left Screen) (Page 2 of 3)

0§jm*\

Revision M

Queued/Dayfile Utilities 18-47

QMOVE
/
Source Exif Data:
File Type : PDF
File Type Extension : pdf
MIME Type : application/pdf
PDF Version : 1.3
Linearized : No
Page Count : 1000
Creator : ScanSnap Manager
Producer : Mac OS X 10.5.8 Quartz PDFContext
Create Date : 2009:10:23 06:33:29Z
Modify Date : 2009:10:23 06:33:29Z

EXIF Metadata provided by EXIF.tools

NOS_2_Analysis_Handbook_Ref_60459300M_Dec88_Part_1 NOS 2 Analysis Handbook Ref 60459300M Dec88 Part 1

NOS_2_Analysis_Handbook_Ref_60459300M_Dec88_Part_1 NOS_2_Analysis_Handbook_Ref_60459300M_Dec88_Part_1

Navigation menu

Versions of this User Manual:

Views

Navigation