NOS_2_Reference_Set_Vol_3_System_Commands_60459680H_Apr87 NOS 2 Reference Set Vol 3 System Commands 60459680H Apr87
User Manual: Pdf NOS_2_Reference_Set_Vol_3_System_Commands_60459680H_Apr87
Open the PDF directly: View PDF .
Page Count: 818 [warning: Documents this large are best viewed by clicking the View PDF Link!]
![](asset-1.png)
60459680
CONTRpL DATA
NOS VERSION 2
REFERENCE SET
Volume 3
SYSTEM COMMANDS
CDC® COMPUTER SYSTEMS:
CYBER 180
CYBER 170
CYBER 70
MODELS 71, 72, 73, 74
6000
![](asset-2.png)
REVISION RECORD
REVISION
(04-26-82)
B
(01-27-83)
(10-11-83)
(10-05-84)
(03-28-85)
(12-16-85)
(09-30-86)
H
(04-23-87)
Publication No.
60459680
DESCRIPTION
Manual released. This manual reflects NOS Version 2 at PSR level 562. This manual documents
parameter-prompting procedures and the following new commands: ALTER, CFO, DELETE, Detach, DMB,
DROP, DUP, GO, LIBTASK, MOVE, PAUSE, QGET, READ, SC0PY, SETFS, SETJ0B, UPR0C, WHATJSN, WRITE, WRITEN.
This manual reflects NOS 2.1 at PSR level 580. This revision Incorporates the MFLINK, MFQUEUE,
SHELL, and new terminal definition commands; menu-generating procedures and new procedure
directives; support of 885-42 disk drives; as well as numerous usability changes. Because of
extensive changes to this manual, change bars and dots are not used. This manual obsoletes all
previous editions.
Th i s m an u a l re fl e c t s N O S 2 . 2 a t P S R l ev e l 596 . T h i s re v i s i o n i n c o r p or a t e s t h e f ol l o w i n g f e a tu r e s :
enhanced system security; service class assignment by users; a multihost network; full screen
editing; screen mode input for procedures and other applications; an expansion of online help,
including online manuals; equipment status table expansion; project prologues and epilogues; SCOPE 2
station; and the Interactive Transfer Facility (ITF). Because of extensive changes to this manual,
change bars and dots are not used. This revision obsoletes all previous editions.
Th i s ma n u a l r e fl e ct s N OS 2 .3 a t P S R l e ve l 61 7 . T h i s r e vi s i o n i n co r p o ra t e s t h e f o l l o wi n g f e a t u r es :
834 disk subsystem support; 639 magnetic tape unit support; PSU printer support; FSE enhancements;
NOS procedure enhancements, and the following new system commands: BLOCK, EFFECT, ERRMSG, LISTLID,
RECLAIM, REDO, SHOW, and TDU. This manual obsoletes all previous editions.
This manual reflects NOS 2.4.1 at PSR level 630. This revision documents the KEY command and the
following new features: support of CYBER 180 Models 840, 850, and 860; 895 disk subsystem support;
5870 Non-Impact Printer support; NOS/VE dual-state support; and NOS procedure enhancements.
This manual reflects NOS 2.4.3 at PSR level 647. This revision documents the APPSW command, the RC
terminal definition command, and the following features: support of CYBER 180 model 990; support of
836 disk subsystem; enhancements to 533/536 printer support; support of CDCNET version 1; disk error
recovery enhancements (ENQUIRE output); AUTO command internal 0003 byte processing.
This manual reflects NOS 2.5.1 at PSR level 664. This revision documents the XMODEM and DROPDS
command and the following features: support of print train Images, security enhancements, and
miscellaneous technical corrections.
This manual reflects NOS 2.5.2 at PSR level 678. This revision documents support for the Televideo
terminal and the 585 printer, new user messages related to enhancements to tape error recovery,
changes to several procedure directives, and the addition of the .SET directive and the STR, STRB,
and STRD functions.
REVISION LETTERS I. O, Q, S, X AND Z ARE NOT USED.
Address comments concerning this
manual to:
© 1982, 1983, 1984, 1985, 1986, 1987
by Control Data Corporation
All rights reserved
Printed in the United States of America
Control Data Corporation
Technology and Publications Division
4201 North Lexington Avenue
Saint Paul, MN 55126-6198
or use Comment Sheet in the back of
this manual.
![](asset-3.png)
LIST OF EFFECTIVE PAGES
New features, as well as changes, deletions, and additions to information in this manual, are indicated by bars in the margins or by a dot
near the page number if the entire page is affected. A bar by the page number indicates pagination rather than content has changed.
PAGE REV
Front Cover
Inside Front
Cover
Title Page
2
3H-
4 H
5/6 H-
7 H
8 H
9 H
10
11
12 H-
13
14
15 H.
16 H-
17
18 H-
19 E-
20 H-
21 G'
22 H-
1-1
1-2
1-3 H-
1-4 H-
1-5
1-6
2-1
2-2
2-3
2-4
2-5
2-6
2-7
2-8
2-9
2-10
2-11
2-12
2-13
2-14
2-15
2-16
2-17
3-1
3-2
3-3
3-4
3-5
3-6
3-6.1
3-6.2
3-7
3-8
3-9
PAGE
3-10
3-11
3-12
3-13
3-14
3-15
3-16
3-17
3-18
3-19
4-1
4-2
4-3
4-4
4-5
4-6
4-7
4-8
4-9
4-10
4-11
4-12
4-13
4-14
4-15
4 - 1 6
4-17
4-18
4-19
4-20
4-21
4-22
4-22.1
4-22.2
4-23
4-24
4-24.1/4-24.2
4-25
4 - 2 6
4 - 2 7
4 - 2 8
4-29
4-30
4-31
4-32
4-33
4-34
4-34.1
4-34.2
4-35
4 - 3 6
4 - 3 7
4 - 3 8
4-39
4-40
4-40.1/4-40.2
4-41
4-42
REV PAGE
4-43
4-44
4-45
4-46
4-47
4-48
4-49
4-50
4-51
4-52
4-53
4-54
5-1
5-2
5-3
5-4
5-5
5-6
5-7
6-1
6-2
6-3
6-4
6-5
6-6
6-7
6-8
6-8.1/6-8.2
6-9
6-10
6-10.1
6-10.2
6-11
6-12
6-13
6 - 1 4
6-15
6-16
6-16.1
6-16.2
6-16.3
6-16.4
6-17
6-18
6-19
6-20
6-21
6-22
6-23
6-24
6-25
6-26
6-27
6-28
6-29
6-30
6-31
7-1
REV
G
H
H
D
E
H
D
D
E
H
D
H
D
E
E
E
E
C
E
D
H
H
H
H
H
H
H
H
H
G
G
G
G
H
H
E
H
H
H
H
H
H
H
D
E
H
F
D
D
D
H
D
D
D
H
D
D
H
PA G E
7-2
7-3
7-4
7-5
7-6
7-7
7-8
7-9
7-10
7-11
7-12
7-12.1/7-12.2
7-13
7-14
7-15
7-16
7-16.1/7-16.2
7-17
7 - 1 8
7-19
7-20
7-21
7-22
7-22.1/7-22.2
7-23
7-24
7-25
7-26
7-27
7-28
7-29
7-30
7-31
7-32
7-33
7-34
7-35
7-36
7-37
7-38
7-39
7-40
7-41
7-42
7-43
7-44
7-45
7 - 4 6
7 - 4 7
7 - 4 8
7 - 4 9
7 - 5 0
7-51
7-52
7-53
7-54
7-55
7-56
REV
H
H
H
H
D
D
D
H
D
E
E
E
D
D
G
D
H
H
D
D
D
D
E
E
F
E
H
D
D
D
D
D
G
D
D
D
F
E
D
D
D
D
D
D
D
E
E
D
D
D
D
F
F
D
D
D
D
D
PAGE
7-57
7-58
7-59
7-60
7-61
7-62
7-63
7-64
7-65
7-66
7-67
7-68
REV
7-69
7-70
7-71
7-72
7-73
7-74
7-75
7-76
8-1
8-2
8-3
8-4
8-5
8-6
8-6.1
8-6.2
8-7
8-8
8-8.1/8-8.2
8-9
8-10
8-11
8-12
8-13
8-14
8-15
8-16
8-17
8-18
8-19
8-20
8-20.1/8-20.2
8-21
8-22
8-23
8-24
8-25
8-26
8-27
8-28
8-29
8-30
8-31
8-32
8-33
8-34
60459680 H
![](asset-4.png)
PAGE REV
8-35
8-36
8 - 3 7
8-38
8 - 3 9
8-40
8-41
8-42
8-43
8-44
8 - 4 5
8-46
8 - 4 7
8 - 4 8
8 - 4 9
8 - 5 0
8-51
8 - 5 2
9 - 1
9 - 2
9 - 3
9 - 4
9 - 5
9 - 6
9 - 7
9 - 8
9-9
9-10
9 - 11
9 - 1 2
9 - 1 3
9 - 1 4
9 - 1 5
9 - 1 6
9 - 1 7
9-18
9-19
9-20
9-21
9-22
9 - 2 3
9 - 2 4
9 - 2 5
9 - 2 6
9 - 2 7
9-28
9-29
9-30
9-31
9 - 3 2
9 - 3 3
9 - 3 4
9-35
9-36
9-37
9-38
9-39
9-40
9-41
9-42
9-43
9-44
9 - 4 5
9-46
9-47 F.
9-48
9-48.1
9-48.2
9 - 4 9
9-50
9 - 5 1
PAGE REV
9 - 5 2
9 - 5 3
9 - 5 4
9 - 5 5
9 - 5 6
9 - 5 7
9 - 5 8
9 - 5 9 D.
9 - 6 0 H.
9 - 6 1
9 - 6 2
9 - 6 3
9 - 6 4
9 - 6 5
9 - 6 6
9-67
9 - 6 8
10-1
1 0 - 2
1 0 - 3
10-4
10-4.1/10-4.2 H-
10-5
10-6
10-7
10-8
10-8.1/10-8.2
10-9
10-10
10-11
10-12
10-13
10-14
10-15
10-16
10-17
10-18
10-19
10-20
10-21
10-22
10-22.1/
10-22.2
10-23
10-24
10-25 H-
10-26 H-
10-27
10-28
10-29
10-30
10-31
10-32
10-33 D.
10-34 H'
10-35 H-
10-36
10-37
10-38
10-38.1
10-38.2 H-
10-39
10-40
10-41 H-
10-42
10-43
10-44
10-44.1/
10-44.2 H •
10-45
10-46
PAGE REV
10-47
10-48
10-49
11-1
11 - 2
11 - 3
11 - 4
11 - 5
11 - 6
11-6.1/11-6.2
11 - 7
11 - 8
11 - 9
11-10
12-1
1 2 - 2
1 2 - 3
1 2 - 4
1 2 - 5
1 2 - 6
1 2 - 7
1 2 - 8
1 2 - 9
12-10
12-10.1/
12-10.2
12-11
12-12
12-13
12-14
12-15
12-16
12-16.1/
12-16.2
12-17
12-18
12-19
12-20
12-21 H-
12-22
12-23
12-24
12-25
12-26
13-1
1 3 - 2
13-3
13-4
14-1
14-2
14-3
14-4
14-5
14-6
14-7
14-8
1 4 - 9
14-10
14-11
14-12
14-13
14-14
14-15
14-16
14-17
14-18
14-19
1 5 - 1
15-2
1 5 - 3
1 5 - 4
PAGE REV
1 5 - 5
1 5 - 6
15-7
1 5 - 8
15-9
15-10
15-11
15-12
15-13
15-14
15-15
15-16
15-17
15-18
15-19
15-20
15-20.1/
15-20.2
15-21
15-22
15-23
15-24
15-25
15-26
15-27
15-28
15-29
15-30
15-31
15-32
15-33
15-34
15-35
15-36
15-37
15-38
15-39
15-40
15-41
15-42
15-43
15-44
15-45
1 6 - 1
1 6 - 2
16-3
1 6 - 4
16-5
1 6 - 6
1 6 - 7
1 6 - 8
1 6 - 9
A-l
A - 2
A - 3
A - 4
A - 5
A - 6
A - 7
A - 8
A - 9
A-10
A-ll
A- 12
A-13
A- 14
A- 15
B-l
B - 2
B - 3
B - 4
PAGE REV
B-5
B - 6
B - 7
B - 8
B - 9
B- 10
B-ll
B- 12
B- 13
B- 14
B- 15
B- 16
B- 17
B- 18
B- 19
B- 20
B- 21
B- 22
B- 23
B- 24
B- 25
B- 26
B- 27
B- 28
B- 29
B- 30
B-31
B- 32
B-33
B-34
B- 35
B-36
B- 37
B-38
B- 39
B-40
B- 41
B- 42
B- 43
B- 44
B- 45
B- 46
B- 47
B- 48
B- 49
B- 50
B- 51
B- 52
B-5 3
B- 54
B- 55
B- 56
B-57
B-58
B-5 9
B-60
B- 61
B-62
B-63
B-64
B-65
B-66
B- 67
B- 68
B- 69
B- 70
B- 71
B-7 2
B- 73
B-7 4
B- 75
.^T^osX
-■^^^v
60459680 H
![](asset-5.png)
PAGE REV
B-76
C-l
C-2
C-3
C-4
C-5
C-6
C-7
C-8
C-9
C-10
C-ll
C-12
C-13
C-14
C-15
D-l
D-2
D-3
D-4
E-l
E-2
F-l
F-2
F-3
F-4
F-5
F-6
F-7
G-l
G-2
G-3
G-4
G-5
G-6
G-7
G-8
G-9
G-10
G-ll
H-l
H-2
H-3
H-4
H-4.1
H-4.2
H-5
H-6
H-7
H-8
H-9
1-1
1-2
1-3
1-4
J-l
J-2
J-3
J-4
J-5
J-6
J-7
J-8
J-9
J-10
J-ll
J-12
J-13
J-14
J-15
J-16
PAGE REV
J-17
J-18
J-19
J-20
J-21
J-22
J-23 H-
J-24
J-25 H-
J-26
J-27 H-
J-28
J-29
J-30
K-l
K-2
L-l
L-2
L-3
L-4
L-5
L-6
L-7
L-8
L-9
M-l
M-2
M-3
M-4
M-5
M-6
M-7
M-8
M-9
N-l H-
N-2
0-1
0-2 H-
0-3
P-l
P-2
P-3
P-4
P-5
P-6
P-7
P-8
Index-1
Index-2
Index-3
Index-4
Index-5
Index-6
Index-7
Index-8
Index-9
Index-10
Index-11
Index-12
Index-13
Index-14
Index-15
Index-16
Comment Sheet
Inside Back
Cover
Back Cover
PAGE REV PAGE REV PAGE
J$$0&\
60459680 H 5/6
![](asset-6.png)
/^%
![](asset-7.png)
PREFACE
^^s
4$$$!\
This manual describes the Network Operating System (NOS) Version 2. NOS can operate on the
following computer systems:
CDC CYBER 180 Computer Systems
Models 810, 830, 835, 840, 845, 850, 855, 860, 870, 990, 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
6000 Computer Systems
AUDIENCE
Volume 1, Introduction to Interactive Usage (60459660), is written for the novice.
Volume 2, Guide to System Usage (60459670), is written for the applications or systems
programmer who is unfamiliar with NOS.
Volume 3, System Commands (60459680), is written for all NOS users.
Volume 4, Program Interface (60459690), is written for the experienced COMPASS applications
programmer or systems programmer.
The reader of each volume should have a knowledge of the material contained in the previous
volumes.
ORGANIZATION
The NOS reference set describes the external features of NOS 2. This reference set
comprises four separate volumes.
Volume 1, Introduction to Interactive Usage, shows a user at an interactive terminal how to
enter, run, and correct programs, and how to create, retrieve, and maintain permanent
files. Other topics covered include physical terminal connection, and login/logout
procedures.
Volume 2, Guide to System Usage, describes the general concepts of NOS and some of the
utilities used with NOS. Topics included are job processing, file concepts, procedures,
magnetic tape processing, Modify, and file loading. This volume is a learning tool and does
not contain comprehensive descriptions of all NOS commands.
Volume 3, System Commands, describes the system commands that form the user interface to NOS,
60459680 H
![](asset-8.png)
Volume 4, Program Interface, describes the COMPASS program interface to NOS. Detailed
descriptions of function processors and macros available to COMPASS user programs are
included.
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 Corporation
Publications and Graphics Division ARH219
4201 Lexington Avenue North ^^
St. Paul, MN 55112 "^
Additionally, if you have access to SOLVER, an online facility for reporting problems, you
can use it to submit comments about the manual. Declare your problem type as DOC and use
NS2 as the product identifier.
IN CASE OF TROUBLE
Control Data's Central Software > ipport 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 us at one of the following numbers
and a support analyst will work with you.
From USA and Canada: (800) 345-9903
Fro m ot her c ou n tr ie s: (61 2) 8 51- 41 31
The preceding numbers are for help on product usage. Address questions about physical
packaging and/or distribution of printed materials to Literature and Distribution Services
at the following address:
Control Data Corporation
Literature and Distribution Services
308 North Dale Street
St. Paul, Minnesota 55103
or you can call (612) 292-2101. If you are a Control Data employee, call (612) 292-2100.
CONVENTIONS
REFERENCES TO OTHER MANUALS IN THE NOS REFERENCE SET
Throughout this manual, references to Volumes 1, 2, and 4 of the NOS Reference Set are in
the form: refer to section n, (volume name). If a volume number is not specified, the
reference is to Volume 3.
60459680 H
![](asset-9.png)
/pifev
/p*V
180-CLASS MAINFRAMES
Some of the CYBER 170 Computer Systems share many of the functional and architectural
attributes of the CYBER 180 Computer Systems. Specifically, CYBER 170 Models 815, 825, 835
845, and 855 fall into this category. It is sometimes convenient to refer to the'cYBER 180'
models and these CYBER 170 models collectively. This manual uses the term 180-class
mainframes to refer to this collection.
EXTENDED MEMORY
Extended memory for model 176 is large central memory extended (LCME). Extended memory for
the 180-class mainframes and the models 865 and 875 is unified extended memory (UEM) and may
also include extended core storage (ECS) or extended semiconductor memory (ESM). Extended
memory for all other NOS computer systems is either ECS or ESM. ECS and ESM are the only
forms of extended memory that can be shared in a linked shared device multimainframe complex
and can be accessed by a distributive data path (DDP).
In this manual, ECS refers to both ECS and ESM, and extended memory refers to all forms of
extended memory unless otherwise noted.
Programming information for the various forms of extended memory can be found in the COMPASS
Version 3 Reference Manual and in the appropriate computer system hardware reference manual.
60459680 H
![](asset-a.png)
CYBER 70 COMPUTER SYSTEMS REFERENCES
References to the CYBER 70 Computer Systems pertain only to models 71, 72, 73, and 74.
CONTROL STATEMENT
The manuals of many NOS products use the term control statement instead of the term command.
This manual uses the term command almost exclusively. You can consider the two synonymous.
EXAMPLES
The following conventions apply to examples that appear in this manual:
• Examples of actual terminal sessions that appear in this manual were produced on a
display terminal in NORMAL character mode unless otherwise specified. Uppercase
characters represent terminal output; lowercase characters represent user input
unless otherwise noted. (However, user input that is displayed within the text of
this manual is shown in uppercase characters). The vertical spacing in examples
does not necessarily coincide with the spacing that appears on your terminal.
• Program examples are written either in FORTRAN 5 or BASIC 3 (hereafter referred to
as just BASIC).
• This manual uses commas to delimit command parameters and periods to terminate y
commands. For clarity, however, commands that appear in text use an opening
parenthesis for their initial delimiter and a closing parenthesis for their
terminator.
COMMAND FORMAT
Interpret uppercase characters within command formats literally. Lowercase characters are
variables and are described immediately following the line that shows the command format.
SPECIAL KEYBOARD ENTRIES
This manual uses special notation to represent certain keyboard entries:
• @ denotes the message transmission key on the keyboard. Depending on the terminal
class, this key may be the RETURN, CR, CARRIAGE RETURN, NEW LINE, SEND, or ETX key.
For some terminal classes, the RETURN or NEW LINE key also denotes a message
terminator, but the message is kept in the terminal buffer until the corresponding
SEND or ETX key is pressed, sending all messages in the buffer to IAF. Appendix K
supplies more information. IAF and the network respond to the @) by positioning the
carriage to the firs t chara cter po sitio n on the ne xt l ine.
• ■•—designates the backspace character.
• The notation CTRL/x directs you to press the control key (which is labeled CTRL,
CNTL, CNTRL, or similar characters) on the terminal and, while holding this key
down, press the key specified by x. For example, CTRL/H means press and hold the
control key while you press the H key.
10 60459680 H
![](asset-b.png)
RELATED PUBLICATIONS
The following is a list of NOS operating system manuals and NOS product set reference
manuals.
You might also want to consult the NOS System Information manual. This is an online manual
that includes brief descriptions of all NOS operating system and NOS product set manuals.
You can access this manual by logging into NOS and entering the command EXPLAIN.
These manuals are available through Control Data sales offices or Control Data Literature
Distribution Services (308 North Dale, St. Paul, Minnesota 55103).
If you need a brief description of the product commands and their parameters, you should
refer to the NOS 2 Applications Programmer's Instant.
Control Data Publication
APEX IV Reference Manual
APL Version 2 Reference Manual
APT IV Version 2 Reference Manual
BASIC Version 3 Reference Manual
CDCNET Conceptual Overview
CDCNET Terminal Interface Usage Manual
COBOL Version 5 Reference Manual
Common Memory Manager Version 1 Reference Manual
COMPASS Version 3 Reference Manual
Conversion Aids System Version 2 Reference Manual
CYBER Database Control System 2 Database Administrator
Reference Manual
CYBER Database Control System Version 2 Application
Programming Reference Manual
CYBER Interactive Debug Version 1 Reference Manual
CYBER Loader Version 1 Reference Manual
Publication Number
84002550
60454000
17326900
19983900
60461540
60463850
60497100
60499200
60492600
19265358
60485200
60485300
60481400
60429800
60459680 H 11 I
![](asset-c.png)
Control Data Publication Publication Number
CYBER Record Manager Advanced Access Methods Version 2
Reference Manual
CYBER Record Manager Basic Access Methods Version 1.5
Reference Manual
CYBER 70 Model 71 Computer System Hardware Reference Manual
CYBER 70 Model 72 Computer System Hardware Reference Manual
CYBER 70 Model 73 Computer System Hardware Reference Manual
CYBER 70 Model 74 Computer System Hardware Reference Manual
CYBER 170 Computer Systems Models 171 through 175
(Levels A, B, C) Model 176 (Level A) Hardware Reference Manual
CYBER 170 Computer Systems Models 720, 730, 740, 750, and 760,
Model 176 (Level B/C) Hardware Reference Manual
CYBER 170 Computer System Model 825
Hardware Reference Manual
CYBER 170 Computer Systems Models 835, 845, and 855
Hardware Reference Manual
CYBER 170 Computer Systems Models 865 and 875
Hardware Reference Manual
Data Base Utilities Version 1 Reference Manual
Data Catalogue 2 Reference Manual
DDL Version 3 Reference Manual, Volume 1
DDL Version 3 Reference Manual, Volume 2
DDL Version 3 Reference Manual, Volume 3
FORM Version 1 Reference Manual
FORTRAN Common Library Mathematical Routines Reference Manual
FORTRAN Data Base Facility Version 1 Reference Manual
FORTRAN Extended Version 4 Reference Manual
FORTRAN Extended Version 4 to FORTRAN Version 5 Conversion
Aids Program Version 1 Reference Manual
FORTRAN Version 5 Common Library Mathematical Routines
Reference Manual
FORTRAN Version 5 Reference Manual
General Purpose Simulation System V (GPSS)
General Information Manual
60499300
60495700
60453300
60347000
60347200
60347400
60420000
60456100
60469350
60469290
60458920
60498800
60483200
60481900
60482000
60482100
60496200
60498200
60482200
60497800
60483000
60483100
60481300
84003900
I 12 60459680 H
![](asset-d.png)
Control Data Publication
Information Management Facility Version 1 Application
Programming Reference Manual
Message Control System Version 1 Reference Manual
Modify Version 1 Reference Manual
Network Access Method Version 1/Communications Control
Program Version 3 Terminal Interfaces Reference Manual
Network Access Method Version 1
Host Application Programming Reference Manual
Network Access Method Version 1 Network
Definition Language Reference Manual
NOS Full Screen Editor User's Guide
NOS Version 2 Administration Handbook
NOS Version 2 Application Installation Handbook
NOS Version 2 Applications Programmer's Instant
NOS Version 2 Diagnostic Index
NOS Version 2 Installation Handbook
NOS Version 2 Network Terminal User's Instant
NOS Version 2 Operator/Analyst Handbook
NOS Version 2 Reference Set, Volume 1,
Introduction to Interactive Usage
NOS Version 2 Reference Set, Volume 2, Guide to System Usage
NOS Version 2 Reference Set, Volume 4, Program Interface
NOS Version 2 Security Administrator's Handbook
NOS Version 2 System Maintenance Reference Manual
NOS Version 2 System Overview
NOS Version 2 Systems Programmer's Instant
NOS Version 2 Tape Management System (TMS) User Reference Manual
On-Line Maintenance Software Reference Manual
Pascal Version 1.1 Reference Manual
PERT/Time Version 2 Reference Manual
Query Update Version 3 Reference Manual
Publication Number
60484500
60480300
60450100
60480600
60499500
60480000
60460420
60459840
84002760
60459360
60459390
60459320
60459380
60459310
60459660
60459670
60459690
60460410
60459300
60459270
60459370
60463110
60454200
60497700
60456030
60498300
60459680 H 13
![](asset-e.png)
Control Data Publication
Remote Batch Facility Version 1 Reference Manual
Remote Host Facility Access Method Reference Manual
Remote Host Facility Usage
SORT/MERGE Version 5 Reference Manual
SYMPL Version 1 Reference Manual
TAF/CRM Data Manager Version 1 Reference Manual
TAF Version 1 Reference Manual
TAF Version 1 User's Guide
Text Editor Version 1 Reference Manual
TOTAL-CDC Version 2 Reference Manual
Update Version 1 Reference Manual
XEDIT Version 3 Reference Manual
5870 Printer User's Reference Manual
6000 Series Computer Systems Hardware Reference Manual
8-Bit Subroutines Reference Manual
Publication Number
60499600
60459990
60460620
60484800
60496400
60459510
60459500
60459520
60436100
76070300
60449900
60455730
60462720
60100000
60495500
DISCLAIMER
This product is intended for use only as
described in this document. Control Data
cannot be responsible for the proper
functioning of undescribed features or
undefined parameters.
I " 60459680 H
![](asset-f.png)
CONTENTS
/0$£\
0l^f\
1. SYSTEM DESCRIPTION
System Hardware
Central Processor Unit
Central Memory
Job Field Length
Central Memory Resident
Extended Memory
Peripheral Processors
Peripheral Equipment
System Software
User Programs
Operating System
CYBER Loader
CYBER Record Manager
2. FILES
1-1
1-1
1-2
1-2
1-2
1-3
1-3
1-4
1-4
1-5
1-5
1-5
1-6
1-6
2-1
File Names 2-1
File Structure 2-1
CYBER Record Manager File Structure 2-3
NOS File Structure 2-3
Physical File Structure 2-4
Card Files 2-6
Mass Storage Files 2-6
Magnetic Tape Files 2-7
File Types 2-11
Input Files 2-11
Queued Files 2-11
Local Files 2-12
Primary Files 2-13
Direct Access Files 2-13
Library Files 2-13
Permanent Files 2-13
Indirect Access Permanent Files 2-14
Direct Access Permanent Files 2-14
Mass Storage File Residence 2-15
Family Devices 2-15
Auxiliary Devices 2-16
Alternate Storage Subsystems 2-16
Libraries 2-17
User Name Library 2-17
Program Libraries 2-17
User Libraries 2-17
3. JOB FLOW AND EXECUTION 3-1
Job Initia ti on and Terminati on 3-1
Batch Jobs 3-1
Interactive Jobs 3-2
Login 3-2
Logout and Application
Switching Procedure 3-4
Submitting Jobs to Remote Hosts 3-6
Job Origin Types 3-6.2
Job Service Classes 3-6.2
Job Names 3-7
Job Sequence Name (JSN) 3-7
User Job Name (UJN) 3-8
Validation 3-8
Accounting 3-8
Job Scheduling 3-9
Job Control 3-9
Field Length Control 3-9
Input File Control 3-11
Time Limit Control 3-11
SRU Limit Control 3-11
Command Limit Control 3-11
Rollout Control 3-12
Error Control 3-12
Security Features 3-13
Memory Protection 3-13
System and File Access Controls 3-13
Security Access Levels 3-14
Security Access Catagories 3-16
Responsibilities for Data Security 3-16
Security Conflict Processing 3-17
Job Completion 3-17
4. PROCEDURES 4-1
Procedure File Residence and Search
Order 4-2
Procedure Structure 4-2
Procedure Processing 4-3
Interactive Parameter Entry 4-4
Procedure Expansion 4-4
.EXPAND Directive 4-6
Inhibit Character 4-6
Concatenation Character 4-8
.EX Directive 4-9
Execution of the Command Record 4-9
Procedure Directives 4-9
Procedure Header (.PROC) Directive 4-11
Interactive Format 4-11
Checklist Entries 4-13
Special Values 4-14
60459680 H 15 |
![](asset-10.png)
Checklist Patterns 4-16
Menu Format 4-22
Formatting and Help Directives 4-23
.CORRECT Directive 4-23
.ENDHELP Directive 4-24
.ENTER Directive 4-24
.Fn Directive 4-24.1
.HELP Directive 4-25
.NOCLR Directive 4-31
.NOTE Directive 4-31
.PAGE Directive 4-32
.PROMPT Directive 4-32
Expansion Control Directives 4-33
.CC Directive 4-33
.EXPAND Directive 4-33
.IC Directive 4-33
.SET Directive 4-34
File Directives 4-34.1
.DATA Directive 4-34.1
. E O F ( o r . E O P ) D i r e c t i v e 4 - 3 8
.EOR (or .EOS) Directive 4-38
Branching Directives 4-38
.ELSE Directive 4-38
.ENDIF Directive 4-39
.EX Directive 4-39
.IF (or .IFE) Directive 4-40
.COMMENT (.*) Directive 4-40.1
Calling a Procedure (BEGIN Command) 4-41
Requesting Help on Procedure Calls 4-46
Ending a Procedure (REVERT Command) 4-51
Parameter Matching Modes 4-53
Order-Dependent Mode 4-53
Order-Independent Mode 4-53
5. COMMAND PROCESSING 5-1
Command Format 5-2
Command Processing Flow 5-5
Exit Processing 5-7
6. FLOW CONTROL COMMANDS 6-1
Command Syntax 6-2
Operators 6-2
Arithmetic Operators 6-2
Relational Operators 6-3
Logical Operators 6-4
String Operators 6-4
Order of Evaluation 6-5
Operands 6-5
Constants 6-5
Numeric Strings 6-5
Literals 6-5
Symbolic Names 6-7
Functions 6-12
FILE Function 6-12
DT Function 6-14
LEN Function 6-16
NUM Function 6-16
STR Function 6-16.1
STRB Function 6-16.2
STRD Function 6-16.3
Command Descriptions 6-16.3
BEGIN Command 6-16.3
DISPLAY Command 6-16.4
ELSE Command 6-17
ENDIF Command 6-18
ENDW Command 6-19
EXIT Command 6-19
IF (or IFE) Command 6-20
MODE Command 6-22
NOEXIT Command 6-24
ONEXIT Command 6-24
REVERT Command 6-24
SET Command 6-25
SKIP Command 6-30
WHILE Command 6-31
7. JOB CONTROL COMMANDS 7-1
BLOCK Command 7-2
CFO Command 7-3
CHARGE Command 7-4
CHVAL Command 7-5
CLASS Command 7-7
COMMENT Command 7-9
CTIME Command 7-10
DAYFILE Command 7-10
DROP Command 7-12.1
ENQUIRE Command 7-13
ENTER Command 7-21
ERRMSG Command 7-22
GO Command 7-22
HTIME Command 7-22.1
Job Command 7-23
LDI Command 7-26
LENGTH Command 7-27
LIMITS Command 7-28
Resource Limits 7-29
Other Characteristics 7-30
User Permissions 7-31
Network Applications 7-32
Local Applications 7-32
Privileged Network Applications 7-32
Shell Permissions 7-32
Security Permissions 7-33
Security Access Categories 7-33
Security Access Levels 7-33
Service Classes 7-33
Default Service Classes 7-33
LISTLID 7-36
16 60459680 H
/*^^\
![](asset-11.png)
MACHINE Command 7-39
MFL Command 7-39
NORERUN Command 7-40
NOTE Command 7-40
OFFSW Command 7-41
ONSW Command 7-42
PASSWOR Command 7-42
PAUSE Command 7-44
PROTECT Command 7-44
QGET Command 7-45
QUEUE7 Command 7-46
RERUN Command 7-50
RESOURC Command 7-50
Deadlock Prevention 7-52
Single Resource Use 7-54
Tape Units 7-54
Resource Overcommitment 7-55
Altering Resource Requirements 7-56
Unit Assignment 7-57
RFL Command 7-57
ROLLOUT Command 7-58
RTIME Command 7-58
SETASL Command 7-59
SETCORE Command 7-60
SETJAL Command 7-61
SETJOB Command 7-62
SETJSL Command 7-63
SETPR Command 7-64
SETTL Command 7-64
SHELL Command 7-66
STIME Command 7-67
SUBMIT Command 7-68
SWITCH Command 7-73
UPROC Command 7-73
USECPU Command 7-74
USER Command 7-74
8. COMMANDS FOR INTERACTIVE JOBS 8-1
Terminal Control Commands 8-2
ASCII Command 8-2
AUTO Command 8-3
BRIEF Command 8-4
CSET Command 8-4
EFFECT Command 8-4
KEY Command 8-5
LINE Command 8-6.1
NORMAL Command 8-7
SCREEN Command 8-7
TDU Command 8-8.1
TIMEOUT Command 8-9
TRMDEF Command 8-9
Using TRMDEF with NAM/CDCNET 8-10
Examples 8-11
Subsystem Selection Commands 8-11
ACCESS Command 8-12
BASIC Command
BATCH Command
EXECUTE Command
FORTRAN Command
FTNTS Command
NULL Command
Interactive Status Commands
Detach Command (ctD)
Immediate Job Status
Command (ctE)
Abbreviated Job Status
Command (ctS)
Job Processing Commands
APPSW Command
BYE Command
DIAL Command
EXPLAIN Command
GOODBYE Command
HELLO Command
HELL07 Command
HELL07 Directives
HELP Command
HELPME Command
LIB Command
LIST Command
LOGIN Command
LOGOUT Command
NOSORT Command
RECOVER Command
REDO Command
RUN Command
Secure Login Command
SHOW Command
TEXT Command
WHATJSN Command
X Command
XMODEM Command
Primary File Editing Commands
Parameter Format
Suppressing Editing Responses
Line Number Overlap
Inserting Lines
ALTER Command
DELETE Command
DUP Command
LIST Command
MOVE Command
READ Command
RESEQ Command
WRITE Command
WRITEN Command
9. FILE MANAGEMENT COMMANDS
ASSIGN Command
BKSP Command
8-12
8-13
8-13
8-14
8-15
8-15
8-16
8-16
8-17
8-17
8-18
8-18
8-19
8-20.1
8-20.1
8-21
8-21
8-22
8-22
8-26
8-26
8-26
8-28
8-28
8-29
8-29
8-30
8-34
8-35
8-36
8-36
8-37
8-37
8-38
8-38
8-39
8-40
8-41
8-41
8-42
8-42
8-44
8-45
8-46
8-48
8-49
8-51
8-51
8-52
9-1
9-2
9-4
60459680 H 17
![](asset-12.png)
CLEAR Command
COPY Command
Copy Termination
Block Sizes
Processing Options
COPYBF Command
COPYBR Command
COPYCF Command
COPYCR Command
COPYEI Command
COPYSBF Command
COPYX Command
DOCMENT Command
EVICT Command
FCOPY Command
LIST80 Command
LOCK Command
L072 Command
MFQUEUE Command
Parameter Descriptions
The Routing Directive
NEW Command
OUT Command
OVWRITE Command
PACK Command
PRIMARY Command
RENAME Command
REQUEST Command
RESEQ Command
RETURN Command
REWIND Command
ROUTE Command
Parameter Descriptions
Implicit Routing
SCOPY Command
SECHDR Command
SETFAL Command
SETFS Command
SKIPEI Command
SKIPF Command
SKIPFB Command
SKIPR Command
SORT Command
TCOPY Command
TDUMP Command
UNLOAD Command
UNLOCK Command
VERIFY Command
WRITEF Command
WRITER Command
9-5 DEFINE Command 10-17
9-5 GET Command 10-20
9-10 DROPDS Command 10-21
9-10 MFLINK Command 10-22
9-10 MFLINK Directives 10-23
9-11 APPEND Directive 10-24
9-12 ATTACH Directive 10-24
9-13 CHANGE Directive 10-24
9-15 CHARGE Directive 10-25
9-16 DEFINE Directive 10-25
9-17 DROPDS Directive 10-25
9-18 GET Directive 10-25
9-20 PACKNAM Directive 10-25
9-22 PERMIT Directive 10-26
9-23 PURGE Directive 10-26
9-26 REPLACE Directive 10-26
9-26 SAVE Directive 10-26
9-27 USER Directive 10-26
9-31 Interactive Use of MFLINK 10-27
9-31 OLD Command 10-28
9-33 PACKNAM Command 10-29
9-34 PERMIT Command 10-30
9-35 PURGALL Command 10-31
9-35 PURGE Command 10-32
9-36 RECLAIM Command 10-33
9-37 Magnetic Tapes 10-34
9-37 Command Format 10-35
9-38 RECLAIM Output 10-44
9-40 REPLACE Command 10-45
9-42 SAVE Command 10-46
9-43 SETPFAC Command 10-48
9-44 SETPFAL Command 10-49
9-44
9-50
9-51
9-54 11. LOAD/DUMP MEMORY COMMANDS 11-1
9-55
9-56 DMB Command 11-1
9-56 DMD Command 11-5
9-57 DMDECS Command 11-6
9-57 DMP Command 11-6.1
9-58 DMPECS Command 11-7
9-58 LBC Command 11-8
9-59 LOC Command 11-8
9-62 PBC Command 11-9
9-64 RBR Command 11-9
9-65 WBR Command 11-10
9-65
9-68
9-68 12. TAPE MANAGEMENT 12-1
10. PERMANENT FILE COMMANDS
Common Parameters
APPEND Command
ATTACH Command
CATLIST Command
CHANGE Command
COMMON Command
18
Tape Assignment
10-1 Command Rules
Processing Options
10-2 ASSIGN Command
10-7 BLANK Command
10 -7 LAB EL C omm and
10-10 LISTLB Command
10-15 REQUEST Command
10-16 VSN Command
12-1
12-2
12-3
12-5
12-9
12-11
12-19
12-21
12-25
60459680 H
![](asset-13.png)
13. CHECKPOINT/RESTART 13-1
CKP Command 13-1
RESTART Command 13-2
14. SYSTEM UTILITY COMMANDS 14-1
EDIT Command 14-1
FSE Command 14-2
KRONREF Command 14-4
MODIFY Command 14-5
OPLEDIT Command 14-8
PDU Command 14-10
PROFILE Command 14-11
UPDATE Command 14-14
XEDIT Command 14-18
15. LIBRARY MAINTENANCE 15-1
Library File Access Methods 15-1
Library Record Types 15-2
CATALOG Command 15-5
C O P Y L a n d C O P Y L M C o m m a n d s 1 5 - 7
GTR Command 15-11
ITEMIZE Command 15-14
LIBEDIT Command 15-17
Command Format 15-18
LIBEDIT Directives 15-20
ADD Directive 15-23
BEFORE Directive 15-24
BUILD Directive 15-24
COMMENT Directive 15-25
COPY Directive 15-25
DATE Directive 15-25
DELETE Directive 15-26
FILE Directive 15-26
IGNORE Directive 15-27
INSERT or AFTER Directive 15-27
LIBGEN Directive 15-28
LIST Directive 15-28
NEW Directive 15-28
NOINS Directive 15-28
NOREP Directive 15-29
NOREW Directive 15-29
OLD Directive 15-29
RENAME Directive 15-29
REPLACE Directive 15-30
REWIND Directive 15-30
TYPE or NAME Directive 15-31
VFYLIB Directive 15-31
LIBEDIT Output 15-31
LIBGEN Command 15-32
ULIB Command 15-34
VFYLIB Command 15-35
Library Processing Examples 15-37
LIBRARY Command 15-43
Maximum Size of Global Library
Set 15-43
Library Search Order 15-44
Examples 15-44
1 6 . T E R M I N A L I N P U T / O U T P U T 1 6 - 1
Terminals 16-1
Input/Output Conventions 16-2
Input From Terminal 16-2
Length of Output/Input Lines 16-3
Terminating Input Line 16-3
Correcting Input Line 16-3
Deleting Input Line 16-4
E n t e r i n g I n p u t B e f o r e P r o m p t s 1 6 - 4
Page Wait 16-5
Suspending Output 16-5
Aborting Output Block 16-5
Interrupting Job Step 16-6
Terminating Job Step 16-6
Continuing a Suspended Job 16-7
Using ATTN on IBM 2741 Terminals 16-8
Control Bytes 16-9
APPENDIXES
A. CHARACTER SETS
Character Set Anomalies
Character Set Tables
Interactive Jobs
Batch Jobs
Jobs Using Line Printers
Jobs Using Magnetic Tape:
A-l
A-2
A-2
A-3
A-3
A-3
A-l 2
D. SAMPLE JOB OUTPUT
TERMINAL CHARACTER CONVERSION
Data Input
Data Output
D-l
E-l
E-l
E-2
B. DIAGNOSTIC MESSAGES
C. GLOSSARY
B-l
C-l
F. CARD FILE DATA CONVERSION
Input Card File Formats
Coded Cards
Conversion Modes
F-l
F-2
F-3
F-3
60459680 E 19
![](asset-14.png)
/^s^\
Literal Input F-3 (AR)
Binary Cards F-5 Re
Summary F-5 (BF)
Punch File Formats F-5 (BR)
Coded Cards (Punch) F-6 (BS)
Binary Cards (Punch B) F-6 (Bl)
Absolute Binary Cards (P8) F-7
(AR) - Automatic Character
Recognition
(BF) - Blocking Factor
G . A N S I T A P E L A B E L F O R M A T S G - l
Required Labels G-l
VOL 1 - Volume Header Label G-2
HDR1 - First File Header Label G-4
E0F1 - First End-Of-File Label G-8
E0V1 - First End-Of-Volume Label G-9
Optional Labels G-10
HDR2 through HDR9 - Additional
File Header Labels G-10
E0F2 through E0F9 - Additional
End-Of-File Labels G-10
E0V2 through E0V9 - Additional
End-Of-Volume Labels G-10
User Labels G-ll
H. LINE PRINTER CARRIAGE CONTROL H-l
Printed Data H-l
Paper Length H-l
580 Line Printers H-l
| 533/536 and 585 Printers H-2
Carriage Control H-2
Format Channel Selection on
I Non-PFC Printers H-4.2
Format Channel Selection on
| 533/536 Printers H-4.2
Carriage Control Arrays H-7
Array Syntax H-7
I Reserved Format Channels H-9
Example H-9
I. OBSOLETE TAPE FORMATS 1-1
B (Blocked) Format 1-1
E (Line Image) Format 1-2
X (External) Format 1-3
End-of-Tape/End-of-Reel Conditions 1-3
J. NAM/CCP TERMINAL DEFINITION
COMMANDS J-l
Introduction J-l
Terminal Definition Command Format J-3
Restrictions J-4
Terminal Definition Commands J-4
(AB) - Abort Output Block
Character J-5
(HD)
(HN)
(HS)
K.
Break Key as User Break 1
Backspace Character
I n t e r r u p t i o n o r
User Break 1 Character
(B2) - Termination or
User Break 2 Character
(CH) - Display Terminal
Characteristics
(CI) - Carriage Return Idle Count
(CN) - Cancel Character
(CP) - Cursor Positioning after
Input
(CT) - Network Control Character
(DL) - Delimiters for Single-
Message Transparent Input Mode
(EB) - End-of-Block Character
(EL) - End-of-Line Character
(EP) - Echoplex Mode
(FA) - Full-ASCII Input Mode
(HC) - Host Connection
- Display of Host Nodes
- Host Node Selection
- Host Selection
(IC) - Flow Control for Input
Devices
(IN) - Input Device and
Transmission Mode
(LI) - Line Feed Idle Count
(LK) - Lockout of Unsolicited
Messages
(MS) - Message to Network
Operator
(OC) - Flow Control for Output
Devices
(OP) - Output Device Selection
(PA) - Parity Processing
(PG) - Page Waiting
(PL) - Page Length
(PW) - Page Width
(RC) - Reset Terminal
Characteristics
(SE) - Special Editing Mode
(TC) - Terminal Class Command
(TM) - Terminating a Terminal-
Host Connection
(XL) - Multimessage Transparent
Mode
DELIMITING AND TRANSMITTING
TERMINAL INPUT
Physical End-of-Line (Line Feed)
Logical End-of-Line (Carriage Return)
Message Transmission
J-5
J-6
J-6
J-7
J-7
J-8
J-8
J-9
J-9
J-10
J-10
J-ll
J-l 2
J-13
J-14
J-14
J-15
J-15
J-17
J-17
J-18
J-18
J-20
J-20
J-21
J-21
J-21
J-2 2
J-23
J-23
J-24
J-24
J-24
J-25
J-26
J-27
K-l
K-l
K-l
K-l
20 60459680 H
![](asset-15.png)
jgg^N.
0^\
V
L. PASSIVE PROCEDURES L-l 0. INTERACTIVE TRANSFER FACILITY (ITF) 0-1
.PROC Directive L-l
Procedure and Parameter Descriptions L-2
Parameter Matching L-2
Order-Dependent Parameter
Matching Mode L-2
Order-Independent Parameter
Matching Mode L-6
Selecting the ITF Application
Selecting a Remote CYBER 200 System
Processing Your Job on the
Remote CYBER 200
Terminating Your ITF Session
P. FILE TRANSFERS USING XMODEM
0-1
0-1
0-2
0-2
P-l
M. PAPER TAPE OPERATIONS
General Description
Teletypewriter
Control Characters
Input Lines
Punching Tape Off-Line
Tape Mode
Punching a Tape On-Line
Corrections
M-l XMODEM Command
Using XMODEM in Prompting Mode
M-l Sending a File from a CYBER
M-l Receiving a File from a Micro
M-2 Configuration File
M-2 File Transfer Notes
M-3 Text Files
M-3 CYBER Binary
M-4 Micro Binary
M-4 Limitations and Considerations
P-l
P-3
P-3
P-4
P-4
P-6
P-6
P-6
P-6
P-7
N. MASS STORAGE DEVICE STATISTICS N-l
INDEX
1-1 Central Memory Allocation
2-1 Logical Structure of Files
2-2 NOS and CRM File Terminology
2-3 Sample Card File Structure
2-4 Use of ANSI Labels
3-1 FORTRAN Compile and Execute Deck
3-2 Submitting Jobs to Remote Hosts
4-1 Procedure File Structure
4-2 TESTPN with Valid Entry
4-3 TESTPN with Invalid Entry
4-4 Summary of Checklist Entries
4-5 Calling a Procedure
5-1 Command Processing Flow
7-1 QUEUE7 Execute Queue Sample
Listing
7-2 QUEUE7 Input Queue Sample Listing
7-3 QUEUE7 Output Queue Sample Listing
FIGURES
1-3 7-4
2-2
2-3 15-1
2-6 15-2
2-8 15-3
3-2 15-4
3-6.1
4-3 F-l
4-5
4-5 H-l
4-15
4-41 H-2
5-6
L-l
7-47
7-48 L-2
7-49
Resource Commitment Processing
(Simplified) 7-53
R a n d o m A c c e s s F i l e S t r u c t u r e 1 5 - 2
LIBEDIT Input and Output 15-18
User Library Structure 15-33
Maximum Size of Global Library
Set 15-43
Examples of Coded Card
Conversion F-4
Carriage Control Tape Format
(Standard Paper Length; 6LPI) H-5
Carriage Control Tape Format
(Short Paper Length; 8LPI) H-6
Keyword Substitution in Two
Procedures L-5
Keyword Substitution in
Nested Procedures L-9
60459680 G 21
![](asset-16.png)
TABLES
2-1 Physical File Structure on
Different Devices
Data Representation on
Magnetic Tape
User Job Access Levels
Procedure Directives
Programmable Function Keys for
Procedures
Help on Procedure Calls
Range of Permissible Formats
for the COPY Command
Code Set-Line Terminator
Reference Chart
Compatible File Structures for
the VERIFY Command
10-1 Access Mode Granted When
Attaching a Currently Attached
Direct Access File
Character Sets for Interactive
Jobs
Character Sets for Batch Jobs
2-2
3-1
4-1
4-2
4-3
9-1
9-2
9-3
A-l
A-2
2-5
2-7
3-15
4-10
4-25
4-48
9-6
9-24
9-67
10-10
A-5
A-7
A-3
A-4
A-5
A-6
H-l
H-2
J-l
J-2
K-l
L-l
L-2
ASCII to 6/12-Bit Display Code
Conversion A-10
Nine-Track ASCII Coded Tape
Conversion A-l3
Nine-Track EBCDIC Coded Tape
Conversion A-l4
Seven-Track Coded Tape
Conversions A-l5
Carriage Control Characters for
5 1 2 / 5 8 0 a n d 5 8 7 0 P r i n t e r s H - 3
Carriage Control Characters for
585 Printers H-4
Default Terminal Definitions J-28
Parameter Ranges for Terminal
Definition Commands J-29
Default Message Delimiters
and Transmission Keys K-2
Parameter Substitution in
Order-Dependent Mode L-4
Parameter Substitution in
Order-Independent Mode L-8
22
'*^^S\
60459680 H
![](asset-17.png)
SYSTEM DESCRIPTION
/ff^x
NOS is capable of several concurrent processing modes. The following are the processing
modes available.
• Local batch.
• R em ot e b at ch .
• Transaction.
• Interactive.
The network processing modes (remote batch, transaction, and interactive) operate through
the Network Access Method (NAM) communications software. These processing modes are
implemented, respectively, by the following NAM applications: Remote Batch Facility (RBF),
Transaction Facility (TAF), and Interactive Facility (IAF).
The primary emphasis of this manual is interactive and local batch processing. For the
other processing modes, consult the appropriate manuals listed in the preface.
NOS, like all operating systems, is the interface between you and the capabilities of system
hardware components. The remainder of this section describes the hardware and software that
make up a NOS-controlled computer system. In most cases, you need not understand the
operation of system hardware or the internal operation of system software. This manual
describes these topics only as general background for understanding NOS commands.
SYSTEM HARDWARE
NOS can operate within the CYBER 180, CYBER 170, CYBER 70, and 6000 Computer Systems (refer I
to the preface for an exhaustive list of model numbers). The primary hardware components of ■
each system are the following.
Central processor unit(s).
Central memory.
Extended memory (optional).
Peri phe ral processors.
Peripheral equipment.
0^^.
60459680 E 1-1
![](asset-18.png)
CENTRAL PROCESSOR UNIT
The central processor unit (CPU) executes instructions and manipulates and stores data
retrieved from central memory. The number and type of CPUs within a mainframe vary with the
machine model. As a result, some models can execute additional instructions. These model
differences do not affect applications written in higher level languages.
CENTRAL MEMORY
The primary functions of central memory (CM) are:
• To buffer data to and from the peripheral processors.
• To transfer instructions and data to and from the CPU. ^*^v
Job Field Length
The job field length is the portion of central memory that is assigned to your job. Several
jobs can reside in CM simultaneously. Each job is assigned a starting CM address (its
reference address or RA) and is allocated an initial field length (the CM words in which the
job resides and executes). The field length is adjusted during job execution as described
in section 3. Figure 1-1 shows a job field length within CM.
A reference to an address outside the job's field length range causes a hardware error /
condition and job termination.
The maximum field length depends on the CM size and installation parameters used to control
memory usage. The system assigns the CPU to jobs requiring CPU activity. Rapid switching
of CPU control between jobs enables them to execute concurrently. The exact amount of time
allowed for each job depends on system activity and system parameter settings. Thus, the
time required to complete a job may vary from run to run, although the actual CPU execution
time is similar.
When a job completes, aborts, or rolls out (that is, its execution is suspended), the field
length is released, cleared, and made available to another job.
1-2 60459680 C
![](asset-19.png)
CENTRAL
MEMORY
ABSOLUTE
ADDRESS
REFERENCE
ADDRESS (p)
CENTRAL
MEMORY
RESIDENT
USER
JOB
RA
RA + p 0*£p<FL
RA + FL FL
FIELD
LENGTH
(FL)
Figure 1-1. Central Memory Allocation
Central Memory Resident
The portion of CM reserved for system use is called central memory resident (CMR). It
contains system tables, directories, and the CM portion of the system monitor (CPUMTR),
EXTENDED MEMORY
Extended memory for NOS computer systems (refer to preface), can be used for the following
purposes.
• As a directly accessible memory device via FORTRAN or COMPASS statements for
extended memory data storage and retrieval (refer to the FORTRAN 5 Reference Manual
or appendix D of Volume 4, Program Interface).
• As storage for frequently accessed small files (refer to ASSIGN command in section 7
and Permanent File Commands in section 9).
• As an alternate system device for st ori ng copi es of fre que ntly used routines.
• As a link between mainframes in a multimainframe configuration.t
You must be authorized to use extended memory (refer to LIMITS command in section 7).
fModel 176 cannot use extended memory to link mainframes,
60459680 H 1-3
![](asset-1a.png)
PERIPHERAL PROCESSORS
The peripheral processors (PPs) process communications between CM and individual peripheral
devices. They also perform system control functions. A peripheral processor can:
• Read and write CM.
• Read and write extended memory indirectly via CM or directly via the distributive
data path (DDP).T
• Transfer data to and from peripheral devices through the data channels.
NOS supports a variety of PP configurations. Each computer system supports a different
range of configurations. To determine the configurations supported by your computer system
consult the appropriate system hardware reference manual listed in the preface.
PERIPHERAL EQUIPMENT
Peripheral equipment varies among installations but usually includes card readers and
punches, line printers, mass storage devices, and magnetic tape units. NOS supports the
following equipment models.
405 Card Reader
415 Card Punch
533/536 Printer
580-12, 580-16, and 580-20 Line Printers
585 Printer
5870 Non-Impact Printer
834/836 Disk Storage Subsystem
844-21 Disk Storage Subsystem
844-41/44 Disk Storage Subsystems
885-11/12 Disk Storage Subsystems
885-42 Disk Storage Subsystem
887 Disk Storage Subsystem
895-1/2 Disk Storage Subsystem
819 Disk Storage Subsystem
Mass Storage Subsystem (MSS)
7990 Mass Storage Extended Subsystem (MSE)
639, 667, 669, 677, 679, and 698 Magnetic Tape Units
tDDP does not apply to peripheral processors for models 176, 865, 875, and 180-class
mainframes.
1-4 60459680 H
^e^
![](asset-1b.png)
0S&\
/00^X\
(
255x Network Processing Units
26xx Device Interfaces
380-170 Network Access Device
6683 Satellite Coupler
SYSTEM SOFTWARE
Software executed within a computer system can be divided between software that is built
into the system during system initialization and software that executes as jobs within the
running system. Software present when the system begins running includes the operating
system and products such as compilers, CYBER Loader, and CYBER Record Manager.
USER PROGRAMS
A user program is a group of CPU instructions that perform a certain task or calculate a
result. A user program can be written in a language at any of three levels.
• Compiler languages provide you with a language suited to your particular needs. The
program statements are translated by the appropriate compiler (FORTRAN, COBOL,
ALGOL, and so on), which generates assembler language or machine language
instructions. Programs written in compiler languages may be machine-independent.
• Assembler languages provide a one-to-one relationship between instructions and
machine operation. Mnemonics are provided for each instruction. These languages
are machine-dependent. Much of the NOS system is written in COMPASS, the assembler
language of the CYBER 180, CYBER 170, CYBER 70, and 6000 Computer Systems.
• Hardware instructions are interpreted directly by the computer. Each hardware
instruction is a binary number. Most users are rarely concerned with instructions
written at this level except when program debugging requires interpreting memory
dumps.
OPERATING SYSTEM
NOS is a group of programs that supervise and coordinate the operation of system hardware
and the execution of products and user programs. The following lists some of the functions
of NOS.
• Loading and scheduling of user programs.
• Job validation and accounting.
• Command translation.
• File retrieval, manipulation, routing, and storage.
• Job input and output.
• Normal and abnormal job termination.
• Memory dumps.
60459680 G I"5
![](asset-1c.png)
CYBER Loader
CYBER Loader prepares programs for execution. Following your directions, it allocates
memory for a program, loads the program modules into their appropriate locations, generates
a load map, and initiates program execution. It can load subdivided programs for more
efficient use of memory. Refer to the CYBER Loader Reference Manual for more information.
CYBER Record Manager
CYBER Record Manager (CRM) is the interface between program input/output (I/O) functions and
NOS physical I/O functions. NOS commands do not use CRM. Some of the products that use CRM
are COBOL 5, FORTRAN Extended 4, FORTRAN 5, Sort/Merge 5, PL/I (Programming Language I), and
DMS-170.
The functions of CRM are divided between the Basic Access Methods (BAM) and Advanced Access
Methods (AAM). BAM handles sequential and word-addressable file organizations; AAM handles
indexed sequential, direct access, and actual key file organizations. Refer to the
appropriate CYBER Record Manager manual listed in the preface.
1-6 60459680 C
![](asset-1d.png)
FILES
0^\
0^\
A file is a collection of information addressable by name. All NOS data processing involves
operations performed on files. Files can be differentiated by their name, structure, or
file type or by whether they are assigned to a job (NOS jobs are described in section 3).
FILE NAMES
A file name consists of unique string of seven or less alphanumeric characters. Although
NOS allows file names that begin with a digit, many of its products (FORTRAN 5 and COBOL 5,
for example) do not support such file names. Refer to the product reference manual listed
in the preface for details.
Examples:
A Al TAPE DUMP12 COMPILE
NOS uses many internal scratch files. Most of these scratch files have names beginning with
the letters ZZ or SCR. Avoid using a name starting with these letters for any of your files.
The following file names are significant because they are associated with system-managed
files that are assigned to your job.
INPUT OUTPUT PUNCH PUNCHB P8
Refer to the description of File Types for more information.
FILE STRUCTURE
A file consists of a well-defined set of data. Its physical representation varies markedly
with the device upon which it resides. For instance, the physical structure of a file on
magnetic tape is only remotely similar to its physical structure on disk. To facilitate the
manipulation of file data by user and system programs, the system imposes a logical
structure on a file that does not vary with device residence.t
A logical file consists of a contiguous series of data (physically, the data is not always
contiguous). A file always has a beginning of information and an end of information. It
can be subdivided into a maximum of three levels. Figure 2-1 illustrates the structure of a
file with one, two, and three levels of subdivisions. NOS and its products (refer to
sec ti on 1 ) al l u se th is ba sic s tru ct ur e f or a l og ica l file .
tThere are differences in logical structure that depend on device residence, but these
differences are of interest only to a COMPASS programmer. These differences are described
in Volume 4, Program Interface.
60459680 H 2-1
![](asset-1e.png)
NOS and some of its products do differ in both the levels of file subdivision they recognize
and the names of the subdivisions. One of the most prominent of these products is CYBER
Record Manager (CRM). It handles input and output for some widely used products like
FORTRAN 5 and COBOL 5. The next two subsections contrast the treatment that NOS and CRM
give a logical file.
Beginning of
Information End of
Information
Third-level Subdivision Data
cccc|cccccc|cccccccc|cccc|cccccc|ccccccccccccfccccccc
Second-level Subdivision
I c cc c c cc c c c clc clc cl ccccccccc cccccccccccc ccccccccc
c c |c c c clc c c cl
First-level Subdivision
cccccccccccccccc cccccccccc c c c le c c cl
Figure 2-1. Logical Structure of Files
2-2
60459680 C
'*s^\
![](asset-1f.png)
CYBER RECORD MANAGER FILE STRUCTURE*
CRM recognizes all three levels of file subdivision. It calls a first-level subdivision a
partition, a second-level subdivision a section, and a third-level subdivision a record.
Through CRM, you can specify a file organization, a blocking type, and a record type for
your data. The file organization determines how records are accessed, the blocking type
determines how CRM records are grouped on their storage media, and the record type defines
the smallest unit of data CRM can retrieve. Refer to the CRM manuals listed in the preface
for a detailed description.
NOS RLE STRUCTURE
NOS recognizes only two levels of file subdivision, the first and second levels.t NOS calls
a first-level subdivision a file and a second-level subdivision a record. The record is the
smallest recognizable unit for both CRM and NOS but the term does not always refer to the
same subdivision for the two processors. Figure 2-2 illustrates the differences in
terminology.
file
processor
first-level
subdivision
second-level
subdivision
third-level
subdivision
NOS
CRM
fi l e
partition
record
section record
Figure 2-2. NOS and CRM File Terminology
Since NOS terms a first level subdivision a file, a NOS file can contain more than one
l o g i c a l fi l e ; i f i t d o e s , i t i s c a l l e d a m u l t i fi l e fi l e . A m u l t i fi l e fi l e b e g i n s a t
be gi nni ng -of -i nfo rm ati on ( BO I) a nd e nds at e nd-o f- inf or mat io n (E OI) . A fi le w it hin a
multifile file begins either at BOI or after the end-of-file (EOF) of the preceding file.
It ends at its EOF.
Each file consists of zero or more logical records of information. A record is zero or more
60-bit CM words. A record begins at the BOI, after an EOF, or after the end-of-record (EOR)
of the preceding record. It ends at its EOR. The following is the structure of a
single-record file.
BOI data EOR EOF EOI
BOI data EOR EOI
Most simple files, like text files, have one of these two formats.
fThis is true for NOS commands but, at the program level, NOS does recognize third-level
subdivisions.
0^\
60459680 C 2-3
![](asset-20.png)
The following is the structure of a multirecord, multifile file.
BOI data EOR data EOR EOF data EOR data EOR EOF EOI
The last EOF in a file may or may not be present depending upon the program used to create
the file.
PHYSICAL RLE STRUCTURE
When NOS stores a file, it automatically converts the file to a structure that will conform
to the physical characteristics of the storage medium. The logical file and record marks
are converted to physical BOI, EOR, EOF, and EOI indicators.
The basis of all physical file structures is the physical record unit (PRU), the minimum
amount of data that can be read or written in a single device access. Table 2-1 lists the
PRU size, and record and file mark indicators for each supported storage device.
2-4 60459680 C
![](asset-21.png)
0^*\
Table 2-1. Physical File Structure On Different Devices
Record and Pile Mark Indicators
Device
Magnetic disk
or extended
memory
Card deckst
PRU Size
64 CM words.
One card.
Interactive Terminal
Magnetic
tapetttt
(Internal)
SI
(System
internal)
(Stranger)
(Long block
stranger)
(Foreign)
One line.
512 CM words;
each PRU in
cludes a 48-bit
terminator.
BOI
PRU 1 or random
address 1 of
the disk (count
ing from 0).
First card in
the deck.
None.
EOR
PRU of less
than 64 words
w i t h a l in k t o
the next PRU.
Card with a
7/8/9 punch
in column 1.
Remote Batch
Facility
(RBF)/HASP can
also use /*E0R.
EOF
Zero-length
PRU (no data)
with special
link to next
PRU.
Card with
6/7/9 punch
in column l.tt
EOI
Zero-length
PRU with no
forward link.
If labeled, tape
mark following
HDR1 label. If
unlabeled, load
point.tt
512 CM words;
each PRU of
less than 512
words has a
48-bit
terminator.
Maximum of 512
CM words; (refer
to BS parameter
on COPY command
in section 9
and to appendix
J in volume 4).
No maximum
defined (refer
to BS param
eter on COPY
command in
section 9 and
to appendix J
in volume 4).
Determined by
C or FC param
eter on ASSIGN,
LABEL, or
REQUEST command.
If labeled, tape
mark following
HDR1 label. If
unlabeled, load
point .ttt
If labeled, tape
mark following
HDR1 label. If
unlabeled,
load point .tt
If labeled, tape
mark following
HDR1 label.
If unlabeled,
load point.ttt
Load point.
On input, one
nonnull line of
data with EOR
l e ve l 1 . .
A PRU of less
than 512 words
with level
number of 0.
A PRU of less
than 512 words
with level
number between
0 and I63.
End of each
PRU.
End of each
PRU.
None.
On input,
one null line
of input.
Zero-length
PRU whose
terminator
contains a
level number
of 178.
Zero-length
PRU whose
terminator
contains a
level number
of 17
Tape mark.ttt t
Tape mark.ttttt
Tape mark.
Card with
6/7/8/9 punch
in column 1.
RBF/HASP can
also use /*E0I.
None.
Tape mark fol
lowed by an
E0F1 label.
Tape mark fol
lowed by an
E0F1 label.
If labeled, a
tape mark fol
lowed by an
E0F1 label. If
unlabeled, there
is no EOI in
dicator.
If labeled, a
tape mark fol
lowed by an
E0F1 label. If
unlabeled, there
is no EOI in
dicator.
None.
tFor more information, refer to appendix F.
ttThe 6/7/9 card is not recognized in a remote batch Job. In an RBF job the end-of-file marker is a card with a
7/8/9 punch in column 1 and a level number of 17s in columns 2 and 3. RBF/HASP can also use a card with /*E0R in
columns 1 through 5 and a level number of 17g in columns 6 and 7.
tttln the case of multivolume tape files, BOI is the HDRl label of the first volume. In the case of an ANSI multifile,
++ BOI Is the HDRl label associated with the beginning of the multifile.
*II or more lnformation, refer to section 12 and appendix G.
tttttOn labeled tapes, interchange standards require that tape marks be used only to delimit tape label groups.
60459680 E 2-5
![](asset-22.png)
Cord Files
The physical file and record indicators in a card file are shown in figure 2-3 and listed in
table 2-1. Although card decks do not have a defined PRU size, a card is the minimum data
unit. NOS can read and punch cards in coded (Hollerith), binary, and absolute binary
formats as described in appendix F. Coded cards are punched in 026 or 029 keypunch mode.
The system uses the installation default keypunch mode (chosen by the installation) for
reading cards unless a 26 or 29 is punched in columns 79 and 80 of a job, EOR, or EOF card,
indicating that the subsequent cards are punched in that mode. NOS can punch up to 80
characters on a coded card and up to 150 characters (15 CM words) on a binary card.t
EOF
E O R * A
BOI
.•-'G5%.
Figure 2-3. Sample Card File Structure
Mass Storage Files
Mass storage files are stored on disk or extended memory.
To use NOS, you do not need to know the physical structure of mass storage; you do need to
know its logical structure, which contains the concepts of logical devices and logical
tracks. A logical device is one or more physical disk units known to the system as a single
device. A logical track is a file allocation unit determined by the device type.
t Keypunch mode selection is not supported for jobs entered through a 200 User Terminal or
similar remote batch terminal except for HASP.
2-6 60459680 C
![](asset-23.png)
Each permanent file on mass storage is accessed via a catalog track containing the permanent
file catalog of its owner. Indirect access files (refer to Permanent Files) must reside on
the same device as their catalog; direct access files may reside on another device. Space
is allocated for mass storage files in units called reservation blocks. An indirect access
file reservation block is always 64 words (one PRU). A direct access file reservation block
is a logical track. The maximum size of your mass storage file is determined by your
validation limits (refer to LIMITS Command in section 6).
0F^\
Magnetic Tape Files
You may write information on magnetic tapes in either coded mode or binary mode. Coded mode
operations involve data conversion from NOS-supported character sets to external character
sets as shown in table 2-2. Coded mode is applicable largely for S and L tape formats.
Binary mode operations copy files with no character set conversion and can be used for any
tape format.
The term coded mode should not be confused with coded line. A coded line is defined as a
line of 160 characters or less, terminated by a zero byte. Similarly, coded and binary mode
should not be confused with coded and binary files. A coded file is a NOS system file coded
in 6-bit display code, 6/12-bit display code, or 7-bit ASCII code. A binary file is simply
a file containing binary information. Coded files can be copied in coded or binary mode;
binary files can be copied only in binary mode.
The only NOS commands recommended for coded mode operations are COPY, FCOPY, and TCOPY. Any
of the copy commands can be used for binary mode copies. For CYBER Record Manager (CRM)
files, the CM parameter on the FILE command is used to select coded or binary mode. For
FORTRAN programs, use the BUFFER 0UT(n,l) statement to select binary mode and the BUFFER
0UT(n,0) statement to select coded mode. For COBOL programs, use either the RECORDING MODE
IS BINARY statement or the RECORDING MODE IS CODED statement.
The representation of data in memory and on tape depends on the number of tracks (seven or
nine), the recording mode (binary or coded), and the specification of the CV=cv parameter on
the LABEL command. Table 2-2 shows how the data representation varies with these factors.
Table 2-2. Data Representation on Magnetic Tape
0r*\
Number of
Tracks Binary Mode
1 . O d d p a r i t y.
2. Groups of four 6-bit
characters in memory are
written without conversion
on three-frame units on tape*
1 . O d d p a r i t y.
2. Each 6-bit character in
memory is written without
conversion.
Coded Mode
1 . O d d p a r i t y.
2. Each 6-bit character in
memory is translated into
an 8-bit equivalent on tape.
You can choose EBCDIC
or ASCII by specifying
CV=EB or CV=AS on a LABEL
command.
1• Even parity.
2. Each 6-bit character in
memory is translated to
its BCD equivalent on
tape. The % character is
lost in the translation.
60459680 E 2-7
![](asset-24.png)
I Tap e De nsity
You can select 200- (read only), 556-, or 800-characters-per-inch (cpi) density for
seven-track tapes or 800-, 1600-, or 6250-character-per-inch (cpi) density for nine-track
tapes, provided these densities are available with the site hardware. NOS automatically
processes tape parity errors and end-of-tape conditions unless you select other processing
options (refer to Processing Options in section 12). You can also control error processing
by using the EO parameter on a FILE command.
Tape Labels
Tape labels identify and delimit tape volumes and tape files. Tape marks begin and end most
tape labels. A tape mark is a special bit sequence written and recognized by a tape unit.
NOS processes ANSI standard and nonstandard labeled tapes. Nonstandard labeled tapes are
those whose format or content do not conform to the ANSI standard described in appendix G.
NOS skips to the first tape mark when reading a nonstandard labeled tape if the tape
assignment statement specifies the LB=NS parameter (refer to section 12). All information
after the first tape mark is then handled as data. Any tape marks occurring after the first
tape mark are handled as appropriate for the tape format (refer to table 2-1).
File set configurations (* means tape mark):
Single file on single volume
(A)
VOL1 HDRl
(A)
File A data IL EOF1
Single file on more than one volume
(A)
Volume
1
Volume
2
VOL1 HDR1 File A data
(A)
VOL1 HDR1 File A data
IL EOV1
(A)
EOF1
More than one file on a single volume
(A)
VOL1 HDRl File A data }l
(A) (B)
EOF1 HDR1 File B data
(B)
EOF1
More than one file on more than One volume
(A) (A) (B)
Volume
1
Volume
2
Volume
3
VOL1 HDR1 File A data EOF1 HDR1 File B data EOV1
(B)
VOL1 HDRl File B data EOV1
(B)
VOL1 HDRl File B data
(B) (C)
EOF1
(C)
HDR1 File C data EOF1
Figure 2-4. Use of ANSI Labels
^*^^.
^5^SV
2-8 60459680 H
![](asset-25.png)
ANSI standard labels as defined by NOS are those that conform to the American National
Standard Magnetic Tape Labels for Information Interchange X3.27-1969 standard. NOS can
create or verify ANSI labels if the LABEL command assigns the tape file. Label verification
ensures that the correct volume has been mounted. ANSI labels separate multifile set files
and indicate if a file continues on another volume.
The ANSI label EOF indicates end-of-information for a file within a file set. The use of
ANSI labels to delimit files within file sets is illustrated in figure 2-4.
An ANSI-labeled tape must have the following labels. Other optional labels are described in
appendix G.
Label Location
V0L1 Beginning of volume.
HDRl Beginning of information. If the file continues on to another volume, the
HDRl label is repeated. It must follow the V0L1 label and precede the
continuation of the file information.
E0F1 End of information.
E0V1 End of volume (required only if the file continues on another volume).
Appendix G gives the tape label formats.
Tape Data Formats
NOS can read and write data on magnetic tape in any of the following formats.
Format Mnemonic
Internal (NOS default) I
System internalt si
Stranger S
Long block stranger L
Foreign p
These data formats differ in their PRU (block) size and in their record and file mark
indicators (refer to table 2-1). Other format differences are as follows:
tNOS/BE system default tape format (binary mode only)
60459680 E 2-9
![](asset-26.png)
y e ^ ^ v
Tape
Format Labels I/O Mode Tape
P a r i t y Noise Sizet
I Labeled or unlabeled Binary or
codedtt
Odd
Odd
Seven-track: <eight frames
Nine-track: <six frames
SI Labeled or unlabeled Binary onlyttt Odd
Odd
Seven-track: <eight frames
Nine-track: <six frames
Labeled or unlabeled Binary
Coded 7-track
Coded 9-track
Labeled or unlabeled Binary
Coded 7-track
Coded 9-track
Unlabeled (labels read Binary
as data) Coded 7-track
Odd
Even
Odd
User-selected;
default is < 18 frames
Odd
Even
Odd
Use r-selec te d;
default is < 18 frames
Odd
Eventttt Use r-selec te d;
default is < 18 frames
NOS terminates all blocks on I format types and all blocks that are not a full PRU on SI
format tapes with a 48-bit block (PRU) terminator. The terminator contains the total number
of bytes in the block (including the terminator itself), the number of blocks since the last
HDRl label, and the level number of the block. This terminator enables read operations on I
format tapes to check whether the number of bytes read and the block number expected match
the byte count and block number in the terminator. If either does not match, the system
attempts to recover the missing data. This feature prevents dropped or fragmented blocks
and provides a higher degree of reliability than other data formats.
Tapes should be read with the same format specified as when they were written. Data is then
recovered in its original form. For some formats, NOS writes extra bits which are discarded
when the tape is read. I format nine-track tapes are always written with an even multiple
of 12-bit bytes per block. SI format nine-track tapes may have an extra 4 bits written per
block to preserve the lower 4 bits of a CM word. (A 60-bit CM word would be written in
eight frames, 8 bits per frame.)
All nine-track tapes are written with odd parity. Binary seven-track tapes have odd parity;
coded seven-track tapes have even parity. If a parity error is detected on an F format
seven-track tape, the recording mode (binary or coded) is automatically switched to allow
reading of mixed mode tapes.
Volume 4, Program Interface, describes tape formats in greater detail.
tTape blocks read that are smaller than the noise size are discarded. An attempt to write
a block smaller than the noise size produces an error message. Refer to the NS=ns
parameter of the LABEL command,
ttSpecification of coded mode aborts the job step; refer to TCOPY Command in section 9.
tttI/O mo de b it is ig no re d.
ttttl/O mode on write for F format is specified in the control word and is returned in the
control word on read.
2-10 60459680 E
![](asset-27.png)
y#«^\
■I
RLE TYPES
The system maintains several tables for each job. Every file assigned to a job has an entry
in one or more of these tables. A table entry for a file includes the file name, the device
on which the file resides, file type, and its current position and status.
The system assigns one or more of the following file types to files associated with a job:
I n p ut fi l e t y p e
Queued file type
Local file type
Primary file type
Direct access file type
Library file type
INPUT FILES
An input file is also called a job file because it contains user-supplied commands and data
for a job (refer to section 3). Initially, input files exist on mass storage in the input
queue. A file enters the input queue directly when a local or remote batch job enters the
system or indirectly when a user job submits another job via an LDI, ROUTE, or SUBMIT
command. The input file for an interactive job is normally assigned to the terminal and is
used by an interactive job to read data entered at the terminal into the program. A user
job refers to its input file by the file name INPUT (refer to Input File Control in section
QUEUED FILES
A file is queued as a result of one of the following events:
• Generally, whenever you enter a LDI, OUT, ROUTE, MFQUEUE, or SUBMIT command. Refer
to the description of each individual command for cases where the command fails to
queue a file.
• Job termination. The system automatically queues files named OUTPUT, PUNCH, PUNCHB,
and P8; deferred routed files; and other system-reserved output files if they are
assigned to the job. In interactive jobs, however, the files OUTPUT, PUNCH, PUNCHB,
and PB are not automatically queued.
A queued file can have one of five dispositions:
Input
P l o t
P r i n t
Punch
Wait
60459680 D 2_n
![](asset-28.png)
'"^%\
Your job's origin type determines the default processing of your queued job output. Jobs
originating at a central site card reader are queued to a line printer with the same
system-defined identifier as the card reader. Similarly, the system queues remote batch
output to the remote batch terminal where the job originated. The system gives each remote
batch terminal a unique terminal identifier (TID) when it logs in and uses this TID for
queueing files originating from the terminal. You can determine the default destination of
batch output for your jobs by using the ENQUIRE command and specifying either the JSN=jsn or
UJN=ujn parameter. ENQUIRE shows the default destination in the DS field of its display.
RB indicates remote batch routing and BC indicates routing to the batch devices at the
central site.
You can override the default queueing of job output with the LDI, QGET, ROUTE, SETJOB, or
SUBMIT command (refer to section 7).
Queued files with an input disposition wait until they are scheduled for execution. The
service class of the job determines the scheduling priority of an input file.
For queued files with plot, print, or punch dispositions, their priority grows as they wait
in the queue. Such files are processed when the appropriate device becomes available and
when the file's priority is higher than all other files queued to that device. Refer to the
ROUTE command in section 9 for an enumeration of disposition codes for plotting, printing,
and punching.
A fil e wi th a pr in t di sposi ti on m ust be f or matt ed fo r li ne p ri nting . Mo st sy stem ut il ities
format file OUTPUT for printing, but you must include the appropriate printer control
characters when you create a file to route to a printer (refer to the COPYSBF command and to
appendix H). Files with uppercase and lowercase characters require special processing
(refer to the FCOPY command). Appendix D contains the printer output from a sample job.
A queued file with a wait disposition awaits further specifications from you. The system
queues output from detached interactive jobs with a wait disposition unless you specify a
different disposition. You can explicitly queue files with a wait disposition with the LDI,
ROUTE, SETJOB, and SUBMIT commands.
A file remains queued on mass storage until one of the following occurs:
• The system resource it requires becomes available and the file's priority is the
highest of all queued files with the same disposition.
• You remove the file with the QGET or DROP command.
• Site perso nnel re move it if it resid es i n the queue too long (site-d etermine d).
You can get a list of your queued files with the ENQUIRE command (refer to section 7).
LOCAL FILES
Files of local file type are temporary files. Although all files assigned to a job are
considered local to the job, the local file type includes only those files assigned to your
job that are not given one of the other file types.
You can create a local file in many ways. The following list shows some implicit methods of
creating a local file:
• Name the file for the first time in a copy command or in a read or write command
within a program. A local file created in this manner always resides on mass
storage.
2-12 60459680 E
![](asset-29.png)
J ^ N
• Name the file for the first time in an ASSIGN or REQUEST command that assigns the
local file to mass storage or to an interactive terminal or name the file in an
ASSIGN, LABEL, or REQUEST command that assigns the local file to magnetic tape.
• Name the file in a GET command generating a local mass storage file.
• Name the file as the output file in a compiler-or assembler-call command.
• Name the file as the list or output file in one of the file editing commands (MODIFY
or EDIT, for example).
To save the contents of a local mass storage file, you issue a SAVE or REPLACE command to
copy the local file to a permanent indirect access file or an APPEND command to copy the
local file onto the end of an existing permanent indirect access file. Data written on a
local file assigned to magnetic tape is written on the tape for later access. Local files
are released upon job completion.
PRIMARY FILES
The primary file is a temporary mass storage file designated as the primary file by a
PRIMARY, NEW, or OLD command. Only one primary file can exist for a job at a time. Some
commands use the primary file as the default file when a file name is not specified,
rewinds the primary file before each job step. NOS
DIRECT ACCESS FILES
You assign a direct access permanent file to your job by issuing an ATTACH or DEFINE
co mm an d. W he n you d efi ne t he fi le or whe n y ou a tt ac h th e fil e i n a mode pe rm ittin g fi le I
modification, you can write on the permanent file. Refer to Permanent Files in this section.
LIBRARY FILES
A li br ar y fi le i s a r ea d- on ly fil e t ha t se ve ra l u se rs c an access si mu lt an eo us ly. T hi s fi le
type should not be confused with system library programs or with public permanent files
stored under user name LIBRARY. Refer to Libraries in this section for a description of the
uses of the term library in NOS.
You must be authorized to access a library file.
If authorized, you can read a library file after naming it in a COMMON command.
PERMANENT FILES
Your permanent files reside on mass storage until you purge them or until your site archives
them (contact your computer center for their archiving procedures). The system maintains a
separate permanent file catalog for each user name and it contains entries for all of your
permanent files created under the user name you are using to access the system. A catalog
entry includes the file name, its location on mass storage, its length, permission modes,
and access history. Unless another user name is specified, the system directs all permanent
file requests to the files of the user specified on the last USER command (or specified in
the login of an interactive job).
60459680 E 2_n
![](asset-2a.png)
User names (refer to Validation in section 3) that contain asterisks represent users with
automatic read-only permission to files in the catalogs of other users. The user name must
match the other user name in all characters not containing asterisks. For example, the user
with user name *AB*DE* can access the catalogs of the following users.
• UABCDEF
• UABDDEE
• MABCDE1
The device residence of permanent files and their backup copies are described under Mass
Storage File Residence in this section.
The two types of permanent files, indirect access permanent files and direct access
permanent files, are described in the following paragraphs.
INDIRECT ACCESS PERMANENT FILES
You access an indirect access permanent file by naming it in an OLD or GET command. The
system copies the permanent file from mass storage to a temporary file (primary or local
file type). To alter an indirect access permanent file, you make the changes to the
temporary copy and then enter the REPLACE command which writes the temporary copy over the
indirect access permanent file. You create an indirect access permanent file by naming a
temporary file in a SAVE or REPLACE command. '-1^\
Mass storage for indirect access permanent files is allocated in 640-character blocks (64 CM
words). Because of its small allocation block size, indirect files are most economical for
relatively small files.
The maximum size of an indirect access file is determined either by your validation limits
(refer to the LIMITS command), or by the device limitations described in Mass Storage Files
i n t his s ec t ion .
DIRECT ACCESS PERMANENT FILES
You access a direct access permanent file directly, not through a temporary copy. Data is
written directly on the permanent file.
You create a direct access permanent file with a DEFINE command, which determines its name
and residence and the default access mode available to other users. Other users may, if you
permit, access the file with an ATTACH command. A number of users can attach the file
concurrently, but only one user at a time can change the file. To change the file, you must
attach it in modify, update, append, or write access mode. If you attach the file in write
mode, no other user can attach that file concurrently.
Even if a file is currently attached to a job, you can purge the file from the permanent
file catalog with a PURGE command. However, the purged direct access file remains attached
to the job until it is released by a RETURN, CLEAR, UNLOAD, OLD, or NEW command or until the
job ends.
2-14 60459680 C
![](asset-2b.png)
jps=v
r
Mass storage for direct access permanent files is allocated in large blocks; the block size
depends on the mass storage device type on which the file resides (refer to Mass Storage
Files in this section). Because of their large allocation block size and the write
interlock feature, direct access files are often used for database files.
The maximum size of a direct access file is determined by your validation limits (refer to
LIMITS Command in section 7), or by the device limitations described in Mass Storage Files
i n t his s ec t ion .
MASS STORAGE FILE RESIDENCE
For most mass storage file operations, you need not be concerned about the specific device
on which your file resides. However, under certain circumstances, you may wish to override
the default device residence for local or permanent files.
With the ASSIGN command, you can assign a local file to either a specific device or to a
device category if you are so authorized.
Every permanent file you create resides either in your family of permanent file devices, on
an auxiliary device, or on an alternate storage subsystem. Unless you specify otherwise, |
all permanent files are saved in your family. Refer to the NOS 2 Analysis Handbook for
further details.
FAMILY DEVICES
A family consists of a set of mass storage devices. Normally, a system has only one family
(the default family) of permanent file devices. However, because families are
interchangeable between NOS systems, several families may be active on one system, or a
system may be part of a multimainframe system. For example, consider an installation with
two systems, A and B. System B provides backup service to system A. If system A failed,
its family of permanent file devices could be introduced into system B without interrupting
current operations on system B.
You identify your family by supplying a one- to seven-character family name. You can
specify a family name on the USER command. If you are authorized to use secondary USER
commands (refer to the USER command), you also specify a family name on a USER command in
interactive jobs. If your family is the system's default family, you may, but need not,
supply the family name. When the family name is omitted, the system uses the system default
family name. If your family has been introduced into another system, you must supply your
family name.
If you choose to save files on family devices, you have the option of either using the
system default device type or specifying another type of permanent file device.
60459680 H 2-15
![](asset-2c.png)
/■"^^V
AUXILIARY DEVICES
An auxiliary device is a supplement to the mass storage provided by family devices. It is
identified by a one-to-seven-character pack name. An auxiliary device is not necessarily a
disk pack that can be physically removed as the pack name implies. Rather, an auxiliary
device can be any mass storage device supported by the system and defined as such by the
installation. Each auxiliary device is a self-contained permanent file device; all direct
and indirect access files represented by the catalogs on the device reside on the device.
Auxiliary devices may be defined as public or private. Anyone who supplies the appropriate
pack name can create, replace, and access files on a public device. Only one user, the
owner, can create and replace files on a private auxiliary device, but others may access or
replace those files as permitted by the owner.
ALTERNATE STORAGE SUBSYSTEMS **)
Disk is the usual residence of permanent mass storage files. However, if your installation
has an alternate storage subsystem, some direct access files can be stored there. An
alternate storage subsystem is well suited for the storage of files that are accessed
infrequently. Accessing a file residing on alternate storage takes a few extra seconds,
because the file must be retrieved and copied (staged) to disk. You can specify the
preferred residence of your direct access files with the PR parameter on the DEFINE, CHANGE,
or SAVE commands. You can ascertain the residence of your files with the CATLIST command.
In the CATLIST output, file names surrounded by parentheses indicate that these files reside
on alternate storage rather than on disk.
Usually, when attaching a file from alternate storage, the system suspends the job until the
file has been staged and assigned to the job. (You can determine the status of your staging
request for an alternate storage file with the ENQUIRE or cE command.) However, if you
specify the RT parameter on the ATTACH, GET, or OLD command, the job continues processing
while the file from alternate storage is being staged to disk. You must then issue a second
ATTACH, GET, or OLD command to assign the file to your job after staging. You can then
check that the file has been attached by using either the FILE function (refer to section 6)
or a LENGTH or ENQUIRE command.
If a permanent file is lost or destroyed, site personnel can recover the file by loading its
backup copy. Generally, sites perform regular dumps of permanent files to magnetic tape to /*^
serve as the permanent file backup. By specifying the BR parameter on the DEFINE, CHANGE, '
or SAVE command, you can choose to have a tape backup copy of your direct access file kept
even if the file resides on alternate storage. You also can choose to have the alternate
storage file copy serve as a backup, or you can require no backup copy of your file.
2-16 60459680 H
![](asset-2d.png)
yflSii^Vy
LIBRARIES
As defined in the glossary (appendix C), the term library has several meanings. The
applicable meaning for the term must be determined from its context. The following
describes some NOS libraries.
USER NAME LIBRARY
Files stored under user name LIBRARY need not be libraries themselves. An installation
saves programs or text as files under user name LIBRARY so that authorized users can access
them from a centralized location. You can access those files by specifying the file name
and the alternate user name LIBRARY on their permanent file request or by issuing a LIB
command for indirect access files.
PROGRAM UBRARIES
A program library is a collection of compressed source deck images stored in Modify or
Update format. You access these compressed source decks through MODIFY or UPDATE commands
(refer to section 15).
USER UBRARIES
User libraries are the files named in the LIBRARY, SATISFY, LIBLOAD, or LDSET loader command
or in program binaries. These files are searched by CYBER Loader to satisfy external
references within a program it is loading. They contain compiled or assembled routines.
The first record of a user library is a ULIB record; the last record is an OPLD record.
Section 15 describes commands that create, catalog, and manipulate user libraries.
60459680 G 2-17
![](asset-2e.png)
![](asset-2f.png)
JOB FLOW AND EXECUTION
The primary job types are batch and interactive. A batch job is a file of commands and
data. Its first record, called the command record, contains lines of text that specify NOS
commands. Every batch job begins with a Job command and a USER command. The end of the
command record is marked by an EOR (or an EOI if there is no data in the job).
If records follow the command record, they contain program, data, or directive input for the
commands. As each command requiring user input is processed, the system reads the next
record in the input file (unless the command specifies otherwise). These records must be in
the same order as the commands that use them.
For example, figure 3-1 illustrates a job file. In this job file, the first two commands
are processed by system routines that require no additional user input. The third command,
FTN5(G0), requests the compilation and execution of a FORTRAN 5 program. The compiler reads
the FORTRAN 5 source program from the second record of the input file. After successful
compilation, the system executes the program. Because the program reads data from the input
file, it takes input data from the third record of the input file. Normal job termination
occurs when the system reads the command record EOR (the first 7/8/9 card).
You can also consider an interactive job to be a file of commands and data. You do not
submit the file to the system as a unit, but enter input one command at a time from a
terminal. Generally, the system processes each command as soon as you enter it. However,
you may group commands in a procedure and those commands are executed together when you call
the procedure.
JOB INITIATION AND TERMINATION
The methods of job entry and termination differ for interactive and batch jobs.
BATCH JOBS
You can enter a batch job in the following ways:
• Enter a job file through a local card reader.
• Enter a job file through a remote batch terminal.
• Enter a job file using the HELLO7, LDI, MFQUEUE, ROUTE, or SUBMIT command from an
interactive or another batch job.
To enter a job file through a remote batch terminal, you must use the Remote Batch Facility
(RBF). Consult the Network Products Remote Batch Facility Version 1 Reference Manual for
details. Section 7 describes the LDI and SUBMIT commands. Section 9 describes the MFQUEUE
and ROUTE commands.
Unless abnormally terminated, your batch job ends after the system executes the last command
in the command record of your job file.
60459680 H 3-1
![](asset-30.png)
/■"^fev
DATA
RECORD
PROGRAM
RECORD
COMMAND
RECORD
Hll * -DATA DECK
SOURCE DECK
USER,NAM,PASS
FTNJOB.
/«*rSs?\
Figure 3-1. FORTRAN Compile and Execute Deck
INTERACTIVE JOBS
To enter an interactive job, you must use the Interactive Facility (IAF). Volumes 1 and 2
of this reference set give a more detailed description of login and logout procedures for
interactive jobs. Section 16 describes terminal and input/output conventions.
Login
Before you can login to a host computer, you must establish a connection with the network
software. If you need information on how to connect to Communications Control Program (CCP)
software, refer to Volume 2, Guide to System Usage. If your network uses CDCNET, refer to
the CDCNET Terminal Interface Usage manual.
Once you have established a network connection, you can begin the login sequence.
3-2 60459680 F
![](asset-31.png)
/0K>\
The following example shows an abbreviated login sequence.t Your entries appear in
lowercase characters.
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978,198X.
YY/MM/DD. HH,MM,SS T02A57
NETWORK OPERATING SYSTEM NOS 2
FAMILY: ,usernam,passwrd,iaf
YOUR PASSWORD WILL BE EXPIRED YY/MM/DD
JSN: AEYT, NAMIAF
READY.
The second line of the login sequence gives the original copyright date of NOS software and
the copyright date of your version of NOS. The third line gives the current date and time,
and the name of your terminal.
After the system validates your user name and password, it assigns your job a job sequence
name (JSN). The JSN in this example is AEYT.
If you have recoverable jobs in the system, the system initiates a recovery dialogue with
you immediately after it logs you in.
["note]
Using a network to recover a job other than
the one you were using before the job was
disconnected may not always work. For this
reason, we recommend that you always use
the same network to recover a job.
t This manual assumes that your system does not require the entry of a personal identifier.
For more information about the personal identifier refer to Volume 2 of the NOS 2
Reference Set.
60459680 H 3-3
![](asset-32.png)
The following example shows a login sequence where you have recoverable jobs.t Again, your
entries appear in lowercase characters.
I WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978, 198X.
YY/MM/DD. HH.MM.SS T01A75
NETWORK OPERATING SYSTEM NOS 2
FAMILY: ,usernam,passwrd,iaf
YOUR PASSWORD WILL BE EXPIRED YY/MM/DD
JSN: ADYE, NAMIAF
RECOVERABLE JOBCS)
JSN UJN STATUS TIMEOUT
AARQ AN2A SUSPENDED 26 MIN.
AASF AN2A SUSPENDED 28 MIN.
ENTER GO TO CONTINUE CURRENT JOB,
RELIST TO LIST RECOVERABLE JOBS,
OR DESIRED JSN: go
READY.
Additionally, some sites may require you to enter charge information during login (refer to
CHARGE command in section 7).
Logout and Application Switching Procedure
When you have finished using IAF, you can either log out or switch to another application.
The logout procedure disconnects you from the host. Application switching ends your session
with IAF but allows you to continue processing under the control of another application
(such as RBF).
To terminate your terminal session, enter one of the following:
GOOD BYE or B YE or LOGO UT
The system responds by printing:
UN=username LOG OFF hh.mm.ss.
JSN=jsn SRU-S s.sss
CHARACTERS=xxxxxKCHS
IAF CONNECT TIME hh.mm.ss.
LOGGED OUT.
This display is followed by additional logout information provided by network software.
t This manual assumes that your system does not require the entry of a personal identifier.
For more information about the personal identifier refer to Volume 2 of the NOS 2
Reference Set.
3-4 60459680 H
![](asset-33.png)
The following is a description of the variable items in the logout display:
jpffiv
Item Description
username User name you entered during login.
hh.mm.ss. The first occurrence of hh.mm.ss. indicates the time of
logout. The second occurrence indicates the length of time
your terminal was connected to IAF.
jsn Your job sequence name.
s.sss A measure of the system resources used while connected to IAF.
x x x x x x x x A c o u n t o f t h e t o t a l n u m b e r o f i n p u t a n d o u t p u t c h a r a c t e r s r e a d
from, or written to, your terminal.
ct The network control character for your terminal. (The network
control character for specific terminal models are listed in
Table J-l.)
had The host availability display (HAD). The HAD appears if you
have enabled it with the HD terminal definition command (refer
to appendix J) or if you are operating in a multihost
environment.
IAF automatically logs out the terminal if no activity has been registered in a site-defined
timeout period (the default is 10 minutes), unless you have a no-timeout terminal status.
Refer to the discussion of the LIMITS command for further information.
When IAF logs out a dial-up terminal to the system, the system automatically disconnects the
terminal after a site-determined period of time (2 minutes is the default). You may wish to
log out without disconnecting the terminal. To log out of the system and reinitialize the
login sequence, enter:
HELLO
LOGIN
IAF logs out the current job, issues the normal logout messages, and then causes the network
to initiate a new login sequence. Any terminal characteristics, such as page width or
terminal class set in the previous job, remain in effect.
/ ^ * v
60459680 H 3-5
![](asset-34.png)
If you wish to leave the IAF application but remain connected to the network and use another
application, you can enter one of the following:
BYE,application
GOODBYE.application
HELLO,application
LOGIN,application
LOGOUT,application
In these commands, the term application means a product that uses the network for terminal
communications. Other applications include TAF, MCS, TVF, PNI, and RBF (refer to the BYE ^p^
command in section 8). Other site-provided applications may also be available. All 1
terminal characteristics in effect under IAF remain in effect under the new application.
After you enter one of the above commands, the system prints the logout message and
disconnects the terminal from IAF. If the site has authorized you to access the
application, the system connects the terminal to the named application. If the named
application is not present or if the site has not granted you access to this application,
the system issues an error message and the prompt:
terminalname - APPLICATION:
where terminalname is the name the network has given your terminal. -^^s
You can again enter the name of an application, or you can enter BYE or LOGOUT to log out or
HELLO or LOGIN to reinitiate the login sequence.
SUBMITTING JOBS TO REMOTE HOSTS
Some sites use multiple host network configurations in which you can log in to a host
mainframe and then submit jobs to other mainframes (remote hosts) in that computer system.
There are various ways in which sites can configure these computer systems, and the means by ""^s
which you submit jobs to a remote host depend on your system configuration, the type of >
remote host, and the nature of the jobs. In all cases, however, you must have special
authorization to submit such jobs (refer to the LIMITS command in section 7).
In general, you can submit a batch job to a remote host by specifying the remote host with
the ST=lid parameter of the Job command or the ROUTE command. If the remote host is a
SCOPE 2 system and the batch job requires interactive input or output, use the HELL07
command. If the remote host is connected through the Queued File Transfer Facility (QTF)
and the batch job has special routing requirements (requirements not provided by ROUTE
parameters), use the MFQUEUE command. If you want to retrieve or change the attributes of
permanent files on such a remote host, you need not submit a complete batch job. You can
use the MFLINK command from a job on your host mainframe.
If you want to connect your interactive terminal to a Virtual Storage Operating System
(operable on a CYBER 200 computer system), select the Interactive Transfer Facility (ITF)
during login or with the BYE, GOODBYE, HELLO, LOGIN, or LOGOUT command.
In a dual-state system, you can submit a batch job from the NOS system to the NOS/VE system
using the ROUTE command. The ROUTE ST=lid parameter routes a NOS file to the NOS/VE batch '*S\
input queue. The file must be written in 6/12-bit display code. /
3-6 60459680 G
![](asset-35.png)
JOB ORIGIN TYPES
When a job enters the system, the system determines the job origin type according to the
means used for job initiation. Its origin identification remains with the job throughout
job processing. The job origin type determines how the job is handled and how it exits from
the system.
The four origin types and their system symbols are as follows (system symbols are described
in section 6):
Origin Type Symbol
System SYO
Interactive IAO
Local batch BCO
Remote batch RBO
System origin jobs originate at the system console, interactive jobs all enter through IAF,
local batch jobs enter through central site batch devices, and remote batch jobs enter
through RBF.
If you are so authorized (refer to the LIMITS command), you can also initiate jobs using the
HELL07, MFQUEUE, LDI, ROUTE, or SUBMIT commands. Depending on how you specify the
parameters of these commands, the resulting jobs can either be local batch or remote batch
in origin type.
JOB SERVICE CLASSES
Every job in the system is assigned a service class. This service class determines the
job's scheduling priority as the job flows through the system. You can make this service
class assignment or you can let the system assign it a default service class based on the
job's origin type and your validation limits (the privileges your site has granted you).
Unless changed by your site, the system has the following 14 service classes:
Service Class
Deadstart
System
Local batch
Remote batch
Interactive
Detached i nter acti ve
Network supervisor
Subsystem
Maintenance
60459680 F
Two-character
Mnemonic
One-character
Mnemonic
ADS
SY
BC
RB
TS
DI
NS
SS
MA
3 - 6 . 1 / 3 - 6 . 2
![](asset-36.png)
![](asset-37.png)
Figure 3-2 summarizes the methods of submitting jobs to remote hosts.
Command/Application Type of Job Being Submitted
Special Host Type/
Connection Type
Job Command
(ST=lid parameter)
ROUTE Command
(ST=lid parameter)
Batch No special
requirements.
HELL07 Command B atch ( wit h inte ra cti ve I/ O) SCOPE 2 system.
MFQUEUE Command Batch (with special routing requirements) RHF (LCN, CDCNET,
or CCP).
ITF A pp lic at ion Interactive VSOS system
(CYBER 200).
MFLINK Command Part of a batch or interactive job
(permanent file manipulations)
RHF (LCN, CDCNET,
or CCP).
Figure 3-2. Submitting Jobs to Remote Hosts
60459680 G 3-6.1
![](asset-38.png)
JOB ORIGIN TYPES
When a job enters the system, the system determines the job origin type according to the
means used for job initiation. Its origin identification remains with the job throughout
job processing. The job origin type determines how the job is handled and how it exits from
the system.
The four origin types and their system symbols are as follows (system symbols are described
in section 6):
Origin Type Symbol
System SYO
Interactive IAO
Local batch BCO
Remote batch RBO
System origin jobs originate at the system console, interactive jobs all enter through IAF,
local batch jobs enter through central site batch devices, and remote batch jobs enter
through RBF.
If you are so authorized (refer to the LIMITS command), you can also initiate jobs using the
HELL07, MFQUEUE, LDI, ROUTE, or SUBMIT commands. Depending on how you specify the
parameters of these commands, the resulting jobs can either be local batch or remote batch
in origin type. >e^%\
JOB SERVICE CLASSES
Every job in the system is assigned a service class. This service class determines the
job's scheduling priority as the job flows through the system. You can make this service
class assignment or you can let the system assign it a default service class based on the
job's origin type and your validation limits (the privileges your site has granted you).
Unless changed by your site, the system has the following 14 service classes:
Service Class
Deadstart
System
Local batch
Remote batch
Interactive
Detached i nter acti ve
Network supervisor
Subsystem
Maintenance
| 3-6.2
Two-character One--character
Mnemonic Mnemonic
A
DS
SY
BC
RB
TS
DI
NS
SS
MA
60459680
,/**«^\
![](asset-39.png)
#R*^
y^V
# ^ N
Two-character One-character
Service Class Mnemonic Mnemonic
Communication task CT C
Installation class 0 10 0
Installation class 1 II 1
Installation class 2 12 2
Installation class 3 13 3
The scheduling priority associated with each service class is site-determined. You can
ascertain how your site has prioritized the service classes you are authorized to use for
each origin type by using the CLASS command. To determine the service class of a job, use
the ENQUIRE command. The system denotes the service class with a one-character mnemonic in
the SC field of the ENQUIRE output.
Your site allows you to use only a subset of the service classes. The LIMITS command shows
you which service classes you can use. Further, your site can restrict the use of certain
service classes to jobs of certain origin types. The CLASS command displays this
information.
You can assign a service class to a job in the following ways:
• Use the CHVAL command to specify default assignments for your jobs according to
origin type. The system uses one of these default assignments if you do not
otherwise make a service class assignment in a job. The LIMITS command shows what
your default service class assignments are for each origin type.
• Use the SC=class or P=priority parameter of the Job command for batch jobs.
• Use the CLASS command to change the service class of your current job.
• Use the SCL=scl parameter of the ROUTE command for jobs to be initiated by that
command.
JOB NAMES
Every job in the system receives a job sequence name (JSN) and a user job name (UJN). This
includes not only your job file, but files you explicitly route for disposal during your
job, such as files routed to a line printer. These job names are the primary job
identifiers for both the system and you. Many system commands use the JSN and UJN as
parameters. You can get a list of the JSN and UJN of all your active jobs by using the
ENQUIRE command.
JOB SEQUENCE NAME (JSN)
The system assigns every job a unique JSN. Each JSN consists of four alphabetic
characters. The banner page of batch output prominently displays the job's JSN: the JSN
appears as the last four characters of the eight characters in block letters (refer to
appendix D for a sample banner page).
60459680 D 3-7
![](asset-3a.png)
,/flSs^V
1**^^
USER JOB NAME (UJN)
The UJN is for your convenience. You can select a meaningful name (a maximum of seven
characters) by which to identify your jobs. For batch jobs, you can set the UJN with the
SETJOB or ROUTE command. If not otherwise specified, the UJN for batch jobs defaults to the
UJN specified on the Job command. For interactive jobs, you can specify the UJN with the
SETJOB command. The UJN for interactive jobs defaults to the user index hash (refer to the
ENQUIRE command).
VALIDATION
In batch jobs, the USER command follows the Job command and is used to identify you as an
authorized user. If you are an authorized user, a set of control values associated with
your user name is used by the system to control all system requests from your job. If you
are not permitted to perform specific functions (such as access nonallocatable devices) and
you attempt to use them, your job will be terminated.
To get a listing of resources at your disposal and of special permissions you possess, enter
the LIMITS command. To change your resource allocation or to get additional permissions,
contact installation personnel.
ACCOUNTING
The unit of accounting for the system is the system resource unit (SRU). The SRU is a
composite value of central processor time, I/O activity, and memory usage. SRU operations
are initiated at the beginning of a job and reinitiated whenever another CHARGE command is
encountered. SRU information includes:
• Central processor time
• Mass storage activity
• Adder activity (fixed charges for some system requests whose resource requirements
are highly variable and beyond your control)
• Magnetic tape activity
• Permanent file activity
• Central memory and extended memory usage
• SRU value
• Matrix Array Processor (MAP) activity
• Application account chargest
This information is written to the job's dayfile at the end of the job or whenever this
job's service class changes. You may request SRU information to be written to your output
file at any time during the job by issuing the ENQUIRE command. The format of SRU
information written in the dayfile is given under Job Completion in this section.
tNot currently supported by the system but reserved for future
3-8 60459680 C
![](asset-3b.png)
0eas,
I
JOB SCHEDULING
When a job enters the system, it is queued for input and waits for the required system
resources to become available or its priority to grow. The job's priority depends on its
service class. The system priorities are system-defined and can be altered only by the
system operator. The scheduling priority of the job is advanced as the job waits. The
priority ages to a system-defined limit. The job scheduler periodically scans the queued
jobs and active jobs to determine whether action is necessary to ensure that the highest
priori ty jobs a re be ing s er viced . T hi s act io n may inc lude rolli ng out lo w pri ority j obs o r
rolling in higher priority jobs. The job scheduler is also activated to analyze the system
status whenever there are changes (for example, when the field length of a job is released,
a job is queued, or a job completes).
Once a job is scheduled for execution, normal command processing begins. The general flow
of the command processing is illustrated in figure 5-1.
JOB CONTROL
While the job is executing, the system exercises the following controls over the job.
FIELD LENGTH CONTROL
The system controls the field length (central memory) assigned to a job, adjusting it
according to the requirements of each job step. CYBER Loader further adjusts the field
length during both program loading and program execution. Memory may be added or removed as
the needs of the program change. Refer to the description of the REDUCE command in the
CYBER Loader Reference Manual. You can further influence the field length assigned to your
job by using the CM parameter of the Job command and the MFL and RFL commands.
The maximum field length for a job (MAXFL) is set at the smallest of the following values.
• The value of the CM parameter of the Job command if specified
• Maximum field length you are authorized to use
• Maximum field length available for user jobs (dependent on machine size)
For any job step, the maximum field length is the smaller of MAXFL or the value you
specified with the MFL command.
The running field length (RFL) is initially set to zero, indicating system control of field
length. The RFL command changes RFL. RFL cannot exceed the current MFL.
To set the initial field length for a job step, the system uses the first value set by one
of the following.
• Predefined initial field length for a system routine or on a global library set
(RFL = special entry point).
•Highest high address (HHA) from EACP loader table (54 table) (refer to the CYBER
Loader Reference Manual).
60459680 C 3-9
![](asset-3c.png)
RFL value, if nonzero.
The smaller of the MFL or the installation-defined default value (release value
50000B).
NOTE
The system automatically assigns a field
length for CM only. To set the initial
field length for a job step in extended
memory, use the RFL command or the MEMORY
macro (refer to Volume 4, Program
Interface).
The following example shows a command record, the MAXFL, MFL, and RFL settings, and the
actual field length (expressed in octal) used to process each command.
Command
JOB,CM60000.
USER,USERABC,1234.
MAXFL
60000
60000
MFL
60000
60000
RFL
0
0
Field
Length
3200
3200
GET,ABSPROG,RELPROG. 60000 60000 2500
Explanation
The CM parameter sets
the MAXFL and MFL
values. The system
sets the field length
as required for pro
cessing the command.
GET command retrieves
copies of an absolute
program and a relocat
able program.
RFL,40000. 60000 60000 2300 The user issues an
RFL command to set
t h e fi e l d l e n g t h f o r
execution of the abso
lute program that
follows.
ABSPROG. 60000 60000 40000
MFL,50000. 60000 600 00 40000
RELPROG. 60000 50000
40000 The absolute program
on file ABSPROG is
executed within a
40000-word field
length.
2300 The user issues an
MFL command to set
the maximum field
length for the follow
ing relocatable load.
50000 If more than a 50000-
word field length is
required, the job
aborts.
3-10 60459680 C
![](asset-3d.png)
INPUT RLE CONTROL
Batch jobs, when initiated, have a file named INPUT (input file type). This file contains
the commands and other input records required for job execution. INPUT is a locked file.
As a result, you may read from it and reposition it, but the system does not allow you to
write on it. If for some special reason you need to write on a file named INPUT, you should
first issue a RETURN(INPUT) command. This command changes the name of the file from INPUT
to INPUT* and leaves it assigned to your job. You may then write on file INPUT. The change
of name caused by the RETURN command applies only if the file has an input file type (refer
to File Types in section 2). /K
For interactive jobs, file INPUT* is present at the beginning of the session and cannot be
returned with a RETURN command. You can create and manipulate a file called INPUT at any
time, although various products, such as the Full Screen Editor, require special processing
in order to handle files named INPUT or OUTPUT as data files.
TIME LIMIT CONTROL
The system sets a default time limit for each job step unless the Job command or the SETTL
command specifies a job step time limit. This time limit is the amount of central processor
time that any one job step is allowed. You cannot increase the limit beyond that for which
you are authorized.
While a job is using the central processor, the CPU time is accumulated and checked against
the time limit for each job step. If the job's origin type is not interactive, the job in
execution terminates or enters exit processing when the time limit is reached. Interactive
jobs are suspended, after which you can increment the time limit and resume execution from
the point of suspension (refer to SETTL Command for an example). In the case of a detached
S^rS™ * the/ys5em susPends or terminates the job according to the parameter values
ot the SETJOB command. You cannot resume jobs suspended in this fashion from the point of
suspension; they enter exit processing.
SRU LIMIT CONTROL
The system sets a limit on the number of system resource units (SRU) that a job step or an
account block can accumulate. An SRU includes central processor time, central memory usage
permanent file activity, and mass storage and tape I/O. An account block is that portion of
a job from one CHARGE command to the end of the job or to another CHARGE command. You may
alter these limits through the SETJSL and SETASL commands or macros; however, you may not
set either limit beyond that for which you are validated.
While a job is in the system, SRUs are accumulated and checked against the SRU step and
account block limits. If either limit is reached, the system treats the job as if it
exceeded its time limit for a job step, which is described in the preceding subsection.
COMMAND LIMIT CONTROL
The system sets a limit on the number of commands you can enter in a job. You can ascertain
this limit by entering the LIMITS command. If your job exceeds this limit, the system so
informs you and allows you seven additional commands before terminating your job. The
ENQUIRE,U command gives the number of commands you have entered in your job.
60459680 E
![](asset-3e.png)
ROLLOUT CONTROL
Each executing program is allowed to reside in CM for a certain amount of time before
relinquishing its space to another program. When this CM time slice is exceeded, the
program may be rolled out. This means that the contents of the job field length (both CM
and extended memory), the job control area, and the control registers (exchange package) are
written to mass storage. The program remains on mass storage until it is rolled back into
memory. Execution resumes from the point where rollout occurred. The amount of time the
job is allowed to occupy CM is called the central memory time slice. The central memory
time slice is a system parameter that can be changed only by the system operator; time
slices vary for each origin type. Whether a job is rolled out when its time slice expires
depends on several factors.
• Whether there are jobs waiting for execution.
• Whether the jobs that are waiting have a higher priority.
• Whether jobs that are waiting require more field length than would be available if
all jobs of lower priority were rolled out.
When a job is rolled out, it is assigned a priority. The priority assigned is a system
parameter that depends on a job's service class and can be changed only by the system
operator. The job's priority increases while the job waits. Normally, all other factors
being equal, the job with the highest priority is selected to be rolled in.
ERROR CONTROL
When job step activity ceases, the system must determine the next command to process. If
activity ceased due to normal termination, the next command processed is the next command in
sequence. If an error caused activity to cease, the system issues the appropriate dayfile
message and exits from the job.
Errors may be detected by system software or hardware. When the system hardware detects an
error condition, NOS issues two or more dayfile messages. The first message gives the
address where the error was detected; the second and following messages give the types of
errors that occurred. NOS then dumps the exchange package for the job either to OUTPUT, for
local batch and remote batch origin jobs, or to local mass storage file ZZZDUMP, for
interactive jobs (refer to section 14). ZZZDUMP is not rewound before or after the dump.
After issuing the appropriate dayfile message(s) for the error(s), the system searches for
an EXIT command. If an EXIT command is found, processing continues with the command
following EXIT. If an EXIT command is not encountered, the system terminates the job.
(Exit processing is further described in section 5.) If a NOEXIT command is in effect, the
system does not search for an EXIT command on subsequent errors, and processing continues
with the next command.
You can specify the error exit mode on which the system is to abort a job step with the MODE
command. For example, you can specify that address out of range,t operand out of range,
and/or indefinite operand)'errors are allowed and program execution continues (refer to
section 6). The default error exit mode specifies that all errors terminate the job.
The EREXIT, RECOVR, REPRIEVE, and MODE macros control error processing in COMPASS programs..
The SETLOF macro specifies file completion procedures when a job step abort occurs. These
macros are described in Volume 4, Program Interface.
TNot applicable to model 176.
3-12
T*&&!\
60459680 C
![](asset-3f.png)
0^^\
SECURITY FEATURES
A NOS computer system provides extensive protection of information contained in your jobs
and files. Most notably, it protects the central memory associated with your active jobs
and it enforces job and file access controls.
MEMORY PROTECTION
A job cannot dump or directly change the contents of the job field length immediately after
a protected command or a user program. The following is a list of protected commands and a
list of load/dump memory commands:
Protected Commands
APL COPYCF IF or (IFE) PASSWOR SECHDR
APPEND COPYCR LABEL PERMIT SET
ASSIGN COPYEI LDSET PROFILE SETFS
ATTACH COPYSBF LIBEDIT PURGE SKIP
BEGIN COPYX LIBLOAD RECOVER SORT
BLANK DAYFILE LIBTASK REDUCE SUBMIT
CATALOG DEFINE LIMITS REPLACE TCOPY
CATLIST DISPLAY LOAD REQUEST UNLOAD
CHANGE EDIT MAP RESOURC UPROC
CHARGE ELSE MFLINK RESTART USER
CHVAL ENDIF MFQUEUE RETURN VERIFY
CLASS ENDW NEW REVERT VFYLIB
CLEAR ENQUIRE OLD REWIND VSN
COPY EXECUTEt OUT SATISFY WHILE
COPYBF FSE OVWRITE SAVE
COPYBR GET PACKNAM SCOPY
Load/Dump Memory Commands
CKP
DMB
DMD
DMDECS
DMP
DMPECS
LBC
LOC
PBC
RBR
WBR
In an interactive job, you cannot enter a load/dump memory command individually or as the
first command of a procedure. If you attempt to change or dump protected memory, the system
issues an informative message to the dayfile and terminates the job step.
This form of memory protection does not apply if the job is of system origin or if you have
system origin privileges and debug mode has been set at the system console.
SYSTEM AND FILE ACCESS CONTROLS
NOS operates in either secured or unsecured mode, depending on the option selected by your
site. On an unsecured system, the primary control of system access is based on user names
and user passwords. NOS may also require certain users to enter a personal identifier in
addition to their user name and password to gain system access. Additionally certain users
may also be restricted to a single terminal session at a time.
tThis applies to EXECUTE when used as a loader command. It does not apply to EXECUTE when
used to select the execute subsystem in an interactive job.
60459680 G 3-13
![](asset-40.png)
The system further restricts the use of certain system resources (for example, applications
and special commands) to those explicitly granted that privilege by your site. NOS enforces
file access controls based on user names, file passwords, and permissions granted by the
owner of the file. The controls based on file passwords and permissions are discretionary;
they are set at the discretion of the file owner.
In a secured system, NOS enforces an additional set of access controls based on security
access levels and categories. These controls limit access to information based on the
user's validated clearance level and need-to-know categories versus the security access
level and category markings associated with each file. These mandatory controls take
precedence over the discretionary controls, which also remain available.
You must be validated to use one or more security access levels and zero or more security
access categories. Every file on a secured system has a single security access level and
may have one or more access categories associated with it. To access a file, the user job
must be validated for the file's security access level and for all of the file's access ■aS^\
categories.
SECURITY ACCESS LEVELS
A security access level limits the disclosure of sensitive information to persons who are
authorized to access information at the level of sensitivity indicated by that access
level. A secured system supports up to eight security access levels. The number of access
levels to be used, the names of those levels, and the degree of sensitivity associated with
each level are selected by your site. The access levels are ordered so that the most
sensitive information is associated with higher access levels. (The access levels have
numerical values of 0 through 7; the corresponding released default names are LVLO through
LVL7.) You are validated for a set of security access levels (normally a contiguous range
of levels, such as LVLO through LVL4).
The system associates a set of access levels with each job. This set is the intersection of
your validated set of access levels, the range of levels currently valid for the system, the
range of access levels allowed for your job's origin type, and, if specified by the system,
the range of access levels allowed over your communication line to the computer. For
interactive jobs, your job's initial access level is the lowest level in the set of access
levels for your job. For batch jobs, the initial access level is the access level of the
local file that initiated the job.
Example 1: You are validated to use levels LVLO through LVL5, the system is currently
validated for levels LVLO through LVL7, your job origin type has an access level range
of LVL1 through LVL4, and your communication line has an access level range of LVLO
through LVL3. As shown in table 3-1, your job will have an access level set of LVLl
through LVL3 and the job's initial access level will be LVLl. If this job is initiated
via a ROUTE or SUBMIT of a local file with access level LVL2, that will be the job's
initial access level.
3-14 60459680 G
![](asset-41.png)
Table 3-1. User Job Access Levels
LVLO LVLl LVL2 LVL3 LVL4 LVL5 LVL6 LVL7
User
System
Job Origin
Communication
Line
User Job
/SpS^N
Each file has a security access level. Unless you specify otherwise, each file you create
will have the same access level as your job at the time you create the file. You can always
raise the access level of your files (refer to the SETFAL and SETPFAL commands) to any level
for which your job is validated, but you must have special permission to lower the access
level of your files. However, the access level of direct access files or tape files cannot
be changed while they are assigned to your job. If the access level of such a file is lower
than that of your job, you can always read information from the file but can only write
information to it if you have special authorization. The access level of a local file is
automatically raised to the current job access level whenever an operation is performed on
t h e fi l e ( t h i s i n c l u d e s y o u r p r i m a r y fi l e ) .
Your job's access level is automatically raised whenever you read information from a file
that has a higher access level than your job's current access level (within your job's
validated set of access levels). You can always raise your job's access level using the
SETJAL command to any level for which your job is validated, but you must have special
permission to lower the access level of your job.
Example 2: In the job referred to in example 1, you attach a file that has access level
LVL3 and read information from that file. The access level of your job is immediately
raised from LVLl to LVL3.
Example 3: In the same job, you attempt to set your job's access level to LVL5 using
the SETJAL command. This attempt fails because LVL5 is not in your job's validated set
of access levels.
Unless you are specifically validated, a secured system does not allow you to write
information from a file with a higher access level into a file with a lower access level.
Example 4: You attempt to copy a portion of a file whose access level is LVL2 to a file
whose access level is LVL3. A secured system allows this operation.
Example 5: You attempt to copy a portion of a file whose access level is LVL3 to a file
whose access level is LVL2. A secured system does not allow this operation (unless you
possess special validation).
60459680 G 3-15
![](asset-42.png)
On an unsecured system, you may set access levels on your files (for informational purposes),
but the system does not use those levels to restrict access to the files, nor does it
propagate those levels to your job or to other files. No job has an access level on an
unsecured system.
SECURITY ACCESS CATEGORIES
A secured system supports up to 32 security access categories. The number of categories to
be used and the names of those categories are selected by your site. The access categories
have numerical values of 0 through 31; the corresponding released default names are CATOO
through CAT31. Each user is validated for subset of the site-defined access categories.
Your job's access category set is the intersection of this subset and the set of categories
currently valid for the system.
When you create a permanent file (using the SAVE or DEFINE command), the file is automati
cally assigned all of the access categories in your job's access category set. You have the
choice to explicitly assign all, any, or none of these categories to each of your permanent
files (refer to the SETPFAC command). Access categories restrict the access of your
permanent files to those users who are validated for all of the categories you have set for
the files.
Example 6: You are validated for the categories CAT01, CAT06, CAT18, and CAT22. Using
the SETPFAC command, you assign the categories CAT06 and CAT22 to permanent file ABC,
which has an access level of LVL3. You then make file ABC public. Any user in your
family who is validated for access level LVL3 and the categories CAT06 and CAT22 can
then access file ABC.
On an unsecured system, you may assign access categories to your permanent files for
informational purposes, but the system does not use those categories to restrict access to
the files.
RESPONSIBILITIES FOR DATA SECURITY
In a secured system, security access levels and categories are checked whenever a user
accesses a file, begins a job, or attempts to alter the security parameters of a file or
job. This ensures that only those persons who are validated for the access levels and
categories you have assigned to your files can access them. A secured system thus provides
continuous protection of your data.
Although the system will automatically assign an access level and an access category set to
each file you create, you are responsible for ensuring that the access level and access
category set assigned to each of your files is appropriate. Your site should provide
guidelines for the use of the different access levels and categories it has established.
All of the NOS security mechanisms depend on the protection of your user password. NOS
provides the following mechanisms to help protect your password during interactive login:
• You should always use the secure login procedure (described in section 8) to ensure
that you are communicating with the system-supplied login mechanism.
| 3_i6 60459680 G
/^^v
![](asset-43.png)
• If possible, you should set your terminal to full duplex and enable echoplex mode
(refer to the EP terminal definition command). The network temporarily disables
echoplex when you enter your password during login. If you use the abbreviated
login sequence, all fields in the line containing your password will be masked.
This NOS security feature prevents display of your user password at your terminal.
e A warning message stating when your user password is going to expire is displayed at
your terminal and is issued to the job dayfile.
Although NOS encrypts your user password after login, the programs you execute can affect
the security of your files and validation information. When you execute a program, it can
access the command record of your job. It is possible that a program belonging to another
user can obtain privileged information like your user name and charge numbers.
SECURITY CONFLICT PROCESSING
When your job attempts to perform an operation that could violate system security, the
system identifies the operation as a security conflict and issues a SECURITY CONFLICT
message. A security conflict causes the job step to be aborted and decrements your security
count (you are given a specific security count by the site security administrator). If your
security count is decremented to zero, your current job or interactive session is terminated
without EXIT processing. You are not allowed any additional jobs or logins until the
security administrator resets your security count.
f^* On an unsecured system, a security conflict occurs in the following cases:
• An incorrect secondary USER command.
• A job file submitted with a SUBMIT or ROUTE command has an incorrect USER command.
On a secured system, a security conflict arises in the following cases in addition to those
listed above:
• An attempt to set an invalid access level on a file or job.
r e A n a t t e m p t t o a c c e s s o n e o f y o u r p erma n e n t fi l es f r o m a j o b t h at i s n o t v a l i d a ted
for the access level or access category set of the file.
• An attempt to write data on a tape file or an attached direct access file when the
access level of your job is higher than the access level of the file.
• An attempt to set an access level for a file or job which is lower than the current
access level of the file or job.t
JOB COMPLETION
When there is no more activity at a control point, no outstanding central processor
requests, and no commands to process, the job is completed in the following manner.
1. All CM assigned to the job is released.
2. Extended memory assigned to the job is released.
tThis action does not constitute a security conflict if you have special authorization to
do so (refer to the LIMITS command).
60459680 G 3-17
![](asset-44.png)
3. All equipment assigned to the job is released.
4. All library files attached to the job are released.
5. All scratch (local) file space used by the job is released.
6. All direct access permanent files attached to the job are released; the status
information for these files is updated.
7. The following summations of job activity are added to the end of the job dayfile.
This information is also issued to the associated account dayfile for site usage.
o Adder activity in kilounits (incremented by USER commands, CHARGE commands,
and resource assignments).
hh.mm.ss.UEAD, xxxxxx.xxxKUNS.
• Permanent file activity in kilounits:
hh.mm.ss.UEPF, xxxxxx.xxxKUNS.
• Mass storage activity in kilounits:
hh.mm.ss.UEMS, xxxxxx.xxxKUNS.
• Magnetic tape activity in kilounits:
hh.mm.ss.UEMT, xxxxxx.xxxKUNS.
• Accumulated central processor time in seconds:t
hh.mm.ss.UECP, xxxxxx.xxxSECS.
e SRU value in units for total job usage including CPU time, I/O activity, and
memory usage:
hh.mm.ss.AESR, xxxxxx.xxxUNTS.
• Matrix Array Processor (MAP) HI accumulator:
hh.mm.ss.AEMP, xxxxxx.xxxUNTS.
• Application activity:
hh.mm.ss.UEAC, xxxxxx.xxxUNTS.
tIf the installation defines a CPU multiplier value, the value given is the product of the
actual CPU seconds and the multiplier. The installation may assign a different CPU
multiplier value to each CPU within a dual-processor machine (refer to the NOS 2
Administration Handbook).
I 3-18 60459680 G
![](asset-45.png)
8. The following information is printed at the end of files queued for printing.
• Lines printed in kilolines:
hh.mm.ss.UCLP, mi,es, xxxxxx.xxxKLNS.
or
hh.mm.ss.UCLV, mi,es, xxxxxx.xxxKLNS.
mi Machine identifier.
es Equipment status table (EST) ordinal of the output device.
^^ The UCLV summation is issued if the V carriage control character was used
0^ (refer to appendix H).
9. The following information is issued to the account dayfile only.
• Cards punched in kilocards:
hh.mm.ss.jsn. UCPC, mi,es, xxxxxx.xxxKCDS.
10. For batch jobs, the job dayfile is copied to the end of file OUTPUT. If OUTPUT does
not exist or if it is a deferred routed file with EC=A9 specified, the dayfile is
copied to another file that the system queues for printing.
11. All deferred routed files are queued for disposal. The files named OUTPUT, PUNCH,
PUNCHB, and P8 are also queued for disposal in batch jobs. The system does not
automatically queue files OUTPUT, PUNCH, PUNCHB, and P8 in interactive jobs.t
tThis step is done only if job output is to be queued. You can prevent the queueing of job
output by specifying the appropriate parameter on the SETJOB, ROUTE, SUBMIT, or LDI
command•
60459680 G 3"19
![](asset-46.png)
![](asset-47.png)
0X*\
0^*\
r*
PROCEDURES
A NOS procedure is a sequence of NOS commands, residing in a separate record or file, that
performs a specific task or sequence of tasks. A procedure header directive identifies the
file as a procedure file, and a number of other procedure directives allow you to control
additional procedure processing options.
Once you have created a procedure and stored it in a permanent file, the procedure is
available to you at any future time. To execute the procedure, you must call the procedure
using an appropriate form of the BEGIN command, which we describe later in this section.
Procedures that you create yourself can be called from a local file, a permanent file
(direct or indirect access), or from a local or global library set. Your site may also
provide procedures of general use that you can call from system libraries or from user name
LIBRARY. A procedure can be called from another procedure up to a maximum of 50 nested
procedures.
A procedure called from a batch job functions much like a program subroutine. You can pass
parameters to the procedure on the procedure call (BEGIN command). The procedure accepts
any data passed to it, performs its processing functions, and returns control to the calling
job or procedure.
When called from an interactive job, a NOS procedure functions like a user-defined system
command. Once you have made the procedure file local to your job, you can execute the
procedure simply by entering the procedure or file name, followed by any parameters you may
have defined for the procedure.
Although NOS supports both interactive and noninteractive procedure formats (noninteractlve
procedures are also called passive procedures), any NOS procedure can be called from either
a batch or interactive job. The interactive procedure formats described in this section
differ from th e no ninte rac tive fo rmat (d escribed in App endix L) in t hat the inte ractive
formats provide the end user with various types of interactive help and parameter prompts.
The major features of NOS interactive parameter formats are:
Two Interactive Formats
As the procedure writer, you can choose between the parameter-prompting (*I) or the menu
(*M) interactive formats. The parameter-prompting format prompts the user to enter
required parameter values. The menu format displays a list of possible parameter values
and prompts the user to select one of the values by number.
Procedure Prompting
If the user fails to enter a required parameter value, or enters an invalid value, the
system prompts the user to enter a correct value.
60459680 D 4-i
![](asset-48.png)
Interactive Help
Both interactive formats give the user easy access to system-generated, as well as
procedure-defined help for a procedure and its parameters.
Parameter Validation
The interactive formats provide an easy way of defining the types of parameter values
that can be entered for any particular parameter. The system will not execute an
interactive procedure until the user has entered a valid value for each required
parameter.
PROCEDURE FILE RESIDENCE AND SEARCH ORDER
A procedure is stored as a separate record on a file. Several procedures, or a collection
of procedures and programs, can exist on the same file. Procedures can be stored on local
files, indirect access or direct access permanent files, system libraries, or user name
LIBRARY. Procedures can also reside on magnetic tape as well as mass storage.
The procedure search order is dependent on the form of the BEGIN command used to call the
procedure. For more information on the search order, refer to the BEGIN command description
i n t his s ec t ion .
PROCEDURE STRUCTURE
A procedure file can be divided into five sections, as shown by the example in Figure 4-1.
The first four sections comprise the procedure itself (the procedure begins with the
procedure header (.PROC) directive and ends with a REVERT command at the end of the command
section). The fifth (Data) section may contain programs, procedures, or other data to be
referenced by the procedure.
The first line or lines of a procedure is the procedure header, which consists of a single "ca^\
procedure header (.PROC) directive. The procedure header names the procedure, indicates .'
whether the system will prompt for required parameter values, defines what the prompts will
consist of, and defines any restrictions on the types of values that can be entered for each
parameter. The .PROC directive and all other procedure directives are listed in summary
form in Table 4-1 and are described in detail under Procedure Directives in this section.
Procedure directives are identified by the period (.) before the directive name.
The formatting section contains directives which alter the default text and format of user
prompts. This section of the procedure body is optional, as the system does provide default
text and format for all prompts. If you do specify directives in this section, the
formatting directives must immediately follow the procedure header directive.
The help section contains directives and text which define the help to be provided for
procedure parameters and for the procedure itself. This section of the procedure is
optional, as the system can generate help from the information in the procedure header. If
you do specify any directives in this section, you must include a .ENDHELP directive to end
the section.
4-2 60459680 D
![](asset-49.png)
,PROC,TESTPN*I
,PN"Enter project number"=
(*S10(ABCDEFGHIJ KLMN0PQRSTUVWXYZ$/$1234567890)).
.NOCLR,Executing - Please wait.
.HELP
TESTPN requests that you enter a valid
project number for this application.
.HELP,PN
Enter a project number
(Maximum of 10 characters)
.ENDHELP.
.IF,$PN$.NE.$PRJ/2201$,LABEL1.
NOTE./INVALID PROJECT NUMBER/
REVERT,N0LIST.
.ENDIF,LABEL1.
RETURN,LISTFIL,LGO.
FTN5,I-APPL,L=LISTFIL,B=LG0.
LGO.
REVERT,NOLIST.
EXIT.
REVERT,ABORT.TESTPN
.DATA,APPL.
PROGRAM APPL
PRINT*,'APPL COMPLETE'
END
Procedure Header
Formatting Section
Help Section
Command Section
Data Section
Figure 4-1. Procedure File Structure
yf^*N
The command section consists of procedure directives and system commands you want to be
executed. Most system commands are allowed within a procedure. The exceptions are
prim ari ly the co mma nds restricted t o entry f rom interactive ter min als (refer to section 8 ).
The data section consists of information you want written to a local file or files so that
you can reference it while the procedure executes. You can also reference the data section
in the procedure header. A separate .DATA directive identifies each local file to be
created.
PROCEDURE PROCESSING
The system performs interactive procedure processing in three stages:
• Interactive parameter entry
• Procedure expansion
• Execution of the command record
60459680 H 4-3
![](asset-4a.png)
INTERACTIVE PARAMETER ENTRY
During interactive parameter entry, the system processes the procedure header directive and
all directives in the formatting and help sections.
The system prompts the user for all required parameter values as specified in the procedure
header. Each value the user enters is verified against the validation requirements
specified in the procedure header. If any value fails to meet the validation requirements
the system prompts the user to enter a corrected value.
The correction prompt and other interactive prompts can be modified by directives in the
formatting section.
If the user requests help for the procedure or for a parameter (by entering a ? following
the procedure call or following a parameter prompt), the system displays the applicable /r*^K
system default help text, if any, followed by procedure-defined help text. ]
The interactive parameter entry portion of procedure processing is completed when the user
enters a carriage return after having correctly entered all required parameter values. If
the user correctly enters all required values on the procedure call, no formatting or help
directives (except .NOTE and .NOCLR) are processed, and procedure expansion begins
immediately.
PROCEDURE EXPANSION
Procedure expansion is performed only on the procedure command and data sections. During
procedure expansion, the system:
• Processes all directives in the command and data section.
• Substitutes parameter values specified by the user, or by the .PROC directive, for
each occurrence of the corresponding parameter keyword in the command and data
sections.
• Creates a scratch file, called the procedure command record, which contains the NOS
commands from the procedure command section as modified by directive processing and
parameter substitution.
•Creates a separate local file for each .DATA directive processed during expansion of
the procedure.
At completion of expansion processing, the calling user's job has assigned to it a scratch
file (the procedure command record), containing NOS commands ready to be executed, and a
local file for each .DATA file referenced in the command record.
The procedure command record created during expansion processing is simply the sequence of
NOS commands to be executed. Although procedure directives are used to define and create
the command record, directives themselves do not appear in the command record since they are
not executable system commands.
The procedure command record may not include all system commands from the procedure command
section. This is determined by processing of the .IF, .ELSE, and .ENDIF directives. The
.IF directive functions similarly to the IF command. In the same way that the IF command
determines whether the following sequence of commands will be executed, the .IF directive
determines whether the following sequence of commands is written to the procedure command
record. In other words, if the expression in the .IF directive is true, the commands placed
between .IF and .ELSE or .ENDIF are written to the command record; if the expression is
4-4 60459680 H
![](asset-4b.png)
false, these same commands are not written to the command record. To see the results of the
.IF directive, look at figures 4-2 and 4-3. These figures show the command records
resulting from valid and invalid entries for the procedure in figure 4-1.
Note that at the end of processing in either figure 4-2 or 4-3, a listing of the user's
local jobs would show a file called APPL. This file is created as a result of the .DATA
directive in procedure TESTPN from figure 4-1.
/0^^\
Procedure Command record:
RETURN,LISTFIL,LG0.
FTN5,I=APPL,L=LISTFIL,B=LG0.
LGO.
REVERT,N0LIST.
Dayfile:
testpn,prj/2201
APPL COMPLETE
/dayfi Le,fr=testpn,op=m
10.18.53.TESTPN,PRJ/2201.
10.18.54.RETURN,LISTFIL,LG0.
10.18.55.FTN5,I=APPL,L=LISTFIL,B=LG0.
10.18.55. 62700 CM STORAGE USED.
10.18.55. 0.009 CP SECONDS COMPILATION TIME.
10.18.55.LGO.
10.18.56. END APPL
10.18.56. 14300 MAXIMUM EXECUTION FL.
10.18.56. 0.007 CP SECONDS EXECUTION TIME.
10.19.21.DAYFILE,FR=TESTPN,0P=M
USER DAYFILE PROCESSED.
/
Figure 4-2. TESTPN with Valid Entry
Procedure Command record:
NOTE./INVALID PROJECT NUMBER/
REVERT,N0LIST.
Dayfi Le:
testpn,888
INVALID PROJECT NUMBER
/dayfi Le,fr=testpn,op=m
10.19.51.TESTPN,888.
10.19.51.NOTE./INVALID PROJECT NUMBER/
10.20.03.DAY FILE,FR=TESTPN,0P=M
USER DAYFILE PROCESSED.
/
Figure 4-3. TESTPN with Invalid Entry
60459680 E 4-5
![](asset-4c.png)
Following are some tools you can use to further control procedure expansion:
• .EXPAND Directive
• Inhibit Character
• Concatenation Character
• .EX Directive
.EXPAND Directive
The .EXPAND directive allows you to suspend expansion processing for one or more lines of a
procedure. Inserting a .EXPAND,OFF directive suspends directive processing and parameter ^^
substitution for subsequent lines of the procedure until the end of the procedure or until a )
.EXPAND,ON directive appears.
An especially useful application of the .EXPAND directive is to inhibit expansion of a
procedure in a .DATA file. Normally, calling a procedure file initiates expansion of the
entire file, including the data section. However, if the data section contains another
procedure file, you may not want the .DATA file to be expanded until it is called by a BEGIN
command. Inserting a .EXPAND,OFF directive before the .DATA directive prevents the creation
of the .DATA file. Inserting a .EXPAND,OFF directive immediately after the .DATA directive
causes the .DATA file to remain unchanged by expansion of the original procedure.
Inhibit Character
Like the EXPAND directive, the inhibit character also inhibits parameter substitution or
directive processing during procedure expansion. In general, the scope of the inhibit
character is more limited than that of the EXPAND directive. The default inhibit character
is xi (or = if you are using a CDC graphic character set). You can define a different
inhibit character using the .IC directive.
Usage rules for the inhibit character are:
• The inhibit character placed before a parameter keyword in the command or data
section inhibits substitution of that keyword.
• The inhibit character placed before a procedure directive (including a .DATA
directive) in the command or data section inhibits expansion processing of that
directive.
4_6 60459680 G
![](asset-4d.png)
i^SN
The inhibit character placed before a concatenation character InhibLts processing of
the concatenation operatLon; the concatenation character remains Intact. In this
case, the inhibit character does not prevent parameter substitution of a keyword
following the concatenation character.
Expansion processing strips all Inhibit characters from the procedure command record
with two exceptions:
those appearing in a $-dellralted literal string.
those appearing In a sequence of two or more Inhibit characters. When they
appear in sequence, only the first Inhibit character is omitted from the
procedure command record.
The inhibit character Is often used to allow use of the same character string for both a
parameter keyword and value. For example, If an Input file parameter Is written as #1=1,
procedure expansion will remove the #, leave the first I Intact, and perform normal
substitution on the second I.
If a keyword or directive is subject to expansion processing more than once, you can control
when it will be processed by inserting one or more inhibit characters before the keyword or
directive. In the following example, expansion of procedure PR0C1 creates one local file
caLled DATA1 and strips the # from the second .DATA directive. Since the # character is no
longer present when PR0C2 is executed, PR0C2 expansion creates local file DATA2.
-PR0C,PR0C1*I.
REVERT.
.DATA,DATA1.
.PR0C,PR0C2*I.
REVERT.
#.DATA,DATA2
Following is an example of inhibit character usage.
In this example, procedure INHIBIT resides on file PROCFIL.
.PROC,INHIBIT*I,I=(*N=TEST).
GET,I.
FTN5,#I=I,L=0
LGO.
COMMENT. I, Ul, Ul, UUU
60459680 D 4-7
![](asset-4e.png)
If procedure INHIBIT is called by the command:
begin,inhibit
The resulting dayfile segment is:
10.31.00.BEGIN,INHIBIT.
10.31.00.GET,TEST.
10.31.OO.FTN5,I=TEST,L=0
10.31.00. 56000 CM STORAGE USED.
10.31.00. 0.011 CP SECONDS COMPILATION TIME.
10.31.00.LGO.
1 0 . 3 1 . 0 1 . S T O P
1 0. 3 1. 0 1. 5 60 0 F I NA L E X EC U TI O N F L.
10.31.01 0.000 CP SECONDS EXECUTION TIME.
10.31.01. COMMENT. TEST, I, TESTI, II. "^
10.31.01.SREVERT.CCL '
Concatenation Character
The concatenation character allows parameter substitution for a substring of a character
string. The default concatenation character is _ (or r-*" if you are using a CDC graphic
char ac ter s et) .
Usage rules for the concatenation character are: >*s«^k
• Expansion processing removes all concatenation characters from the procedure file
except those included in a $-deliraited literal string and those preceded by a #
character.
• After removal of a concatenation character, the preceding and following character
strings are concatenated by shifting the remainder of the line one character to the
left. For example, if PROG is a parameter keyword for which the user enters a value
of NEW, the string PR0G_B becomes NEWB after expansion processing.
Following is an example of concatenation character usage.
Procedure LINK resides on file FILE1.
.PR0C,LINK*I,SUFFIX"F0R C0PY"=(*N=,BF,BR,CF,CR,EI,SBF,X),LFN1=(*F),LFN2=(*F).
REWIND,LFN1.
C0PY_SUFFIX,LFN1,LFN2.
In the following example, the first BEGIN command does a COPYSBF of file PLAN to file
SCHEME. The next BEGIN command does a C0PYEI of file MAZE to file TAXES. Each resulting
dayfile follows the BEGIN command.
begin,link,filel,suffix=sbf,lfnl=plan,lfn2=scheme.
08.00.17.$BEGIN,LINK,FILE1,SUFFIX=SBF,LFN1=PLAN,LFN2=SCHEME.
08.00.18.REWIND,PLAN.
08.00.18.C0PYSBF,PLAN,SCHEME.
08.00.18. EOI ENCOUNTERED.
08.00.18.$REVERT.CCL
4-8 60459680 G
![](asset-4f.png)
jst^\.
begin,link,filel,suffix=ei,lfnl=maze,Ifn2=taxes.
08.03.23.$BEGIN,LINK,FILE1,SUFFIX=EI,LFN1=MAZE,LFN2=TAXES.
08.03.23.REWIND,MAZE.
08.03.24.C0PYEI,MAZE,TAXES.
08.03.24. EOI ENCOUNTERED.
08.03.24.SREVERT.CCL
.EX Directive
The .EX directive immediately terminates expansion processing and executes the command
included in the directive. No further expansion processing is performed, and the procedure
command record is not executed.
The most common use of .EX is to initiate immediate processing of a menu procedure option as
shown in the following example:
.PR0C,APR0C*M
,PARM=
(1-0PT1",
2"0PT2",
3"0PT3").
.EX.BEGIN,PARM,LIBFILE.
EXECUTION OF THE COMMAND RECORD
At completion of expansion processing, the system increments the procedure nesting level
count and begins execution of the procedure command record.
When all commands in the procedure command record have been processed, the system executes a
system- or user-supplied REVERT command, decrements the procedure nesting count, and returns
control to the calling job or procedure.
PROCEDURE DIRECTIVES
Procedure directives have these general syntax features:
• They all have a period as a prefix character.
• You can use a comma or an opening parenthesis as a separator within directives.
• You can use a period or a closing parenthesis as a terminator. You must use a
period or closing parenthesis as a terminator if you append comments to the
directive.
• A procedure directive can span more than one line. No line can contain more than
150 6-bit characterst and each line to be continued must either end with a nonblank
separator or the succeeding line must begin with a nonblank separator.
• Unless otherwise stated, the system reads the characters you enter in directives as
6-bit display code (uppercase characters only). You can enter the text for help
information and prompts in uppercase and lowercase characters (6/12-bit display
code).
tThis value can be changed during installation.
60459680 F 4-9
![](asset-50.png)
/*5fi&»i
The detailed descriptions of the procedure directives later in this section include any
exceptions to the general syntax features just cited.
Procedure directives can be grouped by function into six basic types. The directives are
listed by type in table 4-1.
Table 4-1. Procedure Directives
Directive Type Directive Function
Procedure header .PROC Specifies the procedure name, defines parameters, and
enables parameter prompting.
Formatting .CORRECT Specifies the prompt to follow an incorrect parameter
entry.
.ENTER Specifies the prompt to appear before a parameter entry
is made.
.Fn Specifies a label for programmable function key Fn.
.NOCLR Inhibits the automatic clearing of the screen while the
procedure executes.
.NOTE Specifies a message to appear on the screen while the
procedure executes.
.PAGE Specifies the string to precede the page number on the
screen.
.PROMPT Specifies the text for the general request for input.
Help .ENDHELP Marks the end of the help section of the procedure.
.HELP Specifies help text for the procedure or a parameter.
Expansion .CC Specifies the concatenation character to be used in the
Control procedure body.
.ELSE Terminates skipping initiated by a matching .IF or
initiates skipping until a matching .ENDIF is found.
.ENDIF Terminates skipping initiated by a matching .IF or
.ELSE.
.EX Submits a single command to the system for immediate
execution.
.EXPAND Terminates or restores procedure expansion for
subsequent lines of the procedure.
.IF Allows conditional expansion of the procedure body.
.IC Specifies the inhibit character to be used in the
procedure body.
F i l e .DATA Cre ate s a loca l file .
.EOF Inserts an end-of-file mark in a (.DATA) file created
by the procedure or in the procedure command record.
.EOR Inserts an end-of-record mark in a (.DATA) file created
by the procedure or in the procedure command record.
Comment .* Identifies comments in the procedure.
4-10 60459680 F
![](asset-51.png)
PROCEDURE HEADER (.PROC) Directive
Every procedure begins with a procedure header (.PROC) directive. The .PROC directive names
the procedure, controls parameter prompting, and defines any restrictions on values that can
be entered for the parameters.
The .PROC directive must be the first line of the procedure and must begin in column 1. It
can be continued on one or more succeeding lines by ending the continued line, or beginning
the continuation line, with a non-blank separator character. The .PROC directive must end
with a pe ri od (. ).
In this section we describe the interactive and menu formats of the .PROC directive,
noninteractive format is described in Appendix L. The
Interactive Format
/jP^N
This directive enables the interactive processing of a procedure call (refer to Requesting
Help on Procedure Calls later in this section). The directive:
• Designates procedure parameters as optional or required.
• Designates permissible values and correct syntax for each parameter through a
checklist.
• Supplies descriptions for each parameter to be used in prompting the procedure
caller.
Format:
.PROC,pname*I"title",pi,p2,...,pn.ck.
Parameter Description
pname
t i t l e
Specifies the procedure name; pname can be one to seven alphanumeric
characters. The procedure name should begin with an alphabetic
character. You must append *I to the procedure name to enable
parameter prompting.
Specifies the procedure title. The system assumes that your title is
in 6/12-bit display code, which supports uppercase and lowercase
characters. The title string can be a maximum of 40 lowercase
(12-bit) characters, 80 uppercase (6-bit) characters, or any
combination of lowercase and uppercase characters that does not exceed
480 bits. The title field can be null ("") or omitted. If omitted,
the default title used in the screen mode parameter display is the
procedure name pname.
The system displays the title whenever the procedure is called and
required parameters are not supplied.
60459680 E 4-11
![](asset-52.png)
Parameter Description
Pi Specifies optional parameters. The maximum number of parameters is
50. Each parameter p^^ has the following form:
keywrd"descriptionl,=( checklist)
or
keywrd'description'=(checklist)
keywrd Specifies the keyword of the parameter, keywrd
can be a string of 1 to 10 alphanumeric
characters. The occurrences of keywrd in the
procedure body are replaced by a value that
conforms to the specifications made in the
check li st . Th is va lue i s s pe ci fie d b y a
parameter on the procedure call or by default
according to checklist specifications.t
If keywrd is surrounded by dollar symbols
($keywrd$), any dollar symbols which surround or
are contained within the parameter value will be
retained as a part of the value. Note that when
the user is prompted for the value in screen
mode, the value entered will be treated as a
literal value even if it is not surrounded by
dollar symbols.
description Specifies an optional text string that the system
displays when prompting for a parameter. The
title string can be a maximum of 40 lowercase
(12-bit) characters, 80 uppercase (6-bit)
characters, or any combination of lowercase and
uppercase characters that does not exceed 480
bits. In screen mode, the system will display a
maximum of 40 characters. The description field
may be null or omitted.
You must enclose the text string in quotation
marks or apostrophes. If you use quotation
marks, the default prompt for the parameter p^
has the following format:
Enter keywrd description?
If you use apostrophes, the system uses only your
description string in the prompt:
description?
Two examples which show these prompting formats
appear under the description of the .HELP
directive.
t There is a seven-character restriction on the length of the keyword if the name call
format of the BEGIN command is to be used, the keyword is to be specified on the call, or
the procedure is a local file.
4-12 60459680 H
![](asset-53.png)
Parameter Description
checklist Specifies a list of the acceptable values and
syntax for p±. The checklist must be enclosed
in parentheses. The value specified for a
parameter in a procedure call is compared to each
of the entries in the checklist in left to right
order and a match must occur for a value to be
acceptable. If more than one match occurs, the
first match determines the substitution.
If the checklist is omitted, the system assumes
that any uppercase 1- to 40-character value is
valid. The detailed description of acceptable
checklist entries is in the following paragraphs.
ck Specifies a 1-to 10-character comment keyword. The keyword must be
immediately preceded and followed by periods with no intervening
spaces. This is an optional parameter. The system substitutes
comments specified on the procedure call for the comment keyword in
the procedure body. The system substitutes a null value for the
comment keyword if no comments are on the procedure call. If you do
not specify a comment keyword, the system ignores comments made on the
procedure call.
Note that the system treats the comment keyword ck as a contiguous
string upon substitution. If ck is concatenated to another long
string in the procedure body, this substitution could produce a line
that exceeds the line length limit (150 6-bit characters).
A comma must separate .PROC and the procedure name. The separator between the procedure
name and the procedure parameters can be a comma, reverse slant (\), or slant (/). Reverse
slants and slants have special significance as described under Parameter Matching Modes
later in this section.
CHECKUST ENTRIES
Entries in the parameter checklist are of three types: simple values, equivalenced values,
and checklist patterns. A single checklist can contain any combination of entry types and
multiple entries of the same type.
A simple value is an entry of the form:
p s t r i n g
where pstring is any 1- to 40-character string. If pstring contains nonalphanumeric
characters other than asterisks (*), it must be enclosed in literal delimiters ($). |
A simple value specifies that if the user enters a value of pstring on the BEGIN command,
pstring is substituted for the parameter keyword in the procedure body.
60459680 H 4-13
![](asset-54.png)
An equivalenced value is an entry of the form:
pstring=pvalue
where pstring and pvalue are 1- to 40-character strings. If either pstring or
pvalue contains nonalphanumeric characters other than asterisks (*), it must be
enclosed in literal delimiters ($).
An equivalenced value specifies that if the user enters a value of pstring on the BEGIN
command, pvalue is substituted for the parameter keyword in the procedure body.
There are five checklist patterns that can be used in the checklist. Each pattern defines a
set of restrictions to be placed on values entered by the user. The five checklist patterns
are summarized in figure 4-4 and are described in detail on the following pages.
Each checklist pattern has three forms:
*p=
*p=pvalue
where p is a character identifying the checklist pattern and pvalue is any 1- to
40-character string. If pvalue contains nonalphanumeric characters other than
asterisks (*), it must be enclosed in literal delimiters ($).
The *p form specifies that a parameter value entered by the user will be substituted for the
parameter keyword if the value meets the requirements defined by *p.
The *p= form specifies that a null substitution will occur if the value entered by the user
meets *p requirements. In other words, all occurrences of the parameter keyword will be
omitted from the procedure command record.
The *p=pvalue form specifies that pvalue is to be substituted for the parameter keyword if
the value entered by the user meets the requirements of the *p pattern.
Special Values
There are three special values which can be specified in an equivalenced value entry in a
*p=pvalue checklist pattern. These special values are:
Special Value
#DATA
#FILE
//PRIMARY
Significance
Specifies the name of the local file created by an unlabeled .DATA
directive (that is, a .DATA directive on which the lfn parameter was
omitted). Note that there can be no more than one unlabeled .DATA
directive in a procedure. The actual file name used will be ZZCCLAA,
ZZCCLAB, ZZCCLAC, or so on depending on the nesting level of the
procedure.
Specifies the file containing this procedure.
Specifies the primary file.
4-14 60459680 H
![](asset-55.png)
Checklist Pattern
*Am..nt
*Am..n= t
*Am..n=valuet
*Fm..nt
*Fm..n=t
*Fm..n=valuet
*K
*K=
*K=value
*N or *D
*N= or *D
*N=value
or
*D=value
*Sm..n(chars)t
or
*Sm..n/kt
*Sm..n(chars )=t
or
Description
Allows entry of any character string up to 40 characters. The
string replaces keyword.
Entry of ch aracter str in g cau ses a nul l sub stituti on .
Entry of character string replaces keyword with value.
Allows entry of a valid NOS file name. The file name replaces
keyword.
Entry of a file name causes a null substitution.
Entry of a file name replaces keyword with value.
Allows the keyword to be entered as a value. No substitution
results.
Entry of the keyword causes a null substitution.
Entry of the keyword replaces keyword with value.
Specifies that the parameter is optional. No substitution
results.
Specifies that omission of the parameter causes null
substitution.
Specifies a default value for the parameter. Omission of
parameter replaces keyword with value.
Allows entry of any characters selected from chars or from the
set represented by k. The characters selected replace
keyword, chars defines all allowable alphanumeric or special
characters, k can be any of the following mnemonic
abbreviations:
A A n y a l p h a b e t i c c h a r a c t e r s
B Any octal characters
D Any decimal characters
AB Any alphabetic and octal characters
AD Any alphabetic and decimal characters
To include an asterisk (*) as a member of the set, append an
asterisk to the mnemonic. For example, D* specifies any
decimal character and * as allowable characters.
Entry of allowable characters causes a null substitution.
*Sm..n/k=t
*Sm..n(chars)=valuet Entry of allowable characters replaces keyword with value.
or
*Sm..n/k=value
pstring
pstring=
pstring=pvalue
Entry of string pstring replaces keyword with pstring.
Entry of string pstring causes a null substitution
Entry of string pstring causes pvalue to replace
keyword.
t The specification m..n is optional and defines the minimum and maximum length of the
character string or file name that can be entered for the parameter value. Valid ranges
are 0 to 40 for *A, 1 to 7 for *F, and 1 to 40 for *S. If only a single length value is
specified, it is assumed to be the maximum; for example, *A10 allows entry of any string
from 0 to 10 characters long.
Figure 4-4. Summary of Checklist Entries
60459680 H 4-15
![](asset-56.png)
Checklist Patterns
Checklist Pattern
*Am..n=value
*Am..n=
*Am..n
*Fm..n=value
*Fm..n=
*Fm..n
Description
Specifies the substitution for keywrd regardless of the specifica
tions for p± on the procedure call. m..n specifies the minimum
and maximum values for the length of the entry on the procedure
call. The default value for m is 0 and for n is 40. The maximum
value for n is 40. If *Am..n=value is in the checklist, value
replaces keywrd in the procedure body regardless of what is
specified on the procedure call.
You can specify any string of 0 to 40 uppercase characters for
value. You must delimit special characters, other than asterisks
(*), with dollar signs.
If value is //DATA, all occurrences of keywrd in the procedure body
are replaced by the name of the data file created by the .DATA
directive (refer to .DATA Directive for the name of this file). If
value is //FILE, all occurrences of keywrd in the procedure body are
replaced by the name of the file that contains the procedure. Any
data read from this file begins with the record immediately
following the record that houses the procedure. If the procedure
resides on a library and is called by a name call form of the BEGIN
command, keywrd is replaced by a null value. If value is //PRIMARY,
all occurrences of keywrd in the procedure body are replaced by the
current primary file.
If * Am .. n= is in t he che cklis t, a nu ll val ue re place s keywr d. If
*Am..n is specified, whatever is specified on the procedure call
replaces keywrd.
If you specify some form of the *A entry more than once in a single
checklist, the system uses the leftmost entry.
Example:
.PR0C,EB0C*I,P1=(*A5),P2=(*A10..15),P3=(*A20..) .
In this procedure header directive, PI allows entry of a character
string 0 to 5 characters long, P2 allows a string 10 to 15
characters long, and P3 allows a string 20 to 40 characters long.
Specifies that the parameter entry for p£ on the procedure call be
a file name that conforms to the operating system format for a local
file name. m..n specifies the minimum and maximum length of the
file name. The default value for m is 1 and for n is 7. If
*Fm..n=value is in the checklist, value replaces keywrd in the
procedure body when a file name is specified on the procedure
call. You can specify any 0- to 40-character string for value.
You must delimit special characters, other than asterisks (*), with
dollar signs.
4-16 60459680 H
![](asset-57.png)
/ffSN.
Checklist Pattern Description
If value is //DATA, all occurrences of keywrd in the procedure body
are replaced by the name of the data file created by the .DATA
directive (refer to .DATA Directive for the name of this file). If
value is //FILE, all occurrences of keywrd in the procedure body are
replaced by the name of the file that contains the procedure. Any
data read from this file begins with the record immediately
following the record that houses the procedure. If the procedure
resides on a library and is called by a name call form of the BEGIN
command, keywrd is replaced by a null value. If value is //PRIMARY,
all occurrences of keywrd in the procedure body are replaced by the
current primary file.
If *F m.. n= i s in th e ch eck list , a n ull va lue rep la ces ke ywrd . If
*Fm..n is specified, the file name specified on the procedure call
replaces keywrd.
If you specify some form of the *F entry more than once in a single
checklist, the system uses the leftmost entry.
Example:
Procedure EXEC is on local file EXEC:
.PR0C,EXEC*I,I=(*F4..7),B=(*N=LG0,*F),
L=(*F=0UTPUT).
FTN5,#I=I,#B=B,#L=L.
*K=value
*K=
*K
EXEC is called:
EXEC,I=CARDS,L=PRINT.
The procedure body becomes:
FTN5,I=CARDS,B=LG0,L=0UTPUT.
Specifies the substitution for keywrd when the parameter entry for
pj on the procedure call is only the keyword keywrd or if the
keyword is entered in response to an interactive prompt. If
*K=value is in the checklist, value replaces keywrd in the
procedure body. You can specify any string of 0 to 40 uppercase
characters for value. You must delimit special characters, other
th an as te ri sk s ( *) , wi th dol la r si gn s.
If value is //DATA, all occurrences of keywrd in the procedure body
are replaced by the name of the data file created by the .DATA
directive (refer to .DATA Directive for the name of this file). If
value is //FILE, all occurrences of keywrd in the procedure body are
replaced by the name of the file that contains the procedure. Any
data read from this file begins with the record immediately
following the record that houses the procedure. If the procedure
resides on a library and is called by a name call form of the BEGIN
command, keyword is replaced by a null value. If value is
//PRIMARY, all occurrences of keywrd in the procedure body are
replaced by the current primary file.
/p8?s
60459680 H 4-17
![](asset-58.png)
Checklist Pattern Description
If *K= is in the checklist, a null value replaces keywrd. If *K is
in the checklist, no substitution occurs.
Specifying some form of the *K entry more than once in a single
checklist is an error. However, you can specify another pattern
that is equivalent. Refer to procedures SUBN1 and SUBN2 in the
following examples.
Examples:
Procedure KEY is on local file PROCFIL.
.PROC,KEY*I,P1 = (*K),P2=(*K=X),P3=(*K=0. _.
COMMENT. #P1=P1, #P2=P2, #P3=P3 ^
KEY is called:
BEGIN,KEY„P1,P2,P3.
The procedure body becomes:
COMMENT. P1=P1, P2=X, P3=
The following calls to procedures SUBN1 and SUBN2 illustrate the y=^
left-to-right checking of the checklist and the use of equivalent '=^
patterns. Procedures SUBN1 and SUBN2 are on local files by those
same names and have the following lines, respectively:
.PR0C,SUBN1*I,P1=(*K=KEYW0RD,P1=STRING,*N=DEFAULT).
N0TE.+#P1=P1
.PR0C,SUBN2*I,P1=(*N=DEFAULT,P1=STRING,*K=KEYW0RD).
N0TE.+#P1=P1
Procedure SUBN1 is called:
subn1,p1
The system writes:
P1=KEYW0RD
Procedure SUBN2 is called:
subn2,p1
The system writes:
P1=STRING
^Ssgv
4-18 60459680 F
![](asset-59.png)
/^p^\
Checklist Pattern
*N=value
*N=
*N
*D=value
*D=
*N
Description
A *K checklist pattern applies only when the keyword is entered by
itself, or in response to an interactive prompt. It does not apply
when an equivalenced value matching the keyword is entered as shown
in the following call to procedure SUBN1:
subn1,P1=p1
The system writes:
P1-STRING
Specifies the substitution for keywrd when there is no parameter
e n t ry f o r p ^ o n t h e p r o c e d u re c a l l. I f * N s = v a lue o r * D =va l u e i s |
in the checklist, value replaces keywrd in the procedure body. You
can specify any string of 0 to 40 uppercase characters for value. I
You must delimit special characters, other than asterisks (*), with I
dollar signs. I
If value is #DATA, all occurrences of keywrd in the procedure body
are replaced by the name of the data file created by the .DATA
directive (refer to .DATA Directive for the name of this file). If
value is //FILE, all occurrences of keywrd in the procedure body are
replaced by the name of the file that contains the procedure. Any
data read from this file begins with the record immediately
following the record that houses the procedure. If the procedure
resides on a library and is called by a name call form of the BEGIN
command, keywrd is replaced by a null value. If value is //PRIMARY,
all occurrences of keywrd in the procedure body are replaced by the
current primary file.
If *N= or *D= is in the checklist, a null value replaces keywrd. I
If *N or *D is in the checklist, no substitution occurs. I
I f n o f o r m a t o f t h e * N o r * D e n t r y i s i n t h e c h e c k l i s t , p . i s a |
required parameter and interactive prompting occurs when it is
omitted from the procedure call. Specifying some form of the *N or ■
*D entry more than once in a single checklist is an error. |
Example:
Procedure SUB is on local file PROCFIL.
.PR0C,SUB*I,P1=(*N),P2=(*N=X),P3=(*N=).
COMMENT. #P1=P1, UP2-P2, #P3=P3, P4
SUB is called:
BEGIN,SUB.
The procedure body becomes:
COMMENT. P1=P1, P2=X, P3=, P4
60459680 H 4-19
![](asset-5a.png)
Checklist Pattern Description
*N and *D values are displayed under different conditions. *D
values are always displayed when screen mode interactive prompting
is required and a non-null value has not been entered for the
parameter. *D values are always accepted if entered. *N values
are displayed in screen mode only when they are valid according to
another checklist pattern which has no replacement value. If an *N
value matches more than one checklist pattern, the first checklist
pattern determines whether the value is displayed.
*Sm..n(chars)=value Specifies that the parameter entry for pA on the procedure call
*Sm..n(chars)= may consist of a string of characters selected (in any order) from
*Sm..n(chars) the set of characters represented by chars or from the set of
or characters represented by k. m..n specifies the minimum and
*Sm..n/k=value maximum values for the length of the string entered on the
* S m . . n / k = p r o c e d u r e c a l l . T h e d e f a u l t f o r m i s 1 a n d f o r n i s 4 0 . T h e
*Sm..n/k maximum value for n is 40. chars represents a set of up to 40
uppercase alphanumeric and/or special characters. Special
characters other than asterisks must be $-delimited. k selects one
of the following sets:
k Characters
A All alphabetic characters
B All octal characters
D All decimal characters
A B A l l a l p h a b e t i c a n d o c t a l c h a r a c t e r s
AD All alphabetic and decimal characters
To include one or more asterisks as members of the set, append an
asterisk to the mnemonic. For example, AB* specifies all
alphabetic and octal characters and asterisks are allowed.
If *Sm..n(chars)=value or *Sm..n/k=value is in the checklist, value
replaces keywrd in the procedure body when 1 to n characters from
chars are specified on the procedure call. You can specify any
string of 0 to 40 uppercase characters for value. You must delimit <>^\
special characters, other than an asterisk (*), with dollar signs. '
If value is //DATA, all occurrences of keywrd in the procedure body
are replaced by the name of the data file created by the .DATA
directive (refer to .DATA Directive for the name of this file). If
value is //FILE, all occurrences of keywrd in the procedure body are
replaced by the name of the file that contains the procedure. Any
data read from this file begins with the record immediately
following the record that houses the procedure. If the procedure
resides on a library and is called by a name call form of the BEGIN
command, keywrd is replaced by a null value. If value is //PRIMARY,
all occurrences of keywrd in the procedure body are replaced by the
current primary file.
■■^*K
4-20 60459680 H
![](asset-5b.png)
Procedure COPIL will accept one to four letters for the F parameter.
More than one set may be specified for a parameter. For example,
p r o c e d u r e S E T h a s t w o s e t s s p e c i fi e d f o r t h e P p a r a m e t e r . I
.PR0C,SET*I,P1=(*S,*SO,*S3). |
Parameter entries could include P=BB or P=XZY but not P=AZ or P.
Null sets are not allowed. For example, all the set entries for PI
in the following procedure header are in error.
.PROC,SET*I,P=(*S3(ABC),*S3/D>.
60459680 E 4-20.1/4-20.2
![](asset-5c.png)
0*%
![](asset-5d.png)
Checklist Pattern Description
r
jt$$bz\
If *Sm..n(chars)= or *Sm..n/k= is in the checklist, a null value is
substituted for keywrd. If *Sm..n(chars) or *Sm..n/k is in the
checklist, the parameter entry for pi on the procedure call
replaces keywrd.
Example:
Procedure COPIL is on local file COPI:
.PR0C,C0PIL*I,0"0LD FILE NAMEH=(*F,*N=OLD),
R"REPLACEMENT FILE NAME"=(*F,*N=LG0),
NMNEW FILE NAME"=(*F,*N=NEW),
L"LAST REC0RD"=(*F,*N=O,
F,,FLAG"=(*S4( ARTE) ,*N=).
COPYL,0,R,N,L,F.
REVERT.
COPIL is called:
BEGIN,COPIL,COPI,0=OLD,R=MODIFID,
N-NEW,F=AE.
The procedure body becomes:
COPYL,OLD,MODIFID,NEW„AE.
Procedure COPIL will accept one to four letters for the F parameter.
More than one set may be specified for a parameter. For example,
procedure SET has two sets specified for the P parameter.
.PR0C,SET*I,P=(*S3(ABC),*S3/D).
Parameter entries could include P=BB, P=BCA, or P=901 but not
P=XZY, P=AZ, P=P or P=A2.
Null sets are not allowed. For example, all the set entries for PI
in the following procedure header are in error.
.PROC,ERROR*I,P1 = (*S,*SO,*S3).
60459680 H 4-21
![](asset-5e.png)
Checklist Pattern
pstring=pvalue
pstring=
pstring
Description
Specifies the substitution for keywrd when the parameter entry for
p.^ on the procedure call matches pstring. pstring must be 0 to 40
uppercase characters. Special characters must be $-delimited. If
pstring=pvalue is in the checklist, pvalue replaces keywrd in the
procedure body when pstring is specified on the procedure call.
You can specify any string of 0 to 40 uppercase characters for
pvalue. You must delimit special characters, other than asterisks (*)
with dollar signs.
If pvalue is //DATA, all occurrences of keywrd in the procedure body
are replaced by the name of the data file created by the .DATA
directive (refer to .DATA Directive for the name of this file). If
pvalue is //FILE, all occurrences of keywrd in the procedure body
are replaced by the name of the file that contains the procedure.
Any data read from this file begins with the record immediately
following the record that contains the procedure. If the procedure
resides on a library and is called by a name call form of the BEGIN
command, keywrd is replaced by a null value. If pvalue is
//PRIMARY, all occurrences of keywrd in the procedure body are
replaced by the current primary file.
If pstring= is in the checklist, a null value replaces keywrd.
pstring is in the checklist, pstring replaces keywrd.
Example:
Procedure LABL on a global library file:
.PR0C,LABL*I,FN"FILE NAME"=C*F),
VSN "VSN OF TAPE"=(*A),
WRITE "YES OR N0"=(YES=W,N0=R).
LABEL,FN,#VSN=VSN,#PO=WRITE,WRITE.
REVERT.
If
Procedure LABL is called:
LABL,FN=STATS,VSN=TAPE24,WRITE=N0.
Procedure body becomes:
LABEL,STATS,VSN=TAPE24,P0=R,R.
Menu Format
This format of the .PROC directive generates a menu when you call the procedure and make no
menu selection, when you make an incorrect selection, or when you request help information
(refer to Requesting Help on Procedure Calls). The presence of the NOLIST parameter on the
.HELP directive suppresses the menu display when you request .HELP information.
.^ssffix
4-22 60459680 H
![](asset-5f.png)
Format:
.PROC,pname*M"title",keywrd=(selections).ck.
Parameter
pname
t i t l e
0^U\
keywrd
selections
ck
Description
Specifies the procedure name, pname must be a 1- to 7-character
string of alphanumeric characters. Make the first character of pname
an alphabetic character to avoid inadvertent editing of the primary
file on name calls to procedures. You must append *M to pname to
enable menu generation.
Specifies the menu title. The title string can be a maximum of 40
lowercase (12-bit) characters, 80 uppercase (6-bit) characters, or any
combination of lowercase and uppercase characters that does not exceed
480 bits. The title field can be null ("") or completely omitted. If
you omit title, the system uses the procedure name pname as the title
when the procedure is called in screen mode. The title appears
whenever the system displays the menu.
Specifies the keyword in the procedure body for which the system
substitutes one of the selections, keywrd can be a string of 1 to 10
alphanumeric characters.
Defines the menu selections. A maximum of 50 selections can be
defined for a menu. The definitions must have the following format:
num^Hdescript|",...,numn"descriptn"
num* Defines an integer number that identifies the menu
selection in the screen display, num^ can be any
integer up to 10 digits in length. Menu selections
appear in the screen display in the order they are
defined in the .PROC directive, not necessarily in the
order defined by the selection numbers.
descript. Describes the menu selection. The description can be
a maximum of 40 lowercase (12-bit) characters, 80
uppercase (6-bit) characters, or any combination of
lowercase and uppercase characters that does not
exceed 480 bits. In screen mode, the system will
display a maximum of 40 characters. You can also
specify a null description ("") or omit this field.
This description appears whenever the system displays
the menu.
Specifies a 1- to 10-character comment keyword. This is an optional
parameter. A period must follow the comment keyword. The system
substitutes comments specified on the procedure call for the comment
keyword in the procedure body. The system substitutes a null value
for the comment keyword if no comments are on the procedure call. If
you do not specify a comment keyword, the system ignores comments made
on the procedure call.
Note that the system treats the comment keyword ck as a contiguous
string upon substitution. If ck is concatenated to another long
string in the procedure body, this substitution may produce a line
that exceeds the line length limit (150 6-bit characters).
60459680 H 4-22.1
![](asset-60.png)
A menu has the following format:
t i t l e
num-j. descript.j
nun^. descript2
numn. descriptn
SELECT BY NUMBER OR TYPE Q TO QUIT?
where title, nun^, and descriptj conform to the descriptions given them previously. You
can specify the prompt for a selection using the .PROMPT directive. If you do not, the ^-
system uses a default prompt as just shown. Additionally, the system centers all lines when ^1
in screen mode.
The Q option aborts the procedure call and initiates a search for an EXIT command in the
procedure. If the procedure was called from another procedure, the EXIT commands in the
calling procedure or procedures are also processed.
r ^ ^ K
4~22*2 60459680 G
![](asset-61.png)
FORMATTING AND HELP DIRECTIVES
Along with the procedure header, the formatting and help directives further define the
parameter prompts and help information that appears at the terminal. The formatting
directives, if present, must follow the procedure header. Comment directives (beginning
with .*) may be interspersed among the formatting directives. Help directives and help text
follow the formatting directives. Comment directives placed in the help section are
considered a part of the help text.
.CORRECT Directive
The .CORRECT directive specifies the first field of the prompt that follows a set of
incorrect parameter entries. When the system prompts the procedure caller for corrections
to an incorrect entry, the prompt has the following three fields:
text parameter descriptiont
This directive specifies the text field.
Format:
.CORRECT,text.
.CORRECT=text.
Parameter
t e x t
Description
Specifies a 1- to 80-character text string that appears on the
screen. The system interprets your string in 6/12-bit display code,
which supports uppercase and lowercase characters.
In the first format, any alphanumeric or special characters may be
used except a period or right parenthesis (. or )). Special
characters need not be enclosed in $ signs.
In the second format, any characters may be used (including a period
or right parenthesis), but special characters must be enclosed in
$ signs.
In screen mode, the default text string is:
Please correct
In line mode, the default string is:
Correct
In screen mode, if the prompt is too long, the system truncates the prompt and indicates the
truncation with an ellipsis (no truncation occurs in line mode). You can suppress display |
of the parameter field of the prompt by using apostrophes rather than quotation marks around
the description in the procedure header. In screen mode, the prompt appears left-justified
on the top line of the screen.
This directive does not apply to menu procedures.
tThe description field does not appear in screen mode.
60459680 H 4-23
![](asset-62.png)
■*"«S^V
.ENDHELP Directive
The .ENDHELP directive specifies the end of the help section of the procedure body. You
must include an .ENDHELP directive if there are any help directives in the procedure. Only
one .ENDHELP directive is allowed in a procedure.
Format:
.ENDHELP.
.ENTER Directive
The .ENTER directive specifies the text for the initial prompt for a parameter. When the
system initially prompts the user for a parameter, the prompt has the following three fields:
t e x t parameter description
This directive specifies the text field.
Format:
.ENTER,text.
,ENTER=text.
Parameter Description
t e x t S p e c i fi e s a 1 - t o 8 0 - c h a r a c t e r t e x t s t r i n g t h a t a p p e a r s o n t h e
screen. In the first format, any alphanumeric or special characters
may be used except a period or right parenthesis (. or )). Special
characters need not be enclosed in $ signs.
In the second format, any characters may be used (including a period
or right parenthesis), but special characters must be enclosed in
$ signs.
The system interprets your string in 6/12-bit display code, which
supports uppercase and lowercase characters. The default for the
screen mode is:
Please enter
The default for line mode is:
Enter
In screen mode, if the prompt is too long, the system truncates the prompt and indicates the
truncation with an ellipsis (no truncation occurs in line mode). You can suppress display
of the text and parameter fields of the prompt by using apostrophes around the description
in the procedure header. In screen mode, the prompt appears left-justified on the top line
of the screen.
This directive does not apply to menu procedures.
4-24 60459680 H
'*^S\
![](asset-63.png)
.Fn Directive
The .Fn directive specifies a label for one of the six programmable function keys you can
use with screen mode parameter displays.
Format:
.Fn,text.
,Fn=text.
where n is one of the integers 1 through 6.
Parameter Description
t e x t S p e c i fi e s a l a b e l s t r i n g o f n o t m o r e t h a n 8 c h a r a c t e r s . Yo u c a n
specify lowercase and uppercase characters.
In the first format, any alphanumeric or special characters may be
used except a period or right parenthesis (. or )). Special
characters need not be enclosed in $ signs.
In the second format, any characters may be used (including a period
or right parenthesis), but special characters must be enclosed in
$ signs.
The function and default label of each of the programmable function keys are given in the
table 4-2.
60459680 H 4-24.1/4-24.2
![](asset-64.png)
![](asset-65.png)
Table 4-2. Programmable Function Keys for Procedures
Key
Fl
F2
Default Label
FWD
BKW
F3 HELP FWD
F4 HELP BKW
F5 HELP
F6 QUIT
Function
Pages forward through screens of parameters or menu
selections.
Pages backward through screens of parameters or menu
selections.
Pages forward through screens of .HELP text.
Pages backward through screens of .HELP text.
Displays .HELP text at the bottom of the screen.
Aborts the procedure call and initiates search for an
EXIT command in the current procedure and (if nested) in
the calling procedure(s).
.HELP Directive
The .HELP directive indicates that the text that follows it is information about the
procedure itself or its parameters. The procedure caller can access this information by
entering a question mark as a parameter in a procedure call or by appending a question mark
to the procedure name or a parameter name. When the system encounters a question mark in a
procedure call, it stops processing the call and starts help processing. Therefore,
anything entered after the question mark will not be read. Refer to Requesting Help on
Procedure Calls later in this section. If specified, .HELP directives must immediately
precede the .ENDHELP directive.
Formats:
0&>\
■g^S\
.HELP.
.HELP,,NOLIST.
.HELP,parm.
.HELP,parm,NOLIST.
Parameter
NOLIST
parm
Description
Suppresses the display of some of the .HELP text during help
processing.
Specifies one of the parameter keywords in an interactive procedure
(*I) or specifies one of the menu selections (choice^) in a menu
procedure (*M).
The first and second formats indicate that the text that follows the directive describes the
procedure itself. For interactive procedures in line mode, the NOLIST parameter suppresses I
the display of a parameter list when the caller requests information about the procedure
itself. For menu procedures, the NOLIST parameter suppresses the display of the menu in
line mode.
For interactive procedures, the third, and fourth formats indicate that the text that follows
the directive describes the parameter associated with the keyword parm. The NOLIST
parameter suppresses the display of acceptable parameter values as given in the parameter's
checklist.
60459680 H 4-25
![](asset-66.png)
>*^\
For menu procedures, the third and fourth formats indicate that the text following the
directive describes the specified menu selection. The NOLIST parameter suppresses the
display of the menu after the display of the .HELP text.
The text information starts on the line following the .HELP directive. The text can span
multiple lines and must end with either another .HELP directive or an .ENDHELP directive.
Parameter substitution does not occur within the .HELP text.
The system assumes that your .HELP text is in 6/12-bit display code, which supports
uppercase and lowercase characters. In batch jobs, the system displays .HELP text in
uppercase only.
Interactive (*I) Help
When you request help information about an interactive procedure, the system displays the ^^1
following: '
• The text following the procedure's .HELP directive.
• The parameters that follow the procedure name on the .PROC directive unless
suppressed by the NOLIST parameter of the .HELP directive (.HELP,,NOLIST).
• A prompt fo r a value . The pr omp t includes the de scriptive strin g specified with th e
parameter in the .PROC directive.
When you request information about a particular parameter of an interactive procedure, the ^%
system displays the following: /
• Parameter values that are acceptable according to the parameter's checklist (the
presence of NOLIST on the parameter's .HELP directive suppresses the display of
these values).
• The text that follows the parameter's .HELP directive.
• The current value, if any, of the parameter.
•A prompt for a value. The prompt includes the descriptive string specified with the /*®\
parameter on the .PROC directive. )
Menu (*M) Help
When you request help information about a menu procedure, the system displays the following:
• The text following the procedure's .HELP directive.
• The menu unless suppressed by the NOLIST parameter of the .HELP directive
(.HELP,,NOLIST).
• A prompt for a menu selection.
When you request information about a particular menu selection, the system displays the
following:
• The text following the .HELP directive for that menu selection.
• The menu unless suppressed by the NOLIST parameter of the .HELP directive.
• A prompt for a menu selection.
4-26 60459680 G
^***!\
![](asset-67.png)
/^**
r
Line Mode Example:
Procedure PRINT (on file PRINT) verifies that the selected file is local before it routes
t h e fi l e t o a p r i n t e r.
| NOTE
The .HELP text uses lowercase and uppercase
characters.
,PROC,PRINT*I,F"FILE NAME"=(*F),
rDC'DISPOSITION CODE"=(*N=LP,LP,PR,LR,LS,LT).
.HELP.
This procedure routes a permanent file to the selected line printer.
.HELP,F.
The name of the permanent file to be routed.
.HELP,DC.
The disposition code. DC accepts only the line printer options.
.ENDHELP.
.I F,F ILE (F,. NOT. LO ),P F.
GET,F.
.ELSE,PF.
r REWIND,F.
.ENDIF,PF.
COPYSBF,F,Z.
ROUTE,Z,#DC=DC.
REVERT,NOLIST.
To get a description of procedure PRINT, either append a question mark to the file name or
enter a question mark as the first parameter. If PRINT is a local file, you can get such a
description by entering any of the following:
PRINT?
r PRINT,?
BEGIN,PRINT,PRINT?
BEGIN,PRINT,PRINT,?
If PRINT is not local, enter any of the following:
BEGIN,PRINT,PRINT?
or
BEGIN,PRINT,PRINT,?
or
GET,PRINT
PRINT,?
or
GET,PRINT
PRINT?
60459680 H 4~27
![](asset-68.png)
The following is a sample of the dialogue generated by the .PROC and .HELP directives:
/begin,pri nt,print?
This procedure routes a permanent file to the selected line printer.
PARAMETERS FOR PRINT ARE F, DC
ENTER F FILE NAME? ?
ALLOWABLE VALUE(S)
MUST BE A FILE NAME
The name of the permanent file to be routed.
ENTER F FILE NAME? datafil
ENTER DC DISPOSITION CODE? ?
ALLOWABLE VALUE(S)
LP
PR
LR
LS
LT
PARAMETER MAY BE OMITTED
The disposition code. DC accepts only the line printer options.
ENTER DC DISPOSITION CODE? pr
To illustrate the effect of enclosing the description string for a parameter in apostrophes
instead of quotation marks, we use the same procedure as in the previous example and replace
the quotation marks with apostrophes:
.PROC,PRINT*I,F'FILE NAME'=(*F),
DC DISPOSITION CODE' = (*N = LP,LP,PR,LR,LS,LT).
Note the difference in the prompts.
/begin,print,print?
This procedure routes a permanent file to the selected line printer.
PARAMETERS FOR PRINT ARE F, DC
FILE NAME? ?
ALLOWABLE VALUE(S)
MUST BE A FILE NAME
The name of the permanent file to be routed.
FILE NAME? datafil
DISPOSITION CODE? ?
ALLOWABLE VALUE(S)
LP
PR
LR
LS
LT
PARAMETER MAY BE OMITTED
The disposition code. DC accepts only the line printer options.
DISPOSITION CODE? pr
4-28 60459680 E
![](asset-69.png)
Screen Mode Example:
If you are at a terminal supported by the full-screen display products and your terminal is
in screen mode, the system can use full-screen displays to prompt you for parameters and to
provide you with help information.
The following screen results if you call procedure PRINT (as defined in the previous
example):
PRINT
yjpfet.
F FILE NAME:
DC DISPOSITION CODE: LP
Specify values and press NEXT when ready
/$fj^s F5 | HELP| F6 | QUIT|
If you press the HELP key while the cursor is positioned in the input field for first
parameter, you get the following screen:
PRINT
F FILE NAME:
DC DISPOSITION CODE: LP
ALLOWABLE VALUE (S)
MUST BE A FILE NAME
The name of the permanent file to be routed.
Specify values and press NEXT when ready
F FILE NAME
JsPN F 5 | H E L P 1 F 6 J Q U I T
60459680 H 4-29
![](asset-6a.png)
If you press the HELP key while the cursor is positioned in the input field for the second
parameter, you get the following screen:
PRINT
F FILE NAME:
DC DISPOSITION CODE: LP_
Specify values and press NEXT when ready
DC DISPOSITION CODE
ALLOWABLE VALUE(S)
PR
LR
LS
LT
PARAMETER MAY BE OMITTED
The disposition code. DC accepts only the line printer options,
F5 HELP F 6 Q UI T
To get help information about the procedure itself, you can append a question mark to the
name of procedure on the call or press the HELP key again after you get help for any of the
parameters.
PRINT
F FILE NAME:
DC DISPOSITION CODE: _kP_
Specify values and press NEXT when ready
PRINT
This procedure routes a permanent file to the selected line printer.
F5 |HELPJ F6 |QUITJ
Refer to Volume 2 for a detailed description of calling procedures in screen mode.
4-30 60459680 H
![](asset-6b.png)
.NOCLR Directive
The .NOCLR directive inhibits the system from automatically clearing the screen at the end
of the procedure call (once all required parameters are supplied). You can also specify a
message to appear on the top line of the screen. Unless specified to do otherwise, the
system clears the screen at the end of the call, and the screen is blank until the procedure
completes execution or sends output to the terminal.
The .NOCLR directive must be placed before any .HELP directives in the procedure.
Format:
.NOCLR,message.
.N0CLR=message.
Parameter Description
message Specifies a 1- to 40-character text string that appears on the
screen. You can use uppercase and lowercase characters in the string.
In the first format, any alphanumeric or special characters may be
used except a period or right parenthesis (. or )). Special
characters need not be enclosed in $ signs.
In the second format, any characters may be used (including a period
or right parenthesis), but special characters must be enclosed in
$ signs.
This directive applies only if the procedure is executed in screen mode.
.NOTE Directive
The .NOTE directive specifies the message that appears on the screen and in your dayfile at
the end of the procedure call (once all required parameters are supplied). Unless specified
to do otherwise, the system clears the screen at the end of the call (refer to the .NOCLR
Directive), and the screen is blank until the procedure completes execution or sends output
to the terminal.
Format:
.NOTE,message.
,NOTE=message.
Parameter Description
message Specifies a 1- to 40-character text string that appears on the screen
and in your dayfile. You can use uppercase and lowercase characters
in the string.
In the first format, any alphanumeric or special characters may be
used except a period or right parenthesis (. or )). Special
characters need not be enclosed in $ signs.
In the second format, any characters may be used (including a period
or right parenthesis), but special characters must be enclosed in
$ signs.
This directive applies only if the procedure is executed in screen mode.
60459680 H 4-31
![](asset-6c.png)
.PAGE Directive
The .PAGE directive specifies the string that precedes the page number for procedure
displays that require more than one screen.
Format:
.PAGE,text.
.PAGE=text.
Parameter
t e x t
Description
Specifies a 0- to 40-character text string. You can use uppercase and
lowercase characters in the string. The default is:
Page
In the first format, any alphanumeric or special characters may be
used except a period or right parenthesis (. or )). Special
characters need not be enclosed in $ signs.
In the second format, any characters may be used (including a period
or right parenthesis), but special characters must be enclosed in
$ signs.
.PROMPT Directive
When a procedure is called in screen mode, the .PROMPT directive defines the last line of
the screen, assuming no .HELP text is being shown. By default, this line tells the
procedure caller how to proceed. For menu procedures, the input field immediately follows
this prompt. In line mode, this directive applies only to menu procedures, where the system
produces a screen-like display.
Format:
.PROMPT,text.
.PR0MPT=text.
Parameter
t e x t
Description
Specifies a 0- to 40-character text string that appears as the prompt
on the screen. The text string can be a maximum of 40 lowercase
(12-bit) characters, 80 uppercase (6-bit) characters, or any
combination of lowercase and uppercase characters that does not exceed
480 bits.
In the first format, any alphanumeric or special characters may be
used except a period or right parenthesis (. or )). Special
characters need not be enclosed in $ signs.
In the second format, any.characters may be used (including a period
or right parenthesis), but special characters must be enclosed in
$ signs.
4-32 60459680 H
![](asset-6d.png)
^|P®\
Parameter Description
In screen mode, the default for menu procedures is:
Select from the list above and press NEXT,
and for interactive procedures the default is:
Specify values and press NEXT when ready.
In line mode, the default for menu procedures is:
SELECT BY NUMBER OR TYPE Q TO QUIT.
( EXPANSION CONTROL DIRECTIVES
The expansion control directives allow you to control certain aspects of procedure
expansion. These directives allow you to inhibit expansion of portions of a procedure, to I
change the inhibit and concatenation characters, and to skip portions of the procedure when
writing lines to the procedure command record.
.CC Directive
\ The .CC directive specifies the character used to concatenate character strings during
procedure expansion. The new concatenation character remains in effect until the procedure
terminates or until you enter another .CC directive. The default concatenation character is
the ASCII character _ or the CDC graphics character 1+ . The .CC directive can be placed
anywhere in the procedure.
Format:
.CC(n)
0m>\ Parameter Description
n Specifies the new concatenation character.
.EXPAND Directive
The .EXPAND directive terminates or restores procedure expansion for subsequent lines of the
procedure. The .EXPAND directive can be used anywhere in the procedure following the
formatting and help directives.
Format:
EXPAND,option
60459680 H 4-33
![](asset-6e.png)
-^
Parameter
ON
OFF
Description
Specifies that subsequent lines of the procedure will be expanded
normally. This is the default value.
Specifies that no parameter substitutions or directive processing will
be performed on subsequent lines. In other words, any subsequent
commands or procedure directives will be written to the command record
just as they appear in the procedure file.
.IC Directive
The .IC directive specifies the character used to inhibit parameter substitution or
directive processing during procedure expansion. The new inhibit character remains in
effect u nt il the procedure t er mi na te s or un ti l you enter a no th er .IC directive. The d ef au lt
inhibit character is the ASCII character // or the CDC graphics character = . The .IC
directive can be placed anywhere in the procedure.
Format:
.IC(n)
Parameter Description
Specifies the new inhibit character.
.SET Directive
The .SET directive allows you to build new parameters using strings and substrings created
by the STR, STRB, and STRD functions and concatenation operations, which are described in
section 6.
Format:
• SETjkeywd^strexpj,... ,keywdi=strexpi,
Parameter
keywd^
strexp^
Description
Defines a new keyword or references an existing keyword, either
from the .PROC header or from an earlier .SET directive. Keywd^
can be used for substitution in subsequent statements just as if
it had been a formal parameter contained in the .PROC header.
May be any valid CCL expression, usually but not necessarily an
expression which produces a string result. If the result of
strexpj^ is not a string but a value, the value is left-justified
and considered a string. The resulting string in either case is
substituted for any occurrences of keywd^ in subsequent
statements of the procedure.
4-34
.'J-S5!Ni
60459680 H
![](asset-6f.png)
j0JHfeS
Example 1:
.PR0C,CATTER*I,P1=(*A),P2=(*S3/D).
.SET,K9=STR($P1$,1,4)//STRD(P2,-1).
.IF,$K9$.EQ.$G00D1$,G0.
NOTE./THE 1ST 4 CHAR OF P1 AND THE LAST OF P2 = K9.
,ELSE,GO.
REVERT,EX.DISPLAY,STR($SORRY, K9 IS NOT G00D1$).
.ENDIF,60.
In this example, two substrings were concatenated to produce one string in the .SET
expression. Every occurrence of keyword K9 in the lines following the .SET directive is
replaced by the string resulting from the concatenation of substrings PI and P2. If GOODY
and 101 were supplied as values for PI and P2, the value of K9 would be set to G00D1. (For
a detailed explanation of how the STR and STRD functions operate, refer to section 6.) The
subsequent .IF statement would be true, causing the NOTE command to be included and
executed. If BADNEWS were substituted for PI, the .IF statement would be false, resulting
in the execution of the REVERT command and then of the DISPLAY command.
Example 2:
.PR0C,VALUES*I,P1=(*S/D),P2=(*S/D).
.SET,V1=STRD(P1+P2),V2=STRD(P1*P2),V3=STRD(P1**P2).
-IF,V1=V2=V3.NOTE./SUM, PRODUCT AND POWER ARE EQUAL.
NOTE./THE SUM OF P1 AND P2 IS V1.
NOTE./THE PRODUCT OF P1 AND P2 IS V2.
N0TE./P1 TO THE POWER OF P2 IS V3.
As this example demonstrates, the .SET directive along with the STRD function can create new
keywords which make it possible to include arithmetic values as strings in subsequent
commands and directives.
FILE DIRECTIVES
The file directives either create local files during procedure expansion time or place file
marks in the procedure command record.
.DATA Directive
A .DATA directive in a procedure marks the beginning of a sequence of data lines to be
written to a separate file when the procedure is called. The data file can contain program
source code, other NOS procedures, or any other type of data.
Format:
.DATA,lfn.
60459680 H 4-34.Ii
![](asset-70.png)
Parameter Description
l f n S p e c i fi e s t h e n a m e o f t h e fi l e o n w h i c h t h e d a t a l i n e s a r e t o b e
wr it te n. I f a fi le n am ed l fn i s alr ea dy as si gned t o th e jo b, it is
returned, and new local file lfn is created. You cannot specify INPUT
for lfn. If lfn is not specified, the .DATA file can be referenced in
the procedure header using the special symbol //DATA.
The default for lfn depends on the nesting level of the procedure. At
the first procedure level, the system calls this file ZZCCLAA; at the
second procedure level, it is ZZCCLAB; and so on.
You can use the .IF, .ELSE, and .ENDIF directives within the data lines following the .DATA
directive to conditionally include lines in the data file.
File marks generated by .EOR and .EOF directives can subdivide the lines written to the data ^^
file into records or files. The sequence of data lines is terminated by one of the
following:
• Another .DATA directive.
• An end-of-record (not an .EOR directive) in the procedure file.
• An end-of-file (not an .EOF directive) in the procedure file.
• An end-of-information in the procedure file.
The data file created does not include the .DATA directive. Keyword substitution continues
within the data file unless you insert a .EXPAND directive to suspend expansion processing.
After the data file is written, it is rewound.
4-34.2 60459680 H
![](asset-71.png)
The following examples show three different ways of inserting a FORTRAN 5 program into a
procedure.
Example 1: Procedure accesses program data with .DATA directive
The following procedure is on an indirect access permanent file named DATAFIL.
.PROC,ALPHA*I,
P1 = (*F,*N=#DATA),
LSTFILE=(*F,*N=FTNOUT).
FTN5,I=P1,L=LSTFILE.
LGO.
REPLACE,LSTFILE.
.DATA
PROGRAM APROG
statements
END
The following BEGIN command in a command record of the job accesses procedure ALPHA on file
DATAFIL.
BEGIN,ALPHA,DATAFIL.
A sample of a resulting dayfile is:
11.07.59.BEGIN,ALPHA,DATAFIL.
11.07.59.FTN5,I=ZZCCLAA,L=FTN0UT.
11.08.00. 61000 CM STORAGE USED.
11.08.00. 0.015 CP SECONDS COMPILATION TIME.
11.08.00.LGO.
11 . 0 8 . 0 0 . S T O P
11 . 0 8. 0 0 . 5 6 00 F I NAL E X E C UTI O N F L .
11.08.00. 0.000 CP SECONDS EXECUTION TIME.
11.08.00.REPLACE,FTNOUT.
11.08.01.$REVERT.CCL
All input after the .DATA directive (the FORTRAN 5 source program) is written onto the
default temporary file ZZCCLAA. Parameter substitution is performed on the FORTRAN program
prior to its being written to ZZCCLAA.
60459680 E 4_35
![](asset-72.png)
Example 2: Procedure accesses program data with //FILE
The following procedure is on an indirect access permanent file named PFILE. The record
immediately following procedure BETA contains the program data. The //FILE default tells the
FTN5 compiler to search for input from the next record on file PFILE.
.PR0C,BETA*I,
P1 = (*F,*N=#FILE),
LSTFILE=(*F,*N=FTNOUT).
FTN5,I=P1,L=LSTFILE.
LGO.
REPLACE,LSTFILE.
-EOR-
PROGRAM BPROG
statements
■
END
The following call accesses procedure BETA on file PFILE.
BEGIN,BETA,PFILE.
The following is a segment of the resulting dayfile. Parameter substitution occurred within
the procedure but not within the FORTRAN 5 program.
11.08.35.BEGIN,BETA,PFILE.
11.08.36.FTN5,I=PFILE,L=FTN0UT.
11.08.36. 61000 CM STORAGE USED.
11.08.36. 0.013 CP SECONDS COMPILATION TIME.
11.08.36. LGO.
11.08.37. STOP
11.08.37. 5600 FINAL EXECUTION FL.
11.08.37. 0.000 CP SECONDS EXECUTION TIME.
11.08.37.REPLACE,FTN0UT
11.08.37.$REVERT.CCL
4-36 60459680 E
![](asset-73.png)
Example 3: Procedure accesses program data from another file
A procedure may access data outside of the procedure file. The following procedure is in
the default file PROCFIL. It uses a GET command to access the program data on file TEST and
writes the binary output.
.PR0C,GAMMA*I,P1=(*F),X=(*N=FTN0UT).
GET,P1.
FTN5,I=P1,L=X.
LGO.
REPLACE,X=LISTFIL.
The following call accesses procedure file GAMMA.
BEGIN,GAMMA„P1 =TEST.
Parameter substitution occurred within the procedure but not within the FORTRAN 5 program,
as shown in the following dayfile segment.
11.06.48. BEGIN, GAMMA,, P1=TEST.
11.06.48.GET,TEST.
11.06.49.FTN5,I=TEST,L=FTN0UT.
11.06.50. 61000 CM STORAGE USED.
11.06.50. 0.013 CP SECONDS COMPILATION TIME.
11.06.50.LGO.
11.06.51. STOP
11 .06 . 5 1. 5 6 0 0 F I NA L E XEC U T IO N F L .
11.06.51. 0.000 CP SECONDS EXECUTION TIME.
11.06.51.REPLACE,FTN0UT=LISTFIL.
11.06. 51.SREVERT.CCL
60459680 D 4-37
![](asset-74.png)
I .EOF (or .EOP) Directive
| The .EOF (or.EOP) directive generates an end-of-file on the data file created with a .DATA
directive. Wherever an .EOF appears, an actual end-of-file is recorded when the data file
is written on the file specified in the .DATA directive. The system always writes an
end-of-record at the end of a data file. If you want an end-of-file also, you must end the
file with an .EOF directive. The .EOF directive is valid only after a .DATA directive. The
.EOP directive may be used interchangeably with the .EOF directive.
Format:
.EOF.
I . E O P .
| .EOR (or .EOS) Directive ■*%,
The .EOR (or .EOS) directive is used to separate records in a data file created with a .DATA
directive. Wherever an .EOR is placed, an actual end-of-record is recorded when the data
file is written on the file specified in the .DATA directive. The system always writes at
least one end-of-record at the end of a data file, whether or not you specify an .EOR
I directive. The .EOR directive is valid only after a .DATA directive. The .EOS directive
may be used interchangeably with the .EOR directive.
Format:
.EOR. /*^\
| . E O S . )
BRANCHING DIRECTIVES
The branching directives provide conditional inclusion of commands, other directives, or
data lines in the procedure. The function of the .ELSE, .ENDIF, and .IF directives is much
like that of their command equivalents. The branching can appear in any of the four
sections of the procedure body.
.ELSE Directive
The .ELSE directive in conjunction with the .IF directive either terminates or initiates the
skipping of lines in the procedure body.
Format:
•ELSE.label.
Parameter Description
label Specifies a 1- to 10-character,alphanumeric string. The string must
begin with an alphabetic character.
If the condition in the matching .IF directive is true, the .ELSE directive initiates the
skipping of the lines between itself and the next matching .ENDIF directive (two directives
match only if their label parameters are identical). If the condition in the matching .IF
directive is false, the .ELSE directive terminates the skipping that the .IF directive
initiated. An .ELSE directive cannot terminate the skipping initiated by another .ELSE
directive.
4-38 60459680 H
![](asset-75.png)
0^<K
.ENDIF Directive
The .ENDIF directive terminates skipping initiated by a matching .IF or .ELSE directive
(directives match only if their label parameters are identical).
Format:
.ENDIF,label.
Parameter Description
label Specifies a 1- to 10-character, alphanumeric string. The string
must begin with an alphabetic character.
.EX Directive
The .EX directive submits a single command to the system for immediate execution. The
system performs keyword substitutions in the command before executing the command. No
further procedure directives are normally processed. Although .DATA files are created, the
command record is never executed. Since the command record is not executed, the procedure
nesting level of your job is not incremented.
Format:
.EX.command.
Parameter Description
command Any valid command. The length of the expanded command cannot exceed
80 characters.
If the command entered by .EX aborts, the system responds as though the command had been
entered from the calling job or procedure.. For example, assume that procedure A calls
procedure B and that procedure B contains a .EX directive. If the command entered by the
•EX directive is erroneous, the system immediately suspends command processing and begins
searching for an EXIT command in procedure A.
The .EX directive is most often used in menu procedures in which the command executed by .EX
is a call (BEGIN command) to another procedure. Since the purpose of the menu procedure is
merely to prompt for a single item of user input, the most efficient way of calling the
resulting procedure is in a .EX directive.
Example:
The following menu procedure initiates one of three nested procedures, (EXEC1, EXEC2, or
EXEC3) depending on the menu item selected.
.PR0C,FIX*M,P=
(1"OPTION 1",
2"0PTI0N 2",
3"0PTI0N 3").
.EX.BEGIN,EXEC_P,PFILE.
REVERT,NOLIST.
r60459680 G 4-39
![](asset-76.png)
.IF (or .IFE) Directive
The .IF directive conditionally writes lines from the procedure body to the procedure
command record or the file associated with the .DATA directive. The .IF directive is to the
procedure command record as the IF command is to the job command record (refer to the IF
command). Before evaluating the conditional expression, the system performs parameter
substitution for the portion of the directive that follows the .IF. Since the system
processes the .IF directive at procedure expansion time, the .IF directive cannot depend
upon the effects of commands in the procedure body.
Formats:
.IF,expression.command.
.IF,expression,label.
Parameter Description
expression Specifies an expression that is either true or false (refer to Command
Syntax in section 6). The separator following expression in the first
format must be a terminator.
command Specifies any valid system command.
label Specifies a 1- to 10-character, alphanumeric string. The string must
begin with an alphabetic character. An identical string must appear
in a subsequent .ELSE or .ENDIF directive.
If expression is true, the first format writes command in the procedure command record while
the second format processes all lines between the .IF directive and the first matching .ELSE
or .ENDIF directive (two directives match only if their label parameters are identical).
If expression is false, the system does not write command in the procedure command record
| (for the first format) nor does the system write and process the lines between the .IF
directive and the first matching .ELSE or .ENDIF directive (for the second format).
| NOTE
When using the first format (.IF,expression,
command.), values for .command, that match a
CCL relational, logical, or string operator
(such as .EQ. or .OR.) are interpreted as
operators, causing the procedure to abort.
To write a valid .IF directive when .command,
matches an operator, terminate the expression
or command with a right parenthesis instead
of a period.
4-40 60459680 H
![](asset-77.png)
COMMENT (.*) Directive
The .* directive enables you to document a procedure with internal comments. These comments
do not appear in the dayfile when the procedure is processed. The comment, which follows
the .*, can contain any combination of characters.
Format:
,*comment
Parameter Description
comment Represents your comments.
The comment directive can appear anywhere in the procedure body. However, a comment
directive inserted in the help section is considered as part of the help text.
r
i#^*>
60459680 H 4-40.1/4-40.2 |
![](asset-78.png)
*%
*%
![](asset-79.png)
CALLING A PROCEDURE (BEGIN COMMAND)
The BEGIN command initiates execution of a procedure. When a BEGIN command is entered, the
system begins executing the specified procedure and continues until a REVERT command is
entered. The REVERT command causes the system to return to the command record of the calling
job or procedure. The system then continues execution with the first command following the
BEGIN command. Procedures can be nested up to a level of 50 nested procedures.
Figure 4-5 shows a diagram of a procedure call from a batch job and from an interactive job.
The interactive example also diagrams a first level nested procedure call.
Batch Job File
AJOB.
USER,USERNAME,PASSWORD.
BEGIN, APROC'
Procedure
.PR0C,APR0C*I,
REVERT.
Interactive Command
Procedure
BEGIN,BPROC
.PR0C,BPR0C*I.
BEGIN, CPROC
REVERT.
Procedure
.PR0C,CPR0C*I.
REVERT.
Figure 4-5. Calling a Procedure
60459680 D 4-41
![](asset-7a.png)
You can alter the contents of a procedure by passing parameters to the procedure through the
BEGIN command. The system substitutes the parameter values into the procedure body according
to the rules specified in the procedure header (refer to .PROC Directive earlier in this
section).
The system allows you to input the parameters from a full-screen format if the following
conditions are true:
• Your terminal supports full-screen input for procedures (currently, only a CDC 721).
• Your terminal is in screen mode (refer to the SCREEN command).
• The procedure is interactive; that is, the .PROC directive contains a *M or *I.
• You do not supply required parameters on the procedure call.
Formats:
BEGIN,pname,pfile,pj,p2,...,pn.comment
or
-pn am e ,p fil e ,p i, p 2, ... ,p n.c om men t
or
pname,pj,p2,...,pn.comment
or
pfile,pi,p2,...,pn.comment
The first format is the full BEGIN command format that can be used in either batch or
(interactive jobs. When you use this format, the system uses the following search order when
attempting to locate file pfile:
• local files
• indirect access files in your permanent file catalog
• direct access files in your permanent file catalog
• indirect access files under user name LIBRARY
• direct access files under user name LIBRARY
The second format can be used only from an interactive job. It uses the same search order
as the first format.
The third and fourth formats are the name call formats in which the command name BEGIN can
be omitted.
4 42 60459680 E
![](asset-7b.png)
The third format can be used from a batch or interactive job if one of the following is true:
• pname is a procedure within a record in a file called pname. The system locates
this procedure record and executes it.
• pname is a procedure in a global library set.
• pname is a procedure in the system library.
The fourth format can be used from a batch or interactive job.
file. The system executes the first procedure on pfile. pfile is the name of a local
00^\
/ j ^ N
Parameter Description
pname Specifies the procedure name from the procedure header directive. If pname
is omitted from the first format, two consecutive commas must be specified.
The default procedure is the record at the current position of pfile. If
pfile is at its end-of-information, the system rewinds pfile and uses the
first procedure on pfile. If pfile is INPUT, the file is not rewound.
pfile Specifies the name of the file containing the procedure. The file name
pfile must be inserted as the second parameter in the first format. Its
omission is indicated by two consecutive commas following pname. To get a
description of the procedure pname, you can append a question mark to pfile
(refer to Requesting Help on Procedure Calls later in this section). File
pfile is not automatically returned after the procedure executes.
If pfile is omitted from the first format, the installation-defined default
file name is used (PROCFIL is the default).
Pi Specifies an optional parameter that may affect the substitution to be made
for a keyword used in the procedure. The value you specify is compared to
the appropriate checklist specified for this parameter in the procedure
header. The checklist entries are checked in a left-to-right fashion and
the first match determines the substitution. Refer to the .PROC Directive
in this section for more details on parameter substitution. The specific
formats for p^ are described later in this subsection.
If you are using the third or fourth format of the BEGIN command as
previously shown, there is a 7-character restriction on both the keyword
portion and the value portion of the parameter p^.
comment Specifies the value associated with the comment keyword (ck) on the
procedure header. The value consists of any characters you specify
following the terminator. If the ck keyword appears on the procedure
header, the system substitutes your comment for the comment keyword ck in
the procedure body. Otherwise, the system ignores this comment.
60459680 G 4-43
![](asset-7c.png)
For interactive procedures (*I), optional parameters p^ can have the following formats:
Pi Description
keywrd Specifies a parameter identical to a keyword on the procedure header.
Substitution is controlled by the *K entry in the checklist for the
parameter.
key wr d? Spe cifies in te ra ct iv e BEGI N processi ng (re fe r to Requ esting H el p on
or Procedure Calls later in this section).
1
keywrd= Removes keywrd in the procedure body (null substitution) unless overridden
by a checklist specification.
keywrd=val Allows order-independent substitution (refer to Parameter Matching Modes in
this section), val replaces keywrd in the procedure body unless the
associated checklist specifies otherwise, val can be a 1- to 40-character
symbolic name or value. Section 6 describes symbolic names, val can
contain special characters (nonalphanumeric) if they are delimited by dollar
signs. Asterisks are the exception; they can appear without dollar sign
delimiters.
This parameter format has the following valid variations:
Format Meaning
keywrd=val Substitutes the string val for keywrd.
keywrd=val+ Substitutes the decimal value of val for keywrd.
keywrd=val+D Same as keywrd=val+.
keywrd=val+B Substitutes the octal value of val for keywrd.
When calling a procedure, a keyword can be named more than once if the
keywrd=val parameter format is used each time. The system issues a message
informing you that a keyword is named more than once on the command. It
uses the value specified with the last occurrence of the keyword.
4-44 60459680 H
![](asset-7d.png)
/0SS*\
Pi Description
val Unless overridden by a checklist specification, assigns this 0- to
40-character (uppercase only) symbolic name or value to the keyword whose
position in the procedure header parameter list matches the position of this
parameter in the BEGIN command parameter list (refer to Parameter Matching
Modes in this section). Special characters (nonalphanumeric), other than
asterisks (*), must be delimited by dollar signs. This parameter format has
the following variations:
Format
val
val+
val+D
val+B
Meaning
Substitutes the string val itself.
Substitutes the decimal value associated with val.
Substitutes the decimal value associated with val,
Substitutes the octal value associated with val.
NOTE
If you specify a parameter p^ on a name
call to a local file, neither the keyword
keywrd or the value val can exceed seven
characters.
For menu procedures (*M), the procedure call can contain only one substitution parameter
p^. On such calls, p^ can have one of the following formats:
Pi Description
choice Specifies a menu selection that appears on the procedure header. The menu
selection must be an unsigned integer.
choice? Specifies interactive help processing (refer to Requesting Help on Procedure
or Calls later in this section).
1
If you omit p^, the system displays the menu and prompts for a menu selection.
Example:
The following procedure is accessed by a sequence of BEGIN commands in the command record of
the j ob.
.PR0C,TEST1*I,FK.
COMMENT. FK
60459680 H 4-45
![](asset-7e.png)
The resulting dayfile shows each BEGIN command and the substitutions made. The relevant
segment of the dayfile is as follows:
10.15.26.BEGIN,TEST1,FKTEST,20.
10.15.27.COMMENT. 20
10.15.27. RE VERT. CCL
10.15.27.SET,R2=100.
10.15.27.BEGIN,TEST1,FKTEST,FK=R2+.
10.15.28. COMMENT. 100
10.15.28. REVERT.CCL
10.15.28.BE6IN,TEST1,FKTEST,FK=R2+D.
10.15.29.C0MMENT. 100
10.15.29.REVERT.CCL
10.15.29.BEGIN,TEST1,FKTEST,FK=R2+B.
10.15.30.COMMENT. 144
10.15.30. RE VERT. CCL
10.15.30.BE6IN,TEST1,FKTEST,FK.
10.15.31 .COMMENT. FK
10.15.31.RE VERT.CCL
10.15.31.BEGIN,TEST1,FKTEST,FK=.
10.15.32.COMMENT.
10.15.32. REVERT. CCL
10.15.32.BE6IN,TEST1,FKTEST,VALUE.
10.15.33.C0MMENT. VALUE
10.15.33.REVERT.CCL
10.15.34.BEGIN,TEST1,FKTEST,$VALUE-2$.
10.15.34.COMMENT. VALUE-2
10.15.34. REVERT.CCL
10.15.35.BE6IN,TEST1,FKTEST,*.
10.15.35.COMMENT. *
10.15.35.REVERT.CCL
REQUESTING HELP ON PROCEDURE CALLS
After you call a procedure interactively but before the system executes the specified
procedure, you can have a dialogue with the system about the procedure. This is possible
only if the procedure writer appended the *I or *M to the procedure name in the procedure
header (refer to the .PROC directive described in this section). You can do any of the
following:
• Request help information about the procedure itself.
• Request help information about a procedure parameter.
• Supply omitted parameters.
• Reenter parameter values that are in error.
If the parameter specifications in the procedure call are incorrect or incomplete, the
system initiates the dialogue. You can also initiate the dialogue by requesting a
description of the procedure or parameters in one of the following ways:
• Append a question mark to the procedure file name.
• Append a question mark to the name of a procedure parameter for *I procedures or to
a menu selection for *M procedures.
4-46 60459680 D
![](asset-7f.png)
• Enter a question mark as a parameter on the procedure call.
• Enter a question mark in response to an interactive prompt.
• Press the HELP key any time after you call the procedure if your terminal is in
screen mode.
If you omit required parameters or if any parameter is in error on the procedure call, the
system prompts you for the required parameters and those in error. If the system prompts
you for a parameter that need not be specified and you want to use the default for that
parameter, enter a carriage return. If the format of a parameter entry is not correct or
the parameter entry is not specified on the procedure header directive, you are reprompted
for the parameter. Prompting for parameters terminates when:
• You satisfy all parameter requirements.
• You enter a parameter followed by a terminator (a period or a right parenthesis), or
enter just a terminator. If all required parameters have been entered, the system
executes the procedure. Otherwise, the system continues prompting until all
required parameters are satisfied.
• It is a menu procedure executing in line mode and you enter Q. The system does not
execute the menu. For nested menu procedures, entering Q causes the system to
discontinue expansion of the current procedure and begin searching for an EXIT
command in the calling procedure.
0^" • Your terminal is in line mode and you enter the termination or interruption
character for your terminal (refer to appendix J). The BEGIN command processing
ends and the system does not execute the procedure. For nested procedures,
terminating the dialogue in this way causes the system to search for an EXIT command
in the calling procedure.
• Your terminal is in screen mode and you press the QUIT key. The system does not
execute the procedure. For nested procedures, terminating the dialogue in this way
causes the system to search for an EXIT command in the calling procedure.
rAs with all commands, you can always append a comment after the terminator on the call.
Additionally, you can append a comment to a parameter entry made during a parameter-
prompting dialogue. Still, the comment must follow a terminator (refer to the last example
in this subsection).
0$^>\
60459680 E 4-47
![](asset-80.png)
The procedure calls in table 4-3 illustrate the various methods of requesting help on
procedure calls. For convenience, we show the name call format of the BEGIN command.
Table 4-3. Help on Procedure Calls
Procedure Call
Re suit
Interactive
Procedure (*I)
Menu
Procedure (*M)
pname The system prompts for
required parameters or
parameter values in error.
The system displays the
menu and prompts for a
selection.
pname ? The system provides any
.HELP text about the pro
cedure itself and then
prompts for parameters.
The system provides any
.HELP text about the proce
dure itself, displays the
menu, and prompts for a
selection.
pname,? Same as pname? . Same as pname,? .
pname,keywrd? The system provides any
.HELP text for the
parameter associated
with keywrd and then
prompts for parameters.
Not applicable.
pname,choice? Not applicable. The system provides any
.HELP text for that menu
selection, displays the
menu, and prompts for a
selection.
4-48 60459680 H
'^\
![](asset-81.png)
If your job is a batch job and you request a description of the procedure or its parameters,
the system writes the description in the job dayfile. If any of the required parameter
specifications are in error, error messages appear in the dayfile. In either case, the
system does not execute the procedure.
The following example shows the interactive entry of parameters.
Example:
Procedure F5 resides on local file F5.
.PR0C,F5*I,I"INPUT,^(*F,*N=INPUT),
B"BINARIES"= (*F,*N=LGO),
L"OUT PUT'<= (* F,*N=OUT PUT) ,
LO"LIST OPT IONS "= (*N=O,0,0,R,A,M,S).
FTN5,M=I,#B=B,#L=L,#L0=L0.
REVERT.
To elicit prompts for the parameters on the procedure, the user enters
f5,?
The following dialogue ensues:
PARAMETERS FOR F5 ARE I, B, L, LO
ENTER I INPUT? test
ENTER B BINARIES ? bfile
ENTER L OUTPUT ? Listing
ENTER LO LIST OPTIONS? s
REVERT.
The following example is the same as the previous example, except that apostrophes replace
the quotation marks in the procedure header:
.PROC, F5*I, I 'INPUT »= (*F,*N=INPUT ),
B 'BINARIES '= (*F,*N=LGO) ,
L'OUT PUT'= (*F,*N=0UT PUT),
LO'LIST OPTIONS '= (*N=0,0,0,R,A,M,S) .
FTN5, #1 =1, ffB =8, #L =L , #L0 =L0.
REVERT.
To elicit prompts for the parameters on the procedure, the user enters
f5,?
The following dialogue ensues:
PARAMETERS FOR F5 ARE I, B, L, LO
INPUT? test
BINARIES ? bfile
OUTPUT ? Listing
LIST OPTIONS? s
REVERT.
60459680 D 4-49
![](asset-82.png)
^r^^s
The following example shows help processing with a menu procedure:
NOTE
The .HELP text uses lowercase and uppercase
characters.
/List,f=menu
.PR0C,MENU*M"SAMPLE MENU",0PTI0N=
(1 "OPTION 1",2"0PTI0N 2", 3"0PTI0N 3") .COMMENT.
.KELP
This procedure shows the structure of a menu procedure.
.HELP,1
This is HELP text for option 1.
.HELP, 2
This is HELP text for option 2.
.HELP, 3
This is HELP text for option 3.
.ENDHELP.
.IF,0PTI0N.EQ.1.N0TE.+Y0U CHOSE #0PTION 1 COMMENT.
.IF,0PTI0N.EQ.2.N0TE.+Y0U CHOSE ^OPTION 2 COMMENT.
.IF,0PTI0N.EQ.3.N0TE.+Y0U CHOSE flOPTION 3 COMMENT.
REVERT,NOLIST.
/menu?
This procedure shows the structure of a menu procedure.
SAMPLE MENU
1. OPTION 1
2. OPTION 2
3. OPTION 3
SELECT BY NUMBER OR TYPE Q TO QUIT ? 1 ?
This is HELP text for option 1.
SAMPLE MENU
1. OPTION 1
2. OPTION 2
3. OPTION 3
SELECT BY NUMBER OR TYPE Q TO QUIT ? 2?
This is HELP text for option 2.
SAMPLE MENU
1. OPTION 1
2. OPTION 2
3. OPTION 3
SELECT BY NUMBER OR TYPE Q TO QUIT ? 3?
This is HELP text for option 3.
4-50 60459680 D
![](asset-83.png)
SAMPLE MENU
1. OPTION 1
2. OPTION 2
3. OPTION 3
SELECT BY NUMBER OR TYPE Q TO QUIT ? 1. finally
YOU CHOSE OPTION 1 FINALLY.
/menu,2
YOU CHOSE OPTION 2.
ENDING A PROCEDURE (REVERT COMMAND)
The REVERT command terminates procedure processing.
Format:
REVERT,opt.com
opt Controls the revert options and whether the REVERT command appears at
the terminal and in the job dayfile.
opt Meaning
ABORT Returns control to the next EXIT command in the command
record unless a NOEXIT command has been processed.
This parameter sets EF=CPE (CPU abort). It returns
control to the command following the calling BEGIN
command if a NOEXIT command has been processed. This
parameter causes the REVERT command to appear at the
terminal and in the job dayfile.
EX Returns control to the command record of the calling
procedure and executes the command com as if the
command had actually appeared in the calling
procedure. The EX parameter causes the REVERT command
to appear in the job dayfile but not at the terminal.
NOLIST Returns control to the command following the calling
BEGIN command and suppresses the display of the REVERT
command at the terminal and in the dayfile.
If you omit opt, control returns to the command following the calling
BEGIN command. The REVERT command appears in the job dayfile but not
at a terminal unless you are under the batch subsystem and the REVERT
is not within a nested procedure call.
Specifies a comment unless used with the EX parameter. In this case,
com must be a command.
The system always appends the following commands to a procedure record.
$RE VERT. CCL
SEXIT.CCL
SREVERT, ABORT. CCL
These commands terminate procedure processing if no user-supplied REVERT commands are
processed.
/0^°\,
60459680 E 4-51
![](asset-84.png)
Example:
The following procedure (REVTST) is on a file called PROCFL. It reverts to the job calling
it if the named file has no read permission and aborts (causing control to be transferred to
the job EXIT command) if the named file has no read modify permission.
.PR0C,REVTST*I,LFN1,LFN2.
.IF,FILE(LFN1,RD),LABELL
TDUMP,I=LFN1.
.ELSE, LABELL
REVERT.NO READ PERMISSION
,ENDIF,LABEL1.
.IF,FILE(LFN1,RM),LABEL2.
C0PY,LFN2,LFN1.
,ELSE,LABEL2.
REVERT,ABORT. NO READ/MODIFY PERMISSION
.ENDIF,LABEL2.
The following two jobs (REVJOB1 and REVJ0B2) call the REVTST procedure,
execute-only file; REVJ0B2 attaches a read or execute file.
REVJOB1 attaches an
REVJ0B1.
USER,USERNAM,PASSWRD,FAMNAME.
ATTACH,FILE1/UN=ALTUSER,PW=PW1,M=E.
BEGIN,REVTST,PR0CFL,FILE1,XFIL.
COMMENT. RETURNS HERE
EXIT.
COMMENT. EXIT ON ERROR
REVJ0B2.
USER,USERNAM,PASSWRD,FAMNAME.
ATTACH,FILE2/UN=ALTUSER,PW=PW2,M=R.
BEGIN,REVTST,PR0CFL,FILE2,XFIL.
COMMENT. RETURNS HERE
EXIT.
COMMENT. EXIT ON ERROR
The following are the dayfile segments produced by REVJOB1 and REVJOB2. REVJOB1
processes the REVERT command and terminates normally. REVJ0B2 processes the
REVERT,ABORT command and terminates by error processing.
17.03.53.REVJ0B1.
17.03.53.USER,USERNAM„FAMNAME.
17.03.53.CHARGE,*.
17.03.53.* CHARGE(1514,5612PAY)
17.03.56.ATTACH,FILE1/UN=ALTUSER,M=E.
17.03.56.BEGIN,REVTST,PR0CFL,FILE1,XFIL.
17.03.56.REVERT.N0 READ PERMISSION
17.03.56.COMMENT. RETURNS HERE
17.03.56.EXIT.
17.05.05.REVJ0B2.
17.05.05.USER,USERNAM„FAMNAME
17.05.05.CHARGE,*.
17.05.05.* CHARGE(1514,5612PAY)
17.05.13.ATTACH,FILE2/UN=ALTUSER,M=R.
17.05.13.BEGIN,REVTST,PR0CFL,FILE2,XFIL.
17.05.13.TDUMP,I=FILE2.
17.05.13. TDUMP COMPLETE.
17.05.13.REVERT,AB0RT. NO READ/MODIFY
PERMISSION
17.05.13.EXIT.
17.05.13.COMMENT. EXIT ON ERROR
4-52 60459680 H
![](asset-85.png)
PARAMETER MATCHING MODES
When you call a procedure, the system must match each parameter on the BEGIN command with a
parameter on the procedure header. The system uses two methods of parameter matching,
order-dependent and order-independent.
ORDER-DEPENDENT MODE
In order-dependent mode, the system compares in order each parameter on the procedure call
with the parameter in that position on the procedure header. If any parameter entries do
not conform to the restrictions in the parameter checklist or required parameters are
omitted on the procedure call, the system prompts you for them. After all required
parameters are entered, the system substitutes the selected keywords into the procedure body
according to the checklists in the .PROC directive.
Example:
Procedure ITEM is on a global library file:
.PROC, ITEM*I,F"LOCAL FILE NAME"= (*N=LG0,*F),
L"NAME OF LIST OUTPUT FILE"= (*N=OUTPUT,*F),
BL"EACH FILE START ON NEW PAGE? YES OR N0'^= (YES=$,BL$,N0=,*N=),
NR"REWIND BEFORE & AFTER? YES OR N0"= (YES=,N0=$,NR$,*N = ).
IT EM IZ E, F, #L =L_BL_N R.
REVERT.
The procedure is called:
ITEM,LIST,,NO,NO.
The parameters are matched in order-dependent mode and the procedure body becomes:
ITEM IZE,LIST,L=OUT PUT, NR.
REVERT.
In order-dependent mode, the system treats excess parameters on the BEGIN command as a
nonfatal error.
ORDER-INDEPENDENT MODE
For each BEGIN command, parameter matching always starts in order-dependent mode. The
system switches to order-independent mode if, in the comparison of a BEGIN command parameter
and a procedure header parameter, one of the following occurs.
• A parameter on the procedure call is in the format keyword=value.
• A reverse slant (\) precedes the parameter on the .PROC directive or the BEGIN
command.
• A slant (/) precedes the parameter on the .PROC directive.
• A slant precedes the parameter on the procedure call and a slant separates any two
parameters on the .PROC directive.
60459680 D 4-53
![](asset-86.png)
However, if a slant is specified on the procedure call and not on the .PROC directive, the
slant is not treated as a separator, but as part of the parameter value.
Parameter matching mode cannot switch back from order-independent to order-dependent mode.
Once in order-independent mode, the system matches each successive keyword on the procedure
call or interactive entry to the identical keyword in the procedure header directive,
regardless of the order of the procedure header parameters or the order of specification on
the procedure call.
To show order-independent parameter matching, the preceding example is slightly modified.
An *K entry has been added to the BL parameter checklist to make BL a valid parameter
entry. A reverse slant is used as a separator before the NR parameter to ensure
order-independent mode.
.PR0C,ITEM1*I,F"L0CAL FILE NAME"=(*N=LGO,*F), "^
L"NAME OF LIST OUTPUT FILE"= C*N=OUTPUT,*F), •
\NR"REWIND BEFORE & AFTER? YES OR NO"=(YES=,NO=$,NR$,*N=),
BL"EACH FILE START ON NEW PAGE? YES OR N0"=(YES=$,BL$,N0=,*N=,*K=$,$8L).
ITEMIZE,F,#L=L_BL_NR.
REVERT.
The procedure call (ITEM1 is on a global library file):
ITEM1,LIST„BL,NR=N0.
starts parameter matching in order-dependent mode. The reverse slant in the procedure "cS^\
header switches parameter matching to order-independent mode. BL and NR are matched in
order-independent mode. In order-independent mode you must specify all parameters in the
form keyword=value, unless there is an *K entry in the parameter checklist. Then you can
specify just the keyword as the parameter entry. Since *K is specified in the BL parameter
checklist, the system accepts BL as a parameter entry. The NR parameter must be specified
as NR=value or omitted.
After the substitution, the procedure body becomes
ITEMIZE,LIST,L=OUTPUT,BL,NR.
REVERT.
4-54 60459680 H
Ar€Stj^>^
![](asset-87.png)
COMMAND PROCESSING
Global Library File Commands
System Commands
Jobs entering the system consist of one or more logical records. The first logical record
contains system directives (commands) which describe the processing that is to occur in the
job file. In interactive jobs, you enter the commands directly at the terminal. This
section describes command processing and how the commands affect other aspects of job
processing.
The operating system recognizes four types of commands.
• Local File Commands These commands call programs or procedures on
files that are assigned to the job. The name of
the command is simply the name of the file. LGO
is an example. It is the system default local
file used for retaining object code generated by
one of the language processors.
These commands call programs or procedures on
files that have been specified in a LIBRARY
command.
These commands are divided into 10 categories.
Flow control commands
Job control commands
Special commands for interactive jobs
File management commands
Permanent file commands
Load and dump central memory commands
Tape management commands
System utility commands
Librar y uti li ty comman ds
Loader commands*
The product set commands call the various products
available under NOS. Their formats are given in
the applicable product reference manual and in the
NOS 2 Applications Programmer's Instant.
Since your executing programs can access the command record of your job, it is possible that
they might manipulate items like user names and passwords. Hence, your executing programs
can affect system security.
Product Set Commands
tRefer to the CYBER Loader Reference Manual.
60459680 D 5-1
![](asset-88.png)
COMMAND FORMAT
All commands consist of from one to four fields. The first field is optional. It is a $ or
/ prefix character which precedes the program name. If a $ is present, it indicates that
the specified program to be executed must be loaded from the system library. Therefore,
even if a local file of the same name is present or a program or procedure of the same name
resides on one of your global library files, the system program, not the local program or
global library program, is executed. In all interactive subsystems except the batch
subsystem, the system places a $ in the first field of all commands. Even in the batch
subsystem, the system places a $ in front of the file editing commands ALTER, DELETE, DUP
LIST, MOVE, READ, WRITE, and WRITEN. '
If you use a slant in the first field of local file or global library file commands, the
system processes the parameters in operating system format. For global library file
commands, the presence of an NPC= entry point in the specified library also forces the /ss^
system to process the parameters in operating system format (refer to Volume 4, Program J
Interface). Otherwise, the system processes local file and global library file commands in
product set format.
The slant option is ignored for command calls to programs residing on the system library.
For those types of calls, parameters are processed in the operating system format unless the
SC directive of SYSEDIT has been entered. Refer to the SYSEDIT command in the NOS 2 System
Maintenance Reference Manual for a description of the SC directive.
Example:
If file EXTRACT is a local file and you enter /*^\
/EXTRACT, A,B, 10.
the system treats the file as a local file command. The parameters are processed in
operating system format because of the leading slant.
The second field contains the name of the program to be executed. The command name can be
any valid file name.
The third field (optional) contains parameters which further define the operation to be ^.
performed. The parameter field is set off from the name field by a separator character. A "*^\
valid terminator character must follow the third field (or the second field if no parameters '
are present). In interactive jobs, the terminator is optional.
The fourth field consists of a comments field. The comments field follows the terminator.
In general, the system ignores this field. However, some commands (MODIFY, FSE, GTR
LIBEDIT, and the like) read this comments field for directives. '
In general, commands may not be continued beyond a single line. Exceptions are the
execution control commands (described in section 6) and tape management commands (described
in section 12).
Global library file commands containing an ARG= entry point (ARG= is described in Volume 4,
Program Interface) are not required to follow either the operating system or product set
format. The only syntax requirements enforced by the system for these commands is that the
command name must be a valid file name followed by a separator. The command itself may have
additional syntax requirements.
The following is a comparison of the operating system and product set formats (refer to the >d5s.
NOS 2 Applications Programmer's Instant for commands using the product set format). /^\
5-2 60459680 E
![](asset-89.png)
0^\
Operating System Format
1. Valid separators are
+ - " / = , (
and any other character with a display
code value greater than 44g except
* ) $ . and blank.
2. Valid terminators are
. )
3. Letters, numbers, and the * are
the only characters allowed in the
parameter field. The one exception
to this rule is the use of literals
(that is, character strings delimited
by dollar signs). Characters other
than letters, numbers, and the * can
be included in literals. No char
acters within a literal have special
meanings; the system merely checks
the syntax of the literal. The
called program must do its own
processing of the literal.
4. All embedded blanks within a command
except those appearing in literals
are ignored.
5. Comments may appear on the command
but they must follow the terminator.
They may contain any character.
Comments are not printed for some
commands.
6. Parameters, s eparators, an d termi
nators are stored in the job's field
length beginning at RA+2. The char
acters , . and ) are stored as binary
zero. For all parameters and all valid
separators except the comma, their dis
play code equivalent is stored. Refer
to section 10 of Volume 4, Program
Interface, for more information.
Product Set Format
1. Same as for the operating system
format.
2. Same as for the operating system
format.
3. Same as for the operating system
format.
4. Same as for the operating system
format.
5. Same as for the operating system
format.
6. Parameters are stored in their dis
play code equivalent beginning at
RA+2. Separators and terminators are
stored as follows:
Character
>((SWSy
Code (Octal)
1
2
3
4
5
6
60459680 E 5-3
![](asset-8a.png)
Operating System Format Product Set Format
Character Code (Octal)
»10
) or . 17
Other valid 16
separators
7. File names are one to seven alpha
numeric characters.
8. Not NOS/BE compatible.
Refer to section 10 of Volume 4,
Program Interface, for more
information.
7. File names are one to seven alpha
numeric characters. In some products,
file names beginning with a numeric
character are invalid.
8. NOS/BE compatible.
,^s>!\
In general, no parameter can contain more than seven characters. The exceptions include
procedure calls, flow control commands, some tape management commands and system or global
library file commands with an ARG= entry point.
Depending on the program, the parameters can appear in either order-dependent or order-
independent format. Order-dependent parameters are required when the parameters must be
passed in a specific order. An example of order-dependent parameters is:
RESEQ,MYFILE,B,,20.
In this example, the system expects the resequencing increment to be passed as the fourth
parameter; therefore, a separator must be present for the parameter not specified.
Order-independent parameters may be passed in any order. This is made possible by the use
of keywords. A keyword is an identifier which* has meaning either by itself or when used in
conjunction with an option. Usually, keywords are passed with an option and a separator.
The separator must not be a comma. When the list of parameters is passed to the called
program, all separators except commas are also passed.
Some programs require specific separators (usually =), and others merely require that a
separator be present. Examples of keyword notation are:
1. C0B0L5,I=SFILE,B=BFILE.
2. C0B0L5,B=BFILE,I=SFILE.
3. C0B0L5,L=0,E,EL.
4. J0BX,T10,CM45000.
In examples 1 and 2, both parameters and separators are passed to the COBOL 5 compiler.
Since these parameters are order independent, both commands produce the same result.
In example 3, two keywords are passed with no separator character. In example 4, the
keyword is the first character of the first parameter and the first two characters of the
second parameter.
5-4 60459680 E
![](asset-8b.png)
The parameters and an image of the command being processed are written in the iob
communication area (refer to section 10 of volume 4). The job communication area is the
first J008 words of your job's field length, from RA through RA+77r. Section 1 and
appendix E in Volume 4, Program Interface, describe the fi?st lOOgwords of ?his area.
The following commands produce the same image in the job communication area,
are processed using operating system format. Both commands
PERMIT,FILEABC,USERAAA=R,USERBBB=W.
$PERMIT,FILEABC,USERAAA=R,USERBBB=W.
COMMAND PROCESSING FLOW
The system translates a command by:
1. Reading the command from the job's command record.
2. Verifying the format of the command as described in Command Format.
3. Comparing special command names with the name of the command being processed. If
the command name is CTIME, HTIME, RTIME, *, or STIME, the system processes the
command. r
4.
5.
6.
7.
8.
9.
Searching the file name table for a file assigned to the job with a name identical
to the name of the command. However, if a $ precedes the program name, this step is
skipped. If an identical name is found, the program is loaded into memory. The
arguments are extracted from the command and stored in RA+2 through RA+n+1 (n is the
number of parameters) unless the command is a system or global library file command
with an ARG= entry point. The CPU is requested to begin execution unless special
loader commands follow.
Searching the global library directory for a program name that matches the command
name. If a $ precedes the command name, this step is skipped. If the program is
found, the system proceeds as in step 4; otherwise, the system searches further.
Searching the central library directory for a program name that matches the command
name. If the name is found, the system proceeds as in step 4; otherwise, the system
searches further.
Searching the peripheral processor library directory for a program name that matches
the command name if the command name is a three-character name with the first
character alphabetic. If found, the name is placed, with a maximum of two
arguments, as a peripheral processor request, and the system exits to the program.
If the command name is not found during any of the above searches, the command is
declared invalid and the job is aborted.
A command is normally echoed to the dayfile except for system commands or global
library commands containing an SDM= entry point in the entry point list.
Figure 5-1 illustrates the flow of command processing.
60459680 E 5-5
![](asset-8c.png)
READ A
COMMAND
KD
COMMAND PROCESSOR
SEARCHES ITS LIST OF
COMMAND NAMES FOR
SPECIAL COMMAND
PROCESS
SPECIAL
REQUEST
SEARCH GLOBAL
LIBRARY SET FOR
COMMAND NAME
USE NOS FORMAT
FOR PROCESSING
PARAMETERS
SEARCH PP LIBRARV
FOR NAME. IF NAME
IS VALID PP
PROGRAM NAME
SEARCH FNT FOR
FILE ASSIGNED TO
THIS JOB
USE NOS FORMAT
FOR PROCESSING
PARAMETERS
_J
PROCESS FIELD
LENGTH CONTROL
(SEE SECTION 3)
LOAD PROGRAM
TO CENTRAL
MEMORY
STORE COMMAND
AND COMMAND
ARGUMENTS IN
JOB'S FIELD
LENGTH
EXECUTE
PROGRAM
PLACE NAME WITH
UP TO TWO OCTAL
ARGUMENTS AS A
PP REQUEST
EXIT TO PROGRAM \
(NO FL CHANGE) J
Figure 5-1. Command Processing Flow
5-6 60459680 C
![](asset-8d.png)
/^X
EXIT PROCESSING
When an error condition occurs during a job, the system searches the command record for an
EXIT command.* If the record does not contain an EXIT command, the system terminates the
job if the job is not interactive or returns control to the terminal if the job is
interactive. If the system finds an EXIT command, it clears the error condition and
processes the commands that follow the EXIT command. If the error was a time limit error,
the limit is reset to the time used plus eight seconds. This gives you time for post-error
cleanup operations. If the error was an SRU limit error, the limit is reset to the SRUs
used plus eight SRUs.
If a NOEXIT command has been processed, normal error processing is not performed. That is,
if the no exit flag has been set by the NOEXIT command prior to the error, the error flag is
cleared, no search is made for an EXIT command, and processing continues with the next
command. An ONEXIT command can be used to return to error processing mode; it clears the no
exit flag.
The following sequence of commands illustrates this exit processing.
JOBCCC.
USER,SMITH22,SMAL
NOEXIT.
GET,A,B.
ONEXIT.
ATTACH,MASTER/M=W.
SKIPEI,MASTER.
COPYBF,A,MASTER.
COPYBF,B,MASTER.
PACK,MASTER.
COPYSBF,MASTER.
EXIT.
ENQUIRE,F.
-EOR-
-EOI-
This job attempts to make local copies of two indirect access permanent files and adds them
to a direct access file. The NOEXIT command suspends error processing, and the job
continues even if file A or B is not found. The ONEXIT command turns error processing back
on. If any error occurs thereafter, processing skips to the EXIT command and continues with
the ENQUIRE command. If no error occurs after the ONEXIT command, processing continues
until reaching the EXIT command and then the job terminates (ENQUIRE command is not
processed).
r*After a security conflict, the system does not always allow EXIT processing. Refer to
Security Features in section 3.
/fSN
60459680 E 5-7
![](asset-8e.png)
/^%
![](asset-8f.png)
FLOW CONTROL COMMANDS
0$®$*\
Flow control commands control the processing sequence of commands within the command record
of a job. They can insert commands from a procedure file, conditionally or unconditionally
skip commands, and control error processing. To determine the conditions for transfer of
control, you can use error flags, file attributes, or other job attributes. The flow
control commands and a brief description of each appear in the following list:
Command Description
BEGIN Initiates processing of a procedure.t
DISPLAY Evaluates an expression and displays the result in the dayfile of the
job.
E L S E Te r m i n a t e s s k i p p i n g i n i t i a t e d b y a f a l s e e x p r e s s i o n w i t h i n a n I F c o m m a n d
or initiates skipping to a matching ENDIF command.
ENDIF Terminates skipping initiated by a matching IF, SKIP, or ELSE command.
ENDW Establishes the end of the loop.
E X I T C o n t r o l s t h e c o m m a n d fl o w i n t h e e v e n t o f e r r o r s .
IF(or IFE) Conditionally skips one or more commands.
M O D E S p e c i fi e s t h e t y p e o f e r r o r s t h e s y s t e m r e c o g n i z e s f o r E X I T p r o c e s s i n g .
NOEXIT Disables EXIT error processing.
O N E X I T E n a b l e s E X I T e r r o r p r o c e s s i n g .
REVERT Returns processing from a procedure to the command record of procedure
that called it.
SET Assigns values to special symbolic names.
SKIP Skips to the first matching ENDIF command.
WHILE Establishes the beginning of a loop. If the associated expression is
true, the loop is processed; if it is false, the loop is not processed.
T Section 4 contains a detailed description of this command.
60459680 D 6-1
![](asset-90.png)
COMMAND SYNTAX
The syntax for these commands is similar to the syntax of all other commands as described in
section 5. However, these are some significant differences.
• Functions, arithmetic expressions, relational expressions, and logical expressions
can appear in parameters of certain commands.
• A right parenthesis ending an expression within a command cannot also serve as the
command terminator. You must include an additional right parenthesis or period to
terminate the command.
• Parentheses can nest expressions within expressions.
• A parameter can consist of more than seven characters.
• A command can be longer than 80 characters if its parameter specifications require
such. It can extend over more than one line if each line to be continued contains
no more than 80 characters and ends with a separator.
The following subsections describe the command syntax, including the operators, operands,
and functions which make up valid expressions. Following that is a discussion of each
command.
OPERATORS
Operators separate operands in a expression. There are four types of operators:
arithmetic, relational, logical, and string. Operators are used in the expressions within
the IF, WHILE, DISPLAY, and SET commands and the FILE, STR, STRB, and STRD functions.
ARITHMETIC OPERATORS
Integer arithmetic is used in each step of the evaulation of an expression. Division,
multiplication, and exponentiation produce a zero result if the absolute value exceeds ^^k
2 -1. The accuracy of computations depends on whether the operands are binary or /
decimal. Binary operands (specified using a postradix of B) are restriced to 9 digits not
including the postradix; results involving binary operands are restricted to 16 digits.
Decimal operands and displayed decimal results are restricted to 10 digits (the system
interprets each digit as a 6-bit quantity). For both binary and decimal operands, overflow
is ignored.t
tlf an operand is one of the symbolic names Rl, R2, R3, or RIG; there are further y^a3^\
restrictions. Refer to the SET command in this section. )
6-2 60459680 H
![](asset-91.png)
The following are t he a rith meti c op era tors .
Operator
+Addition.
-Subtraction.
*Multiplication.
/Division.
** Exponentiation.
Leading - Negati on . Th is ope rato
Leading + Ignored.
Operation
RELATIONAL OPERATORS
A relational operator produces a value of 1 if the relationship is true, and 0 if it is
false. The following are the relational operators (either form may be used).
Operator Operation
.EQ. Equal to.
^ . N E . Not equal to.
< . L T . Less than.
> . G T. Greater than.
_< .LE. Less than or equal to.
> . G E . Greater than or equal to.
60459680 H 6-3
![](asset-92.png)
LOGICAL OPERATORS
When an expression contains a logical operator, the system evaluates all bits of each
operand. Each bit of the first operand is compared to the corresponding bit of the second
operand. If the comparison is true, the corresponding bit in the result is set to 1. If
the comparison is false, the corresponding bit in the result is set to 0. The operator
.NOT. is a special case, operating on a single operand, if the operand is nonzero, the
corresponding bit is set to 0. If the operand is 0, the corresponding bit is set to 1.
If neither of the operands in a logical operation is a string operand, the result of a
logical operation is a 60 bit quantity. If one or both is a string operand, the result of
the logical operation is a string whose length depends upon the result of the operation.
The shorter of the two strings is logically extended with binary zero-fill to the length of
the longer string for the logical operation, and trailing binary zero characters are
tru ncat ed fr om the resul t stri ng.
Operator Operation
•EQV. Equivalence (complement of the logical sum).
.OR. Inclusive OR (logical sum).
.AND. AND (logical product).
• X O R . E x c l u s i v e O R ( l o g i c a l d i f f e r e n c e ) .
. N O T . N O T .
STRING OPERATORS
String operators operate on string operands. A string operand is the result of one of the
functions STR, STRB, STRD, or of a logical operation involving one or more string operands.
Operator Operation
// .CAT. Concatenation of two strings into one string. (Either // or .CAT. may
be used.)
Example:
.PR0C,CATTER*I,P1=(*A),P2=(*S3/D).
,IF,STR($P1$,1,4)//STRD(P2,-1).EQ.$G00D1$,G0.
NOTE./THE 1ST 4 CHAR OF P1 ARE GOOD AND P2 ENDS IN 1
.ELSE,G0.
REVERT,EX.DISPLAY,STR($SORRY, P1 IS NOT GOODS).
.ENDIF,GO.
In this example, two substrings were concatenated to produce one string in the .IF
expression. If GOODY and 101 were supplied as values for PI and P2, the .IF statement would
be true, and the NOTE command would be included and executed. If BADNEWS were substituted
for PI, the .IF statement would be false, resulting in the execution of the REVERT command
and then of the DISPLAY command.
^^
6-4 60459680 H
![](asset-93.png)
ORDER OF EVALUATION
The order in which operators in an expression are evaluated is:
1. Exponentiation.
2. Multiplication, division.
3. Addition, subtraction, negation, concatenation.
4. Relations.
5. NOT.
6. AND.
7. Inclusive OR.
8. Exclusive OR, equivalence.
Operators of equal order are evaluated from left to right.
OPERANDS
One or more operands separated by operators make up an expression. Expressions are used
within the IF, WHILE, DISPLAY, and SET commands. An expression within an expression must
begin with a left parenthesis and end with a right parenthesis. There is no limit on the
length of an expression, except that a period or a right parenthesis (not acting as a
command terminator) must appear within the first 50 operands. Expressions can contain
operands of one or more types. There are three types of operands: constants, symbolic
names, and functions.
CONSTANTS
A constant is a string of 1 to 10 characters that the system processes as an integer. The
constant can be a numeric string or a literal.
Numeric Strings
Each character in the string must be a digit (0 through 9), except the final character. The
final character can be a postradix of D or B to indicate the number base of the constant. A
postradix of B denotes an octal integer. D or an omitted postradix denotes a decimal
integer.
Literals
A literal is a $-delimited string of characters or a string containing a $-delimited
string. The literal can be a null string ($$). The maximum length for a literal is 10
characters, unless it appears within the STR function, in which case it may be any length up I
to the maximum length of the line. I
60459680 H 6-5
![](asset-94.png)
Special characters can appear in literals but they must appear in the $-delimited portion of
the string. To represent a dollar sign within a literal, you must use double dollar signs.
Valid Literal Invalid Literals
$LITERAL1$ LITERAL1
$5LITERAL$ $LITERAL2
$*LITERAL$ LITERAL3$
$$$LITERAL$ *$LITERAL$
$$$$ $$*LITERAL$
$$LITERAL$ 1
$$$
When a literal appears as an operand in a command, a function, or an expression, the system
processes it as an integer whose value is equal to the display code representation of the
literal value rather than as a character string.
A non-numeric string that appears in an expression to be evaluated must be entered as a
literal; otherwise, the system treats it as an erroneous symbolic name.
Example: "s^.
/IF,AFILE.EQ.AFILE,LABEL.
CCL157- UNKNOWN NAME - AFILE
The above command will execute successfully if the file names are entered as literals
(that is, as integer values):
/IF,$AFILE$.EQ.$AFILE$,LABEL.
When you instruct the system to display the value of a literal string, the system
right-justifies the display code value of the string. If the string is the result of the ^\
STR, STRB, or STRD function, it is left-justified and displayed as a character string. '
Example:
/display,$Lit$
49748 141124B
/display,$a$
1 1 B
/display,1
1 1 B
/display,$1$
2 8 3 4 B
/display,$$$$
4 3 5 3 B
/display,literal
CCL157- UNKNOWN NAME - LITERAL
/display,STR(SREALLY A STRINGS).
REALLY A STRING
/ -^^Sv
6 6 6 0 4 5 9 6 8 0 H
![](asset-95.png)
yfflS?^
Name Description
PW Page width (default=136 characters, minimum=40, maximum=255).
PD Page density (default=6 lines per inch; allowable values are 6 or 8),
SC Your job's service class.
S L Te r m i n a l d i s p l a y m o d e ( 0 = l i n e , l = s c r e e n ) .
S S Yo u r c u r r e n t s u b s y s t e m f o r i n t e r a c t i v e j o b s .
TIME Current time of day in the form hhmm.
VER Operating system version number (6-bit display code).
WEEKDAY The day of the week returned as a numerical value.
M O N M o n d a y ( n u m e r i c a l v a l u e = 1 ) .
T U E T u e s d a y ( n u m e r i c a l v a l u e = 2 ) .
WED Wednesday (numerical value - 3).
THU Thursday (numerical value =4).
FRI Friday (numerical value =5).
SAT Saturday (numerical value =6).
S U N S u n d a y ( n u m e r i c a l v a l u e = 7 ) .
60459680 E 6 - 6 . 1 / 6 - 6 . 2
![](asset-96.png)
![](asset-97.png)
As noted in the previous example (DISPLAY,LITERAL), nonnumeric strings that are not
$-delimited cannot appear as operands. If they appear as such, the system treats them as
erroneous symbolic names. You can, however, use such strings as parameter values for
procedures.
r
/gpN
SYMBOLIC NAMES
A symbolic name is a system-defined string of characters to which the system or you can
assign a value. The symbolic names represent job or system attributes. You can ascertain
and sometimes change these attributes by using these symbolic names (refer to the various
commands and functions described later in this section).
Most symbolic names have an initial value of zero. The exceptions are shown in the
following list:
Name Description
CSET Terminal character set mode (NORMAL=0 or ASCII=1).
CS Connection status.
D AT E T h e d a t e i n t h e f o r m y y m m d d .
D A Y T h e d a y o f t h e m o n t h .
DAYS Number of days since January 1, 1977.
HID Two-character machine identifier (6-bit display code).
MONTH The month of the year.
NWK Terminal network connection.
OT Your job's origin type.
PD Page density (default=6 lines per inch; allowable values are 6 or 8).
PL Page length (default=60 lines, minimum=!16, maximum=255).
PS Page size (same as page length).
PW Page width (default=136 characters, minimum=40, maximum=255).
SC Your job's service class.
SL Terminal display mode.
S S Y o u r c u r r e n t s u b s y s t e m f o r i n t e r a c t i v e j o b s .
TIME Current time of day in the form hhmm.
VER Operating system version number (6-bit display code).
VERCCL CYBER control language release level displayed as a numeric value.
WEEKDAY The day of the week returned as a numerical value.
60459680 H 6-7
![](asset-98.png)
The following lists contain the valid symbolic names and a brief description of each. The
lists do not contain the symbolic names you can use with the FILE and DT functions. Those
symbolic names appear with the descriptions of the functions.
• Symbolic names whose values are passed to, but not from, a procedure (refer to
section 4). When a procedure reverts, they are restored to the values they held
when the procedure was called.
Name Description
DSC Flag determining whether skipped commands are entered in the
dayfile (refer to SET Command in this section).
EF Previous error flag.
Rl Control register 1 contents.
R2 Control register 2 contents.
R3 Control register 3 contents.
• Symbolic names whose values you can set with SET command or the SETJCI macro (refer
to Volume 4, Program Interface).
Name Description
DSC Flag determining whether skipped commands are entered in the
dayfile.
EF Previous error flag.
EFG Global error flag.
EM Current exit mode (refer to MODE Command, later in this section).
Rl Control register 1 contents.
RIG Global control register 1 contents.
R2 Control register 2 contents.
R3 Control register 3 contents.
S S S u b s y s t e m f o r a n I n t e r a c t i v e j o b .
/ ^ ^ V
6-8 60459680 H
![](asset-99.png)
Symbolic names whose values are set by the operating system.
0^\
Name
CMN
CS
CSET
DATE
DAY
DAYS
DSC
ECN
EF
FAMILY
FL
HID
MFL
MFLL
MONTH
NWK
OT
SC
SL
SPS
SPW
SPD
n
Description
Central memory RFL setting divided by 100g (refer to RFL Command
in section 7).
Connection status.
Terminal character set mode (NORMAL=0 or ASCII=1).
The date in the form yymmdd.
The day of the month.
Number of days since January 1, 1977.
Flag indicating that skipped commands are to be entered in the
dayfile.
Extended memory RFL setting divided by IOOO3 (refer to RFL
Command in section 7).
Previous error flag.
Current family name.
Current CM field length.
Two-character machine identifier (6-bit display code).
Maximum CM field length.
Maximum extended memory field length.
The month of the year. (January = 1, February = 2, etc.)
Network type; possible values for NWK are:
0 = Terminal not connected to NAM.
1 = Terminal connected to NAM/CCP.
2 = Terminal connected to NAM/CDCNET.
Job origin type.
Service class of the job.
Terminal display mode (LINE or SCREEN).
System page size (in lines).
System page width (in characters).
System page density (in lines per inch).
60459680 H 6 - 8 . 1 / 6 - 8 . 2
![](asset-9a.png)
![](asset-9b.png)
Name
SSM
Description
Operating system security mode (0 means unsecured. 1 means
secured).
SYS Host operating system.
TIME Current time of day (hhmm).
V E R O p e r a t i n g s y s t e m v e r s i o n n u m b e r ( 6 - b i t d i s p l a y c o d e ) .
WEEKDAY The day of the week (Monday = 1, Tuesday = 2, etc.).
• Symbolic name whose value is set by the calling or termination of a procedure.
Name Description
PNL Procedure nesting level (0 when processing the original command
record, 1 when processing a first level procedure, and so forth).
Its maximum value is 50.
Symbolic name whose value can be set by the termination of a procedure (refer to SET
Command in this section).
Name
EFG
Description
Global error flag.
Symbolic names with fixed values that can be compared with the error flag value (EF
or EFG) within an expression. These values correspond to error code values. In an
expression, you can check the error flag (EF) for a nonzero value; a nonzero value
indicates an error, and a zero value indicates no error. For detailed error
examination, you can compare EF with a particular symbolic name or its error code
value. You are encouraged to use the symbolic name, because the numeric values can
change in future releases of NOS. The following list contains the errors that allow
exit processing.
Name Value (Octal) Description
TIE User break 1.
TAE User break 2.
ARE Arithmetic error.
ITE SCP invalid transfer address.
PSE Program stop error.
PPE PPU abort.
60459680 H 6-9
![](asset-9c.png)
/^tf&w£$V
Name Value (Octal)
CPE
PCE 10
11
MLE 14
TLE 15
FLE 16
TKE 17
SRE 20
FSE 22
RCE 23
ODE 24
IDE 25
SPE 26
STE 27
ECE 30
RSE 31
SSE 32
RRE 34
OKE 35
DRE 37
RAE 40
JSE 41
SVE 42
SYE 43
PEE 44
SWE 45
Description
CPU abort.
PPU call error.
Reserved for installation.
Message limit.
Time limit error.
File limit error.
Track limit error.
SRU limit error.
Forced error; set by operator entry of ERR. under
DIS utility.
Job hung in auto recall.
Operator drop.
Idledown.
Reserved for your site.
Suspension timeout.
Extended memory parity error.
Recovered system (level 3).
Subsystem aborted.
Operator rerun.
Operator kill.
Deadstart rerun.
Recovery abort.
Job step abort.
S e c u r i t y c o n fl i c t .
System abort.
CPU parity error.
Software error.
6-10
^*ES\
60459680 G
![](asset-9d.png)
Name Value (Octal)
ORE
MXE
46
47
Description
Override error condition.
Maximum number of error flags.
Symbolic names with fixed values that can be compared with the job's connection
status (CS) value within an expression.
Name Value Description
NICS Not interactive.
DTCS Detached.
OLCS Online.
Symbolic names with fixed values that can be compared with the terminal character
set-mode (CSET) value within an expression.
Name
NORMAL
ASCII
Value
0
1
Description
Uppercase characters only.
Uppercase and lowercase characters.
Symbolic names with fixed values that can be compared with the month of the year
(MONTH) value within an expression.
Name Value Description
JAN January.
FEB February.
MAR March.
APR April.
MAY May.
JUN June.
JUL July.
AUG August.
SEP September.
OCT 10 October.
NOV 11 November.
DEC 12 December.
60459680 G 6-10.1
![](asset-9e.png)
Symbolic names with fixed values that can be compared to the terminal's network
connection (NWK) value within an expression.
Name Value Description
Terminal has no NAM connection.
Terminal is connected using NAM/CCP.
Terminal is connected using NAM/CDCNET.
Symbolic names with fixed values that can be compared with the origin type (OT)
value within an expression.
NONE
CCP
CDCNET
Name Value Description
BCO Local batch origin.
IAO I nte r a c ti v e o r i g in.
RBO Remote batch origin
SYO System origin.
Symbolic names with fixed values that can be compared with the service class (SC)
value within an expression:
Description
System service class.
Local batch service class.
Remote batch service class.
Interactive service class.
Detached interactive service class.
Network supervisor service class.
Subsystem service class.
Maintenance service class.
Communication task service class.
Installation service class 0.
Installation service class 1.
Installation service class 2.
Installation service class 3.
Deadstart service class.
Name Value
SYSC
BCSC
RBSC
TSSC
DISC
NSSC
SSSC
MASC 10
CTSC 11
IOSC 12
use 13
I2SC 14
I3SC 15
DSSC 77
6-10.2 60459680 G
![](asset-9f.png)
0^\
Symbolic names with fixed values that can be compared with the terminal display mode
(SL) value within an expression.
Name
LINE
SCREEN
Value
0
1
Description
Line mode.
Screen mode.
Symbolic name with a fixed value that can be compared with the host operating system
(SYS) value within an expression.
Name Value Description
Network Operating System.
Network Operating System/Batch Environment.
SCOPE 2 Operating System.
Symbolic names with a fixed value that you can compare with the subsystem for an
interactive job (SS).
NOS
NOSB
SC2
Name Value
ACCESS
BASIC
BATCH
EXECUTE
FORTRAN
FTNTS
NULL
Description
The access subsystem.
The BASIC subsystem.
The batch subsystem.
The execute subsystem.
The FORTRAN 5 subsystem.
The FORTRAN Extended 4 subsystem,
The null subsystem.
0^\
60459680 G 6-11
![](asset-a0.png)
Symbolic names with true or false values. True is 1; false is 0.
Name
F
FALSE
SWn
T
TRUE
Description
Fixed value of 0 (false).
Fixed value of 0 (false).
One of six sense switches (n can be from 1 to 6). Their values
are set by the OFFSW, ONSW, and SWITCH commands (refer to section
/) •
Fixed value of 1 (true).
Fixed value of 1 (true).
Symbolic names with fixed values that can be compared with the day of the week
(WEEKDAY) value within an expression.
Name Value Description
MON Monday.
TUE Tuesday.
WED Wednesday.
THU Thursday.
FRI Friday.
SAT Saturday.
SUN Sunday.
FUNCTIONS
Functions are used as expressions or operands within expressions in commands. Functions are
| not commands. The functions are FILE, DT, LEN, NUM, STR, STRB, and STRD.
FILE Function
| The FILE function determines whether a local file has a specified attribute. The system
returns a value of 1 (true) or 0 (false) depending upon whether the file has or does not
have the specified attribute(s). Only the equipment number (EQ) attribute can return values
othe r than 1 or 0. Th e lis t of fi le att ri but es fol low s the desc rip ti on o f the FILE fun cti on
format.
The FILE function must be used as an expression or as a part of an expression in a command.
A left parenthesis must appear before the file name, a comma must appear between the file
name and the expression, and a right parenthesis must appear after the expression.
6-12 60459680 H
/*S%v
![](asset-a1.png)
Format:
FILE(Ifn,expression)
Parameter
lfn
expression
/gptev
/S^^N
Description
Name of the local file for which attributes are being determined.
Either a special FILE function attribute or an expression, consisting
of logical operators and special FILE function attributes. The
expression must be appropriate for the command in which the FILE
function appears. If the FILE function is part of an IF command or
.IF directive, the expression should be one that can be evaluated as
true or false. If the FILE function is part of the DISPLAY command,
the expression could have a numeric value other than a true or false
value.
The expression within a FILE function cannot include the NUM function,
the symbolic name SS, or another FILE function; the DT function or the
following symbolic names can be used within the expression. Any other
symbolic name within the expression is treated either as an implicit
DT function (refer to DT Function which follows) or as an unidentified
variable.
Parameter Description
AP File has append permission.
AS File is assigned or attached to your job.
BOI File is positioned at BOI. This is effective only for
a file on mass storage.
EOF Last operation was a forward operation, which
encountered an EOF and is now positioned at that EOF.
This is effective only for a file on mass storage.
EOI Last operation was a forward operation, which
encountered an EOI and is now positioned at that EOI.
This is effective only for a file on mass storage.
EQ EST ordinal of the equipment on which the file
resides. If the file is not assigned to a device, it
has an EST ordinal of zero.
EX File has execute permission.
FS File size in PRUs.
GL File is a global library.
IN File type is input.
LB File is on a labeled tape.
LI File is a system library file.
60459680 H 6-13
![](asset-a2.png)
Parameter Description
LO File type is local.
MD File has modify permission.
MS File is on mass storage.
OP File is opened.
PM File is an attached direct access permanent file.
PT File type is primary.
Q F F i l e t y p e i s q u e u e d .
RA File has read append permission.
RD File has read permission.
RM File has read modify permission.
RU File has read update permission.
T P F i le i s o n m a g n e t i c t a p e.
TT File is assigned to a terminal. /B^t
UP F ile has upd a te p e rmi s sio n .
WR File has write permission.
Z L F i l e h a s z e r o l e n g t h .
Example:
The following job segment shows the FILE function being used inside an IF command. The FILE
function determines if file ACCT is not at the beginning-of-information (BOI). If ACCT is
not at BOI, the IF command is true and the system rewinds ACCT before copying it onto ITEM.
If ACCT is at BOI, the IF command is false and the system skips to the ENDIF command and
copies ACCT onto ITEM. In both cases, ACCT is copied to ITEM and is replaced.
IF,FILE( ACCT,.NOT.BOI),LABELL
REWIND,ACCT.
ENDIF, LABELL
COPY,ACCT,ITEM.
RE PLACE,ITEM.
DT Function
The DT function determines the device type on which a file resides. DT can be used only
within a FILE function. The value of the DT function is true if the two-character mnemonic
included in the function is equal to the two-character device type. The operating system
defines the mnemonics.
>*s^\
6-14 60459680 E
![](asset-a3.png)
Format:
FILE(lfn,DT(dt))
Parameter Description
lfn Name of the file for which device residence is being determined.
d t A t w o - c h a r a c t e r m n e m o n i c i d e n t i f y i n g t h e d e v i c e , w h i c h m a y b e a n y o n e
of the following:
Type Equipment
DB 885-42 Disk Storage Subsystem (full-track).
DC 895-1/2 Disk Storage Subsystem (full-track).
DD 834 Disk Storage Subsystem (full-track).
D E E x t e n d e d m e m o r y .
DF 887 Disk Storage Subsystem (4K sector; full track). |
DG 836 Disk Storage Subsystem (full-track).
DH 887 Disk Storage Subsystem (16K sector; full track). I
DI 844-21 Disk Storage Subsystem (half-track).
DJ 844-41/44 Disk Storage Subsystem (half-track).
DK 844-21 Disk Storage Subsystem (full-track).
DL 844-41/44 Disk Storage Subsystem (full-track).
DM 885-11/12 Disk Storage Subsystem (half-track).
DP Distributive data path to extended memory.
D Q 8 8 5 - 11 / 1 2 D i s k S t o r a g e S u b s y s t e m ( f u l l - t r a c k ) .
DV 819 Disk Storage Subsystem (single-density).
D W 8 1 9 D i s k S t o r a g e S u b s y s t e m ( d o u b l e - d e n s i t y ) .
MT Magnetic tape drive (seven-track).
NE Null equipment.
NT Magnetic tape drive (nine-track).
TT Interactive terminal.
60459680 H 6-15
![](asset-a4.png)
0*&$$\
Example:
The following dayfile segment shows that TAXES is on a nine-track magnetic tape, so it is
copied to output and then unloaded. If the DT function was false, TAXES would be unloaded
without being copied.
14.00.45.IF,FILE(TAXES,DT(NT)),LABL1.
14.00.46.COPY,TAXES,OUTPUT.
14.00.46.EOI ENCOUNTERED.
14.00.46.ENDIF,LABLL
14.00.46.UNLOAD,TAXES.
LEN Function
The LEN function returns the length of a specified string,
Format:
LEN(st ri ng )
Parameter
s t r i n g
Description
A string of any length up to the maximum length of a CCL line. If the
string is a literal, the length returned is the length of the string
after the removal of the surrounding dollar signs ($) and of any extra
dollar signs within the string.
NUM Function
The NUM function determines whether a character string is numeric. It evaluates the
character string as true (1) if it is numeric or false (0) if it is not. NUM must be used
as an expression or as part of an expression.
Format:
NUM(string)
Parameter
s t r i n g
Description
A string of 1 to 40 characters. If the string contains one or more
special characters, it must be delimited by dollar signs (for example,
$***$). if delimited by dollar signs, the string is always evaluated
as non-numeric.
Example:
The following procedure uses the NUM function to ensure that the passed parameter, NUMBER,
is numeric. If a non-numeric value is passed, the procedure terminates with an appropriate
message.
6-16 60459680 H
/ ^ ^ \
![](asset-a5.png)
.PROC,PR0C1*I,NUMBER.
.IF,NUM(NUMBER),QUIT.
WHILE,R1.LE.NUMBER,LOOP.
SET,R1=R1+1.
ENDW,LOOP.
REVERT. PROCESSING COMPLETED
.ENDIF,QUIT.
REVERT,ABORT. NONNUMERIC PASSED
STR Function
The STR function produces a left-justified string of any length up to the maximum CCL line
length. The STR function makes it possible to manipulate character strings greater than 10
characters in length. An STR function result may be compared or combined with the results
of STRB, STRD or other STR functions in a variety of ways.
Format:
STR(strexp,lc,rc)
Parameter
strexp
lc
Description
May be any legal CCL expression, usually but not necessarily a
literal. Literals are left-justified, and may be any length up to the
maximum line length. Nonliteral values are treated normally during
evaluation of the expression. However, a numeric result will be
left-justified and treated as a string.
Must be an expression producing a numeric result, either positive or
negative, lc indicates which character of strexp is to be the
leftmost character of the string produced by STR, counting from the
left if lc is positive or from the right if negative. A value of zero
or a negative value which exceeds the length of strexp is treated as
equivalent to 1. A positive value greater than the length of strexp
produces a null string, lc may be omitted if it would reference the
leftmost character of strexp and if re is also omitted. (The
preceding comma must also be omitted when lc is omitted.)
Must be an expression producing a numeric result, either positive or
negative, re indicates which character of strexp is to be the
rightmost character of the string produced by STR, counting from the
l e f t i f r e i s p o s i t i ve o r f r o m t h e r i g h t i f n e g a t i v e . A p o s i t i v e
value greater than the length of strexp is considered equal to the
length. A value of zero or a negative value which exceeds the length
of strexp produces a null string, re may be omitted if it would
reference the rightmost character of strexp. (The preceding comma
must also be omitted when re is omitted.)
In summary, lc and re both reference the string strexp in the same
way: a positive value of n indicates the nth character of strexp
counting from the leftmost character, 1 meaning the first character.
A negative value of -n indicates the nth character of strexp counting
from the rightmost character, -1 meaning the last character.
60459680 H 6-16.1
![](asset-a6.png)
Example:
The following expressions all produce the same result, the string $ABET$.
STR(SALPHABETAGS,5,-3)
STR($ALPHABETAG$,-6,8)
STR($ALPHABET$,5)
STRB Function
The STRB function produces a left-justified string of 1 to 17 characters
representing the octal value of a specified expression.
Format:
STRB(numexp,lc,rc)
Parameter
numexp
lc
Description
May be any legal CCL expression, usually but not necessarily numeric.
If numexp is or contains a literal, the literal is limited to no more
than 10 characters and will be right-justified and binary-zero filled
for evaluation.
The result produced by numexp is treated as a one-word signed value
and is converted to a character string in octal. For example, the
decimal value 25 for numexp would result in the string $31$.
Specifies which character of numexp is to be the leftmost in the
resulting string. For further explanation of this parameter, refer to
the description of the STR function.
Specifies which character of numexp is to be the rightmost in the
resulting string. For further explanation of this parameter, refer to
the description of the STR function.
/*^%K
Example:
Each of the following expressions will produce the string $102$.
STRB($ABC$,-5,-3).
STRB(10203B,-5,-3).
• 6-16.2 60459680 H
![](asset-a7.png)
STRD Function
The STRD function produces a left-justified string of 1 to 16 characters representing the
decimal value of a specified expression.
Format
STRD(numexp,lc,re)
Parameter
numexp
lc
Description
May be any legal CCL expression, usually but not necessarily numeric.
If numexp is or contains a literal, the literal is limited to no more
than 10 characters and will be right-justified and binary-zero filled
for evaluation. The result produced by numexp is treated as a
one-word signed value, and is converted to a character string in
decimal. For example, the decimal value 25 for numexp would result in
the string $25$.
Specifies which character of numexp is to be the leftmost in the
resulting string. For further explanation of this parameter, refer to
the description of the STR function.
Specifies which character of numexp is to be the rightmost in the
resulting string. For further explanation of this parameter, refer to
the description of the STR function.
Example:
The following expression produces a string of $0012$.
STRD(10000+36/3,-4).
COMMAND DESCRIPTIONS
Individual descriptions of the commands follow in alphabetic order,
BEGIN COMMAND
Refer to Calling a Procedure in section 4.
60459680 H 6- 16 .3 •
![](asset-a8.png)
DISPLAY COMMAND
The DISPLAY command evaluates an expression and sends the result to the job dayfile in both
decimal and octal integer form or in character string form, depending on the expression.
(If the expression is an STR, STRB, or STRD function or a concatenation thereof, the
resulting string is displayed as a character string; otherwise, the decimal and octal
integer format is used.) The largest decimal value which can be displayed is 10 digits. If
the value is larger than 10 digits, GT followed by 9999999999 is displayed. If the value is
negative and larger than 10 digits, LT followed by a minus and 9999999999 is displayed. In
octal code, numbers as large as 16 digits can be displayed. For an expression
larger than 2*8-1, zeros are displayed.
Format:
DISPLAY,expression^,expression, • • • ,expressionn.
Parameter Description
expression Specifies any valid symbolic name or expression described earlier in
this section.
Example:
The following sample dayfile shows several display operations.
12.53.18.DISPLAY/TIME.
12.53.18. 1253 2345B.
12.53.27.SET,R1,=99.
12.53.40.SET,R2,=901.
12.54.05.DISPLAY,R1.
12.54.05. 99 143B.
12.54.16.DISPLAY,R1+R2.
12.54.16. 1000 1750B.
12.55.09.DISPLAY,STR($N0W IS THE TIMES).
12.55.09.NOW IS THE TIME.
12.56.10.DISPLAY,STRB(R1+R2) .
12.56.10.1750.
12.56.26.DISPLAY,STRD(R1+R2). "^
12.56.26.1000. /
12.58.26.DISPLAY,STRB(R1+R2)/STR($B IS EQUAL TO S)//STRD(R1+R2).
12.58.26.1750B IS EQUAL TO 1000.
13.01.32.DISPLAY,STR($FIRSTRATE$,4,6)//STR($RINGER$,2,4).
13.0L32.STRING.
13.01.53.DISPLAY,3/2.
13.01.53. 1 1B
13.02.07.DISPLAY 2**47.
13!o2!07! GT 9999999999 4000000000000000B.
13.02.24.DISPLAY,-2**47.
13.02.24. LT -9999999999 -4000000000000000B.
13.02.38.DISPLAY,2**48.
13.02.38. 0 0B.
13.03.28.DISPLAY,99999999999.
13.03.28. CCL156- STRING TOO LONG - 99999999999
y * ^ \
6-16.4 60459680 H
![](asset-a9.png)
The first DISPLAY command displays the value of the symbolic name TIME. The current time
given is in the form hhmm. The next six lines demonstrate the use of the Rl and R2 symbolic
names. The next 10 lines illustrate the use of the STR, STRB, and STRD functions for ■
generating display character strings. The other DISPLAY commands specify numeric I
expressions. The integer constant in the final DISPLAY command has more than 10 digits,
resulting in an error message.
ELSE COMMAND
The ELSE command performs one of the following functions.
• It terminates skipping initiated by a false IF command whose label string matches
that of the ELSE command. If the label string does not match, the ELSE command is
skipped.
•It initiates skipping from the ELSE command to the ENDIF command whose label string
matches that of the ELSE command. This happens for a true IF command.
Neither a SKIP nor an ELSE command terminates skipping initiated by another SKIP or ELSE
command.
Format:
ELSE,label.
Parameter Description
label Specifies a 1- to 10-character alphanumeric string. The string must
begin with an alphabetic character.
Example:
The following commands use the FILE function to determine if a file named TEST1 is local to
the job. If the file is local, it is copied to the OUTPUT file; if it is not, it is assumed
to be an indirect access permanent file, and a local copy is obtained and copied to OUTPUT.
60459680 H 6-17
![](asset-aa.png)
If the file is local, each succeeding command, up to the ELSE command, is processed, and the
ELSE command initiates a skip to the ENDIF command. If the file is not local, control skips
to the ELSE command, and each command succeeding the ELSE command is processed.
I F,FILE(TEST1,L0),LABELL
C0PYSBF,TEST1,OUTPUT.
ELSE,LABEL1.
GET,TEST1.
C0PYSBF,TEST1,OUTPUT.
ENDIF,LABEL1.
The following dayfile segment results when the preceding commands are processed and TESTI is
not initially a local file.
11.33.00.1 F,FILE(TEST1,L0),LABELL
11.33.00. ELSE,LAB ELL
11.33.00.GET,TESTL
11.33.00.C0PYSBF,TEST1,OUTPUT.
11.33.01.END OF INFORMATION ENCOUNTERED.
11.33.01.ENDIF,LABEL1.
The following dayfile segment results when the preceding commands are processed and TESTI is
initially a local file.
15.40.19.IF,FILE(TEST1,LO),LABEL1.
15.40.19.C0PYSBF,TEST1,0UTPUT. tttmr
15.40.21. END OF INFORMATION ENCOUNTERED. y
15.40.21.ELSE,LABEL1.
15.40.21 .ENDIF,LABELL
ENDIF COMMAND
The ENDIF command terminates skipping initiated by a SKIP, IF, or ELSE command. In all
cases, the label string on the ENDIF command must match the label string on the command that
initiates the skipping. If the system encounters an ENDIF command with a nonmatching label
string, it ignores that command.
Format:
ENDIF,label.
Parameter Description
label Specifies a 1- to 10-character alphanumeric string. The string must
begin with an alphabetic character.
^\
y^&Sk
6-18 60459680 D
![](asset-ab.png)
0ftoi\
Example:
When the SKIP command in the following sequence of commands is processed, control skips to
ENDIF, and none of the commands between SKIP and ENDIF are processed.
SKIP,LABEL1.
commands
ENDIF,LABEL1.
ENDW COMMAND
The ENDW command identifies the end of the WHILE command loop. A command loop is a sequence
of commands that may be repeatedly processed. The number of times the loop is processed
depends on the evaluation of the expression specified in the WHILE command that begins the
loop.
The ENDW command must have a label string that matches the label string specified in the
WHILE command that begins the loop.
Format:
ENDW,label.
Parameter Description
label Specifies a 1- to 10-character alphanumeric string. The string must
begin with an alphabetic character.
Refer to WHILE Command in this section for an example of ENDW command use.
EXIT COMMAND
The EXIT command indicates the position in the command record where processing will resume
if an error is encountered prior to the EXIT command. If no error is encountered, the EXIT
command indicates where to terminate normal command processing.
When used in procedures, we recommend that the EXIT command be preceded by a SKIP or REVERT
command to prevent execution of the EXIT command in the case where no error occurs. An EXIT
command executed in this way terminates the executing procedure as well as all calling
procedures if nesting has occurred, but does not restore control registers to their previous
values.
Format:
EXIT.
For additional information, refer to the description of the NOEXIT and ONEXIT commands later
in this section and to the description of exit processing in section 5.
j$^&\
60459680 E 6-19
![](asset-ac.png)
IF (OR IFE) COMMAND
The IF command conditionally skips one or more commands.
Formats:
IF,condition.command.
IF,condition,label.
Parameter Description
condition Specifies an expression that is either true or false. The separator
following condition in the first format must be a terminator.
command Specifies a valid command.
label Specifies a 1- to 10-character alphanumeric string. The string must
begin with an alphabetic character. An identical string must appear in
a subsequent ELSE or ENDIF command.
The first format conditionally skips only the command specified within the IF command. If
condition is true, the system executes the specified command. If condition is false, the
system skips the command.
NOTE
When using the first format (IF,expression,
command.), values for .command, that match a
CCL relational, logical, or string operator
(such as .EQ. or .OR.) are interpreted as
operators, causing the procedure to abort.
To write a valid IF command when .command,
matches an operator, terminate the expression
or command with a right parenthesis instead
of a period.
The second format conditionally skips all commands between the IF command and the first
matching ELSE or ENDIF command (two commands match if their label parameters are
identical). If condition is true, the system executes all commands between the IF and the
matching ELSE or ENDIF. If condition is false, the system skips all intervening commands.
Example 1:
The following commands initiate the compilation and execution of a FORTRAN program and then
test for any errors during execution. If an error was made, the error code is displayed.
FTN5,I=IFTEST.
SET,EF=0. INITIALIZE ERROR FLAG
NOEXIT.
LGO.
ONEXIT.
IF,EF.NE.O.DISPLAY,EF.
If the job step executes without error, the error flag (EF) is 0. In this case, the DISPLAY
command is not executed. If an error occurs, the error flag is not 0, the condition is
true, and control passes to the DISPLAY command; the system then displays the error code in
the error flag register. (The NOEXIT and ONEXIT commands are described later in this
section.)
6-20 60459680 H
![](asset-ad.png)
In the following example, the FORTRAN program FTNPROG attempts to call a subroutine BETA
which does not exist (outside the field length of the job).' The commands that are used
appear first and the dayfile segment follows.
FTN5,I=FTNPR0G.
SET,EF=0. INITIALIZE ERROR FLAG
NOEXIT.
LGO.
ONEXIT.
IF,EF.NE.O.DISPLAY,EF.
12.57.02.FTN5,I=FTNPROG.
12.57.02. 61000 CM STORAGE USED.
12.57.02. 0.009 CP SECONDS COMPILATION TIME.
12.57.02.SET,EF=0. INITIALIZE ERROR FLAG
12.57.02.NOEXIT.
12.57.02.LGO.
12.57.03. NON-FATAL LOADER ERRORS -
12.57.03. UNSATISFIED EXTERNAL REF — BETA
12.57.03. MODE ERROR.
12.57.03. JOB REPRIEVED.
12.57.03. UNSATISFIED EXT IN FLAG NEAR LINE 2
12.57.03. 7500 MAXIMUM EXECUTION FL.
12.57.03. 0.000 CP SECONDS EXECUTION TIME.
12.57.03. RPV - PREVIOUS ERROR CONDITIONS RESET.
12.57.03. CPU ERROR EXIT AT 400121.
12.57.03. CM OUT OF RANGE.
T 12.57.03.ONEXIT.
12.57.04.IF,EF.NE.0.DISPLAY,EF.
12.57.04.DISPLAY,EF.
12.57.04. 3 3B
Example 2:
The following procedure file is an indirect access file called COLORPR. It uses the IF
command to determine if the color the BEGIN command substituted for COLOR is red or blue.
Different processing is done for the colors red and blue. Any other color is ignored. The
# character in the comment line inhibits substitution for the word (COLOR) it precedes
(refer to Parameters and the Procedure Body in section 4).
.PR0C,A*I,C0L0R.
IF,$C0L0R$.EQ.$RED$,L1.
COMMENT. PROCESSING DONE FOR #COLOR OF COLOR
REVERT.
ENDIF, LL
IF,$C0L0R$.EQ.$BLUE$,L2.
COMMENT. PROCESSING DONE FOR 0COLOR OF COLOR
REVERT.
ENDIF,L2.
COMMENT. NO PROCESSING FOR #C0L0R OF COLOR
z^PN
60459680 F 6-21
![](asset-ae.png)
/ * ^ v
The following commands call procedure A.
BEGIN,A,C OLORPR,BLUE.
BEGIN,A,COLORPR,RED.
BEGIN,A,COLORPR,PINK.
The following dayfile segment results when the preceding commands are processed. It shows
the effect of the # character.
08.34.30.BEGIN,A,C0L0RPR,BLUE.
08.34.32.IF,$BLUE$.EQ.$RED$,L1.
08.34.32.ENDIF,L1.
08.34.32.IF,$BLUE$.EQ.$BLUE$,L2.
08.34.32.COMMENT. PROCESSING DONE FOR COLOR OF BLUE
08.34.32. REVERT. /eS^
08.34.33.BEGIN,A,C0L0RPR,RED. ^)
08.34.34.IF,$RED$.EQ.$RED$,L1.
08.34.34.COMMENT. PROCESSING DONE FOR COLOR OF RED
08.34.34.REVERT.
08.34.34.BEGIN,A,C0L0RPR,PINK.
08.34.35.IF,$PINK$.EQ.$RED$,L1.
08.34.35.ENDIF,L1.
08.34.35.IF,$PINK$.EQ.$BLUE$,L2.
08.34.35.ENDIF,L2.
08.34.36.COMMENT. NO PROCESSING FOR COLOR OF PINK
08.34.36.SREVERT.CCL
MODE COMMAND
The MODE command defines the error conditions that cause the system to exit from normal
processing. When the error that you specified occurs, the system sets the appropriate error
flag and exits from normal processing to perform any error processing required. If an error
occurs for which you did not select the exit mode processing, the system ignores the error
and continues normal processing.
Format:
MODE,m,n.
Parameter Description
m CPU program error exit mode (0<m<17g). Modes lOg through 173 are
only valid for model 176. Selects the error conditiori(s) for which
normal error processing does and does not occur. If no mode is
selected, the default is 7.
n Included for compatibility with earlier versions of NOS. The system now
ignores the value specified on the command.
6-22 60459680 D
![](asset-af.png)
0S^\
The following values can be supplied for m.
m Normal Error Processing Occurs
0 None.t
1 Address out of range.
2 Operand overflow.t
Address out of range or
operand overflow.
Indefinite operand.t
Address out of range or
indefinite operand.
Indefinite operand or operand
o v e r fl o w.
Indefinite operand, address out
of range, or operand overflow
(default value).
10,11ttt Operand underflow or address out
of range.
12,13ttt Operand underflow, address out
of range, or operand overflow.
14,15 Operand underflow, address out
of range, or indefinite operand.
16,17 Operand underflow, address out of
range, operand overflow, or
indefinite operand.
Error Ignored and Job Continues
Address out of range, operand overflow,
indefinite operand, or operand
u n d e r fl o w. t t
Indefinite operand, operand overflow,
or underflow.
Address out of range, indefinite
operand, or operand underflow.
Indefinite operand or operand
under f low .tt
Address out of range oc operand
overflow or underflow.tt
Operand overflow or underflow.tt
Address out of range or operand
underflow.
Operand underflow.
Operand overflow or indefinite
operand.
Indefinite operand.
Operand overflow.
None.
tOn the model 176, address out of range (m=l) is always selected.
ttOperand underflow is applicable only to the model 176.
tttThese modes are valid only on the model 176. Since address out of range (m=l) is always
selected, the two modes are equivalent.
60459680 D 6- 23 •
![](asset-b0.png)
Descriptions of the error conditions are as follows:
Error Condition Description
Address out of range error. An error caused by an attempt to reference central memory or
extended memory outside of established limits.
Operand overflow error. An error resulting when a floating-point arithmetic unit
receives an operand with an exponent value of +1777g (3777 or
4000 in packed form). This is the largest exponent value that
can be represented in floating-point format.
Indefinite operand error. An error resulting when a floating-point arithmetic unit
encounters a calculation it cannot resolve. Examples of
indefinite operand errors are an attempt to divide 0 by 0 and
an attempt to multiply an overflow operand by an underflow
operand.
Operand underflow error. An error resulting when a floating-point arithmetic unit
receives an operand with an exponent of -1777g (0000 or 7777
in packed form). This is the smallest exponent value that can
be represented in floating-point format.
For further information about the processing of error mode errors, refer to Error Control in
section 3. For further information on the error conditions described above, refer to the
appropriate CYBER 180, CYBER 170, CYBER 70, or 6000 Computer System reference manual.
NOEXIT COMMAND
The NOEXIT command suppresses EXIT command processing. If an error occurs, control is not
transferred to the command following the next EXIT command. Instead, processing continues
with the next command (unless the error causes the job to unconditionally terminate). Refer
to the description of exit processing in section 5 for more information.
Format:
NOEXIT.
ONEXIT COMMAND
The ONEXIT command reverses the effect of a NOEXIT command. If an error occurs in
processing the commands following ONEXIT, control transfers to the command following the
next EXIT command. Refer to the description of exit processing in section 5 for further
information.
Format:
ONEXIT.
REVERT COMMAND
Refer to Ending a Procedure in section 4.
6-24 60459680 D
![](asset-b1.png)
/^P^N
SET COMMAND
The SET command assigns a value to a control register, an error flag, or the flag that
determines whether skipped commands are entered in the dayfile. Using the SS symbolic name,
it also can change the current interactive subsystem.
Format:
SET,symbolj=expressionj,symbol2=expression2,...,symboln=expressionn
symbol^ One of the following symbolic names. I
Name Description
Rl, R2, or R3 Local control registers. When a procedure is
called, the current values of Rl, R2, and R3 are
passed to the procedure. The values of these
registers may change within the procedure.
However, when processing reverts, these registers
are restored to the values they had when the
procedure was called. The initial value for each I
i s 0 . ■
R1G Global control register. When a procedure is
called or reverts, RIG keeps its current value.
The initial value for RIG is 0. |
EF Local error flag. When a procedure is called, the
current value of the error flag is passed to the
procedure. The value of the error flag may change
within the procedure. However, when the procedure |
reverts, the error flag is restored to the value it
had when the procedure was called. The initial
value for EF is 0.
EFG Global error flag. When a procedure is called or
reverts, EFG keeps i ts current value if it is not
zero. If EFG has a value of zero when the
procedure reverts, the system sets EFG equal to
EF. The initial value of EFG is 0.
DSC Dayfile-skipped-command flag. Initially, it is set
to 0, so that commands that are skipped (not
processed) are not entered in the dayfile. If DSC
is 1, the system enters skipped commands in the
dayfi le with t wo leadi ng peri od s.
PL or PS Page length (or page size). Default is 60 lines.
PW Page width. Default is 136 characters.
PD Page density. Default is six lines per inch.
SS Interactive subsystem indicator. The default of SS
is NULL.
expression Any valid expression. The value derived through evaluation of the
expression is assigned to the symbolic name. Acceptable values for
each symbolic name follow.
60459680 H 6-25
![](asset-b2.png)
,rf^V
symbol Suggested Value
Rl, R2, R3, or RIG Any integer between -131071 and 131071. If
the value is outside this range, it is
truncated. The values in these registers are
18-bit quantities, 17 digits and a sign. When
truncation occurs, the upper bits are truncated
but the sign bit is always retained. The
system does not issue a message as a result
of the truncation.
EF or EFG Any integer between 0 and 63. The values in
these registers are 6-bit unsigned quantities.
When truncation occurs, the upper bits are
discarded. If the value is greater than 63,
it is truncated. To assign the value defined
by the system for an error condition, set the
error flag to one of the error condition
symbolic names (refer to Symbolic Names at the
beginning of this section). The system sets
the EF flag to the appropriate error code when
an error occurs.
DSC 1 or 0. If the value of the expression is
nonzero, DSC is set to 1. While DSC is 1,
skipped commands are entered in the dayfile
preceded by two periods. Some error
processing routines set DSC to 1 so that
skipped commands are written in the dayfile.
PL or PS Any integer between 16 and 255.
PW Any integer between 40 and 255.
P D 6 o r 8 . Y o u c a n s e l e c t a p r i n t d e n s i t y o f
either six or eight lines per inch.
SS Any subsystem name (ACCESS, BASIC, BATCH,
EXECUTE, FORTRAN, FTNTS, or NULL).
6-26 60459680 D
![](asset-b3.png)
/SPN.
Examples:
The first three examples use procedures from the following procedure file. It is an
indirect access permanent file with the name SETFILE.
,PR0C,P1*I.
DIS PLAY, RL
DISPLAY,R1G.
SET,R1=9.
SET,R1G=888.
-EOR-
.PR0C,P2*I.
GET,ABC.
DISPLAY,EF.
DISPLAY,EFG.
-EOR-
-PR0C,P3*I.
GET,BASIC1.
BASIC.
DISPLAY,EF.
DISPLAY, EFG.
-EOR-
-EOF-
Example 1 - Control Register Use:
The following commands (below on the left side) set and display registers Rl and RIG. A
procedure, PI, is called which displays these registers, resets them, and then reverts to
the command record where they are again displayed.
On the right is the dayfile segment resulting from processing of the commands.
SET,R1=1.
SET,R1G=10.
DISPLAY, RL
DISPLAY,R1G.
BEGIN,P1,SETFILE.
DISPLAY,RL
DISPLAY,R1G.
16.34.42.SET,R1=1.
16.34.42.SET,R1G=10.
16.34.43.DISPLAY,R1.
16.34.43. 1 1B
16.34.43.DISPLAY,R1G.
16.34.43. 10 12B
16.34.43.BEGIN,P1,SETFILE.
16.34.44.DISPLAY,R1.
16.34.44. 1 1B
16.34.44.DISPLAY,R1G.
16.34.44. 10 12B
16.34.44.SET,R1=9.
16.34.44,R1G=888.
16.34.44.SREVERT.CCL
16.34.44. DISPLA Y,RL
16.34.44. 1 1B
16.34.45.DISPLAY,R1G.
16.34.45. 888 15708
The Rl and RIG registers retain their setting when the procedure is called. However, after
new values are set in the procedure and control reverts to the command record, Rl returns to
its previous value and RIG retains the value set in the procedure.
60459680 D 6-27
![](asset-b4.png)
0*m$$$\
Example 2 - Error Flag Use (EFG Nonzero):
The following commands (below on left side) set values in the error flags EF and EFG and
then call a procedure which attempts to access an indirect access permanent file. Control
reverts to the command record where EF and EFG are displayed to see if any error code
generated is returned via these flags. On the right side is the dayfile segment resulting
from the processing of the commands.
NOEXIT. 16.43.35.NOEXIT.
SET,EF=10. 16.43.35. SET,EF=10.
SET,EFG=20. 16.43.35. SET, EFG=20.
DISPLAY,EF. 16.43.35.DISPLAY,EF.
DISPLAY,EFG. 16.43.35. 10 12B
BEGIN,P2,SETFILE. 16.43.35. DISPLAY, EFG.
DISPLAY,EF. 16.43.35 20 24B
DISPLAY.EFG. 16.43.35.BEGIN,P2,SETFILE.
16.43.36.GET,ABC.
16.43.36. ABC NOT FOUND.
16.43.36.DISPLAY,EF.
16.43.36. 6 6B
16.43.36. DIS PLAY, EFG.
16.43.36. 20 24B
16.43.36.$REVERT.CCL
16.43.37.DISPLAY,EF.
16.43.37. 10 12B
16.43.37. DISPLAY, EFG.
16.43.37. 20 24B ^^\
The procedure attempts to get a permanent file which does not exist. This changes EF to
error code 6. It does not affect EFG. Control reverts to the command record and displays
EF and EFG. EF returns to its initial setting; EFG remains unchanged throughout.
/*^%».
6-28 60459680 D
![](asset-b5.png)
Example 3 - Error Flag Use (EFG Zero):
To return the error code generated in a procedure to the command record, EFG must be 0
before there is an exit from the procedure. This is demonstrated by the following commands
(below left side).
The dayfile segment (on the right) resulting from processing of the commands shows how the
error code is returned.
NOEXIT.
SET,EF=10.
SET,EFG=0.
BEGIN,P3,SETFILE.
DISPLAY,EF.
DISPLAY,EFG.
09.42.52.NOEXIT.
09.42.52.SET,EF=10.
09.42.52.SET,EFG=0.
09.42.52.BEGIN,P3,SETFILE.
09.42.53.GET,BASIC1.
09.42.55.BASIC.
09.42.56. INPUT FILE EMPTY OR MISP0SITI0NED
09.42.56.DISPLAY,EF.
09.42.56. 7 7B
09.42.57.DISPLAY,EFG.
09.42.57. 0 0B
09.42.57.SREVERT.CCL
09.42.58.DISPLAY,EF.
09.42.58. 10 12B
09.42.58.DISPLAY,EFG.
09.42.58. 7 7B
The procedure attempts to compile a BASIC program that is not an INPUT record. This
generates error code 7 in EF but does not affect EFG while control is still within the
procedure. When control reverts to the command record, EF returns to its original setting
and error code 7 is set in EFG.
60459680 H 6-29
![](asset-b6.png)
/^tSv
Example 4 - DSC Flag Use:
The following commands (below on left side) demonstrate the effect of DSC=0 and DSC=1. On
the right side is the dayfile segment resulting from processing of the preceding commands.
SET,DSC=0. 16.49.36
SKIP,LABL1. 16.49.36
COMMENT. SINCE THE DAYFILE SKIP 16.49.36
COMMENT. CONTROL IS SET TO ZERO. 16.49.37,
COMMENT. THESE STATEMENTS WILL NOT 16.49.37
CO MM EN T. AP PE AR IN T HE D AYFIL E. 16 .4 9. 37
ENDIF,LABLL 16.49.37
SET,DSC=1. 16.49.37
SKIP,LABL2. 16.49.37
CO MM ENT. SI NC E T HE DAYF IL E SK IP 16.4 9. 37
COMMENT. CONTROL IS NOW SET TO ONE, 16.49.37
COMMENT. THESE STATEMENTS WILL 16.49.37
COMMENT. APPEAR IN THE DAYFILE AND
COMMENT. EACH WILL BE FLAGGED
COMMENT. WITH TWO INITIAL PERIODS.
ENDIF,LABL2.
,SET,DSC=0.
,SKIP,LABLL
,ENDIF,LABL1.
,SET,DSC=1.
.SKIP,LABL2.
...COMMENT. SINCE THE DAYFILE SKIP
...COMMENT. CONTROL IS NOW SET TO ONE,
...COMMENT. THESE STATEMENTS WILL
...COMMENT. APPEAR IN THE DAYFILE
...COMMENT. AND EACH WILL BE FLAGGED
...COMMENT. WITH TWO INITIAL PERIODS.
,ENDIF,LABL2.
i^^\
SKIP COMMAND
The SKIP command initiates unconditional skipping of succeeding commands. Skipping is
terminated by an ENDIF command that has a label string matching the label string specified
on the SKIP command. Only an ENDIF command, and not an ELSE command, terminates skipping
initiated by a SKIP command.
Format:
SKIP,label.
Parameter
label
Description
Specifies a 1- to 10-character alphanumeric string. The string must
begin with an alphabetic character.
^"^K
An example of the use of the SKIP command is given after the description of the ENDIF
command.
6-30 60459680 D
<*^\
![](asset-b7.png)
WHILE COMMAND
The iterative commands WHILE and ENDW bracket a group of commands into a loop that can be
repeatedly processed. The beginning of the loop is identified by a WHILE command and the
end by an ENDW command. The ENDW command must have a label string that matches the label
string specified on the WHILE command. The loop is repeated as long as the expression in
the WHILE command is true. If the expression is initially false, control immediately skips
to the ENDW command.
Label strings of all WHILE commands within the command record of a job should be unique.
Duplication of a label string within a command record or within a procedure can produce
unpredictable results. The same label string can be used in a called procedure and in the
calling command record or procedure.
Format:
WHILE,expression,label•
Parameter Description
expression Specifies any valid symbolic name or expression described earlier in
this section. The separator following expression must be a comma.
l a b e l S p e c i fi e s a 1 - t o 1 0 - c h a r a c t e r a l p h a n u m e r i c s t r i n g . T h e s t r i n g m u s t
begin with an alphabetic character.
Example:
The following commands initiate a loop which is repeated five times.
SET,R1=0.
SET,R2=5.
WHILE,R1.LT.R2,FINISH.
SET,R1=R1+1.
DISPLAY,R1.
ENDW,FINISH.
You can vary the number of repetitions by setting different values in R2.
60459680 D b_3l
![](asset-b8.png)
0^%
![](asset-b9.png)
jS^\
JOB CONTROL COMMANDS
The job control commands alter information that controls jobs while in the system and
retrieves information concerning the status of jobs. The commands included in this category
are:
BLOCK
CFO
CHARGE
CHVAL
CLASS
COMMENT
CTIME
DAYFILE
DROP
ENQUIRE
ENTER
ERRMSG
GO
HTIME
Job
LDI
LENGTH
LIMITS
LISTLID
MACHINE
MFL
NORERUN
NOTE
OFFSW
ONSW
PASSWOR
PAUSE
PROTECT
QGET
QUEUE7
RERUN
RESOURC
RFL
ROLLOUT
RTIME
SETASL
SETCORE
SETJAL
SETJOB
SETJSL
SETPR
SETTL
SHELL
STIME
SUBMIT
SWITCH
UPROC
USECPU
USER
You must have specific authorization to use LDI, PASSWOR, PROTECT, or SUBMIT. You can use
the remaining commands regardless of your authorization. A listing of validation
information can be obtained using the LIMITS command. Although you are allowed to change
several control values for your job (with the Job, RFL, SETPR, and SETTL commands), you can
never specify more than that for which you are validated.
The system uses the USER command and CHARGE command for checking your authorization and
system accounting information. The RESOURC command is used by the system to prevent
deadlocks from occurring when several tapes or packs are used concurrently.
r60459680 H 7-1
![](asset-ba.png)
BLOCK COMMAND
The BLOCK command defines one or more lines of 10 by 10 (10 lines by 10 columns) block
letters to be added to a file. The large, 10-line characters provide easier identification
of output listings.
Format:
BLOCK,lfn,rewind,cc./line1/line2/.../linen
Parameter
lfn
rewind
Description
Specifies the name of the local file to receive the block character
lines. Default is OUTPUT.
Specifies whether or not lfn is rewound before the block character lines
are printed. Values that can be specified for rewind are R (rewind) and
NR (no rewind). The default is NR.
NOTE
If file lfn contains data and you specify that lfn
is to be rewound, the block characters written to
the file will overwrite data at the beginning of the
file.
line.
Specifies the carriage control character to be inserted before the first
line of block characters. The default value is 1 (top of form). The
carriage control characters are described in appendix H (a space, PM,
and special characters are not accepted).
Specifies the delimiting character that separates the block character
lines. The delimiter can be any character and must be the first
character following the command terminator. Consecutive delimiters
generate blank lines.
Specifies either a string of up to ten characters which constitute one
line of block characters, or one of the following special values:
Special Value
DATE
TIME
USER
UJN
JSN
Description
Current date.
Current time.
Current user name,
User job name.
Job sequence name,
7-2 60459680 H
![](asset-bb.png)
j0M&h\
Example:
Following is a BLOCK command and its resulting output:
/block
BLOCK,
/list,
1
,blockf,*myj ob*date
BLOCKF.*MYJOB*DATE
f=blockf
MM MM Y Y Y Y JJJJJJJJ OOOOOOOO BBBBBBBBB
MMMM MMMM Y Y Y Y JJJJJJJJ OOOOOOOOOO BBBBBBBBBB
MM MMMM MM YY YY JJ 00 000 B B B B
MM MM MM YYYY JJ 00 0 00 B B B B
MM MM MM YY JJ 00 0 00 BBBBBBBBB
MM MM YY JJ 00 0 0 0 BBBBBBBBB
MM MM YY J J J J 00 0 0 0 B B B B
MM MM YY J J J J 000 00 B B B B
MM MM YY JJJJJJJ oooooooooo BBBBBBBBBB
MM MM YY JJJJJ oooooooo BBBBBBBBB
88888888 5555555555 11 oooo 22222222 88888888
8888888888 5555555555 II 1111 oooooo II 2222222222 8888888888
8 8 8 8 55 II 11 11 00 00 II 2 2 2 8 8 8 8
8 8 8 8 55 II 11 00 00 II 22 8 8 8 8
88888888 555555555 II 11 00 00 II 222 88888888
88888888 5555555555 II 11 00 00 II 222 88888888
8 8 8 8 55 II 11 00 00 II 222 8 8 8 8
8 8 8 8 55 II 11 00 00 II 222 8 8 8 8
8888888888 555555555 II 1111111111 oooooo II 2222222222 8888888888
88888888 5555555 1111111111 oooo 2222222222 88888888
0
Column one of the listing contains printer carriage control characters 1 and 0.
character produces a form feed; the 0 characters produce double spacing.
The 1
CFO COMMAND
The CFO command sends data to one of your executing jobs. The command places data in
locations RA + 70B through RA + 74B of the program's field length. The CPU program
receiving the data must set the CFO flag (bit 14 of RA + 0) to indicate it will accept CFO
data. The CFO command clears the CFO and the PAUSE flags in RA after it places data in the
job's field length.
Format:
CFO,jsn.data
Parameter
jsn
data
Description
The job sequence name (JSN) of the job to receive the data.
The data for the job. The data must be 36 characters or less.
/0^S.
60459680 H 7-3
![](asset-bc.png)
CHARGE COMMAND
The CHARGE command causes the system to record on the account dayfile all information
regarding resources used in the previous account block, and designates a new charge and
pro ject n um ber fo r su bs eq uent a ct ivity. Its pu rpose is to co ntrol the ac counting activi ty
of the system for a customer or the installation. An account block is that portion of a job
from one CHARGE command to the end of the job or to another CHARGE command.
Format:
CHARGE,chargenumber,proj ectnumber.
CHARGE,*.
or
CHARGE.
Parameter Description
chargenumber Specifies the charge number assigned to you by your site.
projectnumber Specifies the project number assigned to you by your site.
If you use the third format of this command, the system reads the charge number and the
project number from a record of file INPUT. This record must be a single line with the
following format:
chargenumber,proj ectnumber
If your job is an interactive job, the system provides some security by overprinting an area
on your terminal and then prompting you to enter your charge and project numbers in this
area.
If you use the second format of this command, the system uses your default charge and
project numbers (refer to the LIMITS command in this section).
The CHARGE command is used in the control of user accounting. The project master user can
impose limits on the SRUs your jobs may accumulate under that project number; can restrict
your access to the system to a certain time of the day; and, in general, can monitor your
use of the system.
If a charge number has a project prologue associated with it, the project prologue is
executed each time the charge number is entered on a CHARGE command. A CHARGE command
entered as the first command in the job also causes the system and user prologues, if any,
to be executed. The system prologue is executed first, followed by the project and user
prologues. For a CHARGE command other than the first CHARGE command in the job, only the
project prologue is executed.
If your site requires that you use a CHARGE command, the system internally processes a
CHARGE,* command when necessary. For interactive jobs, the system executes the CHARGE,*
command each time you login. For batch jobs, the system internally executes a CHARGE,*
command if you do not include a CHARGE command immediately following the USER command. If
you do include a CHARGE command following the USER command, the system uses the charge
number you supply.
| 7-4 60459680 H
■**SS|\
![](asset-bd.png)
The CHARGE command sets the SRU limits for the account block and the job step to the user
name v alida ti on li mi ts or the accoun t val id ation l imits , whi ch ev er is sma ller. Re fe r to the
SETJSL and SETASL commands later in this section.
In addition to the site requirement for a charge number, you may also be required to enter a
charge number under certain conditions. Specifically, you may be required to enter an
additional number as a result of an SRU limits exceeded condition or as a result of a
project prologue.
If you are assigned more than one charge or project number, you can include additional
CHARGE commands in your job to record resources used under each charge number-project number
combination. Whenever a new CHARGE command is issued, the SRU information for the previous
charge number and project number is written to an account dayfile and then cleared.
However, the other accumulators (central processor time, mass storage activity, and so on)
are not cleared but continue to increment.
For a complete list of accounting messages issued to the job's dayfile, refer to Job
Completion in section 3.
CHVAL COMMAND
The CHVAL command redefines your validation limits or privileges. Currently, you are only
allowed to redefine your default service class assignments.
Format:
CHVAL,UC=otsc.
Parameter Description
UC=otsc Specifies the default service class assignment according to origin
type. The value otsc is the desired service class mnemonic appended to
the mnemonic for the origin type. Do not place a separator between the
mnemonics. The value ot must be one of the following:
ot Description
IA Interactive origin
BC Local batch
RB Remote batch
The value sc must be one of the following:
sc Description
SY System
BC Local batch
RB Remote batch
60459680 H 7-5
![](asset-be.png)
Parameter Description
sc Description
TS Interactive
DI Detached interactive
N S N e t w o r k s u p e r v i s o r
MA Maintenance
CT Communication task
In Installation class n (0 <_ n <^ 3)
You must be authorized to use the service class you select. The LIMITS
command shows the service classes you are allowed to use and your
default service class assignments.
Example:
In the following example, the default service class assignment for interactive jobs is
changed from interactive (TS) to detached interactive (DI).
/limits
THE FOLLOWING ARE ALLOWED SERVICE CLASSES -
BATCH (BC)
REMOTE BATCH (RB)
INTERACTIVE (TS)
DETACHED INTERACTIVE (DI)
THE USER DEFAULT SERVICE CLASS
FOR BATCH ORIGIN IS BC
FOR REMOTE BATCH ORIGIN IS RB
FOR INTERACTIVE ORIGIN IS TS
INQUIRY COMPLETE.
/chval,uc=iadi
UPDATE COMPLETE,
/limits
THE FOLLOWING ARE ALLOWED SERVICE CLASSES -
BATCH (BC)
REMOTE BATCH (RB)
INTERACTIVE (TS)
DETACHED INTERACTIVE (DI)
THE USER DEFAULT SERVICE CLASS
FOR BATCH ORIGIN IS BC
FOR REMOTE BATCH ORIGIN IS RB
FOR INTERACTIVE ORIGIN IS DI
INQUIRY COMPLETE.
7-6 60459680 D
![](asset-bf.png)
CLASS COMMAND
The CLASS command changes the service class of your current interactive job or of a batch
job you have submitted for execution. For interactive jobs, the CLASS command can only
change the service class of the interactive job from which it was entered; it cannot change
an interactive job connected to another terminal. For batch jobs, you can change the
service class of any executing job or any job in the input queue. This includes the job
from which the CLASS command was entered.
The CLASS command also shows the relative priority of the available service classes for a
specified origin type. Implicitly, the relative priority display also shows which service
classes are allowed within the chosen origin type.
Format:
CLASS,SC»sc,0P°A.
or
CLASS,sc,,,A.
or
CLASS, OT=»ot,L=lfn.
/iP^v
CLASS,,ot,lfn.
or
CLASS,SC=sc,JSN=jsn.
or
CLASS,sc,,,,jsn.
The parameters are order-independent if you specify them in the keyword=value form.
Otherwise, they are order-dependent.
Parameter
SC=sc
Description
Specifies the desired service class for the job. The value sc must be
one of the following:
sc Description
SY System
BC Local batch
RB Remote batch
TS Interactive
y ^ ^ V
60459680 D 7-7
![](asset-c0.png)
Parameter Description
sc Description
DI Detached interactive
NS Network supervisor
MA Maintenance
CT Communication task
In Installation class n (0 £ n j< 3)
There is no default for this parameter. The service class you specify
must be within your validation limits (refer to the LIMITS command).
0 P = A S e l e c t s t h e a b o r t o p t i o n . T h e c o m m a n d a b o r t s i f t o o m a n y j o b s i n t h e
system already have the service class you specified. Otherwise, if this
situation occurs, the system rolls out your job and waits until it can
make the desired assignment.
OT=ot Specifies the origin type for which the system shows the relative
priority of the available service classes. The value ot can be any of
the following:
ot Description
SY System origin
IA Interactive origin
B C L o c a l b a t c h o r i g i n
RB Remote batch origin
The default is the origin type of the current job. If you specify OT=ot
along with SC=sc, OT=ot is ignored.
L=lfn Specifies the file that receives the display generated by this command.
OUTPUT is the default. If you specify L=lfn along with SC=sc, L°lfn is
ignored.
JSN31 jsn Specifies the JSN of an executing job or a job in the input queue.
The first and second formats change the service class of your current job. If you use the
first or second format and do not specify a valid service class (for instance, you omit that
value), the system displays the relative priority of the service classes available for your
job. F urthe r, if you r job is i nt eractiv e, you receiv e a pro mpt f or a servi ce cla ss.
The third and fourth formats generate a display of the relative priority of the available
service classes for a designated origin type.
The fifth and sixth formats change the service class of an executing batch job or of a job
in the input queue. They cannot be used to change the service class of an interactive job.
z^^k
7-8 60459680 D .^
![](asset-c1.png)
Example:
r
/ip*\
The following terminal session shows how you can ascertain the relative priority of the
service classes for your current job.
/ c l a s s
AVAILABLE SERVICE CLASSES
RELATIVE PRIORITY
CLASS INPUT FILES EXECUTING JOBS OUTPUT FILES
DI * ****** ***********
10 * ******* ***********
TS *********** ************ *********** CURRENT
ENTER CLASS: di
CLASS COMPLETE.
/
COMMENT COMMAND
The COMMENT command allows you to place a comment in the system dayfile and the dayfile of
any of your jobs.
Format:
0^*\
V COMMENT,jsn.comment
or
COMMENT.comment
or
*comment
Parameter Description
jsn Specifies the job sequence name (JSN) of the job in whose dayfile you
want the comment written. The default is the current job.
comment Specifies the message you want written in the designated dayfiles.
If you use the third format of the command, the asterisk must be the first nonblank
character of the command.
60459680 H 7-9
![](asset-c2.png)
CTIME COMMAND
The CTIME command requests that the accumulated CPU time for the job be issued to the job's
dayfile (in seconds).
Format:
CTIME.
DAYFILE COMMAND
The DAYFILE command causes the system to write the job's dayfile to the file specified.
F o r p r i n t e d D AY F I L E o u t p u t , y o u c a n s p e c i f y o u t p u t p a g e s i z e a n d p r i n t d e n s i t y u s i n g t h e P L ^
and PD parameters. The DAYFILE command also honors the page length and print density set
for your job using the SET command and the PL and PD symbolic names.
Format:
DAYFILE,L=lfn,FR=string,OP=op,PD=pd,PL=pl,I=infile.
DAYFILE,lfn,string,op,pd,pi,infile.
Parameter Description
L=lfn Specifies the file on which the dayfile is to be written. If L=lfn is
omitted, OUTPUT is assumed. Pagination will occur if listing file name
is OUTPUT or if the PD or PL parameters are specified.
FR=string Specifies a character string for which a search is to be made in the
dayfile. The op parameter specifies the field to be searched.
The string specified must begin with the first character in the field to
be searched. The time field begins with a blank. -"^
If the string contains characters other than letters and numbers (such
as blanks), it must be enclosed by $ delimiters. A $ within the string
must be entered twice ($$) so it is not interpreted as a delimiter.
Interactive commands entered in the dayfile are preceded by a $ unless
you were under the batch subsystem when you issued the command. To
search for a interactive command, the $ preceding the command is
replaced with two $'s, and the command is enclosed by $ delimiters (for
example, $ $ $OLD $).
If the str ing is foun d, t he por tion of t he d ayfi le f oll owi ng t he las t
oc cu rr en ce o f the s pecifie d s tring is ou tp ut. If t he st ri ng is no t
found, an informative message and the entire dayfile is output for jobs
where the output file is connected to a terminal; where the output file
is not connected to the terminal, the job receives only the informative
message.
7"10 60459680 D
![](asset-c3.png)
,^*v
Parameter Description
OP=op Selects search option (single character):
PD=pd
PL=pl
op
T
M
I
Description
Search time field for string specified by FR=string.
Search message field for string specified by FR=string.
Inc re me nt al dump (d ay fil e printed f ro m poin t of la st day fil e
command).
Full dump.
If a literal string (string) is specified and op is omitted, OP=M is
assumed. If both string and op are omitted, OP=F is assumed unless the
output file is connected to a terminal. In this case, OP=I is assumed.
Specifies the print density; default is PD=6.
£d
3
4
6
8
Print Density
Double space; 6 lines per inch
Double space; 8 lines per inch
Single space; 6 lines per inch
Single space; 8 lines per inch
Specifies page size; if specified, the actual page size used is
determined by page density (pd) and the value specified for pi, as
follows:
pd
3
4
6
8
Page Size
pl / 2
pi / 2
Pl
Pl
If this parameter is omitted, page size is determined from system page
size and print density as follows:
pd
3
4
6
8
Default Page Size
30 lines
30 lines
60 lines
60 lines
I=infile Specifies a file which contains a dayfile to be used for input. If
I=infile is omitted, the DAYFILE command uses the active dayfile for
input.
NOTE
A paginated dayfile listing cannot be used
as the input file (I=infile). Refer to
L=lfn parameter.
jfSN
60459680 E 7 - 11 •
![](asset-c4.png)
Examples:
DAYFILE,,$ 11.21.$,T.
The dayfile is dumped to OUTPUT starting at the last occurrence of 11.21. in the
time field.
DAYFILE,I=DAY,FR=$$$GET,STATS.$
The dayfile is dumped to OUTPUT starting at the last occurrence of $GET,STATS, in
the message field of the previously written dayfile named DAY.
The system may place diagnostic messages in the output produced by DAYFILE. They are not
part of the job's dayfile from which the DAYFILE output is produced. These messages begin
with NOTICE*** and are described in appendix B.
7-12 60459680 E
![](asset-c5.png)
DROP COMMAND
/$P^N
The DROP command drops executing jobs or queued files. You can drop only jobs or queued
files belonging to you. You cannot drop the job from which you enter the DROP command.
A job or queued file belongs to you if it is your current job, was created by your current
job, or was created by another job belonging to you. Thus, any job you submit from your
current job belongs to you, even if the USER command in the submitted job has a user name
« * ! ! « » ! U S 6 r n a m e y ° U s P e c i f i e d w h e n Yo u l o g g e d i n ( o r d i f f e r e n t f r o m t h a t o f t h e
first USER command if the current job is a batch job).
Format:
DROP,JSN=j sn,DC=q,UJN=ujn,OP=R.
or
DROP,jsn,q,ujn,R.
The parameters are order-independent if you specify the parameters in the keyword=value
form. Otherwise, they are order-dependent.
Parameter
JSN=jsn
UJN=ujn
DC=q
Description
Specifies the job sequence name (JSN) of the job to be dropped.
Specifies the user job name (UJN) of the job to be dropped. You can
specify the JSN, the UJN, or both.
Specifies the disposition of the job to be dropped. You must specify q
if neither the JSN nor the UJN is specified. In this case, the system
drops all of your jobs with the specified disposition. If JSN or UJN is
specified, the default for q is ALL.
WT
PR
PU
PL
IN
EX
ALL
Description
Jobs queued with a wait disposition.
Jobs queued for printing.
Jobs queued for punching.
Jobs queued for plotting.
Jobs queued for input.
Executing jobs.
All jobs belonging to you.
OP=R
Examples:
DROP,ABDA.
DROP,, PR.
DROP.
Directs the system to drop the specified executing jobs without EXIT
processing but with single-reprieve processing for jobs containing such.
Drops executing job ABDA.
Drops all of your jobs queued for printing.
Incorrect. You must specify a JSN, UJN, or the DC=q parameter.
DROP,JSN=ABFF,OP=R. Drops executing job ABFF with a single reprieve and without EXIT
processing.
60459680 E 7-12.1/7-12.2
![](asset-c6.png)
![](asset-c7.png)
0^^y
r
ENQUIRE COMMAND
The ENQUIRE command gives you information about your jobs in the system. For output listing
files not connected to your terminal, the ENQUIRE command honors the page length and print
density set for your job using the SET command and the PL and PD symbolic names.
Format:
ENQUIRE,OP=p1p2...pn,FN=lfn1,0=lfn2.
or
ENQUIRE,p1p2...pn.
or
ENQUIRE,JSN=jsn,0=lfn2.
or
ENQUIRE,UJN=ujn,0=lfn2.
or
ENQUIRE.
Parameter Description
0P=pip2...p7 Any combination of the following options. You can request a maxi
mum of seven options on a command (for example, ENQUIRE,OP=BDFJLRS.).
Pi Description
A Gives listings of the B, D, R, U, J, L, and F options.
If you specify no parameters or only the 0=lfn2
parameter in a batch job, the OP=pjp2...pn
parameter defaults to OP=A.
B Returns identification and priority information. On a
secured system, the system also lists the current job
access level, the upper limit for the job access level,
the lower limit for the job access level, and the
security access categories you can assign to permanent
files.
60459680 D 7-13
![](asset-c8.png)
Parameter
Pi
Description
pie:
Description
/enquire,b
SYSTEM ACTIVITY.
USER NAME STARSKY
USER INDEX HASH AN2A
JOB SEQ. NAME ABLE
FAMILY NOSHOP
CHARGE NUMBER 2222
PROJECT NUMBER 666N666
PACK NAME •NONE*.
PACK TYPE DI1
PRIMARY FILE •NONE*.
SUBSYSTEM BATCH.
CPU PRIORITY 30
MAX FL (CM) 203700
MAX FL (EM)
LAST FL (CM)
LAST FL (EM)
Returns a listing of the resources you have demanded and
those which have been assigned (refer to RESOURC Command
in this section 6).
Example:
RESOURCE DEMAND INFORMATION.
RESOURCE DEMAND ASSIGNED
PE
HD
7-14 60459680 D
![](asset-c9.png)
Parameter
Pi
F
Description
Description
Gives the status of files assigned to your job.
Example:
/enquire,f
LOCAL FILE INFORMATION.
FILENAME LENGTH/PRUS TYPE STATUS FS
INPUT* IN.* EOR
PROLOG LO. EOR NAD
PROCFIL LO. EOI
INPUT TT.
OUTPUT TT.
PRCFILE LO. EOR NAD
ZZZZZLD LO. EOR NAD
PUBTOOL 835 PM.* EOR NAD
LIBRT 6429 PM.** INACCESS* NAD
TOTAL = 8
An asterisk (*) after the file type indicates that
the file is locked. (You cannot write on a locked
file .) R efe r to t he FI LE f un ct io n i n s ec ti on 6 f or
the meaning of the file type mnemonics. For
magnetic tape files (TYPE=TP), the current position
block number is displayed in the LENGTH/PRUS column
instead of the file length. The Status column
indicates the current position of the file (I/C
indicates mid- record) and whether the last
operation performed was a write. The entry
*INACCESS* indicates that the file is inaccessible;
it resides on a mass storage device that is
currently off or down. The FS column indicates
whether a file has the no-auto-drop status (refer to
the SETFS command). The LEVEL column gives the
se cu ri ty a cc es s le ve l of the fi le.
On an unsecured system, the security access level is |
listed only if it is not null.
c
0S&\
60459680 G 7-15
![](asset-ca.png)
y^Erc^v
Parameter Description
Pi Description
J Returns the contents of your control registers, error flag
field, and succeeding commands.
If the J option is used within a procedure, only the next
commands in the procedure are listed.
Example:
JOB CONTROL REGISTERS
R1 =
R2 =
R3 =
EF =
EFG =
R1G =
JOB PAGE PARAMETERS.
PW = 136
P L = 6 0
P D = 6
PENDING COMMANDS
WHILE,R1<20,C0PY.
COPYELAGENDA.
REWIND,AGENDA.
SET,R1=R1+1.
ENDW,C0PY.
REWIND,ENQWAJ.
COPYSBF,ENQWAJ.
REPLACE,ENQWAJ.
Returns your loader information including the status of
CYBER Interactive Debug utility (refer to the CYBER Loader
Reference Manual).
Example:
LOADER INFORMATION.
MAP OPTIONS = DEFAULT
DEBUG = OFF
GLOBAL LIBRARY SET IS -
LIB 3
7-16 60459680 D
![](asset-cb.png)
0^\
Parameter Description
Pi Description
Returns your amount of resources used. The resources
listed include CPU time, mass storage activity, magnetic
tape activity, permanent file activity, and adder
activity. These statistics are factors used in
calculating SRUs used.
Example:
RESOURCES USED.
C P U T I M E 0 . 1 0 7 S E C S .
MS ACTIVITY 0.914 KUNS.
MT A CT IVI TY 0 .0 00 KU N S.
PF ACTIVITY 0.034 KUNS.
ADDER 0.003 KUNS.
SRU 3.157 UNTS.
r
r
60459680 H 7-16.1/7-16.2 |
![](asset-cc.png)
![](asset-cd.png)
Parameter Description
Pi Description
S Re tur ns yo ur acc umu la ted SRUs . T he SRU repr es ent s your
total usage of the system. This unit is derived from
central processor time, I/O activity, adder activity,
and memory usage.
Example:
SRU ACCUMULATOR.
SRU 3.162 UNTS.
Returns accumulated CPU time.
Example:
CPU ACCUMULATOR.
C P U T I M E 0 . 1 1 1 S E C S .
Returns the initial amount of resources available to you
in seconds, job step SRU, account block SRU, and the
remaining resources available for dayfile messages, com
mands, and mass storage. These values apply to the
current job and were set at the beginning of the job by
default or by the SETJSL, SETASL, or SETTL commands. As
the job progresses, the system increments the
appropriate resource counters. Secondary USER commands
do not affect these values. Entering a different CHARGE
command affects your account block and job step SRU
limits (refer to the CHARGE command).
0fc>\
Example:
RESOURCE USAGE ALLOWED.
SECONDS 64
JOB STEP SRU 31808
ACCOUNT BLK SRU 31808
DAYFILE MESSAGES 993
COMMANDS NO LIMIT
MASS STORAGE 59008
n60459680 H 7-17
![](asset-ce.png)
Parameter Description
UJN=ujn Returns a one-line report of each of your jobs with the specified user
job name (UJN). The report for each job has the following fields:
jsn sc cs ds lid ujn status executing message
The fields have the following descriptions:
Field Description
jsn The job sequence name (JSN). It is a four-character,
system-defined name.
sc The service class of the job. One of the following
mnemonics appears in this field: /e^\
sc Service Class
SSystem
BBatch
RRemote batch
TInteractive
DDetached interactive
NNetwork supervisor
C Communication task
MMaintenance
0Installation class
1 Installation class
2Installation class
3 Installation class
The connection status (CS) of your job; that is, whether
your job is online and interactive, detached and
interactive, not interactive or queued. The following
values can appear:
cs Description
ON Online and interactive
DT Detached and interactive
N I N o t i n t e r a c t i v e
blank Queued
7-18 60459680 D
![](asset-cf.png)
Parameter Description
/fP*N
Field Description
ds The default destination of batch output. It indicates
whether batch output will be routed to the central site
(BC) or to a remote batch terminal (RB).
lid The logical identifier (LID) of the mainframe that is to
process the job. This is a three-character,
site-defined mnemonic.
u j n T h e u s e r j o b n a m e ( U J N ) o f t h e j o b . I t i s e i t h e r t h e
name you assigned the job or it is your user index hash
if you did not assign the job a name.
status The overall job status. It indicates whether the job is
executing, whether it has been rolled out, or the queue
in which it now resides.
executing The command that the system is now executing,
message
Example:
/enqui re,uj n= Idi j ob
JSN SC CS DS LID UJN
ABC F.B . . BC . . LD IJO B
STATUS
WAIT QUEUE
EXECUTING MESSAGE
If you specify only the keyword UJN, the system returns a one-line
report for each job associated with your user name.
/sP^S
Example:
/enqui re,ujn
JSN SC CS DS LID UJN
ABCH.B. .BC.M42.LEVEL
ABCB.T.ON.BC. .AJLA
ABCI.B. .BC.M42.LDIJ0B
ABCF.B. .BC. .LDIJOB
STATUS
INPUT QUEUE
EXECUTING
PRINT QUEUE
WAIT QUEUE
EXECUTING MESSAGE
r
Do not specify the UJN=ujn parameter with any parameter other than
0=lfn2.
JSN=jsn Returns a detailed report of the job with the specified job sequence
name (JSN). The format of the report varies with the status of the
job. If the job is executing, the report includes the JSN, the job's
service class, its connection status, the default destination of its
batch output, the current status of the job, the user job name (UJN),
the job access level (on a secured system only), job resource
information, the executing command, a dayfile extract (maximum of 10
messages), and a list of the next commands to be executed (maximum of
10 commands).
60459680 D 7-19
![](asset-d0.png)
Parameter Description
Example:
/en quire,j sn=abcb
ABCB.T.ON.BC. .EXECUTING UJN=AJLA LEVEL=LVLO
S RUS = 2 .57 3 . S R U L IM I T = N0 L I M IT. C M F L = 5 0 0 0 . E C S F L = 0 .
DAYFILE=
17.26.55. SUBMIT COMPLETE. JSN IS ABCE.
17.27.07. GET,0PLJ0B.
17.27.21. RE PLACE, CATEGOR.
17.27.32.SUBMIT,OPLJOB,TO.
17.27.32. SUBMIT COMPLETE. JSN IS ABCF.
17.28.04.ROUTE,CATEGOR,DC=IN.
17.28.04. ROUTE COMPLETE. JSN IS ABCH.
17.28.13.ENQUIRE,UJN.
17.28.26. ENQUIRE, JSN.
17.29.04. ENQUIRE, JSN=ABCB.
If the job is a queued file, the report includes the job's JSN, its
service class, the default destination of its batch output, the
logical identifier (LID) of the mainframe that is to process the job,
its queue residence, its UJN, length in PRUs, and output
specifications.
Example:
/enqui re,j sn=abcf
ABCF.B. .BC. .WAIT QUEUE UJN=LDIJOB LEVEL=LVL0
PRU LENGTH* 32. DC=TT. FC= . ID= 0. EC=
If you specify the keyword JSN, the system returns a one-line report
on each job associated with your user name. The fields in the display
are identical to those you get when you specify only the keyword UJN,
except that the UJN field and the EXECUTING MESSAGE fields are omitted.
Example:
/enquire,jsn
JSN S C C S D S L ID STAT US J SN SC C S D S LID S TAT US
ABCH.B. .BC.M42.INPUT QUEUE ABCB.T.ON.BC. .EXECUTING
ABCI.B. .BC.M42.PRINT QUEUE ABCF.B. .BC. .WAIT QUEUE
Do not specify the JSN=jsn parameter with any parameter other than
0=1fn2.
FN=lfnj Returns the status of local file lfnl (refer to the OP=F parameter).
0=lfn2 Writes the output on file lfn2» The default is OUTPUT. If you
specify only the 0=lfn2 parameter in a batch job, the
0P=pjp2...pn parameter defaults to 0P=A.
7-20 60459680 D '
![](asset-d1.png)
/**^\
If you enter the ENQUIRE command with no parameters from an interactive job, the system
gives a two-line report of the current job.
Example:
/enqui re
JSN: AAFA SYSTEM: BATCH SRU: 2.055 FILE NAME: SAMPOUT
STATUS: IDLE
It always returns the status IDLE. To get a report on the current job while the system is
executing another command, enter the ctE or ctS command (refer to Interactive Status
Commands in section 8).
If you enter the ENQUIRE command with no parameters in a batch job, the command defaults to
ENQUIRE,0P=A.
ENTER COMMAND
The ENTER command enters a series of commands on one line. This is especially useful for
interactive users operating in the batch subsystem.
Format:
ENTER./commandj/command2/.../commandn
/ Delimiting character used to separate the individual commands on one
line. It can be any character not used within the commands and must
immediately follow a period or right parenthesis.
commandi Any NOS command you are authorized to use. Interactive commands for
which there are no batch counterparts are not acceptable.
The system supplies a terminator (period or right parenthesis) if it is missing from any
command•
Example:
From a terminal, you enter the batch subsystem and type in an ENTER command on one line as
follows:
batch
RFL,0.
/enter.#get,fprog#ftn5,i=fprog#map,part#1go#exit#dtnp#rewind,zzzdump#copy,zzzdump
This is the sequence of commands used in section 14 to illustrate the reading of CM dumps.
Assuming that a FORTRAN 5 program is on the indirect access file FPROG, output like that
shown in the figures in section 14 is produced when this command is processed.
0BS\
60459680 D 7_21
![](asset-d2.png)
ERRMSG COMMAND
The ERRMSG command controls the display of error messages generated by commands executed
within a NOS procedure. An ERRMSG,OFF command inhibits the display of error messages at the
terminal, although all messages are still listed in the dayfile. This command has no effect
when issued from a batch job.
The ERRMSG command must be executed from within a procedure. The error message off status
remains in effect until an ERRMSG,ON command is issued, or until your job returns to
interactive command status. The error message off status is not affected by the entry of
subsequent BEGIN or REVERT commands (that is, nested procedures).
Format:
ERRMSG,status
Parameter Description
status Specifies whether error messages generated by commands within a
procedure are displayed at the terminal. Values that can be specified
for status are OFF (messages are not displayed) and ON (messages are
displayed). The default value is ON.
GO COMMAND
The GO command clears the pause bit of one of your executing jobs. The system may have set
the pause bit because of an error or a request for user input. You can set the pause bit
with one of your programs or with the PAUSE command.
Format:
GO,jsn.
Jsn Specifies the job sequence name (JSN) of the job whose pause bit you
want to clear.
You must check the status of the pause bit to effectively use this command. The program does
not pause just because the pause bit is set. Similarly, the program does not proceed just
because the pause bit has been cleared. You can write a program that checks the status of
the pause bit and waits for that bit to be cleared (refer to the RECALL macro in Volume 4,
Program Interface).
If you want to determine whether a PAUSE or GO command has been entered, write a program to
set bit 13 of word RA and then status it. The system unconditionally clears bit 13 of word
RA whenever the PAUSE/GO command sets/clears the pause flag (bit 12 of word RA). Hence,
when the system clears it, you can check the pause flag. CPU programs that check the pause
flag on NOS 1 continue to work properly on NOS 2, but these programs cannot determine when a
PAUSE or GO command has been entered.
7-22 60459680 E
![](asset-d3.png)
HTIME COMMAND
The HTIME command issues a dayfile message giving the model 176 accumulated clock cycle
count for the job. A clock cycle on the model 176 is 27.5 nanoseconds. COMPASS
instructions require a certain number of clock cycles to execute as described in the COMPASS
Reference Manual. This command can be used for performance comparisons.
Format:
HTIME.
The resulting dayfile message has the following format. The cycle count is in kilocycle
u n i t s .
HTIME nnnnnnnnnnnn.nnn KCYCLES.
An HTIME command processed on a machine other than the model 176 produces the following
dayfile message.
HTIME NOT AVAILABLE.
r
y$^N
60459680 E 7-22.1/7-22.2 |
![](asset-d4.png)
![](asset-d5.png)
JOB COMMAND
The Job command, also known as the job card, specifies the user job name (UJN) and may
specify job processing parameters. Refer to Job Names in section 3 for the significance of
the user job name. The first command of a batch job must be a Job command.
Format:
ujn,P=priority,T=timelimit,CM=memory,EC=xmemory,ST=lid,AL=level.punchmode
or
uj n,Ppriori ty,Ttimelimi t,CMmemory,ECxmemory,STlid,ALlevel.punchmode
or
ujn,SC=class,T=timelimit,CM=memory,EC=xmemory,ST=lid,AL=level.punchmode
or
ujn,SCclas s,Ttimelimi t,CMmemory,ECxmemory,STlid,ALlevel.punchmode
or
uj n,priority,timelimit,memory,xmemory,lid,level.punchmode
or
uj n,class,t imelimit,memory,xmemory,lid,level.punchmode
All parameters except the parameter ujn are optional. If you include keywords when you
specify optional parameters, they are order-independent. Otherwise, they are
order-dependent.
Parameter
ujn
P=priority
SC=class
Description
Alphanumeric user job name (UJN) of one to seven characters. This
name identifies the individual jobs being run under the same user
name.
Specifies the priority level at which the job enters the system.
Using this priority level, the system assigns the job a service
class according to a site-defined algorithm. The value you specify
must be an integer in the range of 0 through 7. The default for
P=priority depends on your default service class assignments and
your site-defined algorithm for mapping priority levels and service
classes (refer to Job Service Classes in section 3).
To assign a service class to your job directly, use the SC=class
parameter.
Specifies the service class to be assigned to the job. The value
class must be one of the following values:
class Description
SY System
60459680 F 7-23
![](asset-d6.png)
Parameter Description
class Description
BC Local batch
RB Remote batch
TS Interactive
DI Detached interactive
NS Network supervisor
SS Subsystem
MA Maintenance
CT Communication task
In Installation-defined class n (0 < n < 3)
The default for SC=class depends on your default service class
assignments (refer to Job Service Classes in section 3).
AL=level Specifies the maximum security access level your job can attain.
Unless changed by your site, the value level can be any one of the
following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
You may not be authorized to use all of these access levels (refer
to the LIMITS command). The default is the lowest access level you
are authorized to use. On an unsecured system, this parameter has
no effect, but the system does ensure that you specify a valid level
name.
T=timelimit Specifies the central processor job step time limit in seconds.
Values can range from 1 to 77777. Decimal is the default base.
Octal values from 1 to 77777s (* t0 32767) can be entered if
followed by a B suffix. The default limit is 64 (100g).f Decimal
values from 32767 to 77777 set the time limit at its maximum. The
time limit set by this parameter must be sufficient for completion
of each of the steps in the job (refer to Time Limit Control in
se ct io n 3 ).
CM=memory Specifies the maximum octal field length for the job (refer to Field
Length Control in section 3). The system rounds the value to the
next highest multiple of 100g. The default value is the maximum
field length for which you are authorized (refer to the LIMITS
command) or the maximum field length available for user jobs
(dependent on machine size), whichever is smaller. The field length
cannot exceed 3765008- This is the absolute upper limit; however,
your site may choose a lower limit.
TYour site can change this default.
7-24 60459680 E
![](asset-d7.png)
Parameter
EC=xmemory
> f f \ ST=lid
Description
A value containing an 8 or 9 or the suffix D is interpreted as
decimal.
Specifies the maximum octal number of 1000Q, 2000g, or 40008
word extended memory blocks required by the job. The extended
memory block size is site dependent; the default block size is
lOOOg words.t This extended memory field length cannot exceed the
amount of user extended memory allowed by the installation (refer to
the LIMITS command). Your job must request the extended memory
(refer to the RFL command in section 7) before it can be used. A
value containing an 8 or 9 or the suffix D is interpreted as decimal,
Specifi es the logica l id entifier (LID ) of the host to w hi ch y ou a re
routing the specified job. The LID must be a three-character
alphanumeric s trin g defined by site personnel. The lo cal host is
the default.
You must have special authorization to use this parameter (refer to
the LIMITS command).
punchmode Specifies the conversion mode for card decks. This parameter must
be entered in columns 79 and 80. A 26 indicates that coded cards
are to be converted in 026 mode; 29 indicates cards are converted in
029 mode. This initial keypunch mode can be changed within the job
by a conversion change card (refer to Coded Cards in appendix F)
when reading cards or a ROUTE command when punching cards. If this
parameter is omitted, the installation default keypunch mode is
used. This conversion mode indicator is ineffective for remote
batch jobs entered with mode 4 card readers; it is effective for
remote batch jobs entered with HASP, 2780, and 3780 card readers.
The system issues error messages when parameter specifications exceed validation limits. It
also issues an error message if an extended memory field length is specified when your
central memory validation limit is less than lOOOOg words. Consult installation personnel
for further installation restrictions based on the machine configuration and subsystems used.
Example:
J0BAAA,,1,50000,20.
has the same effect as;
JOBAAA,CM=50000,EC=20,T=1.
tRefer to the UEBS parameter in common deck PPCOM under Installation Parameters in the
NOS 2 Installation Handbook.
60459680 H 7-25
![](asset-d8.png)
LDI COMMAND
The LDI routine queues one or more jobs for input and optionally enters the job sequence
name (JSN) of each job in the dayfile of the job that entered the LDI command. LDI
initiates a new job each time it encounters an EOF. LDI starts processing at the current
position of the file and continues until an EOI, double EOF, or EOF followed by an empty
record is encountered. The jobs submitted are batch origin type jobs. LDI does no
reformatting of the job file. Therefore, SUBMIT directives (/JOB,/USER,/NOSEQ, and so
forth) are not allowed.
Format:
LDI,FN=lfn,ID=id,OP=OP,DC=dc,UN=un,FM=fm.
or
LDI,lfn,id,OP,dc,un,fm.
The parameters in the first format are order-independent. Those in the second format are
order-dependent.
Parameter
FN=lfn
ID=id
OP=OP
DOdc
Description
Specifies the name of the file containing the job(s) to be submitted.
LOAD is the default.
Specifies the identifier of the local device which will receive job
output. The identifier id must be octal and in the range 0 through
67B. If you omit this parameter or specify only the keyword ID,
implicit central site routing occurs (refer to Implicit Routing under
the description of the ROUTE command, section 9).
You may not specify ID=id parameter if you specify the UN=un or FM=fm
parameter.
Directs the system to enter the job sequence name (JSN) of each job in
the dayfile of the job that issued the LDI command.
Specifies the disposition of output for each job that is queued for
input•
.^^S\
dc Description
IN Disposes of job output according to the default option for
the job's origin type (refer to Job Origin Types and Service
Classes in section 3).
UN=un
NO Discards all output.
TO Queues the output with a wait disposition.
Specifies the user name of the remote batch user to whom the system
routes each job's output. If you omit this parameter or specify only
the keyword UN, implicit remote routing occurs (refer to Implicit
Routing under the description of the ROUTE command, section 9).
You may not specify this parameter if you specify the ID=id parameter.
7-26 60459680 D
![](asset-d9.png)
Parameter Description
FM-fm Specifies the family name of the remote batch user to whom the system
routes each job's output. You must have special authorization to
specify an alternate family name (refer to the LIMITS command). If
you omit this parameter or specify only the keyword FM, implicit
remote routing occurs (refer to Implicit Routing under the description
of the ROUTE command, section 9).
You may not specify this parameter if you specify the ID=id parameter.
The number of executing jobs and output files you have within the system cannot exceed your
deferred batch job validation limit (refer to the LIMITS command in this section). If this
limit is reached, no further jobs can be loaded until an existing job completes.
If any of the submitted jobs contain an invalid USER command, the job entering the LDI
command is aborted with no exit processing. If you entered the command interactively, you
are immediately logged off with no dayfile message. The security count for the user name
that entered the LDI command is decremented accordingly.
LENGTH COMMAND
The LENGTH command gives you the current status of one of your local files.
Format:
LENGTH,lfn.
Parameter Description
lfn Name of a file assigned to the job.
The information given for the local file includes its length in PRUs, type, and current
status. The same information can be obtained with the ENQUIRE command.
60459680 D 7-27
![](asset-da.png)
LIMITS COMMAND
The LIMITS command directs the system to list your validation limits. The LIMITS command
always lists the validation limits associated with the job's current user name. However, if
a job contains more than one USER command, the actual limits associated with the job are a
combination of the limits of the first user name and those of the current user name. You
can use the ENQUIRE(OP=U) command to determine what your actual limits would be in such a
case.
Format:
LIMITS,L=lfn.
Parameter
L = l f n
Description
Specifies the file which receives the validation information. The
default is OUTPUT.
The validation limits show the extent to which you can use various system resources. The
LIMITS output falls into the following categories:
Resource Limits.
Other Characteristics.
User Permissions.
Network Applications.
Privileged Network Applications.
Local Applications.
Shell Permissions.
Security Permissions.
Security Access Categories.
Security Access Levels.
Service Classes.
Default Service Classes.
If there are no entries for a category, the system suppresses the header for that category.
7-28 60459680 D
![](asset-db.png)
/P^N
RESOURCE LIMITS
The system indicates the maximum number of specific system resources you can use. The
following list shows the resources that appear in this category:
Magnetic tape units that may be assigned.
Removable auxiliary devices that may be assigned.
CPU seconds allowed for each job step.
Central memory words allowed.
Extended memory words allowed.
Jobs that can be detached.
Deferred batch files allowed.
Permanent files allowed in your catalog.T
PRUs available for any one indirect file.
PRUs available for any one direct file.
PRUs available for all indirect files.
PRUs available per job.
Messages that may be issued to the dayfiles.
Batch commands that may be processed.
Cards that may be punched per file.
Lines that may be plotted per file.
Lines that may be printed per file.
SRUs allowed per job.
The maximum number of deferred batch jobs does not apply to you if you have system
privileges and debug mode is set on the system display console or if your jobs are of the
system origin type.
tThe value SYSTEM denotes that you do not have a static limit for the number of permanent
files allowed in your catalog. Whenever you initiate a permanent file operation, the
system assigns a limit, which can vary with the service class of your job.
r60459680 D 7-29
![](asset-dc.png)
OTHER CHARACTERISTICS
This category lists some general characteristics associated with your user name and your
jobs. The list may include any of the following:
User index.
Default charge number.
Default project number.
User prologue.
System prologue.
Default subsystem for interactive jobs.
Default character set mode for interactive jobs.
Expiration dates for your user passwords.
/<s*\
yflaSv
7-30 60459680 D
![](asset-dd.png)
USER PERMISSIONS
In addition to specifying resource limits for certain resources, the system lists special
privileges that you possess. The following list contains special privileges you might
possess, including the privilege to: |
Change your passwords.
Use privileged interactive commands.
Create dir ect a cc ess fi le s.
Create indirect access files.
Have system origin privileges.
Access/create library files.
Assign magnetic tapes.
Access system without supplying charge/project number.
Access or create files on auxiliary devices.
Access transaction functions for library updates.
Have unlimited terminal connect time without timeout.
Use sys te m cont rol p oin t faci lit y.
Have special accounting privileges.
Have the BIO subsystem privilege to use the V carriage control character in a I
user-specified PFC array in a file. |
Use the PROTECT command.
Transfer permanent files between hosts.
Transfer queued files between hosts.
Specify mainframe logical identifiers (LIDs) on the Job and ROUTE commands.
Specify charge numbers other than the default charge number.
Define a password without random characters.
Have remote maintenance privileges.
Specify an alternate family during a job.
Control network processing units (NPUs).
60459680 G 7-31
![](asset-de.png)
NETWORK APPLICATIONS
The following are network applications you may be authorized to use:
• Interactive Facility (IAF).
• Remote Batch Facility (RBF).
• Transaction Facility (TAF).
• Message Control System (MCS).
• Terminal Verification Facility (TVF).
• Interactive Transfer Facility (ITF).
LOCAL APPLICATIONS
The system lists local applications you are authorized to use. If there are no such
applications, this category does not appear in the output.
PRIVILEGED NETWORK APPLICATIONS
.<^*^^s
The system lists the privileged network applications you are authorized to use. The /
Communications Supervisor (CS) is one such application.
SHELL PERMISSIONS
The system lists controls applicable to a shell program you write to monitor commands
entered under your user name. The list includes the following:
Clear controls upon loading errors with shell program.
Clear shell processing if screening program aborts.
Local file load of shell program.
Global file load of shell program.
System library load of shell program.
Monitor commands from terminal.
Monitor commands outside of procedures.
Monitor commands inside of procedures.
7-32 60459680 D
![](asset-df.png)
x^*S
SECURITY PERMISSIONS
There are special security-related permissions you may possess. The list may include any of
the following permissions:
Write unlabeled magnetic tapes.
Write to or extend a file with an access level lower than your job access level.
Lower file access levels.
Lower your job access level.
Assign an expiration date for a file password or file permission.
Assign an expiration date for your user password.
Execute on-line diagnostics.
Perform security administrator duties.
SECURITY ACCESS CATEGORIES
The system lists the access categories you can associate with your permanent files. When
you create a permanent file, the system associates all categories for which you are
authorized with this file. You can change this association with the SETPFAC command.
SECURITY ACCESS LEVELS
The system lists a set of access levels that determine the access levels at which your jobs
may run and the access levels at which you may create or access files.
SERVICE CLASSES
The system lists all of the service classes you can assign to a job.
restrict the use of a service class to jobs of certain origin types,
these restrictions with the CLASS command.
You r si te can f urther
You can determine
DEFAULT SERVICE CLASSES
The system lists the service class it initially assigns to your job if you do not specify a
service class on the Job command or ROUTE command. This default assignment can vary with
the origin type of your job. Unlike most other validation limits and privileges, you can
change this default assignment with the CHVAL command.
60459680 D 7-33
![](asset-e0.png)
The following is an example of a user's validation limits:
r'^N.
/ l i m i t s
LIMITS FOR STARSKY FM/NOSCLSH 83/08/09. 17/11/13/
MAXIMUM NUMBER OF -
MAGNETIC TAPE UNITS THAT MAY BE ASSIGNED 3
REMOVABLE AUXILIARY DEVICES THAT MAY BE ASSIGNED 2
CPU SECONDS ALLOWED FOR EACH JOB STEP UNLIMITED
CENTRAL MEMORY WORDS ALLOWED/100B 2037B
EXTENDED MEMORY WORDS ALLOWED/1000B OB
JOBS THAT CAN BE DETACHED 3
DEFERRED BATCH FILES 8
PERMANENT FILES ALLOWED IN YOUR CATALOG UNLIMITED
PRUS AVAILABLE FOR ANY ONE INDIRECT FILE 192
PRUS AVAILABLE FOR ANY ONE DIRECT FILE 1024
PRUS AVAILABLE FOR ALL INDIRECT FILES 4096
PRUS AVAILABLE FOR JOB 66048
MESSAGES THAT MAY BE ISSUED TO THE DAYFILES 1008
BATCH COMMANDS THAT MAY BE PROCESSED UNLIMITED
CARDS THAT MAY BE PUNCHED PER FILE UNLIMITED
L I N E S T H AT M AY B E P L O T T E D P E R F I L E 5 1 2
LINES THAT MAY BE PRINTED PER FILE UNLIMITED
SRUS ALLOWED PER JOB UNLIMITED
OTHER CHARACTERISTICS -
USER INDEX 5410B
DEFAULT CHARGE NUMBER ASSIGNED 1234
DEFAULT PROJECT NUMBER ASSIGNED 123A456
SYSTEM PROLOGUE 2B
USER PROLOGUE PROLOG
INTERACTIVE SUBSYSTEM BATCH
INTERACTIVE CHARACTER SET MODE NORMAL
7-34 60459680 D
,4*gi^v
![](asset-e1.png)
/ $ ^ \
THE FOLLOWING ARE VALID USER PERMISSIONS -
CHANGE YOUR PASSWORD
CREATE DIRECT ACCESS FILES
CREATE INDIRECT ACCESS FILES
ACCESS/CREATE LIBRARY FILES
ASSIGN MAGNETIC TAPES
ACCESS OR CREATE FILES ON AUXILIARY DEVICES
TRANSFER PERMANENT FILES BETWEEN HOSTS
TRANSFER QUEUED FILES BETWEEN HOSTS
SPECIFY LID-S ON JOB AND *ROUTE* COMMANDS
CHARGE NOT RESTRICTED TO DEFAULT
DEFINE NON-RANDOMIZED LOGIN PASSWORD
THE FOLLOWING ARE VALID NETWORK APPLICATONS -
INTERACTIVE FACILITY (IAF)
REMOTE BATCH FACILITY (RBF)
TRANSACTION FACILITY (TAF)
TERMINAL VERIFICATION FACILITY (TVF)
THE FOLLOWING ARE VALID SHELL PERMISSIONS -
PROCESS COMMANDS OUTSIDE CCL PROCEDURE
SYSTEM LIBRARY LOAD OF SHELL PROGRAM
THE FOLLOWING ARE VALID SECURITY PERMISSIONS -
WRITE UNLABELED MAGNETIC TAPES
THE FOLLOWING ARE VALID SECURITY ACCESS LEVELS -
ACCESS LEVEL LVLO
THE FOLLOWING ARE ALLOWED SERVICE CLASSES -
BATCH (BC)
REMOTE BATCH (RB)
INTERACTIVE (TS)
DETACHED INTERACTIVE (DI)
THE USER DEFAULT SERVICE CLASS
FOR BATCH ORIGIN IS BC
F O R R E M O T E B A T C H O R I G I N I S R B
FOR INTERACTIVE ORIGIN IS TS
INQUIRY COMPLETE.
/
60459680 F 7-35
![](asset-e2.png)
LISTLID COMMAND
The LISTLID command lists information on the configuration of your network and on the
availability of hosts in the network. Information available through LISTLID includes:
• Logical identifiers (LIDs) and physical identifiers (PIDs) for hosts in the
network. LIDs are used in certain NOS commands (for example, Job, ROUTE, MFLINK,
and MFQUEUE) to specify the destination host for a job or file routing operation.
• The subsystem(s) available to provide network communications. This could be any or
all of the following: Remote Host Facility (RHF), Network Access Method (NAM), and
SCOPE 2 Station Facility (SSF).
• Host characteristics such as local host or linked status, store and forward
capabilities, and host availability.t
Note that the site administration has the option of choosing whether information for any
given LID or PID can be listed using the LISTLID command.
Format:
LISTLID,LID=lid,PID=pid,l=lfn
or
LISTLID,ST=lid,PID=pid,1=lfn
Parameter Description
LID=lid Specifies the LID for which information is to be displayed. If LID=lid
or or ST=lid is specified, information is listed for the specified LID.
ST=lid (The LID and ST keywords are interchangeable; either may be used, but
not both.) If this parameter is omitted and the PID parameter is also
omitted, information is listed for all LIDs in the network.
PID=pid Specifies that output is to be listed only for LIDs associated with this
PID. If the LID=lid parameter is also specified, information is listed
only for that LID. ••» If no LID=lid parameter is specified, information is
listed for all LIDs associated with this PID. If only the keyword PID
is specified, information is listed on all LIDs, grouped according to
their associated PIDs.
L=lfn Specifies that LISTLID output is to be written to file lfn. If this
parameter is omitted, output is written to file OUTPUT.
Examples:
LISTLID.
This command lists information on all LIDs in the network for which the site allows
information to be listed. The information is listed in output format 1.
LISTLID,LID=lid,L=lfn.
This command lists information on all LIDs in the network with the name lid except those
that the site does not allow to be listed. The information is listed in output format 1 on
fi l e l f n .
rHosts connected through an X.25 network are always considered available as long as the /**s\
network processing unit (NPU) connecting your host to the X.25 network is available. *
7-36 60459680 E
![](asset-e3.png)
LISTLID,LID=lid,PID=pid.
This command provides information on the named LID associated with the specified PID. If
the site does not allow listing of the named LID, or of both the named LID and PID, the
system returns a dayfile message indicating that the specified LID was not found. If the
site allows the LID to be listed but not the PID, LISTLID outputs information using format
2; however, the system will not display the PID name or the names of available subsystems.
Instead, the system replaces those names with the characters .
LISTLID,LID=lid,PID.
This command lists all LIDs with the name lid except those that the site does not allow to
be listed. The specified LIDs are listed under their associated PIDs using output format 2,
LISTLID,PID.
This command uses output format 2 to list all LIDs, grouped according to their associated
PIDs. Any LIDs that the site does not allow to be listed are omitted from the output. Any
PIDs that cannot be listed are replaced by the characters .
LISTLID,PID=pid.
This command uses output format 2 to list all LIDs associted with the specified PID. Any
LIDs that the site does not allow to be listed are omitted from the output. If the PID
cannot be listed, pid is replaced with the characters .
LISTLID uses two output formats. Output format 1 is used when the LISTLID command does not
contain a PID parameter.
LID MAINFRAME ATTRIBUTE
LOOPBACK
NETWORK
M64 NOS 964 RHF,SSF
M42 NOS 420 LINKED NONE AVAILABLE
B2C VSOS LINKED RHF
MFZ SC0PE2 LINKED SSF
MSI NOS MSI LINKED NAM
Output format 2 is used when a PID parameter is specified on the LISTLID command.
• Example of output format 2:
PID LID MAINFRAME TYPE ATTRIBUTE RHF NAM SSF
M64 SN 964 HOST HV IN NA DISABLED
M64
LBK
>piP*N
In output format 2, the attributes listed for each PID are also applicable for each LID
listed under that PID. In the above example, therefore, LID M64 has the attributes H and V,
while LID LBK has the attributes H, V, and B.
60459680 D 7-37
![](asset-e4.png)
y<:*«\
Attributes listed in the ATTRIBUTE column can be listed by name or by mnemonic.
Attribute Name
HOST
LINKED
STORE FORWARD
VALIDATION
LOOPBACK
Mnemonic Description
H I n d i c a t e s t h a t t h i s i s t h e l o c a l h o s t ( t h a t i s , t h e h o s t
you are logged into).
L Indicates that this host is linked to your local host.
S I n d i c a t e s t h a t y d u c a n t r a n s f e r q u e u e d fi l e s t o t h i s
host through an intermediate linked host.
V Indicates that user validation is performed by the local
host as well as by the destination host. If this
attribute is not listed for your local host, user
validation is performed only by the destination host.
B I n d i c a t e s t h a t t h e L I D i s a l o o p b a c k L I D ( u s e d f o r t e s t
purposes).
Entries that can be listed in the RHF, NAM, and SSF columns are as follows:
Entry
IN
NA
OUT
DISABLED
Significance
Indicates that the link to the PID is in service. Note that for RHF
networks and NAM X.25 public data networks, an in service (IN) status is
returned whenever the network is in service, without regard to whether the
remote host itself is available. To determine if the remote host is
available, you can attempt a file transfer to that host.
Indicates that the subsystem is not available or that no link exists to this
PID throught this subsystem.
Indicates that the link to the PID is out of service due to a network fault
condition.
Indicates that the link to the PID has been disabled by the console operator.
7-38 60459680 D
![](asset-e5.png)
/H^v
MACHINE COMMAND
Some programs that ran on mainframes other than models 815, 825, 835, 845, and 855 will not
run on the models 815, 825, 835, 845, and 855 until changes are made in your job. Programs
most likely to run incorrectly on models 815, 825, 835, 845, and 855 are COMPASS programs
with tight instruction-modification loops. The MACHINE command will enable some of these
programs to run correctly on these models.
Format:
MACHINE,EP=state.
Parameter Description
EP=state Specifies whether extended stack purging is selected. EP=ON selects
it and EP=OFF disables it.
Instruction stack purging is extended by specifying ON and is made normal by specifying OFF
and remains in effect until a subsequent MACHINE command or MODE macro alters it. The
initial status of stack purging is site-selectable. For more information on stack purging,
refer to the MODE macro in Volume 4, Program Interface.
To determine if a program will run correctly on models 815, 825, 835, 845, and 855, run the
job with extended stack purging disabled (EP=OFF). If unexpected results occur, do another
run with stack purging extended (EP=ON). When stack purging is extended, the execution time
of the program may be increased. If unexpected results still occur, recode COMPASS programs
or recompile high-level language programs on models 815, 825, 835, 845, and 855.
MFL COMMAND
The MFL command resets the maximum field length for each subsequent job step.
Format:
MFL,CM=nnnnnn,EC=mmmm.
or
MFL, nnnnnn, mimum.
Parameter Description
CM=nnnnnn Specifies the maximum central memory field length (octal is assumed
unless decimal is specified by a D suffix or use of the digits 8 or 9).
EC=mmmm Specifies the maximum extended memory field length. The value of nrnimm
is the actual extended core field length divided by lOOOg.
The first format is the order-independent form and the second format is the order-dependent
form.
60459680 D 7-39
![](asset-e6.png)
The parameter nnnnnn sets an upper boundary for the field length of subsequent job steps.
The value cannot exceed the maximum field length for the job nor can it be less than 1500,
the field length required for the utility (CONTROL) that processes MFL. If extended memory
is assigned for the job, the CM field length cannot be less than 10000. Likewise, the
parameter mmmm sets an upper boundary for the extended memory field length of subsequent job
steps and cannot exceed the maximum field length for the job. If the value 0 (zero) is
entered for CM or extended memory field length, the MFL is set to either the maximum field
length for which you are authorized or the field length specified on the Job command,
whichever is smaller.
The MFL command clears any initial running field length previously established with the RFL
command or the SETRFL macro and allows the system to determine the field length for each
succeeding job step. The system continues to determine field lengths until another RFL
command or SETRFL macro is encountered.
NORERUN COMMAND
The NORERUN command clears the job rerun status.
Format:
NORERUN.
If the NORERUN command has been issued, the job may not be rerun. This may be desirable to
prevent updating of a data base when the job would otherwise be rerun by the operator.
This command is ignored from an interactive origin job.
NOTE COMMAND
The NOTE command creates a file containing lines of data entered as a character string on
the same line as the command.
Format:
NOTE,lfn,NR./linei/iine2/.../linen
Parameter Description
lfn Specifies the name of the file which contains the specified lines.
Default is OUTPUT.
NR Inhibits rewind of lfn. Default is to rewind the file at the
beginning and end of NOTE command execution.
/ Specifies the delimiting character used to separate the individual
en tr ie s th at b ec ome li ne s in th e fil e. I t can b e an y ch ar ac ter. I t
must immediately follow a period or right parenthesis. Multiple
delimiters generate blank lines.
linei Specifies the character string which constitutes one line of data in
lfn.
I f a fi l e c o n t a i n s m o r e l i n e s t h a n c a n b e e n t e r e d w i t h a s i n g l e N O T E c o m m a n d , a s e r i e s o f - ^ ^ v
NOTE commands, each with an NR, can be used. This series should be followed with a PACK '
command since each NOTE command writes an EOR.
7-40 60459680 D
![](asset-e7.png)
igpWN,
Example:
The following sequence of commands creates a procedure file (PFILE) that can insert an input
record after any record in an existing master file (LISTFIL).
NOTE/PFILE,NR.+.PROC,INSERT*I,N.+GET,LISTFIL.+COPYBR,LISTFIL,NEWLIST,N.
NOTE/PFILE/NR.+COPYBR,INPUT,NEWLIST.+COPYEI,LISTFIL,NEWLIST.
NOTE,PFILE,NR.+REPLACE,NEWLIST=LISTFIL.
PACK,PFILE.
SAVE,PFILE.
To insert an input record after the second record in LISTFIL, the user includes the
following command in the job that contains the new input record.
BEGIN,INSERT,PFILE,2.
OFFSW COMMAND
The OFFSW command clears the sense switches for reference by one of your jobs.
Format:
OFFSW, switch! ,switch2 switch^ jsn.
Parameter Description
switchi Specifies the switch(es) to be cleared. You must denote each switch
switchi by an integer in the range of 1 through 6. If you specify 0
for this parameter, the system clears all sense switches.
jsn Specifies the job sequence name (JSN) of the job whose sense switch(es)
will be changed, jsn is an optional parameter; its default is the JSN
of the current job. The system recognizes the jsn parameter by its
alphabetic characters; therefore, jsn can appear anywhere in the
parameter list and can be omitted without leaving a blank parameter
field.
Refer to the description of the ONSW command for further information on sense switch
settings.
60459680 D 7-41 •
![](asset-e8.png)
ONSW COMMAND
The ONSW command sets the sense switches for reference by one of your jobs. The system
stores the sense switch settings in your control point area and copies them to RA at the
beginning of each job step for use by the central program. The sense switch field in the
control point area and the one in RA are updated separately.
Format:
ONSW,switch!,switch2,...^witchn,jsn.
Parameter Description
switch.^ Specifies the switch(es) to be set. You must denote each switch
switch^ by an integer in the range of 1 through 6. If you specify 0
for this parameter, the system sets all sense switches.
jsn Specifies the job sequence name (JSN) of the job whose sense switches
will be changed, jsn is an optional parameter, its default is the JSN
of the current job. The system recognizes the jsn parameter by its
alphabetic characters; therefore, jsn can appear anywhere in the
parameter list and can be omitted without leaving a blank parameter
field.
You can also use the SWITCH command to set the sense switches.
PASSWOR COMMAND
The PASSWOR command changes the passwords associated with your user name. To use PASSWOR,
you must be authorized to change your password. (Refer to the LIMITS command to determine
if you are authorized to change your password.) Your site has the option of using the
password randomization feature. This feature appends a site-determined number (from two to
five) of randomly generated characters to the end of a new password that you select.
If your site uses password randomization, you can enter the PASSWOR command only from an
i n t e r a c t i v e j o b . I f y o u r s i t e d o e s n o t u s e p a s s w o r d r a n d o m i z a t i o n , t h e o r i g i n t y p e o f y o u r ^ ^
j o b m u s t m a t c h t h e t y p e o f p a s s w o r d y o u w a n t t o c h a n g e . I n o t h e r w o r d s , a n i n t e r a c t i v e ^ )
password must be changed from an interactive job, and a batch password must be changed from
a batch or remote batch job.
Format:
PASSWOR,oldpassword,newpassword,XD-expiredate.
or
PASSWOR,oldpassword,newpassword,XT=expireterm.
PASSWOR.
•*5^v
7-42 60459680 D
![](asset-e9.png)
oldpassword
newpassword
XD=expiredate
XT=expireterm
Parameter Description
Specifies the old password. This is a required parameter if
password randomization is used.
Specifies the new password. The new password must be not more than
seven characters long. Your site determines the minimum length of
passwords (4 is the default). This is a required parameter if
password randomization is used.
Specifies the expiration date for the password. The value
expiredate must be a 6-digit string of the form yymmdd, where yy,
mm, dd are 2-digit year, month, and day designators, respectively.
The latest date you can specify and the default expiration date are
site-determined.
You must have special authorization to specify an expiration date
for password (refer to the LIMITS command).
Specifies the life of the password in days. If you specify 0, the
password expires immediately. If you specify 4095 or *, the
password does not expire. The default expiration term and the
maximum expiration term are site-determined (no site can choose a
value greater than 4095).
You must have special authorization to specify an expiration term
for a password (refer to the LIMITS command).
You cannot specify a new expiration date (using either XD or XT) without also specifying the
oldpassword and newpassword parameters. Also, if you omit both the XD and XT parameters
when you enter the PASSWOR command, the default expiration date is the current date plus the
site-determined expiration term.
The first and second formats can be entered either from batch or interactive jobs. These
formats cannot be used if the password randomization feature is used.
The use of the third format is dependent on whether or not your site uses the password
randomization feature.
For sites that do not use password randomization, the third format can be used for added
security and can be entered from either an interactive or batch job. When entered from an
interactive job, the system prompts you to enter each parameter in an overprinted input
field. When entered from a batch job, the system reads the parameters from a record in file
input. This record must be a single line of the format:
oldpassword,newpassword
For sites using password randomization, the third format is the only valid format, and it
must be entered from an interactive job. In this case, the system prompts you to enter
values and also prompts you to specify whether it is a batch or interactive password.
60459680 D 7-43
![](asset-ea.png)
PAUSE COMMAND
The PAUSE command sets the pause bit of one of your executing jobs.
Format:
PAUSE,jsn.
Parameter
jsn
Description
Specifies the job sequence name (JSN) of the job whose pause bit you
w a n t t o s e t . *
You must check the status of the pause bit to effectively use this command. The program
tust becaZ8^ b6C^SVhe.PaUSe bU ±S Set' Similarly, the program does not proceed
just because the pause bit has been cleared. You can write a program that checks the status
4°! P^g^rinterf^e):31'8 *" "" ^ t0 ^ ^^ (refer C° ^ «<*"■ -c^n^lum^8
sft^i/ffnf0 def^ine/hfher a PAUSE °r G0 command has bee* entered, write a program to
H w h e n ever flTJjj£ / S ? f " "V?" *" 8 yStem u n c o n d i t i ^ally c l e a r s b i t 1 * 3 I f wordka whenever the PAUSE/GO command sets/clears the pause flag (bit 12 of word RA) Henrp
nZ on^T^r8 I'' y°,U ^ Ch6Ck the PaUSe flag' CP" ""«"" ^ Sick "because
ss.«™ com^hL^rL^d:17 on N0S 2*but these programs —det— — *
PROTECT COMMAND
I=!^R°^T COnma?d is used to activate or deactivate preservation of the extended memory
your^b is z^roVdlt th" ^T*? **"•'- Warily, the extended memory assig'd L
steps. completion of a job step. With EC=ON, it is preserved between job
section)/6 aUth°rlZed C° USe the PR0TECT command (refer to the LIMITS command in this
NOTE
For mainframes using unified extended memory (UEM),
the execution of absolute programs or program
overlays always resets UEM to zero regardless of
PROTECT command status.
Format:
PROTECT,EC=state.
or
PROTECT,state.
7-44
--^^s.
60459680 E
![](asset-eb.png)
0%B>i.
Parameter Description
EC=state Activates or deactivates extended memory preservation. You can specify
two values for state:
state Description
ON Activates the preservation of memory.
OFF Deactivates the preservation of memory. OFF is the default.
QGET COMMAND
_^ The QGET command assigns a queued file to your job. You must specify the job sequence name
( (JSN) or the user job name (UJN) associated with the queued file. Unless explicitly routed
elsewhere, the file remains with your current job. If a local file already exists with the
same name as the queued file, the QGET operation will be aborted.
Format:
QGET,JSN=j sn,DC=q,UJN=uj n,FN=1fn.
or
QGET,jsn,q,ujn,lfn.
Parameter Description
JSN=jsn Specifies the four-character, system-generated JSN associated with the
queued file.
DC=q Specifies the disposition of the queued file. WT is the default.
q Description
PR Print
PU Punch
PL Plot
W T W a i t
UJN=ujn Specifies the UJN associated with the queued file.
FN=lfn Specifies the local file name for the queued file. If specified, the
JSN is the default local file name. Otherwise, the default is the UJN.
If you specify neither a JSN nor a UJN or specify a UJN associated with two queued files
with the same disposition, a fatal system error occurs.
60459680 E 7_45
![](asset-ec.png)
QUEUE7 COMMAND
The QUEUE7 command allows you to examine the system batch queues in linked SCOPE 2 systems.
The QUEUE7 command has two formats:
QUEUE7,ID=pid,L=lfn,p1,P2,p3,p4.
or
QUEUE7,help.
Parameter
ID=pid
L = l f n
Pi
Description
Specifies the physical identifier (PID) of the SCOPE 2 mainframe to be
searched. If no PID is specified, all mainframes are searched. This
parameter may be specified with the parameter name (ID) and equal sien
omitted. n 6
Specifies the name of the file to receive the QUEUE7 output. The
default is OUTPUT.
Specifies the SCOPE 2 queues (input, output, execute, or punch) to be
displayed. Valid options for Pl are listed below. From one to four
options can be specified. The default is E.
Ei
A
E
Description
Lists jobs found in all queues (E, I, 0, and P).
Execute queue; lists the SCOPE 2 R display. Figure 7-1
provides an example of an execute queue listing.
Input queue; lists the SCOPE 2 R display for input. Figure
7-2 provides an example of an input queue listing.
Output queue; lists the SCOPE 2 H display for output.
Figure 7-3 provides an example of an output queue listing.
Punch queue; lists the SCOPE 2 H display for punch output.
Punch queue listings are the same as output queue listings,
as shown in figure 7-3.
7-46 60459680 D
![](asset-ed.png)
JIP^Ny
Parameter
help
Description
Displays the command format or the physical identifiers for all
available SCOPE 2 mainframes. The following are valid entries for the
help parameter.
help Description
ID Displays physical identifiers for all SCOPE 2 mainframes in
the network.
SYNTAX Displays the QUEUE7 command format,
or
S
/queue7,e
JOBS 6/ 52/ 70 R(Z),1.
ORD ACTION
ID
TYPE
JOBNAME PRTY JOB TIME TIME LCM
O R I G I N U S E D L E F T I N U S E
FIRST ACTION MESSAGE/LAST DAYFILE MESSAGE
J O B B G
STAT
3 M06/**
REPONSE
JOBXXXZ 4000 M06/**
PAUSE. DO NOT GIVE A GO.
0 7 2 6
TESTING ON 606
PA US
4 M06/**
RESPONSE
JOBXXXZ 4000 M06/**
PAUSE. DO NOT GIVE A GO.
0 7 2 6
TESTING ON 606
PA US
5 M06/**
RESPONSE
JOBXXXZ 4000 M06/**
PAUSE. DO NOT GIVE A GO.
0 7 2 6
TESTING ON 606
PA US
QUEUE7 COMPLETE
Column headers
Header
ORD
ACTION ID
JOBNAME
PRTY
JOB ORIGIN
TIME USED
TIME LEFT
LCM IN USE
JOB STAT
BG
60459680 D
Figure 7-1. QUEUE7 Execute Queue Sample Listing
for the QUEUE7 execute queue listing have the following meanings:
Description
The job ordinal.
The station/terminal identifier of the terminal from which the job expects
a response; present only when the job requires a response.
Job name of the executing job.
Priority of the job; must be in the range of 0 to 7777g.
Station/terminal identifier of the terminal from which the job was
submitted.
CPU seconds used by the job.
CPU seconds remaining for execution.
Number of LCM buffers in use by the job.
Current processing state of the job.
Indicates that the job will be scheduled as a background priority job.
7- 47 |
![](asset-ee.png)
FIRST ACTION MESSAGE/
LAST DAYFILE MESSAGE
If there are action messages for the job, the message is the first action
message; otherwise, the message is the last dayfile message.
ACTION Indicates that the above message requests an operator
action such as a tape mount.
CFO RESP Indicates that the above message requests the operator to
respond with a CFO type entry.
RESPONSE Indicates that the above message requests the operator to
respond with a command such as GO or DROP.
/queue7,i
SFTS 10/ 172/ 172 H(Z),I,103.
ORD FILENAME FILE PRTY DEVICE
ORIGIN MT NT
-REQUIREMENTS TIME
YD YL SM SN SP LIMIT
DEPEND BG
107Z JOBXXXZ
110Z JOBXXXZ
M06/** 1002 0 0
M06/** 1002 0 0
0 0 1 0
0 0 1 0
STAT ION M06
INPUT 2
OUTPUT 1
PUNCH 0
M02 MFF M05 MSD
0 0 0 0
0 0 0 0
0 0 0 0
MFU UKWN TOT
0 0 2
0 0 1
0 0 0
QUEUE7 COMPLETE
Figure 7-2. QUEUE7 Input Queue Sample Listing
7-48 60459680 D
![](asset-ef.png)
J$$!0?\
/fPN.
Column headers for the QUEUE7 input queue listing have the following meanings:
ORD Input queue suffixed with the last letter of the SCOPE 2 physical
identifier.
FILENAME File name of the input job as specified on the job card.
FILE ORIGIN Identifier of the station/terminal from which the job was submitted.
PRTY File priority; must be in the range from 0 to 7777g.
DEVICE- The number of magnetic tape or disk devices assigned to the job.
REQUIREMENTS
TIME LIMIT Job time limit as specified on the job card.
DEPEND A two-character dependency identifier as specified on the job card.
B G I n d i c a t e s t h a t t h e j o b w i l l b e s c h e d u l e d a s a b a c k g r o u n d p r i o r i t y j o b ,
/queue7,o
SFTS 10/ 17 2/ 172 H(Z) ,0,103
ORD FILENAME F I L E P R T Y
DESTIN
DISP FORM
CODE CODE
FILE
SIZE
FILE IN
TRANSFER
111Z JOBXXXZ M06/** 4003 PR
STATION M06
INPUT 2
OUTPUT 1
PUNCH 0
M02 MFF M05
0 0 0
0 0 0
0 0 0
MSD MFU UKWN
0 0 0
0 0 0
0 0 0
TOT
2
1
0
QUEUE7 COMPLETE
Figure 7-3. QUEUE7 Output Queue Sample Listing
60459680 D 7-49
![](asset-f0.png)
Column headers for the QUEUE7 output queue listing have the following meanings:
O R D O u t pu t q u e ue o r din a l s uffi x e d w i t h t h e l a s t l e t t e r o f t h e S COP E 2 p h y s i cal
identifier.
FILENAME File name of the output file as specified on the job card.
FILE DESTIN Station/terminal identifier of the terminal to which the output file is to
be routed.
P R T Y F i l e p r i o r i t y ; m u s t b e i n t h e r a n g e f r o m 0 t o 7 7 7 7 g .
DISP CODE File disposition code.
FORM CODE Forms code of the file.
FILE SIZE File length in PRUs.
FILE IN Indicates whether or not the file is currently being transferred to a
TRANSFER station; possible values are Y for yes, and N for no.
RERUN COMMAND
The RERUN command sets job rerun status.
Format:
RERUN.
If the RERUN command has been issued, the operator can rerun the job if necessary. This
command is ignored from a interactive origin job.
RESOURC COMMAND
I The RESOURC command is required in any job that uses more than one tape or removable
auxiliary pack concurrently; it prevents deadlocks with other jobs which may need the same
resources. You do not need to use a RESOURC command if you have only one multivolume tape
file or multipack disk file because the system treats each as only one resource unit.
I Nonremovable auxiliary packs should not be specified on the RESOURC command; non removable
packs are always available to all users.
7-50 60459680 F
/<^^\
![](asset-f1.png)
Format:
RESOURC,rt1=u1/levelx,rt 2=u2/level2 rtn=u=n/leveln.
Parameter Description
rt^ Resource type:
LO 200-cpi, seven-track magnetic tape unit
HI 556-cpi, seven-track magnetic tape unit
HY 800-cpi, seven-track magnetic tape unit
HD 800-cpi, nine-track magnetic tape unit
PE 1600-cpi, nine-track magnetic tape unit
GE 6250-cpi, nine-track magnetic tape unit
MT t S eve n-t rac k ma gne tic ta pe uni t
NTt Nine-track magnetic tape unit (800/1600-cpi)
DBm 885-42 Disk Storage Subsystem (full-track; Km<3)
DCm 895 Disk Storage Subsystem (full-track; l<m<2)
DDm 834 Disk Storage Subsystem (full-track; Km<8)
DGm 836 Disk Storage Subsystem (full-track; l<m<3)
Dim 844-21 Disk Storage Subsystem (Km<8)
DJm 844-41/44 Disk Storage Subsystem (Km<8)
DKm 844-21 Disk Storage Subsystem (full-track; l<m<8)
DLm 844-41/44 Disk Storage Subsystem (full-track; Km<8)
DMm 885-11/12 Disk Storage Subsystem (half-track; l<m<3)
DQm 885-11/12 Disk Storage Subsystem (full-track; Km<3)
DV 819 Disk Storage Subsystem (single-density)
DW 819 Disk Storage Subsystem (double-density)
The value n denotes the number of units (spindles) required for a
particular auxiliary disk file that you will access in your job. In
this case, the rt^ value must correspond to the R=r specification on
the permanent file command that references the disk pack (refer to
section 10).
Ui Maximum number of units of resource type rti this job will use
concurrently; any rtj^ entry can be changed on subsequent RESOURC
commands. (Refer to Altering Resource Requirements.) An rt=0 entry can
be entered to clear a resource type that is no longer required.
level Specifies the security access level at which you want to access magnetic
tape units. The parameter is ignored for auxiliary disk packs. Unless
changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default is the current job access level.
On a secured system, the access level you specify must be valid for the
job (ENQUIRE,B returns this information) and for the device to which you
ar e a ss ig ni ng t he file.
On an unsecured system, the parameter has no effect. The system does,
however, check for valid parameter specifications.
rtRetained for compatibility with NOS 1.2. Refer to restrictions described under Tape Units
in this section.
60459680 F 7-51
![](asset-f2.png)
DEADLOCK PREVENTION
The system manages the use of tape units and disk packs so as to prevent deadlocks from
occurring. A deadlock means that the system, by assigning a tape unit or pack to one job,
prevents another job with currently assigned resources from completing. For example, an
installation with two tape units is processing jobs A and B. Each job needs both units
during some phase of processing. Job A is assigned unit 1. If job B were assigned unit 2,
neither A nor B could complete until the other job relinquishes its assigned unit.
To prevent deadlocks from occurring, the system requires that a RESOURC command be included
in any job that uses more than one tape or disk pack concurrently. Thus, in the previous
example, a RESOURC command is required in both jobs. The information supplied by the
commands enables the system to anticipate the deadlock situation and roll out job B until
job A no longer needs both units. When the RESOURC command is executed, the system first
checks if the specified number of units exceeds the number of units you are authorized to
use or the numb er of un it s avai lab le at t he ins tal la tio n.t If e it her of t hes e sit uat ion s
occurs, the system issues an error message to your dayfile and aborts the job. (Refer to
figure 7-4.)
;*&%.
TFor jobs that use only one tape or pack at a time and do not contain a RESOURC command, /tgs^
the system checks validation limits when the request is made. ^
7-52 60459680 D
![](asset-f3.png)
/gites,
r
Figure 7-4. Resource Commitment Processing (Simplified)
When the job requests a tape or pack,t the system compares the number of units that jobs
being processed have scheduled via RESOURC commands with the number of units actually
assigned. If it determines that the assignment would cause a deadlock (refer to Resource
Overcommitment), it rolls out the job until a deadlock would not occur. If the assignment
would not cause a deadlock, the system searches for the requested tape or pack. If found,
it is assigned to the requesting job. If the pack is not found and the NA keyword was
included in the request or if the tape is not found, the requesting job is rolled out until
the operator makes the pack or tape available.
tRefer to Permanent File Commands in section 9 for a description of disk pack requests
and to Tape Management Commands in section 12 for a description of tape requests.
60459680 D 7-53
![](asset-f4.png)
SINGLE RESOURCE USE
A job that uses only one tape or disk pack concurrently does not need to specify resource
demand with a RESOURC command. However, before assigning the same or a different type of
resource, the current single resource (tape or disk pack) must be returned with either the
RETURN or UNLOAD command. To allow more flexible resource handling, both the RETURN and
UNLOAD functions decrement the default resource demand count from one to zero for jobs
requiring only one tape or disk pack concurrently. For those jobs requiring more than one
tape or disk pack concurrently (as specified by the RESOURC command), UNLOAD does not
decrement the resource demand count; RETURN decrements the resource demand count only when
all concurrent resource demands have been satisfied.
TAPE UNITS
The system supports nine-track magnetic tapes in three different densities. In system -^^
commands, you use a 2-character density resource identifier to specify the correct density.
The identifiers are as follows:
Identifier Density
H D 8 0 0 c p i
PE 1600 cpi
GE 6250 cpi
The 679-2/3/4 tape units are capable of processing both 800-cpi and 1600-cpi nine-track
tapes; the 679-5/6/7 tape units handle both 1600-cpi and 6250-cpi nine-track tapes. An .^^\
800-cpi nine-track tape cannot be processed on a 1600/6250-cpi unit, and 6250-cpi nine-track '
tape cannot be processed on an 800/1600-cpi unit. The NT resource identifier, retained for
compatibility, can be used only to allocate 800/1600-cpi nine-track units} and cannot be
specified concurrently in the same job with HD, PE, and GE resource demands. Default
nine-track resource allocation is by density.
Examples:
Assume that an installation has the following tape drive resources:
• Two 679-4 nine-track tape drives (800/1600-cpi densities).
• Two 679-7 nine-track tape drives (1600/6250-cpi densities).
1. If a job makes a tape unit resource request with
RESOURC,NT=3.
the job is aborted with the message
INSUFFICIENT RESOURCES ON SYSTEM,
because only two units (the 679-4s) meet the NT specification.
tNT resource demand cannot exceed the number of 800/1600-cpi nine-track drives at the
installation. However, at tape assignment time, a 1600-cpi tape mounted on a 1600/6250-cpi
unit is accepted for NT resource demand if it does not cause overcommitment (potential
deadlock).
7-54 60459680 D
![](asset-f5.png)
2. If a job makes a tape unit resource request with
RESOURC,NT=1,PE=1.
the job is aborted with the message
CONFLICTING RESOURCE TYPES.
because the NT specification cannot be used with a density specification
(HD/PE/GE).
3. If a job contains the following commands
LABEL,TAPE,NT,D°PE,VSN=TAPE1.
RESOURC,NT=2.
the job is aborted with the message
CONFLICTING RESOURCE TYPES.
because the LABEL command requested a tape unit by density (the default);
therefore, later commands cannot schedule tape units using the NT specification.
Density identifiers are provided for seven-track tape units even though these units do not
have alternate densities. This is done for consistency of format. The LO, HI, HY, and MT
resource identifiers are all equivalent, and the last specification of any one of these is
the seven-track tape unit demand for the job. For example, the resource request
RES0URC(HI=1,HY=2) results in two seven-track tape resources being allocated for the job.
RESOURCE OVERCOMMITMENT
Under certain conditions, the system overcommits resources, provided all jobs with currently
assigned resources can complete. For example, an installation with three tape units is
processing jobs A and B. Included in each job is a RESOURC command scheduling two units.
Job A requests its first tape. It is assigned the tape (unit 1) because there are enough
un it s av ai la ble fo r jo b A t o com pl et e. J ob B re qu es ts i ts fi rs t ta pe . It is as si gned t he
tape (unit 2) because either A or B can complete if assigned the last unit, and when the job
that is assigned the last unit completes, the other can then use that unit and also
complete. Job B then requests and is assigned its second tape (unit 3). It completes its
operations (that is, terminates or returns the files on the tape) and makes the unit
available for job A to complete.
NOTE
In a multimainframe environment, only the
configuration of the machine on which the
job is processed is considered in the
overcommitment algorithm.
60459680 D 7-55
![](asset-f6.png)
/c^'cSK
ALTERING RESOURCE REQUIREMENTS
The system manages its resources by keeping totals of the number of units of each device
type scheduled and assigned to jobs. The number of units scheduled and the number of units
assigned to a job can vary during job processing.
To change the number of units of a device type scheduled for this job, you can issue another
RESOURC command. When decreasing the number of units scheduled for the job via a RESOURC
command, the total resulting scheduled units must not be less than the number of units
currently assigned to the job. If the resulting total would be less than the number
currently assigned, the system aborts the job with an error message.
If the job has tape and/or removable pack units assigned to it when it attempts to increase
its resource demands, the system determines if the request would cause a deadlock. If it
would, it aborts the job with an error message.
NOTE
Always return all units assigned to your
job before issuing another RESOURC command
to increase resource demands. This action
prevents a possible job abort caused by a
potential deadlock condition.
The scheduled units can also be decreased by a RETURN command if the job, at the time of the ^
return, is using its maximum scheduled units (refer to the description of the RETURN command
in section 9).
Example:
The first RESOURC command schedules two 800-cpi, nine-track tape units. The two LABEL
commands assign the tape units to the job. Because the maximum scheduled units were used
concurrently, the RETURN command decreases the scheduled tape units to zero. The second
RESOURC command schedules two 844-21 disk units and one 800-cpi, nine-track tape unit.
SAMSJOB,CM50000,T40.
USER,SJGREEN,WGT.
CHARGE,*.
RES0URC,HD=2.
LABEL,X,D=HD,VSN=TAPE1.
LABEL,Y,D=HD,VSN=TAPE2.
RETURN,X,Y.
RESOURC, DI1=2,HD=1.
-EOI-
**^^V
7-56 60459680 D
![](asset-f7.png)
UNIT ASSIGNMENT
The method of assigning units depends on the resource type. For example, all tapes and all
private disk packs not accessible by alternate users can only be assigned to one job at a
time. All public packs and those private packs accessible by alternate users are shareable,
and therefore, can be assigned to several jobs at the same time.
On indirect access file requests, the pack is charged to the job in fulfilling its resource
demand only if the request causes the pack to be mounted. For direct access file requests,
the pack is charged to the job when the first ATTACH of a direct access file is made.
A unit is assigned to a job until the job terminates or all direct access files residing on
the unit that are assigned to the job are returned. At this point, a tape or a nonshareable
pack can be dismounted. A shareable pack, however, can be dismounted only when there are no
files residing on the unit that are assigned to any of the jobs sharing the pack.
NOTE
In GET requests for indirect access files,
a pack is assigned to a job only as long as
the pack is actually being used (that is,
until the system retrieves the local copy
of the file). Therefore, during a series
of GET requests, the operator may determine
that the pack is not being used and dis
mount it. If you have a direct access file
on the pack, you can avoid this situation
by attaching the direct access file before
issuing the GET requests.
A single job cannot have more than 36 removable pack devices attached to the job
concurrently.
RFL COMMAND
The RFL command sets the initial running field length for each subsequent job step when
neither the routine for processing that step nor a loader table specifies a field length
(refer to Field Length Control in section 3).
Format:
RFL,CM=nnnnnn,EC=mmmm.
or
RFL,nnnnnn,mmmm.
Parameter Description
CM=nnnnnn Specifies the central memory field length (octal is assumed unless
decimal is specified by a D suffix or use of the digits 8 or 9). The
value is rounded up to the nearest multiple of 100g.
Specifying nnnnnn as 0 removes the effect of the previous RFL command
and returns the setting of the field length to system control.
EC=mmmm Specifies the extended memory field length in octal. The value of
mmmm is the actual extended memory divided by lOOOg.
60459680 D 7-57
![](asset-f8.png)
The parameters may be specified positionally, by keyword, or intermixed positionally and by
keyw ord . If i nte rmi xed , the positional pa ram ete rs are evaluated ac cor din g to t heir po sit ion
among all the parameters.
The values of nnnnnn or mmmm cannot exceed the values specified on the last MFL command or
the maximum allowed for the job.
Prior to the appearance of the RFL command (or SETRFL macro), the system determines the
field length for each job step, provided no field length is specified by a system routine or
loader table (refer to Field Length Control in section 3).
ROLLOUT COMMAND
The ROLLOUT command suspends job execution and places the job in the rollout state. This
releases the control point, central memory, and extended memory assigned to the job. You
can specify a time period that must elapse before the job is returned. Otherwise, the job
scheduler usually returns the job to execution when its priority is the highest of the jobs
rolled out (refer to Rollout Control in section 3).
Format:
ROLLOUT,t.
Parameter Description
t Optional time delay measured in job scheduler delay intervals. Values "y,
for t range from 0 to 262080 (777700g) intervals. Although the
default base is decimal, octal values can be specified by a B suffix.
Typically, a job scheduler delay interval is one second but can be site-determined.
RTIME COMMAND
The RTIME command requests that the time be read from the real-time clock and issued to the
dayfile (in seconds). This is the accumulated time since the last system deadstart. ."**%
Format:
RTIME.
The dayfile message format is:
RTIME nnnnnn.nnn SECS.
| 7-58 60459680 D
![](asset-f9.png)
SETASL COMMAND
The SETASL command sets the system resource unit (SRU) limit for an account block. An
account block is the job step sequence whose execution is charged to an account (refer to
SRU Limit Control in section 3). The account is specified by the charge and project numbers
on a CHARGE command, or if no CHARGE command is required, by the user name on the USER
command. Each user name and each account has an SRU validation limit (refer to the LIMITS
and ENQUIRE commands). Except for interactive jobs, the default account block SRU limit
(set during CHARGE or USER command processing) is the smaller of the user name and the
account validation limits. For interactive jobs, the default limit is 64 SRUs.
Format:
SETASL,s.
Parameter Description
s Maximum number of SRUs allowed for account block execution. Although
the default base is decimal, octal values can be specified by a B suffix
on the value.
s must be greater than or equal to the current job step SRU limit* and
less than or equal to the SRU limit associated with your user name.
Exceptions to this rule are the asterisk (*) and a value of 32760
(77770B) or greater. These exceptions set the account block SRU limit
to the validation limit.
If the account block SRU limit is reached during account block execution, the system issues
an error message and terminates the job (refer to Exit Processing in section 5).
tThe job step SRU limit must be lowered in the job before the account block SRU limit is
lowered. Refer to the SETJSL command in this section.
60459680 H 7-59
![](asset-fa.png)
SETCORE COMMAND
The SETCORE command presets each word within the field length except for RA+2.
Format:
SETCORE,p.
or
SETCORE,-p.
Parameter Descripton
p Any of the following: (If a minus sign precedes the parameter p, the
complement of p is set in core.)
P
0
ZERO
INDEF
INF
Fill Characters
0
Zeros (0)
Indefinite (1777 0000 0000 0000 0000)
Infinite (3777 0000 0000 0000 0000)
Each word within the field length (except for RA+2) is set to p. If p is omitted, the
system assumes p=0.
Calling the CYBER loader destroys the effect of a SETCORE command since the loader uses
memory as a work area.
To preset memory within a load sequence, use a LDSET,PRESET command as described in the
CYBER Loader Reference Manual.
/**^s.
^■S\
y^>v
7-60 60459680 F
![](asset-fb.png)
SETJAL COMMAND
The SETJAL command changes the security access level of the current job. Initially, your
job has the lowest possible access level that is valid for your job (ENQUIRE,B returns this
information). Refer to Security Features in Section 3 for a detailed discussion of access
levels•
Format:
SETJAL,AL=level.
Parameter Description
AL=level Specifies the security access level you want assigned to the job.
Unless changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
On a secured system, the access level you specify must be valid for the job. In addition,
to lower the access level of your job, you must be authorized to do so (refer to the LIMITS
command).
On an unsecured system, the command has no effect. The system does, however, check for
valid p ar ame te r sp eci fic at io ns .
60459680 D 7 -61 |
![](asset-fc.png)
SETJOB COMMAND
The SETJOB command changes some of the current job's attributes. You can change the user
job name (UJN), can redirect the disposition of output if the job is not interactive or
becomes a detached interactive job, and can change the job processing option for job
termination or job suspension.
The SETJOB command does not take effect until the job terminates or is suspended. If you
specify more than one SETJOB command, the last one takes precedence.
Format:
SETJOB,UJN=ujn,DC=dc,OP=op.
or
SETJOB,ujn ,dc ,op,
Parameter
UJN=ujn
DC=dc
OP=op
Description
Changes the job's default UJN to ujn. A UJN must be seven or less
alphanumeric characters. For interactive jobs, the default is the
user index hash (refer to the ENQUIRE command). Otherwise, the
default is the UJN specified on the Job command.
Specifies the disposition for output upon job termination. The
default for all jobs is DF. You cannot change the output disposition
for an interactive job unless the job terminates as a detached
interactive job.
dc Description
TO Queues output with a wait disposition.
NO Discards output.
DF Specifies default output processing. The output disposition
depends on the job's origin type (refer to File Types in
section 2). No output is queued for interactive jobs.
Specifies the job processing option the system exercises upon detached
interactive job when it is no longer executing. Not applicable to
noninteractive jobs. The default is SU.
op Description
SU The job remains in a suspended state until recovered or
timed out (refer to the RECOVER command).
TJ The system terminates the job.
Job attributes associated with omitted parameters remain unchanged.
7-62 60459680 D
![](asset-fd.png)
SETJSL COMMAND
The SETJSL command sets the system resource unit (SRU) limit for each subsequent job step
(refer to SRU Limit Control in section 3). Except for interactive jobs, the default job
step SRU limit (set during CHARGE or USER command processing) is the smaller of the user
name and the account validation limits (refer to the LIMITS and ENQUIRE commands). For
interactive jobs, the default job step limit is 64 SRUs. From an interactive job, you can
increment your job step SRU limit to complete job step execution as described in the
following paragraphs.
Format:
SETJSL,s.
Parameter Description
s Maximum number of SRUs allowed for job step execution. Although the
default base is decimal, octal values can be specified by a B suffix on
the value. The value s must be greater than 0 and less than or equal to
the current account block SRU limit, and the SRU limit associated with
your user name. Exceptions to this rule are the asterisk (*) and values
greater than 32760 (77770B). These values set the job step SRU limit at
the validation limit if the account block SRU limit is set at the
validation limit.
The system issues an error message when the job step SRU limit is reached. A job step
within a batc h jo b is then termina ted (re fer to Exit Process ing in sect ion 5). In
interactive jobs, you can increment the SRU limit after receiving the SRU limit message or
terminate the job. If the job is suspended because a job step or the job itself exceeded
its SRU limit, the message
*SRU LIMIT*
ENTER S TO CONTINUE OR STOP TO END JOB STEP.
TYPED AHEAD INPUT MUST BE REENTERED.
is issued. You can enter one of the following:
Entry
S,nnnnn
Description
Increases the SRU limit by 64 units. Job execution continues. The
64-unit increment can be changed by your site.
Increases the SRU limit by nnnnn decimal units. Job execution
continues. You can enter octal units by specifying a B after the octal
number.
S,; Increases the SRU limit to your maximum. Job execution continues.
STOP Terminates the job step. Subsequent commands, if any, are not processed,
Any increase to the SRU limit through either S or S,nnnn is in effect only for the current
job step. When the job step terminates, the account block SRU limit and job step SRU limit
revert to their original values, set by default or by the SETASL and SETJSL commands,
respectively. Entering S,* in response to an SRU LIMIT message could cause the interactive
session in progress to exceed the account block SRU limit set by the SETASL command or by
default. The system then issues an SRU LIMIT message after a job step has begun. To remedy
this situation, use the SETASL command to raise the account block SRU limit above the
current number of accumulated SRUs for the interactive session.
60459680 H 7-63
![](asset-fe.png)
^%\
The account block SRU limit must be raised before the job step SRU limit can be raised.
Refer to the SETASL command in this section. When a limit occurs, any typed ahead input
will be discarded since it would be processed as a response to the limit message.
SETPR COMMAND
The SETPR command decreases the CPU priority of a job. A user job cannot increase its
priority.
SETPR,p.
Parameter Description
p Specifies the priority, 1 < p < 70g. "^)
Upon job initiation, a job is assigned the maximum priority allowed for its service class.
(The installation defines these priority values.) If a job's CPU priority is lower than
that of other jobs, the job is assigned control of the CPU only when jobs of a higher
priority do not need it.
SETTL COMMAND
The SETTL command sets the CPU time limit for each subsequent job step. Each user name is ^*^\
validated for a maximum job step time limit (refer to the LIMITS and ENQUIRE commands).
When you do not specify a time limit, the system sets the limit at 64 CPU seconds.t
Interactive jobs can increment their job step time limit to complete job step execution
(refer to Section 8).
Format:
SETTL,t.
Parameter Description
t Maximum number of CPU seconds allowed for job step execution. Although
the default base is decimal, octal values can be specified by a B suffix
on the value.
t must be greater than 0 and less than or equal to your validated time
limit. Exceptions to this rule are the asterisk (*) and values greater
than 32760 (77770B). These values set the job step time limit at your
validated time limit.
To set a time limit for job step execution on one CPU of a dual-processor machine, you must
include a USECPU command in the job. Otherwise, the time limit is set for the cumulative
job step execution time on both CPUs.
The system issues an error message when the job step time limit is reached. A job step
within a batch job is then terminated (refer to Exit Processing in section 5). In
interactive jobs, you can increment the time limit after receiving the time limit message or
terminate job.
TYour site can change this default.
I 7-64 60459680 H
![](asset-ff.png)
If the job is suspended because a job step exceeded its time limit, the message:
♦TIME LIMIT*
ENTER T TO CONTINUE OR STOP TO END JOB STEP.
TYPED AHEAD INPUT MUST BE REENTERED.
is issued and you can enter one of the following:
Entry Description
T Increases the central processor time limit by 64 CPU seconds. Job
execution continues. The 64 CPU second increment can be changed by your
site.
T,nnn nn Increa se s the cent ra l proc essor time l imit b y nnnn n deci ma l se co nds.
Job execution continues. You can enter octal seconds by specifying a B
after the number.
T » * I n c r e a s e s t h e c e n t r a l p r o c e s s o r t i m e l i m i t t o y o u r m a x i m u m . J o b
execution continues.
Causes the job to go through normal abort procedures (for example, EXIT
processing which can be useful when using procedure files).
STOP Terminates the job step. Subsequent commands, if any, are not processed.
Any increase to the central processor time limit through either T or T,nnnn is in effect
only for the current job step. When the job step terminates, the central processor time
limit reverts to its original value, previously set by default or by the SETTL command.
When a limit occurs, any typed ahead input will be discarded since it would be processed as
a response to the limit message.
In the following example, a program exceeds its allocated time limit. The user enters T to
increase the time limit and the program then runs to completion.
List
00100 PROGRAM T
00110 DO 6 1=1,2500
00120 DO 6 J=1,4000
00130 A=1
00140 6 CONTINUE
00150 END
READY.
set t l,,10
READY.
run
*TIME LIMIT*
ENTER T TO CONTINUE OR STOP TO END JOB STEP.
TYPED AHEAD INPUT MUST BE REENTERED.
t
SRU 66.835 UNTS.
RUN COMPLETE.
60459680 H 7-65
![](asset-100.png)
SHELL COMMAND
The SHELL command enables or disables shell program processing of system commands.
A shell program is a user-written program (usually in COMPASS) which redefines the set of
commands that can be entered by a user. A shell program can:
• Limit a user to a subset of NOS commands; the shell program can define which NOS
commands the user can or cannot enter.
• Redefine the effects of a NOS command. A shell program redefines a particular
command by defining an alternate command or series of commands to be executed
whenever the user enters the original command. For example, you could redefine a
user's ATTACH command to execute both an ATTACH and a LIBRARY command for the
specified file, thus making the file a global library.
• Define user-written commands that are not a part of the standard NOS command set.
In effect, a shell program creates a user-defined subsystem that can be imposed on
application users by user name. To enable a shell program for a user name, you can place
the SHELL command in the user's prologue. You can also associate a shell program with a
user name using the MODVAL utility. (MODVAL is described in the N0S2 Administration
Handbook.)
For more information on how to write a shell program, refer to the NOS Reference Set,
Volume 4, Program Interface.
Format:
SHELL.
or
SHELL,spn.
or
SHELL,spn,Pl,...,p7. ^
Parameter Description
spn Specifies the shell program name to be executed.
Pi Specifies parameters to control the loading and execution of the shell
program.
pl Description
E Clears controls if there are errors during the loading of
the shell program. If you do not specify E and such errors
occur, your job is aborted with no EXIT processing.
A Clears controls if the shell program aborts.
L Allows local file loading of the shell program. When
loading the program from a local file, the program must be ^
s t o r e d i n A B S - t y p e r e c o r d s . ( R e f e r t o s e c t i o n 1 5 f o r a ^ ^ %
description of record types.)
7-66 60459680 D
![](asset-101.png)
/i|f«£-\
G A l l o w s g l o b a l l i b r a r y l o a d o f t h e s h e l l p r o g r a m .
S Allows system library load of the shell program.
T Specifies that the system monitor commands directly from the
terminal.
B Specifies that the system monitor commands outside
procedures.
C Specifies that the system monitor commands inside procedures.
The first format disables shell control.
The second format, specifying only the shell program name, sets the default for pi as A,
S, and B.
The last format specifies the extent of shell program control. To get your shell program
loaded, you must specify at least one of the parameters L, G, or S. To enable any type of
command monitoring, you must specify at least one of the parameters T, B, or C.
Example:
/sheLL,rmsheLl
SHELL,RMSHELL.
/rewind,*
9 FILES PROCESSED,
/ascii
UNAUTHORIZED COMMAND.
In this example, RMSHELL is a shell program that allows execution of REWIND but not ASCII.
The SHELL command causes the system to perform a system library load of RMSHELL, to enable
shell control, to clear controls if the shell program aborts, and to monitor commands
outside procedures.
The system passes REWIND,* to RMSHELL for examination. Since it is part of the subset of
allowed system commands, RMSHELL passes control to the system to process that command
exactly as it is. However, when the system passes the ASCII command to RMSHELL, an
UNAUTHORIZED COMMAND message is issued, and the command is not passed back to the system.
STIME COMMAND
The STIME command requests that the accumulated SRU value for the job be Issued to the job's
dayfile.
Format:
STIME.
Dayfile message format:
STIME nnnnnn.nnn UNTS.
60459680 D 7-67
![](asset-102.png)
SUBMIT COMMAND
The SUBMIT command places a user-supplied job file into the input queue as a separate job.
SUBMIT can reformat the file according to directives within the file. Refer to Job Names in
section 3 for a description of the names associated with the submitted job.
Format:
SUBMIT,Ifn,q,NR.c
Parameter Description
lfn Specifies the name of the file to be submitted to the system for
processing as a batch job. The first record of the file must be in
6-bit display code. The default is the job's primary file.
q Spec ifies dispositio n of j ob output (OU TPUT, PUNCH, PUNCHB, and P8) as
follows:
BC or B Use the default processing for local batch jobs to
dispose of job output at the central site.
NO or N Discard job output at job termination unless the files
have been explicitly routed (default value for
interactive origin jobs). The dayfile is not written to
file OUTPUT.
RB=un or Route job output to the remote batch or interactive
E=un user specified by the user name un. The default for un
is the user name associated with the submitting job.
TO J ob ou tpu t (i ncl ud in g t he da yfil e) is q ue ue d w it h a w ai t
disposition.
N R N o r ew i nd opt i on ; t h e s ub m it fi le and t he fi le s pe c ifie d o n a c RE A D
reformatting directive are not rewound before or after processing. If
NR is omitted, the files are rewound before, but not after processing.
c P r e fi x c h a r a c t e r u s e d t o i d e n t i f y r e f o r m a t t i n g d i r e c t i v e s i n t h e fi l e t o
be submitted (lfn). If omitted, the system assumes c is /.
The number of deferred batch (LDI, SUBMIT, and ROUTE) jobs that you can have in the system
concurrently depends on your validation (refer to the LIMITS command in this section). If
this limit is exceeded, an error message is issued to the dayfile, and the SUBMIT command is
not processed.
For SUBMIT to process reformatting directives, the first line of the submit file must be a
cJOB directive. Each line preceded by a prefix character is recognized as a reformatting
directive. The prefix character is specified on the SUBMIT command (/ by default).
Throughout this description, the letter c, preceding a directive, denotes the prefix
character. Reformatting directives may be interspersed throughout the submit file as long
as transparent submit mode is not in effect. Transparent submit mode is selected by the
cTRANS directive and requires you to observe special rules when inserting subsequent
directives into the file (refer to description of TRANS and NOTRANS directives).
7"68 60459680 E
![](asset-103.png)
The system does not process reformatting directives unless the first line of the submit file
contains the cJOB directive. Other directives can follow the cJOB directive (that is, they
can precede the job and/or USER commands), but the first two commands following the cJOB
directive must be a Job command and a USER command, respectively. The USER command can be
inserted in the form of a cUSER directive. For example, the following sequences of lines
are both valid:
lnj cJOB
ln2 ujn,parameters.
ln^ USER,username,password, (or cUSER)
or
lnj cJOB
ln2 cNOSEQ
ln3
ln4
ujn,parameters.
USER,username,password, (or cUSER)
lnj, ln2, ln3, and ln^ are optional line numbers.
You can include line numbers on the submit file and specify which line numbers are to be
removed during reformatting with the cSEQ and cNOSEQ directives. This is especially useful
if the submit file contains a BASIC program where line numbers are a requirement of the
language. If line numbers are included in a submit file, the file must begin with a cJOB
directive.
The reformatting directives available are described as follows:
Directive
cJOB
cUSER
cCHARGE
Description
Indicates that the submit file is to be reformatted and selects the
following default reformatting directives. The default directives
re main in eff ect unt il s pe cifi ed o ther wise .
cNOTRANS (disabled by cTRANS)
cSEQ (disabled by cNOSEQ)
cPACK (disabled by cNOPACK)
Th e cJ OB d ir ectiv e mu st be th e fir st l in e of th e su bm it fi le. If
omitted, the file is not reformatted. If line numbers are included in a
submit file, the file must begin with a cJOB directive.
Inserts a USER command identical to that of the submitting job during
reformatting. SUBMIT does not insert a password in the new USER
command. Hence, you cannot use the cUSER directive when routing jobs to
remote hosts (ST=lid parameter of the Job command) that do not support
NOS 2 security features. Further, you can only use this directive to
create the first USER command in a job.
Inserts a CHARGE command that is identical to the CHARGE command
currently in effect for the submitting job. If no CHARGE command is in
effect for the submitting job, this directive has no effect on the
SUBMIT file.
60459680 E 7-69
![](asset-104.png)
Directive Description
c E O R I n d i c a t e s t h a t a n e n d - o f - r e c o r d m a r k i s t o b e p l a c e d a t t h i s p o i n t i n
the submit file during reformatting.
cEOF Indicates that an end-of-file mark is to be placed at this point in
the submit file during reformatting.
c S E Q I n d i c a t e s t h a t t h e f o l l o w i n g l i n e s m a y b e p r e c e d e d b y l i n e n u m b e r s a n d
requests that they be removed (default value).
cNOSEQ Reverses the effect of the cSEQ directive. No attempt is made to
remove leading line numbers from subsequent lines. This is especially
useful when line numbers are required (such as in a BASIC program).
cPACK Requests that all succeeding end-of-record and end-of-file marks be ^
removed (default value). This directive applies only to internal EOR
and EOF marks that currently exist. The cEOR and cEOF reformatting
directives are not affected.
cNOPACK Reverses the effect of the cPACK directive. Requests the system not
to discard succeeding internal end-of-record and end-of-file marks
that currently exist.
cTRANS Requests transparent submit mode. In transparent submit mode, SUBMIT
ignores reformatting directives until an EOR or EOF mark is
encountered. The EOR or EOF mark cannot be a mark to be created by a ^^^
cEOR or cEOF directive. SUBMIT performs the following procedure for
transparent submit mode processing.
1. Read cTRANS directive.
2. Check if the next line is a reformatting directive. If it is not,
skip steps 3 and 4.
3. Process reformatting directive. If it is a cNOTRANS directive,
end transparent submit mode processing.
4 . R e t u r n t o s t e p 2 . )
5. Select transparent submit mode and read lines until an internal
EOR or EOF mark is encountered.
6. If the cPACK directive is in effect, remove the EOR or EOF mark.
7. Return to step 2.
7-70 60459680 G
![](asset-105.png)
Directive Description
The cTRANS directive is typically used in conjunction with the cREAD
directive. The cREAD directive copies the contents of an existing
file into the submit file at the location of the cREAD directive.
Because the file is read in transparent submit mode, no check for
reformatting directives is attempted until an internal EOR or EOF is
encountered. The cREAD directive must follow the cTRANS directive and
must be located before the first succeeding line that is not a
reformatting directive. If not, transparent submit mode is selected
before the cREAD directive is encountered and the cREAD is ignored.
The cSEQ or cNOSEQ directive in effect before transparent submit mode
was selected has no effect upon the submit file or the file being read
(cREAD) while transparent submit mode is in effect. However, the
cPACK or cNOPACK directive in effect before transparent submit mode
was selected remains in effect after it is selected.
cNOTRANS Reverses the effect of the cTRANS directive and informs the system
th at th e sub mit fil e is t o be e xa min ed o n a li ne -by -li ne b as is. Al l
directives encountered in the submit file while the cNOTRANS directive
is in effect are processed. This directive is initially selected by
default and remains in effect until a cTRANS directive is encountered
in the submit file.
/SP^N
Be careful in placing this directive in the submit file. If
transparent submit mode is selected, this directive can possibly be
ignored unless it immediately follows either a cREAD directive or an
internal EOR or EOF mark.
cREAD.lfn Requests that the system read the contents of the specified file, lfn,
and insert that file in place of the cREAD directive in the submit
file, during reformatting. Reading terminates when an EOF or EOI is
encountered on lfn. If the file to be read is not currently local to
the job, the system automatically attempts a GET and then an ATTACH on
the file. If lfn is not specified in the directive, TAPE1 is
ass umed . If th e file spe ci fie d canno t be fo un d or th e rea d file i s
found to be busy (direct access files only), the job is terminated.
The file specified by lfn in the cREAD directive is automatically
rewound before the read operation unless the NR parameter is specified
on the SUBMIT command. In this case, the rewind directive must
precede the cREAD directive in the submit file if it is desired to
rewind file lfn before the read operation begins. The system returns
all files specified in cREAD directives before completion of the job.
If the cPACK directive is in effect when the file lfn is read, all
internal EOR marks are removed. If the cNOPACK directive is in
effect, all internal EOR marks are read into the submit file in the
proper position during reformatting.
60459680 D 7 -71 |
![](asset-106.png)
Directive Description
Unless transparent submit mode is in effect when file lfn is read,
each line of that file is also checked for a reformatting directive.
Any directives contained in the file, except another cREAD, are
processed. The cREAD directive cannot be nested. In addition, any
directives in effect before the cREAD directive is processed remain in
effect for the file being read, unless transparent submit mode is
selected. Then, only the cPACK or cNOPACK directive remains in effect
fo r the fil e bei ng r ea d. M or eov er, on ly t ho se d ir ect ive s that
immediately follow an internal EOR in the file being read are
processed.
If the file to be read is a binary file, it is recommended that the
cTRANS directive be used to ensure that binary data is not mistaken
for a reformatting directive. The cTRANS directive should immediately
precede the cREAD directive in the submit file, if used.
cREWIND,lfn Requests that the system rewind file lfn to the beginning-of-
information (BOI). If lfn is not supplied, TAPE1 is assumed. This
directive is required only if the NR parameter is included in the
SUBMIT command. Otherwise, file lfn is automatically rewound.
This directive is used in conjunction with the cREAD directive. Thus,
if it is desired to rewind a file before the read operation begins,
this directive must precede the cREAD directive in the submit file.
cjEC=c2 Indicates that the prefix character is to be changed from c^ j
(current prefix character) to c2 (new pre fix ch aracter). The new
prefix character code is used to recognize all subsequent reformatting
directives until further changed.
Input lines must not exceed 150 6-bit characters. SUBMIT processes the first 80 characters
as the command. The remaining 70 characters are discarded and may contain a sequence number
or comments. If a line exceeds 150 characters, the results are unpredictable.
If the submitted job contains an invalid USER command, the job entering the SUBMIT command
i s a b o r t e d . T h i s c o n s t i t u t e s a s e c u r i t y c o n fl i c t ( r e f e r t o t h e U S E R c o m m a n d l a t e r i n t h i s . ^ s s v
section). The security count for the user name that entered the SUBMIT command is ^^)
decremented. If this results in a security count of zero, the job is immediately terminated
with no EXIT processing (you are logged out if the job is interactive). For further
information concerning use of the SUBMIT command from an interactive terminal, refer to
Volume 2, Guide to System Usage.
Consult your job's dayfile to determine the cause of any errors that occurred during job
processing. The dayfile for the submitted job is disposed according to the disposition
parameter on the SUBMIT command.
When you submit a batch job from an interactive job, all output is dropped (unless requested
otherwise by the disposition parameter). This includes the dayfile output. Therefore, make
provisions within your job to save the contents of the dayfile if a processing error
occurs. You can do this by including the following commands at the end of the command
record.
EXIT.
- DAY FILE ,l fn.
REPLACE,lfn.
7-72 60459680 D
![](asset-107.png)
SWITCH COMMAND
The SWITCH command sets the sense switches for reference by one of your programs.
Format:
SWITCH,switchj,switch2,...,switchn,jsn.
Parameter Description
switch^ Specifies the switch(es) to be set. You must denote each switch
switch^ by an integer in the range of 1 through 6. If you specify 0
for this parameter, the system sets all sense switches.
jsn Specifies the job sequence name (JSN) of the job whose sense switches
will be changed, jsn is an optional parameter, its default is the
current job. The system recognizes the jsn parameter by its alphabetic
characters; therefore, jsn can appear anywhere in the parameter list and
can be omitted without leaving a blank parameter field.
UPROC COMMAND
The UPROC command specifies a user prologue, a program the system executes each time you
start a job.
Format:
UPROC,FN=pfile.
UPROC,pfile.
Parameter Description
pfile One of your permanent files that contains the desired prologue. If
pfile contains more than one procedure, the system executes only the
first one. If you omit the FN=pfile parameter or give pfile the value
of zero, the system will no longer execute a user prologue.
The system executes your user prologue only after it processes your user validation and
charge information but before it initiates job recovery processing. Depending on the length
and nature of your user prologue, you may want to initiate recovery processing before your
user prologue ends. For example, if your user prologue aborts, the system does not initiate
recovery processing. To do this, place the RECOVER command within your user prologue (refer
to section 8 for the RECOVER command and section 4 for the writing of procedures).
60459680 H 7-73
![](asset-108.png)
USECPU COMMAND
The USECPU command specifies which central processor is to be used when more than one is
available for processing.
Format:
USECPU,n.
Parameter Description
n Specifies which central processor to use.
Jft Description
0 Use either central processor.
1 U s e C P U 0 .
2 U s e C P U 1 .
The USECPU command may be used only when the system is running on a model 72-2x, 73-2x,
74-2x, 174, 720-2, 730-2, 6500, 6700, 830-2, 865-2, or 875-2. On a model 74-2x or 6700, CPU
0 is the parallel processor, and CPU 1 is the serial processor. On the other systems, both
CPUs are serial processors. This command is ignored on single CPU machines.
USER COMMAND
The system uses the parameters on the USER command to determine if you are an authorized
user, which resources you are validated to.use, and the extent (limits) to which you may use
those resources.
No commands are allowed between the Job and USER commands in noninteractive jobs. If this
is attempted, the first command is interpreted as an invalid USER command, and the submitting
job is aborted with appropriate messages to the dayfile. The submitted job is dropped.
Format:
USER,username,password,familyname.
Parameter Description
username Specifies a one- to seven-character alphanumeric user name.
password
familyname
Specifies an alphanumeric password. Its maximum length is seven
characters; its minimum length is defined by the installation.
Specifies an optional parameter identifying the familytof permanent file
devices on which your permanent files reside. Specify a family name
when the system can access more than one permanent file device family.
If this is not the first USER command of the job or it is the first USER
command from a job submitted from another job, you must not specify a
family name different from the current one unless you are so authorized
(refer to the LIMITS command).
t Refer to section 2 for a description of permanent file device families,
| 7-74
'-^\
60459680 H
![](asset-109.png)
This command also defines controls and validation limits for the job and defines your
permanent file base. An installation may operate with secondary USER commands either
enabled or disabled. If the system is a secured system, secondary user commands cannot be
enabled. Only if secondary USER commands are enabled, may you specify a different permanent
file catalog or family during job processing by issuing another USER command. The system
only associates permanent file validation limits with this new user name. The remaining
v al i d at i o n l imi t s s til l r e flec t t h o se o f t h e u ser n ame s pe c i fie d a t j ob i n it i a ti o n ( r ef e r t o
the LIMITS command earlier in this section).
On a secured system or on an unsecured system with secondary USER commands enabled, an
invalid USER command is processed as a security conflict. Your job aborts and your security
count is decremented. If this results in your security count being set to zero, batch jobs
will terminate without EXIT processing. At a terminal, you will be immediately logged out
with no dayfile messages issued to the terminal. If the security count is not zero, the job
rstep is aborted with appropriate messages to the terminal and the dayfile and with EXIT
processing enabled (unless explicitly disabled).
On an unsecured system with secondary USER commands disabled, any secondary USER command
will be invalid and aborts the job. This is not a security conflict and the security count
is not decremented.
The password is deleted from the USER command before this command is issued to the dayfile.
Normally, the familyname parameter need not be included on the USER command. However, if
you make a practice of specifying your family name each time you submit a job, you can be
sure that your job will be processed even if your normal system is not available and your
permanent file family is moved to a backup system. If, after the first USER command, you do
not specify a familyname on the USER command, your permanent file family remains the same.
If you specify the 0 (zero) familyname, your permanent file family becomes the system
default family.
Example:
An installation has two systems, A and B. System B provides backup service for system A.
The system default family name for system A is AFAM, and the system default family name for
system B is BFAM.
During normal operations, system A user CWJONES with password JPWD could enter either of the
following USER commands.
USER,CWJONES,JPWD.
USER,CWJONES,JPWD,AFAM.
System B user JDSMITH with password SPWD could enter either of the following commands.
USER,JDSMITH,SPWD.
USER,JDSMITH,SPWD,BFAM.
If system A failed, user CWJONES would be required to enter
USER, CWJONES, JPWD, AFAM .
to identify his family of permanent file devices. User JDSMITH could enter either of the
USER commands as before because the default family name would still be valid.
60459680 H 7-75 |
![](asset-10a.png)
Normally, the familyname parameter need not be included on the USER command. However, if
you make a practice of specifying your family name each time you submit a job, you can be
sure that your job will be processed even if your normal system is not available and your
permanent file family is moved to a backup system. If, after the first USER command, you do
not specify a familyname on the USER command, your permanent file family remains the same.
If you specify the 0 (zero) familyname, your permanent file family becomes the system
default family.
Example:
An installation has two systems, A and B. System B provides backup service for system A.
The system default family name for system A is AFAM, and the system default family name for
system B is BFAM.
During normal operations, system A user CWJONES with password JPWD could enter either of the
following USER commands.
USER,CWJONES,JPWD.
USER,CWJONES,JPWD,AFAM.
System B user JDSMITH with password SPWD could enter either of the following commands.
USER,JDSMITH,SPWD.
USER, JDSMITH, SPWD, BFAM.
If system A failed, user CWJONES would be required to enter
USER,CWJONES,JPWD,AFAM.
to identify his family of permanent file devices. User JDSMITH could enter either of the
USER commands as before because the default family name would still be valid.
7-76 60459680 D
■^5v
![](asset-10b.png)
COMMANDS FOR INTERACTIVE JOBS
There are many system commands that you can use only in interactive jobs or that were
designed primarily for interactive use. Unless specified otherwise, these commands cannot
be used in procedures. This section describes these commands under the following headings:
Terminal Control Commands
ASCII LINE
AUTO NORMAL
BRIEF SCREEN
CSET TDU
EFFECT TIMEOUT
KEY TRMDEF
• Subsystem Selection Commands
ACCESS FORTRAN
BASIC FTNTS
BATCH NULL
EXECUTE
• Interactive Status Commands
ctD
ctE
ctS
• Job Processing Commands
0^\
APPSW LOGOUT
BYE NOSORT
DIAL RECOVER
EXPLAIN REDO
GOODBYE RUN
HELLO Secure Login
HELL07 SHOW
HELP TEXT
HELPME WHATJSN
LIB
LIST XMODEM
LOGIN
Primary File Editing Commands
ALTER
DELETE
DUP
LIST
MOVE
READ
RESEQ
WRITE
WRITEN
60459680 G 8-1
![](asset-10c.png)
TERMINAL CONTROL COMMANDS
The terminal control commands change the characteristics of the terminal and vary the source
and format of information given to and received from the system. You can enter these
commands at any time after you successfully log in.
ASCII COMMAND
If you are at an ASCII terminal, this command allows you to use the ASCII 128-character set
and to place the terminal in ASCII mode. On non-ASCII terminals, this command allows the use
of up to 128 of the characters defined for the terminal. The ASCII command allows you to
enter lowercase letters that are interpreted by the system rather than translated to upper
case as is done in normal mode.
Format:
ASCII
In ASCII mode, characters entered from the terminal are translated into 6/12-bit display
code. On an ASCII terminal, 6/12-bit display code consists of 95 graphic characters and 33
control characters (the 128-character set). The standard ASCII graphic 64-character set con
tains only the first 64 (or 63 depending on an installation option) of these 95 characters.
In normal mode, you are restricted to these 64 (or 63) characters. Characters of the ASCII
graphic 64-character set are processed internally as 6-bit display code characters. The
additional characters that make up the ASCII 128-character set are processed internally as
12-bit display code characters. Refer to appendix A for further information on display codes
and character sets.
The system normally receives all ASCII characters except line feed, carriage return, NUL,
EOT, DEL, and the logical backspace character. Control characters (line feed, cancel line,
and backspace) are not received unless in full-ASCII or special editing mode. Commands can
be entered in either uppercase or lowercase regardless of ASCII mode.
NOTE
If a correspondence code terminal is being
used, you must be in ASCII mode in order to
use the full correspondence code set.
You can include this command in a procedure.
8-2 60459680 F
![](asset-10d.png)
y*$^m5v
yfl^Stey
AUTO COMMAND
The AUTO command automatically generates five-digit line numbers.
Format:
AUTO,nnnnn,iiii
Parameter
iiii
Description
Specifies the beginning line number; default value is 00100.
Specifies the increment value added for each succeeding line number;
default value is 10.
To exit from auto mode, you press the cancel line character followed by @, thus deleting
the current line. You can also exit from auto mode by entering the termination sequence.
You can then enter a new command on the next line.
You can alter the line numbering sequence by deleting the line with the cancel line
character and then entering a new beginning line number. You should exercise caution when
doing this since the AUTO command is still in effect and continues generating line numbers
using the original increment value. Thus, if a line number is generated that already exists
in the file, the original contents of that line are lost and must be reentered. The
increment value cannot be altered unless a new AUTO command is entered.
In the following example of the AUTO command, the user deletes a line number to change the
numbering sequence and then deletes another line number in order to place a character in
column 6.
READY,
auto
00100 program header
00110 write 1000
00120
•DEL*
00230 1000 format(15x,' headings')
00240 write 2000
00250 2000 formatd5x,'author',9x,'title',15x,
00260
*DEL*
00260+ 'publisher'^,'cost')
00270 stop
00280 end
00290
•DEL*
List
00100 PROGRAM HEADER
00110 WRITE 1000
00230 1000 FORMAT(15X,'HEADINGS')
00240 WRITE 2000
00250 2000 FORMAT (15X,'AlfTH0R',9X,'TITLE',15X,
00260+ 'PUBLISHER',6X,'C0ST')
00270 STOP
00280 END
READY.
User enters cancel line character.
User enters entire line.
User enters cancel line character.
User completes the line.
User enters cancel line character.
60459680 C 8-3
![](asset-10e.png)
BRIEF COMMAND
The BRIEF command suppresses all full and partial headers produced by certain commands (for
example, LIBEDIT). It also prevents the system from echoing editing changes you make to the
primary file when using the primary file editing commands described later in this section.
Format:
BRIEF
To clear the effect of the BRIEF command, use the NORMAL command.
CSET COMMAND
The CSET command sets the character set mode of the terminal.
Format:
CSET,mode
Parameter Description
mode Specifies terminal character set mode.
ASCII Selects ASCII mode (ASCII 128-character set). ^^\
NORMAL Selects normal mode (ASCII graphic 63/64-character set).
The CSET command may also appear in a procedure file.
NOTE
The CSET command sets only the terminal
character set. If you specify the NORMAL
parameter, you do not affect auto or brief
mode.
EFFECT COMMAND
The EFFECT command enables or disables the output format effectors supplied by IAF. With
the IAF effectors disabled, you control terminal output by supplying an appropriate effector
as the first character of each output line; the system interprets the first character of
each line as an effector and inhibits printing of the character.
Format effectors control carriage positioning on output operations. The effectors for
specific terminal classes are described in the Network Access Method Version 1/Communications
Control Program Version 3 Terminal Interfaces Reference Manual. This command is valid for
all terminals connected through NAM.
8-4 60459680 F
![](asset-10f.png)
NOTE
Control bytes 0001, 0002, 0003, 0005, 0013,
0014, and 0015 should not be used with IAF
effectors disabled.
Format:
EFFECT,mode.
Parameter
mode
Description
Specifies whether or not IAF automatically supplies format effectors.
Values that can be entered for mode are as follows:
Value Description
SYSTEM Format effectors are supplied by IAF. This is the default |
value.
U S E R F o r m a t e f f e c t o r s a r e u s e r -su p p l i e d a s t h e fi r s t c h a r a c t e r |
of each output line.
When format effectors are user-supplied (i.e., EFFECT,USER |
is specified), all format effectors are supported except
those that specify carriage positioning after output.
Specifically, the slant (/) and period (.) effectors are
not supported.
You can include this command in a procedure.
KEY COMMAND
The KEY command maintains key definition files which define the function keys for a CDC 721
terminal. KEY is used to create, edit, display, or load a definition file.
The KEY command is valid only for a CDC 721 terminal operating in screen mode. To use this
command, select the appropriate option from those listed below and enter the command with
that option. The KEY command provides you with interactive help to assist you in creating,
editing, or loading the definition file.
Format:
KEY,option,filename.
or
KEY?
/jfp&V,
60459680 H 8-5
![](asset-110.png)
Parameter
option
Description
Any of the following options.
Opti on Description
HELP Gives a brief description of each option available. The
filename parameter is ignored.
CHECK Checks to see if function key definitions are already
loaded into the terminal. If not, the definitions in file
filename are loaded.
DEFAULT Sets key definitions to the NOS system default keys. The
filename parameter is ignored. The default keys are:
HELP key = HELP
EDIT key = FSE
STOP key = CTRL-T followed by carriage return
DISPLAY Displays the key labels for function keys Fl through F16.
EDIT Initiates creation or editing of a key definition file.
KEY first searches for a local file by the specified name,
the n fo r an indirect access permanen t file. If fil en ame
does not exist, it is created. The edited file is saved
or replaced at completion of editing.
LOAD Loads key definitions into the terminal from the specified
file.
PRINT Creates a local file called KEYPRNT on which the key
definitions are listed from the specified filename.
filename The name of the key definition file. Default is KEYDEFS.
? Lists the options and prompts you for an option and filename.
The KEY command may appear in a procedure file.
/*^^\
8-6 60459680 F
![](asset-111.png)
LINE COMMAND
The LINE command specifies that your terminal is to be operated in line (or scrolling) mode,
as opposed to screen mode. Commands and features affected by the LINE command include
CATLIST, FSE, screen formatting, and the display of NOS procedure parameters.
The LINE command also identifies the terminal model to the system and initiates a search for
the terminal definition file for that model (unless the CDC 721 terminal was specified;
characteristics of this terminal are preloaded into the system so that no definition file is
required). The system uses the following search order in attempting to find the definition
file:
• A loc al fi le ca lle d T ERMLI B (cr ea ted usi ng th e TD U uti lity) .
• An indirect access permanent file called TERMLIB under your user name.
• An indirect access permanent file called TERMLIB under user name LIBRARY
(UN=LIBRARY). Your site may maintain a system file containing common terminal
definitions.
If TERMLIB is found under your user name or under user name LIBRARY, the system copies the
terminal definition to a local file called ZZZZTRM for later use by NOS full screen display
features. The terminal files listed below for the TM parameter are released with the system
and are always available once you have identified your terminal in a LINE or SCREEN command.
Format:
LINE,TM=model.
LINE,model.
Jf^N
60459680 F 8-6.1
![](asset-112.png)
Parameter Description
TM=model Specifies the terminal model. The value specified for model is the
terminal mnemonic defined in the terminal definition file or the
terminal mnemonic for one of the following preloaded terminal
definitions:
model Description
721 CDC 721 terminal.
721V3 CDC 721 terminal version 3.
722 CDC 722 terminal.
72230 CDC 722-30 terminal.
VT100 DEC VT100 terminal.t
Z19 Zenith Z19 or Z29 terminal or Heathkit H19 terminal.tt
ADM3A Lear Siegler ADM3A terminal.ttt
A D M 5 L e a r S i e g l e r A D M 5 t e r m i n a l . t t t
TV924 TeleVideo 924 terminal .tttttt
TV950 TeleVideo 950 terminal.tttttt
TV955 TeleVideo 955 terminal.tttttt
T 4 1 1 5 Te k t r o n i x 4 1 1 5 t e r m i n a l . t t t t
3270 IBM 3270 terminal.ttttt
PCONxx IBM PC using CDC CONNECT, xx is the current level of
CONNECT.
If you want your terminal to have the type-ahead capability, append T
to the model name you are using in the LINE command. Type-ahead
allows you to press a function key two or more times in quick
succession, rather than pressing it once and waiting for the system to
execute it before pressing it a second time.
If this parameter is omitted, the terminal model is left unchanged.
You can include this command in a procedure.
tDEC is a registered trademark of the Digital Equipment Corporation,
tt Zenith Z19 and Z29 are products of the Zenith Corporation. Heathkit H19 is a product
of the Heath Corporation,
ttt Lear Siegler ADM3A and ADM5 are products of the Lear Siegler Corporation,
tttt Tektronix 4115 is a product of the Tektronix Corporation.
tttttlBM 3270 is a product of the IBM Corporation.
| tttttt TeleVideo 924, 950, and 955 are products of TeleVideo Systems, Inc.
^ S S ^ .
8-6.2 60459680 H
![](asset-113.png)
NORMAL COMMAND
The NORMAL command reverses the effect of the ASCII; AUTO; BRIEF; CSET,ASCII; and NOSORT
commands on both input and output. The system initially assumes that this command has been
entered. Normal mode uses the ASCII graphic 63/64-character set. All lowercase letters are
converted to uppercase (refer to ASCII command) and all command headers are printed (refer
to BRIEF command).
Format:
NORMAL
SCREEN COMMAND
The SCREEN command specifies that your terminal is to be operated in screen mode, as opposed
to line (or scrolling) mode. Commands and features affected by the SCREEN command include
CATLIST, FSE, screen formatting, and the display of NOS procedure parameters. The SCREEN
command also identifies the terminal model to the system and initiates a search for the
terminal definition file for that model (unless the CDC 721 terminal was specified;
characteristics of this terminal are preloaded into the system so that no definition file is
required). The system uses the following search order in attempting to find the definition
file:
• A local file called TERMLIB (created using the TDU utility).
• An indirect access permanent file called TERMLIB under your user name.
• An indirect access permanent file called TERMLIB under user name LIBRARY
(UN=LIBRARY). Your site may maintain a system file containing common terminal
definitions.
If TERMLIB is found under your user name or under user name LIBRARY, the system copies the
terminal definition to a local file called ZZZZTRM for later use by NOS full screen display
features. The terminal files are always available once you have identified your terminal in
a SCREEN or LINE command.
Format:
SCREEN,TM=model.
SCREEN,model.
60459680 G 8-7 |
![](asset-114.png)
Parameter Description
TM=model Specifies the terminal model. The value specified for model is the
terminal mnemonic defined in the terminal definition file or the
terminal mnemonic for one of the following preloaded terminal
definitions:
model Description
721 CDC 721 terminal.
721V3 CDC 721 terminal version 3.
722 CDC 722 terminal.
72230 CDC 722-30 terminal.
VT100 DEC VT100 terminal.t
Z 1 9 Z e n i t h Z 1 9 o r Z 2 9 t e r m i n a l o r H e a t h k i t H 1 9 t e r m i n a l . t t
ADM3A Lear Siegler ADM3A terminal.ttt
A D M 5 L e a r S i e g l e r A D M 5 t e r m i n a l . t t t
T4115 Tektronix 4115 terminal.tttt
3270 IBM 3270 terminal, ttttt
PCONxx IBM PC using CDC CONNECT, xx is the current level of
CONNECT.
If you want your terminal to have the type-ahead capability, append T
to the model name you are using in the SCREEN command. Type-ahead
allows you to press a function key two or more times in quick
succession, rather than pressing it once and waiting for the system to
execute it before pressing it a second time.
If this parameter is omitted, the terminal model is left unchanged.
You can include this command in a procedure.
tDEC is a registered trademark of the Digital Equipment Corporation,
ttZenith Z19 and Z29 are products of the Zenith Corporation. Heathkit H19 is a product of
the Heath Corporation,
tttLear Siegler ADM3A and ADM5 are products of the Lear Siegler Corporation.
ttttTektronix 4115 is a product of the Tektronix Corporation,
ttttt IBM 3270 is a product of the IBM Corporation.
8-8 60459680 G
![](asset-115.png)
TDU COMMAND
The TDU command calls an interactive procedure to compile a terminal definition file and
store the compiled definition (in load capsule form) in a user library. The user library
can later be accessed by a SCREEN or LINE command to define terminal characteristics to the
system.
The user library to receive the load capsule must be a local file. If the library file you
specify does not exist as a local file, TDU creates it. If you do not specify a library
file, TDU uses a local file with the name TERMLIB. If no file TERMLIB exists, TDU creates
it.
Format:
TDU,I=definition,L=listing,LIB=library
Parameter Description
I=definition Specifies the terminal definition file. The file must be in 6/12-bit
display code. For information on how to create a terminal definition
file, refer to the Screen Formatting Reference manual.
L = l i s t i n g S p e c i fi e s t h e l i s t i n g fi l e . T h e l i s t i n g fi l e i s a c o p y o f t h e i n p u t
file with error messages, if any, interspersed. The default name is
OUTPUT.
LIB=library Specifies the library file to receive the load capsule. The default
name is TERMLIB. To be used by the SCREEN and LINE commands, the
libra ry fil e m us t b e a l oc al fil e o r a n in dir ec t acces s fil e c al le d
TERMLIB.
The TDU command may appear in a procedure file.
0S^*,
60459680 F 8-8.1/8-8.2
![](asset-116.png)
![](asset-117.png)
TIMEOUT COMMAND
The TIMEOUT command can change your status from the no-timeout status to the standard
timeout status. In standard timeout status, you are automatically logged out after 10
minutes of inactivity. If you have a no-timeout status (refer to the LIMITS command), the
terminal remains connected until you log out. The TIMEOUT command changes your status for
the session in progress.
Format:
TIMEOUT
TRMDEF COMMAND
The TRMDEF command changes one or more of the characteristics of your terminal (for example,
the page length or the page-wait attribute). You can also use terminal definition commands
(also called network commands) for this purpose. Typically, you would use TRMDEF in a
prologue to set your terminal attributes for each login—especially if you tend to log in at
the same type of terminal each time. You would use network commands to make on-the-fly
changes during a given terminal session.
The network commands for a NAM/CCP network are in appendix J. The CDCNET Terminal Interface
Usage manual describes network commands for a NAM/CDCNET network.
Format:
TRMDEF,L=lfn,tCl=vi,...,tcn=vn
Parameter Description
L=lfn Specifies an optional file on which the terminal redefinition
information is written. If lfn is omitted, file OUTPUT is assumed,
If another file is specified, the changes are implemented when the
file is li s te d o r c op i ed t o the ter mi n al .
tCi=Vi Specifies the terminal characteristic to be changed, tci is speci
fied by a two-character mnemonic listed in table J-l in appendix J.
The NUL and DEL characters can be specified on the TRMDEF command
although they cannot be used with the terminal definition commands
(refer to table J-l). You may not use the mnemonics AR, CH, HN, HS,
MS, and TM for tCi.
The new option, Vi, is any value in the range given for that termi
nal c haracterist ic i n table J-l. It can be a d ecima l value , a coded
value with a special meaning (such as PR for printer), or a single
character. You can specify multiple values for DL, EB, EL, and XL if
you separate the values with slants (/), but only as specified in
appendix J. If the new option is a single character, it can be given
in any of the following formats.
>^P^V
Description
Any alphanumeric character (a character with a display
code in the range from 0 through 44g).
60459680 G 8-9
![](asset-118.png)
Parameter Description
Vj Description
$v$ Any character, including special characters, delimited by
dollar signs (for example, $*$). If the character is a
dollar sign ($), it must be specified using two dollar
signs (for example, $$$$).
vvvB Octal value of an ASCII character (for example, 52B, which
would be equivalent to an entry of $*$).
vvD Decimal value of an ASCII character (for example, 42D,
which would be equivalent to an entry of $*$).
Xvv Hexadecimal value of an ASCII character (for example,
X2A, which would be equivalent to an entry of $*$).
NOTE
If a numeric value for a single ASCII
character is specified without a pre- or
post-radix, the value is assumed to be octal
unless it contains an 8 or 9. In this case,
it is translated as decimal.
Using TRMDEF with NAM/CDCNET
The CDCNET network defines a larger set of terminal attributes than does the CCP network.
This gives you a greater degree of control of your terminal and its connections. For
example, associated with the page wait attribute under CCP are two attributes under CDCNET:
HOLD_PAGE (HP) and HOLD_PAGE_OVER (HPO). To avail yourself of this added control, you must
use the CDCNET mnemonics for the attributes when using TRMDEF. The CDCNET Terminal ^^^
Interface Usage manual describes the CDCNET mnemonics along with any restrictions for y4^%
parameter specifications with TRMDEF.
If you do choose to use the CCP mnemonics for terminal attributes even though you are using
a CDCNET network, the system maps the CCP attributes into the corresponding CDCNET
attributes. But again, it will not be a one-to-one mapping. The CDCNET Terminal Interface
Usage manual shows how the two sets of attributes interrelate.
8-10 60459680 G
![](asset-119.png)
Examples
TRMDEF,IN=PT This command changes the input device to a paper tape reader, thus
allowing you to read data and commands from a tape. It has the
same effect as the corresponding terminal definition command (that
is, entry of the control character followed by IN^PT).
TRMDEF,DL=C20/X03/TO This command defines three different transparent input delimiters.
• the transmission of 20 characters
• the entry of an ETX character code
• a t i m e o u t
The first delimiter encountered terminates transparent input mode.
The operating system and the network check the validity of the parameter values you enter.
The operating system does the preliminary check (syntax and general range checking) and the
network does the specialized parameter checking. If you specify an invalid parameter value,
the system informs you and the terminal characteristics in effect before you entered the
command remain in effect. In general, the system informs you immediately of the error. The
only case where you do not receive immediate notification of the error is where you have
specified the L=lfn parameter and the system does not detect the error in its preliminary
check. However, the network notifies you of the error as soon as you try to actualize the
changes (copy file lfn to the terminal). Also, in this case, the system does not resort to
EXIT processing if you entered the command from a procedure.
SUBSYSTEM SELECTION COMMANDS
A subsystem creates an environment that facilitates the execution of certain classes of jobs.
For instance, the FORTRAN subsystem provides a framework in which you can conveniently enter,
compile, and execute FORTRAN 5 programs.
The access, execute, BASIC, FORTRAN, FTNTS, and null subsystems greatly restrict your job
capabilities. Under them, you cannot enter many of the commands described in this manual un
less you use the X,ccc command format (described later in this section). To have the largest
set of system commands at your disposal, use the batch subsystem. If you want to use the RUN
command, however, you must select either the BASIC, execute, FORTRAN, or FTNTS subsystem.
The following commands select a specific subsystem. You should always be aware of the sub
system that is currently active. For example, attempting to execute a FORTRAN program while
operating under the BASIC subsystem causes meaningless diagnostic messages to be issued. To
determine which subsystem is currently active, enter the ENQUIRE command.
NOTE
The subsystem may be automatically selected
by the system at login if this has been set
in th e val id at io n fil e (r ef er t o th e LIM IT S
command). You can also set the subsystem in
your prologue with the SET command.
60459680 G 8-11 |
![](asset-11a.png)
Use the execute subsystem whenever possible to conserve system resources. Efficiency can be
achieved when certain programs are used frequently. For example, a source code program
created under the FORTRAN subsystem must first be compiled before it can be executed (this
process is automatic; you need only enter the RUN command). The program automatically goes
through a compilation phase, which produces an executable object code program, and the
object code program is then executed. Thus, greater efficiency can be achieved by retaining
INTERACTIVE STATUS COMMANDS
The system executes interactive status commands immediately. You may enter them while the
system is executing another command. The system queues other commands that are typed prior
to prompts (refer to section 17).
Format:
ct x
Parameter Description
ct ct is the network control character defined for the terminal (refer to
the CT command in appendix J). Do not include a space between ct and
x. We show one here only for clarity.
x x c a n b e t h e l e t t e r D , E , o r S .
With the exception of the Detach command (ctD), the system generates only a line feed if you
enter an interactive status command during one of the following states:
Text mode
Auto mode
Input mode (a program is waiting for input)
During login
During the processing of the interruption or termination sequence
DETACH COMMAND (ctD)
The Detach command detaches a terminal job from the terminal. You can detach a job at any
time d uring a terminal s ession. To deta ch th e job during o utput, first enter the i nterrup
tion sequence and then enter the Detach command. Otherwise, ctD alone is sufficient.
When you detach a job, the following message appears at the terminal:
JOB DETACHED, JSN=jsn
All files assigned to the detached job remain assigned to it.
![](asset-11b.png)
0H^\
yf^N
J$<ffis<\
Examples
TRMDEF,IN=PT This command changes the input device to a paper tape reader, thus
allowing you to read data and commands from a tape. It has the
same effect as the corresponding terminal definition command (that
is, entry of the control character followed by IN=PT).
TRMDEF,DL=C20/X03/TO This command defines three different transparent input delimiters.
• the transmission of 20 characters
• the entry of an ETX character code
• a t i m e o u t
The first delimiter encountered terminates transparent input mode.
The operating system and the network check the validity of the parameter values you enter.
The operating system does the preliminary check (syntax and general range checking) and the
network does the specialized parameter checking. If you specify an invalid parameter value,
the system informs you and the terminal characteristics in effect before you entered the
command remain in effect. In general, the system informs you immediately of the error. The
only case where you do not receive immediate notification of the error is where you have
specified the L=lfn parameter and the system does not detect the error in its preliminary
check. However, the network notifies you of the error as soon as you try to actualize the
changes (copy file lfn to the terminal). Also, in this case, the system does not resort to
EXIT processing if you entered the command from a procedure.
SUBSYSTEM SELECTION COMMANDS
A subsystem creates an environment that facilitates the execution of certain classes of jobs.
For instance, the FORTRAN subsystem provides a framework in which you can conveniently enter,
compile, and execute FORTRAN 5 programs.
The access, execute, BASIC, FORTRAN, FTNTS, and null subsystems greatly restrict your job
capabilities. Under them, you cannot enter many of the commands described in this manual un
less you use the X,ccc command format (described later in this section). To have the largest
set of system commands at your disposal, use the batch subsystem. If you want to use the RUN
command, however, you must select either the BASIC, execute, FORTRAN, or FTNTS subsystem.
The following commands select a specific subsystem. You should always be aware of the sub
system that is currently active. For example, attempting to execute a FORTRAN program while
operating under the BASIC subsystem causes meaningless diagnostic messages to be issued. To
determine which subsystem is currently active, enter the ENQUIRE command.
NOTE
The subsystem may be automatically selected
by the system at login if this has been set
in th e val id at io n fil e (r ef er t o th e LIM IT S
command). You can also set the subsystem in
your prologue with the SET command.
60459680 G 8 - 1 1 |
![](asset-11c.png)
A specific subsystem can be associated with an indirect access file so that whenever you
specify that file as the primary file, the associated subsystem is selected automatically.
A subsystem flag can be set when you save the file. If you include the SS=subsystem
parameter on the SAVE command, you can specify any of the valid subsystems. If you enter
SAVE without SS=subsystem and the file is the primary file, the subsystem flag for the
current subsystem with the file is set. To save the primary file with no subsystem
association, you can either enter the null subsystem before saving the file, or enter the
command:
SAVE,lfn/SS=NULL
Automatic subsystem association is made only when the primary file is saved. To associate a
subsystem with a temporary file other than the primary file, it must be saved with the
SS-subsystem parameter specified.
ACCESS COMMAND
The ACCESS command selects the access subsystem. You cannot enter a RUN command under the
access subsystem. While in the access subsystem, you can communicate with another
interactive terminal using the DIAL and WHATJSN commands. You must be authorized to use the
access subsystem (refer to LIMITS command).
Format:
ACCESS
The DIAL and WHATJSN commands can be entered only when the access subsystem is active.
BASIC COMMAND
The BASIC command selects the BASIC subsystem. A RUN command under the BASIC subsystem uses
the BASIC compiler.
Format:
BASIC,ccc
Parameter Description
ccc Specifies a command to be executed after the system executes the BASIC
command. Any valid command is permitted, as well as all valid
parameters for that command.
The following example illustrates the use of the ccc parameter.
BASIC, OLD,PRIME
In this example, the user selects the BASIC subsystem and makes a copy of permanent file
PRIME the primary file. The file name (PRIME) is a valid parameter with the OLD command.
8-12 60459680 D
![](asset-11d.png)
BATCH COMMAND
The BATCH command selects the batch subsystem,
batch subsystem.
Format:
You cannot use the RUN command under the
BATCH,fl
Parameter
fl
Description
Specifies the initial running field length for subsequent job steps.
Entering this value is equivalent to entering the RFL.fl command
(refer to section 7). If fl is omitted, 0 is assumed. If you
implicitly selected the batch subsystem by retrieving an indirect
access permanent file with the OLD command, the field length is either
0 or that entered with the last RFL command.
Unless you have a reason to do otherwise, choose the batch subsystem for normal job proces
sing. The batch subsystem allows you to enter essentially all commands allowed in batch
jobs. Some file management commands and nearly all execution control processing commands are
available in the other subsystems only through the X,ccc command.
Although you can enter any system command from an interactive job, the output produced by
several of these commands is formatted for transmission to a line printer (137 characters per
line). Through use of the L072 command, you can format the output for transmission to a ter
minal (72 to 160 characters per line) but some data may be lost. Refer to the description of
the L072 command in section 9.
EXECUTE COMMAND
The EXECUTE command selects the execute subsystem. A RUN command under this subsystem
executes a previously compiled (object code) program. The RUN command must be entered to
initiate execution.
Format:
EXECUTE,ccc
Parameter Description
ccc Specifies one command to be executed after the system executes the
EXECUTE command. Any valid command is permitted, as well as all valid
parameters for that command.
In the following example, you select the execute subsystem and make a copy of permanent file
OBJFILE the primary file. The file name (OBJFILE) is a valid parameter with the OLD command.
EXECUTE , OLD, OB JF ILE
NOTE
Source language programs cannot be executed
under the execute subsystem.
60459680 D 8-13
![](asset-11e.png)
Use the execute subsystem whenever possible to conserve system resources. Efficiency can be
achieved when certain programs are used frequently. For example, a source code program
created under the FORTRAN subsystem must first be compiled before it can be executed (this
process is automatic; you need only enter the RUN command). The program automatically goes
through a compilation phase, which produces an executable object code program, and the
object code program is then executed. Thus, greater efficiency can be achieved by retaining
the object code program in the permanent file system for later execution under the execute
subsystem. This can be accomplished by using the following commands (under the FORTRAN
subsystem):
RUN,B=lfn
Causes the object code program to be placed on temporary file lfn.
SAVE,lfn/SS=EXECUTE _.
Retains file lfn as a permanent file and sets the execute subsystem flag.
If this is done, subsequent requests for the file using the OLD command causes the execute
subsystem to be selected. Entering the RUN command initiates execution of the object code
program.
FORTRAN COMMAND
The FORTRAN command selects the FORTRAN subsystem. A RUN command under this subsystem uses
the FORTRAN Version 5 compiler.
Format:
FORTRAN,ccc
Parameter Description
ccc Specifies a command in addition to the FORTRAN command. Any valid
command is permitted, as well as all valid parameters for that command,
The following example illustrates the use of the ccc parameter.
FORTRAN, OLD, TAX
I In this example, the user selects the FORTRAN subsystem and makes a copy of permanent file
TAX the primary file. The file name (TAX) is a valid parameter with the OLD command.
8-14 60459680 F
![](asset-11f.png)
FTNTS COMMAND
The FTNTS command selects the FTNTS subsystem. A RUN command under this subsystem uses the
FORTRAN Extended Version 4 compiler.
Format:
FTNTS ,ccc
Parameter Description
ccc Specifies a command in addition to the FTNTS command. Any valid
command is permitted, as well as all valid.parameters for that command,
The following example illustrates the use of the ccc parameter.
FTNTS,OLD, DATA GEN
In this example, the user selects the FTNTS subsystem and makes a copy of permanent file
DATAGEN the primary file. The file name (DATAGEN) is a valid parameter with the OLD command.
NULL COMMAND
The NULL command selects the null subsystem. You cannot use the RUN command under this
subsystem.
Format:
NULL
This command is entered before saving the primary file if you do not want a specific
subsystem flag to be associated with the file. Normally, when you save the primary file, an
internal indicator called the subsystem flag is set to indicate the subsystem currently in
use. That subsystem is automatically selected in each succeeding request for the file using
the OLD command. An alternative way of saving the primary file with no subsystem
association is to specify the SS=NULL parameter on the SAVE command. No automatic subsystem
association occurs when saving temporary files other than the primary file.
If you do not specify a subsystem at login time, the system sets the subsystem specified in
the validation file during login (refer to the LIMITS Command in section 7). Null is the
default.
60459680 D 8-15
![](asset-120.png)
INTERACTIVE STATUS COMMANDS
The system executes interactive status commands immediately. You may enter them while the
system is executing another command. The system queues other commands that are typed prior
to prompts (refer to section 17).
Format:
ct x
Parameter Description
ct ct is the network control character defined for the terminal (refer to
the CT command in appendix J). Do not include a space between ct and
x. We show one here only for clarity.
x x c a n b e t h e l e t t e r D , E , o r S .
With the exception of the Detach command (ctD), the system generates only a line feed if you
enter an interactive status command during one of the following states:
• Te x t m o d e
• Auto mode
• Input mode (a program is waiting for input)
• During login
• During the processing of the interruption or termination sequence
DETACH COMMAND (ctD)
The Detach command detaches a terminal job from the terminal. You can detach a job at any
time d uring a terminal s ession. To deta ch th e job during o utput, first enter the i nterrup
tion sequence and then enter the Detach command. Otherwise, ctD alone is sufficient.
When you detach a job, the following message appears at the terminal:
JOB DETACHED, JSN=jsn
All files assigned to the detached job remain assigned to it.
Subsequent to the detachment, the system creates a new terminal session with a new job
sequence name (JSN). Any commands you entered before or after the detachment that the
system has not yet processed become part of the new terminal job. However, if your job is
executing a procedure when you detach it, the procedure remains a part of the detached job.
The system initiates the new job with recovery dialogue processing (refer to the RECOVER
command in this section).
The detached job executes until one of the following occurs:
• No more commands remain. Detaching a job while it is in the IDLE status causes the
system to reach the end of the command record.
• A f a t a l e r r o r a b o r t s t h e j o b .
8-16 60459680 D
r^^\
![](asset-121.png)
0^\
• The job requests input from the terminal or queues output to the terminal.
• Th e job excee ds i ts time limi t or SRU li mit.
• Certain system requests are encountered.
At this point, the system suspends the detached job (unless you had specified the OP-TJ
parameter on the most recent SETJOB command). The job remains suspended until you recover
it or until it exceeds its timeout period. You can recover an executing or suspended job
with the RECOVER command, which is described later in this section.
You may route terminal output from a detached job to the wait queue. To do this you must
enter a SETJOB command and an ASSIGN command before detaching the job. The SETJOB command
should specify DC=TO. The ASSIGN command should be as follows:
ASSIGN,MS,OUTPUT
The system limits the number of jobs you can detach (refer to the LIMITS command in
section 7).
IMMEDIATE JOB STATUS COMMAND (ctE)
This command requests detailed job status response. You can enter this command while
another command is active, and the system processes it immediately. The following output is
an example of the system's response to a ctE command:
JSN: AADF SYSTEM:
STATUS: IDLE
BATCH SRU: 2.095 FILE NAME: SAMPLE2
ABBREVIATED JOB STATUS COMMAND (ctS)
This command causes the system to give an abbreviated job status response. The system
issues one of the following responses.
Response Description
E XE CUT E S ys t em i s c ur ren tly p r oc e ss i ng you r c omm an d .
IDLE System is waiting for you to enter a command.
WAIT System is waiting for system resources to become available.
60459680 E 8-17
![](asset-122.png)
JOB PROCESSING COMMANDS
The job processing commands allow you to perform a variety of job processing or job-related
operations. These commands can be entered at any time after login is complete.
APPSW COMMAND
The APPSW command allows you to temporarily switch to a secondary (alternate) NAM
application program. The NAM application you originally logged into is called the primary
application. The secondary application that you specify on the APPSW command must be one
that is supported by your site and one that you are validated to use. When you log out of
the secondary application, your terminal reverts to the primary application. While in the
secondary application, your current IAF session is suspended. Upon exiting the secondary ^^
application, your IAF session resumes processing at the point where the APPSW command was -~M^
encountered.
The job issuing the APPSW command must be an interactive terminal job and must be a NAM
terminal connection. The APPSW command is invalid for RDF terminals or any origin type
other than Interactive.
Format:
APPSW,AP=appl,Z.data
APPSW,appl,Z.data
Parameter Description
appl Specifies one of the following NAM applications:
appl Description
IAF Interactive Facility.
ITF Interactive Transfer Facility.
M C S M e s s a g e C o n t r o l S y s t e m .
PLATO PLATO-NAM Interface.
RBF Remote Batch Facility.
TAF Transaction Facility.
TVF Terminal Verification Facility.
V E I A F N O S / V E I n t e r a c t i v e F a c i l i t y.
Z Specifies that any characters following the command terminator are
to be forwarded to the secondary application as data.
data Data to be forwarded to the secondary application, data can be up
to 50 characters long; any additional characters are truncated.
8-18 60459680 H
![](asset-123.png)
j^Wt^
BYE COMMAND
The BYE command ends your session with IAF and either logs you out of your host and
disconnects the terminal or places you under the control of another NAM application.
If you are connected to IAF as your secondary application (refer to the APPSW command
description for more information on secondary applications), entering the BYE command with a
null application parameter returns your terminal connection to the primary application.
Format:
BYE,appl
Parameter
appl
Description
If I AF is y our p rim ar y app lic at ion , app l spe ci fies an a pp lic at ion t o
which you wish to be connected. The following are some supported
applications:
appl
ITF
MCS
PLATO
RBF
TAF
TVF
VEIAF
Description
Interactive Transfer Facility.
Message Control System.
PLATO-NAM Interface.
Remote Batch Facility.
Transaction Facility.
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.
NOS/VE Interactive Facility.
If IAF is your secondary application, you have the following options
for the appl parameter:
appl Description
omitted If you omit the appl parameter, your terminal is
logged out of IAF and is returned to the control
of the primary application.
ABORT If you specify ABORT for appl, an abort status
message is returned to the primary application,
and your terminal is disconnected from both the
primary and secondary applications.
Any other application name will be ignored, and you will be returned
to your primary application.
/ff^N
60459680 H 8-19
![](asset-124.png)
If IAF is your primary application and if you select an application that is available and
that you are validated to use, you are automatically released from IAF control and placed
under the control of the named application. If you do not select another application, you
are logged out of the host and the terminal is disconnected. In this case, IAF responds by
printing:
UN=username LOG OFF hh.mm.ss.
JSN-jsn SRU-S s.sss
Characters=xxxxx KCHS
IAF CONNECT TIME hh.mm.ss.
LOGGED OUT.
The following describes the variable items in the logout information:
Item Description
username User name.
hh.mm.ss. Time of day this command was entered.
jsn Job sequence name.
s.sss Measure of system resources used during IAF connection. The SRU is
a unit of measurement which includes all CPU time, memory usage, and
I/O activity since login to IAF.
xxxxxxxx A count of the total number of input and output characters read
from, or written to, your terminal.
If you switch applications without disconnecting from the network, your terminal's
characteristics do not change.
NOTE
Ensure that all temporary files to be
retained are made permanent before issuing
this command. All files which have not
been saved are released when the BYE
command is processed.
This command can appear in a procedure or in a batch job. If used in this manner, it
terminates the job.
8-20 60459680 G
![](asset-125.png)
DIAL COMMAND
The DIAL command sends a one-line message to another terminal user.
Format:
DIAL,jsn,sss
Parameter Description
jsn Specifies the job sequence name (JSN) of the terminal to receive the
message.
sss Specifies the one-line message.
The receiving terminal displays the message in the format:
FROM sjsn:sss
where sjsn is the JSN of the sending job and sss is the message.
The DIAL command can be entered only if the access subsystem is active. The terminal to
receive the message can have any subsystem active; it need not be under the access subsystem
or have access validation.
You can determine the appropriate jsn by using the WHATJSN command. If the terminal
specified is currently receiving output or has an input request outstanding, the message is
lost. No further attempt to transmit the message is made.
EXPLAIN COMMAND
The EXPLAIN command retrieves an online version of a CDC manual.
Format:
EXPLAIN,M=manual
EXPLAIN,manual
Parameter
M=manual
Description
Specifies the manual you want to retrieve. Your site determines what
manuals are available to you. If you omit the parameter M=manual, the
system generates a menu of the EXPLAIN features.
/ f ^ \
60459680 F 8-20.1/8-20.2 |
![](asset-126.png)
![](asset-127.png)
0^\
GOODBYE COMMAND
Same as BYE command.
Format:
GOODBYE,application
This command can appear in a procedure or a batch job. If it does, it terminates the job.
HELLO COMMAND
The HELLO command logs you out of IAF and switches you to another application or reinitiates
the login sequence. Your terminal's characteristics do not change.
Format:
HELLO,application
If application is specified or if you are logged into IAF as a secondary application (in
which case, the application parameter is ignored), this command is the same as the
BYE,application command.
If application is not specified, this command logs you out of IAF, as in the BYE command,
but reinitiates the login sequence. Any temporary files that are to be retained must be
made permanent before the HELLO command is entered. This form of the command allows a new
user to log in without first having to establish communications with the network by dialing
the terminal telephone number.
This command can appear in a procedure or a batch job. If it does, it terminates the job.
60459680 F 8-21
![](asset-128.png)
HELL07 COMMAND
The HELL07 command allows you to submit a job that requires terminal input or output to a
linked SCOPE 2 system and to communicate interactively with an executing SCOPE 2 job. If
your SCOPE 2 job does not require interactive participation, you can route it to SCOPE 2
with the ROUTE command.
A job you submit through HELL07 (or the ROUTE command) must be a standard SCOPE 2 job using
SCOPE 2 control statements. The job initiates terminal input or output operations by
specifying CNF=YES on a FILE control statement or macro or by issuing a CONNECT macro for a
file.
There are two modes of operation under HELL07: control mode and run mode. In control mode,
the initial mode on entering HELL07, you are communicating with the HELL07 utility. In
control mode you can submit a job to SCOPE 2, drop a job, or obtain status information on a
job. Once you submit a job to SCOPE 2 (by entering a SUBMIT directive), you enter run mode,
in which you interact directly with your job as it executes on the SCOPE 2 system. You
remain in run mode until you enter a termination directive.
The following command calls HELL07 and places the terminal in control mode.
Format:
HELL07.
If your NOS system is attached to a single SCOPE-2 mainframe, HELL07 normally responds with
a control mode prompt indicating that it is ready to accept a directive. The control mode
prompt consists of two asterisks (**). The run mode prompt, two dollar signs ($$), is
discussed under the PROMPT directive below. Both the control mode and run mode prompts are
followed by a ? prompt. The ? prompt appears at the beginning of the input line.
In a multimainframe environment, the following prompt may appear after you enter the HELL07
command•
MAINFRAME=
You respond by entering the logical identifier (LID) of the SCOPE 2 system you want to
access. -If the mainframe you request is not available, the following message appears at the
terminal.
MAINFRAME ID NOT IN ID TABLE
In response to this message you may enter an alternate LID, or you may terminate HELL07
processing by typing END.
HELL07 Directives
Once you have received the control mode prompt (**), you can submit a job, drop a job,
obtain status information, or temporarily exit from HELL07 using the following HELL07
directives. The termination directive, *E0F directive, *E0P directive, and *E0S directive
can be entered only In run mode. All other directives can be entered only in control mode.
8-22 60459680 D
![](asset-129.png)
iff^SN
Directive
ub2
(termination
directive)
JP\
DROP,J
or
DR.
END or E
*EOF
*EOP
*EOS
EXIT
PROMPT,status
00t\,
\
RESUME or R
Function
Suspends terminal communications with the SCOPE 2 job. The terminal
returns to control mode while the job continues to run. You can re
establish communications with the job (reenter run mode) later using
the RESUME directive.
ub2 represents the user break 2 termination sequence recognized by
your terminal. The actual termination sequence varies with the
terminal class; most terminal classes use ) or CTRL/T in the
termination sequence. Refer to Terminating Job Step in Section 16 and
to the B2 terminal definition command in Appendix J for more
information on the termination sequence.
Drops a SCOPE 2 job prior to normal termination. You can then enter a
status request to determine when drop completion has occurred.
Disconnects the terminal from HELL07 and drops any SCOPE 2 job active
at the time the END directive is issued.
Inserts an end-of-information designator into terminal input data.
Inserts an end-of-partition designator into terminal input data.
Inserts an end-of-section designator into terminal input data.
Disconnects the terminal from HELL07 but does not drop an active job
you have submitted to SCOPE 2. This allows you to leave HELL07,
execute other commands, eventually return to HELL07, and resume
monitoring the executing job.
Activates or deactivates the automatic run mode prompt which appears
at the terminal whenever the SCOPE 2 job requests input from the
terminal. The run mode prompt consists of two dollar signs ($$).
When the automatic prompt is off, terminal prompts must be supplied by
the executing SCOPE 2 job. Valid entries for status are as follows.
Status Description
The automatic prompt is activated (default).
The automatic prompt is deactivated.
ON
OFF
Reestablishes terminal communications with an executing SCOPE 2 job.
This directive allows you to reenter run mode after having issued a
termination directive. On reentering run mode, the following message
appears at your terminal.
RESUMING 7000 MODE..
NOTE
If you have no SCOPE 2 job active when the
RESUME directive is issued, the above message
will be preceded by the warning message, NO
7000 JOB ACTIVE. The terminal will then
wait in run mode indefinitely for connected
file input/output with a SCOPE 2 job output.
60459680 E 8-23
![](asset-12a.png)
Directive
STATUS or S
SUBMIT, lfn
Function
Returns status information on the SCOPE 2 job submitted (using the
SUBMIT directive). The response is of the following form.
J OB NAME=jobname USERID=id STATUS=status
where:
Name of last job submitted to SCOPE 2.
Your user ID.
jobname
id
status Indicates the status of the job identified by
jobname. The following values can be returned for
status.
status Description
INPUT Indicates job waiting for terminal input.
OUTPUT Indicates job ready for terminal output.
RUN Indicates job is currently executing.
STOP Indicates job has aborted.
Submits a local file lfn to the SCOPE 2 system for execution and
places the terminal in run mode. The SUBMIT directive must be entered
with no terminator. HELL07 responds to the directive with this
message.
FOftWARDING JOB TO MONITOR
The above message indicates that the job is being validated for
account codes. When validation is completed, the following message
appears.
ENTERING 7000 MODE .. WAIT
This message indicates that the logical file name has been routed to
SCOPE 2 for execution. At this point, you have entered run mode and
are waiting for the job to be scheduled. When the job is ready for
input, the run mode prompt ($$) will appear, unless you have disabled
the automatic prompt using the PROMPT,OFF directive.
If the connection to the SCOPE 2 system is inoperative, the following
message is returned in response to the SUBMIT directive.
7000 INTERACTIVE NOT ENABLED
/"SSHSv
8-24 60459680 D
![](asset-12b.png)
/g$fSVy
0^\
Example:
The sample job below reads interactive input from a terminal and writes the input
information to the output file. The sample job is contained in a local file called
TESTJOB. Following the sample job is an example of an interactive session in which the
sample job is submitted to SCOPE 2 through HELL07.
Sample Job
H7J0B, STM FZ, job card parameters.
ACCOUNT,account card parameters,
FILE (INPUT,CNF=YES)
FILE <OUTPUT,CNF=YES)
WHILE, EF=0, TAG.
COPYR.
ENDW, TAG.
6/7/8/9
Interactive Session
/hello7.
MAINFRAME= ? mfz
**
? submit,test job
FORWARDING JOB TESTJOB TO MONITOR
ENTERING 7000 MODE .. WAIT
**
? 1
1
$$
? 222222
222222
$$
? test abcdefg
TEST ABCDEFG
$$
7
•*
end
60459680 D 8-25
![](asset-12c.png)
HELP COMMAND
The HELP command generates a menu of the online help features and prompts you to make a
selection.
Format:
HELP
There are four online help features:
• A list of all NOS commands, except for compiler calls.
• Help in entering a command (the HELPME feature). HELPME gives a description of the
command and its parameters, prompts you for the parameters, and then executes the
command.
• Access to an online version of selected CDC manuals (the EXPLAIN feature).
• A list of the NAM/CCP network commands.
HELPME COMMAND
The HELPME command gives a brief description of a command and its parameters, prompts you
for parameter values, and then executes the command.
Format:
HELPME,command
Parameter Description
command Specifies a command. You can get a list of commands by using the HELP
command or by requesting help after entering HELPME.
The HELPME command is an interactive procedure. You can get help at any time during your
dialog with HELPME by entering a question mark (or pressing the HELP function key if your
terminal is in screen mode). For more information about help on procedure calls, refer to
Requesting Help on Procedure Calls in section 4.
LIB COMMAND
The LIB command retrieves a copy of an indirect access permanent file from the catalog of
special user name LIBRARY and makes it the primary file.
Format:
LIB,Ifn=pfn/PW=password,PN=packname,R=r,NA,ND,WB
Parameter Description
lfn=pfn Specifies the local file name lfn given the retrieved copy of perma
nent file pfn. If lfn= is omitted, the local copy is called pfn.
PW=password Specifies the password needed to retrieve file pfn if one exists.
8-26 60459680 H
![](asset-12d.png)
rs$^*v
Parameter Description
PN=packname Specifies the auxiliary device on which pfn resides if pfn resides on
one.
R=r Specifies the device type of the auxiliary device on which pfn
resides, only if different from the installation-defined default.
NA Specifies the no-abort option. LIB processing errors do not terminate
the job. The job waits for the mounting of disk packs.
ND Specifies the no-drop option. Local files are not released.
WB Specifies the wait-if-busy option. The job waits for the mounting of
disk packs.
Section 10 contains a detailed description of parameters used on permanent file management
commands•
Direct access files can also reside in the catalog of LIBRARY although another command
method must be used to access these files (described in the following paragraphs). The file
category is private, semiprivate, or public. The permission mode is that which has been
granted for private files or specified in the catalog for semiprivate and public files.
When you enter the LIB command, the system retrieves a copy of the specified indirect access
permanent file and makes it become the new primary file. For example:
f LIB,ABC75/PW=13479,ND
Unless you enter the ND parameter, the system releases all files that do not have the
no-auto-drop status. Certain system scratch files (ZZZZZCO, ZZZZZC1, ZZZZZC2, and ZZZZZLD,
for example) have this status. You can give a local file this status with the SETFS command.
In this example, you retrieve a copy of permanent file ABC75 and it becomes the new primary
file; all local files remain associated with the job. The previous primary file becomes a
nonprimary temporary file. The LIB command accesses only indirect access permanent files.
rYou can enter the following commands to access permanent files in the catalog of LIBRARY
(differences in command function are described).
ATTACH,Ifn=pfn/UN=LIBRARY,PW=password,M=m
This command must be entered to use any direct access permanent files in the catalog
of LIBRARY. The system does not create a temporary file since all input and output
op er at io ns di re ct ly i nv ol ve th e p ermanen t fi le i ts el f. H ow ev er, if yo u w is h to
reference the file by a name other than its permanent file name, you can assign a
local file name (lfn) in the command. The primary file name remains unchanged.
GET,lfn=pfn/UN=LIBRARY,PW=password
This command retrieves a copy of the specified indirect access permanent file (from
the catalog of LIBRARY) for use as a temporary file. The primary file remains
unchanged unless lfn specifies the name of the current primary file.
OLD,1fn=pfn/UN=LIBRARY,PW=password
^-^ The function of this command is identical in all respects to that of the LIB command.
0$$*\
60459680 D 8-27
![](asset-12e.png)
You can access from the catalog of LIBRARY only those files that allow alternate user
access. The system considers all users, except user name LIBRARY, alternate users. A
summary of the rules for alternate user access follows:
• Only those users with permission can access private files.
• All users can access semiprivate and public files providing they know the file name,
password (if one exists for the file), type of access (direct or indirect), and user
name (LIBRARY).
The following forms of CATLIST generate the list of accessible files in the catalog of
LIBRARY.
CATLIST,LO=F,UN=LIBRARY (full listing)
CATLIST,UN=LIBRARY (file names only)
LIST COMMAND
The LIST command lists the contents of a local file. If you want to selectively list lines
of the primary file, use the alternate form of the command described later in this section
under Primary File Editing Commands.
Forma t:
LIST,F=lfn
Parameter Description
F=lfn Specifies the local file to be listed. The default is the primary
file.
LOGIN COMMAND
Same as HELLO command.
Format:
LOGIN,application
This command can appear in a procedure or in a batch job. If used in this manner, the
command terminates the job.
/^9|k
8-28 60459680 D
![](asset-12f.png)
/ffp^v^
LOGOUT COMMAND
Same as BYE command.
Format:
LOGOUT,application
This command can appear in a procedure or in a batch job. If used in this manner, the
command terminates the job.
NOSORT COMMAND
The NOSORT command prevents the system from automatically sorting the primary file by
clearing an internal indicator called the sort flag. Normally, the system sorts the primary
file, if needed, whenever the current command causes it to read the file.
Format:
NOSORT
This command can be used when making additions or other modifications to the primary file.
When followed by the NOSORT command, the modifications create a new logical record in the
primary file. The NOSORT command remains in effect only until the next numbered line of
source code is entered. This causes the sort flag to be turned on again.
/fpsy
60459680 D 8-29
![](asset-130.png)
RECOVER COMMAND
The RECOVER command recovers detached jobs or interrupted terminal sessions. The RECOVER
command can also appear in a procedure.
Format:
RECOVER,JSN=j sn,OP=T
or
RECOVER,jsn,T
or
RECOVER
The parameters are order-independent if you specify the parameters in the keyword=value
form. Otherwise, the parameters are order-dependent.
Parameter Description
JSN=jsn Specifies the job sequence name (JSN) of the detached job.
OP=T Directs the system to abort recovery processing if you have no
recoverable jobs. Otherwise, the system engages you in a recovery
dialog.
If you specify no parameters and have recoverable jobs, the system displays those jobs and
their status and prompts you for further recovery directives.
During job processing, recovery may be necessary in the following cases:
• Your terminal is disconnected from the system without being logged out.
• A system malfunction occurs which requires a restart.
• You want to continue a job you detached.
The length of time before the system times out the job depends on your validation limits
(refer to the LIMITS command) and the site-determined default time-out period.
If you have recoverable jobs in the system, the system automatically displays them after
login. The system lists four attributes of each recoverable job: its job sequence name
(JSN), user job name (UJN), current job status, and the time remaining before the system
forces termination of the job.
| 8 - 3 0 60459680 D
![](asset-131.png)
JpN.
r
0N®f\
Example:
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978, 198X.
yy/mm/dd. hh.mm.ss. LE0T1
CDC NETWORK OPERATING SYSTEM NOS 2
FAMILY: ,username,password,iaf
JSN: ABNA, NAMIAF
RECOVERABLE JOB(S)
JSN UJN STATUS TIMEOUT
ABMK AJLA SCH ROLLED
ABMQ AJLA SUSPENDED 14 MIN.
ENTER GO TO CONTINUE CURRENT JOB,
RELIST TO LIST RECOVERABLE JOBS,
OR DESIRED JSN: go
READY.
There are eight status messages that can appear in the STATUS column:
Status Description
EXECUTING The job is executing.
IDLE The system has reached the end of the job's command record.
INITIAL The job awaits its initial rollin.
I/O ROLLED The system is processing interactive input or output from the job.
SCP ROLLIN The job awaits a rollin for an SCP (system control point) request.
SUSPENDED The job is no longer executing.
T/E ROLLED The rolled out job awaits a time or an event.
SCH R O LL ED T he sc hed ul er ha s r oll ed out t h e job .
If you choose the GO option, the system ends the recovery dialogue. If you choose the RELIST
option, the system relists the recoverable jobs. If you specify one of the JSNs, you get the
following display:
JSN: jsn SYSTEM:subsystem SRU: nnnnnn.nnn FILE NAME: primaryfiLe
STATUS: message
CHARACTER SET: charset MODES: modes
instruction
The following describes the variable items (in lowercase) in the display:
item Description
jsn Job sequence name.
subsystem Interactive subsystem.
60459680 H 8-31
![](asset-132.png)
item
nnnnnn.nnn
primaryfile
message
charset
modes
i n s t r u c t i o n
Description
The SRUs used by the job.
The job's primary file. The system suppresses this field if there is
no primary file.
Message from executing job, if present. Otherwise, the field is blank,
The interactive character set mode (ASCII or NORMAL) of the job.
The prompting mode (BRIEF or PROMPT ON).
The system's instruction on job continuation. There are five
possibilities:
TEXT MODE.
OUTPUT AVAILABLE.
INPUT REQUESTED.
IDLE.
JOB IN SYSTEM.
If the job has output available, the job is started and output continues at the terminal. A
job waiting for input will not start until you enter the input.
In general, recovery is designed to provide minimum inconvenience to you with maximum secur
ity. Certain programs (like the FSE editor) recreate the environment that existed at the
time of job disruption. However, under certain circumstances, recovery of your information
cannot be perfect. Here are three examples of such circumstances:
• In some cases, a few lines of output may be lost when a phone line is disconnected
because data queued in the network cannot be recaptured by IAF.
• If a phone line is disconnected when you are entering lines, you can normally expect
to lose the last few lines you entered.
• When you are reconnected, terminal characteristics for that terminal session are set
to the initial values. If a system prologue or user prologue sets terminal
characteristics, these characteristics are restored during job recovery. If the
recovered job had altered any of the terminal characteristics, they will not be
restored automatically. For example, you set the page width to 90 before being
disconnected. Upon recovery, the page width is set to the initial value for the
terminal class, not to 90.
y^Ofy,
8-32 60459680 D
![](asset-133.png)
The following is another example of job recovery,
READY.
List
00100 LET A=1
00110 INPUT B
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT I," FACTORIAL
00150 NEXT I
00160 END
READY,
run
IS ";A
The user is disconnected before entering data
and logs in again.
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978,198X.
yy/mm/dd. hh.mm.ss. T02A57
CDC NETWORK OPERATING SYSTEM
FAMILY: ,usernam,passwrd,iaf
JSN: AEYT, NAMIAF
RECOVERABLE JOB(S)
JSN UJN STATUS TIMEOUT
ACPJ AJLA SUSPENDED 8 MIN.
ENTER GO TO CONTINUE CURRENT JOB,
RELIST TO LIST RECOVERABLE JOBS,
OR DESIRED JSN: acpj
JSN: ACPJ SYSTEM: BASIC SRU: 0.047
STATUS:
CHARACTER SET: NORMAL MODES: PROMPT ON
INPUT REQUESTED.
FILE NAME: RECOVER
? 10
1
2
3
4
5
6
7
8
9
10
FACTORIAL IS
FACTORIAL IS
FACTORIAL IS
FACTORIAL IS 24
FACTORIAL IS 120
FACTORIAL IS 720
FACTORIAL IS 5040
FACTORIAL IS 40320
FACTORIAL IS 362880
FACTORIAL IS 3.62880E+6
READY.
60459680 F 8-33
![](asset-134.png)
REDO COMMAND
The REDO command allows you to modify and reenter a previously entered command without
retyping the entire command.
Format:
RED0,string/GO
Parameter Description
string Specifies the initial characters of the command to be modified and
reentered, string can be up to ten characters long; however, if a blank
or command terminator appears in the string, it is recognized as the end
of the string. If string is specified, the system searches for the most
recently entered command beginning with that string. If string is
omitted, the system reenters the command immediately preceding the REDO
command.
GO >*1^^\
Reenters the specified command without modification; display of the A
OLD:, MOD:, and NEW: prompts is suppressed.
When you enter the REDO command, the system prints the characters OLD:, followed by the
command to be modified. On the next line, the system prints the characters MOD: as a prompt
for you to enter modifications to the line. You enter modifications using the modification
symbols described below. When you finish your modifications and enter a carriage return,
the system executes the modified command and prints the characters NEW:, followed by the
modified line. Following is an example of a CATLIST command that is altered to specify a
diff er en t fi le na me:
/REDO
OLD: CATLIST,LO=F,FN=BTK
MOD: fac
NEW: CATLIST,LO=F,FN=FAC
In this example, the user spaced over to the last three characters in the line and typed in
a new file name.
The REDO command modification symbols are as follows:
Symbol Effect
space Leaves the character unchanged.
# Deletes the character and shifts the remainder of the line one character to
t h e l e f t .
& Replaces the character with a space.
A I n s e r t s a c h a r a c t e r s t r i n g b e f o r e t h e c h a r a c t e r m a r k e d b y t h e A . T h e
inserted string is terminated by a # or a carriage return. If a A is
followed immediately by a carriage return, the line is redisplayed as
modified up to that point, and further modifications are allowed.
! Deletes the remainder of the line.
other Any other character entered replaces the original character.
Example:
/REDO
OLD: RECLAIM/DUMP,TN=MYVSN,PF=*/ALPHA,GAMMA=BETA
MOD: A,Z.# DF FILADT=MS,
NEW: RECLAIM,Z./DUMP,DF=MYFIL,DT=MS,PF=*/ALPHA,GAMMA=BETA
8-34 60459680 F
![](asset-135.png)
jl^N
RUN COMMAND
The RUN command compiles and/or initiates execution of a local file. The compiler used (if
any) depends on the current subsystem. This command is valid only in the BASIC, FORTRAN,
FTNTS, and execute subsystems.
Formats:
RUN
RUN,I=lfni
RUN,B=lfn2 or RUN,C=lfn2
RUN,I=lfnx ,B=lfn2 or RUN,1=1^ ,C=lfn2
RUN,T,q1,q2,...,qn
Parameter Description
lfnj Specifies the local file that contains the source program to be
compiled and executed.
lfn2 Specifies the compiler or assembler output file. File lfn2 can be
later executed in the execute subsystem by entering just RUN.
q i S p e c i fi e s l o c a l fi l e s t o r e p l a c e fi l e s s p e c i fi e d o n t h e P R O G R A M
statement in a FORTRAN 5 program.
The first format of the command compiles and initiates execution of the primary file.
The second format of the command compiles and initiates execution of the local file lfnj
if the subsystem and the source program are compatible.
The third format of the command compiles the primary file and generates a binary file,
lfn£, containing the resulting object code. The object code is not executed. File lfn£
can later be executed under the execute subsystem by entering the RUN command. The B and C
parameter names are interchangeable.
The fourth format compiles local file lfnj and generates a binary file, lfn2, containing
the resulting object code. The object code is not executed. File lfn2 can later be
executed under the execute subsystem by entering the RUN command. The B and C parameter
names are interchangeable.
The fifth format of the command applies only when running a previously compiled (object
code) FORTRAN program in the execute subsystem. It allows you to rename local files
specified in the PROGRAM statement without recompiling the program. Parameters qi through
qn specify new local file names to be used in place of those that currently exist in the
PROGRAM statement (the parameters are order-dependent and must correspond to those they
replace).
The following example illustrates the use of the RUN,T command. Assume a FORTRAN program
contains the following PROGRAM command.
PROGRAM TEST (INPUT,OUTPUT,AAA,BBB,TAPE1=AAA,TAPE2=SBB)
Normally, to execute a program containing this command, you must define local file AAA.
Local file BBB results from the execution of the program. However, you could change the
names of local files AAA and BBB without recompiling the program (if the object program
exists) by using the RUN,T command under the execute subsystem. For example:
RUN,T, INPUT,0UT PUT, CCC, DDD
60459680 E 8-35
![](asset-136.png)
I SECURE LOGIN COMMAND t
The secure login command ensures that your login information goes to the correct host
software. You can enter this command at any time you are connected to the network. If you
are already connected to a host when you enter this command, you will be unconditionally
disconnected and reconnected so that you can proceed with a secure login. This command does
not disconnect you from the network.
The secure login command includes a security character that is chosen by your site. The
procedure you use to enter this security character depends on your terminal type:
Terminal Type Secure Login Procedure
Asynchronous Press the BREAK key (or ATTN) and type the security character,
(except 2741s)
X.25 PSN terminal Press the BREAK key (or ATTN), type the security character, and
enter the message transmission signal.
Mode 4 Clear the screen, enter a carriage return, and clear the screen
again. Type the security character and press the end-of-block key.
HASP Type the security character and press the end-of-line key.
2780 or 3780 Enter /* and the security character from the console or a card
reader.
2 7 4 1 P r e s s t h e N L k e y t w i c e a n d t h e A T T N k e y o n c e . T y p e t h e s e c u r i t y
character and press the NL key again.
13270 Clear the screen and enter the program attention 1 key once. Type
the security character and press the ENTER key.
SHOW COMMAND
The SHOW command calls an interactive procedure to display a screen formatting panel. SHOW
is used for testing purposes. It allows you to display a panel without having to write a
program that calls the panel.
Format:
SHOW,I-panelname
Parameter Description
panelname Specifies the name of a compiled panel in user library PANELIB or in
a global library set.
Since the SHOW command is an interactive procedure, you can get help information for the
procedure by entering:
SHOW?
^SSv
■/*S%u
tlf your terminal is connected to a CDCNET network, refer to the CDCNET Terminal Interface f
Usage Manual.
8-36 60459680 G
![](asset-137.png)
TEXT COMMAND
The TEXT command selects text mode. Text mode allows direct entry of information (program
commands, data, or text) into the primary file without specifying line numbers. The system
interprets commands entered in text mode as text and does not process them directly.
Format:
TEXT
Unless changed during installation, the input line can consist of a maximum of 160
characters. The system appends data to the end of the file.
To terminate text mode, you should terminate the current input line with a carriage return,
then enter the interruption sequence or the termination sequence defined for the terminal in
use or the ETX character followed by a carriage return. (Interruption and termination in
sequences are discussed in section 16.)
The system automatically packs the text file to ensure that the data is in one logical
record.
NOTE
ytPN,
Do not enter a user break to terminate text
mode until you have received the ENTER TEXT
MODE message at your terminal. If entered
before this message, your user break clears
any unprocessed input, and no data goes into
the primary file.
WHATJSN COMMAND
The WHATJSN command returns the job sequence name (JSN) of the terminal you specify by a
user name. When several terminals are logged in under the specified user name, a list of
JSNs is returned. The WHATJSN command can be entered only from the access subsystem. It is
used in conjunction with the DIAL command to send a message to a user at an interactive
terminal.
Format:
WHATJSN,username
Parameter Description
username Specifies the user name of user whose JSN you seek.
60459680 D 8-37
![](asset-138.png)
X COMMAND
The X command forces the system to interpret a command as a batch command. The X command
does not explicitly change the current subsystem for your job, however.
Format:
X,ccc
Parameter Description
ccc Any valid batch command.
This command cannot exceed 80 characters. You must type the entire command but can omit the
terminator. However, you must enter a terminator after a command if you want to append a
comment to the command.
This command is used to enter a batch command that either is invalid in your current
subsystem or has a different function in that subsystem.
For example, the command
X,BASIC
calls the BASIC compiler instead of changing your subsystem to BASIC.
XMODEM COMMAND
The XMODEM command initiates the transfer of files between NOS and a microcomputer using the
Christensen protocol.
Format:
XMODEM,fn,td,ft,If,sp,ec,fm,cf.
XMODEM,FN=fn,TD=td,FT=ft,LF=lf,SP=sp,EC=ec,FM»fm,CF»cf.
Refer to appendix P for more information on the XMODEM command.
/ ^ | b L ,
8-38 60459680 G
![](asset-139.png)
0^*.
PRIMARY FILE EDITING COMMANDS
To allow ease of editing primary files, the system provides a line editing capability that
can be used under any subsystem. The line editing capability allows you to:
List lines
Correct lines
Delete lines
Insert lines
Copy lines
The following commands perform the previously indicated editing operations upon the primary
file:
Command
ALTER
DELETE
DUP
LIST
MOVE
READ
RESEQ
WRITE
WRITEN
Function
Changes character strings within lines of the primary file.
Deletes lines from the primary file.
Duplicates lines and moves the duplicates to a specific location in
the primary file.
Selectively lists lines of the primary file.
Moves lines from one location to another in the primary file.
Inserts another file at a specified location in the primary file.
Resequences or adds line numbers to the primary file.
Copies lines from the primary file to a specified sequenced file.
Copies lines from the primary file to an unsequenced file.
For other methods of file editing, refer to the EDIT, FSE, and XEDIT commands.
JfifiKRrfX^
i#^S
60459680 D 8 - 3 9 |
![](asset-13a.png)
yfiPsIX
PARAMETER FORMAT
The following subsections describe the specific format of each command. Each command uses
one or more of the following parameters:
Parameter
Name Format Function
Line number
Line range q..r
Lines :1 »c2»» • • >cn
Line number
increment
String /string/
Spe cifie s pri ma ry file lin e numbe r.
Specifies a set of sequential lines in the
primary file, q is the beginning line number of
the range, q may be specified by an asterisk to
signify that the line range starts at the
beginning of information (BOI). r represents
the ending line number of the range, r may be
specified by an asterisk to signify that the
line range ends at the end of information
(EOI). To specify a range from BOI to EOI you
may enter a single asterisk. When using line
numbers, q must be less than or equal to r.
Specifies a nonsequential set of lines and line
ranges separated by commas. Ci represents a
line or line range. For example,
60..90,120,10..40,350
is a valid entry. Regardless of the order the
lines or line ranges appear in the parameter,
the lines are processed in the order they appear
in the file.
Generates sequential line numbers
when inserting text into the file or when
resequencing is required due to overlapping line
numbers (refer to Line Number Overlap section),
z must be in the range of one to 4095 and, when
omitted, assumes a value of one.
Specifies a sequence of characters, including
spaces, delimited by a string delimiter. The
string delimiter may not consist of the
following:
digit
)
* : l e t t e r
@ space
The delimiter chosen may not appear in the
string. In this subsection, a slant (/) is used
as the string delimiter.
8-40 60459680 D
![](asset-13b.png)
09Hr\
Parameter
Name
String pair
Format
/stringl/string2/
File name filename
Function
Specifies two different character sequences
separated by a string delimiter. Stringl
represents a string as it appears in the file.
String2 represents how stringl will appear after
command processing. Stringl and string2 may be
null strings. A null string contains no
c ha r ac ter s. For exa mpl e, if str ing l w ere nul l,
the string pair would appear as //string2/ .
Refer to the string parameter description for
invalid string delimiters.
A file name consisting of 1 to 7 characters
where each character is a letter or digit.
SUPPRESSING EDITING RESPONSES
When changing lines within a file, the changed lines are displayed immediately after the
edit command has been processed. If you do not want the changed lines listed, enter:
BRIEF
This command will prevent the listing of changed lines. To resume listing changed lines,
enter:
NORMAL
The BRIEF and NORMAL commands are described earlier in this section.
LINE NUMBER OVERLAP
Some editing commands require the system to resequence lines of your file. New line numbers
may overlap existing line numbers. If this occurs, you are asked If the command should be
executed:
INSERTED LINES OVERLAP EXISTING LINES, AT 130.
ENTER Y TO CONTINUE OR N TO STOP
If your response is YES, the lines will be inserted and all lines that are overlapped will
have new line numbers generated in increments of the specified line number increment. If no
increment is specified, new line numbers are generated in increments of one from the last
inserted line. If your response is NO, the command is not executed.
If your primary file is a BASIC or FORTRAN program, select the corresponding subsystem
before editing. If you are not under the correct subsystem, the system may not make the
necessary changes when resequencing lines. Refer to the RESEQ command in section 9 for more
Information on how the system resequences FORTRAN and BASIC programs.
60459680 D 8-41
![](asset-13c.png)
INSERTING LINES
You can add a line to the primary file by prefacing it with a unique line number.
The following example demonstrates how to insert a single line into a sequenced file.
Example:
List
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00200 END
READY.
00115 Let c=30
List
00100 LET A=1
00110 LET B=10
00115 LET C=30
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00200 END
File is listed.
Line is entered inserting
line 115 between 110 and 120
File is listed to show
corrected version.
ALTER COMMAND
The ALTER command enables you to change character strings within specified lines in the
primary file.
Format:
ALTER,c1,c2,...,cn,/stringl/string2/
where the lines parameter is optional. If the lines parameter is omitted, the changes
specified by stringl and string2 apply to the entire file.
When you enter the lines and string pair, only the occurrences of stringl appearing in the
lines specified by the lines parameter are changed to string2.
When you enter the lines parameter, stringl, and a null string2 (/stringl//), all
occurrences of stringl appearing in the lines specified in the lines parameter are deleted,
When you enter the lines parameter, a null stringl, and string2 (//string2/), string2 is
appended to the lines specified in the lines parameter.
| 8 -4 2 60459680 D
![](asset-13d.png)
To correct a single line in error, you can simply respecify the line number and enter the
l i n e c o r r e c t l y.
The following example demonstrates how to change a line by entering the corrected version of
the line:
Example:
List
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
00200 END
READY.
00110 Let b=20
File is listed.
";I,"IS ";A
Line is entered changing
B's value from 10 to 20.
READY message is not
given after entry of line
List
00100 LET A=1
00110 LET B=20
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
0200 END
•;I,"IS ";A
File is listed to show
co rr ected ve rs io n.
When you enter the lines parameter, and stringl and string2 are null (///), the lines
specified in the lines parameter are listed.
Example:
List
00100 LET A=1
00110 LET B=20
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
00200 END
File is listed.
•;I,"IS ";A
READY.
aLter,100..130,/b/c/
00110 LET C=20
00120 FOR 1=1 to C
READY.
List
00100 LET A=1
00110 LET C=20
00120 FOR 1=1 TO C
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
00200 END
•;I,"IS ";A
ALTER command is entered, changing
B to C in lines 100 through 130.
Changed lines are displayed
automatically.
File is listed to show
co rr ected ve rs io n.
60459680 D 8-43
![](asset-13e.png)
DELETE COMMAND
You can delete specified lines from the primary file using the DELETE command.
Format:
DELETE,c1,C2,...,cn,/string/
where either the lines parameter or string parameter must be specified.
When you enter the lines parameter and do not enter the string parameter, all lines
specified by the lines parameter are deleted.
When you enter the string parameter and do not enter the lines parameter, all lines in the
file containing the specified string are deleted.
When you enter both the lines parameter and the string parameter, only those lines specified
by the lines parameter containing the string specified in the string parameter are deleted.
•"-%^V
Example:
List
00100 LET A=1
00105 LET B=10
00110 LET C=20
00120 FOR 1=1 TO C
00130 A=A*I
00140 PRINT "FACTORIAL I;I,"IS ";A
00150 NEXT I
00200 END
File is listed.
READY.
deLete,100..130,/b=10/
00105 LET B=10
READY.
List
00100 LET A=1
00110 LET C=20
00120 FOR 1=1 TO C
00130 A=A*I
00140 PRINT "FACTORIAL I;I,"IS ";A
00150 NEXT I
00200 END
DELETE command is entered,
deleting all lines from 100
through 130 which contain
the string B=10. The deleted
line is automatically listed.
File is listed to show
corrected version.
| 8 - 4 4 60459680 D
![](asset-13f.png)
You can also delete a line by specifying its line number and entering an empty line for it,
The following example demonstrates how to delete a single line from a sequenced file by
entering the number of the line to be deleted.
Example:
List
00100 LET A=1
00105 LET B*10
00110 LET C=20
00120 FOR 1=1 to C .
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00200 END
File is listed.
READY.
00105 00105 followed by carriage
return is entered, deleting
line 00105. The READY message
is not given after entry
of line.
PList
00100 LET A=1
00110 LET C=20
00120 FOR 1=1 TO C
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
00200 END
";I,"IS ";A
Fi le is li st ed t o sh ow
co rr ected ve rs io n.
/sP^\
DUP COMMAND
You can duplicate lines and insert them in a specified location in the primary file using
the DUP command.
Format:
DUP,q..r,n,z
where q..r is a line range and may be specified as a single line number.
n specifies the line number after which the duplicated the lines are to be inserted. If n
is not specified, the duplicated lines are inserted at the end of the file. If n is less
than the first line number in the file, the duplicated lines are inserted at the beginning
of the file. If n is between two existing line numbers, the duplicated lines are inserted
between the adjacent lines and incremented by z. If the new line numbers overlap existing
edit file line numbers, line resequencing occurs as described under Line Number Overlap.
60459680 D 8-45
![](asset-140.png)
When BASIC statements containing line numbers and their referenced lines are duplicated, the
lines and their duplicates are kept separate. The duplicate statements containing line
references reference duplicate lines. Duplicate statements do not reference original
statements.
Example:
List
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00200 END
READY.
dup,130..150,150,10
00160 A=A*I
00170 PRINT "FACTORIAL
00180 NEXT I
File is listed.
";I,"IS ";A
DUP command is entered,
duplicating lines 130 through
150, and inserting the
duplicates after line 150,
incrementing subsequent lines
by 10. Affected lines are
automatically listed.
File is listed to show
corrected version.
READY.
List
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00160 A=A*I
00170 PRINT "FACTORIAL ";I,"IS ";A
00180 NEXT I
0200 END
UST COMMAND
You can selectively list the lines of the primary file using the LIST command.
Format:
LIST,C!,C2,...,cn,/string/
If you s pe ci fy no pa ra me te rs, t he sy st em lis ts a ll lines i n t he fi le . To l is t a ll o f t he
lines in a local file other than the primary file, you can use the alternate format of the
LIST command, described earlier in this section under Job Processing Commands.
/*5tfB£|\
/**^\
8-46 60459680 D
![](asset-141.png)
The following example illustrates how to use the command.
Example:
yjffftx
READY.
List
00100 LET A=1
00105 LET B=10
00110 LET C=20
00120 FOR 1=1 TO C
00130 A=A+1
00140 PRINT "FACTORIAL ";I, "IS ";A
00150 NEXT I
00200 END
READY.
List,100..130
00100 LET A=1
00105 LET B=10
00110 LET C=20
00120 FOR 1=1 TO C
00130 A=A+1
READY.
List,120,100,140..200
00100 LET A=1
00120 FOR 1=1 TO C
00140 PRINT "FACTORIAL ";I, "IS ";A
00150 NEXT I
00200 END
READY.
List,/ a/
00100 LET A=1
00130 A=A+1
00140 PRINT "FACTORIAL ";I, "IS ";A
READY.
List,130..200,/a/
00130 A=A+1
00140 PRINT "FACTORIAL ";I, "IS ";A
READY.
List the entire file.
List a range of lines.
List a nonsequential set of lines.
List all lines that contain the
character A.
Li st only th os e lines i n a s pe ci fie d
range that contain the character A.
60459680 D 8-47
![](asset-142.png)
MOVE COMMAND
You may also manipulate lines of the primary file with the use of the MOVE command.
MOVE command moves lines from one location in the primary file to another location.
The
Format:
MOVE,q..r,n,z
where q..r is the line range parameter and may be specified by a single line number. The
line number (n) and line number increment (z) parameters are optional.
The line range parameter specifies the lines to be moved.
If the n parameter is omitted, the lines are moved to the end of the file and successive
line numbers are generated in increments of z, if specified, from the last line of the
primary file.
If the new line numbers overlap existing line numbers in the primary file, line resequencing
occurs as described in the Line Number Overlap subsection.
Example:
List
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00200 END
File is listed.
READY.
move,100,110,10
INSERT LINES OVERLAP EXISTING LINES, AT 120.
ENTER Y TO CONTINUE OR N TO STOP
? y
00120 LET A=1
00130 FOR 1=1 TO B
00140 A=A*I
00150 PRINT "FACTORIAL ";I,"IS ";A
00160 NEXT I
MOVE command is entered,
moving line 100 and
inserting it immediately
following line 110,
incrementing subsequent lines
by 10. Affected lines are
automatically listed.
READY.
List
00110 LET B=10
00120 LET A=1
00130 FOR 1=1 TO B
00140 A=A*I
00150 PRINT "FACTORIAL
00160 NEXT I
00200 END
•;I,"IS ";A
File is listed to show
corrected version.
8-48 60459680 D
![](asset-143.png)
READ COMMAND
The READ command inserts the lines of a file (read file) at a specific location in the
primary file.
Format:
READ,filename,n,z
where the line number (n) and line number increment (z) parameters are optional. The
parameter filename is the name of the file to be inserted.
When the line number parameter is entered, the contents of the file to be inserted are
inserted immediately following line n. If the parameter n is a line number that is not in
the primary file, the read file is inserted after the largest line number that is less than
n. The line numbers of read files are incremented by 1, unless an increment is specified by
the z parameter.
If the line number parameter is not entered, the contents of the read file are added to the
end of the primary file and incremented by z from the last line number of the primary file.
For sequenced read files, line numbers are added in increments of one, unless otherwise
specified by the z parameter. A sequenced read file will be resequenced in increments of z
from the last line number in the primary file.
Unsequenced read files will have a five-digit line number added and followed by a blank (in
the FORTRAN and FTNTS subsystems, the line number is added but not the blank). If a line
consists of only a line number or a line number followed by zero or one blank, the line will
not be inserted into the primary file.
If the new line numbers overlap existing lines in the primary file, line resequencing occurs
as described in the Line Number Overlap subsection.
60459680 D 8-49
![](asset-144.png)
In the BASIC subsystem, when inserting a sequenced read file where no overlapping of line
numbers occurs, the system handles line references within the read file in the following
manner. The system automatically updates line references within statements if the referenced
lines are within the read file. It does not alter line references within statements if the
lines referenced lie outside of the read file.
Example:
•;I,"IS ";A
List
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
00200 END
READY,
get,skid
READY.
read,skid,150,10
INSERT LINES OVERLAP EXISTING LINES,
AT 200.
ENTER Y TO CONTINUE OR N TO STOP
? y
00160 LET A=1
00170 LET B=50
00180 FOR 1=1 TO B
00190 A=A*I
00200 PRINT "FACTORIAL";I,A
00210 NEXT I
00220 END
READY.
List
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00160 LET A=1
00170 LET B=50
00180 FOR 1=1 TO B
00190 A=A*I
00200 PRINT "FACTORIAL";I,A
00210 NEXT I
00220 END
Primary file is listed,
Read file is made local.
READ command is entered. With line
increments of 10, the read file is
inserted after line 150.
Y is entered to continue
command processing.
Inserted lines are
automatically listed.
Primary file is listed to
show corrected version.
*nS™£v
8-50 60459680 D
![](asset-145.png)
RESEQ COMMAND
Refer to the RESEQ command in section 9.
WRITE COMMAND
You can also append lines and line numbers of the primary file to another specified file
(destination file) by using the WRITE command.
Format:
WRITE,filename,c1,c2,...,cn,/string/
where the required parameter filename is the name of a local file. The lines and string
parameters are optional.
If the lines parameter is entered and the string parameter is omitted, all lines specified
by the lines parameter are copied to the destination file. If both the lines parameter and
string parameter are entered, the lines specified by the lines parameter which contain the
string specified by the string parameter are copied to the destination file.
If the string parameter is entered and the lines parameter is omitted, all lines in the
primary file containing the specified string are copied to the destination file. If both
the lines and string parameters are omitted, all lines of the primary file are copied to the
destination file.
Example:
List
00100 LET A=1
00110 LET B=10
00115 LET C=20
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
00200 END
Primary file is listed.
•;I,"IS ";A
READY,
write ,fiLe2,100.. 110,120..*
READY.
List,f=fiLe2
00100 LET A=1
00110 LET B=10
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL
00150 NEXT I
00200 END
WRITE command is entered,
writing lines 100 through
110 and lines 120 through
200 to destination file
FILE2.
FILE2 is listed.
•;I,"IS ";A
60459680 D 8-51
![](asset-146.png)
WRITEN COMMAND
To copy lines from a sequenced primary file to an unsequenced destination file, enter the
WRITEN command. The WRITEN command copies specified lines of the primary file to the
destination file while removing the line numbers; resulting in an unsequenced destination
file.
Format:
WRITEN,filename,c ±,C2,•••»cn,/string/
Example:
list
00100 LET A=1
00110 LET B=10
00115 LET C=20
00120 FOR 1=1 TO B
00130 A=A*I
00140 PRINT "FACTORIAL ";I,"IS ";A
00150 NEXT I
00200 END
Primary file is listed.
READY.
writen,fi Le3,100..110,120..*
READY.
List,f=fiLe3
LET A=1
LET B=10
FOR 1=1 TO B
A=A*I
PRINT "FACTORIAL ";I,"IS ";A
NEXT I
END
WRITEN command is entered,
writing lines 100 through
110 and lines 120 through
200 to destination file
FILE3.
FILE3 is listed.
Parameter combinations and functions are the same for the WRITEN and WRITE commands.
8-52 60459680 D
![](asset-147.png)
FILE MANAGEMENT COMMANDS
The file management commands manipulate files assigned to your job. The commands included
in this category are:
ASSIGN
BKSP
CLEAR
COPY
COPYBF
COPYBR
COPYCF
COPYCR
COPYEI
COPYSBF
COPYX
DOCMENT
EVICT
FCOPY
LIST80
LOCK
L072
MFQUEUE
NEW
OUT
OVWRITE
PACK
PRIMARY
RENAME
REQUEST
RESEQ
RETURN
REWIND
ROUTE
SCOPY
SECHDR
SETFAL
SETFS
SKIPEI
SKIPF
SKIPFB
SKIPR
SORT
TCOPY
TDUMP
UNLOAD
UNLOCK
VERIFY
WRITEF
WRITER
0®*\
The commands in this section position files, copy data from one file to another, specify the
method and format of input or output, sort files, and add corrections. You can assign your
files to a specific device type; change the file type, identification code, and write
interlock status; and release them from your job. You can also receive information about
records in a file or documentation in a file.
If you use these commands on files structured by CYBER Record Manager (CRM), the output may
not reflect the CRM logical file structure. The only commands recommended for copying CRM
files are COPY and COPYEI.
If a file is not specifically assigned through the use of an ASSIGN, LABEL, or REQUEST
command, the system assigns the file to available mass storage.
60459680 E 9-1
![](asset-148.png)
ASSIGN COMMAND
The ASSIGN command directs the system to assign a file to the specified device or device
type. The following descriptions refer to devices other than magnetic tape. For use of the
ASSIGN command with magnetic tape, refer to section 12.
Format:
ASSIGN,nn,Ifn,checkpoint,AL=level.
Parameter Description
nn Specifies the device or device type to which the specified file is to
be assigned; nn may be either the EST ordinal of a peripheral device
or the device type as defined as follows:
Type Equipment
DB 885-42 Disk Storage Subsystem (full-track).
DC 895-1/2 Disk Storage Subsystem (full-track).
DD 834 Disk Storage Subsystem (full-track).
DE Extended memory.
■ DF 887 Disk Storage Subsystem (4K sector; full-track).
DG 836 Disk Storage Subsystem (full-track).
| DH 887 Disk Storage Subsystem (16K sector; full-track).
DI 844-21 Disk Storage Subsystem (half-track).
DJ 844-41/44 Disk Storage Subsystem (half-track).
DK 844-21 Disk Storage Subsystem (full-track).
DL 844-41/44 Disk Storage Subsystem (full-track).
D M 8 85 - 11 /1 2 D i sk S to r ag e S u bs y st e m ( ha l f- tra ck) .
DP Distributive data path to extended memory.
DQ 885-11/12 Disk Storage Subsystem (full-track).
DV 819 Disk Storage Subsystem (single-density).
DW 819 Disk Storage Subsystem (double-density).
MS Mass storage device.
NE Null equipment.
TTt Interactive terminals.
tTh is dev ic e ty pe app li es onl y to in te ractive or ig in job s.
9-2 60459680 H
![](asset-149.png)
Parameter Description
lfn Specifies the name of the file to be assigned to the specified
equipment.
checkpoint Specifies that lfn is to be used as a checkpoint file (refer to
section 13).
checkpoint Meaning
J p V
0^\
CK Each dump is written at the previous EOI of lfn.
C B E a c h d u m p i s w r i t t e n a t t h e B O I o f l f n .
AL=level Specifies the security access level to assign to the file. Unless
changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default is the current access level of the job.
On a secured system, the access level you specify must be valid for
the job (ENQUIRE,B returns this information) and for the device to
which you are assigning the file.
On an unsecured system, the parameter has no effect. The system does,
however, check for valid parameter specifications.
When using this command to assign a file for checkpoint dumps on a
secured system, use the AL=level parameter to assign the file at the
highest access level valid for the job (ENQUIRE,B returns this
information). The CKP command aborts the job if the checkpoint file
is not at this access level.
Example 1:
ASSIGN,MS,0UT PUT.
This command assigns file OUTPUT to mass storage. With this assignment in an interactive
job, you can cause output normally printed at your terminal to be written on a mass storage
file instead. Here, output means information generated by a program during execution.
Dayfile messages are still printed at the terminal. Once this assignment is made, output is
written on the mass storage file OUTPUT until the file is returned or reassigned.
Example 2:
ASSIGN,TT,XYZ.
This command assigns file XYZ to your interactive terminal. The assignment means that input
that the system would have read from file XYZ is instead solicited by a prompt at the
terminal and that output that the system would have written on file XYZ is instead displayed
at the terminal.
If you have multiple files assigned to your terminal, you may get some unpredictable results.
60459680 C 9-3
![](asset-14a.png)
Example 3:
ASSIGN, DI, ABC.
This command assigns file ABC to an 844-21 disk drive, if one is available.
The ASSIGN command can also be used to create or access existing seven- or nine-track
unlabeled tapes. For a description of the command as it applies to magnetic tape
assignment, refer to section 12, Tape Management.
BKSP COMMAND
The BKSP command directs the system to bypass a specified number of logical records in the
reverse direction.
Format:
BKSP,lfn,n,m.
Parameter Description
lfn Specifies the name of the file to be backspaced.
n Specifies the number of logical records (decimal) to backspace; if
this parameter is omitted, the system assumes n=l. The maximum for n
is 262143.
m Specifies the file mode: C for coded, B for binary. If m is omitted,
the system assumes the file is in binary mode.
The BKSP request can be issued at any point in a logical record. If, for example, FILE1
were positioned within the third record, a
BKSP.FILEl.
request would reposition F1LE1 to the beginning of the third record. The system does not /^^.
backspace past the beginning-of-information (BOI). However, EOF indicators are considered )
separate records and are included in the record count.
The BKSP command has no effect on a primary file since that file is rewound before every
operation.
s*^\
^
9-4 60459680 C
![](asset-14b.png)
^hitfi^!%k
CLEAR COMMAND
The CLEAR command releases all files currently assigned to the job. You can also specify
files that are not to be released.
Format:
CLEAR.
or
CLEAR,*,lf^ ,lfn2 lfnn.
The first format releases all files. The second format releases all files except those
named. If no files are named, all files assigned to the job are released.
There are several exceptions. The CLEAR command does not release any files that have
checkpoint or no-auto-drop status. Certain system scratch files (for example, ZZZZZCO,
ZZZZZC1, ZZZZZC2, and ZZZZZLD) have no-auto-drop status. You can give any local file this
status by using the SETFS command.
Refer to RETURN command in this section for the operations performed on each file type.
COPY COMMAND
The COPY command copies data from one file to another if the files are within the range of
permissible formats listed in table 9-1.
NOTE
When you copy a file with no EOR or EOF file
marks, the resulting file may have a differ
ent logical file structure. In particular,
when copying such a file to tape, the system
adds an EOR mark to the end of the file.
Such changes do not affect file content but
may cause verification errors.
00^\
\ 60459680 C 9-5
![](asset-14c.png)
Table 9-1. Range of Permissible Formats for the COPY Command
Input
Ol fn x)
Output (0=lfn2)
Mass
Storage
or
Terminal
Tape Formats
ISI
Mass Storage
or Terminal Yes Yes Yes Yes Yes If
Tape
Formats
Yes Yes Yes Yes Yes /////Yy
SI Yes Yes Yes Yes Yes W6/sss/A
S Yes Yes Yes Yes Yes Ii
L Yes Yes Yes mi Yes
F Yes Yes Yes m®m Yes
9-6 60459680 C
![](asset-14d.png)
/fi^V
Order-dependent format:
C0PY,lfni,lfn2,x,c,tc,copycnt,bsize,charcnt,erlimit,pip2...pn,lfn3,ns
Order-independent format:
COPY,I=lfn1>o=lfn2,V=x,M=c,TC=tc,N=copycnt,BS=bsize,CC=charcnt,EL=erlimit,
PO=Plp2...pn,L=lfn3,NS=ns.
The parameters can appear in order-dependent format, order-independent format, or a
combination of both. If order-dependent and order-independent parameters are mixed in one
COPY command, the order-dependent parameters must appear in their proper position. All
parameters are optional. However, the specification of certain parameters precludes the
application of others. A nonapplicable parameter may be ignored or it may be invalid. This
is stated in the individual descriptions of the parameters.
Parameter Description Default
I = l f n i S p e c i fi e s t h e n a m e o f t h e fi l e t o b e c o p i e d . I N P U T
0=lfn2 Specifies the name of the file receiving the copy. OUTPUT
V=x If the x parameter (1 to 7 alphanumeric No verify
characters) is present, both files are rewound,
copied, rewound, verified, and rewound. The x
parameter must not be zero.
M=c Specifies whether the input and output files are
coded files.
c Description
Cl Coded mode is set on input only.
C2 Coded mode is set on output only.
x Coded mode is set on both input
and output. The value x is any alpha
numeric, 1- to 7-character string.
Binary
TC=tc
This parameter applies only to S and L format
tapes. If coded mode is set on an SI tape,
the system aborts the job. For other formats,
the system ignores the mode setting.
Specifies the termination condition for copy
ing used in conjunction with N=copycnt. The
termination condition can be specified as
follows:
Copy to double
EOF (TC=D or
TC=EOD)
tc Description
F or The N keyword specifies the number
E O F o f fi l e s t o c o p y .
I or Copy to the end of information. The
EOI N keyword is ignored.
60459680 D 9-7
![](asset-14e.png)
J^^^\
Parameter Description Default
tc Description
D or The N keyword is the number of double
EOD EOF s to co py to . If N > 1 is speci
fied together with this TC value, and
verify is also selected, the files are
verified only to the first empty file
(COPY calls VERIFY with N=0 parameter).
N=copycnt Specifies the copy count used with the copy termi- 1
nation condition specified by the parameter TC=tc.
BS=bsize Specifies the maximum block size (in central
memory words) which specifies S or L tape PRU size,
This applies only when copying to or from S and
L tapes. It cannot be specified with the
CC=charcnt parameter.
CC=charcnt Specifies the maximum number of characters in
an S or L tape block. This parameter can be
specified only when copying to or from S and L
tapes. The PRU size and unused bit count are
calculated from the character count. However,
the unused bit count is used only when writing a
full block to an S or L output tape during a copy
from mass storage, I, or SI format tape. The
charcnt value should be a multiple of 10. If it
is not, the characters that exceed the charcnt
value in the last word of the record are discarded
when writing an S or L format tape. This parameter
cannot be specified with the BS=bsize parameter.
EL=erlimit Specifies the number of nonfatal errors allowed 0 (zero)
before abort. This includes both parity errors
and block-too large errors which are returned by
the tape subsystem after completing recovery
procedures. If EL=U is specified, unlimited error
processing is allowed. Error recovery is supported
on mass storage and on all tape formats but is not
supported on a terminal or on unit record equipment.
In the latter cases, any error aborts the job.
If CC=charcnt
is not specified,
1000g for S tape
copy and 2000g
for L tape copy.
No t used (the
PRU size is
s pe c i fie d b y
the BS=bsize
parameter)
■-^\
,-**®?v
9-8 60459680 C
![](asset-14f.png)
j^$^*\
Parameter Description
P0=p^p2...p One or more of the following processing options:
E Input blocks with parity errors or
block-too-large errors are processed
(copied).
D Any noise blocks generated by a copy
from mass storage, I format tape, or
SI format tape to an S or L format
tape are deleted. This parameter can
not be specified on any other type of
copy.
R Allows record splitting during a copy
from mass storage, I format, or SI
format to S or L format tape. This
parameter cannot be specified on any
other type of copy.
M Copy files according to the copy
termination condition specified by
the keyword TC, eliminating each
EOF on output. This option is
primarily for use with labeled S
and L output tapes since it
eliminates the conflict of the
double meaning of a tape mark on
these formats (the tape mark on
these formats serves as both an EOF
and label group delimiter).
L=lfn3 Specifies the name of an alternate file to
receive parity error messages when extended
error processing Is in effect (nonzero EL
specified), in which case, file name lfn3
must not be the same as lfn^ or lfn2«
NS=ns Noise size. Any input block containing
fewer than ns characters is considered to
be noise and is discarded. This parameter
Is valid for Input tapes in S, L, or F
format. The maximum value that can be
spe ci fie d fo r ns is 41. I f NS=0 is speci
fied, the default value of 18 is used.
Example:
The following COPY command combines order-dependent and order-independent parameters.
C0PY,FILE1,FILE2,VERIFY,C0DED,E0F,6,L=MY0UT,P0=E,EL=10.
FILE1 is the input file, and FILE2 the output file. Six coded files are copied and
verified. Up to 10 nonfatal errors are allowed, and the bad data is copied with informative
error messages written to the file MYOUT.
Default
Error blocks
are skipped.
For S or L bi
nary tapes,
noise blocks
are padded to
noise size with
binary zeros;
for coded mode,
they are padded
with blanks.
Record splitting
is not allowed.
Copy files
according to
s p e c i fi c a t i o n
of the copy
termination (TC),
writing an EOF
after each flLe
on output.
OUTPUT
60459680 D 9-9
![](asset-150.png)
The COPY command begins a copying operation at the current position of both files unless the
verify option is specified. If verification is specified, both files are rewound before the
copying begins and rewound, verified, and rewound again after the copying is completed.
This verification may not be meaningful if the logical structure of the two files is
incompatible.
COPY TERMINATION
Copying continues until the termination condition for copying is met or EOI is encountered.
The termination condition can be a file count, a double EOF count, or EOI. If the copying
is terminated by a double EOF (for TC=EOD), the second EOF is detected on lfnx, but is not
transferred to lfn2. If lfn^lf^ the named file Is read until the termination condi
tion Is satisfied or EOI is encountered.
If the copying command specifies a file count, TC=EOF, and EOI is encountered on the input
file before the file count is satisfied, an additional EOF is written on the output file
only if data or records have been transferred since the previous EOF was written (or since
the beginning of the copying if no EOFs have been encountered).
BLOCK SIZES
Both L and F tapes may require additional field length to accommodate their maximum block
size. The maximum block size for an L tape copy is specified either by the BS=bsize
parameter (or its default), or it is calculated from the CC=charcnt. The maximum block size
for an F tape is determined by the maximum frame or character count specified when the file
was assigned. The more accurate the selection of these values which determine block size,
the less are the requirements for field length, CPU time, and I/O time.
PROCESSING OPTIONS
The PO=D option specifies noise block processing, and the PO=R option specifies record
splitting for copies from mass storage, I format, or SI format to S or L format tapes. Due
to the incompatibilities between the logical structure of the input and output files,
records may be encountered on the input file that are too small or too large to be copied
directly to the S or L output tape. If the output file block size is less than noise block
size, it is deleted if PO=D is specified. If PO=D is not specified, the block size is
rounded to the word multiple of noise size with binary zero fill for a binary S or L tape or
with blank fill for a coded S or L tape. Empty records on the input file are skipped since
they cannot exist on an S or L tape. If PO=R is specified and an input file record length
exceeds the S or L tape maximum block size (the PRU size as specified by BS=bsize or its
default, or by CC=charcnt), it Is split into multiple blocks.
The PO=M option makes it possible to copy a multifile file to a labeled S or L format tape
without writing the EOF tape marks. This avoids the conflict of a tape mark serving the
double purpose of defining an EOF and delimiting a label group on S and L format tapes.
This is In keeping with the tendency In the computer industry to define a tape mark only as
a label delimiter.
The EL=erlimlt and PO=E parameters provide extended error processing.
9_10 60459680 D 1
![](asset-151.png)
jp^?$&ff*=S
COPYBF COMMAND
The COPYBF command copies a specified number of files from one multifile file to another.
NOTE
The COPYBF command is not recommended for
use with S, L, or F format tapes because it
does not have the data specification
parameters needed to accommodate the
variety of data formats possible with those
tape formats. For S, L, or F format tape
copying operations, issue a COPY command
with the appropriate parameter
specifications.
When you copy a file with no EOR or EOF file marks, the resulting file may have a different
logical file structure. In particular, when copying such a file to tape, the system adds an
EOR mark to the end of the file. Such changes do not affect file content but may cause
verification errors.
Format:
COPYBF,Ifn!,lfn2,n,c.
Parameter Description
lfnl Specifies the name of the file to copy. If this parameter is omitted,
file INPUT is assumed.
Ifn2 Specifies the name of the file to receive the copy. If this parameter
is omitted, file OUTPUT is assumed.
n Specifies number of files (decimal) on lfn^ to copy. If this
parameter is omitted, 1 is assumed.
c I n d i c a t e s t h a t t h e c o p y i n g t o o r f r o m a n S o r L f o r m a t t a p e s h o u l d b e
performed in coded rather than binary mode. C is a one- to seven-
character string. If coded mode Is set on an SI tape, the system
aborts the job. The system ignores this parameter for mass storage
files and I and F format tape files.
The cop yi n g b eg ins a t t h e cur re n t p os iti on o f l fn x. if l fn i =l fn2 , t he fi le is rea d
until the file count is satisfied or EOI is encountered.
If EOI is encountered on lfnj before the file count is satisfied, an additional EOF is
generated on lfn2 only if data or records have been transferred since the previous EOF was
written (or since the beginning of copy if no EOFs have been encountered).
60459680 C 9_u
![](asset-152.png)
COPYBR COMMAND
The COPYBR command copies a specified number of records from one file to another.
NOTE
The COPYBR command is not recommended for
use with S, L, or F format tapes because it
does not have the data specification
parameters needed to accommodate the
variety of data formats possible with those
tape formats. For an S, L, or F format
tape copying operation, issue a COPY
command with the appropriate parameter
specifications.
When you copy a file with no EOR or EOF file marks, the resulting file may have a different
logical file structure. In particular, when copying such a file to tape, the system adds an
EOR mark to the end of the file. Such changes do not affect file content but may cause
verification errors.
Format:
COPYBR,Ifnj,Ifn2,n,c.
Parameter Description
l f n j S p e c i fi e s t h e n a m e o f t h e fi l e t o c o p y . I f t h i s p a r a m e t e r i s o m i t t e d ,
file INPUT is assumed.
I f n 2 S p e c i fi e s t h e n a m e o f t h e fi l e t o r e c e i v e t h e c o p y. I f t h i s p a r a m e t e r
is omitted, file OUTPUT is assumed.
n Specifies the number of records (decimal) to copy; if this parameter "^
is omitted, 1 is assumed.
c Indicates that the copying to or from an S or L format tape should be
performed in coded rather than binary mode. The value C is an alpha
numeric one- to seven-character string. If coded mode is set on an SI
tape, the system aborts the job. The system ignores the mode setting
for other formats.
The copying begins at the current position of lfnj. EOF indicators are considered
separate records and are inclu ded in the re cord count. If lfn^=lfn2, the file is read
until the record count is satisfied or EOI is encountered.
If EOI is encountered on lfnj before the record count is satisfied, an additional EOR is
written on lfn2 only if data has been transferred since the previous EOR or EOF was
written (or since the beginning of the copy if no EORs or EOFs have been encountered).
9-12 60459680 C
![](asset-153.png)
/j$P*S
COPYCF COMMAND
The COPYCF command copies a specified number of coded files from one file to another. A
coded file is defined as a file containing lines of 500 characters or less, each terminated
by a zero byte (12 zero bits in the lowest byte of a word).
NOTE
/(IfPN,
The COPYCF command is not recommended for
use with S, L, or F format tapes because it
does not have the data specification
parameters needed to accommodate the
variety of data formats possible with those
tape formats. For an S, L, or F format
tape copying operation, issue a COPY
command with the appropriate parameter
specifications.
The COPYCF command cannot copy SI format
tapes. If coded mode is set for an SI
tape, the system terminates the job. The
TCOPY command converts SI coded tape files.
When you copy a file with no EOR or EOF file marks, the resulting file may have a different
logical file structure. In particular, when copying such a file to tape, the system adds an
EOR mark to the end of the file. Such changes do not affect file content buy may cause
v e r i fi c a t i o n e r r o r s .
Format:
COPYCF,Ifni,Ifn2,n,fchar,lchar,na.
Parameter Description
lfni Specifies the name of the file to copy. If this parameter is omitted,
file INPUT is assumed.
lfn2 Specifies the name of the file to receive the copy. If this parameter
is omitted, file OUTPUT is assumed.
n S p e c i fi e s t h e n u m b e r o f fi l e s ( d e c i m a l ) t o c o p y . I f t h i s p a r a m e t e r i s
omitted, 1 is assumed.
f c h a r t S p e c i fi e s t h e fi r s t c h a r a c t e r p o s i t i o n o f e a c h l i n e t o c o p y f o r 6 - b i t
characters. If this parameter is omitted, the copying begins at
character position 1.
lchart Specifies the last character position of each line to copy for 6-bit
characters, lchar must be greater than or equal to fchar. If this
parameter is omitted, the copying ends at character position 136.
na Specifies that the job step should not abort when a line terminator
does not appear before an EOR. na can be any alphanumeric, one- to
seven-character string.
y$^*\ +Since many characters in 6/12-bit display code require 12 bits rather than 6, this param
eter may produce unforeseen results when copying a file containing 6/12-bit display code
data. Refer to appendix A for a description of character set codes.
60459680 F 9-13
![](asset-154.png)
The copying begins at the current position of lfnj. If lfni=lfn2» the file is read
until the file count is satisfied or EOI is encountered. If EOI is encountered before the
file count is satisfied, an EOF is written on lfn2> and the operation terminates. If a
line is encountered that has more than lchar characters, the excess characters are truncated.
The COPYCF command writes lines with an even number of characters. If an input line has an
odd character count and the last character is a blank not immediately preceded by a colon,
the last character is removed. If an input line has an odd character count and the last
character is not a blank or is a blank immediately preceded by a colon, an additional
trailing blank is appended.
If the COPYCF command attempts to copy a line longer than 500 6-bit characters, the line is
truncated, and an informative message is issued to the dayfile after the copying completes.
If the last line of a record does not have an end-of-line terminator, the system issues a
dayfile message. If the na parameter is not specified, the job step then aborts.
9-14 60459680 F
![](asset-155.png)
COPYCR COMMAND
The COPYCR command copies a specified number of coded records from one file to another. A
coded record contains lines of 500 characters or less, each terminated by a zero byte (12
zero bits in the lowest byte of a word).
NOTE
r
The COPYCR command is not recommended for
use with S, L, or F format tapes because it
does not have the data specification
parameters needed to accommodate the
variety of data formats possible with those
tape formats. For an S, L, or F format
tape copying operation, issue a COPY
command with the appropriate parameter
specifications.
The COPYCR command cannot copy SI format
tapes. If coded mode is set for an SI
tape, the system terminates the job. The
TCOPY command converts SI coded tape files.
When you copy a file with no EOR or EOF file marks, the resulting file may have a different
logical file structure. In particular, when copying such a file to tape, the system adds an
EOR mark to the end of the file. Such changes do not affect file content but may cause
v e r i fi c a t i o n e r r o r s .
Format:
COPYCR,Ifnx,Ifn2,n,fchar,lchar.na.
Parameter
>^S?Sy l f n i
l f n -
fchart
1chart
Description
Specifies the name of the file to copy. If this parameter is omitted,
file INPUT is assumed.
Specifies the name of the file to receive the copy. If this parameter
is omitted, file OUTPUT is assumed.
Specifies the number of records (decimal) to copy. If this parameter
is omitted, 1 is assumed.
Specifies the first character position of each line to copy for 6-bit
characters. If this parameter is omitted, the copying begins at
character position 1.
Last character position of each line to copy for 6-bit characters,
lchar must be greater than or equal to fchar. If this parameter is
omitted, the copying ends at character position 136.
Specifies that the job step should not abort if a line terminator does
not appear before an EOR. The parameter na can be any alphanumeric,
one- to seven-character string.
+Since many characters in the 6/12-bit display code require 12 bits rather than 6, this
parameter may produce unforeseen results when copying a file containing 6/12-bit display
code data. Refer to appendix A for a description of character set codes.
60459680 F 9-15
![](asset-156.png)
The copying begins at the current position of lfnj. If lfni=lfn2, the file is read
until the record count is satisfied or EOI is encountered. EOF indicators are considered
separate records and are included in the record count. If the EOI is encountered before the
record count is satisfied, an EOR is written on lfn2, and the operation terminates. The
COPYCR command is processed in exactly the same manner as the COPYCF command except that n
specifies the number of records rather than the number of files.
I If the COPYCR command attempts to copy a line longer than 500 6-bit characters, the line is
truncated, and an informative message is issued to the dayfile after the copying completes.
If the last line of a record does not have an end-of-line terminator, the system issues a
dayfile message. If the na parameter is not specified, the job step then aborts.
COPYEI COMMAND
The COPYEI command copies one file to another. The copying begins at the current position %
of the file and continues until the EOI is encountered. The EOI is not defined for certain
tape formats (refer to table 2-1).
NOTE
The COPYEI command is not recommended for use
with S, L, or F format tapes because it does not
have the data specification parameters needed to
accommodate the variety of data formats possible
with those tape formats. For an S, L, or F for
mat tape copying operation, issue a COPY command
with the appropriate parameter specifications.
When you copy a file with no EOR or EOF file
marks, the resulting file may have a different
logical file structure. In particular, when
copying such a file to tape, the system adds an
EOR mark to the end of the file. Such changes
do not affect file content but may cause
verification errors.
Format:
COPYEI, If nlf If n2,x,c.
Parameter Description
lfni Specifies the name of the file to copy. If this parameter is omitted,
file INPUT is assumed.
Ifn2 Specifies the name of the file to receive the copy. If this parameter
is omitted, file OUTPUT is assumed.
x Specifies that both files are rewound before the copying, and rewound,
verified, and rewound again after the copying is complete, x can be
any alphanumeric, one- to seven-character string.
c Indicates that the copying to or from an S or L format tape should be
performed in coded rather than binary mode. If coded mode is set on
an SI tape, the system aborts the job. For other formats, the system
ignores the mode setting, c can be any alphanumeric, one- to seven-
character string.
If lfni=lfn2, the file is read until EOI is encountered.
9-16 60459680 F
![](asset-157.png)
COPYSBF COMMAND
The COPYSBF command copies a file and inserts a space before the first character of each
l in e o f t h e fi le. For a fi l e w it h ou t pri nte r c o nt r ol c ha r act ers , i n se r t s pa c es i n t he file
with this command before routing the file to a printer. The system assumes that a file
routed to a printer has a printer control character as the first character of each line.
You might get undesirable results if you do not ensure that a printer control character
appears first. Refer to appendix H for more information on printer control characters.
NOTE
The COPYSBF command is not recommended for
use with S, L, or F format tapes because it
does not have the data specification
parameters needed to accommodate the
variety of data formats possible with those
tape formats. For an S, L, or F format
tape copying operation, issue a COPY
command with the appropriate parameter
specifications.
When you copy a file with no EOR or EOF
file marks, the resulting file may have a
different logical file structure. In
particular, when copying such a file to
tape, the system adds an EOR mark to the
end of the file. Such changes do not
affect file content but may cause
v e r i fi c a t i o n e r r o r s .
Format:
COPYSBF,Ifnx,Ifn2,n,na.
Parameter Description
lfnx
lfn2
Spec ifies th e name of the file to copy. If thi s param ete r is o mitted,
file INPUT is assumed.
Specifies the name of the file to receive the copy. If this parameter
is omitted, file OUTPUT is assumed.
Spe ci fie s the n um be r of files ( de ci ma l) to copy. If thi s para me te r is
omitted, 1 is assumed.
na Specifies that the job step should not abort if a line terminator does
not appear before an EOR. na can be any alphanumeric, one- to seven-
cha ra cte r str in g.
60459680 C 9-17
![](asset-158.png)
The COPYSBF command copies n files beginning at the current position of lfni to file
lfn2» shifting each line image one character to the right and adding a leading space.
Each line image may contain up to 500 (6-bit) characters. Any characters beyond 500 are
lost. A page eject character is inserted at the beginning of each logical record (refer to
a pp e nd i x I for a l i st o f c ar r ia g e c ont rol c ha r ac t er s ). I f l fni =lf n 2, n fi l es a re
skipped but no data transfer occurs. If the EOI is encountered before the file count is
satisfied, an EOF is written to lfn2, and the operation terminates.
If the COPYSBF command attempts to copy a line longer than 500 6-bit characters, the line is
truncated, and an informative message is issued to the dayfile after the copying completes.
If the last line of a record does not have an end-of-line terminator, the system issues a
dayfile message. If the na parameter is not specified, the job step then aborts.
COPYX COMMAND
The COPYX command copies logical records of a file until a user-specified condition is met,
NOTE
The COPYX command is not recommended for
use with S, L, or F format tapes because it
does not have the data specification
parameters needed to accommodate the
variety of data formats possible with those
tape formats. For an S, L, or F format
tape copying operation, issue a COPY
command with the appropriate parameter
specifications.
When you copy a file with no EOR or EOF
file marks, the resulting file may have a
different logical file structure. In
particular, when copying such a file to
tape, the system adds an EOR mark to the
end of the file. Such changes do not
affect file content but may cause
verification errors.
F ormat:
COPYX,lfn1,lfn2,x,b,c.
Parameter Description
lfn^ Specifies the name of the file to copy. If this parameter is omitted,
file INPUT is assumed.
I f n 2 S p e c i fi e s t h e n a m e o f t h e fi l e t o r e c e i v e t h e c o p y. I f t h i s p a r a m e t e r
is omitted, file OUTPUT is assumed.
9-18 60459680 F
![](asset-159.png)
y<SF£fJ^\
r
Parameter Description
x Provides additional copy specifications. If omitted, one record is
copied. The value for x may be one of the following:
x Description
n Copy n records, when n is a decimal number.
00 Copy all records up to and including first
zero-length record.
name Copy all records up to and including record of
specified name (record name is first seven characters
of record or the name in the prefix table, if
present).
type/name Copy all records up to and including record of
specified type and name (refer to Library Record
Types in section 15 for list of valid record types).
b Specifies the backspace control. If omitted, 0 is assumed.
_b Description
0 Do not backspace.
1 Backspace file lfn^ one record after copying
completes.
2 Backspace file lfn2 one record after copying
completes.
3 Backspace files lfn^ and lfn2 one record after
copying completes.
c Indicates that the copying to or from an S or L format tape should be
performed in coded rather than binary mode. If coded mode is set on
an SI tape, the system aborts the job. For mass storage files and I
and F format tape files, the mode setting is ignored, c can be any
alphan ume ric, 1- to 7-ch aracter string.
The COPYX command copies logical records from lfn^ to file lfn2 at the current position
of lfnj until the condition specified by x is met. It then backspaces the files according
to the value specified by the b parameter. If an EOF or EOI is encountered on lfn, before
the condition specified by x is met, the operation terminates and the backspace parameter b
is ignored. If lfn1=lfn2, the file is read until the termination condition is satisfied
or an EOF or EOI is encountered.
If EOI is encountered on lfnj before the termination condition is satisfied, an additional
EOR is written on lfn2 only if data has been transferred since the previous EOR was
written (or since the beginning of the copying if no EORs have been encountered).
/£W**\
60459680 H 9-19
![](asset-15a.png)
DOCMENT COMMAND
The DOCMENT command extracts either the external or internal documentation from an appropri
ately documented COMPASS or FORTRAN program. For output listing files not connected to your
terminal, the DOCMENT command honors the page size and print density set for your job using
the SET command and the PS and PD symbolic names.
Format:
DOCMENT,Pl,P2,...,pn.
The parameters p^ can be in any order and must be in one of the following forms.
Parameter Description
Omitted The first default value is assumed.
a T h e a l t e r n a t e d e f a u l t v a l u e i s a s s u m e d .
a=x x is substituted for the assumed value.
Any numeric parameter can be specified with a postradix character of either B or D. The
values that p^ can assume are:
Pi Description
I=lfni Specifies the name of the file that contains the page footing
information; this must be a single statement in the following format.
Column(s) Contents
1 Blank
2-45 Document title
46-55 Publication number
56-60 Revision level
61-70 Revision date
S=lfn2 Specifies the name of the file containing the source statement images
from which to extract the documentation. This file is rewound by
default unless the NR parameter is specified.
L=lfn3 Specifies the name of the file on which the output is to be written.
N=nn Specifies the number of copies to be produced.
T=type Specifies the documentation type:
INT Internal documentation (detailed description of the
internal features of the software).
EXT External documentation (detailed description of the
external features of the software).
C=cc Specifies the character code of the key character for documentation.
9-20 60459680 G
^sss
![](asset-15b.png)
0O^*\
/iPN
Pi Description
P = P P S p e c i fi e s t h e n u m b e r o f p r i n t l i n e s p e r p a g e .
NR Disables rewind on the S (source) file.
NT Negates table generator.
TC Lists table of contents.
The following are the default values for the parameters described.
First Alternate
Parameter Default Default Comment
INPUT Page footing information; if I is 0, no
footing information is printed.
Source statement images.
List file.
Number of copies (decimal).
Documentation type.
Check character (two octal digits).
Number of print lines per page. This is
either the system default or the user-set
value of the PS symbolic name (refer to the
SET command in section 6).
Source file rewind status.
Table generator status.
Tab le of contents status.
Refer to Volume 4, Program Interface, for a detailed explanation of the documentation
standards followed. Volume 4 also contains an example of external and internal
documentation for a sample program.
sCOMPILE SOURCE
LOUTPUT OUTPUT
N 1 1
TEXT INT
C47 03
P60 80
NR REWIND NO REWIND
NT ON OFF
TC OFF ON
60459680 H 9-21
![](asset-15c.png)
•^S\
EVICT COMMAND
The EVICT command releases file space for the specified files but does not release file
assignment to the job unless you have the file assigned to a magnetic tape or cannot write
on it. In this case, the system releases the file assignment to the job.
Format:
E V I C T, I f n ! , l f n 2 l f n n .
Parameter Description
lfnj[ Name(s) of the file(s) to be evicted.
The operation that EVICT performs depends on the file characteristics. /^^V
F i l e
Permanent and
primary files
with wr it e
permission
Deferred
routed
filet
Read-only
fi l e
Tape files
All other
files
EVICT Action
Releases all file space except the first track and writes an EOI on
th e firs t sect or of the first trac k, but keep s file ass ign ed to the
job.
Releases all file space and clears all file routing information.
U nl o ad s file .
Releases tape from the job.
Releases file space, but keeps file assigned to job.
Evicting a tape file performs the same function as an UNLOAD command and so cannot be used
to decrease the number of resource units scheduled via the RESOURC command.
tRefer to the ROUTE command in this section.
9-22 60459680 C
![](asset-15d.png)
/sp^V.
FCOPY COMMAND
The FCOPY command converts a file from one character code set to another.
Format:
FCOPY,P=lfn1,N=lfn2,PC=cs1,NC=cs2,PL=lt1,NL=lt2,FL=fl,LB=lb,R,A.
Parameter
P=lfn
N=lfn.
Description
Specifies the file to be converted (default is OLD). Assign lfnx to
the job before performing the FCOPY operation.
Specifies the file on which the converted data from lfnj is written
(default is NEW). If lfn2 is not assigned to the job, FCOPY creates
it.
When copying from lfnj, the system normally reads lfnt to EOI,
preserving all EOR and EOF marks. If an S-format tape is specified
for lfn2, however, the system reads lfnj only to the first EOR,
EOF, or EOI encountered. If you want to copy an entire file to
S-format tape, you can do so by first removing all EORs and EOFs using
the PACK command.
PC=cs,
/S^&\
60459680 H
Specifies the code set of lfn,. The default value for cs, is
ASCII.
cs^ Description
A S C I I S p e c i fi e s t h e 6 / 1 2 - b i t d i s p l a y c o d e t h a t s u p p o r t s t h e
ASCII graphic 63- or 64-character set present on the
current system.
A S C I I 8 S p e c i fi e s t h e 7 - b i t A S C I I c o d e , r i g h t - j u s t i fi e d i n
12-bit bytes.
A S C I I 8 8 S p e c i fi e s t h e 8 - b i t A S C I I c o d e , r i g h t - j u s t i fi e d i n
8-bit bytes.
ASCII63 Specifies the 6/12-bit display code that supports the
ASCII graphic 63-character set.
ASCII64 Specifies the 6/12-bit display code that supports the
ASCII graphic 64-character set.
A S C F L S p e c i fi e s t h e 8 - b i t A S C I I c o d e o n S - f o r m a t t a p e s
(with fixed line length and no line terminators).
DIS Specifies the 6-bit display code that supports the
CDC graphic 63- or 64-character set present on the
current system.
DIS63 Specifies the 6-bit display code that supports the
CDC graphic 63-character set.
DIS64 Specifies the 6-bit display code that supports the
CDC graphic 64-character set.
EBC FL S pe c ifi es th e 8 - bi t E BC D IC c od e s et o n S -f orm at t ap es
(with fixed line length and no line terminators).
9-23
![](asset-15e.png)
Parameter Description
NC=CS2 Specifies the code set of lfn2. The default value for cs2 is ASCII8.
The possible values for cs2 are the same as for csi.
P L = l t i S p e c i fi e s t h e l i n e t e r m i n a t o r u s e d f o r fi l e l f n i . Ta b l e 9 - 2 s h o w s
valid line terminators for each code set. Values that can be
specified for ltx are as follows:
Value Line Terminator
ZB Zero byte.
CR Carriage return.
FF Form feed.
LF Line feed.
US Unit separator.
R S R e c o r d s e p a r a t o r .
CRLF Carriage return and line feed.
LFCR Line feed and carriage return.
n Specified octal character value (See table 9-2).
The default value for 1^ for most code sets is ZB. For ASCII88, the
default is US. ASCFL and EBCFL do not use line terminators.
NL=lt2 Specifies the line terminator to be used in file lfn2- Table 9-2
shows valid line terminators for each code set. Values that can be
specified for lt2 are the same as for the PL=lti parameter. The
default value for lt2 for most code sets is ZB. For ASCII88, the
default is US. ASCFL and EBCFL do not use line terminators.
/^fi^j.
Table 9-2. Code Set-Line Terminator Reference Chart
Code Set ZB CR FF LF US RS CRLF LFCR
DIS 0-77B
DIS63 0-77B
DIS64 0-7 7 B
ASCII 0-77B,
7400-7477B, or
7600-7677B
ASCII63 0-77B,
7400-7477B, or
76O0-7677B
ASCII64 .Y 0-77B,
7400-7477B, or
7600-7677B
ASCII8 0-177B
ASCII88 0-377B
ASCFL
EBCFL
FL=fl Specifies the length of fixed length lines for S-format tapes. The
default value is 80 characters. This parameter is valid only if ASCFL
or EBCFL was specified for CSj^ or CS2.
9-24 60459680 E
![](asset-15f.png)
/3fP&\
Parameter Description
LB=lb Specifies the number of lines per block for S-format tapes. The default
value is 3840 divided by the fixed line length (FL). (For example, if
FL=80, the default for LB is 3840/80 or 48 lines per block.) The
maximum value of FL*LB is 3840. This parameter is valid only if ASCFL
or EBCFL was specified for CSj or CS2.
R Rewinds lfn^ and lfn2 before and after the conversion. The default
is no rewinding.
A Aborts the FCOPY command if errors occur during the conversion. The
default is not to abort when errors occur.
FCOPY reads lfnj to its EOI, preserving its EOR and EOF marks on the converted file. The
maximum line length that can be processed is 160 12-bit codes or 320 6-bit codes. Lines
that exceed the maximum length are truncated.
Files converted to 7-bit ASCII code can be listed on a local batch printer (refer to the
ROUTE command) but cannot be listed at a interactive or remote batch terminal.
Example:
If you are at an interactive terminal and want to print a file (FILE1) created in ASCII
mode, enter a COPYSBF command to prefix the file lines with appropriate carriage control
characters. Then enter an FCOPY command to convert the file containing 6/12-bit display
code (FILE2) to a file containing 7-bit ASCII code (FILE3). Finally, route the converted
file (FILE3) to a line printer that prints the ASCII graphic 95-character set.
/ascii
/copy,file1.
AaBbCcDdEeFfGg
HhliJjKkLlMmNn
EOI ENCOUNTERED.
/rewind,file1.
REWIND,FILE1.
/copysbf,file1,file2.
END OF INFORMATION ENCOUNTERED.
/rewind,file2.
REWIND,FILE2.
/copy,file2.
1AaBbCcDdEeFfGg
HhliJjKkLlMmNn
EOI ENCOUNTERED.
/fcopy,p=file2,n=file3,r.
FCOPY COMPLETE,
/route,fiIe3,dc=lp,ec=a9.
ROUTE COMPLETE.
The following is the local batch output from the ROUTE command.
AaBbCcDdEeFfGg
HhliJjKkLlMmNn
60459680 H 9-25
![](asset-160.png)
LIST80 COMMAND
The LIST80 routine reads a file containing list output produced by the COMPASS assembler and
compresses it to 80 columns, which fits on 8-1/2-inch by 11-inch printer paper. For output
listing files not connected to your terminal, the LIST80 command honors the page length and
print density set for your job using the SET command and the PL and PD symbolic names.
Format:
LIST80tlfn1>lfn2,NR.
Parameter Description
Ifnj Specifies the file from which to copy; if this parameter is omitted,
file LIST is assumed.
Ifn2 Specifies the file to which to copy; if this parameter is omitted,
file OUTPUT is assumed.
NR Indicates that lfnj should not be rewound.
The output listing omits the following information that appears on the COMPASS assembler
output listing.
• COMPASS version number on the page heading.
• COMPASS assembler binary values. f^^%^
• INVENTED SYMBOLS comment.
• Symbolic Reference Table block column that contains either the system text file
name, the overlay name, or the name of the block containing the symbol.
Comments are truncated to column 65.
LOCK COMMAND
The LOCK command prevents writing on a file.
Format:
L0CK,lfnlfifn2,...,lfnn.
Parameter Description
lfn^ Logical file name of a local file.
With the LOCK command, you can set the write interlock for a local file. Subsequently, the
system allows only read operations on the file.
9-26 60459680 D
![](asset-161.png)
L072 COMMAND
00^\
The L072 command reformats files.
Format:
L072,p1,p2,....pn.
Enter any of the following parameters in any order:
El
I
1=1fnx
1=0
S
S=lfn2
L
L= lf n-
T
T=x
H
H=xxx
LP
NR
Description
Specifies that the reformat parameters are on file INPUT.
Reformat parameters are on file lfnj_.
There is no input file of reformat parameters.
If the I parameter is omitted, 1=0 is assumed.
Specifies that the data to be reformatted is on file SCR.
Specifies that the data to be reformatted is on file lfn2.
If the S parameter is omitted, SCR is assumed.
Specifies that the reformatted data is listed on file OUTPUT.
S p eci fi e s t hat t h e r e f o r m at t e d d a ta i s l i ste d o n fi l e l f n3. l f n 3
is always rewound unless the NR parameter is specified.
If the L parameter is omitted, OUTPUT is assumed.
Specifies that the file to be reformatted is of type B.
Specifies that the file to be reformatted is of type x.
_x_ Description
M Modify source data.
C COMPASS source data.
B Other source data.
If the T parameter is omitted, B is assumed.
Specifies that the number of characters per output line is 72.
Specifies that the number of characters per output line is xxx (maximum
allowed is 150 characters), xxx must be greater than or equal to the
number of characters being moved (Nx) plus the starting column number of
the destination field (Ox).
If the H parameter Is omitted, 72 is assumed.
Specifies that the output is formatted for the line printer.
Specifies that the output file is not rew ound.
60459680 E 9-27
![](asset-162.png)
Pl Description
Nx=y Specifies the number of characters to be moved (up to six
fields).
x(l to 6) Number of field being moved.
y Number of characters being moved.
NOTE
The following restrictions apply to the H,
N, I, and 0 parameters.
(Nx+Ix).GT.150 Yields an error (l<x<6),
(Nx+Ox).GT.H Yields an error (l<x<6).
H.GT.150 Yields an error. ~
Ix°y Specifies the field from which the data originates.
x(l to 6) Number of field being moved.
y Starting column of originating field.
Ox=y Specifies the destination field to which the data is going.
x(l to 6) Number of the field to receive data.
y Starting column of destination field.
IT Suppresses query to terminal asking if you want to change any of the
input parameters before processing begins. If omitted, query is
issued. This parameter is effective only from interactive origin jobs.
The following shows the default values assumed for the N, 0, and I parameters for the /
various source types.
Type NI 11 01 N2 12 02 N3 13 03
B72
C750 41 15 112 58
M 2 6 1 48 10 22 82 51
The remaining parameters of these types are defaulted to 0.
L072 reformats files (output files in general). You can rearrange each line (all lines must
be formatted the same) in the format you choose. All default values compress output to 72
columns, which is appropriate for terminal output or 8-1/2-inch by 11-inch printer paper.
If a 1 is encountered in column 1 (the page eject printer control character), the next two
lines of source data are processed as a two-line header. This header is compressed to 72
c o l u m n s f o r a l l s o u r c e t y p e s. I f n o p age e j e c t c o ntrol c h a r a c t e r s a r e e n c ounte r e d , n o ^ ^
headers are processed. )
9-28 60459680 D
![](asset-163.png)
yfl05rv
/ifP^V
The following values apply to the first line of header and cannot be changed.
Nl=42, 11=8, 01=0 (if LP not specified; otherwise, 01=1).
N2=20, 12=90, 02=42.
N3=5, 13=115, 03=62.
N4=5, 14=121, 04=67.
The subheader lines for COMPASS and Modify listings are processed uniquely.
For B listings, the following values apply to the reformatting.
Nl=43, 11=8, 01=0 (if LP not specified; otherwise, 01=1).
N2=29, 12=70, 02=43.
All parameters are passed to L072 by the command. If an input file is specified, L072 reads
it for additional input parameters. If the job originates from an interactive terminal, and
the IT parameter is not specified, you are asked if you wish to change any of the input
parameters. If you enter YES, the system prints the current parameter values and allows you
to change them individually. Pressing the carriage return key for any parameter leaves the
parameter at its former value. In the following examples, the same input parameters are
entered in three possible ways.
60459680 D 9-29 |
![](asset-164.png)
Examples:
Noninteractive entry of parameters from a terminal:
/Lo72,i=0,s=source,t=b,l=out,n4=1,i4=2,o4=75,h=90
Interactive entry of parameters:
/lo72
DO YOU WANT TO CHANGE ANY CONTROL ARGUMENT VALUES-
ENTER: YES OR NO
? yes@
ARGUMENT VALUE
INPUT FILE NAME:
SOURCE FILE NAME: SCR
OUTPUT FILE NAME: OUTPUT
SOURCE FILE TYPE: BATCH ? _
OUTPUT UNE LENGTH: 72 CHARS.? 90_@
NO. OF MOVED FROM MOVED TO
CHARS. COLUMN COLUMN
(XO (NX) (IX) (OX)
9(£R)
? source®
? out @
b@
1.
2.
3.
4.
5.
6.
72
0
0
0
0o;
o
ENTER CHANGES IN THE FOLLOWING FORMAT
NX=AA*CR*
IX=BB*CR*
OX=CC*CR*
ETC.
TO CONTINUE, ENTER *CR* ONLY. ? n=4=1
? i4=2@
? o 4= 75 @
?@>
L072 COMPLETE.
v«s^\
Batch job entry:
L072,I.
where the input file has the following form:
S=SOURCE,L=OUT,T=B.
N4=1,14=2, 04=75.
H=90.
-EOR-
Each line in the input file must end with a terminator.
9-30 60459680 D
![](asset-165.png)
j0^\
0$&!\
MFQUEUE COMMAND
The MFQUEUE command sends a local file from your host to the input or output queue of a
remote host. The MFQUEUE command functions much like the ROUTE command. For most file
transfers between mainframes, ROUTE is the preferred command. Unlike the ROUTE command,
MFQUEUE provides the capability of sending a separate routing directive with the file or of
indicating that the file has a nonstandard data format. The remote host processes the file
according to the routing directive. Only when you need special routing specifications not
provided by the ROUTE command do you need to use the MFQUEUE command. You must be
authorized to use the MFQUEUE command (refer to the LIMITS command).
Format:
MFQUEUE,lfn,ST=lid,DD=dd,I=dirfile,PC=c,DC=dc.
PARAMETER DESCRIPTIONS
Parameters lfn and ST=lid are required and lfn must be the first parameter; the other
parameters are optional and order-independent.
Parameter Description
l f n S p e c i fi e s t h e n a m e o f t h e l o c a l fi l e t o b e r o u t e d t o t h e r e m o t e h o s t .
The file name must be one to seven alphanumeric characters.
ST=lid Specifies the logical identifier (LID) of the remote host to which the
file is to be routed. The LID specification must be three
alphanumeric characters. ST=lid may not specify the local host.
DD=dd Specifies the data format of the file to be transferred. The DD=dd
parameter both describes the character set of lfn on the host where it
currently resides and also specifies the character set lfn is to have
after the transfer.
For file transfers between NOS mainframes and between NOS/BE and NOS
mainframes this parameter is effectively ignored. The file will have
the same format on both mainframes.
The interpretation of the DD=dd parameter depends on the operating
system(s) involved in the file transfer. The following paragraphs
describe how NOS interprets the DD=dd parameter. For its
interpretation by other operating systems, refer to the Remote Host
Facility Usage manual.
60459680 F 9-31
![](asset-166.png)
Parameter Description
On NOS, you can specify the following values for dd:
dd Description
C6 The file contains character data in a 64-character (or
less) subset of the ASCII 128-character set. The character
code of lfn is 6-bit display code and its lines are zero-
byte terminated (Z-type records).
C8 The file contains character data in a larger than
64-character subset of the ASCII 128-character set. The
character code of lfn is the 7-bit ASCII code (right-
justified in 12-bit fields) and its lines are zero-byte
terminated (Z-type records).
US Specifies that the file contains binary data in structured
format with EORs and EOFs. The file is transmitted as a
continuous string of binary data, broken only by EORs and
EOFs as appropriate.
UU Specifies that the file contains binary data without EORs
and EOFs. NOS treats UU as US.
If the file is character data, you do not need to specify a DD=dd
p ar am e te r. T he r em ote h o st d et erm in e s the fo r ma t i n w hic h t o w ri te th e / * =R %|
file. If NOS is the remote host and the DD=dd parameter has not been •
specified, NOS assumes character data and reads/writes the file in C6
format.
I=dirfile Specifies the local file which contains the routing directive that the
system sends to the remote host. The file name must be one to seven
alphanumeric characters. If you specify only the keyword I, file
INPUT becomes the directive file. If you omit the I=dirfile parameter,
the system reads directives from the lines immediately following the
MFQUEUE command. The lines must begin with the prefix character
defined by the PC=c parameter. The system reads the lines until it
comes to a line without the prefix character. It then strips off the
prefix character from each line and concatenates the lines into one
8ingle directive to send to the remote host. This directive must not
exceed the 256-character limit.
P C = c S p e c i fi e s t h e p r e fi x c h a r a c t e r f o r t h e l i n e s o f t h e r o u t i n g d i r e c t i v e .
The default is an asterisk (*). The prefix character can be any 6-bit
display code character, except a closing parenthesis, a dollar sign, a
period, or a colon. To avoid ambiguity between commands and routing
directive s, use alph abetic value s fo r c ca utiou sly.
9-32 60459680 D
![](asset-167.png)
Parameter Description
DC=dc Specifies the disposition codes for the file to be transferred. You
can specify one of the following codes for dc:
dc Description
CP Punch the file in coded format.
IN Queue the file for input.
I X Q u e u e t h e fi l e f o r i n p u t b u t d o n o t r e t u r n t h e o u t p u t
unless explicitly directed to do so.
LP Print the file.
PB Punch the file in system binary format.
P H S a m e a s C P .
P R S a m e a s L P .
P U S a m e a s C P .
P8 Punch in 80-column binary format.
S B S a m e a s P B .
SP Plot in binary format. ■
Example:
To route a 7-bit ASCII file (MYFILE) to a remote mainframe (with REM
as its LID) for execution, enter this command:
MFQUEUE,MYFILE,ST=REM,DC=IN,DD=C8.
THE ROUTING DIRECTIVE
The routing directive provides additional routing specifications for the queued file. The
I=dirfile parameter determines the residence of this directive. The host strips the prefix
characters from the lines of this directive and forwards the directive unaltered (except for
prefix characters) to the remote host for processing. Hence, the directive must be a command
recognized by the remote host.
This section documents only the routing directive recognized by a NOS 2 remote host. For
information on routing directives for other remote hosts, refer to the Remote Host Facility
Usage manual.
The routing directive accepted by a NOS 2 remote host closely resembles its ROUTE command.
Format:
ROUTE,lfn,p1,p2,...,pn.
The parameter descriptions for this directive are the same as those for the ROUTE command
with the following exceptions:
• The lfn parameter is not required on the ROUTE directive and can be omitted.
r
jgpfev
60459680 H 9-33
![](asset-168.png)
• Parameters p± can be any of the following as described for the ROUTE command:
DC=dc FM=fm SC=sc
DO=lid IC=ic SCL=scl
EC=ec ID=id TID=tid
FC=fc PI=pi UJN=ujn
FID=fid REP=rep UN=un
EXAMPLE:
Assume you are at mainframe MFA. To route local file RBPRINT from mainframe MFA to a
remote batch printer logged in with user name ABC on NOS mainframe MFB, enter a command
similar to the following:
MFQUEUE,RBPRINT,ST=MFB.
*ROUTE,DC=PR,UN=ABC.
You can accomplish the same task with the following ROUTE command:
ROUTE,RBPRINT,DC=PR,UN=ABC,ST=MFB.
NEW COMMAND
The NEW command creates a primary file.
Format:
NEW,lfn/ND.
Parameter Description
lfn Specifies the name of the file to be made the primary file.
ND Specifies that no files currently assigned to the job are released.
The NEW command creates an empty file and makes it your new primary file. If you do not ■/^\
specify the ND parameter, the system releases all files assigned to the job, except those '
with checkpoint or no-auto-drop status. Certain system files (for example, ZZZZZCO,
ZZZZZC1, ZZZZZC2, and ZZZZZLD) always have no-auto-drop status. You can give any local file
this status by using the SETFS command. When the ND parameter is specified, any currently
existing primary file becomes a nonprimary local file.
The automatic rewinding of primary files is incompatible with some file manipulation
commands. Refer to the note in PRIMARY command later in this section.
9-34 60459680 G
![](asset-169.png)
OUT COMMAND
The OUT command queues files that you or the system has given a deferred routing (refer to
the ROUTE command, which is described later in this section). The command initiates the
queueing that the system automatically does at job termination.
Format:
OUT.
or
0OT,*,lfn1,lfn2,...,lfnn.
^^ The first format queues all eligible files. The second format queues all eligible files
/F^ except those named (lfn^. If no files are named, all eligible files are queued.
Any file given a deferred routing can be processed by the OUT command. Eligible files also
include local mass storage files named OUTPUT, PUNCH, PUNCHB, and P8. If selected, OUTPUT
is queued for printing and files PUNCH, PUNCHB, and P8 are queued for punching.
File PUNCH is punched as a coded deck in either 026 or 029 mode, depending on the origin of
the job. If the job is a local batch job, PUNCH is punched in the initial keypunch mode of
the job's command record. For all other job origin types, PUNCH is punched in the system
default keypunch mode.
/#*N File PUNCHB is punched as a binary deck in system binary format. File P8 is punched as a
\ binary deck in 80-column binary format.
OVWRITE COMMAND
The OVWRITE command destroys the contents of files by overwriting them. This command does
not apply to tape files or to files on which you cannot write (for example, direct access
files attached in a mode besides WRITE or files that have been locked). The command
overwrites the entire file.
Formats:
OVWRITE,If m, If n2,..., If nm/0P=p1p2.
or
OVWRITE,*,Ifnx,Ifn2,...,lfnm/0P=p1P2.
Parameter Description
lfn^ Specifies a file assigned to your job. This file cannot be a tape
file.
0P=pjp2 Specifies how the files are to be overwritten and whether the files
are to be released from the job after the overwriting. The value p^
can be any of the following:
60459680 D 9-35
![](asset-16a.png)
Parameter Description
p^ Description
Z Overwrite the files with zeroes. This is the
default. You cannot specify both Z and X.
X Overwrite the files first with zeroes, then with ones,
and then with an alternating pattern of ones and
zeroes. You cannot specify both Z and X.
R R e l e a s e t h e fi l e s f r o m t h e j o b a f t e r o v e r w r i t i n g t h e m .
The first format shown overwrites files lfn^. The second format overwrites all files
assigned to the job except files lfn^.
PACK COMMAND
The PACK command removes all EOR and EOF marks from a specified file and copies it as one
record to another file.
Format:
PA CK , lf n1 ,lf n2 ,x.
Parameter Description
lfn^ Specifies the name of file to be packed. From batch origin, lfn^
must be specified; from interactive origin, the primary file is used
if l fni i s omi tte d. The file must n ot be as sig ne d to a i nte ra cti ve
terminal (file type TT).
lfn2 Specifies the name of file to receive packed data. If lfn2 is
omitted, the packed file is written on lfn^.
x Indicates that lfnj should not be rewound before the pack occurs, x
can be any alphanumeric, one- to seven-character string.
The input file, lfnj[, may consist of any number of records or files. If no third parameter
is supplied, lfnj is read from the BOI to the EOI, and all EOR and EOF marks are removed.
It is written to file lfn2 at the current position as one record. File lfn2 is rewound
after t he p ac k; l fni i s n ot .
NOTE
Do not use the PACK command with S, L, or F
format tapes.
9-36 60459680 D
![](asset-16b.png)
00&>\
PRIMARY COMMAND
The PRIMARY command makes a local file the primary file, or it creates an empty primary file.
Format:
PRIMARY,lfn.
Parameter Description
lfn Specifies the name of local file.
If lfn already exists, it must be a local mass storage file in order to be made the primary
file. If lfn does not exist, the PRIMARY command creates it on mass storage. Any currently
existing primary file (other than the lfn specified) becomes a nonprimary local file. If
the specified file is already primary, the operation is ignored.
NOTE
The primary file is rewound before every
command is processed. Therefore, the file
manipulation commands cannot be used to
p o sit i o n w i t h i n t h e fi l e . A n a t t e m pt t o
add to the file using one of the copying
commands may result in writing over existing
data at the BOI.
RENAME COMMAND
The RENAME command changes the name of a local file.
Format:
RENAME,nfni=ofni,nfn2=ofn2,...,nfnn=ofnn.
Parameter Description
nfa^ Specifies the new name of the local file.
ofn^ Specifies the existing name of the local file.
The RENAME command changes the name of the local file ofnj to nfn£. This does not
change the names of files in the permanent file catalog. The renaming is done in the
following manner:
• If local file nfn^ did not previously exist, file ofn^ is simply renamed.
• If a local file nfn.^ already exists and is not the primary file, the system
discards nf^ and gives ofn^ the name nfn^.
• If nfnjL is the primary file, then the system discards nfnj^, gives of^ the
name nfn^, and makes it the primary file. In this case, ofn^ must have a local
file type.
60459680 D 9.37
![](asset-16c.png)
For example, you have only two files assigned to the job. File A is a local mass storage
file and file B has a queued file type. If you issue the following request
RENAME,X=A.
file A is renamed file X, and its file type (local) is not changed. If you issue the request
RENAME,B=A.
file B no longer exists; file A is renamed file B and retains its local file type.
REQUEST COMMAND
The REQUEST command assigns a file to receive checkpoint dumps or sends a message to the
system operator requesting that the named file be assigned to the device described in the
comment field.
Format:
REQUEST,Ifn,checkpoint,AL=level.comment
Parameter Description
lfn Specifies the name of the file to be assigned to a specified device or
to be used as a checkpoint file. ^^
checkpoint Specifies that lfn is to be used as a checkpoint file.
checkpoint Description
CK Each new dump is written at EOI of lfn.
CB Each new dump is written at BOI of lfn.
comment Specifies the comment that is displayed at the system console. In the
comment field, you direct the operator to make the requested device /=s^v
assignment.
AL=level Specifies the security access level to assign to the file. Unless
changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default is the current access level of the job.
On a secured system, the access level you specify must be valid for
the job (ENQUIRE,B returns this information) and for the device to
which you are assigning the file.
On an unsecured system, the parameter has no effect. The system does,
however, check for valid parameter specifications.
When using this command to assign a file for checkpoint dumps on a
secured system, use the AL=level parameter to assign the file at the
highest access level valid for the job (ENQUIRE,B returns this
information). The CKP command aborts the job if the checkpoint file
is not at this access level.
| 9-38 60459680 D
![](asset-16d.png)
/ps^fe\
If the REQUEST command is used to request assignment of file lfn to the equipment specified
in the comment field, lfn must not be a local file.
If the REQUEST command Is used to assign lfn for checkpoint dumps, lfn must be a local file
and either the CK or CB keyword is specified. These keywords are used in conjunction with
the CKP and RESTART commands; they do the following:
• Save all checkpoint dumps by appending each dump to checkpoint file lfn:
REQUEST,Ifn,CK.
• Save only the last checkpoint dump by writing each dump at the beginning of check
point file lfn:
REQUEST,Ifn,CB.
• Save two consecutive checkpoint dumps by alternately writing on two checkpoint files;
REQUEST,Ifni,CB.
REQUEST,Ifn2,CB.
If the CK keyword is specified for different files or if more than two checkpoint files are
specified, the job aborts. The CK and CB keywords specify a checkpoint file that is local
to the job. You can make the checkpoint file permanent by placing a DEFINE commandt before
the REQUEST command.
DEFINE,lfn.
REQUEST,Ifn,CK.
CKP.
You are not required to supply a REQUEST command to define a checkpoint file. You can use
an ASSIGN or LABEL command or you can use default values.
If no REQUEST command specifying a checkpoint file has been detected when the first CKP
command is encountered, the system requests a device, specifies a file name of CCCCCCC, and
selects the CK option. For a subsequent restart job, however, the system assumes you have
made the checkpoint file available.
If lfn is a local file when you enter the REQUEST command, no new assignment is made and job
processing continues with the next command. However, you can reassign lfn by issuing a
RETURN command on the file before entering the REQUEST command.
You can use the REQUEST command to assign a file to a mass storage device. However, you
must be authorized to assign a file to a magnetic tape or auxiliary device. If you do not
have this authorization and attempt to request a tape unit or auxiliary device, the system
aborts the job.
The REQUEST command can also be used to create or access existing seven- or nine-track
unlabeled tapes. If a magnetic tape assignment is needed to satisfy a REQUEST command, the
MT or NT parameter should be specified. For a description of magnetic tape assignment with
the REQUEST command, refer to section 12, Tape Management.
t Any mass storage file used as a checkpoint file must have write permission.
Refer to LIMITS Command in section 7.
60459680 D 9-39 |
![](asset-16e.png)
RESEQ COMMAND
The RESEQ command resequences source files which have leading sequence numbers or adds
sequence numbers to an unsequenced file. The RESEQ command for interactive jobs acts only
upon the primary file and has a different parameter order.
Format for noninteractive jobs:
RESEQ,lfn,type,start,step.
Format for interactive jobs:
RESEQ,start,step,type.
Parameter Description
lfn
type
Specifies the sorted file to be resequenced. The system does not sort
lfn (refer to the SORT command).
Specifies the type of file:
type Description
B BASIC source code. The system updates BASIC statements
containing line references.
T Text source information; a five-digit sequence number
plus a blank is added at the beginning of each line.
The file text, however, is not inspected. Thus, if
line numbers curently exist, two set of line numbers
result.
F Files that contain FORTRAN source code. The system
adds a five-digit line number to the beginning of each
line without a line number but adds no blanks. If your
FORTRAN source file does not have sequence numbers,
specify this parameter to resequence the file.
other Any number at the beginning of a line is considered a
or sequence number and is resequenced according to the
omitted start and step parameters; numbers are added to lines
where no leading sequence numbers are present. You can
use this option with a FORTRAN source file without
destroying the integrity of statement labels if the
file has leading sequence numbers.
start Specifies the new line number of the first line. The default is 100.
step Specifies the line number increment. The default is 10.
Files that have leading sequence numbers include FORTRAN and BASIC source files formatted
for interactive processing. If the file has no leading sequence numbers, five-digit numbers
are inserted at the beginning of each line. No line number can exceed 99999. When the
system encounters line numbers longer than five digits, it uses only the first five digits
to resequence the file.
/^^^\
9-40 60459680 D
![](asset-16f.png)
r"
When resequencing a BASIC source program, you must specify B for the file type parameter or
enter the command under the BASIC subsystem so that the system changes the line number
references within the source statements. The system supplies 5-digit line numbers and line
number references; excess surrounding blanks are used In the expansion of line number
references.
In order to resequence a BASIC program written in 6/12-bit display code, you must call RESEQ
from an interactive job which is in ASCII mode.
Example:
File X contains the following BASIC source statements.
95 ON SGN(A)+2 GOTO 100,110,120 'COMMENT
100 PRINT "A IS NEGATIVE"
1 0 5 G O T O 130 •COMMENT
1 1 0 P R I N T " A IS ZERO"
1 1 5 G O T O 130 •COMMENT
1 2 0 P R I N T " A IS POSITIVE"
130 LET B=A+130
135 END
The following command changes the contents of file X.
RESEQ,X,B,90,10.
File X now has the following contents:
00090 ON SGN(A)+2 GOTO 00100,00120,00140 'COMMENT
•COMMENT
'COMMENT
00100 PRINT"A IS NEGATIVE"
00110 GOTO 00150
00120 PRINT "A IS ZERO"
00130 GOTO 00150
00140 PRINT "A IS POSITIVE"
00150 LET B=A+130
00160 END
The RESEQ command changes the line numbers and the line number references. Line numbers now
begin at 90 and Increment by 10. The comment on the first line is moved to the right to
allow for the expanded line number references.
The RESEQ command retains at most one trailing space on a blank line. During a sort, the
system deletes lines with only one or no trailing spaces. Hence, a RESEQ command followed
by a sort causes all blank lines to be deleted from the file.
60459680 D 9-41
![](asset-170.png)
RETURN COMMAND
The RETURN command releases files assigned to a job and may release file space depending on
the file type.
Format:
RETURN,lfni,Ifn2,•••tlfnn#
or
RETURN,*,Ifnx,Ifn2»...,Ifnn.
Parameter Description
lfn^ Specifies the name of a file assigned to your job. s**%.
The first format returns the named files (lfni,lfn2,...,lfnn). The second format
returns all files assigned to the job except the named files. If no files are named on the
second format, the asterisk returns all files assigned to the job.
There are several exceptions. The RETURN command does not release any files that have
checkpoint or no-auto-drop status. Certain system scratch files (for example, ZZZZZCO,
ZZZZZC1, ZZZZZC2, and ZZZZZLD) have no-auto-drop status. You can give any local file this
status by using the SETFS command.
RETURN performs the following operations according to the file type. ^*^\
Type Operation
Input File name is changed to INPUT*. File space is not released (refer to
Input File Control in section 3 for further information).
Queued File space is released, and the file is no longer assigned to the job.
The file also loses its queued status.
Local File space is released, and the file is no longer assigned to the job.
Primary Same as Local. ]
Library File space remains, but the file is no longer assigned to the job.
Direct access File space remains, but the file is no longer attached to the job.
Tape Tape is no longer assigned to the job. Refer to the REWIND or UNLOAD
command for a description of the processing that occurs if the previous
operation was a write.
In addition, the return of a magnetic tape file or the return of your last direct access
file on an auxiliary removable disk pack decrements the resource demand count as scheduled
by the RESOURC command if, and only if, the total concurrent resource demand (tapes and
removable packs) is presently assigned.
To release a file without decrementing the resource demand count, you can issue an UNLOAD
command. To release file space without releasing the file from the job, you can issue an
EVICT command.
9-42 60459680 D
![](asset-171.png)
If the file is a magnetic tape file and if the previous operation was a write, the following
operations are performed:
• If the tape is ANSI labeled, the system writes a tape mark, an E0F1 label, and three
tape marks and then returns the tape.
• If the tape is unlabeled and the data format specified on the ASSIGN, LABEL, or
REQUEST command is S, L, or F, the system writes four tape marks and then returns
the tape.
• If the tape is unlabeled and the data format is I or SI, the system writes a tape
mark, an E0F1 label, and three tape marks and then returns the tape.
Refer to Magnetic Tape Files in section 2 and Tape Management command in section 12 for
further information about tape files, and to appendix G for a description of an E0F1 label.
REWIND COMMAND
The REWIND command rewinds files. A mass storage file is positioned at its BOI. A tape
file is positioned at BOI (refer to appendix G). If the labeled tape file begins on a
previous volume, the system notifies the operator to mount that volume.
Format:
/^ REWIND,lfn1,lfn2,...,lfnn.
or
REWIND,*,Ifni,Ifn2,...,Ifnn.
Parameter Description
lfn^ Specifies the name of a file assigned to your job.
The first format rewinds the named files (lfnx,lfn2,...,lfnn). The second format
rewinds all files assigned to the job except the named files. If no files are named on the
second format, the asterisk specification rewinds all files assigned to the job.
If the previous operation on the magnetic tape file was a write, a REWIND command causes the
following operations to be performed.
• If the tape is ANSI labeled, the system writes a tape mark, an E0F1 label, and three
tape marks and then rewinds the tape.
• If the tape is unlabeled and the data format specified on the ASSIGN, LABEL, or
REQUEST command is S, L, or F, the system writes four tape marks and then rewinds
the tape.
• If the tape is unlabeled and the data format is I or SI, the system writes a tape
mark, an E0F1 label, and three tape marks and then rewinds the tape.
Refer to Magnetic Tape Files in section 2 and to section 12, Tape Management, for further
information about tape files, and to appendix G for a description of E0F1 labels.
60459680 D 9-43
![](asset-172.png)
ROUTE COMMAND
The ROUTE command queues a file for disposal. The file routing may take effect when the
command is processed, or it may be deferred. If deferred, the routing characteristics
specified define the handling of the file in later job steps or at job termination. This
command can also rescind a prior deferred ROUTE command.
With the proper validation, you can use the ROUTE command to queue files on other
mainframes. Enter the LIMITS command to display the limits and user permissions for your
user name. The MFQUEUE comand also queues files on other mainframes, but use the ROUTE
command for this purpose unless you need special routing specifications not provided by
ROUTE.
PARAMETER DESCRIPTIONS "^
Format:
ROUTE,Ifn,p1,p2,...,pn.
Parameter Description
lfn Specifies the file to route. File lfn must have a queued file type or
a lo cal fi le ty pe; i t can no t be a pri mary or dire ct access file . Th e
lfn parameter is required on all ROUTE commands.
The remaining parameters are order-independent.
PjL Description
D C = d c S p e c i fi e s t h e d i s p o s i t i o n o f t h e q u e u e d fi l e .
dc Meaning
I N Q u e u e t h e fi l e w i t h a n i n p u t d i s p o s i t i o n . N o r m a l j o b
input file format is required and the first record of the
file must be in 6-bit display code. If the Job command
wi th in the file is in er ro r, t he fil e is n ot queu ed and
remains a local file.
LP Queue the file for printing on any printer.
LR Queue the file for printing on 580-12 printer.
LS Queue the file for printing on 580-16 printer.
LT Queue the file for printing on 580-20 printer.
LX Queue the file for printing on 5870 Non-Impact Printer.
NO Queue the file with an input disposition. Output not
explicitly routed by the job is discarded at job
completion. The dayfile is not written to file OUTPUT.
Normal job input file format is required and the first
record of the file must be in 6-bit display code. If the
Job command within the file is in error, the file is not
queued and remains a local file.
9-44 60459680 H
![](asset-173.png)
Pi Description
dc Meaning
P B S a m e a s S B .
P H S a m e a s P U .
PL Queue the file for plotting.
P R S a m e a s L P.
PU Queue the file for punching in coded format.
P8 Queue the file for punching in 80-column binary format.
S B Q ue u e t he fi le f or p unc h in g s y ste m b i na r y f orm at.
SC Rescind prior routing and change the file type to local.
If no prior routing exists, SC is ignored.
TO Queue the file with an input disposition and queue its
output with a wait disposition unless the job routes it
elsewhere. Normal job input file format is required. If
the Job command within the file is in error, the file is
not queued and remains a local file.
WT Queue the file with a wait disposition.
If the DC=dc parameter is omitted and lfn has been previously given a
deferred routing, the file is queued with the disposition code
previously specified. If the DC=dc parameter is omitted and lfn is
not a deferred routed file, the file name may determine the default.
If DC is omitted and lfn is: ROUTE assumes DC=dc is:
OUTPUT DC=LP
PUNCH DC=PU
PUNCHB DC=SB
P8 DC=P8
If a ROUTE command specifies an input disposition for the file (DC=IN,
DC=NO, or DC=TO) and the file has an invalid USER command, the job
containing the ROUTE command aborts with no exit processing. The
security count for the user name that did the ROUTE is decremented
accordingly. If you specify a remote host (ST=lid2) that does not
perform USER command validation, the local host does not check your
queued file for a USER command.
If a ROUTE command sends a file to a remote host with an input
disposition not supported on that host (for example, DC=TO or DC=NO to
a non-NOS 2 host), the remote host accepts the input file but treats
it as though it were routed with DC=IN. Hence, job output from a job
routed to a non-NOS 2 host with DC=NO or DC=TO returns and prints
locally.
60459680 H 9-45
![](asset-174.png)
Pi Description
On a dual-state system, if DC=NO is specified when routing a NOS/VE
batch job from NOS, the job output will be discarded at termination of
the NOS/VE job. If DC=TO is specified, job output will be queued with
a wait disposition.
DEF Indicates that queueing of the file is deferred to a later job step
(OUT command or ROUTE command with the SC parameter specified) or end
of job. If this parameter is specified, the file is created if it
does not exist. DEF is not allowed if DC=IN, DC=NO, or DC=TO.
D O = l i d 1 S p e c i fi e s t h e l o g i c a l i d e n t i fi e r ( L I D ) o f t h e m a i n f r a m e t o r e c e i v e t h e
output generated by the routed file. The LID can be any three-
character, alphanumeric string defined by your site or you can specify
an asterisk.
By default, output returns to the originating mainframe, including
cases where your routed file submits jobs to still other mainframes.
For example, you are at mainframe MAA and you route job X to mainframe
MBB. Job X routes job Y to mainframe MCC. Then the output from both
jobs X and Y return to mainframe MAA by default.
D0=* returns the output to the mainframe that processed the ROUTE
command on which D0=* appears. For example, you are at mainframe MAA
and you route job A to mainframe MBB. Job A routes job B to mainframe
MCC with D0=* specified. Then output from job A returns to MAA but
output from job B returns to MBB.
In both preceding examples, all the mainframes must be directly
connected; that is, no two mainframes have to rely on a third for file
transfers.
You must have special authorization to use this parameter (refer to
the LIMITS command).
EC=ec Defines external characteristics for files queued for printing or
punching.
For files queued for printing, ec can be the following. (For more
information on print trains associated with various EC codes, refer to
Jobs Using Line Printers in appendix A.)
ec Meaning
A4 Provided for NOS/BE compatibility. If you specify A4, the
system uses the appropriate EC default (refer to following
note).
A6 ASCII graphic 63/64-character set.
A9 ASCII graphic 95-character set (except for CYBER model 810
systems using a PSU printer; to route files to a PSU
printer, use the FC parameter). File lfn must be a 7-bit
ASCII file. Refer to the FCOPY command earlier in this
section for information on how to convert a file to 7-bit
ASCII.
9-46 60459680 H
.^^?\
![](asset-175.png)
y*!^
Pi Description
ec Meaning
B4 Provided for NOS/BE compatibility. If you specify
B4, the system uses the appropriate EC default
(re fe r t o f oll ow i ng n ot e).
B6 CDC graphic 63/64-character set.
For files queued for punching, ec can be the following.
ec Meaning
ASCII Punch ASCII.
026 or 026 Punch 026 mode.
029 or 029 Punch 029 mode.
SB Punch system binary.
80C0L Punch 80-column binary.
For files queued for plotting, ec can have the following values:
ec Meaning
T6 Specifies 6-bit, transparent plot data.
T8 Specifies 8-bit, transparent plot data.
| NOTE
If an invalid external characteristic is
specified, the queued file processor cannot
output the file. You must not specify a
printing characteristic for a queued punching
file or a punching file characteristic for a
print file queued for printing. You also
must not specify an e xternal characteristic
not available at the site. If EC is not
specified, an appropriate EC default is set
on the basis of the DC parameter setting and
installation options.
FC=value This parameter has two possible uses depending on your site or host
configuration:
For routing of output requiring special forms, specify FC=fc, where fc
is a 2-character code assigned by the system operator to an output
device. This prevents output of a file before its special forms are
placed in the output device. In this case, omission of the parameter
results in a null value.
60459680 F 9-47
![](asset-176.png)
Pi Description
For sites supporting two 533/536 or 585 printers, an ASCII graphic
64-character printer and an ASCII graphic 95-character printer, you
can use the FC parameter to select either printer. Specify FC=AS to
select the 95-character printer. In this case, omission of the
parameter results in routing to the 64-character printer.
FID=ujn FID is a NOS/BE parameter included for compatibility. Under NOS, this
parameter performs the same function as the UJN parameter.
FM=fm Indicates routing to a remote batch or interactive terminal logged in
with the family name specified. You must have special authorization
to specify an alternate family name (refer to the LIMITS command).
The one- to seven-character family name must be alphanumeric. If you ^_
s p e c i f y o n l y t h e k e y w o r d F M , i m p l i c i t r e m o t e r o u t i n g r e s u l ts ( r e f e r t o • > # w s ^
Implicit Routing following the last parameter description).
IC=ic Specifies internal characteristics of the file; the value ic is one of
the following:
ic Meaning
DIS 6-bit display code.
ASCII 7-bit ASCII code.
BIN Binary.
9-48 60459680 H
![](asset-177.png)
Pi Description
This parameter is normally not specified since its default is
automatically established through the disposition code (DC=dc) and the
external characteristic (EC=ec) parameters. The following lists show
the default for ic for the various ec values.
/fpfeey
ec for printing Default ic
A4 ASCII
B4 DISPLAY
B6 DISPLAY
A6 DISPLAY
A9 ASCII
ec for punching D e f aul t i c
SB BINARY
80COL BINARY
026 DISPLAY
029 DISPLAY
ASCII ASCII
0^*\
ID=id
PI=pi
PRI=pri
REP=rep
Selects the device locally associated with identifier id. Identifier
id can be 0 to 67B (octal default). If you specify only the keyword
ID, implicit remote routing results (refer to Implicit Routing
following the last parameter description).
Selects a print train image denoted either by a digit from 1 to 7 or
by a 1- to 7-character symbolic name assigned by your site.
File priority,
compatibility.
This is a NOS/BE parameter included for
It produces an informative message under NOS.
Specifies the number of additional file copies to be routed to a
destination. The range for rep is from 0 to 31; therefore, the number
of copies that can be sent ranges from 1 to 32. Values for rep beyond
its range are set to zero, an informative message is sent, and one
copy is routed to the destination. The default value is zero; only
one copy is routed.
60459680 G 9-48.1
![](asset-178.png)
Pi Description
SC =s c Sp ec ifi es a prog ra mm ab le f or ma t co nt ro l (P FC ) ar ra y fo r the 5 80 P FC
printer, or a vertical format definition for a 533/536 or 585
printer. The system is released with two PFC arrays, a default
(sc=0), and an alternate (sc=l). If your site has 533/536 or 585
printers, the system will contain six vertical format definitions for
these printers with a default of sc=3. For more information on PFC
arrays and vertical format definitions, refer to the NOS 2 Analysis
Handbook.
For 533/536 printers, you may choose one of the following sc values:
sc Description
1 12-inch forms at 6 lines/inch.
2 12-inch forms at 8 lines/inch.
3 11-inch forms at 6 lines/inch.
4 11-inch forms at 8 lines/inch.
5 8.5-inch forms at 6 lines/inch.
6 8.5-inch forms at 8 lines/inch.
If no sc value is specified, the system default (SC=3) is used. Refer to NOS 2 Analysis
Handbook for more information on 533/536 printers.
9-48.2 60459680 H
![](asset-179.png)
Pi Description
SCL=scl Specifies the service class to be assigned to this routed file. The
value scl must be one of the following:
scl
DF
Description
The default service class according to the origin type
of the routed file. The LIMITS command shows your
default service class assignments.
SY System.
BC Local batch.
RB Remote batch.
TS I n t e r a c t i v e .
DI Detached interactive
NS Network supervisor.
MA Maintenance.
CT
In
Communication task.
Installation class n (0 < n < 3).
\
ST=lid-
60459680 H
When using the ROUTE command to queue a file to a remote host, the
service class for your job must be valid on the remote host and all
mainframes in the link to the remote host.
For a file queued for output, you can only specify a service class
valid for your current job. The default service class for such a file
is the service class of the current job.
For a file queued for input (DC=IN, DC=N0, and DC=T0), you can only
specify a service class valid for local batch jobs. The default
service class in this case is the service class the system assigns by
default to any of your local batch jobs. If you specify a service
class with this parameter for a file queued for input and the file's
Job command also has a service class specification, the service class
specified on the ROUTE command takes precedence. Refer to Job Service
Classes in section 3 for more information on service classes.
Specifies the logical identifier (LID) of the mainframe to which you
are routing the specified file. The LID can be any three-character,
alphanumeric string defined by your site or you can specify an
a s t e r i s k .
By default, the mainframe processing the ROUTE command also processes
the routed file if it is queued for input. This mainframe also
processes the routed file if it is queued for output unless the job
containing this ROUTE command emanated from another job that is
diverting the output elsewhere.
ST=* ensures that the mainframe processing the ROUTE command always
processes the routed file.
9-49
![](asset-17a.png)
Pi Description
In a dual-state environment, you can route a file to NOS/VE by
specifying the NOS/VE LID on this parameter. The file must be in
ASCII (6/12-bit display code) format.
The ST=lid2 on the ROUTE command overrides the ST=lid parameter on
the Job command of the routed file.
You must have special authorization to use this parameter (refer to
the LIMITS command).
TID=tid The TID=tid form of this parameter functions the same as the UN=un
or parameter and is included for compatibility with NOS/BE. The TID=C
TID=C form of the parameter specifies routing to the central site. If you
specify only the keyword TID, implicit remote routing is selected
(refer to Implicit Routing below).
UJN=ujn Specifies a user job name (UJN) for the file to be routed. Except for
input dispositions, the default is the UJN of the job from which you
enter the command. In the case where you specify an input disposition
(DC=IN, DC=NO, or DC=TO), the Job command of the queued file
determines the default UJN.
UN=un Specifies the user name of the remote batch or interactive user to
whom the system routes the file. If you specify only the keyword UN,
implicit remote routing occurs (refer to Implicit Routing following
the last parameter description).
IMPLICIT ROUTING
For remote batch origin jobs, the following action is taken.
• Specifying an ID, ID=id, or TID=C parameter causes routing to the central site.
• Specifying an FM=fm or UN=un parameter with valid arguments causes routing to the ^%^
specified remote batch or interactive terminal. '
• In all other cases, the system routes the file to the originating remote batch
terminal.
For jobs of any origin other than remote batch, the following action is taken.
• Specifying an ID, ID=id, or TID=C parameter causes routing to the central site.
• Specifying UN, TID, or FM causes routing to the terminal specified by the job's
family name and user name at the time of the processing of the ROUTE command.
• Specifying UN=un or FM=fm with valid arguments causes routing to the specified
remote batch or interactive terminal.
You can use the ENQUIRE command to determine whether your routed file is destined for the
central site or a remote batch terminal. If you specify the JSN=jsn or UJN=ujn parameter,
ENQUIRE returns either RB (remote batch routing) or BC (routing to the batch devices at the
central site) in the DS field of the display. /-sS%k
9-50 60459680 F
![](asset-17b.png)
SCOPY COMMAND
The SCOPY command copies a specified number of coded files from one file to another and,
unless explicitly prohibited, indicates the structure of the file being copied by displaying
the EORs and EOFs in the receiving file. A coded file is defined as a file containing lines
of 500 characters or less, each terminated by a zero byte (12 zero bits in the lowest byte
of a word).
NOTE
The SCOPY command is not recommended for use
with S, L, or F format tapes because it does
not have the data specification parameters
needed to accommodate the variety of data
formats possible with those tape formats.
For an S, L, or F format tape copying
operation, issue a COPY command with the
appropriate parameter specifications.
The SCOPY command cannot copy SI format
tapes. If coded mode is set for an SI tape,
the system terminates the job. The TCOPY
utility converts SI coded tape files.
When you copy a file with no EOR or EOF file
marks, the resulting file may have a
different logical file structure. In
particular, when copying such a file to
tape, the system adds an EOR mark to the end
of the file. Such changes do not affect
file content but may cause verification
errors.
Format:
SCOPY,Ifni,lfn2,n,fchar,lchar,na,R,fcs,fline,lline,ns.
Parameter Description
lfn
lfn<
Specifies the name of the file to be copied. You must specify this
parameter.
Specifies the name of the file onto which lfni is copied; if this
parameter is omitted, file OUTPUT is assumed.
Specifies the number of files (decimal) to copy; if this parameter is
omitted, the file is copied to EOI.
60459680 F 9-51
![](asset-17c.png)
Parameter
fchar
lchar
na
R
fcs
Description
Specifies the first character position (1 to 500 for 6-bit characters)
of each line to copy; if this parameter is omitted, the copy begins at
character position l.t
Specifies the last character position (1 to 500 for 6-bit characters)
of each line to copy; lchar must be greater than or equal to fchar. If
this parameter is omitted, the copy ends at character position 500.t
Specifies that the job step should not abort when a line terminator
does not appear before an EOR. na can be any string of one to seven
alphanumeric characters.
Specifies that both lfni an(* lfn2 be rewound before copying.
Specifies the character set code of lfni. The value 0 indicates
display code or 6/12-bit display code. 0 is also the default. No
other values are allowed.
fl i n e
lline
ns
Specifies the line number of the first line you want to copy from lfni
if lfni Is a sequenced file. If you do not specify this parameter or
if lfni is not a sequenced file (no line numbers), the copying begins
with the first line of lfni.
Specifies the line number of the last line you want to copy from lfni
if lfni is a sequenced file. If you do not specify this parameter or
if lfni is not a sequenced file (no line numbers), the copying is
controlled by parameter n.
Specifi es no s tr uc ture re porti ng . If you s pecif y a non null value , the
system does not display the EORs and EOFs in lfn2. -
If EOI is encountered before the file count is satisfied, an EOF is written on lfn2, and
the operation terminates. If a line is encountered that has more than lchar characters, the
excess characters are truncated.
tSince many characters in 6/12-bit display code require 12 bits rather than 6, this
parameter may produce unforeseen results when copying a file containing 6/12-bit display
code data. Refer to Appendix A for a description of character set codes.
<*^«tE|v
9-52 60459680 F
![](asset-17d.png)
JpPSV
SCOPY writes lines with an even number of characters. If an input line has an odd character
count and the last character is a blank not immediately preceded by a colon, the last
character is removed. If an input line has an odd character count and the last character is
not a blank or is a blank immediately preceded by a colon, an additional trailing blank is
appended.
If SCOPY attempts to copy a line longer than 500, 6-bit characters, the line is truncated, I
and an informative message is issued to the dayfile after the copy completes. '
If the last line of a record does not have an end-of-line terminator, SCOPY issues a dayfile
message. If the na parameter is not specified, the job step then aborts.
Example:
old,filea
READY.
list
RECORD 1
AAA
BBB
CCC
RECORD 2
DDD
EEE
FFF
RECORD 3
GGG
•JHH
III
READY.
scopy,filea
RECORD 1
AAA
BBB
CCC
-E0R-
RECORD 2
DDD
EEE
FFF
-E0R-
RECORD 3
GGG
HHH
III
-E0R-
-E0F-
READY.
60459680 F 9-53
![](asset-17e.png)
SECHDR COMMAND
The SECHDR command adds security-related information to a file. You can choose to have this
information placed on banner pages throughout the file, placed at the top and bottom of each
page, or both.
Format:
SECHDR,Ifn,FF,0P=p1p2p3p4.
The parameter lfn is required and must be the first parameter. The other parameters are
optional and order-independent.
Parameter Description
lfn Specifies a file assigned to your job.
FF Specifies that the file has already been formatted for printing; that
is, carriage control characters (such as those controlling page ejects
and page density) have already been inserted.
0Ps=PlP2P3P4 Specifies where the security information will be inserted in the file.
OP=B is the default. You have the following choices:
Pi Description
B Print the security information on two banner pages,
one at the beginning of the file and one at the end of
t h e fi l e .
F Print the security information on a banner page at the
beginning and the end of every logical file within
fi l e l f n .
R Print the security information on a banner page at the
beginning and the end of every logical record within
file lfn.
P P r i n t t h e a c c e s s l e v e l o f t h e fi l e a t t h e t o p a n d
bottom of every page of output.
You can specify any combination of these options.
y^^v
9-54
^B&K
60459680 D
![](asset-17f.png)
v^gfey
The banner pages have the following header lines:
FILE NAME = file name
DATE PRINTED = yy/mm/dd
USER NAME = user name
where the lowercase characters represent job-specific information. Following those header
lines, the system prints the security access level of the file in large block characters.
Example:
The following command specifies that security information is to be placed both in a header
and a footer on each page of the file and also on banner pages that are to be printed at the
beginning and ending of each logical file within FILE213:
SECHDR,FILE213,0P=FP.
SETFAL COMMAND
The SETFAL command changes the security access level of a local file. In most cases, a
local file receives the access level of the job that creates it. Refer to Security Features
in section 3 for a detailed discussion of file access levels.
Format:
SETFAL,Ifn,AL=level.
The two parameters are required and are order-dependent.
Parameter Description
l f n S p e c i fi e s a l o c a l fi l e . T h e fi l e c a n n o t b e a d i r e c t a c c e s s p e r m a n e n t
file or a magnetic tape file.
AL=level Specifies the security access level you want asssigned to the file.
Unless changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
On a secured system, the access level you specify must be valid for the job (ENQUIRE,B
returns this information). In addition, to lower the access level of a file, you must be
authorized to do so (refer to the LIMITS command).
On an unsecured system, the system does not use this access level assignment in monitoring
access to the file. It does, however, become an attribute of the file.
/?s$P^V
60459680 D 9-55
![](asset-180.png)
^saafjjk
SETFS COMMAND
The SETFS command sets the auto-drop or no-auto-drop status on files assigned to your job.
If given the no-auto-drop status, a file is not released from your job by commands like NEW,
OLD, CLEAR, RETURN(*), and UNLOAD(*).
Format:
SETFS,Ifnx,Ifn2,...,Ifnn/FS=fs.
or
SETFS,*,lfn1,lfn2,...,lfnn/FS=fs.
Parameter Description
lfn£ Specifies the local file to be affected.
FS =fs Spec ifi es e ithe r th e au to -dr op ( FS =AD ) or no -a uto -d rop (F S=NAD )
status. The default status for user-created files is auto-drop.
Certain system files (for example, ZZZZZCO, ZZZZZC1, ZZZZZC2, and
ZZZZZLD) always have the no-auto-drop status.
The first format of th e command giv es th e specified status to th e files lfni. ^e second
format gives the specified status to all files assigned to the job, except files lfn£.
The CLEAR command never releases a file that has a no-auto-drop status, the RETURN and
UNLOAD commands release such a file only if you specify it, and the NEW or OLD command
releases such a file only if It has the same name as the new primary file.
SKIPEI COMMAND
The SKIPEI command directs the system to position the specified file at the EOI.
Format:
SKIPEI,lfn.
Parameter Description
lfn Specifies the name of the file to be positioned.
On magnetic tapes where no EOI is defined, the operation stops at an EOF.
The SKIPEI command has no effect on a primary file since the file Is rewound before every
operation.
/*riS*S
I 9-56 60459680 D
![](asset-181.png)
SKIPF COMMAND
The SKIPF command directs the system to bypass, in a forward direction, the specified number
of files from the current position of the named file.
Format: T^
SKIPF,Ifn,n,m.
Parameter . Description
lfn Specifies the name of the file tpybe positioned.
n Specifies the number (decimal) of files to be skipped; if the
parameter is omitted, the system assumes 1. The maximum for n is
262143.
m S p e c i fi e s t h e fi l e m o d e : C f o r c o d e d , B f o r b i n a r y . I f m i s o m i t t e d ,
the system assumes the file is^-i'n binary mode. If coded mode is set
on an SI tape, the system aborts .the job.
If an EOI is encountered before n files are bypassed, ''file lfn .remains positioned at the EOI,
The SKIPF command has no effect on a primary file since the file is rewound before every
operation.
SKIPFB COMMAND
The SKIPFB command directs the system to bypass, in the reverse direction, the specified
number of files from the current position of the named file.
Format:
SKIPFB,lfn,n,m.
Parameter Description
lfn Specifies the name of the file to be positioned.
n S p e c i fi e s t h e n u m b e r ( d e c i m a l ) o f fi l e s t o b e s k i p p e d ; i f t h e
parameter is omitted, the system assumes 1. The maximum for n is
262143.
m Specifies the file mode: C for coded, B for binary. If m is omitted,
the system assumes the file is in binary mode. If coded mode is set
on an SI tape, the system aborts the job.
If the system encounters BOI (or the load point of the current volume of a multivolume tape
file), SKIPF command processing ends.
The SKIPFB command has no effect on a primary file since the file is rewound before every
operation.
60459680 D 9-57 |
![](asset-182.png)
SKIPR COMMAND
The SKIPR command directs the system to bypass, in a forward direction, the specified number
of logical record or file marks from the current position of the named file.
Format:
SKIPR,Ifn,n,level,m.
Parameter Description
lfn Specifies the name of the file to be positioned.
n S p e c i fi e s t h e n u m b e r ( d e c i m a l ) o f r e c o r d a n d fi l e m a r k s t o b e s k i p p e d ;
if this parameter is omitted, the system assumes 1. The maximum for n
is 262143.
level Specifies the level number; 0OLevel<17. If 0<level<16, both EOR and
EOF marks are counted. If level is 17, only EOF marks are counted.
The default is 0.
m S p e c i fi e s t h e fi l e m o d e : C f o r c o d e d , B f o r b i n a r y . I f m i s o m i t t e d ,
the system assumes the file is in binary mode. If coded mode Is set
on an SI tape, the system aborts the job.
Consecutive EOR or EOF marks are counted separately. If the EOI is encountered before n EOR
and EOF marks are bypassed, file lfn remains positioned at the EOI.
The SKIPR command has no effect on a primary file since the file is rewound before every
operation.
^/■^ilv
SORT COMMAND
The SORT command sorts a file of lines in numerical order based on leading line numbers
consisting of a specified number of digits.
Format:
SORT,lfn,NC=n.
Parameter Description
l f n S p e c i fi e s t h e fi l e t o b e s o r t e d , l f n m a y b e a l o c a l fi l e o r a d i r e c t
access permanent file assigned to your job.
N C =n S p eci fi e s t h e n u m b e r o f l e a d i ng l i ne n u mbe r d i g it s t o u s e i n s o r ti n g
the file. n<10. The default is 5.
In the case of duplicate line numbers, all lines other than the first are considered
correction lines. All lines with the same number are deleted from the file except the last
line encountered.
For input from an interactive terminal, SORT deletes a line if a line number is followed by
an empty line or a line number is followed only by a blank. However, the system retains a
line with more than one blank after the line number.
For input from cards, SORT deletes a line if a card containing only the line number is
submitted.
| 9 - 5 8 60459680 D
,**C3SmV
![](asset-183.png)
/ff^s
If a line number contains more than n digits, you can delete the line either by entering the
first n digits of the line number and pressing the carriage return (terminal input) or by
submitting a card containing only the first n digits of the line number (batch input).
After the sort, lfn is packed and set at EOI.
TCOPY COMMAND
The TCOPY command copies X (external) format binary tapes or E (line image), B (blocked), or
SI (system internal) format coded tapes to mass storage, to an I format tape, or to an SI
binary format tape. It also writes E or B format tapes converted from files on mass
storage, I format tape, or SI format binary tape. The X binary and E, B, and SI coded tape
formats were supported under earlier versions of NOS. Refer to appendix I for the tape
formats of B, E, and X format coded tapes. Now, to access data or write data in one of
these formats, the tape must be assigned as an S (stranger) format tape (refer to the tape
assignment commands in section 12) and the file copied using the TCOPY command.
Order-dependent format:
TCOPY,Ifnj,Ifn2,format,tc,copycnt,charcnt,erlimit,pip2,Ifn3,ns.
Order-independent format:
TCOPY,I=lfni,0=lfn2,F=format,TC=tc,N=copycnt,CC=charcnt,EL=erlimit,
PO=pip2,L=lfn3,NS=ns.
The parameters on the TCOPY command can appear in order-dependent format, order-independent
format, or a combination of both.
If order-dependent and order-independent parameters are mixed In one TCOPY command, the
order-dependent parameters must appear in their proper position. All parameters are
optional. However, the specification of certain parameters precludes the application of
others. A nonapplicable parameter may be ignored or may generate an error. This is stated
in the individual descriptions of the parameters.
/*•*** The parameters are defined as follows:
Parameter Description Default
I=lfni Specifies the file to copy. INPUT
0=lfn2 Specifies the file to receive the copy. OUTPUT
F=format Data format that specifies the type of conver- X
sion for the copying operation. This can be
any one of the following.
format Conversion
Copy an E format tape to mass
storage, an I, or an SI binary tape
file, or generate a new E format
tape from mass storage, an I, or an
SI binary tape file. The E tape
must be unlabeled and assigned as S
format.
60459680 D 9-59
![](asset-184.png)
Parameter Description
format Conversion
B C o p y a B f o r m a t t a p e t o m a s s
storage, an I, or an SI binary tape
file, or generate a new B tape from
mass storage, an I, or an SI binary
tape file. The B tape must be
unlabeled and assigned as S format.
X Copy an X format tape to mass
storage, an I, or an SI binary tape
file. The unlabeled input tape must
be assigned an S format, with noise
size of eight frames for seven-track
tape or six frames for nine-track
tape (refer to NS parameter on tape
assignment command).
S I C o p y a n S I c o d e d f o rma t t a p e t o m a ss
storage, an I, or an SI binary tape
file. The labeled or unlabeled
input tape must be assigned as S
format, with noise size of eight
frames for seven-track tape or six
frames for nine-track tape (refer to
NS parameter on tape assignment
command). If the SI coded input
tape is completed before EOI is
encountered; the position of the
input tape after the copying is
indeterminate. This is because
control words are used on the SI
coded tape read via S format (EOF on
an SI coded tape is a level 17g
block terminator, whereas EOF on an
S tape is a tape mark).
TC=tc Specifies the termination condition for copying
used in conjunction with N=copycnt. The term
ination condition can be specified as follows:
Default
Copy to double EOF
(TC=Dor TC=EOD)
F or
EOF
I or
EOI
D or
EOD
When this TC=tc value is set, the
N keywordspecifies the number of
fi le s t o c o py.
This specifies copying to the end
of information. The N keyword is
ignored.
When this TC=tc value is set, the
N keyword is the number of double
EOFs to which to copy.
N=copycnt Specifies the copy count used by the termination
condition parameter TC=tc.
9-60 60459680 H
![](asset-185.png)
Default
136 characters for
E format; 150
characters for B
format.
Zero
Parameter Description
CC=c har cnt Specifies the character co unt which determines
maximum block size (line length) in characters
for an E or B format tape. This parameter can
only be specified for copying an E or B format
tape.
EL=erlimit Specifies the error limit, which sets the number
of nonfatal errors allowed before abort. An
EL=U specification allows an unlimited number of
errors before an abort. This includes parity
errors and block-too-large errors which are re
turned by the tape subsystem after completing
re co ve ry p ro ce du res. I t al so in cl ud es i nv al id
block format errors (invalid byte-count coded
format and/or unused bitcount) for X format and
SI coded format tapes. Error limit is ignored
when generating an E or B format tape from mass
storage, an I format, and an SI binary format
file since control word read is notused. Error
limit is likewise ignored if the input file de
vice does not support control word read (termi
nals). In that case, any error aborts the job.
P0=pip2 Specifies one or both of the following processing
options (not separated by commas).
E Input blocks with parity errors or block-
too-large errors are processed (copied).
T When generating a B or E format tape,
blocks exceeding the maximum block size
(refer to the CC°charcnt parameter) are
truncated. P0=T is not allowed for other
file conversions.
L=lfn3 Specifies the name of an alternate output file to
receive parity error messages when extended error
processing is in effect (nonzero EL specified),
in which case, the file name lfn3 must not be
the same as lfn2.
NS=ns Noise size. Any input block containing fewer than
ns characters is considered to be noise and is
discarded. This parameter is valid only for E
format to B format conversions. The maximum value
that can be specified for ns is 41. If NS=0 is
specified, the default value of 18 is used.
Example:
The following TCOPY command combines order-dependent and order-independent parameters:
TCOPY,TAPE1,FILE2,E,CC=200,EL=12.
Error blocks are
skipped.
Lines exceeding
the maximum line
size are split
into multiple
b l o c k s .
OUTPUT
60459680 D 9-61
![](asset-186.png)
The input file TAPEl is an E format tape (assigned as an S format tape). It has a maximum
of 200 characters per line. The copying terminates when a double EOF is encountered
(default). The output file FILE2 can be a mass storage file or an I or SI binary format
tape. The error limit allows up to 12 nonfatal errors (parity/block-too-large), and the bad
data is skipped (default) with informative error messages written to the file OUTPUT
(default).
The TCOPY command begins a copying operation at the current position of both files and
continues until the copy termination condition for copying is met or EOI is encountered.
This termination condition can be a file count, double EOF count, or EOI. If the copying is
terminated by a double EOF (for TC=E0D parameter), the second EOF is detected on lfni but
is not transferred to lfn2. If lfni=lfn2, the named file is read until the
termination condition is satisfied or EOI is encountered. An SI coded tape can be
positioned correctly only to EOI (refer to the F=SI parameter description).
If you specify a file count TC=EOF, and EOI is encountered on the input file before the file ,^m\
count is satisfied, an additional EOF is written on the output file only if data or records }
have been transferred since the previous EOF was written (or since the beginning of the
copying, if no EOFs have been encountered).
The EL=erlimit or P0=E parameters provide extended error processing. This allows the
processing or skipping of blocks with parity errors or block-too-large errors. The block
count for the first block to be copied is initially set to zero and is incremented by one
for every block and every EOF processed.
When creating a B format tape from a mass storage, I, or SI binary format file, a block
shorter than the noise size specified on the tape assignment statement is blank filled to
the noise size. A noise block could also be generated when a block exceeding the maximum
block size for the B format tape is split into multiple blocks. If the P0=T parameter is
specified, blocks exceeding the maximum block size are truncated.
When creating an E format tape from a mass storage, I, or SI binary format file, blocks that
exceed the maximum block size for the E format tape are split into multiple blocks. If a
continuation block contains only the end-of-line indicator (zero word), the continuation
block is discarded. If the PO1^ parameter Is specified, blocks exceeding the maximum block
size are truncated (all continuation blocks are discarded).
TDUMP COMMAND
The TDUMP command lists a file in octal or alphanumeric format. It dumps the entire file or
the specified number of lines, records, or files. If more than one limit is set, the limit
reached first overrides the others. If you are in ASCII mode (refer to the ASCII command in
section 8) and the output file is assigned to your terminal, TDUMP interprets input and
displays alphanumeric output as 6/12-bit display code.
NOTE
TDUMP produces unpredictable results when
dumping an S, L, or F format tape file.
Use the COPY command to convert the S, L,
or F format tape file to a mass storage
file or to an I or SI binary format tape
file before attempting to dump the file
using TDUMP.
9-62 60459680 D
![](asset-187.png)
/§3^S
Format:
TDUMP,Pi,p2,.
El
I = l f n L
L=lfn2
0
A
R=rcount
»Pn«
Description
Specifies the local file to be dumped (default is TAPE1).
Sp ec ifi es t he lo ca l fil e t o wh ic h th e outp ut is wri tt en (d ef au lt i s
OUTPUT). If lfn2 is not a local fil e, TDUMP creates it. It does
not rewind lfn2 before or after the dump.
Specifies an octal dump only.
Specifies an alphanumeric dump only.
If both 0 and A are specified, the last one overrides. If neither 0
nor A is specified, TDUMP lists both an octal and an alphanumeric dump.
Specifies the maximum decimal number of records to be dumped. If R is
omitted or set to zero, the dump continues to EOI.
NOTE
The record count restarts at each EOF.
F=fcount
N=lines
NR
Specifies the maximum decimal number of files to be dumped. If F is
omitted, the dump continues to EOI. If F=0, dump continues until an
empty file (double EOF) or EOI is encountered.
Specifies the maximum decimal number of lines to be dumped. If N is
omitted or set to zero, the dump continues to EOI. The blank line
output with the end-of-record, end-of-file, end-of-information, and
ABOVE LINE REPEATED messages is included in the line count.
Do not rewind file lfni before dump (default is to rewind lfni).
Example:
Two lines, each containing the alphabet, were input to file X from an interactive terminal.
File X was dumped to file Y producing the following output.
- FILE BUMP - TDUMP,I=X,L=Y. yy/mm/dd. 08.05.51. PAGE 1.
F 1 R 1 W 0- 0102 0304 0506 0710 1112 1314 1516 1720 2122 2324 2526 2730 3132 0000 0000 0102 0304 0506 0710 1112
ABCDEFGHIJ KLMN0PQRST UVWXYZ ABCDEFGH1J
F 1 R 1 W 4 - 1 3 14 15 1 6 1 7 2 0 2 1 2 2 2 3 2 4 2 5 26 27 3 0 3 1 3 2 0 00 0 0 0 0 0
KLMNOPQRST UVWXYZ
— END OF RECORD —
— END OF INFORMATION —
— END OF DUMP —
60459680 D 9-63
![](asset-188.png)
The prefix
F 1 R 1 W 0
means file 1, record 1, word 0. The zeros following each alphabet are the end-of-line
indicators.
UNLOAD COMMAND
The UNLOAD command releases files assigned to the job and may release file space (depending
on th e fi le ty pe) .
Format:
UNLOAD,Ifnj,Ifn2,...,Ifnn.
or
UNLOAD,*,Ifnj,Ifn2,...,Ifnn.
Parameter Description
lfni Specifies the name of a file assigned to your job.
The first format unloads the named files (lfni,lfn2,...,lfnn). The second format unloads
all files assigned to the job except the named files. If no files are named on the second
format, the asterisk specification unloads all files assigned to the job. There are some
exceptions. The UNLOAD command does not release any files that have checkpoint or no-auto-
drop status. Certain system scratch files (for example, ZZZZZCO, ZZZZZC1, ZZZZZC2, and
ZZZZZLD) have no-auto-drop status. You can give any local file this status by using the
SETFS command.
The UNLOAD command performs the same function as the RETURN command except as noted below.
Refer to the description of the RETURN command given earlier in this section to determine
the operation performed for each file type.
I f t h e fi l e b e i n g u n l o a d e d i s a m a g n e t i c t a p e fi l e o r a d i r e c t a c c e s s fi l e r e s i d i n g o n a n ^
auxiliary removable pack and the job requires more than one tape or pack concurrently, the
UNLOAD command differs from the RETURN command. It does not decrease the number of tapes or
packs that were scheduled for the job with the RESOURC command. If the file is a magnetic
tape file and if the previous operation was a write, the following operations are performed:
• If the tape is ANSI labeled, the system writes a tape mark, an E0F1 label, and three
tape marks and then unloads the tape.
• If the tape Is unlabeled and the data format specified on the ASSIGN, LABEL, or
REQUEST command is S, L, or F, the system writes four tape marks and then unloads
the tape.
• If the tape is unlabeled and the data format is I or SI, the system writes a tape
mark, an EOF1 label, and three tape marks and then unloads the tape.
Refer to Magnetic Tape Files In section 2 and Tape Management commands in section 12 for
further information about tape files, and to appendix G for a description of an EOFl label.
9-64 60459680 D
![](asset-189.png)
UNLOCK COMMAND
The UNLOCK command rescinds the LOCK command and clears the write interlock for the
specified file. This command can only be used on local mass storage files.
Format:
U N L O C K , I f n x , i f n 2 , . . . , l f n n .
Parameter Description
lfni Specifies the name of a local file.
Library files cannot be unlocked.
VERIFY COMMAND
The VERIFY command performs a binary comparison of all data from the current position of the
files specified. The comparison Is meaningful if the files are within the range of
compatible formats listed in table 9-3. For output listing files not connected to your
terminal, the VERIFY command honors the page length and print density set for your job using
the SET command and the PL and PD symbolic names.
Format:
VERIFY,Ifnx,Ifn2,pi,p2,...,pn.
Parameter
lfn
lfn2
Description
Specifies the name of the first file; if this parameter is omitted,
TAPE1 is assumed.
Specifies the name of the second file; if this parameter is omitted,
TAPE2 is assumed.
r
N=x
E=y
L = l f n 3
Optional parameters
Description
In the case of multifile files, specifies the number
of files to verify. The default is N=l.
If you specify just the keyword N, verification
proceeds until the end of information is reached on
b o t h fi l e s .
If you specify N=0, verification terminates whenever
an empty file is encountered on either file.
Specifies the maximum number of errors to list. The
default is E=100. Specifying E has the same effect as
E=0.
L i s t e r r o r s o n fi l e l f n 3 . I f L i s o m i t t e d , t h e
system assumes L=OUTPUT.
60459680 D 9-65
![](asset-18a.png)
-4££$${r~*
Pi Description
A Abort after verification completed if errors occurred.
R Rewind both files before and after the verification.
C Set coded file mode on both files. This is applicable
only to S and L format tapes. If coded mode is set on
an SI tape, the system aborts the job.
C l S e t c o d e d fi l e m o d e o n t h e fi r s t fi l e o n l y . T h i s i s
applicable only to S and L format tapes. If coded
mode is set on an SI tape, the system aborts the job.
C2 Set coded file mode on the second file only. This is
applicable only to S and L format tapes. If coded
mode is set on an SI tape, the system aborts the job.
BS=bsize Defines the maximum block size (PRU size) in central
memory words for an S or L tape. This parameter is
legal only for the verification of S and L tape
verifies. The default for an S tape is lOOOg words,
and for an L tape, it is 2000g words.
Whenever words on lfnj and lfn2 do not match, the VERIFY command lists the following.
• Record number.
• Word number within the record.
• Words from both files that do not match.
NOTE
When printing output for text files, VERIFY
uses the first seven characters of the first
word of the record as the record name.
VERIFY assumes that the record is in 6-bit
display code. Therefore, if you attempt to
display VERIFY output for a record in 6/12-
bit display code while your terminal is in
ASCII mode, the output display may be
garbled* To avoid this problem, you should
set your terminal to NORMAL mode before
listing VERIFY output.
In a verification involving S, L, or F format tapes, the VERIFY command first clears the
extraneous data in the last word of each block (as specified by the byte count and the
unused bit count) and then makes the comparison. On these formats, every block is
considered a record (returns EOR status).
If a verification of an L or F format tape requires additional field length, the VERIFY
command increases the field length as needed.
The maximum block size for an L format tape is specified by the BS=bsize or its default.
The maximum block size for an F format tape is calculated from the frame or character count
specified on the command when the file is assigned..
9-66 60459680 D
![](asset-18b.png)
Table 9-3. Compatible File Structures for the VERIFY Command
FIRST
FILE
(lfnx)
SECOND FILE (lfn2)
Mass Storage
Tape
Format
SI
Mass
Storage
Yes
Yes
Yes
Tape Formats
Yes
Yes
Yes
SI
Yes
Yes
Yes mmm
Y//////A
Yes
/0^\,
NOTE
The No entries indicate that the logical
structures of the files compared are
incompatible. The VERIFY command may
accept those combinations, but the results
require you to make a knowledgeable
correlation of results with the format
descriptions in section 12. In some cases,
the verification of an incompatible pair
may result in a VERIFY GOOD message;
otherwise, a VERIFY ERRORS message is
listed.
/S&*\_
60459680 D 9-67
![](asset-18c.png)
WRITEF COMMAND
The WRITEF command directs the system to write a specified number of file marks on the named
file.
Format:
WRITEF,Ifn,x.
Parameter Description
lfn Specifies the name of the file to be written on.
x Specifies the number of filemarks to be written. If this parameter is
omitted, the system assumes x is 1. The maximum for x is 262143.
If the last operation to the file was a write that did not end with the writing of an EOR or
EOF, WRITEF writes a record mark before it writes the specified number of file marks. For
all other cases, WRITEF writes the file marks without a preceding record mark.
WRITER COMMAND
The WRITER command directs the system to write a specified number of empty records on the
named file.
Format:
WRITER,lfn,x.
Parameter Description
lfn Specifies the name of the file to receive the empty records.
x Specifies the number of empty records to be written. If this
parameter is omitted, the system assumes x is 1. The maximum for x is
262143.
| 9-68 60459680 D
![](asset-18d.png)
/IfP^N
PERMANENT FILE COMMANDS 10
With permanent file commands, you can create, access, and purge permanent files. You can
also control other users' access to your files.
The following are the permanent file commands and their functions.
^v
jj^\
Command
APPEND
ATTACH
CATLIST
CHANGE
COMMON
DEFINE
DROPDS
GET
MFLINK
OLD
PACKNAM
PERMIT
PURGALL
PURGE
RECLAIM
REPLACE
SAVE
SETPFAC
SETPFAL
Function
Appends data to an indirect access permanent file.
Assigns a direct access permanent file to a job.
Lists permanent file information.
Changes permanent file characteristics.
Accesses library type files.
Creates a direct access permanent file.
Releases the disk space associated with a permanent file for which a
valid alternate storage copy exists. The local file copy (if any) will
also be returned.
Retrieves a copy of an indirect access permanent file as a local file.
Transfers a file from one mainfrmae to another or alters the attributes
of a file on another mainframe.
Retrieves a copy of an indirect access permanent file as the primary
file.
Specifies an auxiliary device from which permanent files are to be
accessed.
Grants permanent file access permission to other users.
Purges all files having the specified characteristics.
Purges the named files.
Creates and manages tape and disk backup copies of permanent files.
Copies a local file over an indirect access permanent file.
Creates an indirect access permanent file.
Changes the security access category set of a permanent file.
Changes the security access level of a permanent file.
60459680 G 10-1
![](asset-18e.png)
If an error occurs in an operation on one file of a multifile request, the operation is not
performed on the subsequent files. For example, if an error occurs in the processing of
file B on the following command:
GET,A,B,C,D.
files C and D are not processed.
On a secured system, your job may not access a permanent file unless the job is validated
for the access level and access category set assigned to the file. For an alternate user
access, such an access attempt is treated as a file-not-found error; for an access to one of
your own files, it is treated as a security conflict.
In addition, your job may not change or access certain types of permanent file information.
The following limitations apply:
• CHANGE, PERMIT, and SETPFAC requests are not allowed on files with an access level
lower than that of the job.
• CATLIST requests for permit information are not allowed on files with an access
level higher than that of the job. Normal CATLIST requests are allowed, but
information on the password expiration date and access category set is not included
in the CATLIST output. If a password exists, it is returned as seven asterisks
For more information on permanent files, refer to Permanent Files, Mass Storage File
Residence, and Alternate Storage Subsystems in section 2.
To determine the meaning of a permanent file error message, refer to appendix B.
COMMON PARAMETERS
Some permanent file commands can process several files. Each file is identified by a one-
to seven-character file name. The permanent file operation is performed on each file in the
sequence specified on the command. If the NA parameter is not specified on the command and
if an error occurs while one of the files is being processed, the job step terminates.
When this happens, the files preceding the file in error are processed, but the files
succeeding it are not. If the NA parameter is specified on the command, the job step does
not terminate as a result of the error, and all files are processed except the file in error.
Where a slash is used, it separates the file names from other parameters. The parameters
specified after the slash are optional and order independent. Parameters specified after
the slash affect all files named before the slash.
Permanent file access is controlled by the permit category (CT), user name (UN), file access
password (PW), security access level (AL), and access mode (M). parameters. Permanent file
residence is determined by the preferred residence (PR), auxiliary device (PN), and device
type (R) parameters. Processing options include the no abort (NA), wait-if-busy (WB),
subsystem selection (SS), and backup copy (BR) parameters.
10-2 60459680 G ;
![](asset-18f.png)
In the following list, parameters common to more than one permanent file command are
described in alphabetic order. For the format of each command, refer to the command
descriptions following the parameter descriptions.
Parameter
AL=level
BR=br
Description
Specifies the security access level you want assigned to the file.
Unless changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
When used with the DEFINE command, the default for this parameter is
the current job access level. When used with the SAVE command, the
default is the access level of the local file being saved.
Specifies the backup copy requirement. You can request that a tape
backup copy, an alternate storage subsystem backup copy, or no backup
copy be kept of the permanent file. If BR=br is omitted when the file
is created, a backup copy of the file is stored on tape. For more
information, refer to Alternate Storage Subsystems in section 2.
/#^\
br
Y
MD
Backup Requirement
A tape backup copy should be kept, even if a copy of
the file exists on an alternate storage subsystem.
A tape backup copy need not be kept, if a copy of the
file exists on an alternate storage subsystem.
A backup copy need not be kept for this file. The
system permanent file backup utilities do not process
files with BR=N.
CT=ct Specifies the file permit category. If CT=ct is omitted when the file
is cr eated, the file i s pr ivate . The file c atego ry c an be changed
later.
ct Category
P, PR, or PRIVATE Private files; available for access only
by their creator and by those granted
explicit access permission by the file
creator (refer to the PERMIT command).
The system records the user name of each
user who accessed the file, the number of
accesses made, and the date and time of
the last access by each user. The file
creator can list this information with the
CATLIST(LO=FP) command.
60459680 G 10-3
![](asset-190.png)
Parameter Description
ct
S or SPRIV
Category
NA
PN=packname
10-4
S em i p ri v a te fi les ; a v ail a ble f or
access by a user who knows the
file name, user name, and password
and who has not been explicitly
denied permission to the file
(M=NULL parameter on a PERMIT
command).
Information provided by
CATLIST(L0=FP) for semi-private
files is the same as that provided
for private files.
PU or PUBLIC Public files; available for access
by all users who>know the file
name, user name, and password.
The system records the number of
times the file was accessed and
the date and time of the last
access, but does not record user
names. This information can be
obtained using CATLIST(LO=F).
Specifies the no abort option. Normally, an error in command
processing terminates the job. However, if NA is specified, the job
does not terminate as a result of the error. The error is handled in
one of two ways.
• If the error condition is temporary, job processing is
suspended until the error condition ends (for example, when a
requested direct access file is busy or a requested auxiliary
device is not available). In a multimainframe environment,
job processing may be suspended until some period after the
error condition ends.
• If the error condition is not temporary, the job continues
with the next operation. The job processes the next file
listed on the command or, if no more files are listed,
processes the next command.
You may not specify both the NA and WB parameters.
Specifies the one- to seven-character pack name used in conjunction
with the R parameter to identify the auxiliary device to be accessed
in the permanent file request. This parameter is specified only when
the file to be accessed resides on an auxiliary device.
An auxiliary device is a mass storage device that supplements the
normal family of permanent, file devices. A RESOURC command must be
included in any job that concurrently uses two or more auxiliary disk
packs or an auxiliary pack and a magnetic tape.
If you specify PN=0 on a permanent file command, it overrides any
previously issued PACKNAM commands. You can then access files on the
permanent file family device. PN=0 does not affect subsequent
commands, only the current command.
60459680 G
![](asset-191.png)
J0$^>\
r
Parameter Description
PR=pr Specifies the preferred residence. If PR=pr is omitted when a direct
access file is defined, no preference is assumed. For more
information, refer to Alternate Storage Subsystems in section 2.
Pr Preference
M You prefer that the direct access file be copied to MSF
between accesses. However, the system might not copy the
file to MSF despite the specified preference.
N You have no preference.
PW=password Specifies the 1- to 7-character file password. If a password is
assi gne d to t he file, users oth er than t he file creator must specify
the password when accessing the file.
If only the keyword PW is specified, you must include the password as
a single-line record in the input file. In a interactive job, the
password is requested by a ? prompt at the terminal.
R=r Specifies the device type on which the file resides or is to reside.
_r Device
D B i 8 8 5 - 4 2 D i s k S t o r a g e S u b s y s t e m ( K i < 3 ; f u l l - t r a c k ) .
DCi 895-1/2 Disk Storage Subsystem (l<i<2; full-track).
DDi 834 Disk Storage Subsystem (full-track; l<i<8).
DE Extended memory.
DFi 887 Disk Storage Subsystem (l<i<3; full-track). |
DGi 836 Disk Storage Subsystem (full-track; Ki<3).
DHi 887 Disk Storage Subsystem (l<i<2; full-track). |
Dli 844-21 Disk Storage Subsystem (Ki<8; half-track).
DJi 844-41 or 844-44 Disk Storage Subsystem (l<i<8;
half-track).
D K i 8 4 4 - 2 1 D i s k S t o r a g e S u b s y s t e m ( K i < 8 ; f u l l - t r a c k ) .
DLi 844-41 or 844-44 Disk Storage Subsystem (l<i<8;
full-track).
DMi 885-11/12 Disk Storage Subsystem (Ki<3; half-track).
DQi 885-11/12 Disk Storage Subsystem (l<i<3; full-track).
DP' Distributive data path to extended memory.
DV 819 Disk Storage Subsystem (single-density).
DW 819 Disk Storage Subsystem (double-density).
The value i denotes the number of units (spindles) required for a
particular auxiliary disk file that you will access in your job.
tThe job must be of system origin or you must have system origin privileges.
60459680 H 10-4.1/10-4.2
![](asset-192.png)
![](asset-193.png)
00^\
Parameter Description
The R parameter can be specified on any permanent file command to
identify (along with the PN parameter or with a previous PACKNAM
command) the auxiliary device on which the permanent file resides. R
is specified only if the installation defines the auxiliary device as
removable, and if the desired device type differs from the
installation-defined default device type. R is not required if a
previous PACKNAM command specified the R parameter. If the R
parameter is specified without the PN parameter in a command, R is
ignored on all commands except the DEFINE command (refer to the DEFINE
command in this section).
rSS=subsystem Specifies the interactive subsystem to be associated with the file.
The subsystem can be specified on a SAVE or CHANGE command with one of
the following entries or its abbreviation (the abbreviation is the
first three characters of the entry).
subsystem Interactive Subsystem
BASIC
BATCH
EXECUTE
FORTRAN
FTNTS
NULL
BASIC
Batch
Execute
FORTRAN 5
FORTRAN Extended 4
Null
If the SS keyword is specified without a subsystem, the currently
active subsystem is associated with the file. If the SS keyword is
omitted, no subsystem (null) is associated with the file, unless the
file is the primary file. In that case, the currently active
subsystem is associated with the file.
UN=username Specifies the user name. This parameter must be specified if the
requested permanent file is in another user's catalog. To access the
file, you must have one of the following permissions.
• E xp li ci t p er mi ss io n. T he o wn er of th e f il e granted a cc es s
permission to the user with a PERMIT command.
• I m p lic i t p e r mis s i on . T h e f i l e i s s e m ipr i v ate o r p u b li c a n d s o
can be accessed by users who know the file name, user name,
and password and who have not been explicitly denied
permission.
• Automatic permission. You have automatic permission to access
files in the catalog of another user if your user name
contains asterisks, and if all nonasterisk characters match
characters in the other user's user name.
The UN keyword establishes alternate access validation, unless the
specified user name is the one under which the job is currently being
run. In this case, the specified user name is ignored.
60459680 C 10-5
![](asset-194.png)
Parameter Description
WB Specifies the wait-if-busy option. WB causes the job to wait for busy
files and the mounting of disk packs but to abort on other error
conditions. You may not specify both the NA and WB parameters.
XD=expiredate Specifies the expiration date for a file password or file permit. The
value expiredate must be a six-digit string of the form yymmdd; where
yy, mm, dd are two-digit year, month, and day designators,
respectively. The latest date you can specify and the default
expiration date are site-determined.
You must have special authorization to specify an expiration date for
a file password or permit (refer to the LIMITS command).
XT=expireterm Specifies the life of a file password or permit in days. If you
specify 0, the file password or permit expires immediately. If you
specify 4095 or *, the file password or permit does not expire. The
default expiration term and the maximum expiration term are
site-determined (no site can choose a value greater than 4095,
however) .
You must have special authorization to specify an expiration term for
a file password or permit (refer to the LIMITS command).
10-$ 60459680 C
![](asset-195.png)
0^\
APPEND COMMAND
The APPEND command adds information to the end of an existing indirect access file without
retrieving the file. The APPEND command cannot append data to direct access files.
Format:
APPEND,pfn,Ifnxflfn2 Ifnn/UN=username, PW=password,PN=packname,R=r,NA,WB.
Parameter Description
pfn Specifies the name of the indirect access permanent file to which data
is appended. You do not retrieve the indirect access file before the
append operation, but you must have permission to access the file in
append, modify, or write mode.
If a local copy of the indirect access file is assigned to the job,
the append operation does not change the local copy.
lfni Specifies the name of a local mass storage file to be appended to
pfn. The file must be assigned to the job.
The full descriptions of the following optional parameters are given at the beginning of
this section.
Parameter Description
UN=username Specifies the user name. Specified if pfn is in another user's
catalog.
PW=password Specifies the file password. Specified if UN=username is specified
and pfn has a password.
PN=packname Specifies the auxiliary device name. Specified if pfn resides on an
auxiliary device.
R=r Specifies the device type. Specified if a removable auxiliary device
on a device type other than the installation-defined default is to be
used.
NA Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
WB Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs.
The logical structure of the files is retained; that is, EORs and EOFs are appended as well
as data. The append operation removes the EOI mark at the end of file pfn, but keeps all
EOR and EOF marks.
ATTACH COMMAND
The ATTACH command assigns a direct access permanent file to a job.
Format:
f r AT TA C H » l f n l = p f n i , l f n 2 = p f n 2 l f n n = p f n n / M = m , U N = u s e r n a m e , P W = p a s s w o r d ,
PN=packname,R=r,NA,RT,WB.
60459680 C 10-7
![](asset-196.png)
Parameter Description
lfni=pfni Specifies that the one- to seven-character file name lfni references
direct access file pfni while the file is assigned to the job. If
lfni= is omitted, the direct access file is referenced by its
permanent file name, pfn^ User access is directly to the permanent
file; no working copy is generated.
If a local file name lfni exlsts when this command is processed, it
is discarded (even if command processing does not complete due to an
error).
The full descriptions of the following optional parameters (except M=m and RT) are given at
the beginning of this section.
Parameter Description
M=m File access mode requested. If M=m is omitted, M=READ is assumed.
If m is:
E or EXECUTE
(execute mode)
R or READ
(read mode)
You can:
Execute the file.
Read or execute
t h e fi l e .
RU or READUP t Read or execute
(read update the file
mode)
RA or READAPt Read or execute
(read append the file,
mode)
RM or READMD t Read or execute
(read modify the file,
mode)
Concurrently, other users can:
Read or execute the file.
Read or execute the file.
Read or execute the file; one
user can rewrite the file.
Read or execute the file; one
user can lengthen the file.
Read or execute the file; one
user can lengthen or rewrite
the file.
U or UPDATE Read, execute, or Read or execute the file,
(u pd ate mo de) r ewr ite th e file .
A or APPEND Read, execute, or Read or execute the file,
(append mode) lengthen the file.
t Special care should be taken when using modes RM, RA, or RU. Some programs do not
anticipate that one user may be updating a file while other users are reading the same
file. Specifically, CRM/AAM (refer to the CYBER Record Manager Advanced Access Methods
Reference Manual) is not designed to handle concurrent reading and updating. If a program
using CRM/AAM attempts to access a file attached in RM, RA, or RU mode while a second
program using CRM/AAM is accessing the file in M, A, or U mode, one or both programs may
be aborted with an error message stating that the file was ruined. In fact, the file may
still be intact, but CRM cannot guarantee this and will not allow the access.
10-8 60459680 F
![](asset-197.png)
0^\
Parameter Description
If m is: You can:
M or MODIFY Read, execute,
(modify mode) lengthen, or re
write the file.t
W or WRITE Read, execute,
(write mode) lengthen, rewrite,
or shorten the
file.
Concurrently, other users can:
Read or execute the file.
No access allowed.
You cannot change the file unless you attach it in update, append,
modify, or write mode. Refer to table 10-1 for the access mode
granted when the file is already attached by another user.
If the file is attached in update, append, modify, or write mode, the
current date is recorded as the last modification date even if the
file is not altered.
UN=use rn ame Speci fies the us er n ame. S pecifi ed i f the permanent file(s) is in
another user's catalog.
PW=password Specifies the file password. Specified if UN=username is specified,
and if the permanent file has a password.
PN=packname Specifies the auxiliary device name. Specified if the permanent
file(s) resides on an auxiliary device.
iggPK
R=r
NA
RT
WB
Specifies the device.type. Specified if a removable auxiliary device
on a device type other than the installation-defined default is used.
Spec ifi es th e no a bo rt opt io n. If NA is spe cifi ed , pro ces si ng er ror s
do not terminate the job; the job also waits for the mounting of disk
packs and busy files.
Specifies the real-time processing option. If RT is specified, the
job continues processing after requesting staging of a direct access
file from an alternate storage subsystem to disk. If staging is not
re qu ir ed (t he fil e i s al re ad y re si de nt on di sk ), th e fi le i s assi gn ed
to the job. If the file must be staged, you must issue a second
ATTACH command to assign the file to the job.
If RT is omitted and the file resides only on an alternate storage
subsystem, job processing is suspended while the file on an alternate
storage subsystem is staged to disk and assigned to the job. For more
informati on o n alter nate st orage , refer to Alt ern ate Sto rage
Subsystems in section 2.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs and busy files.
tYou cannot rewrite the file using the copying commands described in section 9. To rewrite
the file while in modify or update mode, you must write your own program using the REWRITE
macro (refer to Volume 4, Program Interface).
60459680 H 10-8.1/10-8.2
![](asset-198.png)
![](asset-199.png)
If an auxiliary device has been previously specified by a PACKNAM command, the system
attempts to find pfni on the auxiliary device rather than on a family device.
In the first column of table 10-1 is the access mode in which the first user attached a
direct access file. The remaining columns are the access modes that may be requested by
another user. At the intersection of the row and column is the access mode granted to the
other user (assuming the user has the appropriate access permission). Busy means that the
other user is sent a message that the file is busy and the job step is aborted unless NA or
WB is specified.
Assuming that no user has the file attached in append, update, modify, or write mode, 16380
users can attach the file concurrently (4095 in read mode, 4095 in read append mode, 4095 in
read update mode, and 4095 in read modify mode). If a user has the file attached in append
mode, 8190 other users can attach the file (4095 in read append mode and 4095 in read modify
mode). If a user attaches the file in update mode, 8190 other users can attach the file
/r^ (4095 in read update mode and 4095 in read modify mode). If a user has the file attached in
\ m o d i f y m o d e , 4 0 9 5 o t h e r u s e r s c a n a t t a c h i t i n r e a d m o d i f y m o d e . I f a u s e r h a s t h e fi l e
attached in write mode, no other user can attach the file.
60459680 F 10-9
![](asset-19a.png)
Table 10-1. Access Mode Granted When Attaching a Currently Attached Direct Access File
Mode in Which
First User
Access Mode Re quested by Another User
Attached File Write Modify Append Update Read Read Modify Read Append Read Update Execute
Write Busy Busy Busy Busy Busy Busy Busy Busy Busy
Mod if y Busy Busy Busy Busy Busy Read Modify Busy Busy Busy
Append Busy Busy Busy Busy Busy Read Modify Read Append Busy Busy
Update Busy Busy Busy Busy Busy Read Modify Busy Read Update Busy
Read Busy Busy Busy Busy Read Read Modify Read Append Read Update Execute
Read Modify Busy Modify Append Update Read Read Modify Read Append Read Update Execute
Read Append Busy Busy Append Busy Read Read Modify Read Append Read Update Execute
Read Update Busy Busy Busy Update Read Read Modify Read Append Read Update Execute
Execute Busy Busy Busy Busy Read Read Modify Read Append Read Update Execute
CATLIST COMMAND
The CATLIST command lists information about your permanent files or the permanent files you
can access in the catalogs of other users. For interactive terminals operating in screen
mode, the system automatically reformats CATLIST output according to the page length set for
your terminal.
Format:
CATLIST,LO=p,FN=pfn,UN=username,PN=packname,R=r,DN=dn,NA,L=lfn,WB.
Parameter Description
L0=p One of the following list options. If LO is omitted, L0=0 is assumed.
_P_
F
Description
Lists pertinent information about the file specified by
the FN=pfn parameter. If you do not specify an FN=pfn
parameter, the system lists information about each file
in your catalog. An example of this list option is
given following the parameter descriptions.
If you specify an alternate user name (UN=username), you
receive a listing of files you can access in the other
user's catalog; however, the only files listed are those
that the owner has explicitly permitted to be listed
(using the AC parameter on a CHANGE, DEFINE, or SAVE
command). The passwords for files in another user's
catalog are not listed. Passwords must be obtained from
the file owner. Charge and project number information
also is not listed in an alternate user CATLIST unless
the calling user has system origin privileges.
10-10 60459680 E
![](asset-19b.png)
Parameter Description
FP
jfiSftRS*\
Description
Lists the access permissions granted for the file
specified on the FN=pfn parameter. If a user name is
also specified (UN=username), only the file permission
granted to that user is listed.
The user names listed include those that have been
granted explicit permission to access the file (private
files only) and those that have accessed the file
through implicit permission (semiprivate files only).
(User names are not recorded for accesses to public
files.) An asterisk follows the user name/permission
mode if explicit permission has been granted this user.
0 (zero) Lists alphabetically the names of the indirect access
files and direct access files in your catalog. If you
specify a user name (UN=username), you receive a list of
the files you can access in the other user's catalog.
A file name surrounded by parentheses indicates that the
file resides on an alternate storage subsystem rather
than on disk.
An asterisk preceding a file name indicates an error
status is set in the catalog entry for the file. The
cause of the error may be one of the following.
• EOI was altered during mass storage recovery.
• Error exists in file data or permit entries.
To clear an error status flag, refer to CHANGE Command
in this section.
P L i s t s o n l y t h e u s e r n a m e s o f u s e r s w h o h a v e a c c ess t o
the specified private file or who have accessed the
specified semiprivate file. This option requires that a
file name be specified (FN=pfn).
X Lists the security access categories associated with the
file specified on the FN=pfn parameter as well as the
information returned by the LO=F parameter. You must
specify the FN=pfn parameter if you specify LO=X.
FN=pfn Specifies the permanent file name. This parameter is required when
listing access permission data (when LO=FP or LO=P is specified).
If FN=pfn and L0=0 are specified, a message indicates whether or not
the file is found in your catalog. If FN=pfn, LO=P, and UN=username
are specified, a message indicates whether or not permission to access
that file has been granted to that user name (username FOUND.).
If pfn contains one or more asterisks, the CATLIST command lists
catalog information for the subset of files whose names match except
where the asterisks appear. For example, FN=***OPL lists all
six-character file names ending in OPL. The asterisk is invalid when
listing permit information with the LO=FP and LO=P list options.
60459680 H 10-11
![](asset-19c.png)
Parameter Description
UN=username Specifies the user name. This parameter has two purposes.
• Fo r lis t opt io ns LO=F a nd L0 =0, i t spe ci fies th e alt ernat e
catalog for which you desire catalog information.
• For list options LO=FP and LO=P, it requests the permission
information recorded for the specified alternate user.
When the short list options, L0=0 and LO=P, are specified, a message
informs you whether or not the file or user name has been found.
PN=packname Specifies the auxiliary device name. This parameter specifies that
CATLIST should use the catalog information on the named auxiliary
device.
R=r
DN=dn
NA
L = l f n
WB
Example 1:
Specifies the device type on which the permanent file catalog
resides. R=r is used with the PN and NA parameters (refer to the R
parameter description at the beginning of this section).
Specifies the device number assigned to a device at system
initialization. If specified, the CATLIST command lists catalog
information from that device.
Specifies the no abort option. If NA is specified, processing errors
do not terminate the job. Do not specify both NA and WB.
Specifies the output file name, lfn is the name of the file assigned
to the job on which CATLIST information is written. If L=lfn is
omitted, the system assumes L=OUTPUT.
lfn is not rewound before or after the CATLIST operation.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs. Do not specify both NA and WB.
Listing of current files in the catalog of STUDENT. The command is entered by user BJK2201
in the form: CATLIST (it is not necessary to specify the L0=0 option since it is the
default value).
CATALOG OF STUDENT
INDIRECT ACCESS FILES
FM/NOSHOP yy/mm/dd. 09.10.47.
ADD (EXAM) GRADES ID M0DIFY2 RESEQ
CAPITAL FIND •HEROFTN LIST PRIME
XX
DIRECT ACCESS FILES
(DIRFILE) DRFILE TV
13 INDIRECT ACCESS FILES,
3 DIRECT ACCESS FILES,
TOTAL PRUS =
TOTAL PRUS =
14.
2.
An asterisk preceding a file name indicates error flag set. A file name surrounded by
parentheses indicates that the file resides on an alternate storage subsystem rather than on
disk.
10-12 60459680 H
![](asset-19d.png)
/gfflfc\
r
Example 2:
Listing of current files that begin with the letters PROC in the catalog of FREE007. The
command is entered by user FREE007 in the form: CATLIST,FN=PROC***.
CATALOG OF FREE007 FM/NOSCLSH yy/mm/dd. 13.27.02.
FILE NAME PROC***
INDIRECT ACCESS FILES
PROCART PROCFIL PR0C1 PR0C1A
4 I N D I R E C T A C C E S S F I L E S , T O T A L P R U S = 1 5 .
Example 3:
Listing of alternate users that have accessed file PRIME in the catalog of STUDENT. The
command is entered by user STUDENT in the form: CATLIST,LO=P,FN=PRIME.
CATALOG OF STUDENT FM/NOSCLSH yy/mm/dd. 07.48.55.
FILE NAME PRIME
USER NUMBERS
CMK2011 JLX2015 KXK4277
3 USERS
Example 4:
Listing of current files in the catalog of SMITH. The command is entered by user SMITH in
the form: CATLIST,L0=F.
C ATA L O G O F S M I T H F M / N 0 S H 0 P y y / m m / d d . 0 8 . 3 7 . 1 9 . PA G E 1
FILE NAHEt FILE TYPE LENGTH DN CREATION ACCESS DATA MOD
PASSWORD COUNT INDEX PERM. SUBSYS DATE/TIME DATE/TIME DATE/TIME
EXPIRES LEVEL PR BR RS AC
CHARGE NO. PROJECT NUMBER
1 C A T X I N D . P R I V A T E 1 8 4 / 0 4 / 1 9 . 8 4 / 0 4 / 2 0 . 8 4 / 0 4 / 1 9 .
1 READ 09.10.23. 08.30.16. 09.10.23.
L V L O N Y D N
2222 PRJ2201
2 T E S T L I B D I R . P U B L I C 1 4 1 8 4 / 0 4 / 1 9 . 8 4 / 0 4 / 1 9 . 8 4 / 0 4 / 1 9 .
0 WRITE 09.11.05. 09.11.05. 09.11.05.
L V L O N Y D Y
2222 PRJ2201
1 I N D I R E C T A C C E S S F I L E , T O TA L P R U S = 1 .
1 D I R E C T A C C E S S F I L E , T O T A L P R U S = 1 .
TAn asterisk preceding a file name indicates that the error flag is set.
60459680 E 10-13
![](asset-19e.png)
Column headings are printed when the LO=F or LO=X parameter is specified. For CATLIST
listing files not connected to a terminal, you can control the print density and page length
using the SET command and the PL and PD symbolic names.
The following are the column headings and their meanings.
Heading
FILE NAME
FILE TYPE
LENGTH
DN
COUNT
INDEX
PERM.
SUBSYS
CREATION
DATE/TIME
Meaning
Permanent file name.
The permanent file type, direct access (DIR) or indirect access (IND),
followed by the file permit category (PRIVATE, SPRIV, or PUBLIC).
Length of the file in decimal PRUs.
Device number of the mass storage device on which the direct access
file is stored. If the file resides on the master device, this field
contains an asterisk.
PASSWORD File password. It is not listed if the file belongs to another user.
If the system is a secured system and if the file has an access level
higher than that of your job, a series of seven asterisks (*******)
replaces the file password.
The number of times the file has been accessed.
This heading is not used by the CATLIST command. It is used by the
PFCAT system utility.
Permission mode allowed the user. The entry is WRITE, MODIFY, APPEND,
UPDATE, READ, READMD, READAP, READUP, EXECUTE, or NULL.
Interactive subsystem associated with the file. The possible entries
are FORT., FTNTS, BASIC, EXEC, and BATCH. If this field contains no
entry, a subsystem is not associated with the file (null).
File creation time and date in the following format.
yy/mm/dd.
hh.mm.ss•
/^^Hh
ACCESS
DATE/TIME
DATA MOD
DATE/TIME
LEVEL
PR
Time and date of the last access to the file.
Time and date of the last modification of the file data.
EXPIRES The expiration date of the file password. It is not listed if the
file does not have a password, the password does not expire, or if the
file belongs to another user.
The security access level of the file. On a secured system, it is
always listed if the file .belongs to you. On an unsecured system, it
is only listed if the level is not null (an assignment has been made)
and the file belongs to you.
Preferred residence for this file. M means alternate storage and N
means no preference. For more information, refer to the description
of the PR parameter at the beginning of this section.
10-14 60459680 G
![](asset-19f.png)
Heading
BR
RS
AC
Meaning
Requested backup copy for this file. Y means tape backup, MD
means alternate storage or tape backup, and N means no backup
required. For more information, refer to the description of the
BR parameter at the beginning of this section.
Actual residence of the file. D means disk, A means alternate
storage, and B means copies of the file exist on disk and on an
alternate storage subsystem. For more information, refer to
Alternate Storage Subsystems in section 2.
Alternate CATLIST permission. Specifies whether alternate users
may obtain information about the file using CATLIST. Y means that
info rm ati on on t hi s file wi ll app ea r in a n alt ernat e use r' s
CATLIST display; N means that an alternate user cannot get
information on this file.
CHARGE NO.
PROJECT NUMBER
Charge number associated with the file.
Project number associated with the file.
CHANGE COMMAND C fl A N<x£l FlLtZN^h /cf -S
The CHANGE command changes certain characteristics of a permanent file. The file need not
be assigned to the job. .
Format:
CHANGE,nfn1=0fni,nfn2=ofn2,...,nfnn=ofnn/PW=password,CT=ct,M=m,BR=br,PR=pr,
SS=subsystem,PN=packname,R=r,NA,CE,WB,XD=expiredate,XT=expireterm,AC=ac,CP.
Parameter Description
nfni=ofni Specifies the file name nfni replaces old permanent file name ofni.
If no name change is desired, only ofni is specified.
The full descriptions of the following optional parameters (except CE and M=m) are given
at the beginning of this section.
Parameter Description
PW=password Specifies the new password. If PW=0 is specified, the CHANGE command
clears the old password without setting a new password.
CT=ct Specifies the new permit category for the file. Entries are P, PR, or
PRIVATE for private; S or SPRIV for semiprivate; and PU or PUBLIC for
public.
M=m Specifies the new alternate user permission mode for semiprivate and
public files. For direct access files, refer to the permission modes
described in the DEFINE command description; for indirect access
files, refer to the permission modes described in the SAVE command
description.
60459680 G 10-15
![](asset-1a0.png)
(^fcw:.jJ7V
Parameter Description
BR=br Specifies the new backup copy selection; entries are Y (tape), MD
(alternate storage), and N (no backup).
PR=pr Specifies the new preferred residence; entries are M (alternate
storage) and N (no preference).
SS=subsystem Specifies the new interactive subsystem to be associated with the
file; entries are BASIC, BATCH, EXECUTE, FORTRAN, FTNTS, and NULL.
PN=packname Specifies the auxiliary device on which the file resides. This
parameter cannot specify a new file residence.
R=r Specifies the device type on which the file resides. This parameter
cannot specify a new file residence.
NA Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
CE Clears file error code. It clears the recovery error field in the
catalog entry. If the job is system origin, it also clears the
alternate storage file errors.
W B S p e c i fi e s t h e w a i t - i f - b u s y o p t i o n . W B c a u s e s t h e j o b t o w a i t f o r t h e
mounting of disk packs.
XD=expiredate Specifies the new expiration date for the file password. The value
expiredate must be a six-digit string of the form yymmdd; where yy,
mm, and dd are two-digit year, month, and day designators,
respectively.
XT=expireterm Specifies the new life of the file password in days. If you specify
0, the file password expires immediately. If you specify 4095 or *,
the file password does not expire.
AC=ac Specifies whether alternate users may obtain information about the
file using CATLIST. Entries are Y (yes) and N (no). The default
value is N.
CP Specifies that the charge and project numbers for the file are to be
replaced by the charge and project numbers currently in effect for
your job.
COMMON COMMAND
The COMMON command accesses the system file SYSTEM.
Format:
COMMON,SYSTEM.
You must be authorized to access library files. If a file with the name SYSTEM is already
local, no action is taken. Otherwise, the system searches for a library file with that
name. If the system finds the file, it assigns the file to your job as a library type file.
10-16 60459680 G
/^^%v
![](asset-1a1.png)
0$^\
DEFINE COMMAND
The DEFINE command creates an empty direct access permanent file. It can also change a file
of the local file type into a direct access file. In this case, the file must reside on a
device on which you can place direct access files (refer to secondary masks and MSAL CMRDECK
entries in the NOS 2 Analysis Handbook or contact site personnel). When you create a file
using the DEFINE command, the file is automatically saved under the charge number and
project number currently in effect for your job.
Format:
DEFINE, lfn i=pfn j, Ifn2=pfn2,..., Ifnn=pfnn/PW=password, CT=ct, M=m, BR=br, PR=pr,
PN=packname,R=r,S=space,NA,WB,AL=level,XD=expiredate,XT=expireterm,AC=ac.
Parameter Description
lfni=pfni The DEFINE command creates an empty direct access permanent file if
pfni and lfni do not exist. If lfni= is omitted, pfni is
assumed to be the local file name and the permanent file name. Each
file name can be from one to seven characters.
If the DEFINE command defines an existing local file as a direct
access file, lfni Is t*le name of the local file, and pf^ is its
new permanent file name.
rThe full descriptions of the following optional parameters (except M=m and S=space) are
given at the beginning of this section.
Parameter Description
PW=password Specifies the 1- to 7-character password that others must specify to
access the file.
CT=ct Specifies the permit category of the defined file. Entries are P, PR,
or PRIVATE for private; S or SPRIV for semiprivate; and PU or PUBLIC
for public. If CT=ct is not specified, CT=PRIVATE is assumed.
M=m Specifies the file access mode permitted to other users if the file is
semiprivate or public, and if explicit access permission has not been
granted to that user. If M=m is omitted, M=READ is assumed.
Other users can attach the file in the following
If m is: modes (refer to the ATTACH command description):
E or EXECUTE Execute.
R or READ Read or execute.
60459680 F 10-17
![](asset-1a2.png)
Parameter Description
RU or READUPT Read update, read, or execute.
RA or READAPT Read append, read, or execute.
RM or READMDT Read modify, read append, read update, read, or
execute.
BR=br
PR=pr
PN=packname
R=r
S=8pace
U or UPDATE Update.
A or APPEND Append.
M or MODIFY Modify, append, update, read modify, read append,
read update, read, or execute.
W or WRITE Write, modify, append, update, read modify, read
append, read update, read, or execute.
N or NULL None.
After a file is defined, it is always assigned to the job in write
mode.
Specifies the backup copy requirement; entries are Y (tape), MD
(alternate storage), and N (no backup). If BR=br is omitted, a backup
copy of the file is stored on tape.
Specifies the preferred file residence; entries are M (alternate
storage) or N (no preference). If PR=pr is omitted, no preference is
assumed•
Specifies the name of an auxiliary device on which the direct access
file is to reside. If PN=packname is omitted, the file residence is
determined by the PR, R, and S parameters.
Specifies the device type on which the permanent file is to reside.
Specify this parameter if a removable auxiliary device with a device
type o ther than the installation-de fined default is used. The devic e
must be a permanent file mass storage device on which direct access
fil es a re a llo we d. I f lf^ alre ad y ex ist s on a dev ice othe r th an
that specified or if an invalid device type is specified, a dayfile
message so informs you. If an auxiliary device name is not specified
by the PN=packname parameter or a previous PACKNAM command, the file
is defined on a family device.
Specifies the decimal number of PRUs requested for the file. It
cannot be larger than your validation limit (refer to LIMITS Command
in section 7). If no device has the specified amount of space
available, a dayfile message so informs you.
tSpecial care should be taken when using modes RM, RA, or RU. Some programs do not
anticipate that one user may be updating a file while other users are reading the same
file. Specifically, CRM/AAM (refer to the CYBER Record Manager Advanced Access Methods
Reference Manual) is not designed to handle concurrent reading and updating. If a program
using CRM/AAM attempts to access a file attached in RM, RA, or RU mode while a second
program using CRM/AAM is accessing the file in M, A, or U mode, one or both programs may
be aborted with an error message stating that the file was ruined. In fact, the file may
still be intact, but CRM cannot guarantee this and will not allow the access.
10-18 60459680 G
![](asset-1a3.png)
Parameter Description
NA
WB
AL=level
XD=expiredate
XT=expireterm
AC=ac
This parameter ensures that the file is assigned to a device that has
the requested space available at the time the file is defined. It
does not guarantee that the space will be available when the file is
w r i t t e n .
Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs.
Specifies the security access level you want asssigned to the file.
Unless changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default for this parameter is the current job access level.
Specifies the expiration date for the file password. The value
expiredate must be a six-digit string of the form yymmdd; where yy,
mm, and dd are two-digit year, month, and day designators,
respectively. You can specify this parameter only if you also specify
PW=password.
Specifies the life of the file password in days. If you specify 0,
the file password expires immediately. If you specify 4095 or *, the
file password does not expire. You can specify this parameter only if
you also specify PW=password.
Specifies whether alternate users may obtain information about the
file using CATLIST. Entries are Y (yes) and N (no). The default is N.
If lf^ does not exist, the device on which pfni resides depends on the R=r and S=space
parameters.
R=r
Specified
Specified
S=space
Not specified
S p e c i fi e d
Not specified Specified
N o t s p e c i fi e d N o t s p e c i fi e d
File Residence
The file resides on the device of type r with the most
space available.
The file resides on the device of type r with the most
space available, provided that device has as many PRUs
available as specified by the space parameter.
The file resides on the device with the most space
available, provided that device has as many PRUs
available as specified by the space parameter.
The file resides on the device with the most space
available.
If an auxiliary device has been previously specified by a PACKNAM command, the file resides
on that auxiliary device rather than a family device.
60459680 D 10-19 |
![](asset-1a4.png)
After the DEFINE command has been processed, the new direct access file remains attached to
the job in write mode. After the file is returned, you must issue an ATTACH command to
access the direct access file. If you purge an attached direct access file, the file
remains attached to the job, although it has been removed from your permanent file catalog.
Until you return the purged file, you cannot define a direct access file having the same
local file name as the purged file.
GET COMMAND
The GET command retrieves copies of indirect access permanent files for use as local files.
Format:
GET,lfni=pfm,lfn2=pfn2,... ,lfnn=pfnn/UN=username,PW=password,PN=packname,
R=r,NA,WB.
Parameter Description
l f n i = p f n i S p e c i fi e s t h e l o c a l fi l e n a m e l f n i g i v e n t h e r e t r i e v e d c o p y o f
indirect access permanent file pfni. If lfni= is omitted, the
local copy of the permanent file is called pfni. If no files are
named, the system uses the primary file name for the permanent file.
The full descriptions of the following optional parameters are given at the beginning of
this section.
Parameter Description
UN=username Specifies the user name. Specified if the permanent file(s) is in
another user's catalog. You must have permission to read or execute
the file(s) (refer to SAVE Command in this section). If only execute
permission has been granted, the file is retrieved in execute-only
mode.
PW=password
PN=packname
R=r
NA
WB
Specifies the file password. Specified if UN=username is specified,
and if the permanent file has a password.
Specifies the auxiliary device name. Specified if the permanent
file(8) resides on an auxiliary device.
Specifies the device type. Specified if PN=packname is specified, or
if a PACKNAM command has been processed and the device type is other
than the system default.
Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs.
10-20 60459680 D
![](asset-1a5.png)
Each permanent file named must be an indirect access file. If the file, lf^, is assigned
to the job before this command is processed, it is returned. The new local file is rewound
after it is retrieved. More than one user can have local copies of an indirect access file
assigned to their jobs simultaneously.
If your current primary file is specified as an lfn on the command, a copy of the associated
permanent file, pfn, becomes the primary file. The subsystem associated with the permanent
file, pfn, becomes the job's current subsystem (refer to section 8).
If an auxiliary device has been previously specified by a PACKNAM command, the system
attempts to find pf^ on the auxiliary device rather than on the family device.
Jf^s, DROPDS COMMAND
The DROPDS command releases the disk space associated with one "or more of your permanent
files, provided that a valid alternate storage copy (on MSE or MSS) exists for each file.
The local file copies of these files (if they are present) will also be returned by this
command•
Format:
DROPDS,Ifn^fti! ,lf n2=pfn2 ,. .. ,lfnn=pfnn/PN=packname,R=r ,NA,WB.
Parameter Description
lfni=pfni Specifies that the permanent file disk space associated with the file
named pfni should be released. The local file named lfni will be
returned at the same time.
If lfni is omitted, the name of the local file is assumed to be pfni.
The full descriptions of the following optional parameters are given at the beginning of
this section.
Parameter Description
PN=packname Specifies the auxiliary device name. Specified if the permanent file
to be released resides on an auxiliary device.
R=r Specifies the device type. Specified if a removable auxiliary device
on a device type other than the installation-defined default is to be
used.
NA Specifies the no abort option. If NA is specified, processing errors
do not abort the job.
W B S p e c i fi e s t h e w a i t - i f - b u s y o p t i o n . T h e j o b w a i t s f o r t h e m o u n t i n g o f
removable auxiliary disk packs.
60459680 G 10-21
![](asset-1a6.png)
MFLINK COMMAND
The MFLINK command optionally transfers a file to or from another mainframe or creates,
purges, or otherwise changes the attributes of a permanent file on another mainframe. You
must be authorized to use the MFLINK command (refer to the LIMITS command).
Format:
MFLINK,Ifn,ST=lid,I=dirfile,DD=dd,EP,RT,PC=c.
Parameter lfn is order-dependent, it must be the first parameter. If you omit lfn, you must
have two consecutive delimiters after MFLINK. The other parameters are order-independent.
Parameter Description
lfn Specifies the optional local file name to be used in any file trans- >^.
fers. The file name must be one to seven alphanumeric characters and /
lfn must reside on disk. If the transfer is from the local host to
the remote host, lfn must be a local file before you enter the MFLINK
command. If the transfer is from the remote host to the local host,
MFLINK either writes over the existing lfn, or if there is no local
file, MFLINK creates a new file with the name lfn. If you omit lfn,
but subsequent directives call for a file transfer, MFLINK uses LFILE
as the default lfn. Some directives, such as CHANGE, PERMIT, and
PURGE (for a NOS remote host) do not require an lfn, because they do
not cause a file transfer. MFLINK rewinds lfn before and after the
t r a n s f e r.
S T = l i d S p e c i fi e s t h e l o g i c a l i d e n t i fi e r ( L I D ) o f t h e r e m o t e h o s t t o w h i c h
MFLINK is to send the directives record. The LID must be a
three-character string defined by your site. You must specify the ST
parameter on the first, and only the first, MFLINK command of a series
of MFLINK commands (an MFLINK session) that are for the same remote
host. The ST=lid specification remains in effect during the entire
session. On subsequent MFLINK commands in the same session, any other
parameters not specified revert to their default values. The
occurrence of the ST=lid parameter on an MFLINK command initiates a
new MFLINK session with the specified remote host. Once you have
entered an MFLINK command with an ST=lid parameter, you can resume
that MFLINK session at any time during your job by entering an MFLINK
command without an ST=lid parameter.
I=dirfile Specifies the local file which contains the directives that the system
sends to the remote host. The file name must be one to seven
alphanumeric characters. The system reads directives from the current
position on the file to the next EOR. If you specify only the keyword
I, file INPUT becomes the directives file. If you omit the I=dirfile
parameter, the system reads directives from the lines immediately
following the MFLINK command. In this case, the directives must all
begin with a prefix character and the system reads directives until it
comes to a line without the prefix character.
10-22 60459680 G
![](asset-1a7.png)
0m^\
Parameter Description
DD=dd Specifies the data format of the file to be transferred. The DD=dd
parameter both describes the character set of lfn on the host where it
currently resides and also specifies the character set lfn is to have
after the transfer.
For file transfers between NOS mainframes and between NOS/BE and NOS
mainframes this parameter is effectively ignored. The file will have
the same format on both mainframes.
The interpretation of the DD=dd parameter depends on the operating
system(s) involved in the file transfer. The following paragraphs
describe how NOS interprets the DD=dd parameter. For its
interpretation by other operating systems, refer to the Remote Host
Facility Usage manual.
On NOS, you can specify the following values for dd:
dd Description
C6 The file contains character data in a 64-character (or less)
subset of the ASCII 128-character set. The character code
of lfn is 6-bit display code and its lines are zero-byte
terminated.
C8 The file contains character data in a larger than
64-character subset of the ASCII 128-character set. The
character code of lfn is the 7-bit ASCII code (right-
justified in 12-bit fields) and its lines are zero-byte
terminated.
US Specifies that the file contains binary data in structured
format with EORs and EOFs. The file is transmitted as a
continuous string of binary data, broken only by EORs and
EOFs as appropriate.
UU Specifies that the file contains binary data without EORs
and EOFs. NOS treats UU as US. If you send a file to a
non-NOS or non-NOS/BE remote host with DD=UU specified and
the file contains EORs or EOFs, the remote host may ignore
them.
0$*\
60459680 G 10-22.1/10-22.2 |
![](asset-1a8.png)
V.
^
^
![](asset-1a9.png)
Parameter
EP
00™^\
RT
/f^S.
PC=c
Description
If the file is character data, you do not need to specify a DD=dd
parameter. The remote host determines the format in which to
read/write the file. If you transfer a binary file to or from a
mainframe with a different word size than the model 170, the mainframe
may add extra bits at EORs or EOFs.
Specifies the error processing that ensues if network problems cause a
loss of the connection during a file transfer. If you omit the
parameter EP, the system retries the request. The EP parameter
inhibits this retry. The system attempts to correct data transmission
errors, regardless of the EP parameter.
Specifies the real-time action the system is to take when network
resources are temporarily unavailable. If you specify RT and some
network resource necessary for you to connect to a remote host is
unavailable, MFLINK aborts without any retries. If you do not specify
RT, after an installation-defined period of time MFLINK retries until
the connection is successful.
Specifies the prefix character for MFLINK directives. The default
prefix character is an asterisk (*). The prefix character can be any
6-bit display code character except a closing parenthesis, a dollar
sign, a period, comma, or a colon. To avoid confusion between
commands and routing directives, use caution in selecting alphabetic
characters for the prefix character.
MFLINK DIRECTIVES
The action taken by MFLINK depends on the directives you specify. You can specify directives
immediately following the MFLINK command if you prefix each directive with the prefix char
acter. The system discards the prefix characters before forwarding the directives to the
remote host. Alternatively, you can specify a directives file with the I=dirfile parameter.
The directives in the directives file do not require the prefix character. The directives
must be commands recognized by the remote host; for example, if the remote host is a NOS/BE
system, your directives must be NOS/BE commands. NOS allows only a small subset of its
commands to be used as MFLINK directives and, further, may require some directives to have a
slightly different form or function from their command counterparts.
This section documents only those MFLINK directives valid for a NOS remote host,
remote hosts, refer to the Remote Host Facility Usage manual. For other
NOS, as a remote host, processes directives of up to 80 characters. A directive longer than
80 characters terminates the processing of the current directives record. A directive can
span more than one line as long as it does not exceed the 80-character limit. You indicate
that the next line is a continuation line by ending the current line with a comma.
60459680 F 10-23
![](asset-1aa.png)
The MFLINK directives fall into the three categories of recovery directives, file transfer
directives, and file alteration directives as follows:
Recovery File Transfer File Alteration
USER
CHARGE
APPEND CHANGE
ATTACH PERMIT
DEFINE PURGE
GET PACKNAM
REPLACE
SAVE
Recovery directives are directives that a host must send a remote host any time you initiate
or resume an MFLINK session. File transfer directives are directives that transfer a file
from one host to another. There can be only one file transfer directive in a given direc
tives re cord.
The directives operate in a manner similar to that of their NOS command counterparts. One
exception is the function of the NA keyword.
The NA option on an MFLINK directive works in a manner very similar to the NA option on NOS
permanent file commands. The main difference is that the system does not suspend MFLINK
processing indefinitely while it waits for a temporary error condition to clear. If APLO
(removable pack option) is set to NONZERO (refer to the description of COMSPFM parameters in
the Installation Handbook) and the temporary error condition persists beyond an
installation-defined timeout period, MFLINK issues a message indicating that the timeout
occurred and then continues. If APLO is set to ZERO, MFLINK will not wait for a pack to be ■/tS|%
mounted but will continue immediately. /
The following directive descriptions show the format of each directive and describe the func
tion of each directive whose function differs from that of its NOS command counterpart.
APPEND Directive
The APPEND directive adds the file specified on the MFLINK command (lfn) to the end of pfn.
Format:
APPEND, pfn/UN=username, PW=pas sword, PN=packname, R=r, NA, WB.
ATTACH Directive
The ATTACH directive retrieves a copy of pfn from the remote host and makes that copy a
temporary file with the name specified on the MFLINK command. No interlock is maintained
between lfn and pfn, except during the file transfer (as if M=READ had been specified).
Format:
ATTACH,pfn/UN=username,PW=password,PN=packname,R=r,NA,RT,WB.
CHANGE Directive
The CHANGE directive operates the same as the NOS command.
Format:
CHANGE,nfn=ofn/PW=password,CT=ct,M=m,BR=br,PR=pr,PN=packname,
R=r,NA,CE,WB,XD=expiredate,XT=expireterm,AC=ac,CP.
10-24 60459680 E
![](asset-1ab.png)
/fipffl^
/j$S5\
y^SpB?5^
CHARGE Directive
The CHARGE directive operates the same as its NOS command counterpart, including the
handling of default charges.
Format:
CHARGE,chargenumber,proj ectnumber.
If the CHARGE directive is required, it must immediately follow the USER directive.
DEFINE Directive
The DEFINE directive creates a direct access file named pfn on the remote host and copies
onto it the file specified by lfn on the MFLINK command. There is no provision to copy over
an existing direct access file; you must purge the existing file. No interlock is
maintained between lfn and pfn, except during the file transfer (as if M=READ had been
specified).
Format:
DEFINE,pfn/PW=password,CT=c,M=m,BR=br,PR=pr,PN=packname,R=r,S=space,NA,WB,
AL=level,XD=expiredate,XT=expireterm,AC=ac.
DROPDS Directive
The DROPDS directive releases the current copy of a permanent file from mass storage when a
back up copy has been saved on a storage device.
Format:
DROPDS,pfn/PN=packname,R=r,NA,WB.
GET Directive
The GET directive retrieves a copy of a permanent file from the remote host and gives it the
name lfn, specified on the MFLINK command.
Format:
GET,pfn/UN=username,PW=password,PN=packname,R=r,NA,WB.
PACKNAM Directive
The PACKNAM directive operates the same as its NOS command counterpart. If you use the
PACKNAM directive, it must precede any file transfer directive in the same directives
record. The PACKNAM directive only applies to the directive record in which it appears.
Format:
PACKNAM,PN=packname,R=r.
PACKNAM,packname,R=r.
60459680 H 10-25
![](asset-1ac.png)
If you are authorized to access auxiliary devices, you can always access files on an
auxiliary device that is already mounted. If you attempt an MFLINK access of a file on an
unmounted auxiliary device, you get a DEVICE UNAVAILABLE message unless your site has
enabled the wait-for-unmounted-device installation option. If this option is present on
more than one mainframe in an RHF network, a deadlock situation is possible. If such a
deadlock occurs, MFLINK would time-out the connection as discussed previously.
PERMIT Directive
The PERMIT directive operates the same as its NOS command counterpart.
Format:
PERMIT,pfn,username=m/PN=packname,R=r,NA,WB,XD=expiredate,XT=expireterm.
PURGE Directive
The PURGE directive operates the same as its NOS command counterpart.
Format:
PURGE,pfn/UN=username,PW=password,PN=packname,R=r,NA,WB.
REPLACE Directive
The REPLACE directive replaces pfn on the remote host with file lfn, as specified on the
MFLINK command.
Format:
REPLACE,pfn/UN=username,PW=password,PN=packname,R=r,NA,WB.
SAVE Directive
The SAVE directive creates an indirect access file named pfn on the remote host and copies
onto it the file specified by lfn on the MFLINK command.
Format:
SAVE,pfn/PW=password,CT=ct,M=m,PN=packname,R=r,NA,WB,AL=level,XD=expiredate,
XT=expireterm,AC=ac.
USER Directive
The USER directive specifies validation information for the remote host. It operates the
same as its NOS command counterpart. The USER directive must be the first directive
associated with an MFLINK command that has ST=lid specified. You do not need to specify
this directive at any other time.
Format:
USER,username,password,familyname.
If the remote host is a NOS Version 2.2 or higher system, the password specified must be the
batch password.
| 10-26 60459680 H
![](asset-1ad.png)
/^T\
/#*s\
INTERACTIVE USE OF MFLINK
When you use MFLINK in an interactive job, the system obtains the directives in one of the
following ways:
• If you specify I=dirfile on the MFLINK command, the system reads the local file
named dirfile. If dirfile is assigned to the terminal, the system prompts the
terminal using the prefix character.
• If you omit the I=dirfile parameter, the system also prompts the terminal using the
prefix character. If the MFLINK command is part of a procedure, the system reads
the lines immediately following the command. If the first line following the
command does not begin with the prefix character, the system prompts the terminal.
When reading from the terminal, the system prompts for directives until you enter an empty
line (only a carriage return) or the prefix character in response to a prompt. The system
then sends the directives (minus the prefix character) to the remote host. The remote host
responds with messages indicating the success or failure of the operations.
Any time you enter an MFLINK command that has the ST=lid specified, the system initiates a
new MFLINK session. If you enter the command without the ST=lid parameter, the system
resumes the session with the remote host currently connected.
Examples: (NOS to NOS)
1. Assume you are at mainframe MFB. To transfer a file from mainframe MFA to MFB and
purge it on MFA, you must enter commands and directives similar to the following:
MFLINK, NE W FILE, ST =* FA.
•USER, XYX, ABC.
*ATTACH,OLDFILE/PN=USER.
*PURGE,OLDFILE/PN=USER.
2. Assume you are on mainframe MFB. To transfer four files from mainframe MFA, enter
commands and directives similar to the following:
MFLINK, FILE 1, ST =M FA, I=DIRECTS.
MFLINK,FILE2,I=DIRECTS.
MFLINK, FILE3,I=DIRECTS.
MFLINK,FILE4,I=DIRECTS.
r60459680 D 10-27
![](asset-1ae.png)
The file DIRECTS has the following contents:
USER,XYZ,ABC.
CHARGE,1234,345N355.
GET,LFN1.
-EOR-
GET,LFN2.
-EOR-
ATTACH,PFN1/PN=USER.
-EOR-
ATTACH,PFNS.
-EOI-
OLD COMMAND
The OLD command retrieves a copy of an indirect access permanent file and makes it the
primary file.
Format:
OLD,Ifn=pfn/UN=username,PW=password,PN=packname,R=r,NA,ND,WB.
Parameter Description
lfn=pfn Specifies the one- to seven-character file name lfn given to the
primary file copy of indirect access permanent file pfn. If lfn= is
omitted, the primary file is named pfn.
The full descriptions of the following optional parameters (except ND) are given at the
beginning of this section.
Parameter Description
UN=username Specifies the user name. Specified if the indirect access permanent
file is in another user's catalog.
PW=password Specifies the file password. Specified if UN=username is specified,
and if the permanent file has a password.
PN=packname Specifies the auxiliary device name. Specified if the permanent file
resides on an auxiliary device.
R=r Specifies the device type. Specified if an auxiliary device of a
device type other than the installation-defined default is to be used.
NA Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
ND Specifies the no drop option. If ND is specified, OLD changes the
former primary file into a local file, but does not return any files.
If ND is omitted, OLD returns all files that do not have checkpoint or
no-auto-drop status.
W B S p e c i fi e s t h e w a i t - i f - b u s y o p t i o n . W B c a u s e s t h e j o b t o w a i t f o r t h e
mounting of disk packs.
/^^Sk
| 1 0 - 2 8 60459680 G
![](asset-1af.png)
/4iffl*N,
If an auxiliary device has been previously specified by a PACKNAM command, the system
attempts to find the permanent file, pfn, on the auxiliary device rather than on the family
device.
If you do not specify the ND parameter, the system releases all files assigned to the job,
except those with checkpoint or no-auto-drop status. Certain system files (for example,
ZZZZZCO, ZZZZZC1, ZZZZZC2, and ZZZZZLD) always have no-auto-drop status. You can give any
local file this status by using the SETFS command. A copy of the indirect access permanent
file named on the OLD command becomes the primary file. The primary file is positioned at
its BOI.
The primary file is rewound before every job step. Therefore, the file positioning commands
have no effect on the primary file. Also, when two commands are issued to write on the
primary file, the second writes over the data written by the first because the primary file
is rewound between commands.
PACKNAM COMMAND
The PACKNAM command directs subsequent permanent file requests to the specified auxiliary
device.
Format:
PACKNAM,PN=packname,R=r.
PACKNAM,packname,R=r.
or
PACKNAM.
Parameter
PN=packname
Description
Specifies the one- to seven-character identifier of the
auxiliary device to be accessed in subsequent permanent file
commands.
R=r Specifies the device type of the auxiliary device specified
by packnam.
You specify this parameter if you want to use a removable
auxiliary device whose device type differs from the
installation-defined default.
If you do not specify this parameter for a nondefault type
pack, you must specify this parameter on each subsequent
permanent file command.
A full description of this parameter appears at the beginning
of this section.
60459680 D 10-29
![](asset-1b0.png)
PACKNAM allows you to omit the PN=packname parameter on command requests for files that
reside on the specified auxiliary device. However, to request permanent files on another
auxiliary device, you must specify the PN=packname parameter on the file request or enter
another PACKNAM command before the request (you must also specify the R=r parameter if the
device type is different). Refer to Mass Storage File Residence in section 2 for
information concerning auxiliary permanent file devices.
You can access permanent files residing on the family system devices while the PACKNAM
request is in effect by specifying PN=0 on permanent file commands. To clear the effect of
a PACKNAM command, include a PACKNAM command in either of the following formats.
PACKNAM.
or
PACKNAM, PN=0. /^
PERMIT COMMAND
The PERMIT command explicitly permits another user to access a private file in your
permanent file catalog. The PERMIT command can also change the mode in which another user
can access a semiprivate file.
Format:
PERMIT,pfn,usernamei=mi ,username2=m2,... ,usernamen=mn/PN=packname,R=r ,NA,WB,
XD=expiredate,XT=expireterm.
Parameter Description
pfn Name of the private or semiprivate file for which access permission is
granted.
usernamei=mi Specifies that user name usernamei is granted the access permis
sions indicated by access mode mi. If mi is omitted, the read
access mode is assumed. If mi is NULL, the user is explicitly /*sv
denied permission to access the file. For the available access modes, )
refer to DEFINE Command or SAVE Command in this section.
The full descriptions of the following optional parameters are given at the beginning of
this section.
Parameter Description
PN=packname Auxiliary device name. Specified if the permanent file resides on an
auxiliary device.
R=r Device type. Specified if a removable auxiliary device on a device
type other than the installation-defined default is to be used.
j * ^ ^ ^ \
10-30 60459680 D
![](asset-1b1.png)
NA
WB
Parameter Description
No abort option. If NA is specified, processing errors do not
terminate the job.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs.
XD=expiredate Specifies the expiration date for the file permit. The value
expiredate must be a six-digit string of the form yymmdd; where yy,
mm, and dd are two-digit year, month, and day designators,
respectively.
XT =e xpi ret erm Spec ifie s the lif e of t he file perm it in day s. If you s pec ify 0, t he
file permit expires immediately. If you specify 4095 or *, the file
permit does not expire.
/fSp»y
PURGALL COMMAND
The PURGALL command purges all permanent files in your catalog that satisfy the criteria
specified by the parameters.
Format:
PURGAIA,TY=ty,CT=ct,AD=ad,MD=md,CD=cd,AF,TM=tm,PN=dn,PN=packname,R=r,NA,WB.
Parameter
TY=ty
CT=ct
AD=ad
MD=md
Description
Specifies the file type to be purged.
ty Action
I or INDIR Purges all indirect access files.
D or DIRECT Purges all direct access files.
A or ALL Purges all files.
If this parameter is omitted, but other parameters are specified, the
system assumes ty is ALL. To purge all files if no other parameters
are specified, you must specify TY=A.
Specifies the permit category to be purged. Entries are P, PR, or
PRIVATE for private; S or SPRIV for semiprivate; and PU or PUBLIC for
public.
Specifies the last access date; its format is yymmdd. All files last
accessed before this date are purged, unless the AF parameter is
specified.
Specifies the last modification date; its format Is yymmdd. All files
last modified before this date are purged, unless the AF parameter is
specified.
60459680 D 10-31 |
![](asset-1b2.png)
y*S!\
Parameter
CD=cd
AF
TM=tm
DN=dn
Description
Spec ifi es th e cre ati on date ; its for mat i s yym mdd . A ll fil es cr eat ed
before this date are purged, unless the AF parameter is specified.
Specifies that files accessed after the date specified by the AD=ad
parameter, modified after the date specified by the MD=md parameter,
or created after the date specified by the CD=cd parameter are purged.
Specifies the time of day on the date specified by the AD, MD, or CD
parameter; its format is hhmmss.
Specifies the device number assigned to a device during system
initialization. Only files on that device are purged.
PN=packname Specifies the name of the auxiliary device on which the files to be
purged reside. The PN parameter cannot be specified if a device
number is specified (DN=dn).
R=r
NA
WB
Specifies the type of auxiliary device on which the files to be purged
reside. The R parameter cannot be specified if a device number is
specified (DN=dn).
Specifies the no abort option. If the specified auxiliary device is
not available, the job is suspended until it becomes available.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs.
To purge all files in your catalog, you must enter:
PURGALL,TY=A.
AF, CT, DN, NA, R, TY, TM, and one date (either AD, MD, or CD) can be entered on a single
PURGALL command.
PURGE COMMAND
The PURGE command names files to be removed from the permanent file device.
Format:
PURGE, pfnj, pf n2,. • ♦, pfnn/UN=username, PW=password, PN=packname, R=r ,NA, WB.
Parameter Description
pfnA Specifies the name of a permanent file to be purged. If no file is
named, and if a permanent file exists that has the same name as the
primary file, that permanent file is purged; the primary file remains
assigned to the job.
y^^^jV
| 10-32 60459680 D
![](asset-1b3.png)
The full descriptions of the following optional parameters are given at the beginning of
this section.
Parameter Description
UN=username Specifies the user name. Specified if the file(s) to be purged is in
another user's catalog. To purge a file, you must have write
permission for that file.
PW=password Specifies the file password. Specified if UN=username is specified,
and if the permanent file to be purged has a password.
PN=packname Specifies the auxiliary device name. Specified if the permanent file
resides on an auxiliary device.
R=r Specifies the device type. Specified if a removable auxiliary device
on a device type other than the installation-defined default is to be
used.
NA
WB
Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs and busy files.
^^ When a PURGE command is issued for any direct access file, the file is purged and the
0^ p erm ane nt fi le c ata log i s alt ere d acc ord ing ly. How eve r, if t he d ire ct a cce ss fi le is
v a tta c hed t o a j o b, it r e main s a ttac h ed to t h e j ob u n til y o u retu r n i t.
RECLAIM COMMAND
The RECLAIM command performs a number of functions related to the transfer of NOS files
between your job and a dump file. The dump file can be a magnetic tape or a mass storage
(disk) file. Using RECLAIM you can selectively dump local or permanent files, retrieve
files from a dump file, and list information about files previously dumped to tape or mass
01°^ storage.
RECLAIM provides you with an easy way of making backup copies of local files or of direct
and indirect access permanent files. It also gives you greater control over the size of
your permanent file disk space. RECLAIM can be entered from a batch or interactive job.
Dumped files can be reloaded as local or permanent files. Reloaded permanent files have the
same permissions, modes, permit categories, and so forth that they had when dumped. Note,
however, that file history information for reloaded files (that is, file creation date, last
date modified, last date accessed, etc.) is set to the date and time of loading. Files can
be reloaded from tape by the file owner or by an alternate user.
Information about dumped files (such as file name, dump date, tape VSN, dump number, and so
forth) can be stored in a dump database. This database is maintained as a direct access
file in your permanent file catalog. RECLAIM automatically creates a dump database when you
enter a DUMP directive unless you specify that you do not want a database for the dump
60459680 D 10-33
![](asset-1b4.png)
/•*^\
(using the DB=0 parameter). If you do not specify a name for the database, RECLAIM uses the
default name RECLDB. To get information on individual files in the database, enter a
RECLAIM command with the LIST directive.
Multiple users can share a dump database. For example, alternate users can access a
database in your catalog by entering a RECLAIM command specifying your database file name
(on the DB parameter) and your user name (on the UN parameter). As with any other permanent
file, alternate users must have WRITE permission to access and use your database file.
MAGNETIC TAPES
As previously mentioned, you can use RECLAIM to dump or retrieve files to or from magnetic
t a p e s a s w e l l a s m a s s s t o r a g e m e d i a . Yo u s h o u l d b e a w a r e o f t h e f o l l o w i n g s p e c i a l r u l e s ^ ^ ^
that apply when using tapes with RECLAIM: •*™s%
• You do not need to enter a REQUEST command for RECLAIM dump tapes. RECLAIM issues
its own REQUEST command internally when you enter a COMPACT, DUMP, LOAD, or COPY
directive (RECLAIM directives are described below). RECLAIM uses the default
parameter values for the REQUEST command.
NOTE
Since RECLAIM issues the REQUEST command
internally, you must be prepared to wait for
the tape mount if you enter a COMPACT, DUMP,
LOAD, or COPY directive from an interactive
job. Other alternatives are to submit the
RECLAIM command from a batch job or to
detach your interactive job using the Detach
(ctD) command.
• RECLAIM dump tapes must be labeled; unlabeled tapes are not permissible.
• If you enter a LOAD, COPY, or LIST directive for a tape that is not already defined
to the RECLAIM database, RECLAIM reads the entire tape and adds all files on the
tape, or all files matching the specified user index if the UI processing option is
specified, to the database. This feature lets you add the entire contents of a tape
to the database without having to name each file individually.
• The tape processing options listed under Processing Options in section 12 are valid
for RECLAIM tapes. Processing options are specified with the PO option.
• The permanent file tapes are written by the RECLAIM utility in a format compatible
with both PFDUMP and PFLOAD. The NOS 2 Analysis Handbook describes these permanent
file utilities.
/-as^\
10-34 60459680 H
![](asset-1b5.png)
COMMAND FORMAT
The parameters of the RECLAIM command are order-independent,
are appended to the end of the command. The directives and the options
NOTE
For sites using the Tape Management System
(TM S) , th ere are a dd it io na l directive
options available on the RECLAIM command
which are not described in this manual. For
a description of the RECLAIM command under
TMS, refer to the NOS 2 Tape Management
System (TMS) User Reference Manual.
Format;
RECLAIM,p1,p2,...,pn./directive1,options1/directive2,
options2/.../directiven,optionsn.
00®\
Parameter
DB=pfn
I = l f n 1
L=lfn2
NH
PW=password
UN=username
NA
NV
Description
Specifies the name of the direct access file that contains the RECLAIM
database. The default file name for pfn is RECLDB. If a value of 0
is entered for pfn, no database is created or maintained.
Do not attach the database file before you call RECLAIM; RECLAIM
attaches the file for you.
Specifies the name of the local file containing the RECLAIM input
directives to be processed. The default file name for lfn1 Is INPUT.
Specifies the name of the local file to receive output listing. The
default file name for lfn2 is OUTPUT.
Inhibits RECLAIM from printing a header on file lfn2.
Specifies the file password for the database file; applicable only if
the database file resides in an alternate user catalog.
Specifies the user name of the database file owner; applicable only if
the database file resides in an alternate user catalog. You must have
WRITE permission to access files under an alternate user name.
No abort option; inhibits RECLAIM abort in case of a program error.
Specifies that a dump is to be written at end-of-information (EOI),
regardless of what precedes the EOI. If this parameter is omitted,
RECLAIM will not write a dump beginning at EOI unless at least one
valid RECLAIM dump precedes the EOI.
60459680 H 10-35
![](asset-1b6.png)
Parameter
directivei
optionsi
Description
Specifies that the RECLAIM command contains input directives following
the terminator. If the Z parameter is specified, the I parameter is
ignored. Use of the Z parameter eliminates the need for an input file
(lfnj) when only a few directives are required.
Specifies how RECLAIM is to manipulate files that meet the criteria
set forth in the directive options. (RECLAIM directives and options
are described below.)
Specifies a file characteristic or attribute RECLAIM is to use in
selecting the file or files to be processed. (RECLAIM directives and
options are described below.) Use a comma to separate individual
options.
RECLAIM directives define the operation to be performed on a specified file or files. All
directives except END can have one or more associated options. A comma is used as the
separator between a directive and its associated options.
When you enter a RECLAIM command with the Z parameter, you type in the directives following
the command terminator. The first character following the terminator must be the separator
character used to separate individual directives. The separator character can be any
character that does not appear within the directives. (We use the / character in the
examples in this section.)
Following are descriptions of the RECLAIM directives. The description of the options for
the directives immediately follows the description of the directives.
Directive
COMPACT
Description
Rewrites a dump file using only the active files from the database.
All files logically deleted (using the DELETE directive) from your
database are physically deleted from the dump file and the database.
Options may also be specified which apply additional file selection
criteria. Files which do not meet these additional criteria are also
physically deleted. The active files rewritten by the COMPACT
directive are consolidated into a single dump before being rewritten;
that is, the new dump file contains only one dump. The database is
updated to remove all inactive entries and update the dumpfile number
for the remaining entries. COMPACT cannot be used on dump files that
have no database file.
You must specify one of the following options to indicate where the
dump file to be created by COMPACT is to be stored:
CF=clfn
CN=cpfn
CT=vsn
OV
Either or both of the CF=clfn and CN=cpfn options must be specified in
conjunction with the DT=MS option if a new mass storage file is to
receive the dump.
The CT=vsn option must be specified if a new tape is to receive the
dump. If you intend to enter a COMPACT directive specifying a new
tape, you must issue a RESOURC command to allow RECLAIM to request the
two tapes at once.
/^^8\
| 10-36 60459680 H
![](asset-1b7.png)
Directive
COPY
Description
You must specify the OV option if the dump is to be rewritten on the
original tape or file. To rewrite a dump tape, the compacted dump is
first written to a disk scratch file, then copied to the original file,
If you know or expect that a dump will require multiple reels, you
must enter a VSN command before entering RECLAIM. The VSN command
should specify as many VSNs as necessary and should associate the VSNs
with the local file name specified by the CF option. If no CF option
is specified, the default local file name NTAPE is used.
Creates local file copies of all dumped files that meet the criteria
specified by the COPY directive options. (The COPY directive is the
same as the LOAD directive except that the LOAD directive creates
permanent files from dumped files.) The copied files are created
using their original permanent file names unless they are explicitly
renamed.
The COPY directive performs its own tape requests internally. If a
copy is initiated for several files resident on a single tape, that
tape is only requested once. If the copy specifies files on multiple
tapes, multiple tape requests are initiated.
The COPY directive can be used to read files from a tape that is not
listed in the RECLAIM database. When used in this way, RECLAIM reads
all files from the tape (regardless of how many files are specified by
the COPY directive options) and adds all files to the RECLAIM database,
The latest (most recently dumped) version of each file is copied
unless you specify other characteristics. The following are examples
of a COPY directive:
RECLAIM,Z./COPY,PF=ALPHA/COPY,PF=BETA/COPY,PF=SIGMA
DELETE
RECLAIM,Z./COPY,PF=*/ALPHA,BETA,SIGMA
Either of the above commands copies the latest (most recently dumped)
versions of files ALPHA, BETA, and SIGMA and makes them local files.
Di sa ble s all fil es In you r dat aba se tha t mee t the cri te ria spec ifi ed
by the DELETE directive options. Deleted files are not physically
deleted from the database and can be restored to active status using
the RESET directive. Use the LIST directive with the DE option to
list deleted files. You can use DELETE to temporarily disable
selected files, thus allowing you to load all files except those
disabled. All files disabled by DELETE are physically removed from
the dump file if a COMPACT directive is entered before the disabled
files are reactivated (using RESET). The following is an example of «
DELETE directive:
RECLAIM,Z./DELETE,DD=851204
The above example instructs RECLAIM to disable all files dumped on the
date 12/4/85.
60459680 H 10-37 |
![](asset-1b8.png)
r ^ ^ g K
Directive Description
DUMP Dumps to tape or mass storage all permanent files that meet the
criteria specified by the DUMP directive options. Information that
RECLAIM requires to perform future reloads from the dump file is
stored in a database file within the specified user catalog. If the
specified database file does not exist, RECLAIM creates it. You can
inhibit the creation or use of a database file by specifying the DB=0
parameter.
Files are dumped in the order they appear in your permanent file
catalogue unless you specify the PF or FN option. Files are then
dumped in the order they are listed for PF or FN. If a file is listed
more than once for PF or FN, multiple copies are dumped, in the
specified order.
Files dumped are written to the dump file at EOI unless EI=NO is
specified. If RECLAIM determines that a dump file is empty or does
not contain a RECLAIM dump, it sends the following message to the
dayfile and the terminal:
UNKNOWN DUMP FILE WILL BE REWRITTEN.
If the DUMP directive was entered interactively, RECLAIM issues the
prompt:
I S T H I S O K ( Y E S O R N O ) ? " ^
If you enter YES, the dump proceeds normally. For a NO response,
RECLAIM ignores the directive and prompts for the next one. In a
noninteractive job, RECLAIM proceeds with the dump.
The following is an example of a RECLAIM DUMP directive:
RECLAIM,Z./DUMP,TY=D,TN=001442
This example Instructs RECLAIM to dump all direct access permanent
files in your catalog to a magnetic tape with the VSN of 001442. If a
database named RECLDB does not currently exist, RECLAIM creates it.
If you know or expect that a dump will require multiple reels, you
must enter a VSN command before entering the RECLAIM command. The VSN
command should specify as many VSNs as necessary and should associate
the VSNs with the local file name specified by the DF option. The
default name is TAPE. For example:
VSN,TAPE=001442/001501/001995.
RECLAIM,Z./DUMP,TN=001442,TY=D
The above example duplicates the previous example, but allows for a
multi-reel dump.
| 10-38 60459680 H
y^S^N.
![](asset-1b9.png)
Directive
END
0p^m^^ LIST
LOAD
Description
Ends the current RECLAIM session. At an interactive terminal, a blank
line followed by a carriage return is equivalent to an END. In a
directive file, an EOR has the same effect as an END directive.
You can use the F tape processing option (refer to Processing Options
in section 12) to instruct RECLAIM to unload a tape when the END
directive is entered. To do this, enter the following SET directive
before you initiate any operation that would cause a tape to be
mounted (such as a COPY, DUMP, or LOAD):
SET,PO=F
Lists RECLAIM database information about all dumped files that meet
the criteria specified by the accompanying directive options. Files
are listed in alphabetical order except for dump files without a
database. Dump files with no database are listed in sequential order.
The LIST directive can be used to list files on a tape that is not
listed in the RECLAIM database. When used in this way, RECLAIM adds
all files on the tape to the RECLAIM database, regardless of how many
files are specified by the LIST directive options.
Loads into your permanent file catalog all of the files that meet the
criteria specified by the LOAD directive options. (The LOAD directive
is the same as the COPY directive except that the COPY directive
creates only local files.) The latest (most recently dumped) version
of each file is loaded unless you specify other characteristics. If a
file name specified in a LOAD directive already exists in the catalog,
the file will not be loaded unless the RP or RP=Y option is also
specified.
The LOAD directive can be used to load files from a tape that is not
listed in the RECLAIM database. When used in this way, RECLAIM loads
all files from the tape (regardless of how many files are specified by
the LOAD directive options) and adds all files to the RECLAIM database.
The LOAD directive performs its own tape requests internally. If a
load is initiated for several files resident on a single tape, that
tape is only requested once. If the load specifies files on multiple
tapes, multiple tape requests are initiated. Following are examples
of the LOAD directive:
RECLAIM,Z./LOAD,PF=MYFILE
The above LOAD directive loads into your catalog the most recently
dumped version of MYFILE.
RECLAIM,Z./LOAD,DD=840112,NF=595
The above LOAD directive loads up to 595 files dumped on the date
1/12/84.
60459680 H 10-38.1 |
![](asset-1ba.png)
Directive Description
RECLAIM,Z./LOAD,PF=ALPHA,NN=BETA,MD=831114
or
RECLAIM,Z./LOAD,PF=*,MD=831114/BETA=ALPHA
Either of the previous LOAD directives loads the latest version of
file ALPHA with a modification date of 11/14/83. File ALPHA is loaded
into your catalog as file BETA. If a permanent file called BETA
already exists in your catalog, the file is not loaded. If a
permanent file named ALPHA exists in the catalog, it does not affect,
and is not affected by, this operation.
QUIT Equivalent to END.
REMOVE Permanently removes a tape volume serial number (VSN) from the
database. This purges from the database all entries for the specified
tape.'
RESET Reactivates all files previously disabled by the DELETE directive that
meet the criteria specified by the RESET directive options.
SET Redefines the RECLAIM defaults for any directive options. Typically,
this directive is used during a long RECLAIM session to establish
criteria for subsequent processing. If a SET directive is encountered z*8^
without an accompanying option, it has no effect on current defaults.
I 10-38.2 60459680 H
![](asset-1bb.png)
The options which can be associated with RECLAIM directives are described below.
Option
CF=clfn
CN=cpfn
CT=vsn
D=den
DA=yymmdd
DB=yymmdd
Description
Specifies the name of the local file to receive the compacted dump.
If clfn is omitted, the local file name is the name specified for the
CN parameter. If the CN parameter is omitted, the default name NTAPE
is used for clfn. This option is used with COMPACT.
Specifies the permanent file to receive the compacted dump if you do
not want to overwrite the original dump file. (Use the OV option to
overwrite the original dump file.) The CN option allows you to
specify different names for the local and permanent file copies of the
dump file. This option does not create, save, or replace the
permanent file; these operations are the user's responsibility. This
option is used with COMPACT.
Specifies the VSN of the tape to which the compacted dump is to be
written. The CT option is used with COMPACT.
Specifies tape density; values that can be specified for den are as
follows:
den
HI
HY
HD
PE
GE
Description
556 cpi; 7-track tapes
800 cpi; 7-track tapes
800 cpi; 9-track tapes
1600 cpi; 9-track tapes
6250 cpi; 9-track tapes
The D option is used with COMPACT and DUMP.
Instructs RECLAIM to process only those files dumped after a specified
date. DA may be used in conjunction with DB to specify a date range.
The DA option is used with COMPACT, COPY, DELETE, LIST, LOAD and RESET.
Instructs RECLAIM to process only those files dumped before a
specified date. DB may be used in conjunction with DA to specify a
date range. The DB option is used with COMPACT, COPY, DELETE, LIST,
LOAD and RESET.
DD=yymmdd Instructs RECLAIM to process only those files dumped on a specified
date. The DD option is used with COMPACT, COPY, DELETE, LIST, LOAD
and RESET.
DE Instructs RECLAIM to process only those files that have been disabled
by DELETE. If this option is omitted, only undeleted files are
processed. The DE option is used with COMPACT, COPY, LIST, LOAD and
RESET.
DF=dlfn Specifies the name of the local file copy of a dump file,
name for dlfn is TAPE. The DF option is used with DUMP.
The default
60459680 G 10-39
![](asset-1bc.png)
Option
DN=dpfn
DT=dtype
Description
Specifies the file to or from which files are to be processed. Only
files on this dump file that meet other specified selection criteria
are selected. The DN option is logically equivalent to and
interchangeable with the TN option except if a DT, MT, or NT option is
not specified. In this case, DN implies a mass storage dump file
while TN implies a tape dump file (therefore, TN causes RECLAIM to
issue an internal REQUEST command, whereas DN does not). The DN
option is used with COMPACT, COPY, DELETE, DUMP, LIST, LOAD, and RESET,
If the DN option (or DT=MS) is used for a DUMP operation, RECLAIM does
not make the mass storage dump file permanent. If you wish to make
the dump file permanent, you may do so. However, the dump file must
be local before you can use it with RECLAIM.
Specifies the type of dump file to be created,
dtype are:
Possible values for
dtype
MS
MT
NT
Significance
The dump is placed on a mass storage (disk) file.
The dump is placed on 7-track magnetic tape. (Same
as MT option.)
The dump is placed on 9-track magnetic tape. (Same
as NT option.)
EI=NO
EX=option
The DT option is used with COMPACT and DUMP.
Instructs RECLAIM to write dumped files at the beginning of the dump
file, thus destroying any existing information on the dump file. If
this option is omitted, files to be dumped are written to the dump
file at end-of-information. The EI option is used with DUMP.
Specifies the use of exception processing for RECLAIM options. Values
that can be specified for option are Y or N. Y indicates that
exception processing will be used; that is, only files that fail one
or more selection criteria are .processed. N indicates that normal
processing is used; that is, only files that meet all selection
criteria are processed. The EX option is used with COMPACT, COPY,
DELETE, DUMP, LIST, LOAD, and RESET.
F=format Specifies any valid NOS tape format,
COMPACT or DUMP.
The F option is used with
FI=nn Specifies the dump number (1 to 63) to which the dump file is to be
positioned. A dump is the set of user files dumped to a file by a
single DUMP or COMPACT directive.
The FI option can be used in conjunction with the RC option to
position the tape or file .pointer to a particular file within a
specified dump. (The FI value associated with a particular file is
listed in the FI column of the RECLAIM output listing.) The FI option
is used with COPY and LOAD.
10-40 60459680 G
![](asset-1bd.png)
Opti on
FN=filename
FT
GT=length
LT=length
LV
MA=yymmdd
MB=yymmdd
MD=yymmdd
MT
Description
Processes files in the same manner as the PF option with one
exception: When used with a DUMP directive, it first checks to see if
a named file exists as a local file. If so, the local file is dumped.
The TY option can be used with FN to specify whether named local files
are to be dumped as direct access or indirect access files. The
default is direct access.
The FN option is used with COMPACT, COPY, DELETE, DUMP, LIST, LOAD,
and RESET. For all directives except DUMP, the FN and PF options are
interchangeable.
Foreign tape. Refer to the NOS 2 Tape Management System (TMS) User
Reference Manual for a detailed description.
Instructs RECLAIM to process only those files that have a length in
PRUs greater than the length specified. GT may be used in conjunction
with LT to specify a size range. The GT option is used with COMPACT,
COPY, DELETE, DUMP, LIST, LOAD and RESET.
Instructs RECLAIM to process only those files that have a length in
PRUs less than the length specified. LT may be used in conjunction
with GT to specify a size range. The LT option is used with COMPACT,
COPY, DELETE, DUMP, LIST, LOAD and RESET.
Specifies that the most current version of the specified file is to be
processed. This is the default for the COPY and LOAD directives. The
LV option is used with COMPACT, COPY, DELETE, LIST, LOAD and RESET.
Instructs RECLAIM to process only those files modified after a
specified date. MA may be used in conjunction with MB to specify a
date range. The MA option is used with COMPACT, COPY, DELETE, DUMP,
LIST, LOAD and RESET.
Instructs RECLAIM to process only those files modified before a
specified date. MB may be used in conjunction with MA to specify a
date range. The MB option is used with COMPACT, COPY, DELETE, DUMP,
LIST, LOAD and RESET.
Instructs RECLAIM to process only those files modified on a specified
date. The MD option is used with COMPACT, COPY, DELETE, DUMP, LIST,
LOAD and RESET.
Specifies the use of a 7-track tape drive.
DUMP.
The MT option is used with
NF=num
NN=pfn
Specifies the maximum number of files to be processed. If the NF
option is omitted, there is no limit on the number of files processed,
except for the DUMP directive. The limit for DUMP is 4095 files. The
NF option is used with COMPACT, COPY, DELETE, DUMP, LIST, LOAD and
RESET.
Specifies a new file name for the file named by the PF option. The NN
option is used with COPY, DUMP and LOAD.
60459680 H 10-41
![](asset-1be.png)
Option
NT
OV
PF=pfn
PO=plp2...pn
PW=password
RC=nnnn
Description
Specifies the use of a 9-track tape drive. The NT option is used with
DUMP.
Specifies that a compacted dump is to be written over the old dump
tape. The OV option is used with COMPACT.
Specifies the name of the permanent file or files to be processed by
RECLAIM. If only one file is to be processed, pfn is any valid NOS
file name. If PF and FN are both omitted, the files to be processed
are determined by the other options which have been specified. If
multiple files are to be selected by name, specify an asterisk (*) for
pfn.
When PF=* is specified, a file name list containing up to 999 file
names may be entered. A line of file names ending with a comma
indicates that the file name list is continued on the next line. For
interactive requests, RECLAIM prompts you to enter the file names with
the message:
ENTER FILE NAMES.
The file name list contains one entry for each file to be processed.
Each entry consists simply of the name of the file to be processed,
unless the file is to be renamed. If the file is to be renamed, the
entry is in the format, newname=oldname. Entries are separated by
commas. An entry not followed by a separator indicates the end of the
list. A comma at end of line indicates that another line follows.
Following is an example of a file name list:
RECLAIM,Z./DUMP,TN=MYVSN,PF=*/ALPHA,GAMMA=BETA
This command will cause RECLAIM to dump files ALPHA and BETA. The
files will be identified in the dump and in the data base as ALPHA and
GAMMA. The PF option is used with COMPACT, COPY, DELETE, DUMP, LIST,
LOAD and RESET.
Specifies general tape processing options for a dump tape. Refer to
Processing Options in section 12 for a description of dump tape
processing options. The PO option is used with COMPACT, COPY, LIST,
LOAD, DUMP, and SET. PO=UR is the default for the COPY, LIST, and
LOAD directives. PO=UW is the default for the COMPACT and DUMP
directives.
Password. Refer to the NOS 2 Tape Management System (TMS) User
Reference Manual for a detailed description.
Specifies the dump record number (1 to 4095) within a dump that
indicates where the dump file is to be positioned. The RC option is
used in conjunction with the FI option to specify the location of a
file within a dump. (The RC value associated with a particular file
is listed in the REC column of the RECLAIM listable output.) The RC
option is used with COPY and LOAD.
10-42 60459680 H
![](asset-1bf.png)
Option
RP=option
00^\
TN=vsn
TO=username
TY=type
UI=user index
UN=username
Description
Specifies that a file is to be loaded or copied from a dump file even
if a local or permanent file by the same name already exists.
Possible values for option are Y or N.
When used with the LOAD directive, specifying RP or RP=Y indicates
that an existing permanent file will be replaced by a file loaded from
a dump. Specifying RP=N or omitting the RP option indicates that an
existing permanent file will not be replaced by a loaded file.
When used with the COPY directive, specifying RP or RP=Y indicates
that a local file will be overwritten by a file copied from a dump.
If RP=N is specified, or if the RP option is omitted, RECLAIM returns
the existing local file before copying the file from DUMP.
The RP option is used with COPY and LOAD.
Specifies the VSN of the tape to or from which files are to be
processed (VSN of the first reel for a multi-reel dump). Only files
on this tape which also meet any other specified selection criteria
are processed. This option is logically equivalent to and
interchangeable with the DN option except if a DT, MT, or NT option is
not specified. In this case, DN implies a mass storage dump file
while TN implies a tape dump file (therefore, TN causes RECLAIM to
issue an internal REQUEST command, whereas DN does not). The TN
option is used with COMPACT, COPY, DELETE, DUMP, LIST, LOAD, RESET and
SET.
Username. Refer to the NOS 2 Tape Management System (TMS) User
Reference Manual for a detailed description.
Specifies the permanent file type to be processed. Values that can be
specified for the TY option are: D (direct access) and I (indirect
access). If this option is omitted, both file types are eligible for
processing. The TY option is used with COMPACT, COPY, DELETE, LIST,
LOAD and RESET.
Instructs RECLAIM to process only files for the specified user index
when the COPY, LIST, or LOAD directive is used to process a dump tape
or file not on the database, or when no database is being used (DB=0).
If this option is either omitted or specified as UI=0, the user index
of files on the dump tape or file being processed will be ignored.
Instructs RECLAIM to process files only for the specified user name on
the RECLAIM database, when files are shared among multiple users. If
this option is omitted, processing is performed only on the calling
user's dumped files. Files for all users will be processed if UN=0 is
specified. The UN option is used with COMPACT, COPY, DELETE, LIST,
LOAD and RESET. If the UN option specifies a user name not originally
in the RECLAIM database, RECLAIM loads all files (LOAD directive) or
li st s in forma ti on a bout a ll d umped fil es (L IST dire ct ive ) on a fil e
set specified by the TN or DN options. Loaded files are recorded in
the database under the user name specified by the UN option.
c60459680 H 10-43
![](asset-1c0.png)
RECLAIM OUTPUT
All RECLAIM directives except END, QUIT and SET generate output listings in the following
format:
RECLAIM Vvvv OP=ddddddd UN=username yy/mm/dd. hh.mm.ss. PAGE nn
PFN TYPE LAST MOD DUMP DATE LENGTH USERNAME TAPE FI REC
pfname ty yy/mm/dd yy/mm/dd
pfname ty yy/mm/dd yy/mm/dd
len dmpuser dumpid fi re
len dmpuser dumpid fi re
n FILES PROCESSED
where:
vvv
ddddddd
username
nn
pfname
ty
len
dmpuser
dumpid
fi
Current version of RECLAIM.
Name of the RECLAIM directive being processed.
User name of the calling user.
Current page number (not displayed for interactive users).
Name of the permanent file being processed.
File type (I for indirect access or D for direct access).
Length in PRUs of file pfname when dumped.
The user name under which file pfname was originally dumped.
VSN of the tape or name of dump file containing file pfname (VSN of
the first reel for a multi-reel dump).
The dump number on dumpid containing file pfname.
The record number on dump fi containing file pfname.
Entering a RECLAIM command with the NH parameter specified suppresses printing of the
heading and the n FILES PROCESSED line; only the file information is printed.
Example 1
The following RECLAIM command lists a portion of dump file database MYDB, and terminates the
RECLAIM session.
/recLaim,db=mydb,z./List,tn=:01/end
RECLAIM V4.2 0P=LIST UN=0MEN 83/12/14. 13.03.34.
PFN TYPE LAST MOD DUMP DATE LENGTH USERNAME TAPE FI REC
DEMA I 83/11/18 83/12/13
DEMB I 83/11/18 83/12/13
187
27
OMEN
OMEN
01
01
2 FILES PROCESSED.
RECLAIM COMPLETE.
| 1 0 -44 60459680 H
![](asset-1c1.png)
Example 2
The following example shows a RECLAIM session in which the system prompts for directives,
This RECLAIM command dumps two files to tape, then lists the affected portion of MYDB.
/reclaim,db=mydb,nh
ENTER DIRECTIVE.
? dump,tn=01,pf=*
ENTER FILE NAMES.
? demc,demd=kdefs
DEMD I 83/10/06 83/12/14 92 OMEN 01
D E M C I 8 3 / 11 / 1 8 8 3 / 1 2 / 1 4 11 5 O M E N 0 1
ENTER DIRECTIVE.
? List,tn=01
DEMA I 83/11/18 83/12/13 187 OMEN 01
DEMB I 83/11/18 83/12/13 27 OMEN 01
D E M C I 8 3 / 11 / 1 8 8 3 / 1 2 / 1 4 11 5 O M E N 0 1
DEMD I 83/10/06 83/12/14 92 OMEN 01
ENTER DIRECTIVE.
?end
RECLAIM COMPLETE.
/
60459680 H 10-44.1/10-44.2 g
![](asset-1c2.png)
![](asset-1c3.png)
/^*V
REPLACE COMMAND
The REPLACE command can purge an indirect access permanent file and replace it with a copy
of a local file on mass storage. It can also save a copy of a local file on mass storage as
a new indirect access permanent file.
Format:
REPLACE,Ifni=pfnA,Ifn2=pfn2,...,lfnn=pfnn/UN=username,PW=password,M=m,
PN=packname,R=r,NA,WB.
Parameter Description
lfni=pfni Specifies that a copy of local file lfni becomes an indirect access
permanent file named pfnA (one- to seven-character name). If an
JPN indirect access file named pfni already exists, it is replaced.
If lfni is omitted, the name of the local file is assumed to be
pfni» If no files are named, a copy of the primary file becomes an
indirect access permanent file, replacing any existing indirect access
permanent file by that name.
The full descriptions of the following optional parameters are given at the beginning of
this section.
Parameter Description
f UN=username Specifies the user name. Specified if the file to be replaced is in
another user's catalog. To replace another user's file, you must have
write permission and be validated to create indirect access permanent
files (refer to LIMITS Command in section 7).
PW=password Specifies the file password. Specified if the UN=username is
specified, and if the permanent file to be replaced has a password.
M=n» Specifies the file access mode if the file does not already exist, or
if you want to change the access mode. If M=m is omitted for a newly
r created file, M=READ is assumed. If the parameter is omitted for a
previously existing file, the current access mode is retained.
PN=packname Specifies the auxiliary device name. Specified if the permanent file
to be replaced resides on an auxiliary device.
R=r Specifies the device type. Specified if a removable auxiliary device
on a device type other than the installation-defined default is to be
used.
NA
WB
Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
Specifies the wait-if-busy option. The job waits for the mounting of
disk packs.
The local files, lfnit are rewound before and after the replace operation.
The indirect access file created has the same access category as the file it replaces.
r Permission information and alternate user access data for the file are retained when a file
is replaced. If the file created is a new file, it is created as a private file.
60459680 E 10_45
![](asset-1c4.png)
SAVE COMMAND
The SAVE command retains a copy of a local file on mass storage as an indirect access file.
When you save a file using this command, the charge number and project number currently in
effect f or you r job a re associated wi th the fi le .
Format:
SAVE,lfni=pfni,lfn2=pfn2,... ,lfnn=pfnn/PW=password,CT=ct,M=m,SS=subsystem,
BR=br, PN=packname, R=r ,NA, WB, AL=level, XD=expiredate, XT=expire term, AC=ac.
■'**%.
Parameter Description
lfni=pfni Specifies that a copy of local file lfni becomes an Indirect access
permanent file named pfni (one- to seven-character name). If
lf«i= is omitted, the name of the local file is assumed to be
pfni. If no files are named, a copy of the primary file becomes an
indirect access permanent file with the same name as the primary file.
The full descriptions of the following optional parameters (except M=m) are given at the
beginning of this section.
Parameter Description
PW=passwrd Specifies the one- to seven-character password that other users must
specify to access the file.
CT=ct Specifies the file permit category; entries are P, PR, or PRIVATE for
private; S or SPRIV for semiprivate; and PU or PUBLIC for public. If
CT=ct is omitted, CT=PRIVATE is assumed.
M=ni Specifies the file access mode permitted to other users if the file is
public or semiprivate, and if explicit access permission has not been
granted to that user. If M=m is omitted, M=READ is assumed.
,**S«^y
I f m i s: Other users can:
R or READ
RU or READUP
RA or READAP
RM or READMD
U or UPDATE
E or EXECUTE
Retrieve a copy of the file. This copy can
be read or executed.
Retrieve a copy of the file. This copy can only
be executed.
A or APPEND Append data to the file with the APPEND command.
M or MODIFY Retrieve a copy of the file or append data to
the file. The user can enter GET, OLD, NEW, and
APPEND commands, but not a REPLACE command, for
t h e fi l e .
W or WRITE
N or NULL
Retrieve a copy of the file, append data to it,
replace it, or purge It.
No access is allowed.
10-46 60459680 D
![](asset-1c5.png)
0^^.
Parameter
SS=subsystem
BR=br
Description
Specifies the interactive subsystem associated with the file. This
subsystem becomes associated with the permanent file pfn, and is
selected automatically each time the file is retreived for use as a
primary file. If SS=subsystem is omitted, SS=NULL is assumed unless
lfn is the primary file. In that case, the file is associated with
the cu rrently activ e sub system. If SS is specified w ithout a
subsystem, the file is associated with the currently active subsystem.
Specifies the backup copy requirement; entries are Y (tape), or MD
(alternate storage), or N (no backup). If BR=br is omitted, a backup
copy of the file is stored on tape. Because indirect access files are
not stored on the alternate storage, BR=MD on a SAVE command is
equivalent to BR=Y.
PN=packname Specifies the name of the auxiliary device on which the indirect
access file is to reside.
R=r Specifies the device type on which the indirect access file is to
reside. The device must be a permanent file mass storage device on
which indirect access files are allowed.
0$^\
NA Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
W B C a u s e s t h e j o b t o w a i t f o r t h e m o u n t i n g o f d i s k p a c k s .
AL=level Specifies the security access level you want asssigned to the file.
Unless changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default is the access level of the local file being saved.
XD=expiredate Specifies the expiration date for the file password. The value
expiredate must be a six-digit string of the form yymmdd; where yy,
mm, and dd are two-digit year, month, and day designators,
respectively. You can specify this parameter only if you also specify
the PW=password parameter.
X T =e x p i r ete r m S p ec i fi e s t h e l i f e o f t h e fi l e p a s s wor d i n d a y s . I f y o u s p e c i fy 0 ,
the file password expires immediately. If you specify 4095 or *, the
file password does not expire. You can specify this parameter only if
you also specify the PW=password parameter.
AC=ac Specifies whether alternate users may obtain information about the
file using CATLIST. Entries are Y (yes) and N (no). The default is N,
The local files, lfni, are rewound before and after the save operation.
j|P\
60459680 G 10-47
![](asset-1c6.png)
SETPFAC COMMAND
The SETPFAC command changes the set of security access categories associated with a
permanent file. You can either specify an entirely new category set or add to or delete
from the current category set. By default on a secured system, the system associates all of
the access categories for which you are authorized to any permanent file you create.
Format:
SETPFAC, pf n,AC=0,category! ,category2,... ,categoryn/PN=packname,R=r,NA,WB.
or
SETPFAC,pfn,AC=categoryi,category2,... ,categoryn/PN=packname,R=r,NA,WB.
Parameter
pfn
AC=0,...
category^,
AC=...
categoryi,
PN=packname
R=r
Description
Specifies the permanent file whose access category set you want to
change.
Specifies a new category set. Unless changed by your site category.^
can be any of the following names:
CATOO,CAT02,...,CAT31
Specifies categories to add or delete from the current category set.
To add a category, prefix the category name with a plus sign or use
no prefix at all. To delete a category, prefix the category name with
a minus sign.
Specifies the auxiliary device name. You must specify this parameter
if pfn resides on an auxiliary device.
Specifies the device type. You must specify this parameter if a
removable auxiliary device on a device type other than the
installation-defined default is to be used.
NA
WB
Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
Specifies the wait-if-busy option. WB causes the job to wait for the
mounting of disk packs.
The first format creates a new access category set. The second format adds to or deletes
from the current category set.
On a secured system, the categories you specify must be valid for your job (ENQUIRE,B
returns this information). On an unsecured system, the system does not use the categories
to monitor access to the file but does maintain the categories as a file attribute.
10-48 60459680 D
![](asset-1c7.png)
/§!W\
/f^N
SETPFAL COMMAND
The SETPFAL command changes the security access level of a permanent file. By default, a
direct access file inherits the access level of the creating job. An indirect access
permanent file inherits the access level of the local file from which it was created. You
can also explicitly set the access level when you create a permanent file by specifying the
AL=level parameter on the command you use to create the file.
Format:
SETPFAL,pfn,AL=level/PN=packname,R=r,NA,WB.
The first two parameters are required and are order-dependent.
Parameter Description
pfn Specifies the permanent file whose access level you want to change.
AL=level Specifies the security access level you want assigned to the file.
Unless changed by your site, level can be one of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
PN=packname Specifies the auxiliary device name. You must specify this parameter
if pfn resides on an auxiliary device.
R=r Specifies the device type. You must specify this parameter if a
removable auxiliary device on a device type other than the
installation-defined default is to be used.
NA Specifies the no abort option. If NA is specified, processing errors
do not terminate the job.
W B S p e c i fi e s t h e w a i t - i f - b u s y o p t i o n . W B c a u s e s t h e j o b t o w a i t f o r t h e
mounting of disk packs.
On a secured system, the access level you specify must be valid for the job (ENQUIRE,B
returns this information). In addition, to lower the access level of a file, you must be
authorized to do so (refer to the LIMITS command).
On an unsecured system, the system does not use this access level assignment to monitor
access to the file but does maintain this assignment as a file attribute.
60459680 D 10-49 I
![](asset-1c8.png)
![](asset-1c9.png)
/^*v
LOAD/ DUMP MEMORY COMMANDS 11
The load/dump memory commands transfer information that resides in your job field length to
a local file or transfer information from a load file into your job field length. The
following commands are included in this category.
DMB DMP LOC WBR
DMD DMPECS PBC
DMDECS LBC RBR
NOTE
Fo r info rma tio n co nce rni ng s ecu rit y re st ric
tions associated with the use of these
commands, refer to Security Control in
sec ti on 3.
The DMB command dumps the exchange package, central memory, and extended memory in binary.
The DMP and DMD commands dump the exchange package or central memory in octal representation
or display code equivalences. Likewise, the DMDECS and DMPECS commands dump extended
memory. These commands are particularly helpful in creating dumps for debugging purposes
(refer to volume 2, Guide to System Usage). Other transfers of data from central memory use
the PBC command, which dumps a binary record to PUNCHB, and the WBR command, which writes a
binary record on a specified file.
Data is loaded to central memory by the LBC, LOC, and RBR commands. The LBC command is
j#^N useful in loading binary data in an unknown format.
i
All numeric parameters for these commands may be expressed in octal (postradix is B) or
decimal (postradix is D) notation. If no radix is specified, octal is assumed.
DMB COMMAND
The DMB command generates a binary dump of the exchange package, central memory, and
extended memory associated with the current job. File ZZZZDMB receives the dump and is not
rewound before or after the dump. If ZZZZDMB is assigned to the terminal before the dump,
the system returns it and creates a mass storage file by that name. Each dump creates one
logical record on ZZZZDMB. Refer to Express Deadstart Dump Interpreter in the NOS 2
Analysis Handbook for a description of how file ZZZZDMB can be formatted into a report.
Format:
DMB,ordinal,xmemory.
60459680 G 11-1
![](asset-1ca.png)
Parameter Description
ordinal Specifies the dump record name. The system appends this parameter to
the letter D to form a seven-character dump record name. Allowable
values of ordinal are 0 through 777777g. if the parameter ordinal
is greater than 377777g, the job aborts after the dump completes.
If you omit this parameter or specify a null entry, the record name
becomes D000000.
xmemory Determines whether the system dumps the extended memory assigned to
the job. The parameter xmemory can be any whole number. If xmemory
is zero or is omitted, the system dumps only the exchange package and
central memory assigned to the job. If xmemory is nonzero, the system
also dumps the extended memory assigned to the job.
^J*--!.f|l....T^.
11-2 60459680 C
![](asset-1cb.png)
You must not place another command (other than DMB, DMD, DMP, DMDECS, DMPECS, or EXIT)
between the program to be dumped and the DMB command.
A logical record of ZZZZDMB has the following format:
r
5 9 4 7 35 L7
07700 | 0016 1 o
1D dump record name
2yy/mm/dd.
3hh.mm.ss.
4pgnr
5 0
6 0
7 0
10 pgnr
11
16
ccdr
prefix table
59 53 17
Ddump record name
59 53 47 17
0ID 1 0
1version
2version
3Ayy/mm/dd.
4Ahh.mm.ss.
5machine characteristics
59 47 17
0XP 32fi
1
20 exchange package
21 (A0) register
30 (A7) register
Jl RA
32 RA+1
59
CM
47
central memory
17
CM FL/1008
59 41 1 7 (
0ECS EM FL/10008
1
m
extended memory
60459680 C 11-3
![](asset-1cc.png)
59 41
END
If an extended memory error occurs, the block in error will be filled with 400g
words of the following format:
59 11
ECSERROR
The variable items in the preceding display have the following descriptions:
item Description
n
m
t\
nnnn
pgnr
ccdr
Octal number of central memory words assigned to the job.
Octal number of extended memory words assigned to the job.
Space (display code value 55g).
Word number of the block in error (starting with 1).
Name of the system program called by DMB. Words 4 and 10
are blank-filled.
An image of RA+70 to RA+75 of the field length dumped. This
is usually a copy of the command being executed prior to the
dump.
11-4 60459680 C
![](asset-1cd.png)
0$^*
DMD COMMAND
The DMD command requests a dump similar to that of the DMP command but adds the display code
equivalences to the right of the octal representations. If lines are duplicated, they are
suppressed and an informative message is issued to the output file.
Formats:
DMD,fwa,lwa.
DMD,lwa.
DMD.
Parameter
fwa
Description
Specifies the first word address of memory to be dumped; fwa is
relative to RA. If fwa is absent, dump mode depends on the presence
or absence of lwa.
r
lwa Specifies the last word address plus one of memory to be dumped; lwa
is relative to RA. If lwa alone is present, DMD assumes fwa is 0. If
neither fwa nor lwa is present, DMD dumps the exchange package and
40g locations before and after the program address in the exchange
package. Only the lower 17 bits of the program address are used.
You must not place another command (other than DMD, DMB, DMP, DMDECS, DMPECS, or EXIT)
between the program to be dumped and the DMD command.
In batch jobs, the dump is written on file OUTPUT. Central memory dumps are written four
words per line.
In interactive jobs, DMD is effective only within procedure files or when specified on the
ENTER command. A dump from a terminal is formatted for 72-column output and written on
local file ZZZDUMP. DMD displays an informative message at the terminal. ZZZDUMP is not
rewound before or after the dump.
60459680 H 11-5 |
![](asset-1ce.png)
DMDECS COMMAND
The DMDECS command requests a dump of extended memory on file OUTPUT. The dump is four
words per line with display code equivalences to the right of the octal representations. If
lines are duplicated, they are suppressed and an informative message is issued to the output
file.
NOTE
The DMDECS command can dump only up to two
million words of extended memory. If you
want to dump more than two million words,
use the DMB command (described in this
section).
Formats:
DMDECS,fwa,lwa.
DMDECS,lwa.
Parameter
fwa
Description
Specifies the first word address of extended memory to be dumped; fwa
is relative to the reference address of the field in extended memory
being used by the job (RAE). If fwa is absent, DMDECS assumes fwa is
0.
lwa Specifies the last word address of extended memory to be dumped; lwa
is relative to RAE.
The DMDECS command must immediately follow a program to be dumped, except that another
DMDECS or a DMPECS, DMB, DMP, DMD, or EXIT command may intervene.
Dumping always stops at the field length in extended memory (FLE) if lwa is greater than
FLE.
If fwa is greater than FLE, fwa is set to FLE-10. If both fwa and lwa are greater than FLE,
fwa is set to FLE-10 and lwa is set to FLE.
11-6 60459680 H
![](asset-1cf.png)
0SO^y.
DMP COMMAND
The DMP command can request an exchange package dump or a central memory dump.
Formats:
DMP,fwa,lwa.
DMP,lwa.
DMP.
Parameter
ypfey
fwa
lwa
Description
Specifies the first word address of memory to be dumped; fwa is
r e l a t i v e t o t h e fi r s t w o r d o f t h e j o b ' s fi e l d l e n g t h . I f f w a i s
absent, the resulting dump depends on the presence or absence of lwa.
If fwa is greater than the job's field length, fwa is set at the job's
field length minus 10g. If fwa is greater than or equal to
4000008, the first dump address is fwa minus 400000g, memory from
the first dump address through lwa is dumped, and the job is aborted.
Specifies the last word address plus one of memory to be dumped; lwa
i s r e l a tiv e t o t h e fi r s t w o r d o f t h e j o b 's fi e ld l e ngt h . I f l w a a l o n e
is present, DMP assumes fwa is 0. If neither fwa nor lwa is present,
DMP dumps the exchange package and 40g locations before and after
the address in the program address register in the exchange package.
Only the lower 17 bits of the program address are used. If lwa is
greater than the job's field length, the dump stops at the end of the
field length.
If either fwa or lwa is nonnumeric, DMP dumps the exchange package and 40o locations
before and after the program address register in the exchange package. If both fwa and lwa
are greater than the job's field length, the last 10g words of the job's field length are
dumped. If fwa equals lwa, the 10g words beginning at fwa are dumped. If fwa is greater
than lwa, DMP issues an error message and terminates the job step.
You must not place another command (other than DMB, DMP, DMD, DMPECS, DMDECS, or EXIT)
between the program to be dumped and the DMP command.
DMP suppresses duplicate lines and then issues an informative message. In batch jobs, the
dump is written on file OUTPUT. Central memory dumps are written four words per line.
In interactive jobs, DMP is effective only within procedure files or when specified on the
ENTER command. A dump from a terminal is formatted for 72-column output and written on
local file ZZZDUMP. DMP displays an informative message at the terminal. ZZZDUMP is not
rewound before or after the dump.
0£^\
60459680 H 11-6.1/11-6.2 |
![](asset-1d0.png)
(*%
![](asset-1d1.png)
DMPECS COMMAND
The DMPECS command dumps the contents of extended memory of a job's field length on file
OUTPUT or a user-specified file. The dump is four words per line. If lines are duplicated,
they are suppressed and an informative message is issued to the output file.
NOTE
The DMPECS command can dump only up to two
million words of extended memory. If you
want to dump more than two million words,
use the DMB command (described in this
section).
A DMPECS command within an interactive job copies the contents of the extended memory of the
job's field length to the local file ZZZDUMP and displays a message at the terminal
informing you of the dump. ZZZDUMP is not rewound before or after the dump.
Formats:
DMPECS,fwa,lwa.
DMPECS,lwa.
DMPECS,fwa,lwa,f,Ifn.
Parameter Description
fwa Specifies the first word address of extended memory to be dumped; fwa
is relative to the reference address of the field in extended memory
being used by the job (RAE).
lwa Specifies the last word of extended memory to be dumped; lwa is
relative to RAE.
f Specifies the print format (included for compatibility with NOS/BE).
lfn Specifies the file to dump to.
If the first format is used, the field in extended memory defined by fwa and lwa is dumped
to the file OUTPUT. Display code equivalences do not appear.
If the second format is used, DMPECS assumes fwa is 0. Display code equivalences do not
appear.
If the third format is used, the specified field in extended memory is dumped to lfn. The
parameter f is ignored. Display code equivalences appear to the right of the octal
representations, the same as the DMDECS command.
The DMPECS command must immediately follow a program to be dumped, except that another
DMDECS or DMPECS, DMB, DMP, DMD, or EXIT command may intervene.
Dumping always stops at the field length in extended memory (FLE) if lwa is greater than FLE.
If fwa is greater than FLE, fwa is set to FLE-10. If both fwa and lwa are greater than FLE,
fwa is set to FLE-10 and lwa is set to FLE.
60459680 H U_7
![](asset-1d2.png)
LBC COMMAND
The LBC command is intended for loading binary data of unknown format.
Format:
LBC,addr.
Parameter Description
addr Specifies the address relative to RA at which binary load begins; if addr
is omitted, 0 (RA) is assumed.
LBC reads only one record from file INPUT. You must make an LBC call for each record of
data to be loaded. If addr is specified in the program call, binary data is loaded
beginning at that address; otherwise, loading begins at the reference address (RA).
LOC COMMAND
The LOC command reads octal line images from file INPUT and enters them in the job's central
memory field length.
Formats:
LOC,fwa,lwa.
LOC,lwa.
LOC.
Parameter Description
fwa Specifies the first word address of an area to clear (zero) before loading
correction statements. If fwa is absent, LOC assumes 0.
l w a S p ec i fi e s t h e l a st w o rd a d d res s p lus 1 o f t h e a r ea t o b e c l e a red . I f l w a
is absent, LOC assumes 0.
To process the LOC command, the system reads correction statement images from the current
INPUT record. A correction statement consists of an octal address and a data field. The
address field specifies the location to be corrected, and the data field contains the data
to be placed in that location. Both fields may start at any column as long as the address
precedes the data. The address field consists of a one- to six-digit address. If it is
five characters or less, it is separated from the data field by a nonoctal character (for
example, a blank). If It is six characters, no separator is required.
The data field consists of 1 to 20 octal characters. If it is less than 20 characters, it
is terminated by a nonblank, nonoctal character and is stored right-justified. If it is 20
characters, no terminator is required. Embedded blanks in the data field are ignored.
If both fwa and lwa are specified and both are nonzero, storage is cleared from fwa to lwa,
and the octal line images are loaded at the specified addresses. If the current INPUT
record is empty, LOC clears the indicated area of memory.
/^SSv
11-8 60459680 C
![](asset-1d3.png)
/dP^N
PBC COMMAND
The PBC routine writes one record from the specified area of central memory to file PUNCHB.
Formats:
PBC,fwa,lwa.
PBC,lwa.
PBC.
Parameter
fwa
lwa
Description
Specifies the address relative to RA at which the binary deck begins;
if this parameter is omitted, the PBC operation depends upon the
presence or absence of lwa.
Specifies the last word address of the binary deck. If lwa alone is
present, PBC assumes that fwa is RA. If lwa equals fwa, and a nonzero
value is specified, PBC adds 108 to lwa. If fwa and lwa are 0 or
are omitted, lwa is set to the value in the lower 18 bits of RA. If
the upper 12 bits of RA are 77008> iwa is the lower 18 bits of the
location following the prefix (77) table plus the length of the prefix
table.
Central memory is not altered by PBC.
RBR COMMAND
The RBR command loads one binary record from a specified file.
Format:
RBR,n,name.
Parameter
name
Description
Specifies that n is used in constructing the name of the file
containing the binary record to be read. If n is less than four
characters and is numeric, TAPEn is the file name. If n contains a
nonnumeric character or is four or more characters long, n itself is
used as the file name. If n is absent, TAPE is the file name.
Specifies the one- to seven-character name used in a record prefix.
The RBR command loads one binary record from the specified file into central memory starting
at RA. If the name parameter is included, a record prefix is placed in central memory
st art in g at R A. Th e re cord it self fo llow s. Th e fo ll owi ng i s th e fo rma t of th e re cord
prefix.
60459680 C 11-9
![](asset-1d4.png)
RA
RA+1
RA+2
RA+3
RA+17
RA+208
59
77
5200
53
Too"
length
lengthj
47 35 17
0016
date (yy/mm/dd.T
length
—O-
0lengthj
Record length including the prefix.
Record length minus words RA through RA + 178<
~<
If the record is too long for available memory, memory Is filled, excess data is skipped,
and an error message is issued to the job's dayfile.
WBR COMMAND
The WBR command writes a binary record from central memory to a file at its current position.
Format:
WBR,n,rl.
Parameter Description
Specifies the n is used in constructing the name of the file on which the
binary record is to be written. If n is less than four characters and is
numeric, TAPEn is the file name. If n contains a nonnumeric character or
is four or more characters long, n itself is used as the file name. If n
is absent, TAPE is the file name.
rl Specifies the record length in words,
taken from the lower 18 bits of RA.
If rl is 0 or absent, the length is
WBR begins writing from RA.
11-10 60459680 C
![](asset-1d5.png)
TAPE MANAGEMENT 12
This section describes commands used with magnetic tape files. For additional information
on NOS magnetic tape files, consult the glossary for definitions of terms; Magnetic Tape
Files in section 2 for descriptions of tape labels and data formats; and appendix G for tape
label formats. Section 7 describes the RESOURC command required in jobs that use more than
one tape or removable auxiliary pack concurrently.
To write on unlabeled tapes, you must have special authorization (refer to the LIMITS
command)•
NOTE
The term file as used in this section may
refer to a multifile file. Refer to table
2-1 for the EOR and EOF marks for tape files.
The commands described in this section are:
ygps ASSIGN Assigns a local file to a tape unitt (system origin jobs or jobs with
f system origin privileges only). Section 9 describes the ASSIGN command
for nontape files.
BLANK Blank labels a tape and may restrict access to the labeled tape.
LABEL Assigns a local file to a magnetic tape, creates and verifies tape
labels, and creates and accesses multifile set tapes.
LISTLB Lists tape labels.
^.^ REQUEST Assigns a local file to a magnetic tape device.
VSN Associates a file name with one or more VSNs for later assignment by a
LABEL or REQUEST command.
TAPE ASSIGNMENT
Whenever a tape is mounted, the system checks for labels. If the tape is labeled, the
system records the volume serial number (VSN) read from the V0L1 label and the equipment on
which the tape is mounted. When a tape assignment is requested by a LABEL or REQUEST
command specifying an lfn and a VSN (or an lfn that has been named in a previous VSN
command), the system compares the VSN with the VSNs read from mounted tapes. If a match is
found, the system automatically assigns the tape to the requesting job, provided a deadlock
would not occur .tt If the tape is not mounted, the system rolls out the job until a tape
with the requested VSN is mounted.
tlf you do not specify a VSN parameter or an MT or NT parameter on the tape assignment
command, the operator can assign the file to any device.
TTRefer to the RESOURC command in section 7.
60459680 C 12_x
![](asset-1d6.png)
For a mounted, unlabeled tape, the operator enters a command specifying the requested VSN.
The system can then assign the tape. A VSN which contains nonalphanumeric characters should
not be specified in a request for an unlabeled tape because nonalphanumeric characters
cannot be entered with the operator command.
If a VSN is not associated with the requested lfn, the system directs the operator to assign
an available device.
COMMAND RULES
On the tape assignment commands (LABEL, REQUEST, and ASSIGN), you can specify the tape label
contents, tape density, track type, nine-track conversion mode, data format, noise size, and
processing options. If any of these specifications are omitted, the system uses a default
value. ^
NOTE
1. For nine-track tapes, the density
specification given on the tape assignment
is used only when the tape is written from
load point. Otherwise, the tape is read or
written using the density previously used
for that tape. To ensure that a labeled
tape is at load point for rewriting the tape
at a new density, perform one of the
following before the write operation.
• Rewind the tape.
• Specify the W parameter on the LABEL
command used to assign the tape.
O Assign the tape using a REQUEST or
ASSIGN command.
2. Do not create labeled S or L format tapes
with tape marks embedded in the data.
Future adherence to ANSI standards will make
these tapes nonstandard as the ANSI standard
allows tape marks to be used only as
delimiters of label groups.
Do not specify duplicate or equivalent parameters. When you specify a parameter, do not
use = as a separator unless the parameter requires the keyword=value format.
12-2 60459680 C
![](asset-1d7.png)
/JilW^
ysz\
You can use a continuation line for an ASSIGN, BLANK, LABEL, REQUEST, or VSN command when I
"e svstef Hn6" "r " m°re than 8° Characters' If > ln Processing one of these commands,the system does not encounter a termination character prior to the end of the line it *
assumes the next line is a continuation line. A continuation line should be terminated with
a valid terminator. The terminator for a continuation line must appear in or before
column 80.
NOTE
The system accepts continuation lines from
an interactive terminal only if they are
within a procedure file.
You can use literals for parameters that contain nonalphanumeric characters. These
parameters are FI/L, FA, SI/M, VA, FA, OFA, and VSN. Nonalphanumeric characters are
characters other than letters, numbers, and asterisks.
A literal is a character string delimited by dollar signs. Blanks within literals are
retained. If the literal is to contain a dollar sign, two consecutive dollar signs must be
included. Thus, the literal
$A B$$41$
is interpreted as
J ^ v A B $ 4 1
When continuation lines are used, a literal cannot extend from one line to another.
PROCESSING OPTIONS
The P0= parameter on the LABEL, ASSIGN, and REQUEST tape assignment commands specify one or
more processing options that are to apply to that tape file. The characters representing
the processing options and their meaning are listed below.
PO=S gives the default end-of-tape conditions. Default error recovery attempts to recover
blocks having errors by repeatedly rereading the block. If the A, E, or N processing
options are not specified, the program determines whether an error aborts the job or the
Intfrf^ce)rf°rmS "^ processing (refer to the FET eP bit description in Volume 4, Program
Pi Description
A
60459680 E
Automatically aborts job on an irrecoverable read or write parity
error (refer to the N option).
Specifies error inhibit. All hardware read/write errors are ignored
and processing continues. The system does not attempt error recovery,
issue error messages, or return error status. During a read
operation, blocks less than noise size (refer to the NS parameter) are
unconditionally bypassed. Use this option guardedly. Use it to
recover portions of data from a bad tape, to check out hardware, and
to write on tape without skipping bad spots; in the latter case, you
are responsible for verifying that the data is written correctly.
12-3
![](asset-1d8.png)
Pi Description
F Forces unload. Unload at end of usage. (Refer to the U option.)
G Disables all hardware error correction activity in GE (6250 cpi) write mode.
An on-the-fly error while writing a GE tape results in standard error recovery
processing. The system erases the defective portion of tape, thereby reducing
the amount of data that can be stored on the tape. The default is
installation-defined (refer to the H option).
H Enables hardware error correction activity in GE (6250 cpi) write mode. The
system allows certain types of single track errors to be written that can be
corrected when the tape is read (on-the-fly correction). This is the
recommended mode because it provides efficient throughput, error recovery, and
tape usage when writing GE tapes on a medium that is suitable for use at 3200 -^
fci or 6250 cpi. The default option (G or H) is installation-defined. *^\
I Rewrites the block on which the end-of-tape occurred as the first block on the
next volume, if the system senses the EOT during a write operation. During a
read operation, the block on which the EOT occurred is ignored and reading
continues on the next volume. If a tape mark and the EOT are sensed at the
same time, the EOT is ignored. This option cannot be specified for I or SI
format tapes. Refer to the P and S options.
L Issues only the first and last error messages for each bad tape block.
Numerous attempts are made to read each bad block, but only the messages for
the first and last attempts are issued to the dayfile. The default is '"^
installation-defined (refer to the M option). '
MIssues an error message for each attempt to read a bad tape block. The
default is installation-defined (refer to the L option).
Specifies that job is not automatically aborted on an irrecoverable read or
write parity error (refer to the A option); data is passed to the job on a
read operation without error status set even if the program requested error
processing. Use this option guardedly.
Writes a trailer sequence following the block on which the EOT was sensed, if
the system senses the EOT during a write operation. Any data that occurs
following the block on which EOT was sensed, yet before the tape mark, is
ignored. During a read operation, the system transfers the block on which the
EOT was sensed to the user job. The read operation resumes on the next reel.
If a tape mark and the EOT are sensed at the same time, the EOT is ignored.
Refer to the I and S options.
Enforces ring out. If the tape is mounted with the write ring in, job
processing is suspended until the operator remounts the tape correctly.
Specifies where the system is to stop on an exit condition. For unlabeled
tape, it directs the system to stop at the first tape mark after the EOT is
sensed. For labeled tape, it directs the system to stop at the tape mark plus
E0F1 or the tape mark plus E0V1 when the EOT is encountered.
12-4
<^^v
60459680 C
![](asset-1d9.png)
vg^>»
Pi Description
If, during a write operation, the system senses the end-of-tape, the
system writes a trailer sequence following the block on which the EOT
was sensed. This trailer sequence consists of a tape mark followed by
an E0V1 label for labeled tapes and four tape marks for unlabeled
tapes. The next block is written on the next volume. During a read
operation, the EOT is noted and the system transfers to the user job
the block on which the EOT was sensed plus all following blocks until
a trailer sequence (as described previously) is recognized. Reading
resumes on the next volume.
U Inhibits unload. Do not unload at the end of usage. For system
origin jobs and the RECLAIM command, the inhibit unload option is
selected by default; for all other jobs, omission of the U option
causes the tape to be unloaded at end of usage.
W Enforces ring in. If the tape is mounted without the write ring in,
job processing is suspended until the operator remounts the tape
correctly.
Specifying QN=9999 on the LABEL command has the same effect for
multifile tapes.
If both ring enforcement options (R and W) are specified or more than one EOT option (I, P,
or S) is specified, the system issues a dayfile message and terminates the job step.
For further information on end-of-tape and end-of-reel conditions, refer to the CLOSER,
REWIND, UNLOAD, and LABEL macros in Volume 4, Program Interface.
ASSIGN COMMAND
The ASSIGN command names a tape unit and the local file to be assigned to that unit. It can
create an unlabeled tape file or access an existing labeled or unlabeled tape. It cannot
create or verify tape labels.
NOTE
To assign a tape unit using the ASSIGN
command, your job must be of system origin
or you must be authorized to use magnetic
tapes and to assign devices by EST ordinals.
Jobs that use this command without proper validation are aborted, and a dayfile message is
issued.
Before performing the assignment, the system unloads the local file (refer to the UNLOAD
command in section 9).
The following description applies only to magnetic tape files; for use of the ASSIGN command
with devices other than magnetic tape, refer to section 9.
60459680 H 12-5
![](asset-1da.png)
Format:
ASSIGN,nn,Ifn,VSN=vsn /vsn =..,=vsn
FC=fcount
C=ccount
CV=cv
„ ,NS=ns,P0=p.po...p
N=cvl ' rlr2 *t
»V"V |S} • fdeT) .Wor-t.LB-lb,
CK
CB ,AL=level.
Required parameters:
Parameter
lfn
Description
Device or device type to which the file lfn is assigned, nn can be
the EST ordinal* of a magnetic tape unit or one of the device types MT
or NT. Specifying MT informs the operator to assign the file to a
seven-track magnetic tape drive; NT informs the operator to assign
the file to a nine-track magnetic tape drive. Omission of this
parameter results in an error.
Name of the file to be assigned to the device nn. Omission of this
parameter results in an error.
Optional parameters:
VSN=vsn /vsn =
Parameter Description
=vsn /vsn One- to six-character volume serial number that
uniquely identifies a reel of tape. ASSIGN does not
use the VSN parameter to assign the tape,
parameter determines the tape assignment.
The nn
MT or NT
D=den or den
Specifies seven-track (MT) or nine-track (NT) tape
dri ve . I t m us t n ot con fli ct wi t h t he nn
specification.
Tape density; must not conflict with the MT or NT
specification. The default is installation-defined,
The parameter is ignored for nine-track tapes not
positioned at load point. Can be one of the
following:
Seven-track (MT)
den Density
LO 200 cpi
HI 556 cpi
HY 800 cpi
200 200 cpi
556 556 cpi
800 800 cpi
Nine-track (NT)
den Density
HD
PE
GE
800
1600
6250
800
1600
6250
800
1600
6250
cpi
cpi
cpi
cpi
cpi
cpi
tContact installation personnel for a list of EST ordinals.
12-6 60459680 H
![](asset-1db.png)
09s.
Parameter
F= form at
\
LB=lb
FC=fcount or C=ccount
CV=cv or N=cv
Description
Dat a format. D ef au lt is I. Ref er to Magnetic Tap e
Files in section 2 for descriptions of the data
formats.
Format Description
I Internal.
SI System internal.t
L Long block stranger.
S Stranger.
F Foreign (designed for tapes of unknown
data format).
Labeled or unlabeled tape. Default is KU if VSN is
omitted or KL if VSN is specified.
lb
KL
KU
NS
Meaning
ANSI-labeled. If the tape is a NOS
tape, volume and header label access
restrictions are enforced (refer to
appendix G).
Unlabeled.
Nonstandard-labeled. Assumes data
begins immed iately afte r th e first t ape
mark.
Whenever F format is specified, this parameter must
be specified. It specifies maximum block size in
frames. No default value. Illegal for other tape
formats.
Conversion modettfor nine-track tapes; applies to
both labels and data on coded tapes; applies only to
labels on binary tapes. Default is installation-
defined. Parameter is ignored for unlabeled I or SI
format binary tapes whose trailer labels are always
ASCII. Must not be specified with MT or seven-track
density specification.
cv Meaning
AS ASCII-display code conversion.
U S S a m e a s A S .
EB EBCDIC-display code conversion.
TNOS/BE system default tape format (binary mode only); used for tape interchange with
NOS/BE systems.
TTRefer to Magnetic Tape Users in appendix A.
60459680 C 12-7
![](asset-1dc.png)
Parameter
NS=ns
PO=p1P2...Pn
CK or CB
Description
Noise size. Any block containing fewer than ns
frames is considered as noise and is discarded. The
NS parameter is not valid for I or SI format tapes
or for other tape formats when either PE (9-track,
1600 cpi) or GE (9-track, 6250 cpi) density is
specified. For PE and GE densities, the noise block
size is zero. Default is 18 frames for other
formats. Maximum value is 31 frames. If NS=0 is
specified, the default Is used.
A string of characters (not separated by commas)
that specify processing options (refer to Processing
Options in this section).
Specifies that lfn is to be used as a checkpoint
fi le (re fer to se c ti o n 1 3) .
CK Each dump is written at the previous
EOI of lfn.
CB Each dump is written at the BOI of lfn.
AL=level Specifies the security access level to assign to the
file. Unless changed by your site, level can be one
of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default is the current access level of the job.
On a secured system, the access level you specify
must be valid for the job (ENQUIRE,B returns this
information) and for the device to which you are
assigning the file.
On an unsecured system, the parameter has no
effect. The system does, however, check for valid
parameter specifications.
^^^Nv
y^SSV
Example:
When using this command to assign a file for
checkpoint dumps on a secured system, use the
AL=level parameter to assign the file at the highest
access level valid for the job (ENQUIRE,B returns
this information). The CKP command aborts the job
if the checkpoint file is not at this access level.
ASSIGN,51,TAPE1,D=PE,F=SI.
This command assigns the file TAPE1 to the nine-track magnetic tape unit identified by EST
ordinal 51.
./"^Ss
12-8 60459680 D
![](asset-1dd.png)
BLANK COMMAND
The BLANK command writes the ANSI standard labels VOL1, HDRl, and E0F1 following the load
point of a tape. The labels are written as follows (asterisks represent tape marks):
V0L1 HDRl E0F1 Zl
If the value of a labeled field is specified by a BLANK command parameter, that value is
written; otherwise, the default value is used. Refer to appendix G for the tape label
formats and default values.
NOTE
A BLANK command issued in a nonsystem origin
job cannot overwrite a label containing an
unexpired expiration date or a nonblank VA
field.
If th e FA fie ld wi th in th e labe l i s
nonblank, a nonsystem origin job must
specify the FA character using the OFA
parameter. If the FA character is A, only
the owner or a system origin job can
overwrite the label.
Format:
BLANK.VSN-vsn, {^} ,{D^n},{«:-j)FA=fa,OFA=ofa,VA=va,
OWNER=username/familyname,LSL=lsl,U.
Parameter
VSN=vsn
Description
One- to six-character volume serial number that
uniquely identifies the reel of tape. It is entered
in the V0L1 label. It need not match the VSN
previously recorded on the tape.
| NOTE
Avoid specifying a volume serial
number that matches a local file
name attached to your job or the
l o c a l fi l e w i l l b e l o s t .
Omitting the VSN parameter
discards any local file named
BLKTAPE from your job.
60459680 H 12-9
![](asset-1de.png)
Parameter
MT or NT
D=den or den
CV=cv or N=cv
FA=fa
Description
Specifies seven-track (MT) or nine-track (NT) tape
drive. Installation-defined default. Must not
conflict with D=den specification.
Tape density; must not conflict with the MT or NT
specification. The default is
installation-defined, den can be one of the
following.
Seven-track (MT) Nine-track (NT)
den Density den Density
LO 200 cpi HD 800 cpi
HI 556 cpi PE 1600 cpi
HY 800 cpi GE 6250 cpi
200 200 cpi 800 800 cpi
556 556 cpi 1600 1600 cpi
800 800 cpi 6250 6250 cpi
Conversion modet for nine-track tape labels.
Installation-defined default. Must not be specified
with MT or seven-track density specification.
cv Meaning
AS ASCII/6-bit display code conversion.
U S S a m e a s A S .
EB EBCDIC/6-bit display code conversion.
File accessibility character indicating who has
access to the labeled tape. Value entered in HDRl
and E0F1 labels.
fa Description
Blank Unlimited access (default).
A Only the owner of this NOS written tape
can access it.
/*^v\
OFA=ofa
Other In all future accesses of this tape,
you must specify this character.
Old file accessibility character on a labeled tape
that is to be relabeled. This parameter must be
specified if the FA field is currently other than A
or blank. Future accesses of the tape must specify
the character specified with the FA parameter.
TRefer to Magnetic Tape Users in appendix A,
12-10 60459680 H
![](asset-1df.png)
Parameter Description
VA=va Volume accessibility character indicating that the
volume must be accessed as an ANSI-labeled tape
(LB=KL). If VA Is nonblank, only a system origin
job can destroy V0L1 (for example, assign tape as
unlabeled). Default is unrestricted access. Refer
to the V0L1 format in appendix G.
OWNER=username/familyname Owner identification entered in V0L1 label.
Determines the owner for file accessibility (FA)
parameter.
LSL=lsl Label standard level entered in V0L1 label. Default
is the number 1.
Isl Description
1 Tape labels and data format for this
volume conform to the ANSI standard.
Blank Tape labels and data format for this
volume may or may not conform to the
ANSI standard.
U If U is specified, the tape is physically unloaded
when returned after blank labeling. If U Is
omitted, physical unloading is inhibited.
An installation can use the BLANK command to restrict use of its labeled tapes. Once a tape
has been blank labeled, you can modify the labels as follows:
1. If t he vol ume acc ess ibi lity fie ld of V0L1 in dic ate s un lim ite d ac ces s (tha t is , VA i s
blank), you can:
• Include another BLANK command to change V0L1, HDRl, or E0F1 values.
• Request the tape as unlabeled (with the parameter LB=KU) and write it in
whatever format you specify.
• Include a LABEL command to change HDRl by specifying one or more of the
parameters associated with that label and specifying the W parameter.
2. If the volume accessibility field is nonblank, you can:
• Include a LABEL command to change HDRl. However, in requesting a tape in
which VA is nonblank, you must specify an ANSI-labeled tape (with the
parameter LB=KL), and therefore, cannot change or destroy the V0L1 label.
• If validated, submit a system origin job to change V0L1.
60459680 H 12-10.1/12-10.2
![](asset-1e0.png)
![](asset-1e1.png)
LABEL COMMAND
Like ASSIGN and REQUEST commands, the LABEL command associates a file name lfn with a
magnetic tape, usually identified by its VSN. Unlike the ASSIGN and REQUEST commands the
LABEL command can create and verify tape labels. It can also position a multifile set for
access to any of its existing files or for appending a new file. The LABEL command can
create and access unlabeled as well as labeled tapes.
NOTE
A LABEL command cannot overwrite a label
with an unexpired expiration date (refer to
appendix G).
To write the labels that begin a labeled tape (refer to Magnetic Tape Files in section 2),
specify a write label (W) parameter. The W parameter always rewinds the tape to load point
and rewrites the first label group. Overwriting the header labels for a tape file
effectively destroys the data on the file. The label contents remain the same when a LABEL
command with the W parameter names an lfn already assigned to a tape file.
If the tape was not previously part of a multifile set (the SI field in the first HDRl label
is blank), then specification of the SI and QN=9999 parameters rewrites the initial tape
labels. r
r To p o s i t i o n t h e t a p e a f t e r a n y H D R l l a b e l o t h e r t h a n t h e fi r s t H D R l l a b e l ( m u l t i fi l e s e tonly), the SI parameter must be specified. When SI is specified, the R and W parameters are
ignored unless QN=1 and the first file on the tape is to be written. The system determines
where to position the tape by matching the SI, FI, and QN parameter values (if specified) to
the corresponding values in the HDRl label. (The HDRl label format is given in appendix G.)
To write the E0F1 and HDRl labels between two files in a multifile set (refer to
figure 2-2), you specify the SI and QN=9999 parameters. The W parameter is ignored if
specified when appending the file (QN=9999). Although the SI=setid parameter must be
specified when appending a file to a multifile set, the appended file will be given the same
setid as the preceding file regardless of the setid value specified in the LABEL command.
JP*S This is done to ensure that all files in a file set have the same set identifier.
If neither the MT nor NT parameter is specified and no VSN is named, the operator can assign
the file to any equipment. You must be validated for the assigned equipment or the job is
terminated.
60459680 H 12_n ■
![](asset-1e2.png)
,-*^^v
Format:
{NTT \
m\ ,D=den,F=format,LB=lb,
JFC=fcount| |CV=cv| |CK|/si=setid|
( C=ccount)'( N=cv|'NS-nS'P0-PlP2"-Pn'(cB)( M=setid) '
f S N = s e c n o l ( Q N = s e q n o | ( F I = f i l e i d | „ t c
\ V=secno) ' lP=seqno J ' lL=fileid J » FA=fa,G=genno,E=gvn,
( C R = c d a t e | } R T = y y d d d | j w l A T , , t „
1 C=cdate) * (T=ddd | ' (r) »AL=level,AC=ac,CT=ct,MD=md,PW=password,TO=to,UN=username,
Required parameter:
=cdate| » JT=ddd |
Parameter
lfn
Optional parameters:
Parameter
VSN=vsn /vsn =. .=vsn ,/vsn
n-1
Description
Name of the file that resides or is to reside on
magnetic tape. If lfn is already assigned to a mass
storage file, processing continues with the next
command. To assign a previously assigned lfn, you
mu st re tu rn lf n b ef or e its r ea ss ig nm en t. If lf n i s
already assigned to a tape and R parameter is
specified, the contents of the tape labels are
compared to the command parameter specifications.
If the label verification fails, the job aborts.
Omission of lfn results in an error.
Description
One- to six-character volume serial number that
uniquely identifies a reel of tape. If VSN is
omitted, the operator assigns an available unit to
lfn. Multiple VSNs can be specified if separated by
/ or = characters. If the VSNs are separated by the
= character, LABEL assigns lfn to the first available
VSN in the list. If the VSNs are separated by the
/ character, lfn is a multivolume file set, and LABEL
assigns the volumes in the sequence given. If
VSN=, VSN=0, or VSN=SCRATCH is specified, a scratch
tape is assigned. If a scratch tape is unavailable,
the job is suspended until a tape is available.
12-12
>35^\
60459680 H
![](asset-1e3.png)
fmstx\
Parameter
MT or NT
D=den
F=format
/^P^»
LB=lb
FC=fcount or C=ccount
Description
Requests seven-track (MT) or nine-track (NT) tape
drive. Installation-defined default. Must not
con fli ct wi th D= d en sp e ci fic ati on .
Tape density; must not conflict with MT or NT
specification. The default is
installation-defined. The parameter is ignored for
nine-track tape not positioned at load point. Can
be one of the following:
Seven-track (MT) Nine-track (NT)
den Density den Density
LO 200 cpi HD 800 cpi
HI 556 cpi PE 1600 cpi
HY 800 cpi GE 6250 cpi
200 200 cpi 800 800 cpi
556 556 cpi 1600 1600 cpi
800 800 cpi 6250 6250 cpi
Data for mat. Default is I. R efer to Mag netic Tape
Files in section 2 for descriptions of the data
formats.
format Description
I Internal.
SI System internal.
S Stranger.
L Long block stranger.
F Foreign (designed for tapes of unknown
data format).
Labeled or unlabeled tape. Default is KL.
KL
KU
NS
Description
ANSI-labeled.
Unlabeled.
Nonstandard-labeled. Assumes data
begins immediately after the first tape
mark.
Whenever F format is specified, this parameter must
be specified. It specifies the maximum block size
in frames (no default value). Not applicable for
other tape formats.
TNOS/BE system default tape format (binary mode only); used for tape interchange with
NOS/BE systems.
60459680 C 12-13
![](asset-1e4.png)
Parameter Description
C V = c v o r N = c v C o n v e r s i o n m o d e t f o r n i n e - t r a c k t a p e s ; a p p l i e s t o
both labels and data on coded tapes; applies only to
labels on binary tapes. Installation-defined
def ault. Ig nored for un la be led I or SI f or mat
binary tapes whose trailer labels are always ASCII.
Must not be specified with MT or seven-track density
specification.
cv Meaning
AS ASCII/display code conversion.
U S S a m e a s A S .
EB EBCDIC/display code conversion.
NS=ns Noise size; any block containing fewer than ns
frames is considered noise and is discarded. The NS
parameter is not valid for I or SI format tapes or
for other tape formats when either PE (9-track,
1600 cpi) or GE (9-track, 6250 cpi) density is
specified. For PE and GE densities, the noise block
size is zero. Default is 18 frames for other
formats. Maximum value is 31 frames. If NS=0 is
specified, the default is used.
P0=pip2...pn A string of characters (not separated by commas)
that spec ifie s pro ces si ng opt ion s. Re fer to
Processing Options in this section.
CK or CB Specifies that lfn is to be used as a checkpoint
fi le ( r ef e r t o s ec t i on 1 3 ).
CK Each dump is written at the previous
EOI of lfn.
CB Each dump is written at the BOI of lfn.
tRefer to Magnetic Tape Users in appendix A.
12-14 60459680 D
![](asset-1e5.png)
Optional tape label parameters (refer to appendix G):
Parameter Description
SI=setid or M=setid
SN=secno or V=secno
One- to six-character file set identifier; must be
specified for file positioning within a multifile
s e t .
The system leaves the set identifier field in the
HDRl label blank if you omit the SI=setid parameter
or if you specify blanks for setid.
You must specify a nonblank file set identifier to
build a multifile set. Hence, if you omit this
parameter when you write the first file on the tape,
the tape cannot then be a multifile set tape. When
you append a file to a multifile set tape, you must
specify this parameter to position the tape. Also,
the specified set identifier must be the same as
t h a t o f t h e fi r s t fi l e i n t h e m u l t i fi l e s e t .
One- to four-digit file section number specifying I
the position of the volume within a multivolume file
set (numbered consecutively from 0001). The default
i s 1 .
QN=seqno or P=seqno
FI=fileid or L=fileid
FA=fa
One- to four-digit file sequence number specifying
the position of the file within the multifile set
(numbered consecutively from 0001). The default is
1. QN must be set to 9999 to append a new file to a
multifile set.
A 1- to 17-character file identifier recorded in the
HDRl label (refer to appendix G). The default is
blank.
File accessibility character indicating who has
access to the labeled tape.
fa
Blank
A
Description
Unlimited access (default).
Only the owner of the tape can access
it.
G=genno
Other To access the tape, you must sp ecify
the character in the FA field of the
HDRl label.
One- to four-digit generation number. The number
zero cannot be used. The default is 1.
/fPN,
60459680 H 12-15
![](asset-1e6.png)
Parameter
E=gvn
Description
One- to two-digit generation version number,
default is 0. The
CR=cdate or C=cdate
RT=yyddd or T=ddd
Creation date in the form yyddd where
1 _< ddd <^ 366. Used only on read operations; write
operations always use the current date.
RT=yyddd specifies the expiration date where yy is
the last two digits of the year, and ddd is the day
of the year (1 < ddd _< 366). T=ddd specifies the
number of days the file is to be retained
(0 < ddd _< 999). The expiration date is entered in
the HDRl label. On or after this date the label and
the file can be overwritten.
R or W If R is specified, the system compares the values
recorded on the file labels with the LABEL command
pa ramet er v al ues . If th e co mpari son fa ils , it
terminates the job. R is the default.
If W is specified, the system writes ANSI standard
labels on the tape. The labels contain the values
specified with the LABEL command parameters or their
default values. If the tape is mounted without the
write ring, job processing is suspended until the
operator remounts the tape correctly. If both the W
and the P0=R parameters are specified, the job step
aborts.
AL=level
12-16
W and R are ignored when SI is specified and
QN > 1. When QN = 1 (default value) and W are
specified, the initial header label is rewritten.
Specifies the security access level to assign to the
file. Unless changed by your site, level can be one
of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default is the current access level of the job.
On a secured system, the access level you specify
must be valid for the job (ENQUIRE,B returns this
information) and for the device to which you are
assigning the file.
On an unsecured system, the parameter has no
effect. The system does, however, check for valid
parameter specifications.
When using this command to assign a file for
checkpoint dumps on a secured system, use the
AL=level parameter to assign the file at the highest
access level valid for the job (ENQUIRE,B returns
this information). The CKP command aborts the job
if the checkpoint file is not at this access level.
60459680 H
![](asset-1e7.png)
0^\.
Parameter
AC=ac
CT=ct
MD=md
PW=password
TO=to
UN=username
Description
Alternate auditability. Refer to the NOS 2 Tape
Management System (TMS) User Reference Manual for a
detailed description.
File category. Refer to the NOS 2 Tape Management
System (TMS) User Reference Manual for a detailed
description.
File Mode. Refer to the NOS 2 Tape Management
System (TMS) User Reference Manual for a detailed
description.
Password. Refer to the NOS 2 Tape Management System
(TMS) User Reference Manual for a detailed
description.
TMS tape option. Refer to the NOS 2 Tape Management
System (TMS) User Reference Manual for a detailed
description.
User name. Refer to the NOS 2 Tape Management
System (TMS) User Reference Manual for a detailed
description.
60459680 H 12-16.1/12-16.2
![](asset-1e8.png)
f*%
![](asset-1e9.png)
g3^&*\
J^p&\
r
j|!S5&»>
Example 1 - Reading and Writing a Single-File File Set:
In the following job, the user reads data from one tape and writes data on another tape.
Program input data previously written at 1600 cpi on a nine-track tape unit is read from
tape TP01. Output data is written on tape TP02.
FTNJOB.
USER, USERNAM, PA SSWRD.
RESOURC, PE=2.
FTN 5.
LAB EL, TA PE 1, VS N=T P01, D=PC , PO =R.
LABEL, TAPE2,VSN=TP02,D=PE,P0=W,W.
LGO.
-EOR-
PROGRAM SORT
END
-EOR-
The RESOURC command schedules two nine-track, 1600-cpi tape units for concurrent use in the
job. The tapes are not requested until after compilation of the program in case compilation
errors occur.
Assuming the compilation completes without fatal error, the LABEL commands request that two
tapes, TP01 and TP02, be mounted and assigned to the job. The tape files are called TAPE1
and TAPE2 within this job. P0=R is specified for the input tape, ensuring that the tape
does not have a write ring. P0=W is specified for the output tape which requires a write
ring. The W parameter on the second LABEL command specifies the writing of ANSI standard
labels. Default values are used in the label fields.
Following completion of the job, the tapes are rewound and unloaded.
Example 2 - Reading and Writing a Multifile Set:
The following job writes the object programs produced by three compilations as three files
of a multifile set. It then copies one of the files to mass storage and executes it.
SJOB.
USER, USERNAM, PASSWRD.
GET,BS0RT,QS0RT,LS0RT.
LABEL,STAPE,VSN=TP03,D=PE,SI=BINSET, FI=BS0RT,P0=W,W.
FTN5,I=BS0RT,B=STAPE.
LABEL,STAPE, VSN=TP03,D=PE,SI=B INSET, FI=QS0RT,QN =9999.
FTN5,I=QS0RT,B=STAPE.
LABEL,STAPE, VSN=TP03,D=PE,SI=B INSET, FI=LS0RT,QN =9999.
FTN5,I=LS0RT,B=STAPE.
LABEL,STAPE,VSN=TP03,D=PE,SI=B INSET, QN=2.
C0PYEI,STAPE,QS0RTB.
QSORTB.
60459680 E 12-17
![](asset-1ea.png)
The GET command retrieves three indirect access files - BSORT, QSORT, and LSORT - containing
FORTRAN source programs. The first LABEL command requests the mounting and assignment of
tape TP03 to the job. The W parameter specifies the writing of ANSI standard labels. The
set identifier and file identifier fields are written using the values specified on the SI
and FI parameters. The B=STAPE parameter on the FTN5 command specifies that the object
program is to be written on the tape file.
The QN=9999 parameter on the second and third LABEL commands specifies that a file is to be
appended to the tape. Although the same set identifier is used for all files within a file
set, the SI parameter must be specified when positioning a multifile set. The second and
third compilations write the second and third files of the file set.
The QN=2 parameter on the fourth LABEL command positions the tape at the second file of the
file set. The tape could also have been positioned according to the file identifier
(FI=QSORT). The second file is copied to a local mass storage file, QSORTB, and executed.
Example 3 - Replacing a File within a Multifile Set:
To replace a file within a multifile set, you must first copy to temporary storage the files
that follow the file to be replaced, then write the replacement file, and last rewrite the
succeeding files in the file set.
RWJOB.
USER,USRNAME,PASWRD.
GET,S0RT2.
LABEL,STAPE,VSN=TPQ3,D=PE,SI=BINSET,QN=2,P0=W.
COPYEI,STAPE,SCRATCH.
LABEL,STAPE,VSN=TPQ3,D=PE,SI=BINSET,QN=1.
C0PYEI,S0RT2,STAPE.
LABEL,STAPE,VSN=TP03,D=PE,SI=BINSET,FI=QS0RT,QN=9999.
COPYEI, SCRATCH, STAPE.
The first LABEL command requests tape TP03 containing the multifile set created in example
2. The tape is mounted with a write ring inserted (PO=W) and is positioned at the second
file of the file set (QN=2). The COPYEI command copies the second file to the mass storage
file, SCRATCH.
The second LABEL command positions the tape at the first file. Although the contents of the
first file are rewritten, the file labels remain unaltered.
The third LABEL command appends the second file to the file set (QN=9999). The labels are
rewritten so you can change the label contents. The third COPYEI command writes the second
file as stored on file SCRATCH.
The third file of the multifile set is lost, because it was not saved before the tape was
rewritten.
12-18 60459680 C
![](asset-1eb.png)
LISTLB COMMAND
The LISTLB command lists the labels of an ANSI-labeled tape file. For a correct listing of
labels, the data format specified on the tape assignment command must correspond to the
format in which the tape was written. For output listing files not connected to your
terminal, the LISTLIB command honors the page length and print density set for your job
using the SET command and the PL and PD symbolic names.
Format:
LisxLB.ifn, {££«<) .{?!::qer}.^^,L=out.
Parameter
/SS^v lfn
SI=setid or M=setid
QN=seqno or P=seqno
LO=ltype
Description
File name assigned to tape file whose labels are to
be listed. Default is file name TAPE. If you use
the default name, assign TAPE to the labeled tape
being read.
One- to six-character file set identifier. If
specified, only label groups whose HDRl label
contains this value are listed. You must specify
this parameter to list the labels of a multifile set.
One- to four-digit file sequence number. If seqno
is specified, only the label group whose HDRl label
contains this value is listed. If seqno is
specified, SI must be specified; otherwise, LISTLB
termin at es.
Label type(s) to be listed. The default is R.
Required and optional labels are listed in appendix
G. Combinations of ltype mnemonics can be
specified, such as LO=VH to list only the VOLn and
HDRn labels.
A List all labels.
R List required labels.
0 List optional labels.
V List VOLn labels.
L=out
List HDRn labels.
List EOFn labels.
List EOVn labels.
List UVLn, UHLn, and UTLn labels.
File on which the labels are to be listed. Default
is OUTPUT.
60459680 H 12-19
![](asset-1ec.png)
>=%\
To list labels for a multifile set (lfn contains more than one HDR1/E0F1 label pair), you
must specify the SI=setid parameter and the tape must be positioned at load point. LISTLB
then positions the tape for reading the requested labels. It searches for labels through
all volumes associated with lfn. At the end of the multifile set or if an expected label
group is not found, the following dayfile message is issued, n is the sequence number of
the last file found, (nnn should be ignored.)
MULTI-FILE NOT FOUND, Lfn AT nnn.
REQUEST SECTION n+1.
FOUND SECTION n.
After issuing this dayfile message, LISTLB leaves the tape positioned after the last listed
label. The next command processed for the tape file must be either RETURN, EVICT, UNLOAD,
or LABEL.
For a tape file that is not a multifile set, there are two cases. If you specify trailer
labels, LISTLB leaves the tape positioned before the trailer labels last listed. Otherwise,
LISTLB leaves the tape positioned after the label last listed.
Example 1:
The following commands list the second label group of file set ABCDEF.
LABEL,T,VSN=EXAMP1,MT,D=HY,SI=ABCDEF.
LISTLB,T,SI=ABCDEF,QN=2.
Example 2:
To list only the volume and header labels (trailer labels omitted) of a multivolume file
set, you must request a volume of the file set, list its labels, and return the file set,
repeating the procedure for each volume of the file set.
LABEL,T,VSN=REEL1,MT,D=HY.
LISTLB,T,LO=VH.
RETURN,T.
LABEL,T,MT,D=HY,VSN=REEL2.
LISTLB,T,LO=VH.
Example 3:
To list all labels of the following file set, only one LISTLB command is required.
VSN,T=REEL1/REEL2.
LABEL,T,VSN=REEL1,D=HY.
LISTLB,T.
The LISTLB(T) command lists all labels on the volumes associated with T, that is, REEL1 and
REEL2.
12~20 60459680 C
![](asset-1ed.png)
REQUEST COMMAND
The REQUEST command associates a file name, lfn, with a magnetic tape device.t You can
direct the operator to make the tape assignment by including a comment following the command
terminator. This comment appears at the system console. However, if the tape is labeled
and you previously specified a VSN via the VSN control command or included the VSN parameter
on the REQUEST command, the system can automatically assign the tape. The REQUEST command
can create unlabeled tape files and access existing labeled and unlabeled tape files. It
cannot create or verify tape labels.
The LABEL command performs the same function as the REQUEST command. Unless you have reason
to do otherwise, use the LABEL command. TMS does not support the REQUEST command.
Format:
REQUEST,lfn,VSN=vsn1/vsn2=...=vsnn_1/vsnn, {^} , {°^enJ ,F=format,
th-ik (FC=fcount) (CV=cvl MP nn [CK)
LB-lb> ( C=ccount) '{N=cv pS=ns,PO=Plp2...pn, jC]}j ,AL=level.comment
Required parameter:
Parameter
lfn
Description
Name of the file that resides or is to reside on
magnetic tape. If lfn is already assigned to a mass
storage file, processing continues with the next
command. To assign a previously assigned lfn, you
must return lfn before Its reassignment. Omission
of this parameter results in an error.
Optional parameters:
Parameter
VSN=vsn./vsn =...=vsn ,/vsn
1 2 n - 1 n
Description
One- to six-character volume serial number
uniquely identifying a reel of tape. You should
specify a VSN for labeled and unlabeled tapes. If
VSN is omitted, the operator must assign an
available device to lfn.
If VSN=, VSN=0, or VSN=SCRATCH is specified, a
scratch tape is assigned. If a scratch tape is
unavailable, the job is suspended until a tape is
available.
Multiple VSNs can be specified if separated by a /
or = character. If the VSNs are separated by the =
character, the system assigns lfn to the first
available VSN in the list. If the VSNs are
separated by the / character, lfn is a multivolume
file set, and LABEL assigns the volumes in the
sequence given.
tlf you do not specify a VSN parameter or an MT or NT parameter on the command, the
operator can assign any device to the file. If you are not authorized to use the assigned
device, the job aborts.
60459680 H 12-21
![](asset-1ee.png)
^^v
Parameter
MT or NT
D=den or den
F=format
Description
Requests seven-track (MT) or nine-track (NT) tape
drive. Installation-defined default. Must not
conflict with D=den specification.
Tape density; must not conflict with MT or NT
specification. The default is
installation-defined. The parameter is ignored for
nine-track tape not positioned at load point. Can
be one of the following.
Seven-track (MT) Nine-track (NT)
den
LO
HI
HY
200
556
800
Density
200 cpi
556 cpi
800 cpi
200 cpi
556 cpi
800 cpi
den
HD
PE
GE
800
1600
6250
Density
800 cpi
1600 cpi
6250 cpi
800 cpi
1600 cpi
6250 cpi
Data format. Default is I. Refer to Magnetic Tape
Files in section 2 for descriptions of the data
formats.
LB=lb
format
I
Sit
S
L
F
Description
Internal.
System internal.
Stranger.
Long block stranger.
Foreign (designed for tapes of unknown
data format).
Labeled or unlabeled tape. Default is KL if a
volume serial number is specified by the VSN
parameter or by a VSN command; otherwise, the
default is KU.
..oCfBsjV
lb Description
KL ANSI-labeled.
KU Unlabeled.
NS Nonstandard-labeled. Assumes that data
begins immediately after the first tape
mark.
TNOS/BE system default tape format (binary mode only); used for tape interchange with
NOS/BE systems.
12-22 60459680 C
![](asset-1ef.png)
Parameter
FC=fcount or C=ccount
CV=cv or N=cv
Description
Whenever F format is specified, this parameter must
be specified. It specifies the maximum block size
in frames (no default value). Illegal for other
tape formats.
Conversion mode* for nine-track tapes; applies to
both labels and data on coded tapes; applies only to
labels on binary tapes. Installation-defined
default. Ignored for unlabeled I or SI format
binary tapes whose trailer labels are always ASCII.
Must not be specified with MT or seven-track density
specification.
cv Meaning
AS ASCII/display code conversion.
U S S a m e a s A S .
EB EBCDIC/display code conversion.
NS=ns
r
PO=p1p2...pn
CK or CB
Noise size. Any block containing fewer than ns
frames is considered as noise and is discarded. The
NS parameter is not valid for I or SI format tapes
or for other tape formats when either PE (9-track,
1600 cpi) or GE (9-track, 6250 cpi) density is
specified. For PE and GE densities, the noise block
size is zero. Default is 18 frames for other
formats. Maximum value is 31 frames. If NS=0 is
specified, the default is used.
A string of characters (not separated by
commas) that specifies processing options,
to Processing Options in this section.)
(Refer
File lfn is to be used as a checkpoint file (refer
to section 9).
CK Each dump is written at the previous
EOI of lfn.
CB Each dump is written at the BOI of lfn.
AL=level Specifies the security access level to assign to the
file. Unless changed by your site, level can be one
of the following names:
LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7
The default is the current access level of the job.
TRefer to Magnetic Tape Users in appendix A.
60459680 H 12-23
![](asset-1f0.png)
Parameter
comment
Description
On a secured system, the access level you specify
must be valid for the job (ENQUIRE,B returns this
information) and for the device to which you are
assigning the file.
On an unsecured system, the parameter has no
effect. The system does, however, check for valid
parameter specifications.
When using this command to assign a file for
checkpoint dumps on a secured system, use the
AL=level parameter to assign the file at the highest
access level valid for the job (ENQUIRE,B returns
this information). The CKP command aborts the job
if the checkpoint file is not at this access level.
The comment appears at the system console. In the
comment field, you can direct the operator to make
the requested assignment.
Example:
To send a message to the operator requesting that volume XYZ be mounted on tape unit NT62
and assigned to lfn TAPE1, you could issue the following command.
REQUEST,TAPE1. NEED VSN=XYZ ON NT062.
12-24 60459680 D
![](asset-1f1.png)
VSN COMMAND
The VSN command associates a file name lfn with one or more vol vanes of tape.t An lfn/VSN
association allows the system to assign the specified VSN to lfn without reference to a VSN
parameter on the LABEL or REQUEST command or to an operator command. Once declared, an
lfn/VSN association remains until the file is returned by an operation such as an EVICT,
RETURN, or UNLOAD command.
Format:
VSN,lfn^vsn. ,lfn =vsn_ ,...,lfn =vsn .
i i z z n n
Parameter Description
lfni File name to be associated with vsni» This parameter is required if
parameters are specified.
vsni one or more one- to six-character volime serial nunbers to be
associated with lfni. if vsni contains nonalphanuneric
characters, it must be a literal delimited by dollar signs ($) .
vs^ Meaning
emitted An available scratch tape is automatically
assigned to lfni.
0 Same as omitted.
SCRATCH Same as omitted.
vsn =vsn=...=vsn Names duplicate volumes, any of which may be
used with lfn. .tt*
vsn /vsn /.../vsn Successive volumes to be assigned to lfni.
The system assigns volumes in the order listed.
With a VSN command you can:
e Qnit the VSN keyword from your LABEL or REQUEST commands and specify lfn/VSN
associations on the VSN command instead. This allows you to specify new VSNs
without changing LABEL or REQUEST command.
• Override the VSN specified on subsequent ASSIGN, LABEL, REQUEST, or VSN commands.
For example, the sequence
VSN,FILEA=123.
VSN, FILEA =124.
LABEL,FILEA.
tUp to 60 VSNs can be specified for a single file name in any combination of duplicate reel
and/or multireel specifications.
ttAll subsequent volumes must have the same characteristics as the first volume in the
sequence. (Characteristics include labels, track type, density, and conversion mode.) It
is recommended that all volumes be blank labeled (refer to the BLANK command) before use
in a multivolune sequence.
60459680 C 12_25
![](asset-1f2.png)
directs the system to assign FILEA to the tape with VSN 123. However, by returning
file lfn, you can specify another lfn/VSN association. Thus, the following sequence
directs the system to assign FILEA to the tape with VSN 124.
VSN, FILEA =123.
RET URN,F ILEA.
VSN, FILEA =124.
LABEL, FILEA.
Associate the VSNs of two or more duplicate volumes with one file name. For
example, the following command indicates that either the tape with VSN VOL100 or the
tape with VSN VOL101 can be assigned to FILE1.
VSN,FILE1 =VOL100«VOL101.
Specify the VSNs of a multivolume file set. For example, the following command ,^tnm\
indicates that FILE2 may extend through the three volumes identified by VSN23,
VSN24, and VSN25.
VSN,FILE2=VSN23/VSN24/VSN25.
Specify alternate volumes within a multivolume file set.
VSN,FILE3=VSNA=VSN1/VSN2/VSNB=VSN3=VSN4.
The first volume of the set can be either VSNA or VSNI. The second volume is VSN2.
The third volume can be either VSNB, VSN3, or VSN4, depending on which is available. r*=si%
12-26 60459680 C
![](asset-1f3.png)
/psfe\
CHECKPOINT/RESTART 13
A job may terminate as the result of system, operator, or programmer error. For some jobs,
it becomes more advantageous to accept the overhead of checkpoint procedures than to run the
risk of losing the entire job output. The checkpoint/restart feature is implemented through
the CKP command and the RESTART command.
NOTE
For information concerning security
restrictions associated with the use of
these commands, refer to Security Control in
section 3.
CKP COMMAND
The CKP command causes a checkpoint dump to be taken.
Format:
C K P, l f n 1 , l f n 2 , . . . , l f n n .
Parameter Description
lfni Specifies a file to be included in the checkpoint dump. If no files are
specified, all files local to the job at the time the CKP command is
processed are checkpointed.
Each time a CKP command is processed, the system takes a checkpoint dump. The dump is
written on the tape or mass storage checkpoint file specified on a REQUEST, ASSIGN, or LABEL
command with the CK or CB parameter. The dump consists of a copy of the job's field length
in central memory, the system information used for job control, and the names and position
and/or contents of all assigned files explicitly or implicitly identified by the CKP
command. These files are:
• INPUT, OUTPUT, PUNCH, PUNCHB, P8, CCCCCCO, and LGO. These files are always included
in the checkpoint dump. Procedure scratch files ZZZZZCO, ZZZZZC1, and ZZZZZC2 are
also included if present. Data files using the default names ZZCCLAA, ZZCCLAB,...,
and ZZCCLZZ are also included if present.
• Library type files, working copies of indirect access files, and some direct access
files. If one of these types of files is specified on the CKP command, it is
included in the checkpoint dump, and all other files of that type are excluded. If
no files are specified, all files of these types assigned to the job are included in
the dump.
The system does not include global library set files (ZZZZZLD and your library files) unless
you specify them on the command.
Each checkpointed mass storage file is copied according to the last operation performed on
it. If the last operation was a write, the file is copied from the BOI to its position at
check po in t tim e; o nly t ha t p or ti on i s av ailab le a t r es ta rt t im e. T he fil e i s pos it io ne d a t
the latter point.
60459680 D 13-1
![](asset-1f4.png)
If the last operation on a mass storage file was a read and the EOI was not detected, the
file is copied from its position at checkpoint time to the EOI; only that portion is
available at restart time. The file is positioned at the former point. If the last
operation was a read and the EOI was detected, no copy is performed.
The exception to this rule is the type of operation performed on execute-only direct access
files. If a dump is specified for this type of file, its name and associated system
information are copied but the contents of the file itself is not copied. Thus, if you
attempt to resume from such a dump, RESTART is unable to retrieve that file and aborts. You
can avoid this by selecting the NA and FC options of the RESTART command and retrieving the
file yourself.
When procedure scratch files are copied, they are copied from BOI to EOI.
For checkpointed magnetic tape files, only the relative position of the tape is captured so
that the tape can be properly positioned during restart. Mixed mode 7-track tapes are not
supported when using CHECKPOINT or RESTART.
If the checkpoint file is to reside on mass storage, you must include a SAVE or DEFINE
command in the checkpoint job and a GET or ATTACH command in the restart job.
If the checkpoint file is to reside on magnetic tape, care should be taken to use a labeled
or nonblank tape. An unlabeled blank tape (one which has never been used) cannot be
specified as the checkpoint file since the checkpoint program attempts to read the tape to
determine the number of the last checkpoint. The tape subsystem then aborts the job with a
blank tape read message.
The system numbers checkpoints starting at 1 and increases by 1 to a limit of 4095. At this
point, a second cycle of numbering begins, again starting at 1. An example showing how to
restart from a specific checkpoint is given in the RESTART command section.
RESTART COMMAND
The RESTART command directs the system to restart a previously terminated job from a
specified checkpoint.
Format:
RES TART, 1 f n ,nnnn ,x i.
Parameter Description
lfn
nnnn
Identifies the checkpoint file; you must have write permission to lfn.
Number of the checkpoint from which to restart; if nnnn is *, the last
available checkpoint on lfn is used; if nnnn is omitted, the first
checkpoint is used. The nnnn parameter can be obtained from the
CHECKPOINT nnnn COMPLETE messages issued to the user's dayfile in
response to CKP command.
13-2
>tS*X
60459680 C
![](asset-1f5.png)
Parameter Description
xi Any of the following in any order:
RI If this parameter is included, the command file on lfn is
not restored. The co mmand file of this restart job at its
current position is used instead.
The procedure scratch files ZZZZZCO, ZZZZZC1, and ZZZZZC2
are not restored from the checkpoint file. The values of
the symbolic names EFG, EF, RIG, Rl, R2, R3, and DSC of
this restart job are used, not the values from the
checkpoint file CPA.
If this parameter is not included, the entire command file
of the checkpointed job is restored and set to its
position at checkpoint time; any command following RESTART
is not processed.
NA If this parameter is included, RESTART does not abort if a
required file is not available. Also, if NA is included
and a read parity error occurs in an attempt to obtain a
file from checkpoint nnnn, RESTART selects checkpoint
nnnn-1 if it is available.
FC Normally RESTART restores all mass storage files included
in the specified checkpoint. This option does not restore
ZZZZZCO, ZZZZZC1, or ZZZZZC2. However, if this option is
selected, RESTART first checks if a file is already local
to the restart job. If it is, RESTART does not replace it
with the file on the checkpoint dump.
Before you enter the RESTART command, do the following:
• Assign the checkpoint file to the job. You must include a REQUEST, ASSIGN, or LABEL
command if the checkpoint file resides on magnetic tape. You can use a GET or
ATTACH command if the checkpoint file resides on mass storage.
• Assign to the job all necessary magnetic tape files to be used by the restarted
job. You can use the LABEL command.
Checkpoint dumps are numbered in ascending order from 1 to 4095. When nnnn equals 4095, the
numbering sequence begins again at nnnn equal to 1. The value of nnnn depends on the
structure of the checkpoint file, as defined by the CK and CB parameters of the REQUEST,
ASSIGN, or LABEL commands.
If CK was specified when the checkpoints occurred, each dump is appended to the checkpoint
file, and therefore, all dumps up to the time the job aborted are available for restart.
You may specify a particular checkpoint dump in the following manner.
f 60459680 C 13_3
![](asset-1f6.png)
J^^V
Assume a CK file of the name CHKFILE is being used and checkpoint number 4095 has been
passed. The job is terminated at checkpoint number 10 in the second cycle of numbering. To
restart the job from checkpoint 4 of the second numbering cycle, the following commands can
be used.
SKIPR,CHKFILE,8196.
COPYBR,CHKFILE,AA,2.
RESTART,AA...
There are two records for every checkpoint, and 4098
checkpoints must be skipped to reach checkpoint 4 of the
second numbering cycle.
The fourth checkpoint is copied to file AA. At this point,
file CHKFILE is not positioned correctly for subsequent
checkpoints. If you intend to continue checkpointing on this
fi l e , a
BKSP,CHKFILE.
command should be included.
The job is restarted from file AA using the fourth checkpoint,
If the CB parameter was specified on the ASSIGN, LABEL, or REQUEST command naming the
checkpoint file, each dump is written over the preceding dump, and therefore, only the last
dump is available. If two REQUEST, ASSIGN, or LABEL commands with CB specified are
submitted, successive dumps are alternated between two files; therefore, the last two dumps
are available .t
All files copied by RESTART are made local to the restart job. Therefore, you must make
sure that any direct access files are not lost. For example, assume that direct access
files X, Y, and Z are attached to a job. The job is then checkpointed and X, Y, and Z are
copied to the checkpoint file lfn. To retain these files as direct access files during
restart, you should include the following sequence of commands.
PURGE,X,Y,Z.
DEFINE,X,Y,Z.
RESTART,lfn,nnnn,x^.
If the information table associated with a file was included on the checkpoint file, but the
file itself was not copied, RESTART issues the appropriate commands to attempt to retrieve
the file unless one of the following is true:
• You specified the FC parameter and the file is already local to the restart job.
• The f il e resid es on magneti c tape.
tlf alternate checkpoint files are used and a read parity error occurs in an attempt to
read the last checkpoint, RESTART aborts even if the NA option was selected.
13-4 60459680 C
![](asset-1f7.png)
SYSTEM UTILITY COMMANDS 14
NOS provides the following utilities for file maintenance and screen formatting.
EDIT Edits a text file.
FSE Edits a file in line or screen mode.
KRONREF Generates a cross-reference listing of system symbols.
MODIFY Edits a Modify-formatted program library file.
OPLEDIT Removes modification decks and identifiers from a Modify-formatted program
library file.
PDU Compiles a panel definition file and loads it in a user library.
PROFILE Enables a master user to update and inquire about a profile file.
UPDATE Edits an Update-formatted program library file.
XEDIT Edits a text file.
EDIT COMMAND
The EDIT command calls the Text Editor utility. The Text Editor manipulates data on a
specified mass storage file through use of special input directives called edit commands.
For a detailed description of the Text Editor and an explanation of these commands, refer to
the Text Editor Reference Manual.
Format:
EDIT»lf*l,m,lfn2,lfn3.
or
EDIT»FN=lfnl,M=m,I=lfn2,l^lfn3.
Parameter Description
l f n i
lfn2
lfn3
60459680 C
Name of fil e t o be ed it ed (r eferred t o a s ed it fi le ). T hi s
specification is required for batch origin jobs.
Mode of file processing:
ASCII or AS ASCII mode edit file.
NORMAL or N NORMAL mode edit file.
File from which directives (edit commands) are to be read. If
omitted, INPUT is assumed.
File to which output is to be written. If omitted, OUTPUT is assumed.
14-1
![](asset-1f8.png)
FSE COMMAND
The FSE command calls the full screen editor FSE. For a complete description of the
features of FSE and its parameters and directives, refer to the Full Screen Editor User's
Guide.
Format:
FSE ,FN=filename, OP=access ,I=input, L=output ,IP=procedure,WF=workfile. directives
or
FSE,file na me ,a cc es s,inp ut ,o ut pu t, pr oce du re ,w or kfl ie .di re ct iv es
The first format is the order-independent format for parameters. The second is the
order-dependent format.
Parameter Description
FN»filename Specifies the file you want to edit. The file can be a local file or
a permanent file. The default is the file most recently edited during
your job.
OP=access Specifies the character set code and the location of the file to be
edited. The following entries are valid:
Access Abbreviation
DISPLAY
or
NORMAL
ASCII
ASCII8
GET
Description
Sel ec ts 6- bit d isp la y cod e. T hi s
is the default if your terminal is
NORMAL mode.
Selects 6/12-bit display code. This
is the default if your terminal is in
ASCII mode.
Selects 7-bit ASCII code right-
justified in a 12-bit byte.
Specifies that the file is a direct
access or an indirect access permanent
file.
I"input
L=output
To specify both a character set and the location of the file, you must
specify two values. For example, 0P=8G and OP=AG are valid.
To specify the OP=access parameter, you must also specify the
FN=filename parameter.
Specifies an input file for directives. The default is file INPUT.
Specifies an output file. The default is OUTPUT.
,*i3!Bs
14-2 60459680 D
![](asset-1f9.png)
Parameter Description
IP=procedure Specifies a file to be the FSE procedure library. The default
procedure library is FSEPROC. If file FSEPROC is not a local file,
FSE automatically retrieves it. If FSEPROC is not one of your
indirect access permanent files, FSE retrieves a copy from user name
LIBRARY.
WF=workfile Specifies a work file for FSE. The default is ZZZWORK.
directives Specifies FSE directives to be executed before FSE executes those in
the input file. Use semicolons to separate directives.
If you specify both an Input directive file (using the I=input parameter) and an output
listing file (using the L=output parameter), FSE is said to be in batch mode. When
operating in batch mode, the input directive file must be coded in 6/12-bit display code.
NOTE
When FSE is executing in batch mode, or when
the FSE command is included in a batch job,
you can significantly increase processing
efficiency by disabling UNDO processing
(using the SET UNDO directive). This action
inhibits FSE from keeping a record of each
operation performed.
r
60459680 D 14-3
![](asset-1fa.png)
KRONREF COMMAND
The KRONREF command generates a cross-reference listing of system symbols used by decks on a
Modify OPL. For output listing files not connected to your terminal, the KRONREF command
honors the page length and print density set for your job using the SET command and the PL
and PD symbolic names.
NOTE
Before entering a KRONREF command specifying
both OPL and NOSTEXT, you must enter an RFL
command to reserve sufficient memory to
contain systems text and OPL contents.
Format:
KRONREF,P=lfnx,L=lfn2,S=lfn3,G=lfn4.
Parameter Description
P=lfnj OPL input from file lfn^ If the P option is omitted or P alone is
specified, file OPL is assumed.
L = l f n 2 L i s t o u t p u t o n fi l e l f n 2 . I f t h e L o p t i o n i s o m i t t e d o r L a l o n e i s
specified, file OUTPUT is assumed.
S=lfn3 System text from overlay lfn3. The system text must contain symbol
definitions. If the S option is omitted or S alone is specified, file
NOSTEXT is assumed. If S=0 is specified, only the common deck
references and statistics are listed.
G=lfn^ System text from local file lfn$. The system text must contain symbol
defin it ion s. If G is o mi tted, sys tem t ext i s acqu ir ed as spec ifi ed or
defaulted by the S option. If G alone is specified, local file TEXT is
used. Use of the G option overrides any S specification.
The names of programs on the OPL are listed for those decks that reference the following:
PP direc t cell lo ca ti on s defined in lfn0 or lfn ,.
3 4
PP resident entry points defined in lfn~.
Monitor functions.
Mass storage table words.
Global or local file name table words and ordinals.
Central memory pointers (in low central memory) defined in lfn« or lfn,.
Central memory locations (in low central memory) defined in lfn3 or lfn,.
Control point area words defined in lfn3 or lfn,.
Executing job table, equipment status table, or queue file table.
Negative field length symbols and dayfile message options.
File types and mass storage constants.
Job origin types and queue types.
Error flags referenced.
Common deck calls.
PP packages called.
Special entry points.
14-4 60459680 E
![](asset-1fb.png)
MODIFY COMMAND
The MODIFY command edits a Modify-formatted program library file. For output listing files
not connected to your terminal, the MODIFY command honors the page length and print density
set for your job using the SET command and the PL and PD symbolic names.
Format:
MODIFY,Pl,p2,...,pn.
The following optional parameters can be specified in any order.
Pi Description
A Write the compile file in compressed format.
C=lfni Write compile output on lfni. If vou specify only C or omit this
parameter, lfni is COMPILE. C=0 results in no compile output.
CB=lfn2 Write binary output on lfn2. This parameter is equivalent to the
B=Ifn parameter on a compiler or assembler call command. If you
specify only CB or omit this parameter, LGO is the binary output
file. CB=0 produces no binary output. This parameter is meaningful
only if you specify the Q=processor or X=processor parameter.
CG=lfn3 Load system text from lfn3. This parameter is equivalent to the
G=lfn parameter on a compiler or assembler call command. Load system
text from SYSTEXT. CG=0 loads no system text. By default, the system
uses the CS=lfn5 parameter. You must specify the Q=processor or
X=processor parameter if the CL=lfn3 is to be meaningful.
CL=lfn4 Write full listing on lfn4« CL=lfn4 is equivalent to the L=lfn
parameter on a compiler or assembler call command. If you specify
only CL, OUTPUT is the list file. If you omit this parameter or
specify CL=0, a short listing is written on OUTPUT. This parameter is
meaningful only if you specify the Q=processor or X=processor
parameter.
CS=lfn5 Take system text from lfn5« This parameter is equivalent to the
S=lfn parameter on a compiler or assembler call command. If you omit
this parameter or specify only CS, the system text is taken from
SYSTEXT overlay. CS=0 produces no system text. This parameter is
meaningful only if you specify the Q=processor or X=processor
parameter.
CV=cv Convert the library to the character set specified by cv (63 or 64).
By default, no conversion occurs.
NOTE
When the CV=63 or CV=64 parameter is speci
fied, Modify prevents compile file genera
tion (C=0).
60459680 F 14-5
![](asset-1fc.png)
Pi Description
D Do not abort the job on a directive error. This parameter does not
affect fatal error processing. By default, the job aborts on a
directive or fatal error.
F E d i t a l l d e c k s o n t h e l i b r a r y a n d w r i t e t h e m o n n e w p r o g r a m l i b r a r y ,
compile file, and source file if the respective options are selected.
By default, the U parameter or EDIT directives determine the decks to
be edited.
I=lfn0 Take directives from next record on lfnD. INPUT is the default.
The system reads no directives if you specify 1=0.
L=lfn7 Write list output on lfny. OUTPUT is the default. L=0 generates no
list output file.
L0=cic2...cn Select list options c^. In an interactive job, the default
is L0=E if the lis t outp ut file is as si gn ed to the t er mi na l.
Otherwise, the default is L0=ECTMWD. You can specify a maximum of
seven list options Ci» .
Ci Significance
A Active lines in deck.
C Directives other than INSERT, DELETE, RESTORE, MODNAME,
I, or D.
D Deck status.
E Errors.
I Inactive lines in deck.
M Modifications performed.
S Statistics.
T Text input.
W Compile file directives.
Example: LO=EMS
N=lfn8 Write new program library on lfng. If you specify only the keyword
N, the system uses file NPL. If you omit this parameter or specify
N=0, the system generates no new program library.
NOTE
If a new program library is being generated,
the system performs an evict operation on
the file specified by the N=lfn8 parameter.
14-6 60459680 D
/£^!\
![](asset-1fd.png)
Pi Description
NR Do not rewind compile file. By default, the system rewinds compile
file at beginning and end of Modify run.
P=lfnQ Take program library input from Ifno. If you do not specify a file,
the system takes the input from OPL. P=0 results in no input file for
the program library.
Q=processor Set LO=E and the A parameter at the beginning of the Modify run and
call the assembler or compiler specified by processor at the end of
the run. The system does not rewind the directives file or the list
output file. If you do not specify this parameter or specify Q=0, no
call is made to an assembler or compiler.
If you specify only the keyword Q, the system sets LO=E and the A
parameter at the beginning of the Modify run and calls the COMPASS
assembler at the end of the run. When this option is selected, the
CB=lfn2, CL=lfn4, CS=lfn5, and CG=lfn3 parameters are
meaningful. Compiler input is assumed to be COMPILE. All other
parameters are set by default. If CL is not specified with Q, lines
beginning with an asterisk in column 1 are not written to the compile
file (compile file directives are processed).
S=lfniQ Write source output on file lfniQ. If you specify only the keyword
S, the file SOURCE is used. If you omit this parameter or specify
S=0, the system generates no source output file.
Do not specify this parameter if you specify the A, Q=processor, or
X=processor parameter.
U Edit only decks for which the directives file contains deck directives
and write them on the compile file, new program library, and source
file (if their respective parameters are selected). F, if specified,
takes precedence. By default, decks to be edited are determined by
EDIT directives or by the F parameter.
r X P r o c e s s t h e s a m e a s Q = p r o c e s s o r p a r a m e t e r , e x c e p t t h a t m o d i f ydirectiv es inp ut (I par am et er) a nd lis t outpu t (L pa rameter) files ar e
rewound before processing.
Z Read the input directives following the terminator of the MODIFY
command; the input file is not read. This eliminates the need for a
separate input file for the directives when only a few directives are
needed. 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. The directives can
extend to column 80 on the command. Continuation lines are not
permitted. If Z is omitted, the command does not contain the input
directives.
NOTE
Do not place another terminator after the
directives.
For a detailed description of the Modify utility, refer to the Modify Reference Manual.
60459680 D 14_7 I
![](asset-1fe.png)
OPLEDIT COMMAND
The OPLEDIT command removes modification decks and identifiers from a Modify-formatted
program library file. For output listing files not connected to your terminal, the OPLEDIT
command honors the page length and print density set for your job using the SET command and
the PL and PD symbolic names.
Format:
OPLEDIT,Pi,p2,...,pn.
Pi Description
I=lfni Use directive input from file lnfi. Take Input directives from file
lfni. INPUT is the default. 1=0 indicates that there are no input
directives.
P=lfn2 Use file lfn2 for the old program library. Use file lfn2 for the
old program library. OPL is the default. P=0 indicates that there is
no old program library.
N=lfn3 Write new program library on file lfn3. Write the new program
library on lfn3. If you specify only the keyword N, NPL is used.
If you omit this parameter or specify N=0, the system writes no new
program library.
L=lfn4 List output on file lfn4» Place list output on file lfn4. OUTPUT
is the default. L=0 generates no list output.
M=lfn5 Write output from *PULLM0D directives on file lfns. If this option
is omitted, M=M0DSETS is assumed.
L0=cic2...cn Selects up to five list options Ci.
flDescription
EErrors.
CInput directives.
MModifications made.
DDeck status.
SStatistics.
If this parameter is omitted or just LO is specified, it selects all
lis t op tio ns . I f th e o ut put fi le i s ass ig ne d t o the t er min al in a
interactive job and this parameter is omitted or just LO is specified,
list option E is selected.
/eS5S\
14-8 60459680 D
![](asset-1ff.png)
0 W \
Pi Description
F Modify all decks.
D Debug; ignore errors.
U
U=0
Generate *EDIT directives for all decks; meaningful only for *PULLMOD
executions.
Generate no *EDIT directives. If the U option is omitted, generate
*EDIT directives for common decks. This is meaningful only for
*PULLMOD execution.
Read the input directives that follow the terminator. The input file
is not read. This eliminates the need to use a separate input file
for the directives wh en only a few directi ves are needed. The first
character following the command terminator is the separator
character. If Z is omitted, the command does not contain the input
directives.
| NOTE
Do not place another terminator after the
directives.
For a complete description of the OPLEDIT utility, refer to the Modify Reference Manual.
60459680 D 1 4 - 9 |
![](asset-200.png)
/<<^%y
PDU COMMAND
The PDU command compiles a panel definition file and stores the compiled panel in a user
library. Refer to the NOS Screen Formatting Reference Manual for information on panels.
Format:
PDU,I=panel,L=listing,C=capsule,LIB=library.
or
PDU,panel,listing,capsule,library.
The first format is the order-independent format for the parameters. The second is the
order-dependent format. Only the first parameter is required.
Parameter Description
I=panel Specifies the name of the panel definition file. The file must be
local. You must specify this parameter.
This file name is the same as the panel name and will be the record
name of the panel in the user library.
L=listing Specifies the name of the listing file. The default is OUTPUT. If
you specify L=0, no listings are generated.
C=capsule Specifies the name of the capsule file, the file on which the system
writes the compiled panel. The default is CAPSULE. If you specify
C=0, no capsule is generated.
LIB=library Specifies the name of the local file to receive the capsule. The
default user library is PANELIB. If you specify LIB=0, the system
does not store the compiled panel in a user library.
The PDU command is an interactive procedure. Hence, you can get help information for the
command and its parameters and be prompted for parameters. If you enter
PDU?
the system gives you information about the command itself and prompts you for parameters.
If you enter
PDU,parameter?
the system gives you information about the specified parameter and prompts you for
parameters.
14-10 60459680 C
![](asset-201.png)
PROFILE COMMAND
The PROFILE command enables the master user to update and inquire about a project profile
file for user profile control. Other capabilities of PROFILE (available only to system
origin jobs) are described in the NOS 2 Administration Handbook. For output listing files
not connected to your terminal, the PROFILE command honors the page length and print density
set for your job using the SET command and the PL and PD symbolic names.
Format:
PROFILE,Pl,p2,...,pn.
The following optional parameters can be specified in any order.
I=lfn
L=lfn2
P=lfno
Meaning
Fi le l fni co ntai ns i np ut d ire ctiv es f or a n up date (O P=U ). I f
omitted, file INPUT is assumed.
File lfn2 receives output listings. If omitted, OUTPUT is assumed.
File lfn3 is the project profile file. If omitted, file PROFILC is
assumed.
CN=cn Charge number inquiry. All project numbers valid for charge number cn
are written to output file. Valid only if OP=I option specified.
PN=pn Project number inquiry. The control values and all valid user names
for project number pn are written to the output file. The OP=I and
CN=cn options must also be specified to use the PN option.
CV Convert option. Builds a source file from NOS 2.2 PROFILC.
Suppresses project prologue and epilogue directives. This parameter
is only meaningful with OP=S.
OP=opt PROFILE processing option. One of the following:
opt Description
L Lists portions of the profile file as specified by the
LO=op parameter.
U Updates the project profile file with directives supplied
by the i np ut file . U is the d ef au lt val ue for t he master
user if the OP option is omitted.
T Interactive update. Processing is the same as OP=U, but
preliminary instructions are suppressed.
I Inquire option. Output is dependent upon the CN or PN=pn
parameter specified.
S Specifies that the profile file is to be written in source
format (directive images) and placed on the source file
(specified by S=source parameter). The source file can be
used as the input for a later create or update session.
60459680 H 14-11
![](asset-202.png)
Pl Meaning
LO=op PROFILE list option (OP=L must be specified). One of the following:
QP Description
CM
PM
FM Full list of everything accessible on the profile file by
the master user. This is the default for a nonsystem
origin job if the LO=op parameter is omitted.
Charge number list of all charge numbers accessible on the
profile file by the master user.
Project number list of all project numbers accessible on
the profile file by the master user.
Directives are available to the master user as input to PROFILE to add or update information
concerning each charge number. The input file for a PROFILE update (OP=U) is divided into
groups of entries that each begin with a charge number directive. Each directive following
a particular charge number entry applies only to that charge number, until another charge
number entry occurs.
Each line of the input file can contain one or more directives (up to 72 characters per
li ne) i n th e fol low ing fo rm at.
diri,dir2 dim
Each directive is separated by a delimiter which can be any special character (display code
greater than 448) exCept the following:
/ + - * :
An end-of-line or end-of-card also delimits directives. The following directives are
available to the master user for PROFILE input.
dlri Description
APN=pn Adds or activates project number pn.
AUN=un Adds user names un (must be preceded by PN directive).
/cn Specifies the charge number cn to which the following directives
apply. If this form of charge number specification is used (refer to
CN=cn directive), it must begin in column 1 with the slant (/).
CN=cn Same as /cn except that it can begin in any column.
D PN = p n D e ac t i va t e s p r oj e c t n umb e r p n . Thi s d i r ect i ve d oe s n ot d e let e t h e
specified project number entry but sets its status such that it cannot
be specified by users.
DUN=un Deletes user name un from the list of those who may access the project
number (must be preceded by PN directive).
EFN=fn Specifies the indirect access permanent file that contains the
epilogue to be associated with the specified project. The epilogue
can be a procedure or a binary program. A null entry, which is the
default, clears the project epilogue.
14-12 60459680 C
z^^t\
![](asset-203.png)
d i r Description
EPW=pw
EUN=un
ISV=x
PCR=option
PEX=yymmdd,
PFN=fn
PN=pn
PPW=pw
PUN=un
SMA=acc
SML=lim
Specifies the file password associated with the project epilogue
file. A null entry, which is the default, indicates that no password
is asso ci at ed wi th th e fi le.
Specifies the user who owns the project epilogue file. A null entry,
which is the default, indicates that the owner of the project epilogue
file is the user on whose behalf the epilogue is to run.
Sets x as the maximum SRU accumulation for any job using the charge
number and project number specified by preceding CN and PN directives.
Defines the conditions under which the system sets a charge-required
state after the project prologue executes. You can specify one of the
following values:
Option Description
U Set a charge-required state unconditionally.
A Sets a charge-required state only if the project
prologue aborts.
n u l l D o e s n o t s e t a c h a r g e - r e q u i r e d s t a t e . T h i s i s t h e
default.
Specifies expiration date for project number of preceding PN
directive. If PEX=0 is entered, the project number is not limited by
an expiration date.
Specifies the indirect access permanent file that contains the
prologue to be associated with the specified project. The prologue
can be a procedure or a binary program. A null entry, which is the
default, clears the project prologue.
Project number for which the following directives (until the next PN
directive) apply.
Specifies the file password associated with the project prologue
file. A null entry, which is the default, indicates that no password
is associated with the file.
Specifies the user who owns the project prologue file. A null entry,
which is the default, indicates that the owner of the project prologue
file is the user on whose behalf the prologue is to run.
Sets the current number of accumulated SRUs the project number has
used (PN directive required). This accumulator is updated at the end
of a job or terminal session and each time a CHARGE command is
entered. When the SMA value surpasses the SML value, the project is
not available to users until either the limit or accumulator is
respecified.
Specifies the maximum number of accumulated SRUs the project (PN
directive) may use. SML=0 implies no restriction.
/f|P^\
60459680 C 14-13
![](asset-204.png)
diri Description
TI=ti Specifies the time of day before which the project number specified by
the PN directive cannot be used. The time is specified in 24-hour
clock notation. For example, a ti specification of 1315 indicates the
project number cannot be used before 1:15 in the afternoon.
TO=to Specifies the time of day after which the project number specified by
the PN directive cannot be used. The time is specified in 24-hour
clock notation. For example, a to specification of 1315 indicates
that the project number cannot be used after 1:15 in the afternoon.
UPDATE COMMAND
The UPDATE command creates, edits, or copies an Update-formatted program library file. For
complete information on Update directives and processing, refer to the Update Reference
Manual.
Format:
UPDATE,Pl,p2,...,pn.
The parameters are optional and can be specified in any order.
For file-specifying parameters (those associated with the keywords C, G, I, K, N, 0, S, or .s^h
T), you can append either the digit 6 or 8 (but not both) to the keyword. Each
file-specifying parameter has its own default for the character code set of the file (refer
to Character Sets in appendix A). The digit 6 or 8 overrides this default. The digit 6
directs the system to represent the file in the 6-bit display code set. The digit 8 directs
the system to represent the file in the 7-bit ASCII code set.t However, the system uses the
ASCII code set only if the digit 8 is appended to the keyword and if the input file is also
represented in the 7-bit ASCII code set. For example, C8=FILE directs the system to write
the decks on the compile file FILE in the ASCII code set.
Pi Description
A Copies the old sequential access program library to a new random
access program library.
B Copies the old random access program library to a new sequential
access program library.
C=lfni Specifies the compile file. Unless otherwise specified, the compile
file has the same character code set as the old program library.
C=PUNCH implies the D and 8 parameters. C=0 implies no compile file.
If you omit this parameter or specify the keyword only, COMPILE
becomes the compile file. If you specify the K=lfnj parameter, the
C=lfni parameter is ignored.
tThe digit 8 directs the system to represent the file in the 6/12-bit display code set if
the job is interactive and the file is an input or output file.
14-14 60459680 C
![](asset-205.png)
/g^K
r
Pi Description
D Sets the width of the compile file to 80 characters. The default is
72.
E Edits the old program library. To completely edit the library,
specify the E parameter on two UPDATE commands. The first occurrence
of the E parameter causes the system to rearrange the directory to
reflect the actual order of the decks on the library and to remove
previously purged identifiers. The second occurrence of the E
parameter causes the system to remove the identifiers that exist only
as directory entries.
F Specifies full Update mode.
G=lfn2 Specifies the output file for the PULLMOD directive. Unless otherwise
specified, the character code set of lfn2 is the same as that of the
old program library. If you do not specify lfn2^ the output from
the PULLMOD directive is appended to the source file (specified by the
S=lfn8 parameter).
H=n Specifies whether a 63- or 64-character character set is to be used in
the Update run.
n Description
3 A 63-character character set.
4 A 64-character character set.
omitted Character set that was used in the old program library.
I = l f n 3 S p e c i fi e s t h e p r i m a r y i n p u t fi l e . T h e d e f a u l t i s I N P U T. T h e d e f a u l t
character code set is 6/12-bit ASCII code if INPUT is associated with
the terminal. Otherwise, it is display code.
K=lfni Specifies the compile file and specifies that the decks are written to
that file in their order of appearance in the COMPILE directives. The
default is file COMPILE. The default character code set is 6-bit
display code.
/gP^N
60459680 C !4_15
![](asset-206.png)
/^s^s^v
Pi Description
L=clc2...cn Specifies one or more of the following list options.
Ci List Options
A Lists deck names and correction set identifiers, COMDECK
directives, definitions, and decks written on the compile
file.
F Uses all list options except 0.
0 Suppresses all listing.
1 Lists lines in error.
2 Lists active Update directives.
3 Notes on each line that changed status during current
execution.
4 Lists text lines.
5 Lists active compile file directives.
6 L i s t s a c t i v e a n d i n a c t i v e l i n e s .
7 Lists all active lines.
8 Lists all inactive lines.
9 Lists correction history of all lines selected by list
options 5, 7, and 8.
The default depends on the nature of the Update processing. For a
creation run, the default is options A, 1, and 2. For a correction
run, the default is A, 1, 2, 3, and 4. For a copy run, the default is
A and 1.
M=lfn4 Merges lfn4 and the old program library. If you specify only the
keyword M, the system merges the file MERGE and the old program
library. The two libraries must have the same character code set. If
the parameter is omitted, no merging occurs.
N=lfn5 Specifies the new program library. If you do specify a new program
library on a correction run, no new program library is generated.
Otherwise, the default is the file NEWPL. The default character code
of the new program library is the same as that of the old program
library unless the primary input file is in 7-bit ASCII code and the
old program library is in 6-bit display code. In this case, the
default is the 7-bit ASCII code set.
14-16 60459680 C
![](asset-207.png)
Pi Description
0=lfn6 Specifies the output file. The default is OUTPUT. The
default character code is the same as that of the old program
library.
P = l f n 7 / s 1 / s 2 / . . . / s 7 S p e c i fi e s fi l e l f n 7 a s t h e o l d p r o g r a m l i b r a r y. I f j u s t
the keyword P Is specified, file OLDPL is assumed. If
sl /s2 /.. ./s 7 is s pec ified , se co ndar y ol d prog ram
libraries will reside on files si,s2 s7.
Q Processes only decks on COMPILE directives (quick mode).
R=clc2...c4 Rewind specified files before and after the Update run.
fi Files
C Compile file.
N New program library.
P Old program library and merge library.
S Source and PULLMOD files.
If Ci is omitted, no files are rewound. If
R=clc2...c4 is omitted, the old program library, new
program library, compile file, source file, and PULLMOD file
are rewound.
S=lfn8 Specifies the name of the source file. If you specify the
keyword only, the file SOURCE becomes the source file. If you
omit the parameter, the system does not write a source file
unless you specify the T=lfn8 parameter. The default
character code set of the source file is the same as that of
the old program library.
r T = l f n 8 F u n c t i o n s t h e s a m e a s t h e S = l f n 8 p a r a m e t e r , e x c e p t t h a t i texcludes common decks from the source file. This parameter
takes precedence over the S=lfn8 parameter.
U Specifies that Update processing is to continue even if
normally fatal errors occur.
W The new program library is written in sequential access
format. If W is omitted, the new program library is written
in random access format unless the file is on magnetic tape.
X Writes the compile file in compressed format. If X is
omitted, the compile file is not compressed.
8 Writes compile file output as 80-character line images. If 8
is o mit ted , the com pil e file is wri tte n as 9 0-c har act er li ne
images.
60459680 C 14_17
![](asset-208.png)
Pi Description
* = c h a r T h e m a s t e r c o n t r o l c h a r a c t e r ( fi r s t c h a r a c t e r o f e a c h d i r e c t i v e ) f o r
this Update run is char, which can be any character having a 6-bit
display code octal value in the range 01 through 54 except for 51 and
52 (the open and close parentheses). If this option is omitted, the
master control character is *.
/=char The comment control character for this Update run is char, which can
be A through Z, 0 through 9, or + -*/$=. The character should not be
changed to one of the abbreviated forms of the directives unless
NOABBREV is in effect. If this option is omitted, the comment control
character is a slant bar.
XEDIT COMMAND
The XEDIT command calls the text editor, XEDIT. For a complete description of XEDIT
parameters and directives, refer to the XEDIT Reference Manual.
NOTE
When XEDIT encounters lines longer than 150
characters it truncates those lines without
warning; therefore, you should use caution
when calling XEDIT to edit a file that may
contain lines longer than 150 characters or
when editing an ASCII file in NORMAL mode.
Format:
XEDIT,lfni»Pl»P2»•••,Pn*directives
All parameters are optional. The following are brief parameter descriptions.
Parameter
l f m
Description
Use lfni as ttie name °f the file to be edited or created. If lfni
is omitted (indicated by two separators before other parameters), the
p rim a r y fi l e i s e dit e d .
Pi
AS
B
C
FR
Description
Edit lfni in ASCII interactive mode. After the
XEDIT job step, processing returns to the original
mode.
Process the job as a batch origin job.
Create a new file lf^.
Take the first editing directive from the first line
of lfn^.
14-18
y^ffiiSv
60459680 D
![](asset-209.png)
Parameter Description
Pi Description
/ 0 ^ \
I=lfn2 Take editing directives from lfn2. By default,
di rec tiv es a re ta ken fr om fil e INPU T. If y ou s pec ify
1=0, the sy stem takes a ll directives from the tr ailing
delimited directive sequence. (If the FR parameter is
also specified, the system processes the delimited
directive sequence after processing directives from
the first line of lfni.)
L=lfn3 Put all XEDIT output on the specified file. OUTPUT is
the default. If you specify L=0, the system
suppresses all output.
NH Suppress printing of the XEDIT header.
P R e t r i e v e a n d e d i t p e r m a n e n t fi l e l f n i . D i r e c t
access files are attached in write mode. If P is
om it ted , the fil e lfn i Is a ssu me d to b e a lo cal fi le.
directives Process the directives that follow the command terminator. The first
ch ar ac te r th at f ol lo ws th e te rm in at or d el im its th e di re ct iv es. T he
value directives has the following form (the semicolon serves as the
delimiter):
;directivei;directive2;...; directiven
Do not place a terminator after the last directive.
60459680 D i4_19 I
![](asset-20a.png)
//?s?^%
![](asset-20b.png)
j 0 ^ \
LIBRARY MAINTENANCE 15
/f*Qb*\
jg^3\
A library is a file containing records that are accessed individually. This section
describes the creation and maintenance of user libraries. User libraries are not to be
confused with program libraries. User libraries are created using the LIBGEN, ULIB, PDU, or
TDU commands. A user library can be named in an LDSET or a LIBRARY command to establish a
lo ca l or g lob al li bra ry se t. Pro gra m lib rar ies a re sou rce c ode libr ari es , crea ted and
edited using either the MODIFY utility or the UPDATE utility.
This section describes file access methods, library record types, and the following commands
and their functions.
Command
CATALOG
COPYL and COPYLM
GTR
ITEMIZE
LIBEDIT
LIBGEN
LIBRARY
ULIB
VFYLIB
Function
Describes the records on a file.
Copies an old file to a new file, updating the records from a
replacement file.
Appends records selected from one file to another file.
Describes the records on a file.
Generates a file containing records from one or more other
files. The records may be of several types.
Generates a user library; that is, a library of relocatable,
capsule, absolute, CP overlay, or procedure file records that can
be accessed by CYBER Loader.
Sp ec ifi es a gl ob al l ib rary se t for t he j ob .
Creates or modifies a local copy of a user library.
Compares the records in two files and lists their differences.
With the exception of CATALOG and ITEMIZE, we do not recommend using these commands on files
structured by CYBER Record Manager (CRM). Because of certain incompatibilities with NOS
file structures, the output from these commands may not accurately reflect the CRM file
structure.
LIBRARY FILE ACCESS METHODS
The methods used to access records within NOS files are sequential access and random access.
To access a record sequentially, NOS rewinds the file to BOI and then reads records until it
finds the requested one. To replace, insert, or delete records from a sequential access
file, NOS must rewrite the entire file. (Records can be appended at EOI without rewriting
t h e fi l e . )
60459680 E 15-1
![](asset-20c.png)
RELATIVE
PRU
ADDRESS
1record.
a
recordg
14 DIRECTORY CONTENTS
1/
record?
NAME LENGTH ADDRESS
record.
23 directory records 17
record?
Figure 15-1. Random Access File Structure
To access a record randomly, the file must be on mass storage and must have a directory
containing the address of each record (figure 15-1). The GTR, LIBGEN, and LIBEDIT commands
can generate random access directories. Records within a file can then be replaced,
inserted, or deleted by rewriting the directory instead of rewriting the entire file.
Records within a random access file can also be accessed sequentially.
LIBRARY RECORD TYPES
NOS determines the type and the name of a record from information contained within the
record. If the record begins with a prefix table, the record name (if any) is obtained from
that table and the type of the record is determined from the first word following the prefix
table. Otherwise, the first word of the record determines the type and name (if any) of the
record.
Prefix tables exist, unless they have been specifically suppressed, for:
• Assembled or compiled programs.
• S y s t em t e xt o v e rla y s .
• User library header records and directory records.
• Modify program library decks, common decks, or directory records.
The prefix table consists of a header word with an octal table type identifier followed by
varying amounts of control information.
The prefix table is identified by octal digits 7700 in bits 59 through 48 of its first word;
consequently, it is often referred to as a 77 or 7700 table. Information in the prefix
table, which originates with the assembler, compiler, or other program that creates the
table, can specify items such as the date created and the system on which the job was
processed (refer to CYBER Loader Version 1 Reference Manual).
15-2 60459680 D
![](asset-20d.png)
If a prefix table is not present, the first word in a record is examined. If a record meets
th e c ri te ri a f or a given t yp e o f re co rd , t he ut il it ie s i de nt if y i t as such. F or instance, a
load file beginning with a Job command may be identified as type TEXT, depending on the
particular characters in the Job command.
Although some of the records may contain display coded data (loader directives, for
instance, are coded), they are considered binary records.
The following record types can be specified on the COPYX, GTR, and LIBEDIT commands and are
recognized by the CATALOG and VFYLIB commands. You determine the record types contained in
a file by issuing a CATALOG command naming the file. VFYLIB lists the differences between
the record types of two files. LIBGEN generates a user library from relocatable (REL)
capsule (CAP), absolute (ABS), CP overlay (OVL), or procedure file (PROC) records.
Mnemonic Meaning
ABS Multiple entry point overlay.
CAP CYBER Loader capsule.
OPL Old program library deck created by Modify.
OPLC Old program library common deck created by Modify or LIBEDIT.
O PLD O l d p r og r a m l i b ra r y d i r e ct o r y c r eat e d b y M odi f y o r L IB E D IT.
OVL Central processor overlay.
PP Peripheral processor program.
PPU Peripheral processor unit program.
PROC Procedure file.
REL Relocatable central processor program.
TEXT Unrecognizable as a program.
ULIB User library directory.
The following record types are recognized by COPYL, COPYLM, and ITEMIZE commands. Record
types ACF, OPLD, UCF, ULIB, and UPLx are recognized by the ITEMIZE command but are not
recognized by COPYL or COPYLM.
Mnemonic
ABS
ACF
CAP
OPL
OPLC
Meaning
Multiple entry point overlay.
Modify compressed compile file. It has no record name. This record type
is determined by a nonzero value in bits 17 through 0 in the second word of
the 77 table.
CYBER Loader capsule.
Old program library deck created by Modify.
Old program library common deck created by Modify.
/#^N
60459680 H 15-3
![](asset-20e.png)
/ ^ ^ \
Mnemonic
OPLD
OVCAP
OVL
PROC
REL
TEXT
UCF
ULIB
UPLx
6PP
7PP
Meaning
Old program library directory created by Modify or LIBEDIT,
Overlay capsule.
Central processor overlay.
Pro ce du re file .
Relocatable user program.
Unrecognizable as a program.
Update compressed compile file. It has no record name,
is determined by a 77 table with a zero word count.
User library directory.
This record type
Update sequential program library with x master control character. It has
no record name. This record type is determined by no 77 table and the
characters CHECK in bits 59 through 30; control characters are obtained
from bits 5 through 0.
Peripheral processor program.
Peripheral processor program.
Appendix G in Volume 4, Program Interface, contains the formats of PP (6PP), OPL, OPLD,
ULIB, and TEXT records. (The OPLC record format is identical to that of the OPL record.)
The Modify Reference Manual describes how to create ACF, OPL, OPLC, and OPLD records. The
CYBER Loader Reference Manual contains the formats of ABS, CAP, OVCAP, OVL, PP, and REL
records. The CYBER Loader Instant contains the PPU (7PP) record format. The Update
Reference Manual contains the formats of UCF and UPLx records. Section 4 describes the
creation of procedures (PROC).
15-4 60459680 F
![](asset-20f.png)
CATALOG COMMAND
The CATALOG command lists information about each record in a file assigned to the job. The
record types recognized by CATALOG are listed in Library Record Types in this section.
NOTE
0**»\
CATALOG produces unpredictable results when
attempting to catalog an S, L, or F format
tape. Use the COPY command to convert the
S, L, or F format tape to a mass storage
file or to an I or SI binary format tape
before attempting to catalog the file.
Format:
CATALOG,lfn,p1>p2^#^pn^
Parameter Description
l f n S p e c i fi e s t h e fi l e t o b e c a t a l o g e d . T h e d e f a u l t i s F I L E .
Pi Pi can be any of the following:
Pi Description
N=n Catalogs n files. If n is 0, the system catalogs the
file until an empty file is encountered (two consecutive
EOFs). If you specify only the keyword N, the system
catalogs until it encounters the EOI. The default is
N=l.
L=fname Specifi es the name of th e output file; if L=fname i s
omitted, CATALOG assumes L=0UTPUT.
T L i s t s t h e e n t i r e t e x t r e c o r d i f t h e r e c o r d n a m e b e g i n s
with any of the following characters:
APRD IPRD
CMRD LIBD
EQPD
If you omit T, the system does not list the contents of
the text record. If the text record name begins with
OVERLAY, the system always lists the first line of the
record.
U L i s t s a l l r e c o r d s w i t h i n a u s e r l i b r a r y . I f fi l e l f n i s
a user library and you omit U, CATALOG lists only the
ULIB record.
D Suppresses the comments field; suppresses all page
headings after the initial page heading for each file.
CS Suppresses character set indicator (63 or 64) for OPL
and OPLC records.
Rewinds lfn before and after cataloging; if R is
omitted, lfn is not rewound.
60459680 C 15-5
![](asset-210.png)
The listing for each file of a multifile file begins on a new page with a page heading for
that file. If the D option has been specified, the page heading appears only once, at the
beginning of the file. For CATALOG listing files not connected to a terminal, you can
control the print density and page length using the SET command and the PL and PD symbolic
names. The information listed under each heading is as follows:
Heading
REC
NAME
TYPE
LENGTH
CKSUM
DATE
Information
Record number (zero-length records and EOF marks are counted).
Record name [the contents of the name field from the second word of the
prefix (77) table, if present; otherwise, the first seven characters of
the record]. For ABS and REL records, the entry points are listed
beneath the record name.
Record type (refer to Library Record Types in this section).
Record length in words, printed as an octal number. For TEXT records,
this includes the prefix table length. For PROC records, this contains
the act ual r eco rd le ngt h. For oth er rec ord typ es, the pre fix tabl e
length is not included.
A checksum (that is, a value used to verify that the contents of a
record were copied correctly). Except for TEXT records, the checksum
does not verify the contents of the prefix table.
Record creation date (taken from the third word of the prefix table, if
present).
COMMENTS Comments are taken from the comments field of the prefix table. A zero
byte or a COPYRIGHT comment in the comments field of the table
terminates the listing. This field is not shown when CATALOG Output is
as si gned to a t erm in al fi le .)
CATALOG lists additional information depending on the record type. Entry points are listed
for REL and ABS records. The character set used, correction identifiers, and their YANK
status (refer to the Modify Reference Manual) are listed for OPL and OPLC records.
NOTE
When printing output for text files, CATALOG
uses the first seven characters of the first
word of the record as the record name.
CATALOG assumes that the record is in 6-bit
display code. Therefore, if you attempt to
display CATALOG output for a record in 6/12
display code while your terminal is in ASCII
mode, the output display may be garbled. To
avoid this problem, you should set your
terminal to NORMAL mode before listing
CATALOG output.
A ULIB record suppresses listing of the other records in the user library unless the U
parameter is specified on the command.
If an OPLD record in the user library is not encountered before an EOF or EOI within the
cataloged file, the following message is output before the *EOF* or *EOI* line.
*OPLD MISSING*
15-6 60459680 E
![](asset-211.png)
When a zero-length record is encountered, the length since the last zero-length record is
given. If an EOR does not precede an EOF or EOI within the cataloged file, the following
message is output before the *EOF* or *EOI* line.
*EOR MISSING*
The ITEMIZE command is similar to the CATALOG command, but ITEMIZE recognizes additional
record types (refer to Library Record Types, earlier in this section).
Example:
Compilation of the FORTRAN program SUBROUT and its subroutines SUBl, SUB2, and SUB3 wrote
relocatable object code on file LGO. The following is a catalog of file LGO (refer to the
heading definitions given earlier).
:c CATALOG
NAME
OF LGO
TYPE
FILE
LENGTH CKSUM DATE
1
2
SUBROUT
SUBROUT
A
A
REL
REL
44
41
6215
7424
yy/mm/dd
yy/mm/dd
3B
Q
REL 41 0465 yy/mm/dd
4C
C
REL 41 5525 yy/mm/dd
* EOF * SUM = 207
COPYL AND COPYLM COMMANDS
The COPYL and COPYLM commands copy an old file to a new file, substituting records from a
replacement file for the matching records on the old file. Records on the replacement file
which do not match records on the old file are either ignored or appended to the new file
/#^v according to your parameter specifications. Records are considered to match if they have
' the same type and same name. However, you may specify that the record type be ignored.
COPYL and COPYLM are commonly used to maintain files of procedures or relocatable records.
COPYL and COPYLM differ only in the handling of multiple occurrences of a record on the old
file. COPYL uses each record on the replacement file only once, replacing the first
matching record from the old file. COPYLM uses the first matching record encountered on the
replacement file to replace each matching record from the old file. COPYL can be used to
replace multiple occurrences of the same record if multiple occurrences of the record are in
the replacement file.
The old file and the replacement file must reside on mass storage or an I or SI format
tape. Only a single file terminated by an end-of-file marker is processed by a single call
to COPYL or COPYLM unless you request processing to the end-of-information by using the E
processing option. When working with multifile files, you must be sure to position the
multifile file to the file that is to be processed.
The order of the records on the replacement file is not significant. The system copies the
records to the new file in the same order as they are on the old file.
60459680 D 15-7
![](asset-212.png)
COPYL and COPYLM issue dayfile messages during processing; no other printed output is
produced. The dayfile messages list which replacement records were copied and which
replacement records were not copied to the new file.
COPYL and COPYLM replace only the types of records listed in Library Record Types, earlier
in this section. Any record on the old file that is not recognized as one of the listed
types is copied to the new file without further processing. Any replacement file record
type that is not listed in Library Record Type, is ignored without comment.
Format:
COPYL,oldlfn,replfn,newlfn,last,flag.
or
COPYLM,oldlfn,replfn,newlfn,las t,flag.
Single replacement,
Multiple replacement.
All parameters are optional and order-dependent. You denote an omitted parameter by
consecutive commas.
Parameter
oldlfn
r e p l f n
newlfn
last
fl a g
Description
File name of the old file; default name is OLD.
File name of the replacement file; default name is LGO.
File name of the updated file; default name is NEW.
Name of the last record on oldlfn to be processed. If last is not
specified, all records on oldlfn are processed from its current
position to the next EOF (or EOI if the E processing option is used).
Processing options.
fl a g
R
Description
(The
Rewind oldlfn and newlfn files before processing,
replfn file is always rewound before and after
processing, oldlfn and newlfn are not necessarily rewound
to beglnning-of-information in multifile files. Refer to
explanation below.)
Append to the end of newlfn all replfn records that do not
match any records on the oldlfn. If A is not selected,
records on the replacement file that do not match any
records on the oldlfn are ignored and a dayfile message is
issued.
Check for matching name of record, but omit check for
matching type of record. If T is not selected, records
match only if both the type and name of the records are
the same.
Process oldlfn until the end-of-information.
These options can be specified by combining one or more letters in any
order, such as TRA, AR, ERTA, or TR.
COPYL and COPYLM check only the first four flag options; if more than
four are specified, the remaining characters are ignored.
**^s\
15-8 60459680 C
![](asset-213.png)
The R option affects file positioning of the old and new files before processing. If R is
specified, the old and new files are rewound before processing. In a multifile file, if
there is one or more end-of-file markers between the current position of the file and the
beginning-of-information, the R option rewinds the file to the first preceding EOF. In the
absence of R, you are responsible for positioning the oldlfn and newlfn files. The R option
does not affect the file of replacement records, since the current file of the replacement
file always is rewound to the beginning-of-information before and after processing.
The E option causes the old file to be processed to the end-of-information. Each
end-of-file encountered on the old file causes a matching end-of-file to be written on the
new file. Records that are added to the new file as a result of combining the A and E
options are appended with an end-of-file prior to the end-of-information. In this case,
such appended records will follow an end-of-file if both end-of-file and end-of-information
existed at the end of the old file.
Processing stops after an end-of-file, end-of-record, or end-of-information is reached,
depending on the structure of the old file and the processing options selected. If
processing stopped because end-of-file or end-of-record was reached, the old file is
positioned after that EOF or EOR. If processing stopped because end-of-information was
reached, the old file is positioned just prior to the end-of-information.
COPYL and COPYLM add an end-of-file to the new file even if no end-of-file is encountered on
the old file. No further positioning of the new file takes place.
y^N
60459680 C 15_9
![](asset-214.png)
y*3V
Example:
The following COPYL command updates OLDFILE with replacement records from REPFILE and writes
them on NEWFILE. The A option appends to the end of NEWFILE any records in REPFILE that do
not match a record on OLDFILE.
COPYL,OLDFILE,REPFILE,NEWFILE„A.
The following dayfile segment shows that COPYL updated the record named B and appended the
record named C.
08.53.23.COPYL,OLDFILE,REPFILE,NEWFILE„A.
08.53.24. UPDATED — PROC / B
08.53.24.APPENDED — PROC / C
08.53.24. COPYL COMPLETE.
The ITEMIZE command show the record information for all records in OLDFILE, REPFILE, and
NEWFILE.
y^H^ftv
/itemize/) Id fi Le
REC
ITEMIZE
NAME
OF OLDFILE
TYPE
FILE
LENGTH CKSUM
1
2
3
A
B
(00)
PROC
PROC
SUM » 10
3310
5306
* EOI * SUM = 10
ITEMIZE COMPLETE.
/itemize,repfi Le
REC
1
2
ITEMIZE
NAME
B
C
OF REPFILE
TYPE
PROC
PROC
FILE
LENGTH
4
4
CKSUM
DATE
DATE
* EOI *
ITEMIZE COMPLETE.
/itemize,newfi Le
SUM = 10
REC
ITEMIZE OF NEWFILE
NAME TYPE
FILE
LENGTH CKSUM DATE
PROC
PROC
SUM = 10
3310
1535
* EOF *
ITEMIZE COMPLETE.
15-10
PROC
SUM = 14
7304
60459680 C
![](asset-215.png)
GTR COMMAND
The GTR command extracts records selected from one file and writes them on another file.
The records are selected according to directives specifying their type and name. (Refer to
Library Record Types in this section for the list of valid record types.) Records can be
accessed randomly (default if a directory exists) or sequentially. If specified, a random
access directory is appended to the changed file. The system writes an EOF after the
directory.
Format:
GTR,lfni,lfn2,d,NR,S,NA.directive1,directive2,...,directiven
NOTE
The parameters must be in the order shown.
GTR identifies its parameters by their
position, not by keywords. An omitted
parameter is denoted by consecutive commas.
Do not place blanks between the terminator
(right parenthesis or period) and
directivei. Also, do not place a
terminator after directiven.
Parameter Description
l f m File which is searched for the requested records; if lfni is
omitted, file OLD is assumed, lfni *s always rewound before the GTR
operation.
l f n -
^p*\
File on which the selected records are written; if lfn2 is omitted,
file LGO is assumed. For disk files, GTR always positions lfn2 at
EOI before copying the selected records. GTR only appends records to
tape files when you specify the NR parameter. Otherwise, GTR starts
wr iti ng on tape files at t hei r BOI.
Random access directory parameter. If d is specified, lfn2 must be
a mass storage file. GTR cannot append records after a directory.
If lfni nas a random access directory and if sequential access (the
S parameter) is not specified, the lfn2 directory record is given
the same name as the lfni directory record. Otherwise, the lfn2
directory record is named lfn2.
d^ Description
omitted No new random access directory (OPLD) is added to
lfn . If the directives specify the user2library
record type (ULIB), the first record of the user
library (ULIB) is not copied to lfn2. The second
and subsequent records are copied, and the last record
(OPLD) is copied without alteration. The system does
not write an EOF at the end of the file.
60459680 F 15-11
![](asset-216.png)
Parameter Description
_d_ Description
U No new random access directory (OPLD) is added to
lfn . If the directives specify the user2library
record type (ULIB), the first record of the user
library (ULIB) is copied without alteration to lfn2
along with the remainder of the library, including the
OPLD. The system does not write an EOF at the end of
the file.
D or other Writes a new random access directory (OPLD) at the end
of lfn2. If the directives specify the user library
record type (ULIB), the first record of the user
li bra ry (UL IB) is copi ed w ith out al ter ati on t o lfn2
along with the remainder of the library, including the
OPLD. The system writes an EOF after the new
directory.
I NOTE |
The new random access directory contains
entries only for records specified on
the current GTR command. To build a new
random access directory which contains
entries for all records on lfn2, use
LIBEDIT.
NR No rewind option, lfnj is not rewound after the operation; lfn2
is not rewound before or after the operation. If lfnj has a
directory, the directory is copied to lfn2.
If NR is omitted, both files are rewound after the operation, but only
when lfn2 is a tape file is lfn2 rewound before the operation.
S lfnj^ is searched sequentially; no attempt is made to read a
directory.
NA No abort option. If specified, GTR does not search for an EXIT
command when an error occurs. It issues a dayfile message for the
error and continues GTR processing at the next directive.
directive.^ Specifies a record or group of records to be retrieved. One or more
of the following formats can be used. Valid record types are listed
under Library Record Types in this section. The default type is the
last type specified on a directive, or if none is specified, TEXT.
The record name is the first seven characters of the record, or if a
prefix table is present, the contents of the name field in its second
word.
Directive Meaning
t y p e / n a m e R e c o r d w i t h t h e s p e c i fi e d t y p e a n d n a m e .
name Record with the specified name and the
default type.
15-12 60459680 H
s*ts $$\
![](asset-217.png)
Parameter Description
Directive
type1/name.-type2/name2
t yP ei/namei-name2
namei-name2
type/name-*
type/*
*
0
Meaning
Group of records beginning with
namei 0f typei and ending with
name2 of type2.
Group of records beginning with namel
of typei and ending with name2 of
type1#
Group of records beginning with namel
of the default type and ending with
name2 of the default type.
All records of the specified type
beginning with the named record.
All records of the default type beginning
with the named record.
All records of the specified type.
All records of the default type.
A zero-length record is inserted.
GTR searches file lfnx for the records specified by the selection directives. If GTR
cannot find a record specified by type and name, it issues the following dayfile message.
GTR ERRORS.
If also issues this message when the record specified is within a user library and when the
GTR command syntax is incorrect.
If lfni has a directory (OPLD) record, GTR writes the selected records on lfn2 in the
order specified on the GTR command. If lfn2 does not have a directory record, GTR writes
the selected records in the order that it finds them on lfni, rather than in the order
specified on the command.
If lfn2 is on tape, the selected records are copied from the current file position; if
lfn2 is on mass storage, the copy starts at the current EOI of the file. If an EOF exists
before the EOI, GTR appends the records as a file following the existing EOF.
Examples:
• GTR,SYSTEM,BIN,D.PP/*
GTR copies all PP records from file SYSTEM to file BIN. It then builds a random
access directory and writes it as the last record on BIN.
• GTR,OPL,NEW,,NR.OPLC/COMCARG,0,COMCCIO
GTR retrieves common decks COMCARG and COMCCIO from file OPL. It then writes
COMCARG, a zero-length record, and COMCCIO at the current position of file NEW.
NEW is not rewound before the operation; OPL and NEW are not rewound following the
operation.
60459680 C 15-13
![](asset-218.png)
• GTR,SYSTEM,SYSLIB,D.ULIB/SYSLIB
GTR copies the user library SYSLIB from file SYSTEM to the end of file SYSLIB.
• GTR.REL/A
GTR retrieves the relocatable record A from file OLD and copies it to file LGO.
ITEMIZE COMMAND
ITEMIZE lists pertinent information about each record of a binary file in a format suitable
for printing. Earlier in this section, Library Record Type describes the types of records
processed by ITEMIZE.
ITEMIZE processes mass storage files or I or SI format tape files. A file can be processed
from beginning-of-information through end-of-information.
Format:
ITEMIZE,Ifn,L=listlfn,BL,PW=n,PD,NR,N=n,E,U.
The first parameter is order-dependent; if lfn is omitted, its position must be indicated by
a comma. All the other parameters are optional and order-independent.
Parameter
PW=n
PD
NR
N=n
Description
lfn Name of file to be itemized; default name is LGO.
L=listlfn List output on file listlfn; default is L=OUTPUT.
BL Burstable listing; each file output starts at the top of a page.
Default is a compact listing in which a page eject occurs only when the
current page is nearly full.
15-14
Print either 136-character lines or 72-character lines, depending on the
value of the decimal integer n. If n > 136, print 136-character line.
If n < 136, print 72-character lines.
If just PW is specified, print 72-character lines regardless of the
listing file device.
If PW=n is omitted, the default value is 72-character lines if the
listing file is a terminal; otherwise, the default value is
136-character lines.
Print density at eight lines per inch; default is six lines per inch.
If this parameter is to produce the desired result, you must ensure that
output appears at a printer capable of eight lines per inch.
No rewind of lfn before or after processing; default is rewind before
and after processing.
Itemize n files, where n is a decimal integer; default is N=l.
If j us t N i s sp ec ified, i te mi ze until e nd -o f- in fo rmation.
If N=0, itemize until an empty file is processed.
60459680 C
"•^x
![](asset-219.png)
Parameter Description
E Expand output to list further information; default is no expansion.
For record types CAP and REL, list entry points.
For types OPL and OPLC, list modification set names and their YANK
status.
For record types UPL, list correction identifier names.
U Itemize all records within a user library; default is list only the
user library directory (ULIB type record).
If both E and U are selected for ULIB type records, all records in the library are itemized;
and for REL type records, their entry points are listed.
Output from ITEMIZE is affected by the type of record and parameters selected. A header
appears for each file terminated by an end-of-file marker within the file specified by the
file name. The first line of the header identifies the file name, file position within that
file, and the date and time of the run. It also includes the FI field if the file is a
multifile set tape file (refer to the LABEL command). The second line of the header has the
following fields:
Field Description
REC Position of the record within the file.
NAME Record name obtained from the second word of the prefix table or from
the first word of the record.
TYPE Type of record. Refer to Library Record Type, earlier in this
section, for a description of the record types.
LENGTH Number of words (octal) in the record, excluding the prefix table
(except TEXT records for which the prefix table is included).
CKSUM Logical checksum (octal), excluding the prefix table (except TEXT
records for which the prefix table is included).
DATE Date record was created as stored in the prefix table.
C O M M E N T S C o n t e n t s o f t h e c o m m e n t s fi e l d i n t h e p r e fi x t a b l e .
If no pr efi x table i s pres en t, the associated fie ld s are b la nk .
NOTE
When printing output for text files, ITEMIZE
uses the first seven characters of the first
word of the record as the record name.
ITEMIZE assumes that the record is in 6-bit
display co de. Therefor e, if you a tt em pt to
display ITEMIZE output for a record in
6/12-bit display code while your terminal is
in ASCII mode, the output display may be
garbled. To avoid this problem, you should
set your terminal to NORMAL- mode before
listing ITEMIZE output.
60459680 E 15-15
![](asset-21a.png)
Additional information listed depends on the type of record:
Record Type , Description
ABS Entry point names are listed.
OPL, OPLC, UPL Deck names are listed.
OVL Overlay level is listed (octal).
TEXT Entire record is listed if the name of the record is OVERLAY
APRDxxx, CMRDxxx, EQPDxxx, IPRDxxx, LIBDxxx or COMMENT.
6PP Lists the octal equivalent of the load address.
7PP Lists the octal equivalent of the load address. .^^v
The E parameter can select further details about several types of records (refer to the
example that ends the ITEMIZE command description).
The last record in each file is the end-of-file marker, which appears on the listing as the
characters *EOF*. The SUM= identification is the total length, in words, for all records in
the file, including the prefix table lengths.
Any zero-length record in the file appears with the record name (00). When a zero-length
record is encountered, a sum of the lengths of the records encountered since the beginning
of the file, or since the last sum was taken, is listed on the output. The length includes ./assx
p r e fi x t a b l e s . R e c o r d n u m b e r i n g i s n o t r e s t a r t e d u n t i l a n e w fi l e i s e n c o u n t e r e d . ^
If a record of type UPL has more correction identifier names and/or deck names than can be
accommodated within ITEMIZE, the following message appears on the listing in place of the
excess names:
TRUNCATED - REQUESTED LIST TOO LONG
In this instance, the Update utility must be used to obtain a complete list of identifiers
and deck names.
A dayfile message is issued when ITEMIZE completes execution. 1
15-16 60459680 G
![](asset-21b.png)
(T$i8"ttl£*y
/#^\
Example:
A FORTRAN program named SUBROUT has three subroutines. The following ITEMIZE command lists
the records of the binary object file LGO. The E option lists the entry point for each REL
type record listed.
/itemize,Lgo,e
ITEMIZE OF LGO FILE
REC NAME TYPE LENGTH CKSUM DATE
1SUBROUT REL
SUBROUT 105 5355 yy/mm/dd.
2SUB1 REL
SUB1 45 0263 yy/mm/dd.
3SUB2 REL
SUB 2 45 3276 yy/mm/dd.
4SUB3 REL
SUB 3 45 1542 yy/mm/dd.
* EOI * SUM = 264
ITEMIZE COMPLETE.
LIBEDIT COMMAND
LIBEDIT is a general-purpose utility that generates a file containing records copied from
one or more other files (figure 15-2). LIBEDIT can build a random access directory for the
new file. It recog nizes the record types liste d in Library Record Types in this section.
LIBEDIT can edit a library according to directives requesting addition, deletion, or
replacement of specified records from one or more replacement files.
LIBEDIT executes in two phases. During the first phase, it reads directives and replacement
records. It groups directives by type and file and groups changes when several insertions
take place relative to the same record.
During the second phase, LIBEDIT writes the new file. If LIBEDIT cannot process the
specified combination of directives, and the D option (refer to description under Command
Format) was not specified, LIBEDIT lists its interpretation of the conflicting directives,
issues an error message, and aborts the job step. If the D option was specified, LIBEDIT
continues processing the directives.
For output listing files not connected to your terminal, the LIBEDIT command honors the page
length and print density set for your job using the SET command and the PL and PD symbolic
names.
( 60459680 D 15-17
![](asset-21c.png)
Figure 15-2. LIBEDIT Input and Output
COMMAND FORMAT
The following command calls LIBEDIT. Its parameters specify options and files used for the
call as illustrated in figure 16-2.
Format:
L I B E D I T, p i , p 2 , . . . , p n .
Optional parmeters Pi can be in any order. Each parameter cannot be specified more than
once.
PL
P=lfni
Description
Edit old file lfn^ The default is OLD. P=0 directs the system to
create the new file from replacement file(s).
Although LIBEDIT can write the new file (lfn2)
directly to tape, the directory that LIBEDIT
writes on such a tape contains tape PRU random
addresses rather than disk PRU random
addresses. If this tape is subsequently
copied to disk, the directory will not be
processed correctly by programs such as GTR
and MODIFY. Therefore, if you intend to copy
the file back to disk at a later time, you
should specify a temporary disk file for the
LIBEDIT new file (lfn2) and then use the COPY
util ity to cop y the new file to tap e.
15-18 60459680 D
![](asset-21d.png)
Pi Description
N = l f n 2 W r i t e t h e n e w fi l e o n l f n 2 . T h e d e f a u l t i s N E W .
I=lfn3 Take the new directives from the next record of file lfn3. The
default is INPUT (INPUT is connected to the terminal in interactive
jobs). 1=0 indicates that there are no directives.
Z Ta k e t h e d i r e c t i v e s f r o m t h e c o m m a n d l i n e . T h e d i r e c t i v e s i m m e d i a t e l y
follow the command terminator. The first character following the
terminator is the separator character used to separate the directives
in the sequence. It can be any character not used in the directives.
For example:
LIBEDIT,Z.#*DELETE REL/PR0G1#*ADD PR0G2
The Z parameter overrides the I=lfn3.
B=lfn4 Use records from file lfn4 for insertions and replacements. The
default is LGO. B=0 indicates that there is no replacement file.
L=lfn5 List output on file lfn5. The default is OUTPUT. L=0 specifies no
output.
L0=listopt Use list option listopt.
listopt Meaning
C List directives.
E List errors.
M List modifications.
N List records written to new file.
F Give a full listing (enable all list options).
You can combine the list options; for example, L0=CM or L0=CE.
The default is L0=EM for interactive jobs, and L0=F for all other jobs,
V Verify the new file against the old file after LIBEDIT processing by
calling VFYLIB. The default is no call to VFYLIB. The U parameter
overrides this parameter.
C Copy the new file over the old file after LIBEDIT processing.
D Do not abort LIBEDIT processing because of errors.
U=record Require the old file to be a user library, add any new records from
the replacement file to the new file, and make the new file a user
library by calling LIBGEN. This parameter overrides the V parameter.
The value record becomes the name of the user library directory
record. If you specify only the keyword U or omit the parameter
entirely, the default record name is ULIB.
NA Do not abort on directive errors.
N I D o n o t i n s e r t u n r e p l a c e a b l e r e c o r d s a t E O F o f t h e n e w fi l e .
60459680 G 15-19
![](asset-21e.png)
<^sSy
Pi Description
NR Do not rewind the old or new file before or after LIBEDIT processing.
By default, the system rewinds the old file and new file.
NX=n Include cross-references in the library directory of the new user
library if n is 0. If n is nonzero, do not include cross-references.
This parameter is meaningful only if you specify the U parameter or
the *LIBGEN directive. The default is NX=0.
LIBEDIT DIRECTIVES
You can specify directives to control LIBEDIT processing. These directives can be in a
record on file INPUT (terminal input for interactive jobs), can be on the file specified by
I=lfn3 parameter of the command, or can follow the terminator of the command when the Z
parame te r is spe ci fie d. Di recti ve s are not req uired .
Unless specified otherwise by parameters or directives, LIBEDIT compares the name and type
of each record on the old file with those of the records on the replacement file (specified
by the B parameter). If a record with the same name and type appears on the replacement
file, LIBEDIT writes that record on the new file and skips the record on the old file unless
you specified the *N0REP directive. If 1=0 and B=0 are specified, LIBEDIT copies the old
file to the new file until it encounters an EOF mark or an OPLD directory on the old file.
Records on a replacement file which do not appear on the old file with the same name and
type are considered unreplaceable. Such records will be inserted at EOF of the new file,
unless the NI parameter or *N0INS directive is specified. If a record with the same name or
type appears on more than one replacement file or appears more than one on a replacement
file, the extra copies will be treated as unreplaceable records.
LIBEDIT processing of user libraries beginning with a ULIB record differs depending on
whether or not the LIBGEN directive is specified. If no LIBGEN directive is specified, the
user library is processed as one record (from ULIB header to OPLD). In this case, the only
part of the user library that can be manipulated by LIBEDIT is the ULIB header. The records
within the user library are transparent to LIBEDIT and cannot be referenced by directives.
If the LIBGEN directive is specified, LIBEDIT deletes the ULIB header and OPLD records from
all user libraries encountered. In this case, LIBEDIT directives can reference any records
within the user library but cannot reference the ULIB header.
LIBEDIT directives take precedence over the parameters of the command when conflicting
spe ci fic at io ns oc cur.
15-20 60459680 G
![](asset-21f.png)
J^^v
LIBEDIT recognizes the following directives,
Directive Function
*ADD
*BEFORE or *B
*BUILD
*COMMENT
*COPY
*DATE
*DELETE or *D
*FILE
*IGNORE
*INSERT or *I or *AFTER or *A
*LIBGEN
*LIST
*NEW
*NOINS
*NOREP
*NOREW
*OLD
*RENAME
*REPLACE
*REWIND
*TYPE or *NAME
*VFYLIB
Inserts records before a zero-length record within the
file.
Inserts record before the named record.
Builds a directory at the end of the new file.
Adds a comment to the prefix table.
Copies the new file to the old at the end of editing.
Adds the date and a comment to the prefix table.
Does not copy specified records to the new file.
Declares a file to be a replacement file.
Ignores records when reading the replacement file.
Copies record from the replacement file after copying
the specified old file record.
Generates a user library by calling LIBGEN after
LIBEDIT processing.
Specifies a list file and list options.
Specifies a new fil e.
Prevents the insertion of unreplaceable records at EOF
of the new file.
Does not automatically replace old file records with
records from the specified file.
Prevents the old file and the new file from being
rewound before and after LIBEDIT processing.
Specifies an old file.
Renames record.
Replaces the named records from the old file with
records from the replacement file.
Names file to be rewound before and after editing.
Sets default record type.
Verifies the new file against the old file by calling
VFYLIB after LIBEDIT processing (overridden by *LIBGEN).
0$&\
60459680 G 15-20.1/15-20.2 |
![](asset-220.png)
0^%\
![](asset-221.png)
0*&»\
A directive begins with an asterisk in column I followed immediately by the directive
identifier. The directive identifier and the first parameter are both delimited by a comma
or one or more spaces. If a directive does not begin with an asterisk and a directive
identifier, LIBEDIT assumes that the operation is a continuation of the previous directive
o pe rat ion . I f a n a st e ri sk and dir ect iv e i d en t ifi er do not beg in t he fi rs t l i ne o f t he
directives record, LIBEDIT prefixes the following to the first line.
*BEFORE,*,
Parameters other than the first parameter are delimited by a space, an end-of-line, or a
comma. A hyphen (-) indicates a record group. Record group identifiers (gid entries)
cannot be split between lines. For example, the lines
*B,0VL/P1,0VL/P2,OVL/
P3
do not constitute a valid directive. The last entry would not be processed as 0VL/P3. On
the other hand, the lines
*B,0VL/P1,0VL/P2
0VL/P3
do constitute a valid directive and would be processed as
*B,0VL/PI,0VL/P2.0VL/P3
Parameters common to many directives are the reference record identifier (rid) and the
record group identifier (gid). Valid record types for these parameters are listed in
Library Record Types in this section. The default type is the last type specified in a
directive; if none are specified, TEXT is the default. The record name is the first seven
characters of the record, or if a prefix table is present, the name in its second word. The
first character of a record name specified in a directive must not be an asterisk.
rid Reference record identifier specifying the reference point for the requested
change. It can have the following formats.
Parameter Description
type/name Reference record has the specified type and name.
name Reference record has the specified name and is of
the default type.
* Reference point is an end-of-file mark (used with
*BEFORE directive only).
gid Record group identifier indicating a record or group of records to be inserted,
deleted, or replaced. It can have the following formats.
Parameter Description
type/name Record with the specified type and name.
name Record with the specified name of the default type.
type /name -type„/name- Group of records beginning with namei of typei
and ending with name2 of type2.
60459680 G 15_21
![](asset-222.png)
Parameter
typei/namei-name2
namei-name2
type/name-*
name-*
type/* '
0
Description
Group of records beginning with namei of typei
and ending with name2 of typei•
Group of records beginning with namei °f the
default type and ending with name2 of the
default type.
All records of the specified type beginning with
the named record.
All records of the default type beginning with the
named record.
All records o f the specified type.
All records of the default type.
A zero-length record is inserted.
LIBEDIT checks the syntax of directives during an interactive session and
reprompts you for a directive in error.
/tr^$$\
15-22 60459680 G
![](asset-223.png)
ADD Directive
The ADD directive inserts records before a zero-length record. A CATALOG listing of the old
file numbers each group of records ending with a zero-length record (called a library on the
listing). This number on the ADD directive identifies the record group.
NOTE
Adding a zero-length record does not change
the directory.
Format:
*ADD LIBn,gidi,gld2 gidn
Parameter Description
L IBn S p ec i fi e s t h e r e co r d g r o u p t o w h i ch t h e r e cor d s a r e a p p end e d . Va l ues
for n are 1 to 63 and can be determined from a CATALOG listing of the
old file.
8"i Identifies the records or groups of records from the current
replacement file that are to be inserted before the zero-length record.
Example:
The following is a CATALOG listing of file Q.
DATE
:c CATALOG
NAME
OF Q
TYPE
F I L E
LENGTH CKSUM
1
2
3
REC1
REC 2
(00)
TEXT
TEXT
SUM =
5302
5304
LIBRARY =
4REC 4 TEXT 5310
* E O I * SUM =
The following output results when a record was added to file Q, producing file Y.
LIBEDIT DIRECTIVE CARDS. yy/mm/dd. 15.12.51. PAGE 1
ygfeWlL
*ADD LIB1, REC 3
RECORDS WRITTEN ON FILE Y
RECORD TYPE FILE
REC1 TEXT
REC2 TEXT
INSERTED REC3 TEXT
00
REC4 TEXT
**E0F**
DATE COMMENT yy/m m/d d. 15.1 2.5 1. PAGE 2
60459680 C 15-23
![](asset-224.png)
BEFORE Directive
A BEFORE directive inserts records or groups of records before a specified reference record
on the old file. An old file record with the same name and type as an inserted record is
not copied to the new file.
Formats:
*BEFORE rid,gidi,gid2>_>gidn
or
*B rid,gld1,gld2>...tgldn
Parameter Description
rid Names the old file record before which the specified replacement file
records are to be inserted.
Si"! Identifies records or groups of records from the current replacement
file that are to be inserted before the reference record (rid).
If the first line of the LIBEDIT directives record does not begin with an asterisk and
directive name, LIBEDIT assumes that the line is the gid parameters following a *BEFORE*,
directive.
BUILD Directive
A BUILD directive constructs and appends a random access directory to the new file. The
directory is in Modify format (an OPLD record). If the old file has an OPLD directory,
LIBEDIT constructs a directory for the new file with or without a BUILD directive. BUILD
can also be used to change the directory name.
Format:
*BUILD dname
dname Specifies the name for the directory record. The name must be one to
seven alphanumeric characters. No default.
15-24 60459680 C
![](asset-225.png)
COMMENT Directive
The COMMENT directive adds a comment to the prefix (77) table of a record written on the new
file.
Format:
♦COMMENT rid comment
Parameter Description
r i d N a m e o f a r e c o r d t o b e w r i t t e n o n t h e n e w fi l e .
comment A string of up to 70 characters that appears in the comment field of
the p r efi x t ab le . A dd i ti on a l ch a ra ct e rs a r e tru nc at e d.
COPY Directive
The COPY directive directs LIBEDIT to copy the new file over the old file after it has
processed all directives. It performs the same function as the C parameter on the LIBEDIT
command. This directive has no parameters.
DATE Directive
The DATE directive adds the current date and the specified comment to the prefix (77) table
of a record written on the new file.
Format:
*DATE rid comment
Parameter Description
rid Record to be written on the new file.
comment A string of up to 70 characters to be written in the comment field of
the prefix table. Additional characters are truncated.
60459680 C 15-25
![](asset-226.png)
DELETE Directive
The DELETE directive suppresses copying of the specified records from the old file to the
new file.
Formats:
*DELKTE8ldlfgld2f..Btgldn
or
*d eidi,gid2,...,gidn
8idi Identifies records or groups of records that are not to be copied from
the old file to the new file.
Example:
*DELETE OVL/LAD-REL/RUN
This directive requests LIBEDIT not to copy the sequence of records starting with overlay
LAD through relocatable CPU program RUN.
RLE Directive
The FILE directive names a file assigned to the job that contains replacement records.
LIBEDIT directives following the FILE directive refer to records on the declared replacement
file.
Format:
*FILE lfn
lfn Specifies the name of a relacement file. If lfn is an asterisk (*),
LIBEDIT uses the replacement file specified by the LIBEDIT command.
If the B parameter was omitted from the command, LGO is used. ,*$$*.
15-26 60459680 C
![](asset-227.png)
IGNORE Directive
The IGNORE directive requests LIBEDIT to ignore a record or group of records on the current
replacement file.
Format:
*IGNOREgidifgid2>_>gidn
8i<*i Identifies records or groups of records on the replacement file that are
to be ignored.
Example:
*FILE ALPHA
*IGNORE C-*
LIBEDIT ignores the sequence of records on file ALPHA starting with record C of the default
type and including all records of the default type from C to the EOF mark.
INSERT or AFTER Directive
The INSERT or AFTER directive requests LIBEDIT to copy the specified records or groups of
records from the current replacement file after it has copied the specified old file record
onto the new file. Any record on the old file that has the same name and type as an
inserted record is not copied to the new file.
Formats:
*INSERT rid,gidi>gid2>...>gidn
or
*I rid,gidi>gid2>_>gldn
*AFTER rid,gidi,gid2 gidn
or
*A rid,gidi>gid2>..#>gidn
Example:
*INSERT OPL/K,TEXT/L
This directive requests LIBEDIT to copy the replacement file text record L to the new file
after it has copied the old file OPL record K.
60459680 C 15_27
![](asset-228.png)
,*J^^\
LIBGEN Directive
The LIBGEN directive specifies that the new file will be a user library. The U parameter of
the LIBEDIT command performs the same function. The LIBGEN directive will override the
VFYLIB directive.
Format:
*LIBGEN recordname
recordname Specifies the name of the new user library directory record. The
default is ULIB.
,«<^x
LIST Directive
The LIST directive changes the list file and the list option (refer to the L=lfn5 and
LO=listopt parameters of the LIBEDIT command described earlier).
Format:
*LIST listfile, listopt
Parameter Description
listfile Specifies the list file. /"^.
listopt Specifies the list option.
NEW Directive
The NEW directive specifies the name of the new file. The N=lfn2 parameter of the LIBEDIT
command performs the same function.
Format:
*NEW newfile
newfile Specifies the name of the new file.
NOINS Directive
The NOINS directive prevents the insertion of unreplaceable records at EOF of the new file.
The NI parameter of the LIBEDIT command performs the same function. This directive has no
parameters.
15-28 60459680 C
![](asset-229.png)
NOREP Directive
The NOREP directive declares the s pecified files to be no -replace files. A no-replace file
is a replacement file whose records do not automatically replace old file records having the
same name and type. The user selects records to be written on the new file from no-replace
files by specifying the file on a FILE directive and then naming the records on *AFTER,
*BEFORE, *INSERT, and *REPLACE directives.
Format:
* N O R E P l f n l fl f n 2 l f n n
lfnl Specifies the no-replace files.
■ NOREW Directive
The NOREW directive prevents the old file and new file from being rewound before and after
LIBEDIT processing. The NR parameter of the LIBEDIT command performs the same function.
This directive has no parameters.
OLD Directive
The OLD directive specifies the name of the old file. The P=lfni parameter of the LIBEDIT
command performs the same function.
Format:
*OLD oldfile
oldfile Specifies the name of the old file.
RENAME Directive
The RENAME directive assigns a new name to a record written on the new file. If the renamed
record is referenced by another directive in the directive record, the old name should be
used. A RENAME is not allowed on a PROC or TEXT type record.
Format:
*RENAME rid,name
Parameter Description
rid Specifies the name of the replacement file record or old file record
to be renamed.
name Specifies the name of the record. The name can be one to seven
alphanumeric characters.
60459680 D 15_29
![](asset-22a.png)
REPLACE Directive
The REPLACE directive requests LIBEDIT to replace the old file records having the specified
names and types with the replacement file records having matching names and types. This
directive is used when the current replacement file has been declared a no-replace file
(refer to the NOREP directive description). If the replacement file is not a no-replace
file, LIBEDIT performs the replace operation automatically.
Format:
*REPLACE gidi,gid2,...,gidn
&idi Specifies records or groups of records that appear on both the old
file and the current replacement file.
Example:
The old file contains text records A, B, C, and D; the replacement file RF also contains
text records named A, B, C, and D. Either of the following directive sequences writes
records A and B from the old file and records C and D from file RF onto the new file.
Sequence 1 Sequence 2
*FILE RF *FILE RF
*NOREP RF *IGNORE A-B
♦REPLACE C-D
REWIND Directive
The REWIND directive tells LIBEDIT to rewind the specified file before and after processing.
Format:
♦REWIND lfn
lfn Specifies the name of the file to be rewound.
15-30 60459680 C
![](asset-22b.png)
0^\
y^*K
TYPE or NAME Directive
A TYPE or NAME directive sets the default record type.
Formats:
*TYPE type
*NAME type
t y p e S p e c i fi e s d e f a u l t r e c o r d t y p e s . V a l i d r e c o r d t y p e s a r e l i s t e d i n
Library Record Types in this section.
The default record type can also be set by an explicit record type specification within a
directive. In either case, the default record type setting remains in effect until another
record type is explicitly named. If a default record type is not declared in the directive
sequence, the default is TEXT. For example, the following two directive sequences are
equivalent•
Sequence 1 Sequence 2
*TYPE REL *INSERT REL/X,Y
*INSERT X,Y *DELETE FILE1-FILE4
*DELETE FILE1-FILE4
VFYUB Directive
The VFYLIB directive verifies the new file against the old file by calling VFYLIB after
LIBEDIT processing. The V parameter of the LIBEDIT command performs the same function.
This directive has no parameters. The LIBGEN directive or U parameter will override the
VFYLIB directive.
LIBEDIT OUTPUT
LIBEDIT interprets all directives in the directive record before beginning directive
processing. If one or more errors are found, LIBEDIT issues the dayfile message
n DIRECTIVE ERROR(S).
and aborts the job step (unless the D parameter is specified on the command or the job is
interactive). The following LIBEDIT output shows the results of a directive syntax error
(the FILE directive is not followed by a space or comma).
DIRECTIVE ERRORS. yy/mm/dd. 10.36.47 PAGE 1
•ERROR* *FILERF1
Directives which cannot be executed are listed as LIBEDIT interpreted them. The following
LIBEDIT run called for a replacement file not assigned to the job.
DIRECTIVE ERRORS. yy/mm/dd. 10.37.39 PAGE 1
•FILE RF1
*B *,X
•ERROR* DIRECTIVE CARD CAN NOT BE PERFORMED
•FILE RF1
• BEFORE TEXT/*,TEXT/X
60459680 C 15-31
![](asset-22c.png)
Nonfatal errors are listed in an error directory following the listing of records written to
the new file. The RECORDS NOT REPLACED error shown in the following example could be
corrected by including an *IGNORE directive naming the records not to be replaced.
DIRECTIVE ERRORS.
•FILER F2
•B *,REC1
RECORDS WRITTEN ON FILE NEW
R E C O R D T Y P E F I L E
INSERTED REC 1 TEXT RF2
**E0F** OLD
DATE COMMENT
yy/mm/dd. 03.37.43. PAGE 1
yy/mm/dd. 03.37.43. PAGE 2
y y/ m m/ d d. 0 8.3 7 .4 3 . PA G E 3ERROR DIRECTORY - RECORDS NOT REPLACED.
RECORD TYPE FILE
REC3 TEXT RF2
REC4 TEXT RF2
If you are using LIBEDIT from an interactive job, the BRIEF command suppresses the printing
of ti tl e li nes on t he ou tput.
LIBGEN COMMAND
The LIBGEN command generates a user library of routines for use with CYBER Loader.
Format:
LIBGEN,pi,p2,...,Pn.
Any of the following parameters may be specified in any order (only one instance of each).
Pi
F=lfn!
P=lfn2
N=name
NX=n
Description
Specifies the source file containing absolute (ABS), overlay (OVL),
procedure (PROC), relocatable (REL), or capsule (CAP) records for the
user l ibrar y. O th er re co rd ty pe s are ign ored. If the file F does not
contain any of the record types specified, no library is generated.
The default for this parameter is LGO.
Specifies the file on which the user library is to be written. The
default is ULIB.
Specifies the name of the user library generated; name is entered in
ULIB and OPLD records. The default is the user library name
determined by the P=lfn2 parameter.
Specifies whether or not to include cross-references in the ULIB
directory. If n is not zero, no cross-references are included in the
ULIB directory. If n is zero, cross-references are included. The
later case is the default.
15-32 60459680 G
![](asset-22d.png)
If the F=lfni and P=lfn2 parameters specify the same file, LIBGEN issues a dayfile
message and does not generate a user library.
Figure 15-3 illustrates the structure of a user library. To generate a user library, the
system rewinds and scans the input file. It then builds a directory of all entry points,
program names, and external references in the records of the file. Adding the ULIB and OPLD
records, the system then copies the input file to the user library file.
j^^
ULIB } User library directory
REL
REL ' Relocatable routines
REL
OPLD | Random access directory
Figure 15-3. User Library Structure
Unless the NX=n parameter specifies otherwise, the ULIB directory contains the external
reference/entry point linkage between routines in the user library. When CYBER Loader loads
a routine from the user library, it loads (at the same time) all user library routines
referenced by the requested routine. All externals for user library routines are satisfied
from the user library, if possible. If desired, you can request with the NX=n parameter
that the ULIB directory contains no cross-linking of records. In that case, when a routine
from the user library is requested, only that routine is loaded. Loading in this manner is
typically slower than using the cross-reference linkage option.
Example 1:
File RELB contains relocatable routines that are used for execution of several
applications. To enable loading of these routines as needed during execution of an
application program, the user generates a user library using the following command.
LIBGEN,F=RELB,P=MYLIB,N=APPLIB.
This creates user library APPLIB on file MYLIB. The following loader sequence allows use of
the APPLIB routines during execution of a compiled FORTRAN 5 program on file LGO.
LDSET,LIB=MYLIB.
LOAD,LGO.
EXECUTE.
The program is loaded and executed with externals satisfied first from user library MYLIB
and then from the system default library SYSLIB. Refer to the CYBER Loader Reference Manual
for more information on library search procedures.
y^3Pv
60459680 G 15-33
![](asset-22e.png)
Example 2:
If a routine has no external references, no entry is made in the ULIB directory. To load
this routine, you must include the loader command LDSET(USEP=pname) in a loader sequence.
Suppose a FORTRAN 5 contains a BLOCK DATA subroutine without external references to any of
its entry points. The user has not named the block, and it has the default name BLKDAT. To
load this routine, you must include the following command in the loader sequence.
LDSET,USEP=$BLKDAT.$.
ULIB COMMAND
The ULIB command creates a user library or adds a record to, deletes a record from, or
replaces a record in an existing user library. ULIB changes affect only the local copy of a
user library. Use the SAVE or REPLACE command to make the user library file permanent.
Format:
ULIB,OP=operation,REC=record,LIB=library.
or
ULIB,operation,record,library.
All parameters are required. The first format is the order-independent format for the
parameters. The second is the order-dependent format.
Parameter Description
OP=operation Specifies the library operation to be done. You can specify one of
the following values:
Operation Description
C Create a new user library.
A Add a record to the user library (same as R).
D Delete a record from the user library.
R Replace a record in the user library (same as A).
F Copy a record from the user library and make the
copy a local file with the same name as the record.
REC=record Specifies the name of the record to be added, deleted, replaced, or
copied. The record name must be the name of a local file.
LIB=library Specifies the name of the local library file to be created or
modified. Except in the case of OP=C or OP=F, ULIB returns the
or ig ina l li bra ry fil e and cre at es a n ew l oca l file . He nc e, U LIB
cannot be used to modify a library on a direct access file.
15-34 60459680 D
![](asset-22f.png)
The ULIB command is an interactive procedure. You can get help information for the command
and its parameters and be prompted for parameters. If you enter
ULIB?
the system gives you information about the command itself and prompts you for parameters.
If you enter
ULIB,parameter?
the system gives you information about the specified parameter and prompts you for
parameters.
VFYLIB COMMAND
The VFYLIB command rewinds two files, compares their records, and lists the differences.
VFYLIB does not perform a bit-by-blt comparison of the two files. It only compares such
entries as name, type, length, and checksum for the records of the two files. For a binary
comparison of two files, use the VERIFY command. For output listing files not connected to
your terminal, the VFYLIB command honors the page length and print density set for your job
using the SET command and the PL and PD symbolic names.
Format:
VFYLIB,lfni,ifn2,Ifn3,NR.
Parameter Description
lfni Name of the first file; if this parameter is omitted, VFYLIB assumes
file OLD.
lfn2 Name of the second file; if this parameter is omitted, VFYLIB assumes
file NEW.
Ifn3 Name of the output file; If this parameter is omitted, VFYLIB assumes
file OUTPUT.
NR If specified, lfni and lfn2 are not rewound after verification.
The record types that VFYLIB recogizes are listed in Library Record Types In this section.
VFYLIB lists changes in residence (between record groups separated by zero-length records),
replacements, deletions, and insertions. A record is defined as being replaced when its
name and type remain the same, but its contents differ. VFYLIB does not compare prefix (77)
table information such as last modification date and last assembly date. VFYLIB does not
consider a difference in record order as a difference between the two files.
60459680 D
NOTE
When printing output for text files, VFYLIB
uses the first seven characters of the first
word of the record as the record name. VFYLIB
assumes that the record is in 6-bit display
cod e. Therefo re , if yo u attempt t o dis pl ay
VFYLIB output for a record in 6/12-bit display
code while your terminal is in ASCII mode,
the output display may be garbled. To avoid
this problem, you should set your terminal to
NORMAL mode before listing VFYLIB output.
15-35
![](asset-230.png)
Example:
The following are CATALOG listings of file OLD and file NEW.
CATALOG OF OLD
REC NAME T Y P E ILENGTH
1A
AREL 41
2(00) SUM = 41
3B
BREL 41
4 C REL 41
5 * EOF *
CATALOG COMPLETE.
SUM =
F I L E 1
CKSUM DATE
7424 yy/mm/dd.
L I B R A R Y = 1
0465 yy/mm/dd.
5525 yy/mm/dd.
143
CATALOG OF NEW
REC NAME TYPE LENGTH CKSUM DATE
1A
AREL 41 7424 yy/mm/dd.
2B
BREL 41 0465 yy/mm/dd.
3(00) SUM = 102 LIBRARY
4 D TEXT 1000
5* EOF * SUM = 103
CATALOG COMPLETE.
VFYLIB. OLD FILE = OLD
0 RECORD TYPE
0 CHANGES IN RESIDENCE.
B R E L
0 DELETED PROGRAMS.
C R E L
0 INSERTED PROGRAMS.
D T E X T
NEW FILE = NEW
ULIB LIB DATE yy/mm/dd. 12.18.25.
COMMENT PAGE
yy/mm/dd. SUBROUTINEOPT=0
yy/mm/dd. SUBROUTINEOPT=0
15-36
s^i\
60459680 C
![](asset-231.png)
LIBRARY PROCESSING EXAMPLES
The following examples illustrate the use of CATALOG, LIBEDIT, and LIBGEN commands. To
duplicate the examples, you should execute the jobs in sequence.
Example 1:
The following submit job builds a program library from a replacement file of relocatable
binary (REL) records.
/JOB
LIBTES1.
/USER
FTN5,L=0.
DEFINE/TESTLIB.
CATALOG,LGO,R.
LIBEDIT,P=0,N=TESTLIB.
CATALOG,TESTLIB,R.
/EOR
SUBROUTINE A
STOP
END
SUBROUTINE D
STOP
END
SUBROUTINE C
STOP
END
SUBROUTINE B
STOP
END
/EOR
•BUILD LIBRARY
*B,*,REL/A,B,C,D
/EOF
The FORTRAN compilation produces relocatable binaries on the default file LGO. The DEFINE
command creates a direct access permanent file TESTLIB on which the new program library is
written. The first CATALOG command lists the LGO file as follows:
CATALOG OF LGO FILE 1 yy/mm/dd. 12.34.49. PAGE 1
REC NAME TYPE LENGTH CKSUM DATE COMMENTS
1 A REL 41 7424 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
A
2 D REL 41 6566 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
3 C REL 41 5525 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
C
4 B R E L 4 1
B
5 * E O F • S U M = 2 0 4
0465 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
The P-0 in the LIBEDIT command indicates that no old program library exists. The N parameter
indicates that the new program library is written on file TESTLIB. The replacement file is
the default LGO. The directives are on the default INPUT file.
60459680 D 15-37
![](asset-232.png)
LIBEDIT reads the binaries from LGO and the directives from INPUT. On the basis of the
direct iv e spe ci fication s, the bi narie s are i nsert ed bef ore t he end-of -fi le on file TESTL IB
in the order specified in the directives (A, B, C, D). The directory record created is
given the name LIBRARY as a result of the *BUILD directive. It is written before the
end-of-file on the new program library TESTLIB.
The directives are written to OUTPUT. The records on file TESTLIB are listed on the next
page of OUTPUT. The following listing consists of these two pages.
LIBEDIT DIRECTIVES. yy/mm/dd. 12.34.52. PAGE
•BUILD LIBRARY
*B,*,REL/A,B,C,D z^SSfei
RECORDS WRITTEN ON FILE TESTLIB
12.34.52. PAGE 2
yy/mm/dd.
RECORD TYPE FILE
INSERTED A REL LGO
INSERTED B REL LGO
INSERTED C REL LGO
INSERTED D REL LGO
ADDED LIBRARY OPLD *****
**EOF**
DATE COMMENT
yy/mm/dd. SUBROUTINE0PT=0
yy/mm/dd. SUBROUTINEOPT=0
yy/mm/dd. SUBROUTINEOPT=0
yy/mm/dd. SUBROUTINEOPT=0
yy/mm/dd.
The second CATALOG command produces the following listing of information about the records
on TESTLIB.
CATALOG OF TESTLIB FILE
REC NAME TYPE LENGTH
1A
AREL 41
2B
BREL 41
3C
CREL 41
4D
DREL 41
5LIBRARY OPLD 13
6* EOF SUM = 217
yy/ mm /d d. 12.34.52. PA GE
CKSUM DATE COMMENTS
7424 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
0465 yy/mm/dd. SUBROUTINE0PT=0,R0UND= A/ S/ M
5525 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
6566 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
2073 yy/mm/dd.
.-*s»v
15-38 60459680 C
![](asset-233.png)
Example 2:
This submit job builds a new program library from an old program library by inserting new
relocatable routines into and deleting routines from the old program library created in
example 1 (TESTLIB).
/JOB
LIBTES2.
/USER
FTN5,L=0.
ATTACH,OLD=TESTLIB.
DEFINE,NEW=TES2LIB.
LIBEDIT.
CATALOG,NEW,R.
/EOR
SUBROUTINE BONE
STOP
END
SUBROUTINE NEWC
STOP
END
SUBROUTINE D
STOP
END
/EOR
•TYPE REL
•I,B,BONE
•D,C
/EOF
Three relocatable binaries (BONE, D, and NEWC) are produced via a FORTRAN compilation. The
old program library (TESTLIB) is attached in read mode and referenced as OLD. A direct ac
cess file (TES2LIB) is created for the new program library. This file is referenced as NEW.
LIBEDIT reads the binaries from the replacement file LGO and the input directives from file
INPUT. It writes the modified old program library (OLD) to the new program library (NEW).
BONE and NEWC are inserted after records B and C, respectively, and record C is deleted.
Record D, which already existed on the old program library, is replaced by record D from the
replacement file LGO. The following action is taken on file NEW.
LIBEDIT DIRECTIVES. yy/mm/dd. 12.34.58. PAGE
*TYPE REL
*I,B,BONE
*D,C
RECORDS WRITTEN ON FILE NEW
RECORD TYPE FILE
yy/mm/dd. 12.34.58.
DATE COMMENT
PAGE
A REL OLD
B REL OLD
INSERTED BONE REL LGO
DELETED-(C) REL OLD
REPLACED D REL LGO
ADDED NEWC REL LGO
ADDED LIBRARY OPLD *****
••EOF** OLD
60459680 C
yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
yy/mm/dd. SUBROUTINE0PT=0,R0UND= A/ S/ M
yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
yy/mm/dd. SUBROUTINE0PT=0,R0UND= A/ S/ M
yy/mm/dd.
15-39
![](asset-234.png)
The CATALOG output shows the following contents of the new program library.
CATALOG OF NEW FILE
REC NAME TYPE
1A
AREL
2B
BREL
3BONE
BONE REL
4D
DREL
5NEWC
NEWC REL
6LIBRARY OPLD
7* EOF * SUM =
LENGTH
41
41
41
41
41
15
262
yy/mm/dd. 12.34.58. PAGE
CKSUM DATE COMMENTS
7424 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
0465 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
4312 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
6566 yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
4432 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
7700 yy/mm/dd.
y ^ ^ V
15-40 60459680 C
![](asset-235.png)
/sPi^Hy
ygp*V
0$^K^
Example 3:
This submit job uses LIBGEN to generate a user library file from the program library file
TES2LIB created in example 2.
/JOB
LIBTES3.
/USER
ATTACH,TES2LIB.
DEFINE,LIBFILE.
LIBGEN,F=TES2LIB,P=LIBFILE,N=L0ADLIB.
CATALOG,LIBFILE,R,U.
/EOF
The program library TES2LIB is attached to the job. A direct access file LIBFILE is defined
f o r w r i t i n g t h e u s e r l i b r a r y fi l e .
LIBGEN scans TES2LIB and builds a ULIB directory of entry points, program names, and external
references for relocatable (REL) records in the file. ULIB is copied to the file LIBFILE,
followed by the records from TES2LIB. A file index of addresses for each record in the file
is added as the last record of LIBFILE. LOADLIB is the name of the ULIB and OPLD records.
The CATALOG output of the user library file LIBFILE shows the following content.
yy/mm/dd. 12.35.07. PAGE 1
CKSUM DATE COMMENTS
7725 yy/mm/dd.
7424 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
0465 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
4312 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
6566 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
4432 yy/mm/dd. SUBR0UTINE0PT=0,R0UND= A/ S/ M
0515 yy/mm/dd.
CA1fALOG OF LIBFILE FILE
:c NAME TYPE LENGTH
1LOADLIB ULIB 13
2A
A
REL 41
3B
B
REL 41
4BONE
BONE
REL 41
5D
D
REL 41
6NEWC
NEWC
REL 41
7LOADLIB OPLD 15
8* EOF * SUM 275
60459680 C 15-41
![](asset-236.png)
Example 4:
This submit job illustrates a method for deleting records from a user library.
/JOB
LIBTES4.
/USER
ATTACH,LIBFILE/M=W.
LIBEDIT,P=LIBFILE,U,Z.#*D,REL/NEWC
CATALOG,NEW,R,U.
/EOR
LIBEDIT references the program library LIBFILE and the directive following the command,
deletes NEWC, and writes this modified file on the default NEW. The output shows the
LIBEDIT processing.
LIBEDIT DIRECTIVES. yy/mm/dd. 12.35.14. PAGE
•D,REL/NEWC
RECORDS WRITTEN ON FILE NEW
R E C O R D T Y P E F I L E
AREL LIBFILE
BREL LIBFILE
BONE REL LIBFILE
DREL LIBFILE
DELETED-CNEWC) REL LIBFILE
ADDED LOADLIB OPLD *****
**EOF** LIBFILE
yy/mm/dd. 12.35.14.
DATE COMMENT
PAGE
yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
yy/mm/dd. SUBR0UTINE0PT=0,ROUND= A/ S/ M
yy/mm/dd. SUBROUTINEOPT=0,ROUND= A/ S/ M
yy/mm/dd.
LIBGEN generates a new user library on the file NEW. It uses LIBFILE as the source and
names the new user library ULIB.
The user library is cataloged, showing the following contents.
15-42 60459680 C
![](asset-237.png)
LIBRARY COMMAND
The LIBRARY command specifies a global library set for your current job. Once you specify a
global library set, you can execute any program or procedure on a global library file by
entering the entry point name for the program or procedure name. Special entry points ARG=,
NPC=, RFL=, and SDM= are also honored. (Refer to Volume 4, Program Interface for more
information.) A program can load overlays randomly from this global library set.
Format:
LIBRARY,fileL,file2,...,filen/directive
Parameter Description
file^
d i r e c t i v e
Specifies a file containing a user library. The file must be a local
file or a system library.
Specifies if filei,file2,...filen are to be added to, to be
deleted from or to replace the global library set.
yfl$^*\
directive Description
A Add the specified files to the global library set.
D D e l e t e t h e s p e c i fi e d fi l e s f r o m t h e g l o b a l l i b r a r y
s e t .
R R e p l a c e t h e e x i s t i n g g l o b a l l i b r a r y s e t w i t h t h e
specified files. R is the default.
To clear your global library set, specify no parameters:
LIBRARY.
NOTE
A no-auto-drop status is set for any file
inserted in the global library set. The
no-drop-status is cleared when a library is
removed from the global library set. Refer
to SETFS command for an explanation of
no-auto-drop status.
MAXIMUM SIZE OF GLOBAL LIBRARY SET
The maximum number of libraries allowed in your global library set varies with the number of
nonsystem libraries you specify. Figure 15-4 shows the various possibilities:
User libraries
Number of system
libraries allowed
Maximum number
of libraries
0
1
2
24
13
2
24
14
4
Figure 15-4. Maximum Size of Global Library Set
60459680 G 15-43
![](asset-238.png)
Nominally, you can never specify more than two user libraries (nonsystem libraries).
However, you can circumvent this restriction by making the local file name of a user library
the same as that of a system library. The system libraries USRLIB1, USRLIB2,..., and
USRLIB8 are available for this purpose.
LIBRARY SEARCH ORDER
The system searches the libraries in the global library set in the order in which you
specified them in the LIBRARY command. If an entry point name appears in multiple
libraries, the system uses its first occurrence. If you want to further control the library
search order, use the LIBLOAD and SATISFY commands, described in the CYBER Loader Reference
Manual.
EXAMPLES
Suppose you want to write a command to yield the date and another to yield your social
security number. This example uses a procedure to produce the date and a FORTRAN 5 program
to display your social security number.
File DATPROC has the following contents:
.PROC,DATE*I.
DISP,$TODAY'S DATE IS:$,DATE+.
REVERT,NOLIST.
eoi
.PR0C,DISP*I,STRING1,STRING2.
N0TE.+STRING1 STRING2
REVERT,NOLIST.
File SSPROG has the following contents:
PROGRAM SSNUM
PRINT*,'MY SOCIAL SECURITY NUMBER IS 530-82-7161.'
END
The following command entries establish your global library set:
/get,datproc,ssprog.
/ftn5,i=ssprog,L=0.
0.009 CP SECONDS COMPILATION TIME.
/Libedit,n=mylib,u,z.+*fi Le datproc
RECORDS WRITTEN ON FILE MYLIB
RECORD TYPE FILE DATE COMMENT
ADDED SSNUM REL LGO yy/mm/dd.
ADDED DATE PROC DATPROC
ADDED DISP PROC DATPROC
LIBRARY GENERATION COMPLETE.
/Library,mylib
LIBRARY,MYLIB.
15-44 60459680 G
![](asset-239.png)
0^\:
The FTN5 command creates file LGO and LIBEDIT creates user library MYLIB, containing the
procedure and compiled program. The LIBRARY command specifies your global library set.
The following sequence tests your commands:
/d ate
TODAY'S DATE IS: yymmdd
/ssnum
MY SOCIAL SECURITY NUMBER IS 530-82-7161.
0.003 CP SECONDS EXECUTION TIME.
Suppose you wish to include three of your own user libraries in the global library set for
your current job. You can accomplish this with the following commands:
/get, myLibl, myLib2, myLib3.
/Library, myLibl, myLib2, myLib3.
TOO MANY USER LIBRARIES SPECIFIED.
/rename, usrLibl = mylib3.
/Library, myLibl, myLib2, usrLibl.
LIBRARY, MYLIB1, MYLIB2, USRLIBL
Note that it was necessary to use the name of a system library USRLIBl for the third library
MYLIB3 in order to use more than two libraries at once.
The following command produces a display of your global library set:
/enquire,L
LOADER INFORMATION.
MAP OPTIONS = DEFAULT
DEBUG = OFF
GLOBAL LIBRARY SET IS -
MYLIB1, MYLIB2, USRLIB1
60459680 G 15-45 •
![](asset-23a.png)
{*%
{**%
![](asset-23b.png)
TERMINAL INPUT/OUTPUT 16
This section distinguishes NAM/CCP network functions from IAF functions to aid in error
checking and to allow you to carry over knowledge of the network to other products (RBF or
TAF, for example). If you are connected to a CDCNET network, refer to the CDCNET Terminal
Interfaces Usage manual for a description of terminal input and output. The network
interface is largely invisible to the IAF user. In most cases, you can ignore the existence
of the network and proceed as if you are communicating exclusively with IAF. However,
certain commands which involve communication only with the network are available to the IAF
user (appendix J). These network commands change the characteristics of a terminal (for
example, changing the backspace character or initiating paper tape operations), change the
character code set of a terminal, and send messages to the local operator. Unlike other
system commands, these network commands can be used any time a data connection exists between
the terminal and the communications network, including prior to the completion of login.
TERMINALS
IAF and the network provide support for 18 terminal classes.t Each terminal class
corresponds to an actual terminal or terminals as follows:
Class Terminal
1 M33, M35, M37, M38 teletypes
2 CDC 713-10, 722, 751-1, 752, 756
3 CDC 721, 722-30
4 I B M 2 7 4 1
5 M 4 0
( 6 Hazeltine 2000
7 Te r m i n a l s c o n f o r m i n g t o t h e A N S I X 3 . 6 4 s t a n d a r d ( D E C V T 1 0 0 ,
TeleVideo 924, 950, 955)
8 Tektronix 4010, 4014
9 HASP protocol post-print format control
10 200 User Terminal
11 CDC 714-30
12 CDC 711-10
13 CDC 714-10/20
14 HASP protocol pre-print format control
j^^\
TTerminals of all classes can be connected to NOS. Some terminals in terminal classes 1,
2, 3, and 5 through 8 can be connected to a packet switching network (PSN) with a
connection established to NOS.
60459680 H 16-1
![](asset-23c.png)
Class Terminal
15 CDC 731-12, 732-12, 734
16 IBM 2780
17 IBM 3780
18 IBM 3270
A computer site may support terminals other than those listed. Consult local site personnel
to determine if terminal types not listed are supported and to obtain additional operating
instructions for supported nonstandard terminals.
Associated with each terminal class are specific terminal operating characteristics. Default >rt^.
values are listed in appendix J. A site can change these default values. If it does, it 1
should provide you with a list of the new values. You can also change terminal character
istics with the TRMDEF command (section 8) and with the terminal definition commands
(appendix J). Important characteristics which may vary from terminal to terminal include:
Abort output block character (AB).
Backspace character (BS).
Cancel character (CN).
Control character (CT).
End-of-line character (EL).
End-of-block character (EB).
Interruption character (Bl).
Termination character (B2).
INPUT/OUTPUT CONVENTIONS
There are many standards and conventions that apply to input and output. Some features,
however, vary according to terminal class as this section indicates. The information in
this section pertains to line mode operations only.
INPUT FROM TERMINAL
The system normally issues you input prompts. However, you need not wait for an input prompt
before entering the next input line (refer to Entering Input Before Prompts later in this
section). Any input from the terminal halts output to the terminal until you enter a
A question mark (?) output to the terminal is usually a request from an executing program
for user input. You can enter terminal definition commands in response to any request for
input. For example, when you are in text mode or are using Text Editor or FSE. If you
enter a terminal definition command following a request for input, the system does not send
a new prompt.
If you are at a PSN terminal, however, you must wait for output to cease before entering ^^\
more input. !
16-2 60459680 F
![](asset-23d.png)
LENGTH OF OUTPUT/INPUT LINES
A logical input line can consist of a maximum of 2500 characters,t but the system does not
impose a limit on the length of a logical output line. The current page widthtt determines
the maximum number of characters in a physical output line. If a logical output line
exceeds the current page width, the system places the additional characters on the next
physical line. If you enter a logical input line (terminated by a carriage return) longer
than 2500 characters, the system discards the entire logical line and issues the *0VL*
message.
TERMINATING INPUT LINE
The line feed key, which terminates physical lines, and the carriage return key, which
terminates logical lines, vary with terminal class. Appendix K lists the carriage return,
line feed, and message transmission keys for the various terminal classes. Line feed and
carriage return are generic terms which represent characters that terminate a line of text.
The logical end-of-line character can be changed by you (refer to the EL command In appendix
J), your application, or by your local site.
You must terminate each logical line of input by entering a carriage return. This tells the
system that the current logical line is complete. The system may respond by positioning the
carriage (or cursor) at the beginning of the next line. You can then enter additional input
information on the new line.ttt
You continue a logical line on a new physical line by entering a line feed. The system
responds by positioning the carriage (or cursor) at the beginning of the next line.
CORRECTING INPUT UNE
You can correct entry errors in the input line before pressing® by using the backspace
character. One character (including spaces) is deleted for each backspace character
entered. If the beginning of the physical line is reached, further backspace characters are
ignored. For example, when the Input line contains
BAX«—SJK««— IC
it is interpreted by the system as the BASIC subsystem selection command (or a line of text
interpreted as the word BASIC, if you are in text mode).
The backspace character can be changed by you (refer to the BS command in Appendix J), your
application, or by your site.
tThis applies only to IAF and can be changed by your site.
tt This ch ar act er ist ic v ar ies wi th t he t er min al c la ss. You can chan ge t hi s ch arac te ris ti c
with the TRMDEF command (section 8) or with one of the terminal definition commands
(appendix J),
tttA PSN does not normally reposition its terminals to the next line until It sends the next
output message. You must reposition the carriage on terminals connected to a PSN (for
example, by entering a carriage return in local mode in order to enter input before the
system prompts for it).
60459680 F 16-3
![](asset-23e.png)
DELETING INPUT LINE
When you discover an error in the command or other input before pressing @, you can delete
the current logical input line by entering the cancel line charactert followed by a carriage
return. For most terminals, this is CTRL/X or the ( character. Default values for each
terminal class are given in appendix J.
The network responds to the cancel line character by printing *DEL* on the next line and
positioning the carriage or cursor to the beginning of a new line. The following example
illustrates the use of the cancel line character.
READY.
10 program t
20 print 6
30 6 format 9'this is a test You enter the cancel line character.
*DEL*
30 6 format
40 end
List
( ' t h i s i s i t ' )
10 PROGRAM T
20 PRINT 6
30 6 FORMAT ('THIS IS
40 END
CT')
READY.
ENTERING INPUT BEFORE PROMPTS
Under IAF, you normally wait for an input prompt before entering data or commands. This
prompt appears as either a READY message, a slant (/), a question mark (?), or a
program-defined prompt. You can, however, enter input before receiving a prompt; the system
processes the input in the order that you enter it. The prompts the system issues after
processing individual commands still appear at the terminal in their normal manner. If you
enter too many commands before receiving an input prompt, the system issues the following
message;
WAIT..
You should then reenter the unprocessed commands after the system issues its REPEAT., prompt.
Even if it is currently processing another command, the system processes these three types
of input immediately: terminal definition commands, interactive status commands, and user
break sequences (interruption and termination sequences).
Terminal definition commands change the terminal's characteristics,
detailed description of terminal definition commands. Appendix J gives a
Interactive status commands get an immediate status response from the system. The
interactive status commands, ctD, ctE, and ctS, use the network control character defined
for your terminal (refer to table J-l). Detailed descriptions of ctD, ctE, and ctS appear
in section 8.
TThis characteristic varies with the terminal class. You can change this characteristic
with the TRMDEF command (section 8) or with one of the terminal definition commands
(appendix J).
16-4 60459680 C
![](asset-23f.png)
y^ff^Sy
n
0O^\
PAGE WAIT
Each terminal class defines a certain number of lines of output as a page.t For a display
terminal with page wait enabled, output stops at each page boundary. To display the next
page, you can enter a carriage return .tt For a printing terminal with page wait enabled, the
system inserts six line feeds at each page boundary and output continues. If output ceases
and the message
OVER..
is displayed at the end of the output, while the present page is not full, another page
exists and can be viewed by pressing (cr) .
SUSPENDING OUTPUT
The procedure for suspending output varies with the terminal type. To suspend output on
asynchronous terminals (terminal classes 1 through 8), you can press the BREAK key (the
BREAK key is sometimes labeled INT, INTRPT, or ATTN). You can also suspend output by
pressing any other key.ttt You can then enter the cancel line character (CN)t followed by a
carriage return to continue output and to avoid having the keyed entry interpreted as input.
Synchronous terminals do not have a BREAK key. You cannot suspend output on these
terminals, except through the normal page wait controls.
After suspending output with the BREAK key, you can either abort the current output block,
interrupt the current job step, or terminate the current job step. The next three
subsections define the procedures for each of these options. If you enter input other than
the controls described in the following sections, the system resumes output.
ABORTING OUTPUT BLOCK
To abort the current output block, first suspend output by pressing the BREAK key and then
enter the abort block character followed by a carriage return .tttt
tThis characteristic varies with the terminal class. It can be changed using the TRMDEF
command (section 8) or one of the terminal definition commands (appendix J).
ttFor mode 4 terminals, enter the network control character (ct) followed by a carriage
return to see the next page.
tttOn asynchronous terminals connected to a PSN, you can only suspend output by using the
BREAK key, which might result in the loss of data the PSN holds.
tttTA PSN does not support the abort output block feature for its terminals.
60459680 C 16-5
![](asset-240.png)
INTERRUPTING JOB STEP
To interrupt a job step, you enter the interruption charactert followed by a carriage
return. For most terminals, the interruption character is CTRL/P, CTRL/F, or a colon (:).
Appendix J lists the default values for each terminal class. The interruption sequence is
also called the user break 1 sequence. IAF responds with the message:
INTERRUPTED*
and discards any input you may have previously entered.
If the system Is transmitting output to the terminal, first suspend output by pressing the
BREAK key and then enter the interruption sequence. To interrupt output on synchronous
terminals, you can enter the interruption sequence only when output ceases at a page
boundary. You must have already enabled page wait.
TERMINATING JOB STEP
To terminate a job step, enter the termination charactert followed by a carriage return.
For most terminals, the termination character is CTRL/T or a right parenthesis. Appendix J
lists the default values for each terminal class. The termination sequence is also called
the user break 2 sequence. IAF responds with
TERMINATED*
and discards any input you may have entered previously.
If the system is transmitting output to the terminal, first suspend terminal output by
pressing the BREAK key and then enter the termination sequence. To terminate output on
synchronous terminals, you enter the termination sequence only when output ceases at a page
boundary. You must have already enabled page wait.
NOTE
You cannot enter the interruption or )
termination sequence if output has been
suspended with a key other than the BREAK
key or the interruption or termination
character.
tThis characteristic varies with the terminal class. It can be changed using the TRMDEF
command (section 8) or one of the terminal definition commands (appendix J).
16-6 60459680 C
![](asset-241.png)
0^s
r
CONTINUING A SUSPENDED JOB
After you have suspended your job during program execution by entering the interruption
sequence, you can enter one of the following:
Entry Description
@ C o n t i n u e s o u t p u t . A p o r t i o n o f t h e o u t p u t i s l o s t i f t h e p r o g r a m
was transmitting output to the terminal when suspended. When output
is complete, program execution continues.
P Proceeds. If the program was transmitting output to the terminal
when suspended, the system discards the data generated by the
program prior to the interruption sequence. The amount of output
discarded depends on the program being executed. Program execution
continues.
Other Stops. Terminates the job step.
60459680 C 16_7
![](asset-242.png)
The following example illustrates the use of the interruption sequence to interrupt a
FORTRAN 5 program.
List
00100 PROGRAM DO
00110 INTEGER E
00120 DO 10 E=1,300
00130 PRINT*,E
00140 10 CONTINUE
00150 READ*, I, J
00160 PRINT*,I,J
00170 STOP
00180 END
READY.
run
1
2
3
•INTERRUPTED*
©
110
111
112
•INTERRUPTED*
@
p@>
193
194
195
196
•INTERRUPTED*
P@
? 4,5
4 5
SRU 0.863 UNTS.
RUN COMPLETE.
You interrupt with the BREAK key to stop
output and enter the interruption
sequence to suspend the job. You
continue by pressing (eg) (some output is
lost).
You again press the BREAK key to stop
output and enter the interruption
sequence to suspend the job.
You enter P®, directing the system to
discard data. As execution continues,
more data is printed at the terminal.
You again suspend the job.
You enter P® directing the system to
discard data. All output has been
generated. Program execution continues.
The number of times you would have
to interrupt a program and enter P
before all output has been generated
depends on the program.
y&$$\
USING ATTN ON IBM 2741 TERMINALS
You must press the ATTN key before entering the network control character, abort block
character, interruption character, or termination character or after entering the cancel
character. For further information about these characters, refer to appendix J.
^SJSK
16-8 60459680 C
![](asset-243.png)
CONTROL BYTES
You can design an interactive program to control terminal activity by including control
bytes in your output. Control bytes perform operations such as controlling the positioning
of the printing element and defining alternate input modes.
A control byte is a 12-bit quantity, right-justified in bit position 0, 12, 24, 36, or 48 of
a central memory (CM) word. You must be careful since data can be mistaken for a control
byte. For example, the 64-character set characters :D at the beginning of a line and
followed by an end-of-line may log out your job if written to the terminal output file,
since the code 0004 is transmitted. The following control bytes are available.
Byte Description
0001
or End-of-block.
0002
0003 Auto input.
0004 Log out job.
0005 Initiate ASCII input mode.
0006 Initiate transparent input mode.
0007 Initiate transparent output mode.
0010 NAM/CDCNET terminal redefinition. I
0011 Initiate ASCII output mode.
0013 End-of-string.
0016 NAM/CCP terminal redefinition. |
The use of these control bytes is described in detail in section 12 of Volume 4, Program I
Interface. For additional information, refer to the EFFECT macro description in Volume 4. |
60459680 H 16_9
![](asset-244.png)
r%
0S=%i
![](asset-245.png)
CHARACTER SETS
i«j!fff*S
jrr*Vi\
J^^\
A character set is composed of graphic and control characters. A code set is a. set of codes
used to represent each character within a character set.
A graphic character may be displayed at a terminal or printed by a line printer. Examples
are the characters A through Z and the digits 0 through 9. A control character initiates,
modifies, or stops a control operation. An example is the backspace character that moves
the terminal carriage or cursor back one space. Although a control character is not a
graphic character, a terminal may produce a graphic representation when it receives a
control character.
All references within this manual to the ASCII character set or the ASCII code set refer to
the character set and code set defined in the American National Standard Code for
Information Interchange (ASCII, ANSI Standard X3.4-1977). References in this manual to the
ASCII character set do not necessarily refer to the ASCII code set.
NOS supports the following character sets.
• CDC graphic 64- (or 63-) character set.
• ASCII 128-character set.
• ASCII graphic 64- (or 63-) character set.
• ASCII graphic 95-character set.
Each installation selects either the 64-character set or the 63-character set. The
differences between the two are described in Character Set Anomalies in this appendix. Any
reference in this appendix to the 64-character set implies either the 63- or 64-character
set, unless otherwise stated.
NOS supports the following code sets.
• 6-bit display code.
• 6/12-bit display code.
• 7-bit ASCII code.
Display code is a set of 6-bit codes from 00g to 778.
The 6/12-bit display code is a combination of 6-bit codes and 12-bit codes. The 6-bit codes
are 00g through 778, excluding 74g and 768. (Refer to Character Set Anomalies for
the interpretation of the 00g and 638 codes.) The 12-bit codes begin with either 748
or 76g and are followed by a 6-bit code. Thus, 74g and 768 are considered escape
codes and are never used as 6-bit codes within the 6/12-bit display code set. The 12-bit
codes are 74018, 74028, 74048, 74078, and 76018 through 76778. All other 12-bit
codes (74xx8 and 76008) are undefined.
60459680 C A_2
![](asset-246.png)
/rtssav
The 7-bit ASCII code (as defined by ANSI Standard X3.4-1977) is right-justified in a 12-bit
byte. Assuming that the bits are numbered from the right starting with 0, bits 0 through 6
contain the ASCII code, bits 7 through 10 contain zeros, and bit 11 distinguishes the
OOOOg code from the end-of-line byte. The 7-bit codes are 00018 through 01778 and
40008.
CHARACTER SET ANOMALIES
NOS interprets two codes differently when the installation selects the 63-character set
rather than the 64-character set. In tables A-l, A-2, and A-3, the codes for the colon and
percent graphic characters in the 64-character set are unshaded; the codes for the colon and
percent graphic characters in the 63-character set are shaded.
If an installation uses the 63-character set, the colon graphic character is always "^^fes
represented by a 638 code, and the 008 code is undefined, rbwever, if the installation
uses the 64-character set, output of 6/12-bit display codes 74048 or 6-bit display code
008 produces a colon. In ASCII mode for interactive jobs, a colon can be input only as a
74048 6/12-bit display code.
When using either the 63- or 64-character set, the use of undefined 6/12-bit display codes
in output files produces unpredictable results and should be avoided.
On input, NOS recognizes alternate 029 punch codes of 11-0 for the right bracket (]) and
12-0 for the left bracket ([). The alternate codes support the COBOL sign overpunch
convention and are not recommended for other uses. Refer to COBOL 5 Reference Manual. "**^
Also, two 008 codes may be confused with an end-of-line byte and should be avoided (refer
to appendix F for further explanation) .
Translation of 7-bit ASCII to 6-bit display code causes character set folding from the
128-character ASCII set to the 63- or 64-character ASCII subset. The following special
character substitutions occur:
7-Bit ASCII 6-Bit Display Code 7 - B i t ASCII
Code Character Code Character Code Charac ter
0140 74 0100
0173 61 0133
0174 —> 75 > 0 1 3 4
0175 62 0135
0176 76 0136
CHARACTER SET TABLES
This appendix contains character set tables for interactive jobs, batch jobs, and jobs
involving magnetic tapes. Table A-l is for interactive jobs, and table A-2 is for batch
jobs. Table A-3 is a conversion table used to cross-reference 7-bit ASCII codes and
6/12-bit display codes and to convert ASCII codes from octal to hexadecimal.
Tables A-4, A-5, and A-6 list the magnetic tape codes and their display code equivalents,
A-2 60459680 C
![](asset-247.png)
/ff*\
The character set tables are designed so that you can find the character represented by a
code (such as in a dump) or find the code that represents a character. To find the
character represented by a code, look up the code in the column listing the appropriate code
set and then find the character on that line in the column listing the appropriate character
set. To find the code that represents a character, you first look up the character and then
find the code on the same line in the appropriate column.
INTERACTIVE JOBS
Table A-l shows the character sets and code sets available to you at an ASCII code
terminal. When in NORMAL mode (specified by the NORMAL command), NOS displays the ASCII
graphic 64-character set and interprets all input and output as 6-bit display code. When in
ASCII mode (specified by the ASCII command), NOS displays the ASCII 128-character set and
interprets all input and output as 6/12-bit display code.
To determine the octal or hexadecimal ASCII code for a character, refer to table A-3.
(Certain terminal definition commands require specification of an ASCII code.)
On output, the US code is reserved for network use and defined as an end-of-line. Use of
this character, except in transparent mode, causes incorrect formatting and possible loss of
output characters.
BATCH JOBS
Table A-2 lists the CDC graphic 64-character set, the ASCII graphic 64-character set, and
the ASCII graphic 95-character sets. It also lists the code sets and card punch codes (026
and 029) that represent the characters.
The 64-character sets use display code as their code set; the 95-character set uses 7-bit
ASCII code. The 95-character set is composed of all the characters in the ASCII
128-character set that can be printed at a line printer (refer to jobs using Line Printers),
Only 7-bit ASCII code files can be printed using the ASCII graphic 95-character set. To
print a 6/12-bit display code file (usually created by an interactive job in ASCII mode),
you must convert the file to 7-bit ASCII code. To do this, you enter the FCOPY command
(section 9). The 95-character set is represented by 7-bit ASCII codes 0040g through
01768.
JOBS USING UNE PRINTERS
The batch character set printed depends on the print train used on the line printer to which
the file is sent. In addition, you may choose from one of several subsets of the characters
on the print train by specifying the print train image (for information on specifying print
train images, refer to the ROUTE command in section 9).
The following table lists the print trains according to the associated ROUTE command EC
parameter values.
r60459680 H A-3
![](asset-248.png)
P r i n t
Train
ROUTE EC Values
That Will Print
ROUTE EC Values
That Will Not Print Suggested
Print Band
ot
1
2t
3t
4
5
6
7
N0NE,B4,B6
N0NE,B4,B6
NONE,B4,B6
N0NE,B4,B6
N0NE,A4,A6,A9
N0NE,A4,A6
A9
N0NE,B4,B6,A4,A6,A9
A4,A6,A9
A4,A6,A9
A4,A6,A9
A4,A6,A9
B4,B6
B4,B6,A9
NONE,B4,B6,A4,A6
595-1/596-1
595-1/596-1
595-1/596-1
595-1/596-1
595-6/596-6
595-4/596-4
or
595-5/596-5
595-6/596-6
595-6/596-6
TThese print trains are reserved for future use. If specified, they have the same
effect as if print train 1 had been specified.
For PSU printers, the batch character sets and associated print bands are as follows:
Character Set 533/536 Print Band
ASCII graphic 64-character set
ASCII graphic 95-character set
530-1
530-2
The characters of the default 596-1 print train are listed in the table A-2 column labeled
CDC Graphic (64 Char); the 596-5 print train characters are listed in the table A-2 column
labeled ASCII Graphic (64 Char); and the 596-6 print train characters are listed in the
table A-2 column labeled ASCII Graphic (95 Char).
If a transmission error occurs when printing a line, the system prints the line again. The
CDC graphic print train prints a concatenation symbol (r*0 in the first printable column of
th e rep eat ed l is tin g of t he lin e. Th e A SCI I prin t trai ns pri nt an und erl ine ( ) i ns tea d of
the concatenation symbol.
If an unprintable character exists in a line (that is, a 7-bit ASCII code outside the range
00408 through 01768), the number sign (//) appears in the first printable column of a
print line, and a space replaces the unprintable character.
To route and correctly print a 6/12-bit display code file on a line printer with the ASCII
graphic 95-character set, you must convert the 6/12-bit display code file to a 7-bit ASCII
code file with the FCOPY command (refer to section 9). The resulting 7-bit ASCII file can
be routed to a line printer (refer to the ROUTE command in section 9) but cannot be output
at an in te ract iv e te rmina l.
A-4 60459680 E
![](asset-249.png)
Table A-l. Character Sets for Interactive Jobs (Sheet 1 of 2)
/S™S^
6/12- 6/12-
ASCII ASCII 6-Bit B i t 7-Bit ASCII ASCII 6-Bit B i t 7-Bit
Graphic Character Display Display ASCII Graphic Character Display Display ASCII
(64 Character) (128 Character) Code Code Code ( 6 4 C h a r a c t e r ) ( 1 2 8 C h a r a c t e r ) Code Code Code
: colon 00* * number sign t number sign 60 60 0043
Display t<sxte' 00 ia otidetised at sites using the 63-charucter set. I opening bracket [ opening bracket 61 61 0133
A "" 01 01 0101 ] c l o s i n g b r a c k e t j c l o s i n g b r a c k e t 62 62 0135
BB02 02 0102 Z p e r c e n t s i g n X percent sign 63 63t 0045
CC03 03 0103 * coloa % ,y * colon 63 ' .'63 s ' 0072
DD04 04 0104 " q u o t e " q u o t e 64 64 0042
E E 05 05 0105 _ underline _ underline 65 65 0137
FF06 06 0106 ! exclamation point ! exclamation point 66 66 0041
G G 07 07 0107 & ampersand & ampersand 67 67 0046
' a p o s t r o p h e
apostrophe 70 70 0047
H11 10 10 0 11 0 ? q u e s t i o n m a r k ? q u e s t i o n m a r k 71 71 0077
I I 11 11 0 111 < l e s s t h a n < less than 72 72 0074
J J • 12 12 0112 > g r e a t e r t h a n > g r e a t e r t h a n 73 73 0076
K K 13 13 0113 @ co m m erc i a l at @ co m m e r c i a l a t 74t 7401 0100
L L 14 14 0114 \ r e v e r s e s l a n t \ r e v e r s e s l a n t 75 75 0134
H M 15 15 0115 c i r c u m fl e x circumflex 76t 7402 0136
N N 16 16 0116 ; semicolon ; semicolon 77 77 0073
0017 17 0117
: colon 7404 0072
P
QP20 20 0120 „.._*-«. %~. < ,«y! ^pOtOttO&'fh-t^r-.. 74* ',Wfcb3« MBSStt*.
Q21 21 0121 ' grave accent 7407 0140
R R 22 22 0122
SS23 23 0123 7601 0141
TT24 24 0124 7602 0142
UU25 25 0125 7603 0143
V V 26 26 0126 7604 0144
W U 27 27 0127 7605
7606
0145
0146
X X 30 30 0130 7607 0147
Y Y 31 31 0131
ZZ32 32 0132 7610 0150
0 0 33 33 0060 7611 0151
1 1 34 34 0061 7612 0152
2 2 35 35 0062 7613 0153
3336 36 0063 7614 0154
4 4 37 37 0064 7615
7616
7617
0155
0156
0157
5540 40 0065
6641 41 0066 7620 0160
7742 42 0067 7621 0161
8843 43 0070 7622 0162
9 9 44 44 0071 7623 0163
+ p l u s + p l u s 45 45 0053 7624 0164
- d a s h - d a s h 46 46 0055 7625 0165
* asterisk * asterisk 47 47 0052 7626
7627
0166
0167
/ slant / slant 50 50 0057 7630 0170
( opening parenthesis ( opening parenthesis 51 51 0050 7631 0171
) closing parenthesis ) closing parenthesis 52 52 0051 7632 0172
$ d o l l a r s i g n $ d o l l a r s i g n 53 53 0044 { opening brace 61T 7633 0173
= e q u a l » e q u a l 54 54 0075 1 v e r t i c a l l i n e 75 t 7634 0174
space space 55 55 0040 } closing brace 621 7635 0175
, comma , comma 56 56 0054 ~ tilde 76t 7636 0176
. period . period 57 57 0056 DEL 7637 0177
^The interpretation of this character or code may dep > n d o n i t > c o n t e x t . R e f e r t o C h a r a c t e r S e t A n om a l i e s e l s e w h e r e i n t h i s a p p endix.
/0K>\
60459680 C A-5
![](asset-24a.png)
Table A-l. Character Sets for Interactive Jobs (Sheet 2 of 2)
6/12- 6/12-
ASCII ASCII 6-Bit Bit 7-Bit ASCII ASCII 6-Bit Bit 7-Bit
Graphic Character Display Display ASCII Graphic Character Display Display ASCII
(64 Character) (128 Character) Code Code Code (64 Character) (128 Character) Code Code Code
NUL 7640 4000 OLE 7660 0020
SOH 7641 0001 DC1 7661 0021
STX 7642 0002 DC2 7662 0022
ETX 7643 0003 DC3 7663 0023
EOT 7644 0004 DC4 7664 0024
ENQ 7645 0005 NAK 7665 0025
ACK 7646 0006 SYN 7666 0026
BEL 7647 0007 ETB 7667 0027
BS 7650 0010 CAN 7670 0030
HT 7651 0011 EM 7671 0031
LF 7652 0012 SUB 7672 0032
VT 7653 0013 ESC 7673 0033
FF 7654 0014 FS 7674 0034
CR 7655 0015 GS 7675 0035
SO 7656 0016 RS 7676 0036
SI 7657 0017 ust 7677 0037
tReserved for network use. Refer to Character Set Tables in this appendix.
S&^s
A-6 6045% 80 C
![](asset-24b.png)
Table A-2. Character Sets for Batch Jobs (Sheet 1 of 3)
CDC ASCII ASCII 6-Bit 6/12-Bit 7-Bit
Graphic
(64 Character)
Graphic
(64 Character) Graphic
(95 Character)
Display
Code Display
Code
ASCII
Code
Punch Code
026 029
: colont : colont oot 8-2 8-2
AIWM^S^^M ol u ^ W 12-1
BB B 02 02 0102 12-2 12-2
CCC 03 03 0103 12-3 12-3
D D D 04 04 0104 12-4 12-4
EEE 05 05 0105 12-5 12-5
F F F06 06 0106 12-6 12-6
G G G07 07 0107 12-7 12-7
HH H 10 10 0110 12-8 12-8
III 11 11 0111 12-9 12-9
J J J 12 12 0112 11-1 11-1
K K K13 13 0113 11-2 11-2
L L L 14 14 0114 11-3 11-3
M M M 15 15 0115 11-4 11-4
N N N16 16 0116 11-5 11-5
0 0 017 17 0117 11-6 11-6
PP P 20 20 0120 11-7 11-7
Q Q Q21 21 0121 11-8 11-8
R R R22 22 0122 11-9 11-9
S S s23 23 0123 0-2 0-2
TTT 24 24 0124 0-3 0-3
U U U25 25 0125 0-4 0-4
V V V 26 26 0126 0-5 0-5
W W W27 27 0127 0-6 0-6
X X X 30 30 0130 0-7 0-7
Y Y Y 31 31 0131 0-8 0-8
Z Z Z 32 32 0132 0-9 0-9
0 0 0 33 33 0060
1 1 134 34 0061
2 2 2 35 35 0062
3 3 3 36 36 0063
4 4 4 37 37 0064
5 5 5 40 40 0065
6 6 6 41 41 0066
7 7 7 42 42 0067
888 43 43 0070
99 9 44 44 0071
+ plus + plus + plus 45 45 0053 12 12-8-6
- dash - dash - dash 46 46 0055 11 11
* as t e r i s k * as te ri sk * asterisk 47 47 0052 11-8-4 11-8-4
tThe inte r p reta t i on of this character or code may depend on its context. Refer to Chara cter Set Anomalies
elsewhere in this appendix.
60459680 C A-7
![](asset-24c.png)
Table A-2. Character Sets for Batch Jobs (Sheet 2 of 3)
r^BSV
CDC ASCII ASCII 6-Bit 6/12-Bit 7-Bit
Graphic
(64 Character)
Graphic
(64 Character)
Graphic
(95 Character) Display
Code Display
Code
ASCII
Code
Punch Code
026 029
/ slant / slant / slant 50 50 0057 0-1 0-1
( opening parenthesis ( opening parenthesis ( opening parenthesis 51 51 0050 0-8-4 12-8-5
) closing parenthesis ) closing parenthesis ) closing parenthesis 52 52 0051 12-8-4 11-8-5
$ dollar sign $ dollar sign $ dollar sign 53 53 0044 11-8-3 11-8-3
= equal = equal = equal 54 54 0075 8-3 8-6
space space space 55 55 0040 no punch no punch
, comma , comma , comma 56 56 0054 0-8-3 0-8-3
. period . period . period 57 57 0056 12-8-3 12-8-3
— equivalence // number sign // number sign 60 60 0043 0-8-6 8-3
[ opening bracket [ opening bracket [ opening bracket 61 61 0133 8-7 12-8-2t
] closing bracket ] closing bracket ] closing bracket 62 62 0135 0-8-2 ll-8-2t
% percent signt % percent signt % percent signt 63t 63t 0045 8-6 0-8-4
wi$i%&m£f^j/t s$K*"$;&mz;?* ■ yyr?\ w -mxo& \y "' 5 c<y - c ,~Z*tes&V ^ y ;&*&« i ^jy#-£2"y*7'$:&tj:
r not equal quote " q u o t e < % " " 'T''-" t f " J mtr* ™"*#-7t * vW &*&WW>?'s
r* concatenation _ underline __ underline 65 65 0137 0-8-5 0-8-5
V logical OR ! exclamation point ! exclamation point 66 66 0041 11-0 12-8-7
A logical AND & ampersand & ampersand 67 67 0046 0-8-7 12
^ superscript ' apostrophe apostrophe 70 70 0047 11-8-5 8-5
>J, subscript ? question mark ? question mark 71 71 0077 11-8-6 0-8-7
< less than < less than < less than 72 72 0074 12-0 12-8-4
> greater than > greater than > greater than 73 73 0076 11-8-7 0-8-6
< less or equal @ commercial at lit 8-5 8-4
> greater or equal \ reverse slant \ reverse slant 75 75 0134 12-8-5 0-8-2
- logical NOT * circumflex 76 12-8-6 11-8-7
; semicolon ; semicolon ; semicolon 77 77 0073 12-8-7 11-8-6
@ commercial at 74t 7401 0100
" circumflex 76t 7402 0136
: colont. Wt « WJ, tr
y^&\$*£$'» r*> y- -. *ipi'&t r- ^;- * ^y ^y *** M;kw$Mi&iM?$ \ \ *%? ■▶s«^*#>^ 5*v%'$ ^>imti«H
&ztV~w&£LT$?:%
* grave accent V*74"Y " 746Y '6i4cT v
a7601 0141
b7602 0142
c7603 0143
d7604 0144
e7605 0145
f7606 0146
g7607 0147
tThe interpretation of this character or c ode may depend on its context. Refer to Char acter Set Anomalies
elsewhere in this appendix.
,<«3^SV
A-8 60459680 C
![](asset-24d.png)
Table A-2. Character Sets for Batch Jobs (Sheet 3 of 3)
CDC ASCII ASCII 6-Bit 6/12-Bit 7-Bit
Graphic
(64 Character)
Graphic
(64 Character)
Graphic
(95 Character)
Display
Code Display
Code
ASCII
Code
Punch Code
026 029
h7610 0150
i 7611 0151
j7612 0152
k7613 0153
17614 0154
m7615 0155
n7616 0156
07617 0157
P7620 0160
q7621 0161
r7622 0162
s7623 0163
t7624 0164
u7625 0165
V7626 0166
w7627 0167
X7630 0170
y7631 0171
z7632 0172
{ opening brace 6lt 7633 0173
| vertical line 75t 7634 0174
} closing brace 62t 7635 0175
~ tilde 76t 7636 0176
tThe in t e r pretation of th is ch aracter or code may depend on its context. Refer to Character Set Anomalies
elsewhere in this appendix.
60459680 C A-9
![](asset-24e.png)
Table A-3. ASCII to 6/12-Bit Display Code Conversion (Sheet 1 of 2)
ASCII
Character
(128 Character)
7-Bit
ASCII Code
Octal Hexadecimal
6/12-Bit
Display
Code
ASCII
Character
(128 Character)
7-Bit
ASCII Code
Octal Hexadecimal
6/12-Bit
Display
Code
NUL
SOH
STX
ETX
EOT
ENQ
ACK
BEL
BS
HT
LF
VT
FF
CR
SO
SI
DLE
DC1
DC2
DC3
DC4
NAK
SYN
ETB
CAN
EM
SUB
ESC
FS
GS
RS
USt
space
! exclamation point
" quote
il number sign
$ dollar sign
% percent signtt
'^Wr^^ti^T^^- -''
& ampersand
' apostrophe
( opening parenthesis
) closing parenthesis
* asterisk
+ plus
, comma
- dash
. period
/ slant
4000
0001
0002
0003
0004
0005
0006
0007
0010
0011
0012
0013
0014
0015
0016
0017
0020
0021
0022
0023
0024
0025
0026
0027
0030
0031
0032
0033
0034
0035
0036
0037
0040
0041
0042
0043
0044
0045
^$;:
0046
0047
0050
0051
0052
0053
0054
0055
0056
0057
00
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
OF
10
11
12
13
14
15
16
17
18
19
1A
IB
IC
ID
IE
IF
20
21
22
23
24
25
'26
27
28
29
2A
2B
2C
2D
2E
2F
7640
7641
7642
7643
7644
7645
7646
7647
7650
7651
7652
7653
7654
7655
7656
7657
7660
7661
7662
7663
7664
7665
7666
7667
7670
7671
7672
7673
7674
7675
7676
7677t
55
66
64
60
53
63tf
67
70
51
52
47
45
56
46
57
50
4 '
5
6
7
8
9
: colontt
; semicolon
< less than
= equal
> greater than
? question mark
@ commercial at
A
B
C
D
E
F
G
H
I
J
K
L
M
N
0
P
Q
R
S
T
U
V
W
X
Y
Z
[ opening bracket
\ reverse slant
] closing bracket
* circumflex
underline
0060
0061
0062
0063
0064
0065
0066
0067
0070
0071
0072
0073
0074
0075
0076
0077
0100
0101
0102
0103
0104
0105
0106
0107
0110
0111
0112
0113
0114
0115
0116
0117
0120
0121
0122
0123
0124
0125
0126
0127
0130
0131
0132
0133
0134
0135
0136
0137
30
31
32
33
34
35
36
37
38
39
3A
3C
3D
3E
3F
40
41
42
43
44
45
46
47
48
49
4A
4B
4C
4D
4E
4F
50
51
52
53
54
55
56
57
58
59
5A
5B
5C
5D
5E
5F
33
34
35
36
37
40
41
42
43
44
7404tt
77
72
54
73
71
7401
01
02
03
04
05
06
07
10
11
12
13
14
15
16
17
20
21
22
23
24
25
26
27
30
31
32
61
75
62
7402
65
tReserved for network use. Refer to Character Set Tables in this appendix.
ttThe interpretation of this character or code may depend on its context. Refer to Character Set Anomalies in
this appendix.
A-10 60459680 C
,XSSv
![](asset-24f.png)
Table A-3. ASCII to 6/12-Bit Display Code Conversion (Sheet 2 of 2)
ASCII 7-Bit 6/12-Bit ASCII 7-Bit 6/12-Bit
Character
(128 Character)
ASCII Code Display
Code
Character
(128 Character)
ASCII Code Display
Code
Octal Hexadecimal Octal Hexadecimal
v grave accent 0140 60 7407 0160 70 7620
a0141 61 7601 0161 71 7621
b0142 62 7602 0162 72 7622
c0143 63 7603 0163 73 7623
d0144 64 7604 0164 74 7624
e0145 65 7605 0165 75 7625
f0146 66 7606 0166 76 7626
g0147 67 7607 0167 77 7627
h0150 68 7610 0170 78 7630
i0151 69 7611 0171 79 7631
j0152 6A 7612 0172 7A 7632
k0153 6B 7613 { opening brace 0173 7B 7633
10154 6C 7614 I vertical line 0174 7C 7634
m0155 6D 7615 } closing brace 0175 7D 7635
n0156 6E 7616 ~ tilde 0176 7E 7636
o0157 6F 7617 DEL 0177 7F 7637
60459680 C A-ll
![](asset-250.png)
JOBS USING MAGNETIC TAPES
Coded data to be copied from mass storage to magnetic tape is assumed to be represented in
display code. NOS converts the data to external BCD code when writing a coded seven-track
tape and to ASCII or EBCDIC code (as specified on the tape assignment command) when writing
a coded nine-track tape.
Because only 63 characters can be represented in seven-track even parity, one of the 64
display codes is lost in conversion to and from external BCD code. The following shows the
differences in conversion depending on the character set (63 or 64) which the system uses.
The ASCII character for the specified character code is shown in parentheses. The output
arrow shows how the 6-bit display code changes when it is written on tape in external BCD.
The input arrow shows how the external BCD code changes when the tape is read and converted
to 6-bit display code.
63-Character Set
6-Bit Display Code
00
33 (0) Output*
63 (:)
External BCD
16 (%)
12 (0)
12 (0)
Input
6-Bit Display Code
00
33 (0)
33 (0)
64-Character Set
6-Bit Display Code
00 (:)
33 (0)
63 (%)
Output
External BCD
12 (0)
12 (0)
16 (%)
6-Bit Display Code
Input
33 (0)
33 (0)
63 (%)
If a lowercase ASCII or EBCDIC code is read from a nine-track coded tape, it is converted to
its uppercase 6-bit display code equivalent. To read or write lowercase ASCII or EBCDIC
characters, you must assign the tape in binary mode and use FCOPY to read or write the tape.
Tables A-4 and A-5 show the character set conversion for nine-track tapes. Table A-4 lists
the conversions to and from the 7-bit ASCII character code and 6-bit display code. Table
A-5 lists the conversions between the EBCDIC character code and the 6-bit display code.
Table A-6 shows the character set conversions between external BCD and 6-bit display code
for seven-track tapes.
A-l 2 60459680 D
![](asset-251.png)
J0**\
Table A-4. Nine-Track ASCII Coded Tape Conversion
6-Bit 6-Bit
Display Display
7-Bit ASCII Code 7-bit ASCII Code
Code Code Code Code Code Code
(Hex) Chart (Hex) Chartt Char (Octal) (Hex) Chart (Hex) Chartt Char (Octal)
20 space 00 NUL space 55 3E IE RS 73
21 7D 66 3F IF US 71
22 ii 02 STX ii 64 40 60 74
23 03 ETX 60 41 61 01
24 04 EOT 53 42 62 02
25 05 ENQ 63 43 63 03
f2*' f b *y * ; y $ 5 - ;^$$^y x«i»«a#ft U»-<\; > » 44 64 04
26 06 ACK 67 45 65 05
27 07 BEL 70 46 66 06
28 08 BS 51 47 67 07
29 09 HT 52 48 68 10
2A 0A LF 47 49 69 11
2B 0B VT 45 4A 6A 12
2C OC FF 56 4B 6B 13
2D 0D CR 46 4C 6C 14
2E 0E SO 57 4D 6D 15
2F OF SI 50 4E 6E 16
30 10 DLE 33 4F 6F 17
31 11 DC1 34 50 70 20
32 12 DC2 35 51 71 21
33 13 DC3 36 52 72 22
34 14 DC4 37 53 73 23
35 15 NAK 40 54 74 24
36 16 SYN 41 55 75 25
37 17 ETB 42 56 76 26
38 18 CAN 43 57 77 27
39 19 EM 44 58 78 30
3A 1A SUB 00 59 79 31
* *HBt*fc 4&pl&f % &4& 0$. is ,ipiefixmo at a&top, «4i«g- 5A
5B
7A
IC FS
32
61
3A * " 14 - $m * '- ' * v * $ y . ^ 5C 7C 75
3B IB ESC 77 5D 01 SOH 62
3C 7B 72 5E 7E 76
3D ID GS 54 5F 7F DEL 65
tWhen these characters are copied from/or to a tape , the characters remain the same but the codes change
from one code set to the other.
ttThese characters do not exist in 6-bit display code. Therefore, when the characters are copied from a
tape, each 7-bit ASCII character is changed to an alternate 6-bit display code charact e r . T h e
corresponding codes are also changed. Example: Wtien the system copies a lowercase a, 6116, from tape,
it writes an uppercase A, Olg.
tttA 6-bit display code space always translates to a 7-bit ASCII space.
60459680 E A-l 3
![](asset-252.png)
Table A-5. Nine-Track EBCDIC Coded Tape Conversion
EBCDIC
Code
(Hex)
40
4A
4B
4C
4D
4E
4F
50
5A
5B
5C
5D
5E
5F
60
61
6B
6D
6E
6F
7A
7B
7C
7D
7E
7F
Cl
C2
C3
Chart
space
i
<
(
+
Code
(Hex)
00
IC
0E
CO
16
OB
DO
2E
01
37
25
05
27
Al
OD
OF
OC
2D
07
IE
IF
3F
C h a r t t
NUL
IFS
SO
{
BS
VT
}
ACK
SOH
EOT
LF
HT
ESC
6-Bit
Display
Code
C h a r t t
space
[
<
(
+
t
&
]
$
Code
(OcVal)
55
61
57
72
51
45
66
67
62
53
47
52
77
76
46
50
56
63
03 ETX
79
2F BEL
ID IGS
02 STX
81
82
83
60
74
70
54
64
01
02
03
EBCDIC
Code
(Hex)
C4
C5
C6
C7
C8
C9
DI
D2
D3
D4
D5
D6
D7
D8
D9
EO
E2
E3
E4
E5
E6
E7
E8
E9
FO
Fl
F2
F3
F4
F5
F6
F7
F8
F9
Chart
Code
(Hex) Char
84
85
86
87
88
89
91 .1
92
93
94
95
96
97
98
99
6A
A2
A3
A4
A5
A6
A7
A8
A9
10 DLE
11 DC1
12 DC 2
13 TM
3C DC4
3D NAK
32 SYN
26 ETB
18 CAN
19 EM
6-Bit
Display
Code
Char
Code
(Octal)
04
05
06
07
10
11
12
13
14
15
16
17
20
21
22
75
23
24
25
26
27
30
31
32
33
34
35
36
37
40
41
42
43
44
tWhen these character? are copied from/or to a tape, the characters remain the same (except EBCDIC codes
4A, 4F, 5A, and 5F) but the codes change from one code set to the other.
ttThese characters do not exist in 6-bit display code. Therefore, when the characters are copied from a
tape, each EBCDIC character is changed to an alternate 6-bit display code character. The corresponding
codes are also changed. Example: When the system copies a lowercase a, 81jg, from tape, it writes an
uppercase A, 01 g.
TTtAll EBCDIC codes not listed translate to 6-bit display code 55g (space). A 6-bit display code space
always translates to an EBCDIC space.
A-14 60459680 C
![](asset-253.png)
j0^\
Table A-6. Seven-Track Coded Tape Conversions
6-Bit 6-Bit
Display Display
External ASCII Code Ex ternal ASCII Code
BCD Character (Octal) BCD Character (Octal)
01 34 40 46
02 35 41 12
03 36 42 13
04 37 43 14
05 40 44 15
06 41 45 16
07 42 46 17
10 43 47 20
11 44 50 21
12t 33 51 22
13 54 52 66
14 ii 64 53 53
15 74 54 47
16T 63 55 70
17 61 56 71
20 space 55 57 73
21 50 60 45
22 23 61 01
23 24 62 02
24 25 63 03
25 26 64 04
26 27 65 05
27 30 66 06
30 31 67 07
31 32 70 10
32 62 71 11
33 56 72 72
34 51 73 57
35 65 74 52
36 60 75 75
37 67 76 76
"977
tAs explained previously in this section, conversion
of these codes depends on whether the tape is being
read or written.
JfSss
60459680 C A-15
![](asset-254.png)
![](asset-255.png)
DIAGNOSTIC MESSAGES
This appendix contains an alphabetical listing of the messages that may appear in your
dayfile. Lowercase characters are used to identify variable names or fields. All messages
are sorted according to the first nonvariable word or character. Messages beginning with
special characters (such as hyphens or asterisks are sorted as if the special characters
were not present. For example, the message
filename ALREADY PERMANENT,
is listed with the messages beginning with A, and the message
****ENDING SUPPORT OF LFM FUNCTION nnB.
is listed with the messages beginning with E.
Dayfile messages usually issued only to COMPASS programs are listed in appendix B of
Volume 4, Program Interface.
If you encounter a diagnostic or informative message that does not appear in this appendix,
consult the NOS 2 Diagnostic Index. This publication catalogs all messages produced by NOS
and its products and specifies the manual or manuals in which each message is fully
documented.
All pages are at revision level H. Only changed or new messages are indicated by change
bars.
60459680 H B-l
![](asset-256.png)
MESSAGE
ABSC, sc.
cmd ACCEPTED..
ACCESS CATEGORIES NOT VALID FOR JOB.
ACCESS LEVEL NOT VALID FOR FILE.
ACCESS LEVEL NOT VALID FOR JOB.
ACCESS LEVEL NOT VALID ON PF DEVICE.
ACCOUNT BLOCK LIMIT.
ADDING FILE lfn TO DATABASE.
ADDING TAPE vsn TO DATABASE.
ADDRESS OUT OF RANGE.
ADDRESS OUT OF RANGE address.
AFD - INPUT FILE NOT FOUND.
AFD - UNEXPECTED EOF/EOI ENCOUNTERED.
ALL EQ.-S CHECKPOINTED.
RECOVERY ABORTED.
filename ALREADY PERMANENT.
B-2
SIGNIFICANCE
An informative message indicating the
initial service class of your job.
sc Service class
The network has accepted your terminal
definition command cmd.
You attempted to use the SETPFAC command
or macro to set one or more permanent file
access categories for which you are not
validated.
One of the following:
You attempted to save a local file
using an access level for the
permanent file that is not valid for
the device on which the local file
resides.
You attempted to define an existing
local file as a direct access
permanent file using an access level
for the permanent file that is not
valid for the device on which the
local file re sides.
One of the following:
You attempted to save a local file
at an access level that is not valid
for your job.
You attempted to define an existing
local file as a direct access
permanent file at an access level
that is not valid for your job.
You attempted to set an access level
for a permanent file that is not
valid for your job using the SETPFAL
command or macro.
On a SAVE, DEFINE, or SETPFAL command or
macro, you specified an access level that
is outside the range of access levels
allowed on your permanent file device.
The monitor detected the expiration of the
account block SRU limit.
ACTION
File lfn is being read; RECLAIM is
adding information for this file to
your database.
Tape with VSN vsn is being read; RECLAIM is
adding information for this tape to your
database.
An address in a parameter block is outside
the job's field length.
LOC read an address on a correction
statement that is greater than or equal to
the job's field length. The correction
statement is ignored and LOC continues.
The file specified by the I=filename
parameter is not a local file.
An EOF or EOI was encountered before the
PRU count was depleted on the input file.
The dayfile is shorter than expected based
on the PRU count.
In the process of aborting a CM recovery,
1CK was called to process all outstanding
checkpoint requests.
You have already saved or defined a file
with the name specified.
None.
None.
Retry using a set of
access categories for
which you are validated
and that is valid for
your job.
Retry using an access
level for the permanent
file that is not lower
than the access level of
the local file.
ROUTINE
CLASS
CCP
PFM
Retry using a valid access
level. PFM
/*S^\
Inform security
administrator that
your permanent file
device is not valid for
all the access levels
for which you are
validated.
Reset account block SRU
limit with SETASL
command or macro. If
the account block limit
is set at its maximum,
issue another CHARGE
command to begin a new
account block.
None.
None.
Specify parameter block
address within field
length.
Correct the correction
statement(s) and retry.
Retry using a local file.
Retry operation.
Level 0 deadstart
required.
Save or define file
using different file
name or purge existing
fi l e .
PFM
1AJ
RECLAIM
CPMEM
DAYFILE
1CK
60459680 H
![](asset-257.png)
MESSAGE
ALTERNATE IMAGE OBSOLETE.
ALTERNATE STORAGE ERROR.
APPENDED - type/name
SIGNIFICANCE
The disk space for the file cannot be
r e l e a s e d b e c a u s e t h e a l t er n a t e s t o r a g e
image is labeled obsolete or the alternate
storage address is not specified in the
permanent file catalog.
I t i s n o t p o s s ib le t o d r o p t h e d i s k s p ac e
associated with the specified permanent
file, since an error exists on the
alternate storage copy of the file.
The record with type and name on the
replacement file was not matched; it has
b e e n a p p en d ed t o t h e n e w fi l e . A o p ti o n
selected.
ACTION ROUTINE
None.
None.
PFM
COPYL
COPYLM
APPLICATION NAME IS REQUIRED.
APPLICATION NOT PRESENT.
APPLICATION RETRY LIMIT.
ARA BURST DEFFECTIVE.
ARG. ERROR.
ARGUMENT ERROR.
ARGUMENT ERRORS.
ARITHMETIC INDEFINITE.
ARITHMETIC OVERFLOW.
ARITHMETIC UNDERFLOW.
est, ASSIGNED TO filename,
ttest, ASSIGNED TO filename,
jsn ASSIGNS EXCEED DEMANDS.
ATTRIBUTE COMMANDS MUST 8E OF ONE NETWORK
TYPE.
You entered an APPSW command that did not
specify a secondary application.
The requested application is currently not
available for use.
Four unsuccessful attempts were made to
enter a legal application name, after which
t h e t e r m i n a l w a s d i s c o n n e c t e d .
First block of tape at 1600 or 6250 cpi
c a n n o t b e r e a d o r w r i t t e n . A n o t h e r u n i t o r
tape should be tried. The dayfile message
STATUS ERROR, filename AT address precedes
this message and specifies the file
(filename) and the address addr.
LDR parameters were outside your job's
fi e l d l e ng t h o r t h e c e n t r a l m e m o r y a d d r e s s
in call is not within your job's field
length.
Th e c o m m a n d s y n t ax i s i n c o r r e c t . W h e n t h e
system processes tape management commands,
for example, it issues this message if both
ring enforcement options (P0=R and P0=W) or
mo re than one EOT option (P0= I, P0=P, and
P0=S) is specified. Also specification of
duplicate parameters (more than one
occurrence of a keyword) or multiple
equivalent parameters (such as MT/NT,
C B / C K , F I / L , R / W, a n d s o f o r t h ) i s n o t
allowed on a tape assignment command. The
address parameter on DMPECS, DMDECS, LBC,
LOC, PBC, or WBR must be numeric.
The ENQUIRE command's syntax is incorrect.
The CPU floating-point arithmetic unit
a t t e m pt e d t o u s e a n i n d efi n i te o p e r a nd .
The CPU floating-point arithmetic unit
received an operand too large for
computation.
The CPU floating-point arithmetic unit
received an operand too small for
computation.
Informative message specifying EST ordinal
assigned to file filename.
Eq u i p m e n t t yp e t t w i t h E S T or d i n a l e s t w a s
assigned to file filename.
System error. The resources actually
assigned to the job with the specified job
sequence name exceed the resources demanded
on a RESOURC command.
Ter m in al a tt r i b ut e s u ni q u e to N AM / CC P a n d
to NAM/CDCNET were specified on the same
TRMDEF command.
Reenter the command with
the appl parameter
specified.
Ent e r t he name of
another application or
l o g o f f a n d t r y l a t e r.
Check the accuracy of
the entry. If problems
persist, contact
installation personnel.
Retry or inform site
analyst.
Examine program to
d e t e r m i n e e r r o r.
Reenter command using
the correct parameters
and syntax.
Check parameters on
command and retry.
Analyze the job output
and dumps to determine
the cause.
Analyze the job output
and dumps to determine
the cause.
Analyze the job output
and dumps to determine
the cause.
None.
None.
I n f o r m s i t e a n a l y s t .
On the TRMDEF command,
check to ensure that all
terminal attributes are
supported by your
network type.
NETVAL
1MT
LDR
COPYB
CPMEM
FOTD
LDI
L072
RECOVER
RESEX
SU8SYST
COPYB
ENQUIRE
1AJ
1AJ
1AJ
LFM
LFM
TRMDEF
60459680 H 8-3
![](asset-258.png)
MESSAGE
BAD CATALOG/PERMIT SECTOR.
BAD DATA IN OLDPL HEADER
BAD FCOPY CONVERSION TABLE.
n BAD FORMAT BLOCKS.
BINARY SEQ. ERROR, RECxxxx CDyyyy.
BLANK LABELS DO NOT VERIFY.
BLANK TAPE, filename AT address.
BLOCK NUMBER nnnnnn, filename AT address.
BLOCK SEQUENCE ERROR, filename AT address.
BLOCK SIZE NOT APPLICABLE.
BLOCK SIZE TOO LARGE ON filenam.
BLOCK SIZE TOO SMALL ON filename.
BLOCK TOO LARGE, filename AT address.
BLOCK TOO LONG FOR BUFFERS.
BOT/EOT ENCOUNTERED, filename AT address.
BREAKPOINT CONDITION.
BUFFER ARG. ERROR.
SIGNIFICANCE
PFM has encountered a catalog or permit
sector which does not have a valid sector
length. This indicates corruption of
system areas on disk.
The file is a program library but its
program library is not of a recognizable
format.
FCOPY tables are in error.
Block(s) not meeting X or Si-coded
conversion requirements have been
encountered on input.
A binary command was found to be out of
sequence and the job was terminated without
EXIT processing. Error is on command yyyy
of record xxxx.
The tape labels written on the blank tape
could not be verified, probably due to
hardware failure.
A blank tape was read. Blank tape is
defined as more than 25 feet of erased tape.
A tape error has occurred at block nnnnnn.
A second message generally accompanies
this message, giving more detail as to
the nature of the error.
The block length recorded in the file did
not match the length of the block read, or
the block number recorded in the file did
not match the system block count (this
message applies to I format tapes only).
Either the CC or BS parameter was specified
on a COPY command for which neither the
input nor output file was an S or L format
tape or the CC parameter was specified on a
COPYB command without the E or B conversion
parameter specified.
S tape block size exceeds maximum for that
format (1000B) and COPY or character count
for E or B tape COPYB exceeds maximum for
that format (5120 characters).
On F to F tape copy the maximum frame count
for the first file exceeds that of the
second file. On S and L tape copy, block
size is less than noise size. On E and B
tape COPYB, block size is less than the
corresponding S tape noise size.
The tape being read contained a data block
greater in size than that allowed by the
specified format or by your specification.
The product of the fixed length line length
(FL parameter) and the lines per block (LB
parameter) was greater than 3840D.
Indicates an abnormal tape position.
The job executed an address for which a
breakpoint was requested by the system.
CM address in call is not less than the
field length minus the word count; buffer
extends past the job's field length.
ACTION
Inform site analyst.
If many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITIALIZE,
and full PFLOAD on the
device.
Try rebuilding the file if
possible. Inform site
analyst.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Check tape format for
errors.
Examine sequencing of
binary deck and correct
error.
Request that the
operator blank label the
tape using a different
tape drive.
Ensure correct tape is
specified on command.
None.
Ensure accuracy of
format parameter (F) on
command or macro.
Refer to the COPY or
COPYB command
description, correct the
command, and retry.
Reduce the block size or
character counts.
Increase block size so
that it is greater than
the noise size. On F to
F tape copy, increase
output file block size
so it is greater than
the block size of the
input file.
Ensure accuracy of
format parameter (F) on
command or macro.
Correct parameters and
retry.
Inform site analyst if
persistent.
Inform software support.
Verify that operation
does not reference
address beyond end of
buffer or job's field
length.
ROUTINE /*^^v
ITEMIZE
COPYB
1AJ
BLANK
1MT
1MT
1MT
COPYB
C0PY8
COPYB
1MT
FCOPY
1MT
1AJ
1AJ
TCS
B-4 60459680 H
![](asset-259.png)
MESSAGE
BUFFER ARGUMENT ERROR, filename AT address.
BUFFER ARGUMENT ERROR ON filename AT
address.
BUFFER CONTROL WORD ERROR.
BUFFER CONTROL WORD ERROR, filename AT
address.
BUFFER OVERFLOW - ALL FILES LISTED BUT NOT
SORTED.
BUFFER SPACE ERROR (TOV)
pfn BUSY.
CALLING JOB MAY NOT DROP ITSELF.
CANNOT ATTACH/GET FILE-FILE SKIPPED.
CANNOT CHANGE CLASS OF ON-LINE JOB.
CANNOT CHANGE CLASS OF SUBSYSTEM.
CARD READER ERROR.
CATALOG ARGUMENT ERROR.
CATALOG FILE NAME CONFLICT.
CATLIST COMPLETE.
CCL1O0-SEPARATOR FOLLOWING VERB MUST BE
COMMA OR LEFT PARENTHESIS
CCL101-LAST NON-BLANK CHARACTER MUST BE
SEPARATOR
SIGNIFICANCE
For tape operations, this message indicates
one of the following.
- FET less than 7 words long for S/L format
- MLRS greater than 1000 octal for S format
- POSMF issued and no HDR1 label found in
FET or extended label buffer
refer to Volume 4.
A buffer pointer did not conform to the
following constraints.
- FIRST .LE. IN
- FIRST .LE. OUT
- IN AMD OUT .LT. LIMIT .LE. FL
Refer to Volume 4.
Dayfile message indicating that the word
count in the disk linkage is greater than
100B.
Either an attempt was made to write a block
smaller than the noise size on an S, L, or
F format tape, or a control word error
occurred in a write (such as bad byte
count).
Informative output file message indicating
that you have more permanent files than can
fit in the sort buffer. The system listed
all of the files but not in alphabetical
order.
Internal error.
The specified direct access file is
currently attached in an incompatible
mode, or is already being accessed by
4095 users in your specified mode (R,
RA, RU, or RM).
You attempted to drop your current job.
An error occurred when attempting to get or
attach a file. The file may have been
attached or purged by another job.
You extended a CLASS command with a JSN
parameter that attempted to change the
service class of an on-line job. You
cannot use the JSN parameter to change the
service class of an on-line job.
The service class of a job executing at the
subsystem service class cannot be changed.
Job was terminated without exit processing.
The syntax of the CATALOG command is
incorrect.
The same file was named as the file to be
cataloged and as the file onto which the
catalog is written.
Informative message indicating a successful
completion of the CATLIST command.
Separator following verb (directive name)
must be a comma or a left parenthesis.
Last character string of line was not
followed by a separator or a terminator.
ACTION
Examine program to
determine error.
Examine program to
determine error in
buffer pointers.
Take a deadstart dump,
write a PSR, and send
the dump and PSR to CDC
along with any support
materials which will
allow CDC to duplicate
the problem.
Examine program to
determine error.
ROUTINE
Submit a PSR with
information on how
to duplicate the
problem.
Reissue ATTACH until
file becomes available,
or issue ATTACH
specifying WB option.
Do not attempt to drop
your current job.
Check your dayfile for a
specific error message.
If you do not find one,
inform the site analyst.
None.
Resubmit job.
Check the CATALOG
command description and
correct the command.
Change one of the file
names on the CATALOG
command.
None.
Change separator
following verb to a
comma or a left
parenthesis.
To terminate command,
make last nonblank
character a period or
right parenthesis. To
continue command on next
command or line, make
last nonblank character
a valid separator.
1MS
SLL
1MT
RECLAIM
CLASS
CLASS
1AJ
CATALOG
CATLIST
CCL
CCL
60459680 H B - 5 |
![](asset-25a.png)
MESSAGE
CCL102-EQUAL SIGN MUST FOLLOW FIRST SYMBOLIC
NAME
CCL103-STATEMENT INCOMPLETE
SIGNIFICANCE
The first parameter in a SET command is a
symbolic name to be equated. An equal sign
must follow the symbolic name.
A terminator was detected immediately
following the command name.
ACTIo,
Change separator
following the symbolic
name to an equal sign.
Equal sign must be
followed by an
expression.
Check command format
(refer to section 6)
and rewrite command,
using a comma
or left parenthesis
after the command name.
/*^8j\
CCL
CCL104-EXPRESSI0N AND COMMAND TERMINATED
BY terminator
CCL120-ALL COMMANDS SKIPPED - XXXXXX
CCL121-LABEL STRING MUST BEGIN WITH ALPHA
CHARACTER
CCL123-ALPHANUMERIC LABEL STRING REQUIRED
CCL124-PRECEDING ERR MSG. APPLIES TO
FOLLOWING
CCL125-NUMBER OF COMMANDS SUPPRESSED=X
CCL126-C0MMANDS TERMINATOR MUST FOLLOW
LABEL
CCL127-LA8EL STRING EXCEEDS xx CHARACTERS
An expression or a command name was
followed by a command terminator (period or
right parenthesis) instead of a comma. Any
of the following conditions may produce
this error. This message is informative and
is issued in conjunction with message
CCL123.
- The label string parameter was omitted.
- A relational or logical operator was
delimited by a period on left side only.
- An unmatched right parenthesis appeared
in expression. If the separator
following a command name was a left
parenthesis, an unmatched right
parenthesis may appear matched. For
example, IFE(R1+R2)=3, LABEL, is
terminated by right parenthesis.
In process of skipping, end of command
record was reached. Any of the following
conditions may produce this error.
- An IFE, SKIP, or ELSE expression was
false and no ENDIF command terminated
resultant skip.
- A WHILE expression was false and no ENDW
command terminated resultant skip.
- An ENDW command was not preceded by a
WHILE command.
The first character of a label string must
not be numeric.
The commands ELSE, ENDIF, ENDW, IFE, SKIP,
and WHILE require a label string
parameter. This message is issued in
conjunction with the message CCL104.
Dayfile message which precedes CCL124 is an
error message which was caused by the
command printed after CCL124.
A command which the system is printing from
an internal buffer continued over more
lines of input than buffer size. The
system prints the first three lines and
then prints this message to indicate the
number of lines suppressed, x. Remaining
lines of the command follow this message.
Either of the following conditions may
produce this error.
- A label string is last parameter on an
ELSE, ENDIF, ENDW, IF, SKIP, or WHILE
command. It must be followed by a
period or a right parenthesis.
- An expression contained a comma, and the
character string that followed was
assumed to be a label string.
The label string parameter on an ELSE,
ENDIF, ENDW, IFE, SKIP, or WHILE command is
greater than xx characters, xx is the
maximum number of characters defined by
installation.
- Place a comma after
the expression or the
command name and add
a label parameter.
- Delimit operator with
periods on both sides.
- If error was caused
by a misleading left
parenthesis following
the command name, add
a comma immediately
after the command
name. Otherwise,
recheck all
parentheses and match
unmatched right
parenthesis.
- Either add an ENDIF
command with a
matching label string
or correct existing
ENDIF command.
- Either add an ENDW
command with a
matching label string
or correct existing
ENDW command so that
WHILE and ENDW label
strings match.
- Precede ENDW command
with a WHILE command.
Change label string to a
label string of 1 to 7
alphanumeric characters,
beginning with an
alphabetic character.
Refer to message CCL104
for cause and suggested
action.
Refer to error message
which precedes this in
the dayfile for cause
and suggested action.
None.
CCL
Terminate command
with a period or a
right parenthesis.
Either remove comma
or replace it with a
left parenthesis,
depending on nature
of error.
Change label string on
any command it appears
to a label string with
xx or fewer alphanumeric
characters.
CCL
CCL
CCL
CCL
CCL
| B - 6
^^^S
60459680 H
![](asset-25b.png)
0^t\
00&\
MESSAGE
CCL150-EXPRESSI0N CONTAINS INCORRECT OPERATOR
CCL151-EXPRESSION FORMAT ERROR (IN FILE
FUNCTION)
CCL152-POORLY FORMED FUNCTION (NUM, DT, SS)
>
CCL153-INC0RRECT FUNCTION CALL (WITHIN FILE
FUNCTION)
CCL154-INCORRECT EXPONENT
CCL155-OPERATOR OR OPERAND SEQUENCE ERROR
CCL156-STRING TOO LONG -strng
CCL157-UNKNOWN NAME -strng
CCL158-OPERATOR/TERMINATOR MUST FOLLOW
FUNCTION (DT, FILE, NUM)
CCL159-FIRST PARAMETER INCORRECT IN SET
COMMAND
CCL160-NUMERIC OR LITERAL ILLEGAL (IN FILE
FUNCTION)
CCL161-STACK OVERFLOW
CCL162 - PERIOD BRACKETED OPERATORS
PREFERRED
CCL163-SUBSYSTEM REFERENCE ERROR
CCL164 - PAGE PARAMETER ERROR
SIGNIFICANCE
x is not a valid operator in the preceding
command.
The format of the expression is incorrect.
The probable cause is use of commas or
unmatched left parenthesis within an
expression. If error was detected within a
FILE function, IN FILE FUNCTION is included
in message. FILE function must be of form
FILE(filename,exp), where exp is a valid
function or symbolic name.
You made one of the following errors.
- Separator after function name is not a
left parenthesis or function is not
terminated by a right parenthesis.
- Character string evaluated by function
contained special characters but was not
$-delimited.
The NUM function, FILE function, or SS
symbolic name appears within a FILE
function.
A negative exponent in an expression is
incorrect.
You made one of the following errors.
- Sequence of adjacent operators is
incorrect. For example, 3*-4 is not
allowed.
- An operand is adjacent to a left or
right parenthesis. Implied
multiplication is not allowed. For
exampte, 3(R+1) is incorrect.
The listed character string is too long. A
character string may not be longer than 10
characters, excluding $ delimiters for
literals.
The alphanumeric character string strng is
is not a symbolic name recognized by the
system.
A function was properly formed and
positioned within a command, but it was not
followed by an operator, separator, or
terminator.
The first parameter in the SET command was
not one of the following symbolic names:
DSC, EF, EFG, R1, R2, R3, R1G, or SS.
The expression of a FILE function may
contain only symbolic names defined for the
function.
Evaluation of an expression overflowed
either operator or operand stack.
Informative message indicating that a
single character operator was used in an
expression, (i.e., > instead of .GT.).
The system does not recognize the name
associated with the symbolic name SS.
An error was detected when setting the job
default page size symbols PD, PS, PW.
ACTION
If x is part of a
character string,
^-delimit character
s t r in g . I f x i s a n
intended operator, refer
to section 6 for a list
of valid operators.
Check parentheses and
match unmatched left
parenthesis or remove
excess commas from FILE
function.
Correct format of
function.
S-delimit special
characters.
Restructure expression
SO NUM, SS, or FILE is
not within a FILE
function.
Remove minus sign
preceding exponent.
- Use parentheses to
separate adjacent
operators.
- Use an operator to
separate operand and
parenthesis.
Shorten character string
to 10 characters or less.
Replace strng with a
valid symbolic name.
Refer to Section 6 for a
list of valid symbolic
names.
Place an operator,
separator, or terminator
after function.
Replace first parameter
with a valid symbolic
name.
Remove numeric or
literal character
string. Refer to
section 6 for a list of
FILE symbolic names.
Check expression for
errors and correct. If
no errors, either
simplify expression or
break it apart so that
two or more commands
have same effect as one.
Use period bracketed
operators.
Refer to section 6 for a
list of valid names.
Check to see if the
value in the expression
is within the range of
the symbol.
ROUTINE
CCL
CCL
CCL
CCL
CCL
CCL
CCL
CCL
CCL
/^* N
60459680 H B-7
![](asset-25c.png)
MESSAGE
CCL200-PR0CEDURE NESTING LEVEL xx EXCEEDED
CCL201-PROCEDURE NAME MORE THAN 7 CHARACTERS
CCL202 - PROCEDURE FILE IS EXECUTE ONLY
MODE
CCL203-PR0CEDURE FILE NAME NOT SPECIFIED OR
INCORRECT
CCL204-MULTIPLE EQUIVALENCE SPECIFICATIONS
FOR XX
CCL205-FORMAL PARAMETER LIST DOES NOT
INCLUDE -x
CCL206-SYMBOLIC SPECIFICATION INCORRECT xxx
CCL207-PROCEDURE NAMED BEGIN IS INCORRECT
SIGNIFICANCE
The current procedure call forced procedure
nesting to exceed the limit of xx, which is
defined by installation.
A procedure name cannot be greater than 7
characters.
The procedure file was attached prior to
the call in execute-only mode. The
procedure file may have been saved prior to
the call in execute-only mode.
You made one of the following errors:
- File name specified on procedure call
was greater than 40 characters.
- pfile parameter on procedure call was
null. Your site does not have a default
for pfile.
A keyword has been specified more than once
on a procedure call. The last
specification is used.
While is equivalence mode, the system
discovered a keyword x on the procedure
call that was not specified on the
procedure header directive.
A parameter, xxx, on the procedure call is
followed by a plus sign. A plus sign
indicates that the system is to convert the
value to display code and is valid only
when preceded by a symbolic name and
followed by a D, B, or a null field.
(Example: R1+B is a valid value, but 37+R1
is not.)
A procedure must not be named 8EGIN.
ACTION
Reposition procedure
calls so limit xx is not
exceeded.
Rename procedure.
Return file and attach
with default mode.
- Specify a file name
with seven or fewer
characters.
- Specify a file name.
If a preceding
specification is
desired, remove
succeeding
specifications.
Otherwise, no action is
required.
Remove keyword x from
procedure call.
If plus sign is part of
a character string,
S-detimit character
s t r i ng . I f p lu s s i g n
should convert a
symbolic name to display
code, replace xxx with a
valid symbolic name.
Refer to section 6 for a
list of valid symbotic
names.
Select another procedure
name.
ROUTINE
CCL
CCL
CCL
CCL
*<r
•e
CCL
CCL211-SPECIFICATION EXCEEDS xx CHARACTERS
CCL212-SEPARAT0R INCORRECT strng s
CCL213-END OF INFORMATION ON PROMPTED INPUT
CCL230-PROCEDURE FILE NOT FOUND
CCL231-PROCEDURE NOT FOUND
CCL232 - PROCEDURE FILE IS BUSY.
The value on a procedure call or default
value on a procedure header directive is
greater than xx characters, xx is defined
by installation.
s is an incorrect separator and strng is
the character string that precedes s. Any
of the following conditions produces this
error.
- On a procedure call, the separator
preceding a formal keyword or a
positionally specified value is not a
comma.
- Invalid separator is part of a character
string. If a valid separator
immediately precedes incorrect separator
s, the string is null.
- 0DATA or #FILE has been specified on the
procedure call.
The user assigned INPUT to a file that is
at the end of information, and CCL needs to
prompt for a parameter. The INPUT file
probably contains faulty data.
The file named on the procedure call was
not assigned to the job and the
installation chose to inhibit automatic
retrieval of a permanent file with that
name.
The local or permanent file indicated on
the procedure call was found, but the
system could not find the procedure on the
fi l e .
The CCL ATTACH found a file busy status on
the procedure file.
Specify a value with xx
or fewer characters.
Change separator s to
a comma.
$-delimit character
s t r i n g .
Remove #DATA or 0FILE
from procedure call
and specify it on
procedure header
directive.
Correct the file
contents or supply the
CCL parameters
interactively.
Check file name for
errors and correct. If
name is correct,
retrieve file prior to
procedure call.
Check procedure name for
errors and correct. If
name is correct, check
file for procedure.
Clear file busy
condition and resubmit
procedure.
CCL
CCL
CCL
B-8 60459680 H
![](asset-25d.png)
/f!P^»».
MESSAGE
CCL233 - PROC HEADER MUST LEAD LIBRARY
PARTITION/PNAME MUST EQ PARTITION NAME
CCL234-UNABLE TO LOCATE LIBRARY PARTITION
xxx
CCL235-FORMAL PARAMETER GT xx CHARACTERS
CCL236-SPECIAL DEFAULT SPECIFICATION UNKNOWN
CCL237-SEPARATOR FOLLOWING SECOND DEFAULT IS
*/*
CCL238-F0RMAL PARAMETER LIMIT xx EXCEEDED
CCL239-PROCEDURE HEADER MUST BE TERMINATED
BY A PERIOD
CCL240-* MAY NOT APPEAR IN FORMAL PARAMETER
NAME
CCL249 - DATA FILE LFN EXCEEDS 7 CHARACTERS
- filename
CCL250-CONCATENATED STRING EXCEEDS xx
SIGNIFICANCE
The name of the procedure must match a
partition in the library where the
procedure resides. The procedure header
must be the first entry in the partition.
The system could not find procedure xxx,
specified on the call-by-name command, on
the currently defined library set.
The number of characters in a keyword on
the procedure header directive exceeds xx,
as defined by installation.
The number sign , which specifies a
special default option on the procedure
header directive, must be followed by
FILE, PRIMARY, or DATA.
In form keyword=default1/mdefault2/ on the
procedure header directive, the second /is
incorrect.
The number of parameters on the procedure
header directive has exceeded xx, as
defined by installation.
The procedure header directive was not
terminated by a period, and no commands
were found after the header directive.
A keyword containing an asterisk was
found on the procedure leader.
The file name specified on a .DATA
directive is longer than seven characters.
Use of a right arrow (or the underline
character in ASCII) produced a linked
string of more than xx characters, or a
string of xx characters with a following
separator, xx is equal to IP.SCL.
(Default is 150).
ACTION ROUTINE
Rebuild library with the CCL
procedure header as the
first entry in the named
partition.
Che ck p rocedur e na me f or C CL
errors and correct. If
name is correct, check
library for procedure.
Define a keyword with xx CCL
or fewer characters.
If number sign is CCL
part of a character
string, enclose the
character string with
dollar signs. If a
special default option
is desired, follow the
number sign with either
DATA, FILE, or PRIMARY.
I f / i s p a r t o f C C L
default2, Enclose the
character string with
d o ll ar s i gn s . I f n o t,
either remove it or
replace it with a
comma or period.
Remove parameters from CCL
procedure header
directive until xx or
fewer parameters remain.
Terminate procedure CCL
header with a period and
add at least one command
to procedure.
Redefine the keyword CCL
without any asterisks.
Specify a shorter file CCL
name.
Reduce number of linked CCL
characters.
CCL251-DATA DIRECTIVE SPECIFIED CCL
FILE - filename
CCL252-PR0CEDURE CONTAINS NO COMMANDS
CCL253 - PROC BODY STRING EXPANDS .GT. xx.
CCL261-ENDW WITH MATCHING LABEL FOUND
The file name that you specified on a .DATA
directive is a working file.
A procedure should contain at least one
command.
After parameter substitution, a single
contiguous string in the procedure body is
longer than the maximum line length, xx is
equal to IP.SCL. (Default is 150).
The system encountered an ENDW command in
the job command record before finding a
WHILE command with a matching label
string. A search is initiated for a
corresponding WHILE command. If a WHILE
command with a matching label string is
found and the WHILE expression is true,
normal processing continues with the
command following the WHILE command. If
the WHILE expression is false or if no
WHILE command with a matching label string
is found, the system skips all remaining
commands in command record.
Select another file name.
None.
Rewrite the string using
fewer characters or
fewer concatenated
s t r i n g s .
Check for a WHILE
command and if not
present, add. If
present, see if WHILE
and ENDW label string
match and are correct.
If they match, place
WHILE command before
ENDW command.
CCL
CCL
CCL
CCL262-C0NTINUING SEARCH, PRINT SKIPPED
COMMANDS
CCL263 EXTERNAL ABORT DURING BEGIN.
To assist in isolation of WHILE command
errors such as CCL261, all skipped commands
will be printed in the job dayfile until
the WHILE search is complete.
An external abort during BEGIN processing
occurred. Check the job dayfile to find
where error occurred.
Correct BEGIN command or
PROC directive as
indicated by dayfile.
60459680 H B-9
![](asset-25e.png)
MESSAGE
CCL263 EXTERNAL ABORT DURING ENDW.
CCL270-ERR IN CCL WORK FILES, REVERT TO JOB
FILE
CCL271-REVERT NOT ALLOWED WITHIN JOB FILE
CCL272-INC0RRECT REVERT PARAMETER - param
CCL273 - EXPECTING . OR ) AFTER REVERT,EX
CCL300-N0N-NUMERIC CHARACTER WITHIN NUMERIC
TERM
CCL302-8/9 DIGIT CONFLICTS WITH POST RADIX
OF B
CCL303-LITERAL NOT TERMINATED
CCL304-STRCCL - SCATTER BUFFER HEADER
INCORRECT
CCL320 - CORRECT
CCL320 - ENTER
CCL321 - EXPECTING ( AFTER PARAMETER* ON
HEADER
CCL322 - END HEADER WITH . OR USE ,/ \
BEFORE PARAM
CCL323 - EXCESS PATTERNS/VALUES - PROC
HEADER
CCL324 - CHECKLIST PATTERN MUST BE *N *K *F
*A *S
CCL326 - I OR M MUST FOLLOW PNAME* ON
HEADER.
CCL327 - EXPECTING VALUE AFTER PATTERN = ON
HEADER
CCL328 - HEADER PARAMETER DESCRIPTION TOO
LARGE.
CCL329 - MISC. AFTER HEADER PARAMETER
DESCRIPTION
SIGNIFICANCE
An external abort occurred during the
search for the WHILE command. The abort is
due to a DROP or RERUN command an exceeded
time limit, mass storage limit, or extended
memory limit.
An error was encountered in a file used by
the system because of user manipulation of
procedures or data. The system attempts to
return to your assigned job file. If
unsuccessful, the job terminates
immediately. If successful, control goes
to the EXIT command.
A REVERT command cannot appear in commands
of the job file.
The parameter param was used on the REVERT
command. The REVERT command allows only
ABORT, EX, or NOLIST as parameters.
REVERT,EX. will not accept any other
parameters. The command must be terminated
and a valid command must immediately follow
the terminator.
An element of an expression which begins
with a numeric character cannot contain a
nonnumeric character, except B or D as a
post radix.
An 8 or 9 is incorrect in an octal number.
A literal which begins with a dollar sign
was not terminated by a second dollar sign.
System error.
This message precedes a system prompt for a
parameter when a batch mode procedure call
contains a parameter entry in error.
In a parameter-prompting procedure, the
equal sign after a parameter name or
description must be followed by a left
parenthesis to indicate the start of a
checklist.
A parameter definition or the *I after the
procedure name must be followed by a
period, comma, slant, or reverse slant.
The sum of checklist values and patterns is
too large (exceeded the internal table size
of CCL, which is an installation option).
The character following the asterisk in a
checklist pattern was not N, K, F, A, or S.
The procedure name must be followed by *I
for interactive procedures or by *M for
menu procedures.
The syntax immediately following the equal
sign in the checklist is incorrect. The
system expects an alphanumeric value, a
literal, or a special name as a value.
A procedure header parameter description
exceeds 40 6/12-bit display code or 80
6-bit display code characters.
The only characters allowed to follow the
terminating quotation mark of a parameter
description are equal sign, period, right
parenthesis, slant, reverse slant, or comma.
ACTION ROUTINE
Check validation CCL
li m i ts. Mo d i f y j o b t o
fit within limits or ask
site to increase the
l i m i t s .
Rewrite the job and/or CCL
procedures to prevent
manipulation of the
system work files.
Remove REVERT command. CCL
Replace parameter param CCL
with a valid
specification.
Correct command and CCL
resubmit.
Remove any nonnumeric CCL
characters other than a
post radix B or D.
R e m o v e a ny 8 's o r 9 's i f C CL
the number is octal or
remove post radix B if
number is decimal.
Place a second dollar CCL
sign at end of character
string denoted as a
literal.
Inform site analyst. CCL
None. CCL
>^?N
Correct procedure header
and resubmit.
Correct procedure header CCL
and resubmit.
Reduce the number of CCL
checklist options or
have CCL reassembled and
installed with an
increased value for
installation parameter
IP.NPV.
Correct procedure header CCL
and resubmit.
Insert *I or *M after CCL
the procedure name.
Correct header and CCL
resubmit.
Reduce the size of the CCL
de s cri p t ion st r i ng.
Correct procedure header CCL
and resubmit.
| B - 1 0 60459680 H
![](asset-25f.png)
/!^V MESSAGE
CCL330 - EXPECTED , = OR ) AFTER CHECKLIST
PATTERN
CCL331 - EXPECTED , OR ) AFTER PATTERN VALUE
CCL332 - WRITE SET AS *SN(SET) ON PROC
HEADER
CCL333 - DUPLICATE *K *N - PROC HEADER
CCL334 - MISSING QUOTE - PROMPT/TITLE/
DESCRIPTION
CCL335 - DESCRIPTION MISSING 3 BRACKET.
CCL336 - PATTERN OR VALUE ON PROC HEADER
-GT. 40
CCL352 - HELP PARAMETER NAME NOT FOUND
CCL353 - ONLY COMMA ALLOWED AFTER .HELP
CCL354 - .HELP STATEMENT INCORRECTLY
WRITTEN
CCL355 - NO .ENDHELP FOR .HELP
CCL357 - DUPLICATE HELP DIRECTIVES IN PROC
BODY
SIGNIFICANCE
The pattern part of a checklist item can
only be followed by another pattern
preceded by a comma, a replacement value
preceded by an equal sign, or a right
parenthesis to indicate the end of the
checklist.
The replacement value part of a checklist
item can only be followed by another
pattern preceded by a comma or a right
parenthesis to indicate the end of a
checklist.
A set pattern in a checklist must be
written as *S followed by an optional
unsigned integer in the range 1-40 followed
by up to 40 characters enclosed in
parentheses.
A single checklist may not contain more
than one *K or more than one *N pattern.
A prompt, title, or description string on
the procedure header must begin and end
with a quote and cannot extend onto another
line.
The terminating right bracket (1) on a
description string was not found.
A single checklist item may contain literal
patterns and replacement values (values
which stand for themselves). These values
may not exceed 40 characters in length.
Literals may not exceed 40 characters after
evaluation.
If a commas follows the .HELP directive,
the system expects to find a parameter
name or the parameter NOLIST.
The system found something other than comma
after .KELP directive.
The .HELP directive can have one of four
formats:
.HELP.
.HELP,keyword.
.HELP,keyword,N0LIST.
•HELP,,NOLIST.
The system found an end of record before it
encountered a .ENDHELP directive.
Either more than one .HELP directive with
no parameter name or more than one .HELP
directive with the same parameter name was
found.
ACTION
Correct procedure header
and resubmit.
Correct procedure header
and resubmit.
Correct procedure header
and resubmit.
Correct procedure header
and resubmit.
Insert quotes.
Start the string with a
left bracket (O and
terminate it with a
right bracket (1).
Correct procedure header
and resubmit.
Correct directive and
resubmit.
Correct directive and
resubmit.
Correct directive
resubmit.
Add an .ENDHELP
directive and resubmit.
Delete duplicate .HELP
directives and retry.
ROUTINE
CCL
CCL
CCL
CCL
CCL
CCL
CCL
CCL
CCL
CCL
CCL
vtfmfB&V
CCL373 - EXPECTING ( OR , AFTER .IF .ELSE
.ENDIF.
CCL374 - EXPECTING PERIOD AFTER .EX
CCL375 - COMMAND IS NULL ON .EX DIRECTIVE.
CCL376 - .IF DIRECTIVE HAS INCOMPLETE
EXPRESSION
CCL377 - EXPECTING , ) OR . AFTER .IF
EXPRESSION
CCL378 - , OR C MUST FOLLOW .DIRECTIVE NAME
CCL379 - NO .ENDIF FOR .IF/.ELSE LABEL
aaaaaa - LAST LINES SKIPPED
A .IF, .ELSE, or .ENDIF directive in the
procedure body must have a left parenthesis
or a comma immediately following the
directive name.
A period must follow the .EX directive name
in the procedure body.
You have not specified a command on the .EX
directive.
A .IF directive in the procedure body is
incomplete.
A comma, period, or right parenthesis must
follow the expression on a .IF directive in
the procedure body.
A procedure directive is missing the comma
or left parenthesis separator.
A .ENDIF directive with a label matching
the .IF/.ELSE directive label aaaaaa was
not found.
Insert a left
parenthesis or a comma.
Insert a period after
the directive name.
Specify a command on the
directive.
Complete the expression
and add a label or
command to the directive.
Insert a comma, period,
or right parenthesis
after the expression.
Place separator after
the directive name.
Add a .ENDIF directive
or correct label on
existing .ENDIF.
CCL
CCL
CCL
CCL
60459680 H B-11
![](asset-260.png)
MESSAGE SIGNIFICANCE ACTION
CCL380 - EXPECTING TITLE OR , AFTER *M ON
HEADER
CCL381 - KEYWORD MISSING ON MENU HEADER
CCL382 - PROMPT ON PROC HEADER IS TOO LARGE
A title, if there is one, or a comma was
not found immediately following the *M on a
menu procedure.
You must specify a formal parameter keyword
after the procedure name in the procedure
header of a menu-generating procedure.
A prompt/description string on your
procedure header is greater than 40
6/12-bit display code or 80 6-bit display
code characters.
Place a title surrounded
by quotes after the *M
or else place a comma
after *M.
Insert a parameter
keyword.
Reduce the size of the
prompt string.
CCL
CCL
CCL383 - MISSING SELECTION ON MENU HEADER
CCL384 - TITLE ON PROC HEADER IS TOO LARGE
CCL385 - EXPECTING = AFTER KEYWORD ON
HEADER
CCL386 - EXPECTING COMMA AFTER HEADER
TITLE
CCL387 - BEGINNING OF HEADER CHECKLIST NOT
FOUND
Your procedure header checklist has a null
specification.
A title string on a menu procedure header
is greater than 40 6/12-bit display code or
80 6-bit display code characters.
An equal sign must follow the parameter
keyword on your procedure header.
A character other than a comma was found
following the title on the procedure header.
Either your procedure header does not
contain a checklist or the checklist begins
with a special character other than a left
parenthesis.
Specify a checklist with
integer selections.
Reduce the size of the
t i t l e s t r i n g .
Insert an equal sign
after the parameter
keyword.
Place a comma after the
title.
Specify a checklist
beginning with a left
parenthesis.
CCL
CCL
CCL
CCL
CCL
CCL388 - EXPECTING INTEGER HEADER SELECTION
OPTION
CCL390 - EXPECTING , OR ) AFTER CHECKLIST
SELECTION
CCL392 - EXPECTING , OR ) AFTER HEADER
PROMPT
CCL393 - EXPECTING PERIOD AFTER HEADER
CHECKLIST
You specified a non integer selection in
your procedure header checklist. A
selection must be a 1- to 10-digit integer.
You specified a special character other
than comma or right parenthesis after a
menu selection on your procedure header.
You specified a special character other
than comma or right parenthesis after a
prompt/description string on your procedure
header.
You specified either no period or a special
character other than a period following a
procedure header checklist.
Make all menu selections
integers.
Replace the special
character with a comma
or terminate the
checklist with a right
parenthesis.
Replace the special
character with a comma
or terminate the
checklist with a right
parenthesis.
Insert a period after
the checklist.
CCL
CCL
CCL
CCL
CCL394 - TOO MANY HEADER SELECTIONS
SPECIFIED
You specified more than 50 menu selections
in your procedure header checklist.
Reduce the number of
selections. CCL
CCL395 - HEADER SELECTION EXCEEDS 10
CHARACTERS
CCL421 - EXPECTING , OR ( AFTER .DIRECTIVE
CCL422 - A .DIRECTIVE WAS FOUND IN THE PROC
BODY
CCL440 - EXPECTING INHIBIT CHARACTER - .IC
DIRECTIVE
In your procedure header, a menu selection
number contains more than 10 digits.
A character other than , or ( was specified
between the directive name and its
parameters.
One of the following:
- A line that is not a directive begins
with a period or a , or a directive is
misplaced.
- A .HELP, .PROMPT, .ENTER, .PAGE, .CORRECT,
•F1, .F2, .F3, .F4, .FS, or .F6 directive
was found after .ENDHELP in the procedure
body.
- An .EOR or .EOF directive is outside
of the data section of the procedure
body.
The .K directive is missing a special
character which would replace the current
inhibition character.
Use 10 or fewer digits
for your selection.
Place a , or ( after the
directive name.
Correct the error
and resubmit.
Specify a special
character as a
replacement.
CCL
CCL
CCL
CCL441 - EXPECTING CONCATENATION CHARACTER
- .CC
CCL442 - EXPECTING TERMINATOR ON DIRECTIVE
The .CC directive is missing a special
character which would replace the current
concatenation character.
A CCL directive was not terminated by a
period or right parenthesis.
Specify a special
character as a
replacement.
Terminate the directive
with a period or a right
parenthesis.
CCL
| B - 1 2 60459680 H
![](asset-261.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
r^ CCL443 - EXPECTING ON/OFF
.EXPAND DIRECTIVE
CCL480- USE NUMERIC MIN..MAX VALUES IN
RANGE
CCL481- USE CONSECUTIVE PERIODS MIN..MAX
IN RANGE
CCL482- MINIMUM EXCEEDS MAXIMUM IN RANGE
CCL483- *F RANGE MUST BE .GE. 1 AND .LE. 7
CCL484- *A RANGE MUST BE .GE. 1 AND .LE. 40
CCL485- USE *SN(SET) OR *SN/M FOR SET
ATTRIBUTES
CCL486- USE M=A,D,B,AD,AB for *SN/M TYPE
SET
CCL487- RANGE MAXIMUM MUST BE .GT. ZERO
CFO FROM JOB jsn
CFO FROM OPERATOR
CHANNEL MALFUNCTION, filename AT address.
* CHARGE(charge,project)
CHARGE ABORTED.
CHARGE CARD REQUIRED.
CHARGE COMMAND REQUIRED.
CHARGE FILE BUSY.
CHARGE INCORRECT AT THIS HOUR.
CHARGE NOT VALID.
CHARGE NUMBER EXPIRED.
CHARGE REQUIRED.
The only arguments allowed for .EXPAND are
ON and OFF. The argument must be preceded
by a comma or opening parenthesis and
followed by a period or closing
parenthesis. The argument may be omitted.
A non-numeric minimum or maxium range was
found within a checklist on the procedure
header.
A range was specified on the procedure
header without 2 consecutive periods
separating the minimum and maximum.
A checklist range on the procedure header
has a minimum larger than the maximum.
The *F checklist pattern specifies a file
name, which cannot exceed 7 characters.
The range for the *A checklist pattern was
zero or greater than 40.
The *S checklist pattern has two forms.
The first is *Sn(SET) and the second is
*Sn/M. The *S specification on the
procedure header does not conform to either.
When the *Sn/M checklist pattern is used,
only A, D, B, or AB may be substituted for
M. For example: *S2..10/AD
A checklist range on the procedure header
has a maximum of zero.
The CFO command was issued to the job by
the job jsn.
The CFO command was issued to the job by
the console operator.
A hardware malfunction occurred.
Indicates that you entered the default
format of the CHARGE command (CHARGE,*).
charge Your default charge number.
project Your default project number.
Dayfile message indicating that a central
site operator action caused the CHARGE
operation to abnormally terminate.
A CHARGE command is required before the
current USER command may be processed.
Dayfile message indicating that a CHARGE
command must be executed before the
requested command can be executed.
Dayfile message indicating that the file
which the system uses to validate charge
numbers and project numbers is busy.
Dayfile message indicating that the
specified project number cannot be used at
this time of day.
Dayfile and output file message indicating
one of the following:
- The charge or project number does not
exist.
- The project number is not available to a
user with this user name.
- The charge and project exist but are
inactive.
Dayfile and output file message indicating
the charge number expiration date has
occurred.
Charge number and project number are
required to complete login sequence.
Correct the argument or
syntax and resubmit.
Use a numeric minimum or
maximum range.
Use consecutive periods
to specify a range.
Change either the
minimum or maximum and
resubmit the procedure.
Correct range maximum to
7 or less.
Correct *A checklist
range.
Correct the *S checklist
pa t te r n.
Correct the *S checklist
pa t te r n.
Change the maximum to a
value greater than zero.
None.
Inform site analyst.
None
Reenter CHARGE command.
Enter a CHARGE command
and retry.
Enter a valid CHARGE
command and then reenter
the original command.
Reenter CHARGE command.
Retry during the time
the project number is
valid.
Check correctness of
charge and project
number. Use another
charge and project
number.
CCL
CCL
CCL
CCL
CCL
CCL
1RI
1RI
1MT
CHARGE
CHARGE
CHARGE
1AJ
CHARGE
CHARGE
CHARGE
Enter CHARGE command
with appropriate charge
and project numbers.
/$ps\
60459680 H B-13
![](asset-262.png)
MESSAGE
CHECK DAYFILE FOR ERRORS.
SIGNIFICANCE
Informative message indicating that you
should check the dayfile for errors.
ACTION ROUTINE
Examine error messages PFATC
in dayfile. PFCAT
PFCOPY
PFDUMP
PFLOAD
COPYB
CHECKPOINT nnnn COMPLETE.
CHECKPOINT nnnn COMPLETED TO filename.
CHECKPOINT FILE ACCESS LEVEL ERROR.
CHECKPOINT FILE ERROR.
CHECKPOINT FILE ERROR.
CHECKPOINT NOT FOUND.
CHKPT UNABLE TO READ TAPE.
CKP REQUEST.
CLASS ARGUMENT ERROR.
CLASS COMPLETE.
CM BLOCK OUT OF RANGE.
CM OR EC REQUEST EXCEEDS MAXIMUM.
CM OUT OF RANGE.
CM PARITY ERROR.
CM RANGE EXIT MODE NOT DESELECTABLE.
CMC PARITY ERROR.
Indicates that checkpoint nnnn has
completed. Issued if only one checkpoint
file is pres en t.
Indicates that checkpoint nnnn has been
completed to file filename. Issued if
alternate CB checkpoint files are used.
None. CHKPT
In a secure system,
access level is not
access level limit,
the checkpoint file
contain alt local fi
of the checkpoint fi
this level since thi
magnetic tape files
permanent file, and
file types used for
the checkpoint file
the same as the job
This is to insure that
is secure enough to
Les. The access level
le is not changed to
s is not possible for
or direct access
these are the usual
checkpoint files.
For RESTART, this message indicates that
the structure of the file declared to be
the checkpoint file does not correspond to
that of a checkpoint file.
During a checkpoint operation, more than
two checkpoint files were present or two
checkpoint files of type "CK" were present.
The specified checkpoint (nn parameter on
RESTART command) could not be found on the
fi l e .
Indicates a tape file had an unrecovered
parity error when CHKPT tried to write it
to the checkpoint file.
Updating of resource file returned error
status other than end-of-device.
A checkpoint has been initiated.
One of your arguments is not correct.
An informative message indicating that your
attempt to change a job's service class was
successful.
Data transfer from extended memory
specified a CM address outside the job
field length.
Field length of more than 77000 octal (CM)
or more than 7777 octal (EM) was specified
in RFL command.
The program referenced an address outside
the job CM field length.
Double data parity error (two data bits
failed) between central memory control
(CMC) and CM as detected by the
single-error correction double-error
detection (SECDED) network, or a single
parity error when operating in default mode
(SECDED network disabled).
You attempted to deselect system checking
for CM out of range errors. This cannot be
done on a model 176.
The CPU sent the central memory control
(CMC) data or an address having incorrect
parity.
Insure that the access
level of the checkpoint
file is the same as the
job access level upper
limit.
Correct specification of
checkpoint file.
Correct specification of
checkpoint file.
Verify that checkpoint
i s o n fi le .
Rerun the job. If the
problem recurs, inform
a site analyst, write
a PSR and include
support material so that
CDC can duplicate the
problem.
None.
Check command
description, then retry.
Analyze the job output
and dumps to determine
the cause.
Retry with lower
value(s).
Analyze job output and
dumps to determine the
cause.
Inform customer engineer
Determine if the program
can run with CM range
error checking. If it
cannot, the program must
be changed.
Inform customer engineer.
CHKPT
RESTART
CHKPT
RESEX
CHKPT
CLASS
CLASS
1AJ
CONTROL
1AJ
1AJ
CPM
1AJ
<^SE§jjy
| B - 1 4 60459680 H
![](asset-263.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
COMMAND ERROR.
COMMAND LIMIT.
COMMAND NOT ALLOWED IN PROJECT PROGRAM.
COMMAND NOT PROCESSED DUE TO OVERLAP
COMMAND NOT UNIQUE.
COMMAND TOO LONG.
COMMENT FROM JOB jsn
COMMENT FROM OPERATOR
CONFLICTING PARAMETERS.
CONFLICTING RESOURCE TYPES.
CONNECT REJECT, filename AT address.
CONNECTION REJECTED.
CONTROL ARGUMENT ERROR
CONTROLLED BACKSPACE ERROR, filename AT
address.
COPY COMPLETE.
COPY FL ABOVE USER LIMIT.
COPY INDETERMINATE.
COPYING - type/name
COPYL COMPLETE.
COPYL DID NOT FIND type/name
CPest, CHcc count INCOMPLETE TRANSFER.
CPest, CHcc CONTROLLER HUNG BUSY.
CPest, CHcc Fcode FUNCTION TIMEOUT.
CPest, CHch Fcode REJ Pdriver,Cconver,Eequip.
CPest, CHCC RESERVED.
CPest, CHcc TURNED OFF.
CPest, COMPARE ERROR.
CPest, FEED FAILURE.
CPM - ACCESS LEVEL NOT VALID FOR JOB.
An incorrect parameter was specified on the
command.
The system has processed the maximum number
of commands allowed in one of your jobs
(refer to the LIMITS command).
A CHARGE command was placed in a project
prolog or epilog.
You have specified that the selected edit
command should not be processed due to
overlapping Line numbers.
The characters entered do not uniquely
specify a command.
You entered a command string longer
t h a n 8 0 c h ar a c t e r s .
A COMMENT command was issued to the job by
the job jsn.
A COMMENT command was issued to the job by
the console operator.
You queued a file and specified an input
disposition more than once.
PE, HD, and GE resources cannot be
specified concurrently with an NT resource
in t h e sa m e job .
The system was unable to connect a
peripheral device.
The requested application is already
servicing the maximum number of terminals.
Internal error.
Controlled backspace operation failed
d u r i n g w r i t e e r r o r r e c o v e r y . P o s i t i o n o f
tape is uncertain.
Copy termination condition was satisfied
befor e E O I was e n count e r ed.
Field length for L or F tape copy exceeds
you r c urr e nt m a x imu m .
Yo u r c o p y i n g o p e r a t i o n w i t h S , L , o r F t a p e
is unpredictable. Only the COPY command
supports these formats.
The record with the type and name on the
old file was copied to the new file.
All records on the old file have been
processed.
The record with type and name on the
replacement file was not found on the old
file. Since the A option was not selected,
the record is ignored.
Card punch messages. Refer to EQest...
Correct command and
r e t r y .
I f y o u m u s t r e r u n t h e
job, restructure it such
that it requires fewer
commands.
Remove the CHARGE
command from the project
prolog or epilog.
None.
Ensure accuracy of
e n t r y . E n t e r a
sufficient number of
characters to specify a
unique command.
Reenter using a shorter
version of the command.
None.
EDIT
LISTLB
1AJ
None.
Reenter with correct
parameters.
Correct the RESOURC
command.
I n f o r m s i t e a n a l y s t .
Request a different
application or log off
and try later.
Submit a PSR with
information on how
to duplicate the
problem.
Inform customer engineer.
None.
Use smaller block size
on L and F tapes or
increase maximum FL.
Inform customer engineer.
CPM
IAF
IAFEX
1RI
1RI
1MT
NETVAL
1MT
COPYB
COPYC
Retry
COPY i copy using
command.
the COPYB
COPYB
None. COPYL
COPYLM
None. COPYL
COPYLM
None. COPYL
COPYLM
QAP
110
You attempted to change the job access
level to a value not valid for the job.
Retry with a valid level. CPM
60459680 H B-15
![](asset-264.png)
MESSAGE
CPM - ARGUMENT ERROR.
CPM - INCORRECT PACK NAME.
CPM - INCORRECT REQUEST.
CPM - INCORRECT *SHELL* FILE.
CPM - INVALID PAGE VALUE.
CPM - LIBRARY NOT FOUND = library.
CPM - MASS STORAGE ERROR.
CPM - MISSING *SHELL* LOAD OPTION.
CPM - SYSTEM ERROR.
CPM - USER ACCESS NOT VALID.
CPU ABORT.
CPU ERROR EXIT.
CPU ERROR EXIT AT address.
CRest, CHcc Acount INCOMPLETE TRANSFER.
CRest, CHcc CONTROLLER HUNG BUSY.
CRest, CHcc Fcode FUNCTION TIMEOUT.
CRest, CHcc Fcode REJ Pdriver,Cconvert,Eequip.
CRest, CHcc TURNED OFF.
CRest, CHcc RESERVED.
CRC ERROR.
CT, CN, OR OV KEYWORD NOT PRESENT.
SIGNIFICANCE
An incorrect argument was specified.
An incorrect pack name has been specified.
A job was incorrect CPM function code,
subfunction code was specified, or extended
reprieve is set (for EREXIT).
You entered a SHELL command with one of the
following errors:
The specified SHELL program was not
found on mass storage.
You specified the local load option
for a file that was not found in the
local file name table (FNT).
There was an error in your job page size
information.
The system could not find the
specified library.
One of the following:
A nonrecoverable error occurred when
your job attempted to access a mass
storage device.
Your job was aborted after being
rolled out due to a recoverable mass
storage device error.
You attempted to set a shell control
without specifying a load option.
For function 42 (Special Charge) or 106
(Set Job Characteristics), CPM was unable
to read the input file.
1. You tried to perform a CPM operation for
which you are not authorized.
2. A CPU program issued a DSDOUT or a
DSDINP macro request when it did not
have access to the L display CMR buffers.
RECLAIM system error.
Self-explanatory.
The errors listed after this message
occurred at address, causing job
termination.
ACTION
Retry the command using
valid arguments.
Ensure that a valid pack
name is used.
Specify auto recall on
monitor request call to
CPM.
Correct the SHELL
command or create the
proper SHELL program
file. SHELL file.
Retry with correct
values.
Ensure that the library
name is correct on the
command or macro.
Inform site analyst.
ROUTINE
CPM
Specify a load option in
the shell command or
macro and try again.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Ensure that the L
display utility was
initiated at the system
console with the
appropriate commands.
Check previous messages
and the dayfile for the
reason for the abort.
If you find no other
messages, inform the
site analyst.
None.
Refer to the
descriptions of the
error messages issued
with this message.
Card reader messages. Refer to EQest, CHcc Inform customer engineer.
The 405 card reader is reserved and cannot
be connected on channel cc.
est EST ordinal of card reader
cc Channel number.
An error was detected in cyclic redundancy
character. The dayfile message STATUS
ERROR, filename AT address precedes this
message and specifies the file (filename)
and the address.
The COMPACT directive has been specified
on the RECLAIM command; COMPACT requires
either the CT, CN, or OV option, but
none of these was specified.
Inform customer engineer.
Retry or inform site
analyst.
Retry with the CT, CN,
or OV option.
CPM
CPM
0^^\
CPM
CPM
CPM
CPM
RECLAIM
RECLAIM
1AJ
110
QAP
110
1MT
RECLAIM
-^^*v
B-16 60459680 H
![](asset-265.png)
MESSAGE
CUMULATIVE LIMIT EXCEEDED.
jsH*n
CUMULATIVE SRU LIMIT EXCEEDED.
DATA BASE ERROR.
DATA/PERMIT ERRORS.
DATA TRANSFER ERROR.
DATABASE CORRUPTED.
DATABASE NOT FOUND-DEFINING NEW ONE.
DAYFILE - INPUT FILE CANNOT BE EXECUTE ONLY.
DAYFILE - INTERACTIVE INPUT FILE NOT ALLOWED.
DAYFILE - JOB FIELD DISALLOWED ON USER
DAYFILE.
DAYFILE - JOB TERMINATION OPTION.
DAYFILE - LOCAL DAYFILE PROCESSED.
DAYFILE - PAGE SIZE FORMAT.
DAYFILE - PRINT DENSITY.
DAYFILE - PRINT DENSITY FORMAT.
DC REQUIRED IF JSN/UJN NOT SPECIFIED.
-DEBUG-GARBAGE IN ZZZZZDS FILE.
DEBUG-ILLEGAL PARAMETER-p.
DEBUG-ONLY ONE PARAMETER ALLOWED.
-DEBUG-ZZZZZDS FILE NOT FOUND.
SIGNIFICANCE
Dayfile and output file message indicating
that one of the installation-defined
resource usage accumulators for this
project exceeded the maximum allowed. The
system does not update these accumulators
in PROFILa. Each installation must provide
this capability if desired.
Dayfile and output file message indicating
that accumulated SRUs have exceeded the
maximum allowed.
The system has detected an error in its
validation file.
When the specified file was loaded from
tape, errors were encountered in both data
and permit information.
ACTION ROUTINE
CHARGE
An error occurred in a read operation
during a file transfer.
RECLAIM encountered a problem with the
database; usually indicates that the
database is empty or has been overwritten
with something other than a database.
RECLAIM did not find the specified database
in your catalog and is attempting to define
a new one.
You specified an execute-only file in the
I=infile parameter of the DAYFILE command.
The input file cannot be execute-only,
infile The input file to be
processed by DAYFILE.
Dayfile data cannot be entered directly
from the keyboard.
Options specified are not allowed for your
job's dayfile processing.
An incorrect value was specified for the
*JT* option.
DAYFILE has successfully completed
processing a local file as input.
The page size option is nonnumeric.
The print density option is not 3,4,6, or 8.
The print density option is nonnumeric.
Print density must be 3,4,6, or 8.
If the JSN or the UJN parameters are
omitted, the DC parameter must be entered.
File ZZZZZDS contains information other
than the suspended job of the current
session. Retrieval of debug information
from session is impossible.
You specified an incorrect parameter on
DEBUG command. The three parameters
allowed are ON, OFF, or RESUME.
You entered more than one parameter on the
DEBUG command.
You did not suspend the debug session
during the current terminal session. Refer
to the SUSPEND command (CYBER Interactive
Debug Version 1 Reference Manual).
None.
Contact installation
personnel.
Enter CHANGE command or
macro with CE parameter
to allow access to the
file. Make the file
local and check if data
is accurate. Enter a
CATLIST command to see
if the permits are
accurate.
Inform site analyst. If
many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITIALIZE,
and full PFLOAD on the
device.
Check to ensure that
your database is in
correct RECLAIM format
and that it is not empty.
None.
Specify an input file
that is not execute-only.
Specify dayfile input
from other than the
terminal (TT device).
Retry with a correct
0P=op parameter.
Correct option and retry.
None.
Retry with a valid
option.
Retry with a valid
option.
Retry with a valid
option.
Add the DC parameter and
retry.
Return file ZZZZZDS and
restart debug session.
Reenter DEBUG command
with correct parameter.
Reenter DEBUG command
with correct parameter.
Restart debug session.
CHARGE
CHARGE
PFM
RECLAIM
RECLAIM
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DAYFILE
DROP
DEBUG
DEBUG
60459680 H
![](asset-266.png)
MESSAGE
DEFAULT CHARGE NOT VALID.
DEFAULT FAMILY USED.
DEFERRED BATCH VALIDATION EXCEEDED
filename.
*DEL*
DEMAND EXCEEDED.
DEMAND FILE ERROR.
DEMAND VALIDATION ERROR.
DETACH LIMIT EXCEEDED.
DEVICE ERROR ON FILE filename AT address.
DEVICE INACCESSIBLE - DETACH FAILED.
DEVICE INACCESSIBLE - LOGIN FAILED.
DEVICE UNAVAILABLE.
DIRECT ACCESS DEVICE ERROR.
DIRECT ACCESS FILE ERROR.
DIRECTIVE ERRORS.
SIGNIFICANCE
Dayfile and output file message indicating
one of the following:
- The default charge or project number
associated with the current user name
does not exist.
- The default charge or project number
associated with the current user name is
not available to that user name.
- The default charge and project
associated with the current user name
exist but are inactive.
You entered a FAMILY command with no
parameter. The default family was used.
You have too many queued files.
The system has deleted the last line of
input. This occurred when the terminal
operator entered the cancel character (CN)
followed by the end of line/end of block
terminator.
You attempted to assign more units than
were scheduled on the RESOURC command.
Resource execution error was encountered.
This error occurred because the demand file
(RSXDid) entry does not match the job
identification.
The specified number of units exceeds your
validation limits.
You have too many detached jobs or are not
authorized to detach jobs.
An irrecoverable error occurred on the mass
storage device containing the file filename.
Your job could not be detached due to a
mass storage device error.
Login failed because of mass storage device
error.
One of the following:
- A packname was specified for a pack that
is not currently mounted.
- For a DIS job, no SUI or USER command
has been entered.
- No permanent file device could be found
for your user name.
- On a secure system, no permanent file
device with the proper access level
could be found for your user name.
One of the following occurred.
- An incorrect device type was specified.
- The device on which the local file
resides may not contain direct access
files.
The system sector for the file contains
incorrect data or cannot be read.
A LIBEDIT directive has incorrect syntax.
ACTION
Use another charge and
project number.
ROUTINE
CHARGE
None.
Enter the LIMITS command
to ascertain the number
of queued files you can
have.
None.
Increase appropriate
parameter value on
RESOURC command.
Rerun the job. If the
problem recurs, inform
a site analyst, write
a PSR and include
support material so that
CDC can duplicate the
problem.
Decrease appropriate
parameter value on
RESOURC command.
If you are authorized to
detach jobs, enter
ENQUIRE,JSN to identify
existing detached jobs
and DROP,jsn to drop
selected jobs.
Inform customer engineer.
Inform site analyst.
Inform site analyst.
If a packname was
specified, try again
with the WB or NA
parameter to request
that the pack be
mounted. For other
errors, inform site
operator.
Specify correct device
type, or return the
local file and retry.
Inform s ite anly st. If
many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITIALIZE,
and full PFLOAD on the
device.
Examine the LIBEDIT
output to determine
cause of error.
CONTROL
DSP
RESEX
RESEX
IAFEX
1MS
IAFEX
IAFEX
PFM
PFM
PFM
LIBEDIT
| B - 1 8 60459680 H
![](asset-267.png)
i^p\l
VSSBSSEV
MESSAGE
n DIRECTIVE ERRORS.
DISK FULL.
DM* TOO SHORT.
DROP COMPLETE.
DROPPED BY USER JOB jsn.
DROPPING SUPPORT OF SUMMARY, USE ENQUIRE.
DSP - CANNOT ROUTE JOB INPUT FILE.
DSP - COMPLETE BIT ALREADY SET.
DSP - DEFERRED ROUTING NOT ALLOWED.
DSP - DEVICE FULL.
DSP - DEVICE UNAVAILABLE.
DSP - FILE NAME ERROR.
DSP - FILE NOT ON MASS STORAGE.
DSP - FILE ON REMOVABLE DEVICE.
DSP - FOMSM CODE NOT ALPHANUMERIC.
DSP - I/O SEQUENCE ERROR.
DSP - IMMEDIATE ROUTING - NO FILE.
DSP - INCORRECT DATA DECLARATION.
DSP - INCORRECT DISPOSITION CODE.
DSP - INCORRECT EXTERNAL CHARACTERISTICS.
DSP - INCORRECT FILE MODE.
DSP - INCORRECT FILE TYPE.
DSP - INCORRECT FILE TYPE.
DSP - INCORRECT INTERNAL CHARACTERISTICS.
DSP - INCORRECT LID.
DSP - INCORRECT ORIGIN TYPE.
SIGNIFICANCE
The system could not interpret n directives.
Job was terminated without exit processing.
System file DM* cannot accommodate the dump.
Informative only.
The job was dropped by the job jsn.
SUMMARY will be removed in a future release.
An attempt was made to route the job input
fi l e .
The complete bit was not cleared before DSP
was called.
A file cannot be deferred routed if data
declaration, or implicit/expticit remote
text is specified.
There is no space on the device for current
use.
DSP attempted to create a file on a device
that was turned off or is currently
unavailable for access.
An attempt was made to create a file with
an incorrect file name.
An attempt was made to route a file not on
mass storage.
A file on a removable device cannot be
routed.
The forms code specification (FC=fc
parameter) must consist of two
alphanumeric characters.
A request was made on a busy file.
The specified file for the immediate
routing could not be found.
The specified data declaration is not
recognized.
Specified disposition code is not
recognized.
You specified an undefined external
characteristic code.
You attempted to route an execute-only file.
The file being processed is not a local or
queued file type.
You entered a ROUTE command that attempts
to route a direct access file. Direct
access files cannot be routed with the
ROUTE command.
You specified an undefined internal
characteristics code.
You specified an incorrect logical
identifier (LID) for a remote mainframe on
the ROUTE command.
The system cannot queue the file for input
with the specified origin type.
ACTION
Correct errors as listed
in LIBEDIT output and
rerun job.
Resubmit job.
Inform site analyst.
None.
None.
Use ENQUIRE instead of
SUMMARY.
Copy job input file to a
local file and route it.
Clear complete bit
before calling DSP.
Correct and retry.
Retry route at a later
time.
Specify different device
or contact site operator.
Specify valid file name.
Copy file to mass
storage before routing.
Copy file to
nonremovable device
before routing.
Specify alphanumeric
forms code.
Wait until file is not
busy.
Ensure that file to be
routed is available to
job for processing.
Correct and retry.
Verify disposition code.
Ver i fy ex te r na l
characteristic code.
Verify that the file to
be routed is not an
execute-only file.
Ensure that file being
processed is of correct
type.
Copy the direct access
file to a temporary
local file and resubmit
the ROUTE command for
the local file.
Verify internal
characteristics code.
Ensure that your LID
s p e c i fic a t io n i s
correct. If the problem
persists, inform site
analyst.
Specify valid origin
type.
ROUTINE
1AJ
CPMEM
DROP
DROP
ENQUIRE
DSP
DSP
DSP
DSP
DSP
DSP
DSP
DSP
60459680 H B-1?
![](asset-268.png)
MESSAGE
DSP - INCORRECT REQUEST.
DSP - INCORRECT SERVICE CLASS
SIGNIFICANCE
One of the following:
- Parameter block is not within field
length.
- Request was not made with auto recall.
An invalid service class was specified.
ACTION ROUTINE
Change parameter block DSP
addresses or specify
auto recall.
Verify the IPRDECK, SERVICE, DSP
CLASS, and PCLASS entries
and ensure that the MODVAL
VM parameter validation is
correct.
DSP - INCORRECT TID.
DSP - INCORRECT USER COMMAND.
DSP - MASS STORAGE ERROR.
DSP - QFT FULL.
DSP - QUEUED FILE READ ERROR.
DSP - ROUTE TO INPUT NOT IMMEDIATE.
DSP - THIS ROUTING NOT ALLOWED.
DSP - TOO MANY DEFERRED BATCH JOBS.
DSP - USER ACCESS NOT VALID.
One of the following.
- Username and familyname parameters were
not in CM field length.
- Terminal identifier (TID) is greater
than or equal to IDLM for batch jobs.
- The familyname or username is not valid.
For*an operation on an input file, either a
USER command was not included, or the user
name or password on USER command is not
valid.
A mass storage error was encountered on the
file.
The system cannot process your file because
it is already processing its maximum number
of queued files.
The system encountered an equipment
malfunction and, consequently, cannot
process your deferred routed file.
You attempted to queue a file for input
using a deferred ROUTE.
You attempted to change the queue
disposition of a deferred routed file.
You attempted to submit more deferred batch
jobs than allowed by your validation limit.
Caller is not validated to specify one of
the following:
DLID
SLID
Data declaration
Verify that TID
parameters are valid.
Verify that a USER
command is present and
that the user name and
password are correct.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Wait and retry.
Recreate the output file.
Change to immediate
route.
Rescind prior routing by
using the SC disposition
code with the ROUTE
command or macro. Route
the file again with the
desired final
disposition code.
Wait for jobs to
complete or request a
larger validation limit
from site personnel.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
DSP
DSP
DSP
DSP
DSP
DUMP FILE CONTAINS 63 DUMPS. TAPE IS FULL.
DUMP FILE MALFUNCTION-EOI ENCOUNTERED.
DUMP FILE MALFUNCTION-FILE NAME MISMATCH.
In response to a DUMP operation, RECAIM has
determined that the tape already contains
the maximum allowable number of dumps; the
DUMP directive is ignored.
An EOI was encountered before the specified
dump file or record was found; the tape has
probably been overwritten.
The specified file name does not match the
file name found at the specified position
on the dump tape; the tape has probably
been overwritten.
Compress the current RECLAIM
dump tape using the
COMPACT directive or use
a new tape.
Check the contents of RECLAIM
the dump fite tape.
Check the contents of RECLAIM
the dump tape.
DUMP FILE MALFUNCTION-POSITON LOST.
DUMP FILE MALFUNCTION-UNRECOGNIZABLE PFC.
DUMP FILE MUST BE IN WRITE MODE
DUMP FILE NOT FOUND
RECLAIM system error.
The PFC for the dumped file is incorrect;
either the tape is bad or has been
overwritten.
A DUMP or COMPACT was attempted using a
mass storage dump file which was attached
in some mode other than WRITE mode.
A LOAD or COPY was attempted and the mass
storage dump file indicated by the data
base could not be found. The file may have
been purged or may never have been made
permanent.
Inform site analyst. RECLAIM
Check the contents of RECLAIM
the tape.
A t t a c h t h e d u m p fi le i n R E C L A IM
WRITE mode and retry.
Check your options. If RECLAIM
they are correct, you
may have to load your
files from an alternate
source. Check with your
site analyst.
| B - 2 0 60459680 H
![](asset-269.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
cmd DUPLICATE CHARACTER The value you specified in the terminal
definition command cmd conflicts with
another terminal definition.
Try another value. CCP
DUPLICATE FILE NAME.
DUPLICATE FILE NAME
DUPLICATE UJN - MUST SPECIFY JSN.
DUPLICATED LINES.
DVest,DNdn,message.
DWest,DNdn,message.
EC NOT VALIDATED.
EDITING COMPLETE,
filename EMPTY.
EMPTY FILE (SSF)
EMPTY SORT INPUT FILE.
/Sfe^X
END est, nn.
END OF SET INCORRECT REQUEST, filename AT
address.
END OF TAPE, filename AT address.
**** ENDING SUPPORT OF STS FUNCTION 01 ***.
ENQUIRE ABORTED.
ENQUIRY COMPLETE.
The file specified already exists in the
system.
The read or destination file name matches
the primary file name.
Two of your jobs have the same UJN.
Duplicate lines, which would have been
printed during a dump operation, were
suppressed.
A form of PFM error message (issued to the
system dayfile, error log, and sometimes
the user dayfile) identifying the mass
storage equipment on which the error
occurred. The equipment type is 819 disk
(single den sity).
est EST ordinal of device.
dn Device number.
message PFM error message.
A form of PFM error message (issued to the
system dayfile, error log, and sometimes
the user dayfile) identifying the mass
storage equipment on which the error
occurred. The equipment type DW is 819 disk
(double density).
est EST ordinal of device.
dn Device number.
message PFM error message.
The number of extended memory blocks
specified on the Job command either exceeds
that for which you are authorized or
exceeds the machine size available to user
jobs.
Library editing is complete.
The file specified on a SAVE command
contains no data.
Internal error.
Dayfile message indicating that the file
specified on the SORT command contains no
data.
The operator ended batch equipment est for
nn copies.
A multifile set tape is positioned at the
end of set after searching for a file set
that was not found. Until the tape is
returned or repositioned within the
multifile set, all other tape operations on
this tape are incorrect.
The end-of-tape was encountered.
The system will phase out support of this
function.
ENQUIRE has been aborted as a result of a
system error.
Message issued when ENQUIRE command
processing is completed.
Use different name in
request.
Enter the edit command
with the read or
destination file name
different than the
primary file name.
Use the ENQUIRE command
to determine the
appropriate JSN to use.
None.
Refer to the
significance and action
of the message as given
in this list of error
messages.
Refer to the
significance and action
of the message as given
in this list of error
messages.
Check your validation
with the LIMITS command.
Ve r i f y t h a t fi l e
contains data and retry.
Submit a PSR with
information on how
to duplicate the
problem.
Correct and rerun.
Return the tape via a
RETURN, UNLOAD, or EVICT
command, or reposition
the tape with the LABEL
command.
Ensure that correct file
manipulation operation
is specified.
Consult the site analyst
to find a different
method to obtain the
required data.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
None.
CPMEM
PFM
PFM
CPM
LIBEDIT
PFM
IAF
SORT
1MT
1MT
SFP
60459680 H 8-21
![](asset-26a.png)
MESSAGE
ENTER GO TO CONTINUE CURRENT JOB.
RELIST TO LIST RECOVERABLE JOBS,
OR DESIRED JSN:
ENTERING RECOVERY MODE ... WAIT
ENTRY POINT NOT FOUND.
ENTRY POINT TABLE OVERFLOW.
EOF ENCOUNTERED.
EOI CHANGED BY RECOVERY.
EOI ENCOUNTERED.
EQest,DNdn,message.
EQUIPMENT NOT AVAILABLE.
ERASE LIMIT, filename AT address.
ERROR CODE ec, filename AT address.
ERROR - FILES(S) NOT PROCESSED.
ERROR FLAG TERMINATION, filename AT address.
ERROR FLAG TERMINATION, FILE filename AT
address
ERROR IN ALTERNATE CATLIST PERMISSION
SIGNIFICANCE
You have recoverable jobs and the system
awaits your input.
SCOPE 2 is entering recovery mode. There
is a delay until the recovery cycle
completes.
The specified entry point could not be
found.
The number of entry points per program unit
has exceeded the table space allowed.
End-of-file was encountered before copy
termination condition was satisfied.
The file was truncated during deadstart
recovery.
End-of-information was encountered on the
input file.
A form of PFM error message (issued to the
system dayfile, error log, and sometimes
the user dayfile) identifying the mass
storage equipment on which the error
occurred.
est EST ordinal of device.
dn Device number.
message PFM error message.
The requested equipment is either in use
or does not exist, or no requested
equipment with the proper access Level
can be found.
For 1600 cpi or 6250 cpi densities, the
block could not be rewritten properly
after 40 erasures (approximately 15 feet
of tape) or, for 800 cpi, the current block
could not be rewritten properly due to
parity errors after 40 attempts to erase
a single area of tape (approximately
40 feet of tape).
The tape is unusable and the job will
terminate.
1MT error code ec has occurred but no
specific message is issued. This would
normally not occur unless the job was
dropped by the operator.
One or more files were not checkpointed
because CHKPT detected an error while
getting a list of the files at the control
point. This could occur if there are many
local files.
The job was aborted with a tape operation
in progress. The operation/request is not
complete. For example, the operator could
kill the job while tape error recovery is
in progress.
The job was aborted with an input/output
request in progress. The operation/request
is not complete.
The option specified on the AC parameter is
incorrect.
ACTION ROUTINE
Enter appropriate RECOVER
response.
Wait for the user prompt. HELL07
Verify that entry point 1AJ
is valid.
Contact Central Software LIBRARY
Support.
None. COPYB
Use CHANGE command or
macro with CE parameter
to allow access to the
fi l e. M a ke t he fi l e
local and list it to
determine how much of
the file was lost.
If the message was not
expected, check if the
copy was performed as
desired. The source
file may not have been
positioned corre ctly
before the copy.
Refer to the
significance and action
of the message as given
in this list of error
messages.
Ensure accuracy of macro
or command or retry at a
later time.
Clean the tape drive.
Have the tape cleaned and
certified or use a new tape.
Run diagnostic T7X to ensure
proper tape drive operation.
PFM
COPYB
COPYC
LFM
RESEX
1MT
Inform site analyst,
Contact Central Software
Support.
None.
Check the AC parameter
description and correct
the command.
1MT
CHKPT
1MT
1MS
PFILES
/ * ^ s \
'^s^\
B-22 60459680 H
![](asset-26b.png)
MESSAGE
ERROR IN ARGUMENT.
ERROR IN ARGUMENTS.
ERROR IN ARGUMENTS.
SIGNIFICANCE
One of the following.
- The pfn is blank or fn = filename.
- You specified no arguments or a blank
argument.
- You specified too many files.
- You entered an incorrect parameter or
combination of parameters.
- You specified both XD and XT parameters
in a command.
- You specified an XD or XT parameter in z
command other than CHANGE, DEFINE, or
SAVE.
- You specified an XD or XT parameter in a
DEFINE or SAVE command without
specifying a PW parameter.
The system did not recognize one or more
parameters.
One or more of the following command errors
were detected.
- More than one date was entered.
- No options were selected.
- The parameter was incorrect or could not
be recognized.
- The TM option was selected but no data
was specified.
- Both the device number parameter and the
pack name or auxiliary device parameter
were selected; auxiliary devices do not
have device numbers.
- Both the NA and WB parameters were
specified; select one or the other.
ACTION
Reenter the command with
correct parameters.
Compare the parameters
specified with the
command description.
PFILES
Correct command and BLANK
retry. PURGALL
ITEMIZE
ERROR IN ARGUMENTS. RESTART detected incorrect arguments on the
command call.
Correct the command. RESTART
ERROR IN ARGUMENTS. The parameter list specified on the Job
command or the USER command was not
correct.
Correct the parameter
list and retry.
ERROR IN BACKUP REQUIREMENT.
ERROR IN CHVAL ARGUMENTS.
The option specified on the BR parameter on
the DEFINE, CHANGE, or SAVE command is
incorrect.
An invalid keyword was specified on the
command. Too many characters were specified
for the UC parameter.
Check the BR parameter
description and correct
the command.
Correct and retry.
PFILES
MODVAL
ERROR IN CONTROL ARGUMENTS. Either the number of arguments was
incorrect, an incorrect argument was
specified, or a numeric parameter was
nonnumeric.
Check the description of
the command.
CONTROL
ERROR IN DATE. The format of the date (ad, md, or cd)
parameter in a PURGALL request was
incorrect.
Check the format of the
PURGALL command in
section 10.
ERROR IN DEVICE NUMBER. The file residency as specified by the
device number parameter was incorrect.
Correct the device
number parameter.
ERROR IN DOCMENT ARGUMENTS. An error was found among the numbers that
were entered as parameters.
Check parameters and
retry.
DOCMENT
ERROR IN EXPIRATION DATE. One of the following:
You specified an expiration date
that is before the current date.
You specified a date with the month
not in the range 1-12 or the day not
in the range 1-31.
You specified an XT parameter
greater than the maximum allowed.
Reenter the command with
a correct XD or XT
parameter.
PFILES
ERROR IN FCOPY ARGUMENTS. The format of the FCOPY command is in error. Refer to the description
of the FCOPY command.
ERROR IN FILE CATEGORY. The option specified on the CT parameter is
incorrect.
Check the CT parameter PFILES
description and correct PURGALL
the command.
ERROR IN FILE DATA. When the specified file was loaded from
tape, an error was encountered in the data.
Enter CHANGE command or
macro with CE parameter
to allow access to the
file. Make the file
local and ensure the
accuracy of the data.
00*\ ^
60459680 H B - 2 3 |
![](asset-26c.png)
ERROR IN FILE TYPE.
ERROR IN FILENAME LIST.
ERROR IN KRONREF ARGUMENTS.
ERROR IN LIBRARY ARGUMENTS.
ERROR IN LIMITS ARGUMENT.
ERROR IN MODE.
ERROR IN PASSWOR ARGUMENTS.
ERROR IN PASSWOR ARGUMENTS.
ERROR IN PERMIT DATA.
ERROR IN PREFERRED RESIDENCE.
ERROR IN RESIDENCE.
ERROR IN ROUTE FUNCTION, LFN=filename.
ERROR IN SECHOR PARAMETERS.
ERROR IN SUBSYSTEM.
ERROR IN SYSTEM TEXT.
ERROR IN TIME.
ERROR IN TRMDEF ARGUMENT.
ERROR IN UPROC ARGUMENTS.
ERROR IN 5TH COPYL PARAMETER.
ERROR LIMIT, integer ADDITIONAL ERRORS
FOUND.
SIGNIFICANCE
You specified an incorrect file type.
A syntax error was found in the list of
file names entered using the PF=* option.
The command entered contained an incorrect
parameter.
The LIBRARY command has an incorrect
argument or the format of the command is
incorrect.
Dayfile message indicating that parameters
other than L=lfn were included on the LIMITS
command.
The option specified on the M parameter is
incorrect.
PASSWOR command parameters are incorrect.
This message is returned for either of two
reasons:
You entered a PASSWOR command that
specifies an expiration date or
term, but does not specify the old
and new passwords. You must specify
an old and a new password to change
the expiration date or term.
You entered a character other than
I, B, or carriage return in response
to the PASSWOR prompt:
ENTER INTERACTIVE OR BATCH (I,B)
When the specified file was loaded from
tape, an error was encountered in the
permit entries.
The option specified on the PR parameter on
the DEFINE or CHANGE command is incorrect.
The R=r parameter you specified
contains an incorrect device type.
Informative message issued to the system
dayfile indicating that an error occurred
while routing filename.
You specified and unknown parameter on a
SECHOR command.
The option specified on the SS parameter c
the CHANGE or SAVE command is incorrect.
The system text referenced by the KRONREF
command did not contain symbol definitions.
The format of the time parameter in a
PURGALL request was incorrect.
One or more parameters specified in the
TRMDEF command were in error.
Dayfile message indicating that incorrect
command arguments were entered.
Fatal error; only A, R, E, and T are
recognized parameters.
More than 20 errors were found during
conversion.
integer Errors in excess of 20.
ACTION
Check the PURGALL
command description
and correct the
statement.
Correct the file name
list and retry.
Correct and rerun.
Correct the error and
reenter the command.
Correct and rerun.
Check the M parameter
description and correct
the command.
Correct command and
reenter.
Correct the PASSWOR
command and resubmit.
Enter CHANGE command or
macro with CE parameter
to allow access to the
file. Do a CATLIST to
see if the permits are
accurate.
Check the PR parameter
description and correct
the command.
Correct the R=r
parameter.
Examine the job's
dayfile for a more
specific error message.
Reenter the command with
the correct parameter(s).
Check the SS parameter
description and correct
the command.
Ensure that the system
text specified by the 6
or S parameter contains
symbol definition s.
Check the format of the
PURGALL command in
section 10.
Ensure that parameters
are in correct format
and new values are valid.
Specify the correct
arguments and rerun.
Correct processing
option.
Verify deck and retry.
RECLAIM
KRONREF
LIBRARY
MODVAL
PFILES
MODVAL
MODVAL
/•cSfev
PFM
PFILES
DSP
MODVAL
COPYL
COPYLM
/"•^iSy
B-24 60459680 H
![](asset-26d.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
ERROR LIMIT EXCEEDED. Number of parity and block-too-large errors
exceed the error limit.
ERROR ON DETACH.
ERROR PROCESSING LIMIT.
EXCHANGE PACKAGE/MEMORY DUMP ON FILE
ZZZDUMP.
EXEC - SLAVE i OMITTED - message
- STOM FILE ERROR.
EXECUTE
EXECUTE ONLY FILE.
EXTENDED MEMORY BLOCK OUT OF RANGE.
EXTENDED MEMORY FLAG REGISTER PARITY.
EXTENDED MEMORY OUT OF RANGE.
EXTENDED MEMORY PARITY ERROR.
EXTENDED MEMORY PARITY ERROR.
EXTENDED MEMORY READ ERROR.
EXTENDED MEMORY ROLLIN ERROR.
FAMILY NOT FOUND.
FCOPY COMPLETE.
FET TOO SHORT.
FIELD BEGINNING AT nn NO COMPARE.
FILE BOI/EOI/UI MISMATCH.
FILE COUNT PARAM NOT NUMERIC.
FILE EMPTY.
FILE ERROR filename.
The system was not able to detach the job
upon your request.
Following an error, a job has tried to
restart itself more than 512 times.
The exchange package and memory dump is
written on local file ZZZDUMP because the
job is of interactive origin and file
OUTPUT is assigned to a terminal.
MESSEXEC was unable to establish or main
tain access to a communication file with
MSSSLV on mainframe i. MSSEXEC will con
tinue to operate, but will not attempt to
receive requests from MSSSLV on mainframe i.
The system is processing one of your
commands.
The permanent file accessed can only be
executed and cannot be read, written, or
listed.
Data transfer between CM and extended
memory specified an extended memory address
outside the job field length.
Parity error detected on extended memory
flag register operation.
Job referenced extended memory address
outside job field length.
ECS transfer on a model 176 failed.
Extended memory failed.
An unrecoverable extended memory read error
occurred.
An irrecoverable extended memory parity
error occurred while the system was writing
the job's extended memory field length to a
rollout file.
No family exists with the name you
specified.
The FCOPY conversion is finished.
FET is not long enough for processing by
requested function.
Verification of label field at character
position nn does not compare with that
specified by the user on an OPEN statement.
Data in the system sector for file filename
does not match information from the EOI
sector and/or catalog information. This
indicates that the file has been destroyed.
The file count specified with the N command
option is not numeric.
The file specified was empty.
An incorrect address was detected on file
filename.
If dayfile shows block-
too-large errors have
occurred and tape is S,
L, or F format, increase
block size and retry;
otherwise, tape is probably
assigned in the wrong
format. If parity errors
have occurred, the tape is
bad and the data on it can
not be correctly recovered.
Retry command.
None.
To examine the exchange
package and dump, list
file ZZZDUMP.
If MSSSLV is to be run on
mainframe i, idle MSSEXEC,
purge the STOM file,
initiate MSSSLV, and then
initiate MSSEXEC.
None.
Ensure accuracy of entry.
Analyze the job output
and dumps to determine
the cause of the error.
Inform customer engineer.
Analyze the job output
and dumps to determine
the cause of the error.
Inform customer engineer.
Inform customer engineer.
None.
Inform the site analyst
of the parity error.
Rerun the job after
extended memory has been
repaired.
COPYB
Inform site analyst. If
many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITALIZE,
and full PFLOAD on the
device.
Correct the parameter
and retry.
Verify that the file
contains data and retry.
Correct error and retry.
IAFEX
1AJ
CPMEM
1AJ
1AJ
1AJ
1AJ
RECLAIM I
CPMEM
1RI
Retry with an existing CONTROL
family name.
None. FCOPY
Increase FET size. LFM
1HT
ITEMIZE
LFM
SFM
RESTART
60459680 H B-25
![](asset-26e.png)
MESSAGE
FILE IDENTIFIER NOT FOUND.
FILE/JOB NOT FOUND.
FILE LENGTH ERROR.
FILE NAME CONFLICT.
.FILE NAME CONFLICT.
SIGNIFICANCE
You failed to specify or improperly
specified the FI=fileid or QN=seqno
parameters of the LABEL command.
The specified file or job was not found in
the system.
The length of a file does not equal the
length specified in the catalog. This
indicates that the file has been
destroyed.
The same file name has been specified for
more than one parameter.
For the L072 command, the S and L file
names are the same. For the ITEMIZE
command, the output and binary file names
are the same.
ACTION
Correct the FI=fileid
and QN=seqno parameter
specifications of the
LABEL command.
Use the ENQUIRE command
to ensure job is still
in the system.
Inform site analyst. If
many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITIALIZE,
and full PFLOAD on the
device.
Correct the command so
that all files have a
unique name.
Rename either output
file o r fil e t o be
itemized.
1MT
CONTROL
PFM
LIBEDIT
L072
ITEMIZE
FILE NAME CONFLICT.
FILE NAME CONFLICT.
FILE NAME CONFLICT.
The old file, replacement file, and the
new file were not all specified by
unique file names.
Either you tried to process two files
having the same name or you specified a
reserved file name.
The same file name was specified for both
the file to be itemized and for the list
file.
Specify unique file
names.
Correct the command so
all files have a unique
name.
Specify the correct file
name and retry.
ITEMIZE
COPYL
COPYLM
FCOPY
COPYB
ITEMIZE
FILE NAME ERROR The file name specified contains more than
seven characters or non-alphanumeric
characters.
Reenter command with
correct file name. IAF
FILE NAME ERROR.
FILE NAME MISSING.
FILE NAME TOO LONG.
FILE NOT DISK RESIDENT
FILE NOT FOUND - filename.
FILE NOT FOUND - filename
FILE NOT ON MASS STORAGE.
FILE NOT OVERLAY FORMAT.
File name contains incorrect characters or
contains more than seven characters.
The LO=P, LP=FP or L0=X option was
specified in a CATLIST command, but no file
was specified with the FN parameter.
A file name was specified that has more
than seven characters.
The disk space associated with the
specified permanent file has already been
dropped.
The designated input file did not exist
prior to the copy or verify.
RECLAIM did not process the named file
because it could not find the file on the
dump tape or file (for a LOAD or COPY
operation) or it could not find a local or
permanent file by that name (for a DUMP
operation).
filename A file name you specified in
a RECLAIM PF or FN option.
The specified file does not reside on mass
storage.
First record on the file was not an overlay.
Ensure that a valid file LFM
name is specified. LISTLB
PFM
Correct and retry. CATLIST
Use a file nam e th at h as C OPYL
seven or less characters. COPYLM
If file should have existed, COPYB
reaccess the file and retry. VERIFY
Check to see that a file RECLAIP
exists with the
specified file name.
Copy file to mass 1AJ
storage and retry.
Correct file format on LDR
LDR call.
FILE STATUS NOT SPECIFIED.
FILE STRUCTURES NOT COMPATIBLE.
FILE TOO LONG.
Your SETFS command does not specify a file
status.
Verification results cannot be guaranteed
correct when the logical structures of the
files being verified are not compatible.
The local file specified for a SAVE,
REPLACE, or APPEND command exceeds the
length allowed or the direct access file
specified for an ATTACH operation in WRITE,
MODIFY, UPDATE, or APPEND mode exceeds the
direct access file length limit for which
you are authorized.
Retry command with a
file status parameter.
Reduce length of file or
save as a direct access
fi l e .
B-Z6 60459680 H
![](asset-26f.png)
MESSAGE
FILE TOO LONG, FILE filename AT address.
FILENAME CONFLICT.
nnn FILE(S) PROCESSED.
FIP - ACN acn NOT WITHIN RANGE.
FIP - CIO ERROR xxB ON filename, reason
FIP - CONNECTION BROKEN ON ACN acn.
FIP - CONVERT MODE N/A FOR filename.
SIGNIFICANCE
The length of the direct access permanent
file currently being written exceeds the
direct access file length limit for which
you are authorized.
The first two parameters of the GTR command
are identical.
The operation was performed on nnn files.
A data transfer error has occurred. The
system has halted the file transfer.
acn Application connection number
(octal).
NETXFR has terminated file transfer because
of a fault while reading or writing the
l o c a l fi l e .
xx CIO error code (octal).
Refer to Volume 4 of the NOS
2 Reference Set.
filename The affected file,
reason Abbreviated error
description:
ERROR ON FILE-OPEN.
DEVICE FULL.
PARITY ERROR.
TAPE BLOCK SIZE ERROR.
The network connection has been broken
unexpectedly. The system has halted the
file transfer.
acn Application connection number
(octal).
The application timed out waiting for
resources to become available,
filename The affected file.
ACTION
Reduce the length of the
file or ask site personnel
for a larger direct access
file length limit.
Specify different file
names for the first two
parameters on the GTR
command.
None.
Inform site analyst.
Correct problem and
retry transfer. Inform
site analyst if
problem persists.
Rerun your job.
site analyst.
Inform
Try again. If problem
persi st s, inf or m si te
analyst.
ROUTINE
1MS
GTR
MFILES
FIP
FIP
FIP
FIP - DISABLE WARNING RECEIVED.
FIP - GT 4 FILE TRANSFERS INITIATED.
FIP - INITIATING XFR OF filename.
FIP - NETOFF DURING FILE TRANSFER.
FIP - NETXFR ERROR, ALL TRANSFER TABLES IN
USE.
FIP - NETXFR ERROR, BAD ATTRIB. xxxx FOR
COMMAND yy.
FIP - NETXFR ERROR, BAD INTERNAL TRANSFER
STATE = xxB.
FIP - NETXFR ERROR. BAD PARAMETER DD = xxB.
FIP - filename ON INVALID DEVICE.
The system has halted the file transfer
because the network is shutting down
immediately.
The system is attempting too many file
transfers simultaneously. The system has
not initiated the file transfer you are
requesting.
The system has initiated the transfer of
fil e fi le n a m e.
filename File being transferred.
An internal error occurred during your file
transfer. The file transfer was not
completed successfully.
NETXFR aborted the application after
finding all internal tables in use.
NETXFR aborted the application after
finding a faulty internal attribute value.
xxxx Attribute value (hexadecimal).
yy associated command value
(decimal).
NETXFR detected an internal fault and
aborted the application.
xx Internal transfer state (octal).
NETXFR detected a faulty DD parameter in
the application's NETXFR call, and aborted
the application.
xx DD parameter value (octal)
You have file filename assigned to an
inaccessible device. The system has halted
th e fi l e t r an s f e r.
filename File being transferred.
Retry the file transfer
after the network is
reactivated.
Inform site analyst.
Inform site analyst.
Retry transfer. Inform
site analyst if
problem persists.
Retry transfer. Inform
site analyst if
problem persists.
Retry transfer. Inform
site analyst if
problem persists.
Inform site analyst or
correct application
program.
Reassign file filename
to an accessible device
and rerun job. Inform
site analyst if the
problem persists.
FIP
FIP
FIP
FIP
FIP
FIP
FIP
00^\
60459680 H B-27
![](asset-270.png)
MESSAGE
FIP - OUTPUT BLOCK NOT DEL ON ACN acn.
FIP - PREMATURE TERMINATION RCVD ON acn.
FIP - PROTOCOL ERROR DETECTED.
FIP - RHF I/O ERROR xxB ON filename, reason
FIP - SECOND FILE XFR ON ACN acn.
FIP - SYSTEM ERROR, reason, status.
SIGNIFICANCE
The remote system did not receive the
network message or data block before the
time-out period elapsed. The system has
halted the file transfer.
acn Application connection number
(octal).
The system detected an error during a file
transfer and halted the file transfer,
acn Application connection number
(o c t a l ) .
An unrecognized or unexpected network
message has been received. The file
transfer is ended.
NETXFR has terminated file transfer because
of a fault while reading or writing file
data to or from the network.
filename The affected file.
xx RHF I/O error code (octal).
Refer to the Remote Host
Facility Access Method
Reference Manual for the
descriptions of the error
codes,
reason Abbreviated error
description:
BLOCK NOT 60-BIT MULTIPLE.
BLOCK LENGTH MISMATCH.
CONTROL WORD FORMAT ERROR.
HOST A8N MISCOMPARE.
INVALID PARTIAL BLOCK.
LAST BLOCK TOO BIG.
NETWORK ABN MISCOMPARE.
RHF FET PARAMETER ERROR.
UNKNOWN BLOCK ERROR.
The system attempted a file transfer on a
connection that already has a file transfer
in progress. The system halted the second
file transfer.
acn Application connection number
(o c t a l ) .
A system error (indicated by reason) has
interrupted NETXFR, which is either
attempting or abandoning recovery
(indicated by status). Subsequent dayfile
messages indicate whether the file transfer
completed.
ACTION
Retry the file
transfer. Inform site
analyst if the problem
persists.
Retry file transfer.
Inform site analyst if
the problem persists.
Retry file transfer.
Inform system analyst
if problem persists.
Retry transfer. Inform
site analyst if
problem persists.
ROUTINE
FIP
Inform site analyst.
Retry the file transfer
after correcting the
problem, or inform
site analyst.
FIP
FIP
FIP
FIP
FIP - TIMED OUT WAITING FOR NETWORK.
FIP - TRANSFER OF filename COMPLETE.
FIP - TRANSFER OF filename IN PROGRESS.
FIP - XFR COMPLETE, NO ERR, IDLEDOWN.
FIP - XFR TERM WITH ERR, IDLEDOWN.
FL BEYOND MFL.
reason CPU TIME LIMIT
PP ABORT
OPERATOR DROP
OPERATOR RERUN
EM PARITY ERROR
MASS STORAGE LIMIT
I/O LIMIT
TERMINAL INTERRUPT
sta tus FIP R EPRIEVI NG
FIP REPRIEVES EXHAUSTED
The network failed to respond before the
time-out period elapsed. The system halted
th e fi l e t r an s f e r.
Self-explanatory.
filename File being transferred.
Self-explanatory.
filename File being transferred.
The network is shutting down, but your file
transfer completed successfully.
The network is shutting down and your file
transfer ended unsuccessfully.
Request field length exceeds maximum field
length.
Ensure that the network
and remote system are
active and retry the
file transfer. Inform
site analyst if the
problem persists.
None.
FIP
Retry the file transfer
when the network becomes
active.
Increase MFL via MFL
request or increase your
validation FL.
1AJ
| B - 2 8
/•^v
/*^^\
60459680 H
![](asset-271.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
y^Vfffesr^k
FL REQUEST BEYOND MFL (ECS).
FL TOO SHORT FOR PROGRAM.
FLE TOO SHORT FOR LOAD.
**** FORMAT ERROR.
FORMAT ERROR.
FORMAT ERROR ON COMMAND.
FORMAT REQUIRES UNLABELED TAPE.
FOT FULL - FILES IGNORED.
pfn FOUND.
un FOUND.
FOUND SECTION section.
*FR* NOT FOUND.
FROM sjsn: message
FROM NOP...message.
FUNCTION REJECT, filename AT address.
FWA .GE. LWA+1.
FWA/LWA .GE. FL.
GARBAGE IN OLDPL HEADER.
GLOBAL LIBRARY DIRECTORY DEFECTIVE.
Extended memory field length requirements
for the job step exceed the extended memory
field length allowed.
The job's field length is too short for the
program.
You attempted to load extended memory data
beyond the job's extended memory field
length.
Your entry is not recognized as valid
system input. The line of input is
disregarded.
One of the following.
- The GTR command format was incorrect.
- An incorrect library type was specified.
- A record name longer than seven
characters was specified.
An error was detected in the format of the
command.
The format specified (F) is valid only for
unlabeled tapes.
The queued files were not processed because
there was no FOT entry for the creation
and/or destination familyname and the table
was full.
The file name specified on the CATLIST
(10=0) command was found in your catalog or
the file name or user name specified on the
CATLIST (L0=P) command was granted
permission.
This is the last line of a three-line
message:
MULTIFILE NOT FOUND, filename AT address.
REQUESTED SECTION section.
FOUND SECTION section.
The system has reached the end of a
m u l t ifi l e s e t .
The specified string was not in the
dayfile. If your job is interactive you
will get a full dayfile dump. A dayfile
dump is not produced for a batch job.
Another interactive user with the JSN sjsn
sent this message using the DIAL command.
The network operator sent this message.
Function was rejected (possible hardware
problem).
The first word address parameter was
greater than the last word address
parameter on DMP, DMD, DMPECS, DMDECS, LOC,
or PBC command or DMP, DMD, DED, or DEP
system requests.
Either first word address parameter of LOC
or the last word address of LOC or PBC was
greater than or equal to your field length.
The file has been identified as a program
library, but does not have a recognizable
format.
The global library directory file ZZZZZLD
contains errors.
Increase job step
extended memory field
length.
Rerun the job with
larger field length
specification.
None.
Refer to the description
of the GTR command.
Check the description of
command format.
The tape must be
assigned as an unlabeled
tape.
A level 0 deadstart is
required to create some
space in the FOT.
None.
Retry with a corrected
FR=string.
If validated to use the
access subsystem, you
may respond to this
message using DIAL.
If necessary, you can
respond using the MS
command.
Inform site analyst.
Correct error and retry.
Reduce FWA and/or LWA
and retry.
Try rebuilding the file
if possible. Inform
site analyst.
Regenerate the library
directory file.
1MA
1AJ
1AJ
1AJ
1AJ
RESEX
QLOAD
QMOVE
»FM
1MT
1MT
CPHEM
CPMEM
ITEMIZE
1AJ
60459680 H B-29
![](asset-272.png)
MESSAGE
GLOBAL LIBRARY DIRECTORY NOT FOUND.
SIGNIFICANCE
Global library set processing is active,
but there is no directory file (ZZZZZLD).
GLOBAL LIBRARY SET CLEARED.
GO FROM JOB jsn
GO FROM OPERATOR
GTR ERRORS.
.H VALUE INCORRECT.
HARDWARE RERUN THRESHOLD EXCEEDED.
HOST AVAILABLE CONTROL CHARACTER=char
ENTER INPUT TO CONNECT TO HOST
HOST BUSY CONTROL CHARACTER*char
ENTER char HD TO SEE HOST STATUS
HOST CONNECTED CONTROL CHARACTERS char
READY FOR INPUT
HOST CONNECTED CONTROL CHARACTER=char
TERMINAL DISABLED BY NOP
HOST CONNECTED CONTROL CHARACTER* char
READY FOR INPUT
HOST DISCONNECTED CONTROL CHARACTER=char
ENTER INPUT TO CONNECT TO HOST
HOST DISCONNECTED CONTROL CHARACTER=char
TERMINAL DISABLED BY NOP
HOST UNAVAILABLE CONTROL CHARACTER=char
ENTER char HD TO SEE HOST STATUS
HTIME xxxxxxxxxxxx.xxx KCYCLES.
HTIME NOT AVAILABLE.
I/O LIMITS EXCEEDED.
I/O ON EXECUTE-ONLY FILE.
I/O ON EXECUTE-ONLY FILE filename AT
address.
An informative message.
A 60 command was issued to the job by the
job jsn.
A GO command was issued to the job by the
console operator.
There are errors on the GTR command.
The H parameter was zero or greater than
the buffer length.
The job has been rerun the maximum number of
times due to a hardware error. The maximum
is n-2, where the default is n=2 (defined by
HRTL in common deck COMSMSC).
Your selected host is available,
char The network control
character for your terminal.
The host rejected your attempt to connect,
char The network control
character for your terminal.
You are connected to the host,
char The network control
character for your terminal.
The network operator has disabled your
terminal. No further input is possible,
char The network control
character for your terminal.
You are connected to the host,
char The network control
character for your terminal.
You have been disconnected from the host,
char The network control
character for your terminal.
The network operator has disabled your
terminal. No further input is possible,
char The network control
character for your terminal.
You have attempted a connection to a host
that is not up.
char The network control
character for your terminal.
Dayfile message giving the model 176 CPU
clock cycle count for the job. The count
is in kilocycle units.
The HTIME command or macro is valid only on
a model 176.
Your validated job I/O limits have been
exceeded during the current RECLAIM session.
An overlay load was attempted from an
execute-only file other than that from
which the main routine was loaded.
You attempted an action not allowed on an
execute-only file.
ACTION
Enter the LIBRARY
command with no
parameters to clear the
global library set
processing, or
regenerate ZZZZZLD by
reentering the LIBRARY
command with the
appropriate libraries
specified.
None.
None.
None.
Check the description of
the GTR command.
Correct parameter and
retry.
Analyze job dumps, mainte
nance registers, and the
error log for HPA reports to
determine cause.
Enter any input to
initiate your connection
to the host.
Check the status of
the hosts in your
configuration.
Proceed with your login
to the host.
ROUTINE
1AJ
Proceed with your login
to the host.
None.
None.
Check the status of
the hosts in your
configuration.
None.
Log in and retry the
operation. If it fails
again, check your
validated I/O limits for
tape mounts to ensure
that you have not
exceeded your limits.
Correct overlay calls
and retry.
Assign file in proper
mode to allow the
desired operation.
LIBRARY
1RI
1RI
GTR
L072
1AJ
CCP
CCP
CCP
CCP
CCP
1AJ
1AJ
RECLAIM
/■^StSk
1MS
| B - 3 0 60459680 H
![](asset-273.png)
MESSAGE
I/O SEQUENCE ERROR.
I/O SEQUENCE ERROR ON FILE filename AT
address.
SIGNIFICANCE
Action was requested on a local file that
was busy.
You attempted to perform a function on a
local file before another function on the
same file was complete.
ACTION ROUTINE
Write a PSR. LFM
PFM
1AJ
Modify program to wait 1MS
until each function is
complete before
attempting another.
IAF CLOSED. IAF is not available for use by terminals.
Issued by NAM. IAF and NAM did not
connect.
Contact Central Software
Support.
IDLE The system is waiting for you to enter a
command.
Enter a command.
ILLEGAL PW SPECIFICATION - IGNORED.
ILLEGAL REQUEST.
The value specified with the PW command
option is not numeric.
No parameters were specified on a DMPECS or
DMDECS command.
C o r r e c t t h e p a r a m e t e r I T E M I Z E
and retry.
Retry job with corrected CPMEM
command.
ILLEGAL USER.
cmd ILLEGAL VALUE
IMPROPER ACCESSIBILITY.
IMPROPER LOGIN, TRY AGAIN.
IMPROPER VALIDATION.
IMPROPER VALIDATION.
INCORRECT ACCESS LEVEL FOR EQUIPMENT.
INCORRECT ARGUMENT.
INCORRECT ARGUMENT VALUE.
INCORRECT CHARACTER.
Four unsuccessful attempts at login were
made after which the terminal was
disconnected from the system.
You specified an invalid value in the
terminal definition command cmd.
You did not specify the correct file
accessibility on the LABEL command or
macro, or volume accessibility was set and
you attempted to assign the tape as
unlabeled from a nonsystem origin job.
You have entered an incorrect family name,
user name, or password during login.
You entered incorrect or insufficient
validation information.
A CHARGE command is required to continue.
You have specified a level outside of the
equipment access level limits.
On a SETFAL, SETJAL, SETPFAC, or SETPFAL
command, you specified an incorrect
argument other than access level or access
category.
A directive keyword was equated to an
incorrect value such as a file name longer
than seven characters or an alphabetic
character in a numeric string.
Incorrect character read from 9-track
tape. If a 1 is detected in bit 7 of a
translated character, the character is
incorrect. The dayfile message STATUS
ERROR, filename AT address precedes this
message and specifies the file (filename)
and the address.
Obtain accurate login NETVAL
information before
attempting to log in.
Inform site analyst if
problem persists.
Choose a valid value NETVAL
(refer to appendix J).
Ensure accuracy of RESEX
request.
Check parameters and IAFEX
retry.
Verify that USER command 1AJ
precedes rest of job
(followed by CHARGE, if
required) and is the
first command after the
Job.
Enter a CHARGE command. 1AJ
Use access level within RESEX
required equipment's
access level limits, or
use equipment with
access level required.
Reenter the command with MLSEXEC
correct arguments.
Correct the value and RECLAIM
retry.
Verify the following: 1MT
- Tape contains coded
data rather than binary,
binary. If binary, use
binary copy operation.
- Tape is ASCII rather
than EBCDIC. If
EBCDIC, specify CV=EB
on LABEL command.
- Tape is 7-bit rather
than 8-bit ASCII. If
8-bit, use FCOPY to
convert to 7-bit.
If all the above are
verified (that is,
tape is 7-bit ASCII)
no t i fy s ite an a l y st.
60459680 H 8-31
![](asset-274.png)
MESSAGE
INCORRECT CHARACTER NUMBER.
INCORRECT CHARGE.
INCORRECT COMBINATION OF QN/SI.
xx INCORRECT COMMAND
INCORRECT COMMAND.
INCORRECT COMMAND.
INCORRECT COMMAND
INCORRECT COMMAND
INCORRECT COPY.
INCORRECT COUNT.
INCORRECT CPU PRIORITY VALUE.
INCORRECT DC CODE.
INCORRECT DC PARAMETER - dc
INCORRECT DEVICE REQUEST.
INCORRECT END OF JOB OPTION SPECIFIED.
♦INCORRECT ENTRY, TRY AGAIN*
INCORRECT EQUIPMENT.
INCORRECT EQUIPMENT ON FILE filename AT
address.
INCORRECT ERROR EXIT ADDRESS.
INCORRECT EXTERNAL CALL.
INCORRECT FILE MODE.
SIGNIFICANCE
In a copy request, one of the following was
detected.
- Last character position was less than
first character position.
- Last character position was greater than
150.
- Either first character position or last
character position was unrecognizable.
Dayfile and output file message indicating
one of the following.
- The charge or project number does not
exist.
- The project number is not available to a
user with this user name.
- The charge or project number exists but
is inactive.
SI was specified and QN was not. If SI is
specified, then QN must also be specified.
The characters xx must be a terminal
definition mnemonic or interactive status
command.
You entered an incorrect command or a
command you are not authorized to use.
The system could not identify the command.
You specified an incorrect command or
too many parameters on the command.
One of the following has occurred:
- The CHARGE command has an incorrect
parameter or it has no terminator.
- You entered an incorrect command or a
command you were not validated to use.
- The job was not in a state to process
the command at that time.
File and/or conversion types do not meet
copy requirements.
The copy file count is nonnumeric or
specified as zero.
You specified a CPU priority value which
exceeds the maximum value allowed.
Disposition code specified on the command
is not valid.
You specified an incorrect DC=dc
parameter.
The device type (R parameter) specified on
a request for an auxiliary device cannot be
recognized or does not exist in the
system. If the auxiliary device specified
by the PN parameter is not the same type as
the system or job default, the R parameter
must be included.
The option specified is not valid for a
noninteractive job.
You entered incorrect characters in
response to an SRU limit or time limit.
Equipment specified does not exist or is
not allowed (for example, an interactive
terainal is requested from other than
interactive origin, or a tape is being
requested with the REQUEST macro).
A system error.
Error exit address is beyond the job's
current fiel d length.
RESEX did not recognize an external call.
You tried to unlock a file that was
attached in execute-only mode.
ACTION
Ensure accuracy of
command parameters.
COPYC
COPYC
Check to see that charge
and project numbers are
correct and reenter.
Specify QN and rerun the
job.
Ensure the accuracy of
your entry and retry.
Correct command and
reenter.
Check validity of
command.
Check the accuracy
of the command.
Use the LIMITS command
to check your validation
and, if validated to use
command, correct the
format of the command
and reenter.
Correct error and retry.
Correct command and
retry.
Reenter the command with
a valid CPU priority.
Correct and retry.
Correct the
DC=dc parameter
Examine auxiliary device
request and ensure its
accuracy.
Retry with a different
option.
Enter correct characters.
Ensure that file resides
on a legal equipment
type.
Inform site analyst.
None.
Inform site analyst.
None.
CHARGE
LISTLB
1AJ
QGET
DROP
CHARGE
IAFEX
COPYB
COPYC
CONTROL
QGET
DROP
CPM
IAFEX
LFM
RESEX
1MS
1AJ
RESEX
LFM
| B - 3 2 60459680 H
![](asset-275.png)
MESSAGE
INCORRECT FILE NAME filename AT address.
INCORRECT FILE STATUS.
INCORRECT FILE TYPE.
pfn INCORRECT FILE TYPE.
INCORRECT FILE TYPE FOR SPECIFIED CHARACTER
SET.
INCORRECT HOLL. CODE, RECxxx CDyyyy.
INCORRECT I/O REQUEST ON FILE filename AT
address.
INCORRECT ID CODE.
INCORRECT INPUT FILE.
INCORRECT INPUT FILE SYSTEM SECTOR.
INCORRECT INSTRUCTION.
SIGNIFICANCE
The file name does not conform to
established rules. The file name must have
a maximum of seven characters,
alphanumeric, and must be left-justified
with binary zero fill.
Specified file status is incorrect.
The specified file is of a type not allowed
in the requested operation. Possible
causes include attempts to
- Change a nonlocal file to file type
library.
- Designate a direct access file as the
primary file.
- Route the primary file.
- Change the access level of a nonlocal
file.
The operation requested cannot be performed
on the specified file because it is of the
wrong file type. This message is issued
when you 1) attempt to define a direct access
file with the same local file name as a
file currently assigned to the job that is
of a file type other than local, or 2) the
local file being saved is a direct access
file attached in read/allow modify or
read/allow append mode.
ASCFL or EBCFL was specified as the
character set for a non-tape file, or any
other character set for a stranger tape
file.
Command yyyy in record xxx was found to
contain an incorrect Hollerith code. The
job was terminated without EXIT processing.
The system could not recognize the
specified function code, or the code was
not valid for the type of device to which
the file was assigned. You attempted to
write on a local file that resides on a
device whose highest access level is below
the current access level of your job. The
system provides a dump of the FET on file
OUTPUT.
An identification code not in the range
0-678 or 77B is present on the LDI command.
An attempt was made to pack a file that is
assigned to an interactive terminal. For
example, file INPUT for an interactive
origin jobs cannot be packed.
Job terminated without exit processing due
to system error.
The CPU attempted to execute an incorrect
or unavailable instruction.
ACTION
Use valid file name.
Check value.
Verify that file type is
appropriate.
ROUTINE
1MS
LFM
LFM
1) Define the file use-
ing a unique name, or
2) Return the file and
reattach it in a differ
ent mode.
Correct the parameter
and retry.
Correct command in error.
Verify CIO function code
being used. Lower the
access level of your
job, if possible, or
raise the access level
of the file.
Reissue the request with
the correct
identification code.
Verify that file being
packed is not assigned
to an interactive
terminal.
Inform software support.
Analyze job output and
dumps to determine the
cause of the error.
PFM
FCOPY
1AJ
1MS
PACK
1AJ
1AJ
INCORRECT JOB ORIGIN TYPE FOR TRMDEF. The TRMDEF command was entered from a job
that was not of an interactive origin.
Retry from an
interactive origin job
or remove the TRMDEF
command.
INCORRECT JSN ARGUMENT.
INCORRECT LABEL TYPE, filename AT address.
INCORRECT LINE LENGTH.
The JSN specified is not four characters.
Incorrect label type. The only valid label
types are ANSI labeled and nonstandard
labeled.
Either of the following out of bounds
conditions exists with respect to the Ix,
Nx, Ox, and H parameters of the L072
command.
- (0x+Nx).GT.H
- (Ix+Nx).GT.(buffer length) where 1 .LE.
x .LE. b
Fix JSN and retry.
Use correct label type.
Correct parameter and
retry.
CLASS
1MT
L072
INCORRECT LIST OPTION. The list option specified in a CATLIST
command is incorrect.
Refer to description of
CATLIST command for
valid List options.
CATLIST
60459680 H B - 3 3 |
![](asset-276.png)
MESSAGE
INCORRECT LOAD ADDRESS.
INCORRECT LOCAL FILE NAME.
INCORRECT MODIFICATION OF filename AT address.
INCORRECT NOISE SIZE ON filenam.
INCORRECT -NR- PARAMETER.
INCORRECT OP PARAMETER - op
INCORRECT */* OPTION.
INCORRECT OPTION ARGUMENT.
INCORRECT OUTPUT FILENAME.
INCORRECT PARAMETER.
INCORRECT PARAMETER.
INCORRECT PARAMETER.
-INCORRECT PARAMETER.
INCORRECT PARAMETER LENGTH OR SEPARATOR.
INCORRECT QUEUE SPECIFIED.
INCORRECT QUEUE TYPE.
INCORRECT -R/NR- PARAMETER.
INCORRECT REPLY LIMIT REACHED.
INCORRECT REQUEST.
INCORRECT RESOURCE COUNT.
SIGNIFICANCE
The load address is less than 2.
The FN=lfn parameter on the QGET command
contains an error.
lfn The local file name for the
queued output.
Either you have attempted to shorten a
modify-only file or the file cannot be
modified at all.
Noise size on S, L, or F format tape does
not meet copy requirements.
You specified something other than NR to
inhibit the rewinding of the file.
You specified an incorrect OP=op
parameter.
An incorrect command option followed the
start.
Command contains an incorrect argument for
an option.
Command contained filename that was more
than seven characters long, or contained a
non-alphanumeric character.
One of the following.
- Parameter value is out of range.
- You specified a parameter that cannot be
included on the command.
- Command is incorrect.
You specified an incorrect parameter on the
current command.
The parameter in the entry was invalid or
too long.
The S or L parameter was entered as zero on
the L072 command.
You specified a parameter longer than seven
characters or used an incorrect separator.
You specified an incorrect disposition code.
System error.
You entered a value other than R or NR for
the second parameter of the BLOCK command.
The number of consecutive incorrect entries
exceeds the limit.
A program issued a request (such as a
MEMORY request) in which the request word
was outside the job's field length.
Total resource demand exceeds maximum
allowed, as defined by installation
parameter MAXD (defined in RESEX).
ACTION
Specify larger load
address and retry.
Correct the parameter.
Determine whether file
can be modified.
For copy, ensure that
noise size on input file
is greater than or equal
to that of the output
file. For COPYB,
correct noise size to
meet requirements and
retry (noise size of 8
for 7-track or 6 for
9-track tapes is
required for X and SI
format conversions).
Correct the NOTE command
and retry.
Correct the
OP=op parameter.
Correct the option and
retry.
Check command
description and retry.
Correct filename and
r e t r y.
Ensure accuracy of
command.
Ensure the accuracy of
your parameter.
Correct the parameter
and retry.
Retry command, adding a
correct S or L parameter
value.
Ensure the accuracy of
your parameter
specifications.
Retry with valid
disposition code.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Correct the R/NR
parameter and resubmit.
None.
If the message occurs
after you entered a user
break 2, ignore the
message. If not,
correct the program.
Reduce RESOURC demands.
1AJ
QGET
1MS
COPYB
MFILES
CLASS
CLASS
IAFEX
LISTL8
CATLIST
CONTROL
L072
CONTROL
SUBMIT
ENQUIRE
NOTE
RECOVER
1MA
B-34 60459680 H
![](asset-277.png)
MESSAGE
INCORRECT SERVICE CLASS.
INCORRECT SORT PARAMETER.
INCORRECT SYNTAX,
cmd INCORRECT TERMINAL CLASS
INCORRECT TERMINAL REQUEST.
INCORRECT TERMINAL TYPE FOR TRMDEF.
INCORRECT USER.
INCORRECT USER ACCESS.
INCORRECT USER COMMAND.
cmd INCORRECT VALUE
INCORRECTLY-FORMATTED LIBRARY, Iname.
INCORRECTLY FORMATTED TRMDEF data.
INDEX TOO LARGE ON OPEN, FILE filename AT
address.
INITIAL COMMAND LIMIT.
INITIAL MESSAGE LIMIT.
INPUT DISCARDED
.INPUT FILE ERROR.
INPUT FILE IN NO RERUN STATUS.
INPUT FILE IN RERUN STATUS.
INPUT FILE NOT FOUND.
SIGNIFICANCE
You entered an invalid service class for
the SC parameter of the CLASS command.
Either you are not validated to use the
service class you specified, or the service
class is not valid for the origin type of
the job you specified in the JSN parameter.
An incorrect parameter has been specified
on the SORT command.
A required parameter is missing, parameters
are given in the wrong order, or an
incorrect separator has been encountered.
The value you specified in the terminal
definition command cmd is not valid for
your terminal.
Informative message indicating that an
unidentified request was encountered, or
auto recall was not requested by the
calling job.
The TRMDEF command was entered from a
terminal that was not a network terminal.
Four unsuccessful attempts at login were
made after which the terminal was discon
nected from the system.
You tried to access a subsystem for
which you do not have authorization.
The user name or password could not be
validated, or a secondary USER command to a
different family was attempted and you are
not validated to change families.
You specified an invalid value in the
terminal definition command cmd.
There is an error in the ULIB record of
file Iname. The system does not create a
directory for this file.
A terminal definition parameter specified
on the TRMDEF command or via the 0016
control byte was not correct.
For an OPEN function, the random index
length exceeded the index buffer size.
The number of commands processed by the job
exceeded the limit for which you are
validated. At this point, an additional
eight commands are allowed for error
processing.
MONITOR has detected that the message limit
for the job has expired.
The network has discarded the last input
from your terminal. May be caused by
entering a user break or interactive status
command while awaiting a response to a
previous user break or interactive status
command.
An error on the input file was encountered
during the unpack operation.
Informative message.
Informative message.
The input file must be either a local or an
attached direct access file.
ACTION ROUTINE
Correct the service CLASS
class entry and resubmit.
C o n s u l t d e s c r i p t i o n o f S O R T
SORT command for valid
parameters.
Check proper command IEDIT
format and reenter the
command.
Choose an appropriate CCP
value (refer to appendix
J).
Correct erroneous TLX
request, or rewrite
program to use recall.
Retry from a network TRMDEF
terminal.
Obtain accurate login NVF
information before
attempting to log in.
Inform site analyst if
problem persists.
Check to see if you
are authorized to use
the subsystem you
specified. (Refer to
LIMITS command"*.
Verify that user name
and password are valid.
Choose a valid value
(refer to appendix J).
EXINIT
EXSLV
CPM
Correct the error in the LIBRARY
ULIB record of Iname.
Ensure accuracy of entry
and retry.
S e t E P b i t i n F E T + 1 t o 1 M S
get error status without
abort or increase index
buffer size.
Split the job into two 1AJ
or more jobs, reduce the
number of commands in
the job, or request a
larger command limit
from site personnel.
Decrease job size or 1AJ
increase limit.
Reenter your last input. CCP
Correct and retry. L07Z
None. QFM
None. QFM
Create the file and FCOPY
retry.
60459680 H B-35
![](asset-278.png)
MESSAGE
INPUT LOST, REENTER LAST LINE.
•INPUT* NOT ASSIGNED TO TERMINAL.
INSERTED LINES OVERLAP EXISTING LINES, AT
nnnnn. ENTER Y TO CONTINUE OR N TO STOP.
INSUFFICIENT RESOURCES ON SYSTEM.
INSUFFICIENT RESOURCES ... RE-ENTER
INSUFFICIENT STORAGE FOR LIBRARY GENERATION.
INTERACTIVE JOB STEP, DUMP DISABLED.
INVAILD APPLICATION, TRY AGAIN.
INVALID DEFAULT CHARGE
INVALID DISPLAY DATA FROM SCOPE 2
INVALID ENTRY.
INVALID FILE STATUS.
INVALID OPTION X.
INVALID USER ACCESS.
pfn IS DIRECT ACCESS.
filename IS EXECUTE ONLY.
pfn IS INDIRECT ACCESS.
filename IS READ ONLY.
ITEMIZE COMPLETE.
ITEMIZING xxxx
SIGNIFICANCE
Your last line of input was lost due to an
IAF internal error.
You entered the PASSWOR command from an
input file when password randomization is
required. If password randomization is
required, you must enter the PASSWOR
command as a direct response to a system
prompt.
The MOVE, DUP, or READ conmand cannot be
completed without line number overlap
processing. The processing will begin at
line nnnnn.
Resource demand exceeds the number of units
physically available on the system.
The system has insufficient resources to
handle the current request.
Additional memory is required for the
LIBGEN command.
You entered a memory dump command directly
from a terminal. This is not allowed.
The requested application is unknown or
unavailable to the user.
An informative message indicating that you
entered a CHARGE(*) command but that your
default charge information is not valid.
Since you are not required to enter a
charge comnunand, your job is not aborted
and you may continue processing.
A hardware or system error occurred.
You entered something other than GO,
RELIST, or a valid job sequence name.
You specified a file status in a SETFS
command other than AD or NAD.
The option specified is not defined for
ENQUIRE.
You attempted to use a command that can be
used only in interactive jobs and your job
is not interactive.
An indirect access file operation was
attempted on a direct access file.
The specified local file cannot be accessed
by SAVE, REPLACE, APPEND or DEFINE since it
is an execute-only file.
A direct access file operation was
attempted on an indirect access file.
filename was not processed because the user
was not permitted to write to it.
Specified processing is finished.
Record xxxx is being processed.
ACTION
Reenter the last line.
If the error recurs,
inform site analyst or
customer engineer.
Resumbit the PASSWOR
command in response to
the system prompt.
Type Y to complete the
edit command or type N
to terminate the edit
command.
Reduce resource demand.
Retry the request.
Increase field length
and retry.
To get a memory dump
from an interactive job,
place the dump command
in a procedure or in an
ENTER command.
Check the accuracy of
the entry. If problems
persist, contact
installation personal
concerning validations.
Contact your site
administration to check
on the validity of
information in your user
validation file.
Reenter the command. If
the same message is
returned, inform the
site analyst.
Enter GO, RELIST, or a
valid job sequence name.
Retry with a proper file
status parameter.
Check parameters on
command and retry.
None.
Use the appropriate
direct access file
request.
None.
Use the appropriate
indirect access file
request.
Correct and retry.
None
None.
ROUTINE
IAFEX
MODVAL
RESEX
HELL07
LIBGEN
1AJ
NVF
MODVAL
QUEUE7
RECOVER
MFILES
ENQUIRE
PFM
PFM
MFILES
ITEMIZE
ITEMIZE
8-36 60459680 H
![](asset-279.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
ITF, ACN acn, APPLICATION LINKAGE ERROR WITH
HOST pid.
CN acn, REASON CODE = nn - xxxx.
The host physical identifier pid has detected Inform site analyst,
one of the following anomalies on the
application connection number acn:
ITF
y$p*3RSy
ITF, ACN acn, APPLICATION LINKAGE REJECTED BY
HOST pid
ITF, ACN acn, RETRANSMITTING TO HOST pid.
ITF, ACN acn, TRANSMISSION RESUMED TO HOST
pid.
ITF, CONNECTED TO HOST pid ON ACN c/TCN yy.
ITF, COULD NOT CONNECT TO HOST pid.
ITF, REASON CODE = nn - xxxx.
ITF, COULD NOT CONNECT TO RHF SUBSYSTEM.
ITF, REASON CODE = nn - xxxx.
01 UNRECOGNIZED COMMAND.
02 INVALID Q UA LI FIER.
03 INVALID ATTRIBUTE.
04 REQUIRED ATTRIBUTE MISSING.
05 CONNECTION TIMED OUT.
06 FC/BRK RECEIVED.
07 FC/NAK RETRY COUNT EXECEEDED.
08 BLOCKS OUT OF SEQUENCE.
09 UNEXPECTED COMMAND.
Indicates ITFS application on remote host
physical identifier has rejected linkage
request.
acn Application connection number
pid Physical identifier
The RHF subsystem has repeatedly rejected
the transmission of a network block by ITF.
acn Application connection number
pid Physical identifier
ITF has successfully transmitted a network
block which had been previously rejected by
the RHF subsystem.
acn Application connection number
pid Physical identifier
Indicates state of terminal connection,
pid is remote host, c is RHF connection
number, and yy is virtual connection number.
ITF was not able to establish an RHF
connection to remote host pid due to one of
the following conditions:
nn xxxx
01 LID UNKNOWN TO SUBSYSTEM.
02 REJECTED BY HOST.
03 NETWORK RESOURCE LIMIT.
04 SERIVCER UNAVAILABLE.
05 PATH DISABLED OR DOWN.
06 HOST NOT RESPONDING,
other CONNECTION REJECT.
ITF was not able to establish
communications with the RHF subsystem due
to one of the following conditions:
If problem persists,
inform site analyst.
If problem persists,
inform site analyst.
None.
None.
If problem persists,
contact local operator
to ensure RHF subsystem
and the LCN are
operational and/or
operator for remote host
pid to ensure RHF
software and hardwre as
well as the ITF servicer
application are
operational there.
Contact local operator.
ITF
ITF
ITF
nn xxxx
ITF, HOST pid HAS RESPONDED.
ITF, NAM NETWORK IDLEDOWN IN PROGRESS.
ITF, RHF NETWORK IDLEDOWN IN PROGRESS.
ITF, RHF NETWORK SHUTDOWN.
ITF, Tnnnn, TERMINAL CONNECTION ABORTED BY
HOST pid.
ITF, Tnnnn, TERMINAL CONNECTION ABORTED TO
HOST pid.
ITF, Tnnnn, TERMINAL CONNECTION ENDED BY
HOST pid.
ITF, Tnnnn, TERMINAL CONNECTION ENDED TO
HOST pid.
ITF, Tnnnn, TERMINAL CONNECTION REJECTED BY
HOST pid.
01 SUBSYSTEM UNAVAILABLE.
02 ITF UNAVAILABLE.
0 3 I T F D I SA BL ED
other NETON FAILURE.
Indicates state of connection to host pid.
The operator has initiated subsystem
idledown. ITF will not accept any new
connections.
The operator has initiated subsystem
idledown. ITF will not accept any new
connections.
The subsystem is terminating immediately.
All connections are aborted.
Indicates state of terminal connection.
Indicates state of terminal connection.
Indicates state of terminal connection.
Indicates state of terminal connection.
Indicates state of terminal connection.
None.
None.
None.
None.
TTF
ITF
ITF
ITF
ITF
ITF
ITF
60459680 H B - 3 7 I
![](asset-27a.png)
MESSAGE
ITF, TERMINAL TIMEOUT.
ITF, TERMINAL WILL DISCONNECT IN ONE MINUTE.
ITF, WAITING FOR HOST pid TO RESPOND.
.IX OR OX NOT DEFINED.
JOB ACTIVE.
JOB ALREADY WAITING ON SERVICE CLASS.
JOB CANNOT ACCESS FILE.
JOB CARD ERROR (jobname)
JOB COMMAND ERROR.
JOB DETACHED, JSN=oldjsn
JSN: newjsn, NAMIAF.
JOB DROP IN PROCESS
JOB HUNG IN AUTO RECALL.
JOB HUNG IN AUTORECALL
JOB IN NORERUN STATE ON RECOVERY.
JOB NOT DETACHED.
JOB NOT FOUND.
JOB NOT RECOVERABLE.
JOB NOT RERUN.
JOB REPRIEVED.
JOB RERUN.
JOB STEP ABORT.
JOB STEP EXCEEDS ACCOUNT BLOCK.
JOB STEP LIMIT.
SIGNIFICANCE
Terminal inactivity forced disconnection.
Due to lack of activity, your terminal will
be disconnected.
Indicates state of connection to host pid.
The Ix or Ox parameter was not specified in
conjunction with the Nx parameter on an
L072 command.
The system is unable to process the command
because the previous command has not
completed.
Change cannot be made because the job is
already waiting for a CLASS command in the
job to complete.
The permanent file being processed has
either an access level or access categories
that are not valid for your job.
The Job command of a routed job contains an
error.
jobname First 20 characters
of the job command
in error.
The Job command on the file being submitted
is in err o r.
Informative message. The system creates
the new JSN newjsn for your current
terminal session.
You have issued a DROP,J request which is
being processed.
System error.
System detected an autorecall call to an
incomplete word and there was no activity
to make the word complete.
Identifies a job recovered on level 0 or
level 3 deadstart that was aborted because
it was in a no-rerun node (due to NORERUN
command or macro).
Condition encountered during terminal job
recovery attempt. The JSN specified is
not associated with a job.
Condition encountered during terminal job
recovery attempt.
Condition encountered during terminal job
recovery attempt.
The system was unable to successfully rerun
a job because of a mass storage read error
or because the QFT is full.
The job has been successfully reprieved.
The job has been terminated and requeued
for input.
The job step was aborted due to mass
storage device error.
You tried to set your job step limit to a
value greater than your account block limit
or tried to set your account block limit to
a value less than your job step limit.
The monitor detected the expiration of the
job step SRU limit.
ACTION ROUTINE
None. ITF
Resume activity or else ITF
terminal is disconnected.
None. ITF
Check the description of L072
the L072 command in
section 9.
Retry when current
operation is complete.
Wait and retry later.
None. Your job cannot
access the file.
Correct the Job command
and retry.
Compare the Job command
in error with the Job
command description in
section 7. Also check
your validation limits.
No action required.
Wait for the user prompt.
Inform site analyst.
Correct the program to
issue a correct recall
request.
Refer to the NORERUN
command or macro
description.
Retry command.
Recheck the JSN.
Retry command.
Retry command.
Recheck the JSN.
Resubmit the job to the
system.
None.
None.
Retry the job step. If
the problem recurs,
inform site analyst.
Check values on SETJSL
and SETASL commands.
Reset job step limit
with SETJSL command or
macro and retry. If job
step SRU limit is set at
maximum, request
increased SRU validation.
CLASS
DSP
1AJ
IAFEX
HELL07
RECLAIM
1AJ
1AJ
IAFEX
IAFEX
IAFEX
1AJ
1AJ
1AJ
1AJ
.rrfS^K
1AJ
B-38 60459680 H
>^S\
![](asset-27b.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
/k'kto**v
y^^N
JOBNAME IS jsn
JSN MORE THAN FOUR CHARACTERS
JSN NOT FOUND.
JSN OR UJN MUST BE SPECIFIED.
LABEL CONTENT ERROR, filename AT address.
LABEL MISSING, filename AT address.
LABEL NOT EXPIRED.
LABEL PARAMETER ERROR ON OPEN, filename
AT address.
LDD - ARGUMENT ERROR - address.
LDD - DEVICE ERROR - FILENAM AT address.
LDD - I/O SEQUENCE ERROR.
LDI ID AND FM/UN CONFLICT.
LDQ - ARGUMENT ERROR - address.
LDQ - DEVICE ERROR - FILENAM AT address.
LDQ - I/O SEQUENCE ERROR.
LDR ERROR.
LFM ERROR.
LFM INCORRECT REQUEST.
LIBEDIT ARGUMENT ERROR(S).
LIBGEN ARGUMENT ERROR.
LIBGEN FILE NAME CONFLICT.
60459680 H
An LDI command queued a file for input.
The entered job has specified job sequence
name.
You specified a job sequence name (JSN)
of more than four characters.
For the JSN parameter of the CLASS command,
you specified a JSN that is not in the
system, or that does no belong to you.
The JSN or the UJN must be specified within
the command parameters.
A block read was the correct size for a
label but one or more required fields (such
as the label name) were incorrect.
During a read operation, a required label
was missing.
You attempted to write on a tape with an
unexpired label.
Label fields did not match on open
request. An additional message,
FIELD BEGINNING AT addr NO COMPARE,
specifying the decimal character position
in HDR1 of the first field that did not
compare correctly, is also issued.
One of the following conditions is true:
- FET address is less than 2.
- FET address is greater than FL-2.
- Auto recall was not set when LDD was
called.
address Parameter block address.
An unrecovered device error occured on file
filename.
I/O was attempted on a file that is
currently active on another I/O request.
Both the ID and FM/UN parameters were
specified on the command. ID may not be
specified with FM or UN.
The FET address is less than 2 or greater
than FL-4.
An unrecovered device error occured on file
filename.
I/O was attempted on a file that is
currently active on another I/O request.
Issued before one of the following errors.
- OVERLAY NOT FOUND IN LIBRARY.
- ARGUMENT ERROR.
LFM detected an error in the request. See
other error messages in dayfile for more
information.
One of the following:
- The function detected was not recognized
as a valid LFM function.
- An LFM function was issued without the
auto recall bit set.
The LIBEDIT command contains an incorrect
parameter.
An incorrect parameter was used on the
LIBGEN command.
The LIBGEN command named the same file as
the input file and as the output file.
None.
Correct the JSN=jsn
parameter.
Check to see if you
entered the correct JSN.
Specify the JSN or the
UJN and retry the
command.
Use LISTLB command to
obtain label data and
retry.
Ensure that tape has
label.
If current contents of
tape can be sacrificed,
have operator blank
label tape. Otherwise,
wait until label has
expired.
Use LISTLB command to
obtain label data.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Contact a customer
engineer.
Check program for
concurrent I/O.
Correct and retry.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Contact a customer
engineer.
Check program for
concurrent I/O.
Correct error and retry.
Ensure that a valid LFM
request is being made.
Verify that a valid LFM
request is being used.
Check the LIBEDIT
command description for
the correct format and
retry.
Check the format of the
LIBGEN command and retry.
Change the input file or
output file name.
LDI
QGET
DROP
CLASS
1MT
1MT
1MT
1MT
FDL
FOL
FDL
FDL
FDL
LDR
LFM
LFM
LI8GEN
LIBGEN
8 - 3 9 I
![](asset-27c.png)
MESSAGE
LIBRARY FILE NOT GENERATED.
LIBRARY FILE NOT ON MASS STORAGE.
LIBRARY GENERATION COMPLETE.
LIBRARY GENERATION FILE EMPTY.
LIBRARY NOT FOUND, Iname.
LID NOT FOUND
LINE LIMIT EXCEEDED.
LINE NUM8ER INCREMENT ERROR
LINE NUMBER LIMIT EXCEEDED.
LINE NUMBER LIMIT EXCEEDED
LINE NUMBER OVERLAP ERROR
LINE RANGE ERROR
LINE TERMINATORS NOT USED ON A STRANGER
TAPE.
LINE lineno TRUNCATED
LINE WAS DISCONNECTED WHILE LOANED.
nnnn LINE(S) TRUNCATED.
nnn LINES TRUNCATED.
xxxxxx LINES TRUNCATED.
nnnnn LINES TRUNCATED ON FILE filename
LIST OF FILES LENGTH TOO LONG OR ZERO.
B-40
SIGNIFICANCE
The file to be processed did not contain
any of the proper record types.
An attempt was made to generate a user
library onto a file not assigned to mass
storage.
Message issued when generation of a library
is completed.
The file to be processed is empty.
User library Iname is not a local file.
In a LISTLID command, you extended a LID
that either does not exist or that the site
had defined as not listable through LISTLID.
Your job generated more lines of print than
that for which you are authorized. If you
do not fill all pages, the system still
assesses a minimum number of lines per page.
Line number increment specified is less
than one or greater than 4095.
The line number encountered or required
during a resequencing (RESEQ) operation
exceeded 99999.
An attempt to move, duplicate, or read a
group of lines in the edit file required a
line number greater than 99999 to be
assigned.
Two or more line ranges have at least one
line number in common.
An incorrect line number was specified in a
line range.
A line terminator parameter was specified
for a file residing on a stranger tape.
The indicated line of the file was
truncated during RESEQ processing.
The line connection to your secondary
application was broken.
nnnn Lines were truncated because they were
longer than 150 characters.
The processing of a SECHDR command caused
nnn lines of your file to be truncated by
one character from the right.
1 or more lines were truncated when they
were found to be longer than the fixed
length line length (FL parameter) or an
FCOPY to a stranger tape.
nnnnn lines on file filename have been
truncated.
The list of files exceeds the length of the
local FNT, starts or extends beyond the
job's field length, or has a length of zero.
ACTION
Check for proper source
file.
Choose an output file
that resides on mass
storage.
None.
Verify that file is
local to job and
contains data.
Make file Iname local.
Check to see that you
entered the correct LID.
Ensure that your print
files do not contain
undesired line feeds and
page ejects (refer to
appendix H). If
necessary, request a
higher limit from your
site.
Reenter command with
correct line number
increment.
Examine program and
correct line number in
error.
Resequence the file
(using RESEQ command)
and reenter the command.
Reenter command with
non-overlapping tine
ranges.
Reenter command with
correct line range.
Remove the line
terminator parameter and
retry.
Check file to determine
whether relevant data
was lost.
Enter another APPSW
command to reestablish
the connection.
Determine if relevant
data was tost in the
truncation. If
possible, split the too
Long lines and repeat
the copy operation.
None.
If data lost was
significant, retry
command with a larger
value for the FL
parameter.
Inform site analyst. If
many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITIALIZE,
and full PFLOAD on the
device.
Contact software support.
ROUTINE
LIBGEN
LIBGEN
LIBGEN
LIBGEN
LIBRARY
LISTLID
QAP
IEDIT
IEDIT
IEDIT
FCOPY
RESEQ
COPYC
SECHDR
FCOPY
IEDIT
1AJ
60459680 H
![](asset-27d.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
r
LIST OPTION ERROR.
LISTLB ABORT.
LISTLB COMPLETE.
LOADER MISSING.
LOCAL FILE xxxxxxx ALREADY EXISTS.
LOCAL FILE LIMIT.
LOG - PPU BUSY.
LOST 7000 COMMUNICATIONS
.L072 COMPLETE.
LPest, CHcc Acount INCOMPLETE TRANSFER.
LPest, CHcc CONTROLLER HUNG BUSY.
LPest, CHcc Fcode FUNCTION TIMEOUT.
LPest, CHcc Fcode REJ Pdriver,Cconvert,Eequip.
LPest, CHcc TURNED OFF.
LPest, CHcc RESERVED.
LRest, CHcc Acount INCOMPLETE TRANSFER.
LRest, CHcc CONTROLLER HUNG BUSY.
LRest, CHcc Fcode FUNCTION TIMEOUT.
LRest, CHcc Fcode REJ
Pdriver,Cconvert,Eequip.
LRest, CHcc TURNED OFF.
LRest, CHcc PRINT ERROR LIMIT EXCEEDED.
LRest, CHcc RESERVED.
LRest, nnnn PRINT ERRORS.
LRC ERROR.
LSest, CHcc Acount INCOMPLETE TRANSFER.
LSest, CHcc CONTROLLER HUNG BUSY.
LSest, CHcc Fcode FUNCTION TIMEOUT.
LSest, CHcc Fcode REJ
Pdriver,Cconvert,Eequip.
LSest, CHcc TURNED OFF.
LSest, CHcc Emmmm PFC ERROR.
LSest, CHcc PRINT ERROR LIMIT EXCEEDED.
LSest, CHcc RESERVED.
LSest, nnnn PRINT ERRORS.
An incorrect list option was specified for
the *LO* parameter in the LIBEDIT command.
A fatal error has occurred while processing
the LISTLB command.
Informative message indicating that the
LISTLB operation has finished.
1AJ could not find BEGIN or LDR=.
The file could not be attached because a
local file already exists with the
name xxxxxxx.
The job tried to create too many local
files.
DSD c a nno t proc e ss a n entr y into t he
errorlog at this time.
Communications between NOS and the SCOPE 2
system have been temporarily lost.
Informative message indicating that the
program has completed processing.
Line printer messages. Refer to EQest...
The line printer is reserved and cannot be
connected on channel cc.
est EST ordinal of line printer
cc Channel number
580-12 line printer messages. Refer to
EQest...
Line printer message. Refer to EQest...
The 580-12 line printer is reserved and
cannot be connected on channel cc.
est EST ordinal of line printer
cc Channel number.
Line printer message. Refer to EQest...
The longitudinal redundancy check character
was read incorrectly (9-track NRZI). The
dayfile message STATUS ERROR, filename AT
ad d re s s p r e c e d e s t h i s m e s s a g e a n d s p e c i fi e s
the file (filename) and the address.
580-16 line printer messages. Refer to
EQest...
5 8 0 - 1 6 l i n e p r i n t e r m e s s a g e . R e f e r t o
EQest...
Line printer message. Refer to EQest...
The 580-16 line printer is reserved and
can not b e c o nn e ct e d t o c ha n ne l cc .
est EST ordinal of line printer
cc Channel number.
Line printer message. Refer to EQest...
Change the *L0*
parameter to specify
only valid options.
Refer to dayfile for
cause of problem.
None.
Inform software support.
Use a different name
in the request or
return the local file.
Reduce local file usage.
Erase command and
retry. Inform site
analyst if the probelm
persists.
Enter a RESUME directive
to attempt recovery.
None.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
Retry or inform site
analyst.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
LIBEDIT
LISTLB
LISTLB
1AJ
QGET
1AJ
DSD
HELL07
L072
110
QAP
110
110
QAP
QAP
110
QAP
1MT
110
QAP
110
QAP
QAP
110
QAP
60459680 H B-41
![](asset-27e.png)
MESSAGE
LTest, CHcc Acount INCOMPLETE TRANSFER.
LTest, CHcc CONTROLLER HUNG BUSY.
LTest, CHcc Fcode FUNCTION TIMEOUT.
LTest, CHcc Fcode REJ
Pdriver,Cconvert,Eequi p.
LTest, CHcc TURNED OFF.
LTest, CHcc Eequip PFC ERROR.
LTest, CHcc PRINT ERROR LIMIT EXCEEDED.
LTest, CHcc RESERVED.
LTest, nnnn PRINT ERRORS.
M.T. NOT AVAILABLE ON FILE filename AT
address.
MAGNETIC TAPE SUBSYSTEM NOT ACTIVE.
MAINFRAME=
MAINFRAME ID NOT IN ID TABLE
MAINFRAME UNAVAILABLE
MARGINALLY WRITTEN TAPE, filename AT address.
MASS STORAGE DIRECTORY NOT WRITTEN.
MASS STORAGE ERROR.
MASS STORAGE ERROR.
MASS STORAGE LIMIT.
MAXIMUM FL ENCOUNTERED - JOB LIST
INCOMPLETE.
MEMORY OVERFLOW.
SIGNIFICANCE
580-20 line printer messages. Refer to
EQest...
ACTION
Inform customer engineer.
580-20 line printer message. Refer to
EQest...
Line printer message. Refer to EQest...
The 580-20 line printer is reserved and
cannot be connected to channel cc.
est EST ordinal of line printer
cc Channel number.
Line printer message. Refer to EQest...
The magnetic tape executive is not
executing.
One of the following occurred during a
magnetic tape request.
- There was no UDT address in the FST.
- The UDT address in the FST was incorrect.
- The MAG subsystem was not present.
Prompt requesting the LID of the SCOPE 2
mainframe you want to access.
The mainframe you requested is not
available.
The mainframe you specified is not
currently available.
Some or all of the previous good blocks
used to create the recovery block ID
window cannot be read with error
correction enabled during repositioning
of the tape for write recovery. The
tape is marginal and will possibly fail
on a read. The job will terminate to
prevent the possibility of bad data in
t h e li b r a ry.
On a GTR command, you have requested that a
mass storage directory record be written on
a nonmass storage file.
An error was encountered in reading a
portion of the permanent file catalog or
permit information (error log and dayfile
message). This indicates a hardware
problem with a disk pack or disk drive.
Job was terminated without exit processing.
You have exceeded your mass storage
validation limits.
The system has found too many recoverable
jobs.
Insufficient field length has been
specified for KRONREF to execute.
ROUTINE
110
QAP
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
110
QAP
QAP
110
Inform customer engineer. QAP
Inform site operator. 1MS
Bring up MAGNET.
Contact site operator LFM
to have MAGNET RESEX
brought up. Otherwise
contact central
software support.
Enter a valid SCOPE 2
mainframe LID.
Enter an alternate
mainframe LID, or type
END to terminate the
HELL07 session.
Enter a QUEUE7, ID command
to list PIDs currently,
active, then reenter the
command with an active
mainframe PID.
Clean the tape drive. Have
the tape cleaned and
certified or use a new tape.
HELL07
HELL07
QUEUE7
1MT
Ensure that file resides
on mass storage.
Inform site analyst. If
many of these errors occur,
the site anlayst should
perform a full PFDUMP, total
INITIALIZE, and full PFLOAD
on the device.
Resubmit job.
Return all unneeded
files and try again. If
the message occurs
again, your validation
limit is too low to
allow the operation you
are attempting.
Proceed as normal or
wait for other jobs to
time out and try again.
Increase field length
with RFL command and
retry.
1AJ
RECLAIM
RECOVER
B-42 60459680 H
![](asset-27f.png)
MESSAGE SIGNIFICANCE ACTION
MESSAGE LIMIT.
/0H$*\
09^
MFL LESS THAN EXTENDED MEMORY MINIMUM CM FL.
MFL REQUEST TOO SMALL, MINIMUM USED.
MFLINK - APPLICATION CONNECTION BROKEN.
MFLINK - APPLICATION CONNECTION TIMEOUT.
MFLINK - APPLICATION DISABLED.
MFLINK - BLOCK TOO LARGE.
MFLINK - CANNOT READ FROM filename.
MFLINK - CANNOT WRITE ON filename.
MFLINK - CONNECTING TO lid.
MFLINK - CONNECTION REJECTED BY REMOTE HOST.
MFLINK - CONTINUATION BLOCK DID NOT FOLLOW.
MFLINK - ERR/LGL RECEIVED FROM SUBSYSTEM.
MFLINK - FC/8RK RECEIVED RC=rc.
MFLINK - FC/NAK RETRY LIMIT.
MFLINK - FILE RETRANSMIT REQUESTED.
MFLINK - INCORRECT LID.
MFLINK - INVALID ACCESS VALIDATION.
MFLINK - INVALID COMMAND cmd.
MFLINK - INVALID CONTROL STATEMENT.
MFLINK - INVALID DATA DECLARATION.
MFLINK - INVALID DIRECTIVE FILE NAME.
The number of messages issued by the job
has exceeded the limit for which you are
authorized. Message functions issued by
compilers or applications that run in the
job's field length are also counted as job
dayfile messages and thus are subject to
your dayfile message limit.
To use extended memory you must have a
required minimum amount of central memory
field length. This message indicates that
you do not have the required central memory
field length.
MFL request was less than CONTROL'S RFL=
value. CONTROL'S RFL= value is used for
this MFL request, thus allowing further MFL
requests.
The connection with the remote host was
broken by the network or remote host.
The remote host did not respond in the
allotted time.
The operator has disabled the PTF for the
network subsystem (RHF or NAM).
The remote host or the network sent a block
or message that was too large.
The file filename does not have read
permission. The file type is not
supported by MFLINK, or the file
does not exist.
The file filename does not have write
permission, or the file type is not
supported by MFLINK.
Informative message. You are being
connected to the remote host you specified.
The remote host you specified has rejected
the connection.
The continuation block did not follow.
The network subsystem (RHF or NAM) detected
detected a logic error in communication.
The remote host has sent a break with
reason code re.
MFLINK was unable to transmit a block after
a system-defined number of attempts. Each
attempt was rejected by the network
subsystem (RHF or NAM).
The remote host has requested that the host
retransmit the file.
No mainframe in the network has the
specified logical identifier (LID), or the
LID specified contains an illegal character
or is not three characters long.
Your user name does not have required
validation to access the remote mainframe.
The system received an invalid command
(cmd) from the remote host or received a
command out of sequence.
You specified an incorrect parameter or
value on the MFLINK command,
command.
You specified an incorrect DD=dd parameter
on the MFLINK command.
You specified an incorrect I=dirfile
parameter on the MFLINK command.
Split job into two or 1AJ
more jobs and retry.
Increase central memory 1MA
field length.
Check the description of CONTROL
field length control in
section 3.
Inform site analyst. MFLINK
MFLINK retries unless
unless EP specified.
I n f o r m s i t e a n a l y s t . M F L I N K
MFLINK retries unless
EP specified.
Contact site operator. MFLINK
MFLINK retries unless
RT specified.
I n f o r m s i t e a n a l y s t . M F L I N K
Correct and resubmit. MFLINK
Correct and resubmit. MFLINK
None. MFLINK
Inform remote analyst. MFLINK
I n f o r m s i t e a n a l y s t . M F L I N K
I n f o r m s i t e a n a l y s t . M F L I N K
I n f o r m s i t e a n a l y s t . M F L I N K
I n f o r m s i t e a n a l y s t . M F L I N K
None. MFLINK
Use the LISTLID command MFLINK
to select the proper LID.
Contact your site MFLINK
administrator to get
the authorization.
I n f o r m s i t e a n a l y s t . M F L I N K
Correct the MFLINK
command and retry.
Correct the MFLINK
command and retry.
Correct the MFLINK
command and reissue.
/r^mp\
60459680 H B-43
![](asset-280.png)
MESSAGE
MFLINK - INVALID FILE NAME.
MFLINK - INVALID FILE TYPE.
MFLINK - INVALID PARAMETER xx FOR yy.
MFLINK - INVALID SUPERVISORY MESSAGE.
MFLINK - LID CURRENTLY UNAVAILABLE.
MFLINK - LID DISABLED.
MFLINK - LID NO LONGER AVAILABLE.
MFLINK - LID UNKNOWN TO SUBSYSTEM.
MFLINK - LOCAL NETWORK RESOURCE LIMIT.
MFLINK - NETON REJECT = re.
MFLINK - NETWORK SEQUENCE ERROR.
MFLINK - NETWORK SHUTDOWN.
MFLINK - NETXFR ERROR re - rejmess
SIGNIFICANCE
The file name you specified on the MFLINK
command is incorrect.
T h e fi l e y o u a t t e mp t e d t o t ra n s fe r t o a
remote host does not have a Local file type.
Informative message indicating the remote
host is sending protocol parameters which
ar e n ot su pp o r t e d b y t h e h o s t .
x x P r o t o c o l p a r a m e t e r.
yy Protocol command.
The remote host or the network sent an in
correct or unsupported supervisory message.
The network subsystem (RHF or NAM) is
unable to complete the connection to
the remote host.
The mainframe with the specified logical
identifier (LID) has been disabled by the
system.
The status of the LID has changed,
is no longer defined.
The lid
MFLINK - NETXFR STATUS = 0.
The network subsystem (RHF or NAM) has
rejected a connection request to the
specified LID even though the system LID
table indicates a network path is
available.
The network subsystem (RHF or NAM) is
temporarily unable to complete the con
nection to the requested remote host.
A system or network error occurred.
re reason code
A network message block was found for the
co nn ec ti o n be fo re t h e c o n n e c t i o n w a s
completed.
The operator has disabled the PTF
application in the network subsystem (RHF
or NAM). MFLINK terminates the network
connection.
An error occurred during file transfer,
re reason code
r e j m a s s r e j e c t m e s s a g e
re rejmess
03 CONNECTION BROKEN.
0 4 P RO T O C OL E R R O R.
05 TIMEOUT EXPIRED.
06 BLOCK NOT SENT.
07 TOO M A N Y TRANSFE R S
0 8 A C N O U T- O F - R A N G E .
09 CIO ERROR.
13 IDLEDOWN ERROR.
14 SHUTDOWN.
1 5 R H F I / O E R R O R
16 INCORRECT DEVICE.
17 CODE CONV N/A. (not avail)
18 CONTROL WORD ERROR.
19 INCORRECT DEVICE.
20 EMPTY FILE.
21 NAM INTERFACE ERR.
22 BLK NUM MISCOMPARE.
23 INCORRECT BLK SIZE.
25 BLOCK SEQUENCE ERR.
26 PRU BOUNDS ERROR.
27 INTRA-HOST PRU XFR.
2 8 E R RO R D UR I N G X F R .
2 9 A B L O UT O F R A N G E .
30 APPL NOT VALIDATED.
3 1 F I L E T Y P E E R R O R .
32 JOB ORIGIN ERROR.
A system or network error occurred.
ACTION ROUTINE
Correct the MFLINK MFLINK
command and retry.
Ensure that the file has MFLINK
the correct type and
retry.
Inform site analyst if MFLINK
p r o b l e m s r e s u l t .
Inform site analyst. MFLINK
Contact site operator. MFLINK
MFLDNK retries unless
RT specified.
Contact stie operator. MFLINK
MFLINK retries unless
RT specified.
C o n t a c t s i t e o p e r a t o r t o M F L I N K
d e fi ne t h e L I D a n d t r y
again. MFLINK retries
unless RT specified.
If problem persists, MFLINK
inform site analyst.
If problem persists, MFLINK
inform site analyst.
MFLINK retries unless
R T s p e c i fi e d .
Inform site analyst if MFLINK
problem persists..
Inform site analyst. MFLINK
Contact site operator. MFLINK
Inform site analyst if MFLINK
problem persists.
MFLINK retries unless
EP specified.
/**Si^v
I n f o r m s i t e a n a l y s t .
| B - 4 4 60459680 H
![](asset-281.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
r
MFLINK - NO CONNECTION RECEIVED.
MFLINK - NO LID SPECIFIED.
MFLINK - NO PATHS AVAILABLE TO LID.
MFLINK - NO REMOTE DIRECTIVES FOUND.
MFLINK - PROTOCOL ERROR IN xx.
MFLINK - RECOVERING ST lid.
MFLINK - REMOTE SUBSTEM RESOURCE LIMIT.
MFLINK - REMOTE SUBSYSTEM NOT RESPONDING.
MFLINK - SUBSYSTEM FULL.
MFLINK - SUBSYSTEM UNAVAILABLE.
The network failed to respond to the
application connection request before the
timeout period elapsed.
You failed to specify the ST=lid parameter
on the first MFLINK command of the MFLINK
session.
No paths are currently available to any
remote host with the specified LID through
either network subsystem (RHF or NAM).
The system is unable to find your MFLINK
directives.
MFLINK received an incorrect value for the
parameter xx.
An informative message. The system is
recovering the files for the mainframe
specified by lid.
The network or network subsystem (RHF or
NAM) on the remote host is temporarily
unable to complete the connection.
The network subsystem (RHF or NAM) cannot
establish communication with the remote
host.
The network subsystem (RHF or NAM) is
temporarily too busy to process your
request.
The network subsystem is temporarily too
busy to process your request.
Inform site analyst if
problem persists.
Correct the MFLINK
command and retry.
If message persists,
contact site operator.
MFLINK retries if RT
not specified.
Correct the MFLINK
command and reissue.
Inform site analyst if
problems result.
None.
Contact site operator.
MFLINK retries unless
RT specified.
MFLINK retries unless
RT is specified.
Contact site operator.
MFLINK retries unless
MFLINK
MFLINK
MFLINK
MFLINK
MFLINK
MFLINK
MFLINK
MFLINK
0$^\
MFLINK - UNKNOWN NETWORK INTERFACE TYPE.
MFLINK - WRONG REMOTE APPLICATION LEVEL.
MFLINK - TRANSFER IMPOSSIBLE TO ST Lid.
MFQUEUE - COMPLETE,
jsn = ROUTED FILE NAME.
MFQUEUE - CONTROL STATEMENT ERROR.
MFQUEUE - DUPLICATE PARAMETER.
MFQUEUE - DIRECTIVE EXCEEDS 256 CHARACTERS.
MFQUEUE - FIRST PARAMETER NOT VALID LFN.
MFQUEUE - ILLEGAL DC VALUE SPECIFIED.
MFQUEUE - ILLEGAL DD VALUE SPECIFIED.
MFQUEUE - ILLEGAL ST VALUE SPECIFIED.
MFQUEUE - INVALID DIRECTIVE NAME.
MFQUEUE - INVALID PARAMETER.
MFQUEUE - NO REMOTE DIRECTIVES FOUND.
MFQUEUE - ST PARAMETER MUST BE SPECIFIED.
An internal error was detected by MFLINK.
You entered an MFLINK command with ST=lid;
the transfer failed because MFLINK's
protocol version or level is incompatible
with the Permanent File Transfer Facitity
(PTF) software at the remote host.
Your job jsn was successfully routed.
MFQUEUE was unable to process the command.
Usually an invalid character or successive
separators is the cause of this problem.
Multiple occurrences are not allowed for
any of the MFQUEUE parameters.
The user supplied remote directive for
this command exceeds 256 characters.
The first parameter must be a valid file
name.
The DC=dc parameter is not supported.
Your DD=dd specification is not supported.
The logical identifier (LID) you specified
in the ST=lid parameter is not three
alphanumeric characters.
The directive file name must be a valid
file name.
You specified a parameter that is not
allowed on the MFQUEUE command.
The directive file was empty or you did not
supply remote directives via the PC
parameter.
The ST parameter is not optional. It must
appear on each MFQUEUE command.
Inform site analyst.
Inform site analyst.
None.
Correct the command.
Correct the command.
Correct the directive.
Correct the command.
Correct the command.
Correct the command.
Correct the command.
Correct the command.
Correct the command.
Fix the job so that the
directive file is not
empty.
Correct the command.
MFLINK
MFLINK
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
MFQUEUE
60459680 H B-45
![](asset-282.png)
MESSAGE
MFSTAT REJECTED REQUEST
SIGNIFICANCE
You did not enter the correct PID for the
SCOPE 2 mainframe.
MISSING DEMAND FILE ENTRY.
jsn MISSING RESOURCE.
MISSING VSN OR EQUIPMENT ASSIGNMENT.
MLTFPROC ABORT - INVALID SEQ ORD (nn).
MLTFPROC ABORT - SEQ ORD OUT OF RANGE (nn).
MODE ERROR.
MONITOR CALL ERROR, xxxx nnnnnnnnn.
MT,Ccc,Eec,Hhhhhhhhh,B.C. RESTART.
MT,Ccc,Eec,Hhhhhhhhh,BAD ERASE.
MT,Ccc,Eec,Khhhhhhhh,BAD RECOVERY-x.
MT,Ccc,Eec,Hhhhhhhhh,BLOCK TOO LARGE.
MT,Ccc,Eec,Hhhhhhhhh,BUSY.
MT,Ccc,Eec,Hhhhhhhhh,CHANNEL ILL.
MT,Ccc,Eec,Hhhhhhhhh,CON. REJ.
MT,Ccc,Eec,Hhhhhhhhh,CON. REJ. MDI.
MT,Ccc,Eec,Hhhhhhhhh,CON. REJ. OFF.
Dayfile message indicating a system problem.
The overcommitment algorithm was initiated
without a demand file entry having been
defined previously.
Dayfile message indicating that a system
problem occurred. The system expected but
did not find a resource unit assigned to
the job with job sequence name jsn. This
could occur if the MAG subsystem was
stopped while tapes were assigned.
Dayfile message indicating a system
malfunction (expected VSN or equipment
assignment was not found).
Fatal error. The sequencer-ordinal
parameter (SEQ=nn) on the MLTF procedure
call is defective, nn must be a number 1 to
63.
Fatal error. The sequencer-ordinal
parameter (SEQ=nn) on the MLTF procedure
call is defective, nn must be 1 to 63.
An arithmetic error, or CPU/CM parity error
has been encountered during processing of
job.
One of the following occurred during the
processing of an monitor request:
- The monitor request call was not
recognized by the system.
- Bad parameters were supplied in the
request.
- Incorrect user access was encountered.
- An incorrect request was included in the
request.
Magnetic tape controller controlware
restarted.
Error detected after an erase was attempted
to recover a write error.
A single block mispositioning error was
recovered by block ID recovery. If x is B,
the error was caused by backspacing the
tape too far; if x is F, the tape was not
backspaced far enough.
Data block is at least one byte longer than
length bbbb shown in third Line of message.
Unit was still busy after one second.
Channel is not accepting function for
status requests properly.
Connect reject; unable to connect to the '
unit.
Connect reject; unable to connect to unit
because of marginal detection indication
(thermal warning). Unit turned off.
Connect reject; unable to connect to unit.
Unit turned off.
ACTION
Be sure to use only the
primary physical
identifier (PID) to
reference a SCOPE 2
mainframe. You may
enter a QUEUE7, ID
command to list PIDs
currently active.
Rerun the job. If the
problem recurs, inform
a site analyst, write
a PSR and include
support material so that
CDC can duplicate the
problem.
Rerun the job. If the
problem recurs, inform
a site analyst, write
a PSR and include
support material so that
CDC can duplicate the
problem.
Reenter the command or
rerun the job. If the
problem recurs, inform
your site analyst or
contact Central Software
Support.
Correct MLTF procedure
c a l l. N o t i f y s it e
analyst if error occurs
after RHF command
ENABLE, mltf ordinal.
Correct MLTF procedure
c a l l . N o t i f y s i t e
analyst if error occurs
after RHF command
ENABLE, mltf ordinal.
Examine reprieve block
error flag to determine
the nature of the error.
Examine program to
determine why incorrect
monitor request call is
being made.
None.
Inform site analyst.
None.
None.
Inform customer engineer.
Inform customer engineer.
Inform site analyst.
Inform customer engineer.
Inform site analyst.
ROUTINE
QUEUE7
RESEX
RESEX
RESEX
MLTF
1AJ
1AJ
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
S^^lK
/^Sv
| 8 - 4 6 60459680 H
![](asset-283.png)
/§fe\ MESSAGE
MT,Ccc,Eec,Hhhhhhhhh,FNffff,Pyyyy.
MT,Ccc,Eec,Hhhhhhhhh,Lbbbb,Bnnnnnn.
MT,Ccc,Eec,Hhhhhhhhh,LOAD CHECK.
MT,Ccc,Eec,Hhhhhhhhh,MARGINAL, DOWN.
MT,Ccc,Eec,Hhhhhhhhh,MARGINAL, OFF.
MT,Ccc,Eec,Hhhhhhhhh,NO EOP.
MT,Ccc,Eec,Hhhhhhhhh,NOISE.
MT,Ccc,Eec,Hhhhhhhhh,NOT READY.
MT,Ccc,Eec,Hhhhhhhhh,ON THE FLY.
MT,Ccc,Eec,Hhhhhhhhh,POSITION LOST.
MT,Ccc,Eec,Hhhhhhhhh,RECOVERED.
MT,Ccc,Eec,Hhhhhhhhh,STATUS.
MT,Ccc,Eec,Hhhhhhhhh,WRONG PARITY.
MT,Ccc-e-uu,vsn,rw,est,Ss,GSgggggggg
MT,Ccc,Dddd...d.
MT,Ccc,Uuu...u,Ttttt.
MT,Ccc,Aaaaaaaaa.
MT,Ccc,Fff,Iii,Bnnnnnn,Lbbbb,Ppppppppp.
MT,Ccc,Eec,Hhhhhhhhh,type.
or
MT,Ccc-e-uu,vsn,rw,est,Ss,GSgggggggg.
MT,Ccc,Dddd...d.
MT,Ccc,Aaaaaaaaa.
MT,Ccc,Fff,Iii,Bnnnnnn,Lbbbb,Ppppppppp.
MT,Ccc,Eec,Hhhhhhhhh,type.
or
MT,Ccc,-e-uu,vsn,rw,est,Ss,GSgggggggg.
MT,Ccc,Dddd...d.
MT,Ccc,Fff,Iii,Bnnnnnn,Lbbbb,Ppppppppp.
MT,Ccc,Eec,Hhhhhhhhh,type.
or
MT,Ccc-e-uu,vsn,rw,est,Ss,GSgggggggg.
MT,Ccc,Dddd...d.
MT,Ccc,Uuu...u,Ttttt.
MT,Ccc,Fff,Iii,Bnnnnnn,Lbbbb,Ppppppppp.
MT,Ccc,Eed,Hhhhhhhhh,type.
SIGNIFICANCE
Function ffff was rejected by the
controller; yyyy is the address in 1MT
where the function was initiated.
The length (bbbb) and block number (nnnnnn)
read from trailer bytes in block did not
match the actual length or the block number
read given in previous message line.
Load sequence failed on the unit.
Indicates controller failure. Channel has
been logically turned off and maintenance
is required.
Unit has been logically turned off because
of read/write failure. This occurred when
a special function to check the read/write
path to a unit failed during initial label
scan. Maintenance is required.
No end-of-operation detected from unit
within 1 second.
A noise block was skipped on the tape.
Tape unit dropped ready status.
Error was corrected as the data was read.
The last good block written cannot be found
during write recovery.
Previously reported error has been
successfully recovered.
Error type cannot be determined so actual
controller status is returned.
Tape was written in parity opposite that
being read.
Four or five or six-line message describing
a magnetic tape hardware malfunction on a
66x or 67x tape unit. Message as
illustrated indicates 7-track, model 667 or
677 unit. If NT appears in place of MT,
message indicates 9-track, model 669 or 679
unit. Message is issued to error log and
dayfile.
The first line of each message provides the
following information.
cc-e-uu Channel, equipment (tape
controller), and physical
unit number of tape unit on
which error was encountered.
vsn Volume serial number
associated with tape on the
specified unit.
r w R e a d ( R D ) o r w r i t e ( W R )
operation; any operation not
involving an actual read or
write is listed as a read.
e s t E S T o r d i n a l o f t h e u n i t o n
which the tape was written.
This is provided only for
labeled tapes generated
under NOS; otherwise, the
field is blank.
s Channel status.
gggggggg General status of magnetic
tape unit. Last byte is
block ID.
The MT,Ccc,Dddd...d line of the message
provides the following information.
cc Channel number; the channel
number is repeated to allow
the analyst to associate
this message with the first
message if errors are
occurring on more than one
tape channel at the same
time.
ddd...d Detailed status of magnetic
tape unit.
ACTION
Inform site analyst.
None.
Push CLEAR button and
reload tape, or inform
site analyst.
Inform customer engineer.
Inform customer engineer.
Inform customer engineer.
None.
Make unit ready.
None.
None.
None.
Inform site analyst.
None.
Refer to the separate
listing of the last line
message (MT,...,type.)
for the appropriate
action.
ROUTINE
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
1MT
0i^\
60459680 H B - 4 7 |
![](asset-284.png)
SIGNIFICANCE
The MT,Ccc,Uuu...u,Ttttt line of the
message provides the following information,
cc Channel number; repeated to
associate this message with
the previous message.
uu...u Detailed unit status,
t t t t T h i r d b y t e o f t h e t a p e u n i t
format parameters (refer to
the magnetic tape subsystem
reference manual for
descriptions of unit format
parameter fields).
The MT,Ccc,Aaaaaaaa line (for FSC only)
contains the additional sense byte
status not placed in the detailed status
or unit status fields.
cc Channel number.
aaaaaaa Sense byte.
ACTION
MT/NT CONFLICT.
MULTI-FILE NOT FOUND, filename AT address.
MULTI-TRACK PHASE ERROR.
ff
ii
bbbb
The MT,Ccc,Fff,...,Ppppppppp line of the
message provides the following information,
cc Channel number; repeated to
associate this message with
the previous message.
Software function on which
the error occurred.
Error iteration; number of
times error has been
encountered on this unit
without successful recovery.
Block number on which error
occurred.
Length of block on which
error occurred in octal
bytes,
pppppppp 1MT internal error
parameters.
The last line of each message provides the
following information.
cc Channel number; repeated to
associate this message with
the previous message
ec Octal error code value.
Parameters passed to the
tape unit for the format
function (refer to the tape
drive's hardware reference
manual for descriptions of
the unit format parameter
fields).
Additional description of
the error. Refer to
individual list ing of the
last line message.
hhhhhhhh
type
Conflict exists between 7-track and 9-track
tape descriptors (track type, density, and
conversion mode). For example, a request
for a 9-track tape specified 200 bpi
density. This message can also be issued
if the device type specified in FET+1
conflicts with the track type specified in
bit 56 of FET+10 octal. If dt=MT and bit
56 is set, the message is issued.
Either LISTLB has reached the end of the
multifile set or the requested file was not
found. The following additional messages
are also given.
- REQUESTED SECTION xxxx.
- FOUND SECTION yyyy. or
- FILE IDENTIFIER NOT FOUND.
The filename, address, xxxx, and yyyy given
can be ignored.
Multiple tracks were found to be in error
at 1600 cpi, making recovery impossible.
The dayfile message STATUS ERROR, filename
AT address precedes this message and
specifies the file (filename) and the
address.
Ensure accuracy of
command.
RESEX
BLANK
If LISTLB reached the
end of the multifile
set, the operation is
complete and no action
is required. Otherwise,
ensure that the correct
tape is being used and
that it contains the
desired file(s). All
label parameters must
match in order to
position to the
specified file.
Retry or inform site
analyst.
1MT
1MT
B-48 60459680 H
![](asset-285.png)
MESSAGE SIGNIFICANCE ACTION
r
MULTIPLE CONCURRENT LOGINS PROHIBITED.
MULTIPLE 7000 JOBS NOT ALLOWED
MUST HAVE SYSTEM ORIGIN PRIVILEGES.
NETWORK APPLICATION ABORTED, RC5=568.
NFETCH: ILLEGAL FIELD MNEMONIC.
NETWORK APPLICATION ABORTED, RC5=569.
NSTORE: ILLEGAL FIELD MNEMONIC.
NETWORK TYPE DOES NOT SUPPORT ATTRIBUTE
COMMAND.
NEXT VSN est,vsn.
NO CLOSING DELIMITER FOUND
NO DATA FOUND FOR USERNAME.
NO EXTENDED MEMORY.
NO FILE NAME SPECIFIED.
NO FILES FOUND.
NO FILES FOUND FOR SPECIFIED DUMP FILE.
NO HDR1 LABEL RETURNED ON OPEN.
NO HOST AVAILABLE CONTROL CHARACTER=char
ENTER char HD TO SEE HOST STATUS
NO HOST CONNECTED CONTROL CHARACTER=char
TERMINAL DISABLED BY NOP
NO HOST SELECTED CONTROL CHARACTER=char
ENTER char HN=NODE NUMBER or
HS=NAME TO SELECT HOST
NO INPUT FILE FOUND.
NO JOB CHARACTERISTICS SPECIFIED.
NO JOBS FOUND.
NO JSN-S RECOVERED.
Another terminal session is active
under your user name, and you are
not validated to have more than one
terminal session simultaneously.
You have attempted to submit a second job
file when you already have an outstanding
SCOPE 2 job in processing.
The Mass Storage Subsystem Utility must be
run from job with system origin privileges.
Either the field or value parameter in the
indicated call was not found.
Either the field or value parameter in the
indicated call was not found.
You are attempting to enter NAM/CDCNET
commands from a NAM/CCP connection.
Tape volume vsn is mounted on tape unit est
and accepted as the next volume in the file
being processed.
No closing delimiter was found on a
string. A string is considered to end
after the last nonblank character.
RECLAIM could not find the calling user in
the directory of the database.
A DMPECS or DMDECS command or DED or DEP
request was entered and no extended memory
field length is assigned to you.
You entered a SECHDR command without
specifying a file name.
No entries exist for specified *FN* option
when the *FN* parameter contained one for
more asterisks.
For a COPY, LOAD, or LIST directive,
RECLAIM did not find the specified VSN in
the database; RECLAIM is attempting to read
the tape and rebuild the database for that
tape.
No HDR1 label was found in the label buffer
after the OPEN function was completed.
Indicates a possible system error.
No hosts are available.
char The network control
character for your terminal.
The network operator has disabled your
terminal. No further input is possible,
char The network control
character for your terminal.
You have not selected a host and a host is
available.
char The network control
character for your terminal.
No valid input file exists; functions
cannot be performed.
You specified no parameters or made
incomplete parameter specifications on the
SETJOB command.
The system can find none of your jobs.
The system encountered an EOR, EOF, or EOI
while reading input directives.
If you need to do this,
contact your site
personnel.
Wait for the first job
to complete before
submitting another job.
Make sure job has system
origin privileges.
NVF
HELL07
ASDEBUG
ASDEF
ASLABEL
ASMOVE
ASUSE
ASVAL
Correct t h e ca l l a n d r e r u n FIP
the job
Correct t h e ca l l a n d r e r u n FIP
the job.
Ensure that the TRMDEF
attributes you are
trying to change can be
changed in your network
by TRMDEF.
None. 1MT
None.
Check for correct
database file
specification.
None.
Reenter the command with
the correct file name.
None.
Check your database file
specification.
Inform site analyst.
Check the status of
the hosts in your
configuration.
None.
Select a host.
Verify that input file
is present.
Do not enter the command
if you do not want to
change any job
characteristics.
Otherwise, specify the
parameter correctly.
None.
IEDIT
RECLAIM
CPMEM
CATLIST
LISTLB
CCP
CCP
CONTROL
ENQUIRE
RECOVER
60459680 H B-49
![](asset-286.png)
MESSAGE
NO LINE NUMBER ON LINE
NO LINE NUMBER ON SORT FILE.
SIGNIFICANCE
Either the primary file or a sequenced
READ file contains a Line without a Line
number.
A Line on the input file to a SORT request
is missing a line number or a line exceeded
the line length limit.
Use an editor to
correct the bad
line.
Check the format of the
input file.
ROUTINE
SORT
NO LINE TERMINATOR AT EOR(S), You attempted to copy a file in which the
last line of one or more records did not
have a line terminator.
Check the structure of
the file to be copied.
COPYC
NO LINES FOUND No line in the edit file meets the criteria
specified by the edit command.
None.
NO MASS STORAGE AVAILABLE. No mass storage space of the requested
type could be found.
Retry later.
NO NEW FILE. N=0 was inappropriately specified for the
*N* parameter.
Either omit the *N*
parameter to allow the
default file *NEW* to be
used or set it equal to
the valid file name.
LIBEDIT
NO PERMITS. No permit entries exist for the specified
file.
None. CATLIST
NO PRIMARY FILE.
NO PRIMARY FILE.
The command entered requires a primary file.
A command needed the primary file as the
default file. No primary file was found.
Establish a primary file IAFEX
with NEW, OLD, or
PRIMARY command and
reenter original command.
Specify a file name on PFILES
the command or create a
primary file with the
NEW, OLD, or PRIMARY
command, and then retry.
NO READ/DESTINATION FILE SPECIFIED No read or destination file was specified
in the edit command.
Reenter command with
specified read or
destination file.
NO READ FILE FOUND - filename. The file specified on the READ directive
cannot be found.
Ensure that file name
specified is correct and
that the file is a local
file or a permanent file.
SUBMIT
NO RECOVERABLE JOBS.
NO RECOVERABLE JOBS.
You have no recoverable jobs.
Condition encountered during terminal
recovery attempt. There are no detached
jobs for this user.
No action required.
None.
RECOVER
IAFEX
NO RESPONSE FROM OTHER MAINFRAME Communications between SCOPE 2 and the
SCOPE 2 station have been interrupted by a
system problem.
Try to reenter the
command at a later time.
QUEUE7
NO SOURCE FILE SPECIFIED.
NO SUCH FILE
No file name was specified on the SUBMIT
command.
The file requested in the SUBMIT directive
cannot be found.
Specify a file name on
the SUBMIT command.
Check to ensure that the
correct file name was
entered and that the
file exists as a local
NOS file.
SUBMIT
HELL07
filename - NO TEMP DEVICE FOUND. You attempted to create a local copy of an
indirect access permanent fite, but the
file's access level was not within the
range of valid access levels for any active
temporary storage device.
Inform security
administrator. The
security administrator
needs to configure the
system so that temporary
devices are available
for all valid access
levels.
PFM
NO TERMINATOR IN COMMAND CALL. No terminator was found before the first
delimiter in a NOTE, BLOCK, or ENTER
command.
Correct command and
retry.
NOTE
| B - 5 0 60459680 H
![](asset-287.png)
MESSAGE
NO WRITE ENABLE, filename AT address.
NO 7000 JOB ACTIVE
NOISE BLOCK PROCESSING IN EFFECT.
n NOISE BLOCKS DELETED,
n NOISE BLOCKS PADDED.
NOISE SIZE IGNORED FOR PE/GE.
NON-BUFFERED EQ-S CHECKPOINTED.
RECOVERY ABORTED.
NON-EXISTENT EDIT VERB SPECIFIED
NON-MATCHING CONVERSION.
NON-MATCHING DENSITY.
NORERUN/RERUN INCORRECT FROM INTERACTIVE
JOBS.
NOT ALL EQUIPMENT SERVICEABLE.
filename NOT DECLARED NRANDOM.
jsn/ujn NOT FOUND.
filename NOT FOUND.
SIGNIFICANCE
Either you attempted to write on a tape
mounted with no write ring, or no write was
allowed because of additional constraints
described in an additional message tine.
You issued a STATUS or RESUME directive
when no SCOPE 2 job can be associated with
your user name.
Noise processing was automatically selected
because the output tape noise size exceeded
the input tape noise size on a COPY where
no noise size was specified.
Block(s> on S or L output tape smaller than
noise size have been deleted/padded.
An informative message indicating that you
entered a LABEL, REQUEST, or ASSIGN command
with a noise size (NS parameter) specified
for a PE or GE density tape on an ISMT
subsystem. The NS parameter is ignored for
those tape densities on an ISMT subsystem.
In the recovery process of aborting a CM
recovery, 1CK was called to process
outstanding checkpoint requests for all
nonbuffered devices.
Internal error.
Informative message indicating conversion
mode on labeled 9-track tape differs from
that specified by assignment request.
System writes tape in specified mode, or
reads tape with write ring out in correct
mode. However, reading tape with write ring
in or using wrong conversion mode generates
conversion errors.
Informative message indicating that the
density specified on the command or macro
is not the same as the density of the
assigned tape. Issued only to 9-track
tapes with write ring out. 9-track tapes
are read at the current density on tape.
They are written at specified density if
write initiated from load point; otherwise,
tape is written at the current density on
the tape.
You entered a NORERUN or RERUN command from
an interactive terminal. The command is
ignored.
The number of batch I/O equipments defined
in the EST exceeds an assembly constant.
It will not be possible to access some
equipment.
An EOF was encountered on the nonrandom
file, filename.
The system could not find the job with
the specified job sequence name (JSN)
and user job name (UJN).
RESTART was unable to retrieve the named
fi l e .
ACTION
If no additional message
line appears, ensure the
inserting of a write
ring by specifying the W
processing option on the
tape request (for
example, P0=W on the
LABEL command).
Otherwise, refer to the
description of the
message in the
additional message line.
None.
None.
ROUTINE
1MT
HELL07
COPYB
None.
Level 0 deadstart
required.
Submit a PSR with
information on how
to duplicate the
problem.
If reading tape with
write ring in, return
and reassign with
correct conversion mode.
None.
RESEX
1CK
RESEX
None.
Modify the EQP deck or
contact Central Software
Support.
Verify that file name is
in correct format.
Check to see if you
specified the correct
JSN and UJN.
Verify that filename is
vaIi d.
QFM
CONTROL
110.
LIBEDIT
QGET
DROP
60459680 H 8-51
![](asset-288.png)
MESSAGE
filename NOT FOUND.
or
username NOT FOUND.
jsn NOT FOUND.
n NOT FOUND.
xxx NOT IN PP LIB.
xxx NOT IN PP LIB. CALLED BY yyy.
filename NOT IN WRITE MODE.
filename NOT ON MASS STORAGE.
filename NOT ON MASS STORAGE.
filename NOT ON MASS STORAGE.
NOT VALID TO DOWNGRADE DATA.
NOT VALIDATED FOR EXTENDED MEMORY MINIMUM CM.
NOT VALIDATED FOR REQUESTED ACCESS LEVEL.
NOT VALIDATED FOR WRITING UNLABELED TAPES.
NOT VALIDATED TO SET XD/XT.
NOTICE*** DATA READ ERROR.
NT DENSITY CONFLICT.
NT DRIVE CONFLICT.
OFFSW, x FROM JOB jsn
SIGNIFICANCE
One of the following:
- The specified permanent file could not
be found.
- The specified user name could not be
found.
- You are not allowed to access the
specified file.
- The specified local file could not be
found.
You specified a JSN that you cannot recover.
n, the specified UJN or JSN, was not found.
Dayfile message indicating that PP package
xxx was not found in PP libraries.
Dayfile message indicating that PP package
xxx, which was called by package yyy, was
not found in the PP libraries.
The file specified in an OVWRITE command or
macro was not processed because you do not
have write access to it.
The file to be saved is not on mass
storage; the first track of the file is not
recognizable.
The file specified in an OVWRITE command or
macro was not processed because it does not
reside on mass storage.
filename was not processed because it could
not be found on mass storage.
You attempted to lower the access level of
a permanent file, but you are not validated
to downgrade files.
You were authorized for the extended memory
specified on the Job command but was not
authorized for at least 10000 octal words
of memory.
User has specified an access level outside
the user's access level validation.
User has not been validated for writing on
unlabeled tape.
You specified an XD or XT parameter in a
CHANGE, DEFINE or PERMIT command or macro
without having validation to use these
parameters.
Read error caused loss of words in the
dayfile.
9-track tape unit specified by EST ordinal
on ASSIGN command does not support the
required density.
One of the following.
- 9-track tape unit specified by EST
ordinal on ASSIGN command conflicts with
other resource requirements for this
job. In this case the system rejects
assignment to prevent the job from
deadlocking itself.
- Increased resource demands (RESOURC
command) cannot be satisfied due to
conflicts with currently assigned
resources (job would deadlock itself).
An OFFSW command was issued to the job by
the job jsn. x represents the sense
switch(es) that has been turned off.
ACTION
Verify that file name/
user name is correct,
that access permission
has been granted, and
that correct access is
being attempted.
Refer to your list of
recoverable jobs. Type
RELIST for another list.
None.
Ensure that the correct
PP package name was
specified.
Ensure that the correct
PP package name was
specified or write a PSR.
Correct and retry.
Verify th at file is on
mass storage.
ROUTINE
Correct and retry.
Move file to mass
storage, or correct the
commmand and retry.
None.
Request a larger CM
validation limit from
site personnel.
Use a validated access
level, or site must
validate user for
additional access level.
Either use labeled tape
or site must validate
user for SAV=CULT MODVAL
privilege.
Retry without XD or XT
parameter, or obtain
validation and retry.
None.
Ensure that density
compatible tape unit is
specified.
Check the description of
the RESOURC command in
section 7. Reduce
resource demand which
causes conflict.
RECOVER
ENQUIRE
SFP
SFP
1MS
PFM
1MS
MFILES
PFM
CHARGE
RESEX
RESEX
PFM
DAYFILE
RESEX
None. 1RI
| B - 5 2 60459680 H
![](asset-289.png)
MESSAGE
OFFSW, x FROM OPERATOR
OLD MASTER FILE EMPTY OR MISPOSITIONED
ONLY CORRECT PARAMETERS ARE *ON* OR *OFF*.
ONSW,x FROM JOB jsn.
OP OPTION NOT VALID.
OPERATOR DROP.
OPERATOR INPUT TERMINATION.
OPERATOR KILL.
OPERATOR OVERRIDE.
OPERATOR RERUN.
OUTPUT INCOMPLETE
OVERLAPPING INSERT OR DELETE.
OVERLAY FILE EMPTY.
OVERLAY FILE NOT FOUND.
OVERLAY LOST.
OVERLAY NOT FOUND.
OVERLAY NOT FOUND IN LIBRARY - ovIname.
*OVL*
PACK COMPLETE.
PACK PARAMETER ERROR.
PARAMETER *ON* OR *OFF* REQUIRED.
PARAMETERS CE AND CP ARE MUTUALLY EXCLUSIVE.
SIGNIFICANCE
An OFFSW command was issued to the job by
the console operator, x represents the
sense switch(es) that has been turned off.
None of the replacement file records were
copied to the new file.
The parameter you specified was not
recognized.
An ONSW command was issued to the job by
the job jsn. x represents the sense
switches that sense switches that have been
turned on.
You specified some value other than T for
the 0P=op parameter.
Informative message indicating that the
operator dropped the job.
ACTION
None.
Ensure that the file is
assigned to the job. If
file is assigned, rewind
the file.
Check command
description and retry.
None.
Either omit the 0P=op
parameter or specify T
for its value.
None.
Job was terminated without exit processing. Resubmit job.
/0®$£\
The operator entered a KILL command to drop
the job. This disallows exit
processing unless the job has extended
reprieve. A job with extended reprieve
processing is reprieved once. Exit
processing is allowed.
The operator entered an OVERRIDE command to
drop the job. This disallows exit, erexit,
and reprieve processing.
The operator is rerunning the job.
A hardware or software problem occurred.
LIBEDIT encountered an overlap in the
record names specified in the directives.
No data appears in the requested file.
The specified file was not available.
The specified overlay was not found.
The specified overlay was not found.
The overlay ovIname was not found in the
system library.
You have entered a logical line that
exceeds the maximum logical line length and
IAF has discarded it.
Informative message indicating that the
program has completed processing.
The PACK command contains too many or no
file names.
No parameter was specified on ERRMSG
command.
You entered a CHANGE command that included
both a CE and a CP parameter. These
parameters cannot both be specified in the
same CHANGE command.
Correct job as needed
and rerun.
Correct job as needed
and rerun.
No action required.
Reenter the command. If
the same message is
returned, inform the
site analyst.
Correct the directives
listed in the LIBEDIT
output so that there is
no overlapping of file
names for insertions or
deletions.
Verify that overlay file
is valid.
Verify that file is
local to job and retry.
Inform software support.
Verify that the file
with the specified
overlay is local to the
job.
Verify that call is to
vali d ove rl ay.
Reenter data in logical
lines of shorter length.
None.
Check the format of the
PACK command in section
9.
Retry with a parameter.
Correct the parameter
specifications and
resubmit.
ROUTINE
1RI
COPYL
COPYLM
CONTROL
1RI
RECOVER
1AJ
1AJ
1AJ
RECLAIM
1AJ
1AJ
RECLAIM
QUEUE7
1AJ
1AJ
1AJ
1AJ
IAFEX
PACK
PACK
CONTROL
60459680 H B-53
![](asset-28a.png)
MESSAGE
PARAMETERS CE AND CP ARE MUTUALLY EXCLUSIVE.
PARAMETERS *0N* AND *OFF* ARE MUTUALLY
EXCLUSIVE.
n PARITY/BLOCK TOO LARGE ERRORS.
PARITY ERROR.
PARITY ERROR, JOB HUNG.
PARITY ERROR - RESTARTED FROM kk.
PASSWORD RANDOMIZATION NOT PERMITTED FROM
BATCH.
PASSWORD TOO LONG.
PASSWORD TOO SHORT.
PASSWORD VERIFICATION ERROR. PASSWORD NOT
CHANGED.
PAUSE FROM JOB jsn
PAUSE FROM OPERATOR
pfn PERMANENT ERROR.
PERMIT LIMIT EXCEEDED.
PF STAGING DISABLED.
PF UTILITY ACTIVE.
PFATC - NO FILES PROCESSED.
SIGNIFICANCE
You attempted to specify both the CE and
the CP parameter on the same CHANGE
command. They cannot be specified together.
You specified both the ON and OFF
parameters on the same command. Only one
is allowed.
Parity and/or block-too-large errors have
been encountered on the input file during
the copy operation.
The tape could not be read/written
correctly. The dayfile message STATUS
ERROR, filename AT address precedes this
message and specifies the file (filename)
and the address.
A CM parity error occurred in the jobs
field length. The job is hung to freeze
the affected area.
Because RESTART detected a parity error in
attempting to restart from the specified
checkpoint nn, the alternate checkpoint kk
was used instead.
You entered a PASSWOR command from a
non-interactive job when password
randomization is required. When password
randomization is required, PASSWOR can
only be entereed from an interactive job.
You entered a PASSWOR command with a new
password that is too long. The new
password cannot exceed seven characters
including randomization characters.
Either you specified fewer than two
nonrandom characters for the new password
specification in a PASSWOR command, or the
new password was shorter than the minimum
password length required by the site.
For the PASSWOR command, you entered the
new password incorrectly in response to the
password identification prompt.
A PAUSE command was issued to the job by
the job jsn.
A PAUSE command was issued to the job by
the console operator.
The specified direct access file resides on
alternate storage and has data errors that
must be corrected. The error flag must be
cleared or the file must be reloaded from a
backup copy.
A PERMIT command or macro cannot be
processed because the file specified
already has the maximum number of permits
allowed.
The specified direct access file cannot be
accessed since it resides on the Mass
Storage Facility (MSF) and the site has
temporarily disabled all MSF file staging.
The operation was not attempted because a
permanent file utility was currently active.
Informative message indicating that no
files meeting the specified selection
criteria were found.
ACTION
Do two separate CHANGE
commands to perform the
two functions.
Retry with either ON or
OFF.
If dayfile shows block
too-large errors have
occurred and tape is S,
L, or F format, increase
block size and retry;
otherwise, tape is
probably assigned in the
wrong format. If parity
errors have occurred,
the tape is bad and the
data on it cannot be
correctly recovered.
Retry or inform site
analyst.
Inform software support.
None.
Resubmit PASSWOR from an
interactive job.
Correct the new password
specification and
resubmit.
Correct the new password
specification and
resubmit.
Resubmit the PASSWOR
command.
None.
None.
Inform site analyst.
The site analyst may
be able to correct the
problem with ASDEBUG or
SSDEBUG; otherwise, the
file must be purged or
reloaded.
None.
Determine from site
operator when MSF file
staging will resume and
retry the job at that
time.
Wait until PF utility is
not active and retry.
None.
ROUTINE
PFILES
CONTROL
COPYB
e^%k
1MT
1AJ
-*^s%
RESTART
MODVAL
MODVAL
MODVAL
MODVAL
1RI
1RI
PFM
-^
PFM
PFM
PFATC
B-54
/•<©X
60459680 H
![](asset-28b.png)
MESSAGE
PFM ABORTED.
POSITION ERROR ON-filename.
POSITION LOST, filename AT address.
POSTAMBLE ERROR.
PP A80RT.
PP CALL ERROR.
PP CALL ERROR.
PREMATURE EOR/EOF ON SOURCE FILE.
PRIOR TAPE ASSIGNMENT LOST.
PROCESSING OPTION NOT APPLICABLE.
PROCESSOR DETECTED MALFUNCTION
PROCESSOR STATE ERROR
PROGRAM FILE EMPTY.
PROGRAM STOP.
PROGRAM STOP AT address.
PROJECT NUMBER EXPIRED.
PRU LIMIT.
PRU LIMIT, FILE filename AT address.
PRUS REQUESTED UNAVAILABLE.
SIGNIFICANCE
Error flag detected at PFM control point.
File filename was not repositioned after
being checkpointed because CHKPT detected
an address error.
A block ID mismatch exists or; the block
ID window is all ones. This indicates
that a NOS terminator label mismatch
exists.
In either case, the position on the tape
cannot be established and the job will
terminate.
A missing or defective postamble was
detected at 1600 cpi. The dayfile message
STATUS ERROR, filename AT address precedes
this message and specifies the file
(filename) and the address.
System error in PPU.
The monitor detected an error in a CPU
request for PP action.
Error detected in PP call due to hardware
or RECLAIM error.
The system encountered an end-of-record
(EOR) or end-of-file (EOF) in the source
file before it processed all the
information.
Magnetic tape executive has been dropped
along with tapes assigned. All of the
job's prior tape assignments are lost.
The processing options, P0=R and P0=D, are
allowed only on a COPY command copying from
mass storage, or an I or Si-binary format
tape to an S or L format tape. The
processing option, P0=T, is allowed on a
COPYB command that generates an E or B
format tape.
A hardware error (error code=20) occurred
such as a data or address parity error
or double bit error.
A hardware error (error code=67) or a
software error.
A load of an empty file was attempted.
The system processed a program stop (00)
instruction.
The monitor detected a program stop
instruction at the specified address.
Dayfile and output file message indicating
that the project number expiration date has
occurred.
The job's mass storage PRU limit was
exceeded during preparation of a local copy
of an indirect access file.
The job's mass storage PRU limit was
exceeded during an attempt to write or
extend this file.
On a DEFINE, no device currently has
available the amount of space requested by
the S parameter. On a secured system, no
device with the proper access level
currently has the amount of space requested.
ACTION
Check dayfile for reason
for error flag.
None.
Clean the tape path.
ROUTINE
CHKPT
1MT
Retry or inform site
analyst.
Examine the job dayfile to
determine the cause.
Verify that correct PP
call is issued.
Inform site analyst.
Remove the extra EORs
and EOFs from the source
file.
From an interactive job,
return/unload all prior
tapes and reassign. A
batch job aborts and
must be rerun.
Refer to the COPY or
COPYB command
description in section
9, correct the command,
and retry.
Analyze job dumps,
maintenance registers,
and the error log or
HPA reports to
determine cause.
Analyze job output,
dumps, listings,
maintenance registers
and the error log or
HPA reports to determine
cause.
None.
None.
None.
None.
Return one or more local
files and retry.
Return one or more local
files and retry.
If possible, reduce the
number of PRUs specified
by the S parameter, or
retry at another time
when space might be
available.
1MT
1AJ
RECLAIM
DOCMENT
1AJ
1AJ
1AJ
1AJ
1AJ
CHARGE
GET
1MS
60459680 H B-55
![](asset-28c.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
NOTE
A number of messages of the form "PTFS-message" are not unique to PTFS. These
messages are listed alphabetically by the message itself; just ignore the letters
PTFS when looking them up.
/ff=*^5^h
PTFS - error message returned by NOS
PTFS - APPLICATION CONNECTION TIMEOUT.
PTFS - CHARGE REQUIRED.
PTFS - CHARGE RESTRICTED TO DEFAULT.
PTFS - DEFAULT CHARGE IS NULL.
PTFS - DIRECTIVE TOO LONG.
PTFS - ERROR IN ARGUMENTS.
PTFS - ERROR IN EXPIRATION DATE
PTFS - EXECUTE ONLY FILE.
PTFS - FILE ALREADY PERMANENT.
PTFS - FILE IS DIRECT ACCESS.
PTFS - FL TOO SHORT FOR PROGRAM.
PTFS - HOST NOT SPECIFIED TYPE.
PTFS - INCOMPLETE CONTINUED DIRECTIVE.
PTFS - INVALID keyword=value.
PTFS - INVALID ACCESS VALIDATION.
PTFS - INVALID ALTERNATE CATLIST
PERMISSION.
PTFS - INVALID BACKUP/RESIDENCE REQUIREMENT.
PTFS - INVALID DATA DECLARATION TYPE.
PTFS - INVALID DEVICE SPECIFICATION.
PTFS - INVALID DIRECTIVE.
An error message has been received from NOS
by PTFS. PTFS takes this message, prefaces
it with a 'PTFS - ', and returns the new
message to you.
The remote host did not respond in the
alloted time.
You must specify a CHARGE directive and you
did not do so.
On a CHARGE command, you specified a charge
and project number which was not the
default that you were validated for, and
your validation restricts you to that
default.
The default charge number for the current
user name is undefined, and charge is
required.
Your directive is too long. A directive
cannot exceed 80 characters.
Either one or both of the following occured
on a SAVE or a DEFINE directive on a MFLINK
command.
- You specified both XD and XP parameters.
- You specified an XD or XP parameter
without specifying a PW parameter.
There was an error in the expiration date
specified on a SAVE or a DEFINE directive
on a MFLINK command.
You attempted to transfer an execute-only
file.
You attempted to save a file that is
already permanent.
You attempted to alter a direct access file
with a REPLACE or APPEND directive. This
is not allowed.
There is a system error in the remote host.
Your job assumes a non-NOS remote host and
you have been linked to a NOS remote host.
The remote host expected the text string to
be a continuation of the previous string
and it was not.
You specified an incorrect parameter
(keyword=value).
Your USER directive has an incorrect user
name or the specified user name does not
have job processing privileges on the
remote host.
You specified an incorrect value for the AC
parameter on a SAVE, DEFINE or CHANGE
command.
You specified an incorrect BR=br or PR=pr
parameter on one of your directives.
You specified an incorrect DD=dd parameter.
You specified an incorrect R=r parameter on
your directive.
The remote host does not recognize the
directive you specified.
Refer to the message
returned by NOS for the
appropriate action. (That
is, ignore the letters
"PTFS -" and look up the
message itself alphabetically
in this appendix).
None.
Restart your session and PTFS
include a CHARGE
directive.
Use CHARGE(*) rather PTFS
than specifying a charge
and project number.
U s e a v a l i d c h a r g e a n d P T F S
project number.
S h o r t e n y o u r d i r e c t i v e P T F S
and retry.
Correct the SAVE or PTFS
DEFINE directive, and
reenter the MFLINK
command.
Correct the expiration PTFS
date on the SAVE or the
DEFINE directive and
reenter the MFLINK
command.
Change permanent file PTFS
access to allow read
permission.
Purge the file and retry. PTFS
Change directive and PTFS
retry.
Inform site analyst. PTFS
Inform site analyst. PTFS
Correct the syntax of PTFS
your directives record
with emphasis on the
continuation lines.
Correct and retry. PTFS
Ensure that the user PTFS
name is correct and
retry. Inform site
analyst if the problem
persists.
Retry, specifying a PTFS
correct value.
C o r r e c t t h e p a r a m e t e r P T F S
and retry.
Correct the DD=dd PTFS
parameter and retry.
Correct and retry. PTFS
E n s u r e t h a t t h e s y n t a x P T F S
of the directive is
correct and retry.
B-56 60459680 H
![](asset-28d.png)
Xj8B&\
0ffiZ\
MESSAGE
PTFS - INVALID MODE/CATEGORY.
PTFS - INVALID xxxxxx=NO VALUE.
PTFS - LID UNAVAILABLE.
PTFS - MISSING CHARGE/PROJECT.
PTFS - MISSING USER NAME.
PTFS - MULTIPLE FILE TRANSFERS REQUESTED.
PTFS - PARAMETERS CE AND CP ARE MUTUALLY
EXCLUSIVE.
PTFS - PF NAME REQUIRED.
PTFS - PF REQUEST COMPLETE.
PTFS - RECOVERY DIRECTIVE AFTER FILE TRANSFER.
PTFS - SECONDARY USER DIRECTIVES DISABLED.
PTFS - UNKNOWN ACCESS LEVEL NAME.
PTFS - USER DIRECTIVE REQUIRED FIRST.
PURGE COMPLETE.
QAC ERROR ENCOUNTERED.
QAP - BUFFER ARGUMENT ERROR.
QAP - INCORRECT REQUEST.
QAP - USER ACCESS NOT VALID.
QFM FILE NAME ERROR.
QGET COMPLETE.
QTF, -n- qfn ACQUIRED, DC=dc, ST=did,
DO=sid.
QTF, -n- qfn CONNECTING TO pid.
QTF, -n- qfn CONNECTION REJECTED.
SIGNIFICANCE
The mode and category you specified for the
file are not defined.
Argument xxxxxx was entered without a value.
The requested LID is not a host LID, is
disabled, or is a store-forward LID.
The CHARGE directive did not have the
required charge and project number.
The USER directive did not contain the
required user name.
You have more than one file transfer
directive in a given directive record.
This is not allowed.
The parameters CE and CP may not both be
specified on the same CHANGE command.
You did not specify the permanent file to
be processed.
The remote host successfully processed your
permanent file request.
Your MFLINK directives are not in the
proper sequence. If a file transfer
directive is in the same record as a USER
CHARGE, or PACKNAM directive; the USER,
CHARGE, or PACKNAM directive must precede
the file transfer directive.
You are not authorized to specify secondary
USER directives.
You entered an unknown access level name on
a SAVE or a DEFINE directive through a
MFLINK command.
You must first specify a USER directive to
access permanent files on remote NOS hosts.
The files have been purged as requested.
System error.
System error.
Bad parameter in QAP call.
You tried to perform an operation for which
you are not authorized (for example, trying
to use PFC arrays when not authorized to do
so).
The filename specified is not a valid file
name.
Informative only.
The system has acquired local queue file
qfn on connection number n from the local
queue with disposition code dc for transfer
to destination LID did with source LID sid.
The system is attempting to establish
communications with remote host pid.
qf n Q u eu e d fil e n am e
pid Physical identifier
The system was unable to establish a
connection to the remote host partner,
qfn Queued file name.
ACTION ROUTINE
Correct and retry. PTFS
Correct remote directive PTFS
and reissue.
Inform site analyst. PTFS
Correct and retry. PTFS
Correct and retry. PTFS
P l a c e t h e fi l e t r a n s f e r P T F S
directives in separate
records, one file
transfer directive per
record.
Use two separate CHANGE PTFS
commands, with one
specifying CP and the
other specifying CE.
Correct and retry. PTFS
Resequence your PTFS
directives and retry.
G e t s i t e p e rs o nn e l t o s o P T FS
authorize you or do not
attempt to use secondary
USER directives.
Correct the access level PTFS
name on the SAVE or the
DEFINE directive and
reenter the MFLINK
command.
Correct and retry. PTFS
None. PURGALL
Inform site analyst. ENQUIRE
Inform Central Software QAP
Support.
Inform Central Software QAP
Support.
Ensure accuracy of
command or determine
proper validation
requi rements.
Verify file name.
None.
None.
None.
If problem persists,
contact remote operator
to ensure remote
subsystem and QTFS are
operational; otherwise
contact site analyst.
QAP
QFM
QGET
QTF
QTF
QTF
60459680 H B-57
![](asset-28e.png)
MESSAGE
QTF, -n- qfn EVICTED.
QTF, -n- qfn INVALID QUALIFIER OR PARAMETER.
QTF, -n- qfn REQUIRED PARAMETER MISSING.
QTF, -n- qfn SENT TO PID xxx, PID yyy
RESPONDING.
QTF, -n- qfn UNEXPECTED ACQUIRE ERROR CODE
nnnB.
QTF, -n- qfn UNRECOGNIZED DISPOSITION CODE.
QTF(S), -n- qfn CONNECTION BROKEN.
QTF(S), -n- qfn CONNECTION TIMED OUT.
QTF(S>, -n- qfn CONNECTION TO pid
ESTABLISHED.
QTF(S), -n- qfn CONNECTION TO pid ABORTED.
QTF(S), -n- qfn CONNECTION TO pid ENDED.
QTF(S), COUNT OF ACTIVE CONNECTIONS
DECREMENTED BELOW ZERO.
QTF(S), -n- qfn ERROR IN FILE TRANSFER.
QTF(S), -n- qfn FC/BRK RECEIVED.
QTF(S), -n- qfn FC/NAK RETRY COUNT EXCEEDED.
QTF(S) -n- qfn FIRST KEYWORD IS NOT *ROUTE*.
QTF(S) -n- qfn INCORRECT EC FOR THIS QUEUE
TYPE.
QTF(S) -n- qfn INCORRECT VALUE (xxx).
QTF(S) -n- qfn INCORRECT VALUE (xxx=yyy).
QTFS, -n- qfn INVALID ATTRIBUTE IGNORED.
B-58
SIGNIFICANCE
The system evicted the local queue file qfn
to connection number n from the local queue,
qfn Queued file name
The system received an invalid network
message from the remote host,
qfn Queued file name
The remote host failed to send a required
parameter on a network message,
qfn Queued file name
The subsystem network description table
does not agree with the remote host PID
returned by the remote host QTFS. The file
transfer may complete.
qfn Queued file name
A system error.
qfn Queued file name
The system has acquired a file from the
local queue with an unrecognized
disposition code. See previous message for
disposition code value,
qfn Queued file name
The remote host partner or the remote
subsystem broke the network connection
usually due to an involuntary termination
or failing network hardware,
qfn Queued file name
Remote host partner did not respond within
the allowed time span. Transfer will be
retried.
qfn Queued file name
Indicates state of connection to remote
host partner.
qfn Queued file name
pid physical identifier
Indicates state of connection to remote
host partner.
qfn Queued file name
pid Physical identifier
Indicates state of connection to remote
host partner.
qf n Q u eu e d fil e n am e
pid Physical identifier
The application received a disconnect
but had no paths active.
Transfer of file qfn was unsuccessful,
qf n Q u eu e d fil e n am e
The remote host partner broke the network
connection. Usual cause is detection of an
unrecoverable protocol anamoly.
qf n Q u eu e d fil e n am e
The subsystem was unable to deliver a
network message.
qf n Q u eu e d fil e n am e
The MFQUEUE routing directive must begin
with the keyword ROUTE.
The external charactersitics (EC) value
specified on a MFQUEUE routing directive
does not match the disposition code of the
file.
You specified an incorrect keyword, xxx, on
an MFQUEUE routing directive.
You specified an incorrect value yyy for
keyword xxx on an MFQUEUE routing directive.
QTFS received a network message from the
remote host QTF with an unrecognized
parameter. Transfer may complete,
qfn Queued file name
ACTION
Inform site analyst.
Inform site analyst.
Inform site analyst.
Inform site analyst.
None.
If error persists,
inform site analyst and
customer engineer.
If error persists,
inform site analyst and
disable remote host pid
in subsystem ID table.
None.
None.
None.
Inform site analyst.
If error persists,
inform site analyst.
If error persists,
inform site analyst.
Inform site analyst.
Correct the MFQUEUE
routing directive.
Correct the MFQUEUE
routing directive using
a print-type EC value if
the file is a print
file, or a punch-type EC
value if the file is to
be punched.
Correct the MFQUEUE
routing directive.
Correct the MFQUEUE
routing directive.
Inform site analyst.
ROUTINE
QTF
QTF
QTF
QTF
QTF
QTF
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
<^Sv
60459680 H
![](asset-28f.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
QTF(S), -n- qfn INVALID SEQUENCE RECEIVED.
QTF(S), JOB ORIGIN ERROR.
QTF(S), -n- qfn MESSAGE FROM REMOTE HOST
QTF(S), -n- qfn xxx.
QTF(S), -n- qfn NETWORK BLOCKS OUT OF
SEQUENCE.
QTF(S), -n- qfn NETXFR ERROR re - rejmess
A network message from the remote host
partner was received that was not in
sequence.
qfn Queued file name
QTF or QTFS was improperly initiated by
user command.
xx x i s t h e te x t o f a m e s s a g e r e c e iv e d f r o m
the remote host partner,
q f n Q u e u e d fi l e n a m e
A network message from the remote host
partner was received that was not in
sequence.
q f n Q u e u e d fi l e n a m e
A n e r r o r o c c u r r e d d u r i n g fi l e t r a n s f e r ,
qfn queued filename
re reason code
rejmess reject message
Inform site analyst.
None.
None.
I n f o r m s i t e a n a l y s t .
I n f o r m s i t e a n a l y s t i f
problem persists.
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF(S) -n- qfn NO USERNAME FOR *DC=WT/TT*
FILE.
QTF(S) -n- qfn ROUTE ERROR nnB-xxxx.
re rejmess
03 CONNECTION BROKEN.
0 4 P RO T O C OL E R R O R.
05 TIMEOUT EXPIRED.
06 BLOCK NOT SENT.
07 TOO M A NY TRA N SF E RS
0 8 A C N O U T- O F - R A N G E .
09 CIO ERROR.
1 3 I D L E D O W N E R RO R .
14 SHUTDOWN.
1 5 R H F I / O E R R O R
16 INCORRECT DEVICE.
17 CODE CONV N/A. (not avail)
18 CONTROL WORD ERROR.
19 INCORRECT DEVICE.
20 EMPTY FILE.
21 NAM INTERFACE ERR.
22 BLK NUM MISCOMPARE.
23 INCORRECT BLK SIZE.
25 BLOCK SEQUENCE ERR.
26 PR U B O UN D S E R R O R .
27 INTRA-HOST PRU XFR.
28 ERROR DURING XFR.
29 ABL OUT OF RANGE.
30 APPL NOT VALIDATED.
31 FILE TYPE ERROR.
32 JOB ORIGIN ERROR.
QTFS is unable to accept a file for the
wait queue because no user name exists
with which to associate the file.
QTFS was unable to queue the file qfn due
t o o n e o f t h e r e a s o n s i n t h e f o l l o w i n g l i s t ,
nn i s th e DS P e r ro r co d e, a nd x xx x is t he
reason.
- INVALID
- DISPOSITION CODE. INVALID ST OR DO
- L I D . I N VA LI D T E R M I N A L I D . I N VA LI D
FOMSM CODE. INVALID JOB COMMAND.
INVALID DATA DECLARATION. INVALID
INTERNAL CHAR. INVALID EXTERNAL CHAR.
INVALID SPACING CODE. TOO MANY DEFERRED
JOBS. INVALID USER ACCESS. INVALID
USER COMMAND. QFT FULL (RETRY LATER).
DISK FULL (RETRY LATER). INVALID OWNER
USER. INVALID CREATION USER. FILE
IS EMPTY.
Specify UN=username QTF
parameter on MFQUEUE QTFS
routing directive.
I f R E T R Y L A T E R , n o Q T F
action is required; QTF QTFS
wilt periodically retry
t o t r a n s f e r t h e fi l e
until the temporary
c o n d i t i o n c l e a r s . F o r
a l l o t h e r r e a s o n s , t h e
fi l e i s e v i c t e d a n d t h e
log file is returned to
originator. Correct the
ROUTE command or MFQUEUE
routing directive, if
possible; otherwise
inform site analyst.
qfn Queued file name
QTF(S), -n- qfn TRANSFER xxxxxxxxxx BY
REMOTE HOST.
QTF(S), -n- qfn REASON CODE = nnnnnn.
or
QTF(S), -n- qfn REASON CODE = nnnnnn - yyy.
QTF or QTFS has been informed by its remote
host partner that the current file transfer
cannot be initiated or completed,
xxxxxxxxxx may be either REJECTED,
TERMINATED, or ABORTED, nnnnnn is the
re a s o n c o d e a n d y y y i s o n e o f t h e f o l l o w i n g :
- (CONTACT SITE ANALYST).
An unexpected reason code was received.
- PROTOCOL ERROR.
The remote host partner detected a protocol
anamoly.
If fatal transfer error, QTF
file is evicted and QTF QTFS
log file returned to
originator. In all
o t h e r c a s e s , t r a n s f e r
will be retried. If
error persists, inform
s i t e a n a l y s t .
60459680 H B-59
![](asset-290.png)
MESSAGE SIGNIFICANCE
TIME-OUT MATURED.
ACTION
Remote host partner did not receive message
within the allowed time span.
- SENDER PROBLEMS.
Unspecified problems were encountered on
the sending (QTF) side.
- RECEIVER PROBLEMS.
Unspecified problems were encountered on
the receiving (QTFS) side.
- FILE SIZE TOO BIG.
The file is too large to be accommodated on
the remote host or not enough space was
preallocated.
- INVALID USERNAME/ACCOUNT.
An invalid or missing account or username
was detected by the remote host partner.
- UNSPECIFIC TRANSFER
Insufficient information was received by
the remote host partner to allow the
transfer to continue.
- QUEUE TYPE UNAVAILABLE.
The disposition code requested on the ROUTE
command or MFQUEUE routing directive could
not be processed on the remote host. For
example, a print file was attempted to be
transferred to a CYBER 200 remote host.
- UNACCEPTABLE ATTRIBUTES.
QTF(S), SUPERVISORY MESSAGE RECEIVED
FOR INACTIVE ACN.
QTF(S), HDR=FIRST TWO WORDS OF HEADER.
QTF(S), -n- qfn UNKNOWN *PI* PARAMETER,
DEFAULT USED.
QTF(S), -n- qfn UNKNOWN STATE-OF-TRANSFER
SENT BY REMOTE HOST.
QTF(S), -n- qfn REASON CODE = nnnnnn - (CONTACT
SITE ANALYST).
QTF(S), -n- qfn UNRECOGNIZED COMMAND
RECEIVED XX.
An invalid attribute value was received by
the remote host partner.
A supervisory message that was received
contained a connection number that was
not currently active.
The remote NOS 2 system received a print
file with an unknown PI (print-image)
parameter. The file will be printed
using the default PI paramaeter.
qf n Que u e d fil e name.
An unrecognized value, nnnnnn, for the
state-of-transfer attribute was received on
a network message from the remote host
partner.
qfn Queued file name
The command sent by the remote host partner
is not recognized.
qfn Queued file name
xx Command number received.
Inform site analyst
Inform site analyst.
Inform site analyst.
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF
QTFS
QTF(S), -n-
RECEIVED. qfn UNRECOGNIZED MESSAGE
QUEUE7 ARGUMENT ERROR
RANDOM INDEX ERROR.
READ AFTER WRITE, filename AT address.
The network message received from the
subsystem is not recognized,
qfn Queued file name
You entered the QUEUE7 command incorrectly.
The random disk address of the permit
sector is in error (error log and dayfile
message). This may be a problem with
your program.
You attempted to read a tape on which the
last operation was a write.
Inform site analyst.
Check the command
format, then reenter the
command. You may enter
a QUEUE7,SYNTAX command
to display the command
format.
Check your program. If
it does not use the
CATLIST macro, inform
site analyst.
Ensure accuracy of tape
positioning commands
(BKSP, BKSPRU, SKIPFB,
or REWIND required to
read after write).
QTF
QTFS
QUEUE7
1MT
/ * ^ \
B-60 60459680 H
![](asset-291.png)
MESSAGE
READ FILE BUSY - filename.
READ FILE EMPTY.
READ ID BURST FAILURE, filename AT address.
READY.
READY DROP, filename AT address.
RECLAIM ABORTED.
RECLAIM ARGUMENT ERROR.
RECLAIM COMPLETE.
RECORD TOO LARGE ON filename.
RECORD TOO LONG.
n RECORDS NOT REPLACED.
n RECORDS SPLITS OCCURRED.
RECOVERY COMPLETE.
RECOVERY COMPLETE...CONTINUE
RECOVERY RERUN.
REMOVABLE PACKS OVERCOMMITMENT.
RENAME NOT ALLOWED FOR PROC OR TEXT RECORD.
RENAME OF PROC TYPE NOT ALLOWED.
REPEAT..
REPLACE ERROR.
0$$&t\.
SIGNIFICANCE
The read file is found to be busy (direct
access file only).
The READ file specified does not exist or
contains no data.
The tape is assigned to a control point
in PE (1600 cpi) mode and the drive is
unable to read the ID burst at load
point. The tape was assigned to a control
point in GE (6250 cpi) and the drive was
unable to read the ID burst at load point
or is unable to set the automatic gain
control using the automatic read
amplitude (ARA) burst.
The system is ready to process the next
command. This message is not issued in
the BATCH subsystem.
Unit dropped ready status.
RECLAIM has been aborted due to error or
user intervention.
An invalid argument was detected in the
RECLAIM command.
Normal completion.
An input record was encountered that
exceeded S or L output tape block size.
The record is too long for available
memory. In response to a WBR request, the
record length parameter was greater than or
equal to the job's field length. Available
memory is filled and the excess data is
skipped.
Informative message. LIBEDIT encountered n
records on a replacement file that were not
named in the directives and did not replace
old file records.
Multiple blocks per record have been
written on an S or L output tape.
Informative message.
Job recovery was successful.
The system is rerunning the job following a
level 3 deadstart.
Removable pack request without NA selected
causes resource overcommitment.
A RENAME of a PROC or TEXT type record was
attempted; this is not allowed.
A RENAME of a PROC type record was
attempted; this is not allowed.
Data will now be accepted by the network.
The same file was found twice during a
catalog search. This error can occur for
APPEND or REPLACE commands or macros after
a file is found and purged and the catalog
search is continued (error log and dayfile
message).
ACTION
Retry after file is not
busy.
Reenter command with a
correct read file.
Load the tape on another
drive or use a different
tape.
Enter your next command.
None.
Check the previous
message for a
description of the error.
Check the RECLAIM
command for correct
parameters, values, etc.
None.
Reduce input record
size, or use COPY
command to increase S or
L tape block size or
allow record splitting
with PO parameter.
Increase field length
and rerun.
Either change the
directives so that the
replacement file is a
no- re pl ace fil e or
include an *IGN0RE
directive listing the
records that are not to
be used.
None.
None.
Issue a STATUS directive
to dtermine the state of
the job, then proceed.
No action required.
Retry later or retry
with NA parameter on
ATTACH, DEFINE, etc.,
with PN parameter
specified.
None.
None.
None.
Inform site analyst. If
many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITIALIZE,
and full PFLOAD on the
device.
ROUTINE
SUBMIT
IEDIT
IMT
IAFEX
EDIT
1MT
RECLAIM
RECLAIM
RECLAIM
COPYBF
COPYB
CPMEM
COPYB
110
HELL07
1AJ
RESEX
LIBEDIT
CCP
PFM
60459680 H 8-61
![](asset-292.png)
MESSAGE
REPOSITION CORRECTED ERROR, filename AT
address.
REPRIEVE BLOCK ERROR.
REPRIEVE CHECKSUM BAD.
REQUEST IS VALID ONLY FROM A NETWORK
TERMINAL.
REQUEST UNDEFINED ON DEVICE, filename AT
address.
REQUESTED SECTION section.
REQUIRED FL EXCEEDS VALIDATED LIMIT.
RESEQ COMMAND ERROR.
RESEQ ERRORS.
SIGNIFICANCE
The tape drive is writing in a marginal
state. This message is intended to
prevent the generation of a marginal
tape by the subsystem and its devices.
This message is to be considered a
marginal drive indicator (MDI) and
requires immediate action.
An address is cut of range or there is an
incorrect parameter in the reprieve
parameter block at the time of an error.
The message is also issued if the specified
reprieve address itself is out of range.
(1AJ issues this message for all errors
except terminal interrupts processed by
1RI.)
The computed checksum does not agree with
the checksum specified in the parameter
block at the time of the error. (1AJ
issues this message for all errors except
terminal interrupts processed by 1RI.)
You attempted to enter an APPSW command
from a job that was not of interactive
origin type or from a terminal not
connected to NAM (for example, through
RDF). To use the APPSW command, your job
must be of interactive origin type and your
terminal must be connected to NAM.
The specified function cannot be performed
on the device on which the file resides.
The system provides a dump of the FET on
file OUTPUT.
This is the second line of a three-line
message:
MULTIFILE NOT FOUND,filename AT ADDRESS.
REQUESTED SECTION section.
FOUND SECTION section.
The system has reached the end of a
m u l t ifi l e s e t .
The job requires more field length than you
are authorized to have.
The RESEQ command contains a syntax error.
A resequencing error was encountered.
ACTION
Clean the drive and test to
ensure proper operation.
Inform the customer engineer.
Ensure parameter block
is correct.
ROUTINE
IMT
Ensure interrupt handler
is still intact. Ensure
that code in the area
for which checksum was
computed has not changed.
Login to IAF from a
terminal connected to
NAM.
Verify that valid device
is specified.
None.
Decrease the job size or
request the site to
increase your field
length validation.
Correct error and rerun.
Refer to preceding
message for more
specific information
about the error.
1AJ
1AJ
TLX
1MS
1MT
LIBEDIT
RESEQ
RESEQ
RESEQ NUMERIC PARAM ERROR. A parameter which is supposed to be numeric
contains a nonnumeric character.
Correct error and rerun. RESEQ
RESERVED FILE NAME.
RESERVED FILE NAME
RESEX ABORT - OPERATOR TERMINATION.
RESEX ABORT - SYSTEM RESOURCE LIMIT.
RESEX ABORT - TERMINAL INTERRUPT.
RESEX FAILURE.
RESOURCE DEMAND ERROR.
Read or destination file name matches an
internal scratch file. (ZZZZZG0-ZZZZZG7)
File name specified on SORT command is
reserved for use by the editor (ZZZZZGO,
ZZZZZG1).
The operator entered a DROP, KILL or RERUN
command. The system performed appropriate
cleanup procedures before termination.
The job terminated prematurely due to job
time limit, SRU Limit, or track limit. The
system performs appropriate cleanup
procedures before termination.
You entered the interrupt or terminate
sequence. The system performs appropriate
cleanup procedures before termination.
The resource executive (RESEX) has detected
a fatal error.
You attempted to decrease the number of
scheduled units to less than the number of
currently assigned units or increase the
number of scheduled units to a point where
a deadlock would occur.
Rename file and reenter
command.
Rename file and
rerun.
Determine reason for
operator action. Rerun
job if possible.
If error caused by SRU
or time limit, increase
resource limits. If
caused by track limit,
contact site analyst.
None.
Write a PSR.
Adjust RESOURC command
parameters accordingly.
IEDIT
SORT
RESEX
RESEX
PFM
RESEX
'*sa?\
B-62 60459680 H
![](asset-293.png)
MESSAGE
RESOURCE ENVIRONMENT ERROR.
RESOURCE NEGATIVE SHARE COUNT.
RESOURCE PF ERROR ec filename.
SIGNIFICANCE
System error.
RESOURCE SCRATCH FILE ERROR.
RESOURCE TYPE ERROR.
jsn RESTARTED FROM yy/mm/dd. hh.mm.ss.
RESUMING 7000 MODE..
RETRY APPLICATION SWITCH.
RFL BEYOND MFL.
RHF, jobn APPLICATION IS NOT NETTED ON
RHF, DUPLICATE NETON REQUEST.
RHF, FATAL SSF ERROR. FC=fc, RC=rc.
RHF, INVALID APPLICATION CALL TO RHF.
RHF, INVALID APPLICATION NAME ON NETON.
RHF, INVALID APPLICATION TABLE ADDRESS.
RHF, jsn INVALID FET PRAM. FET = ADDRESS
RHF, jsn INVALID HEADER ADDRESS address
The resource over commitment algorithm
indicates a greater number of users are
sharing a removable pack than are actually
sharing the pack.
PFM error ec occurred when attaching
resource file filename.
An empty entry has been found in the
overcommitment algorithm scratch file.
You specified an incorrect resource type.
The checkpoint job identified by jsn was
restarted from the checkpoint taken on the
specified date and time. This message is
issued whenever a checkpoint job is
restarted.
HELL07 is attempting to reestablish
connections with a SCOPE 2 job as a result
of a RESUME directive.
An attempt to switch applications failed
due to software error.
The RFL request is greater than the maximum
field length for a job step.
The application with job name or job
sequence name jobn requested an RHF
^rV function before requesting a NETON to RHF.
RHF aborts the application.
Two NETON requests were made for the same
application without an intervening NETOFF
request. RHF aborts the application.
System error.
An application issued an invalid RHF call.
The call may contain an incorrect RHF
function, a request (other than NETON) from
an application with an end-of-job connect
status, or an incorrect word count in the
RHF call. RHF aborts the application.
An application issued a NETON request using
an application name that was not in RHF's
configuration or that contained incorrect
characters. RHF aborts the application.
In an RHF call an application used an
incorrect application table address. The
address may be out of range or may point to
another application table. RHF aborts the
application.
System error.
System error.
ACTION
Reenter the command or
rerun the job. If the
problem recurs, inform
your site analyst or
contact Central Software
Support.
Reenter the command or
rerun the job. If the
problem recurs, inform
your site analyst or
contact Central Software
Support.
Rerun the job. If the
problem recurs, inform
a site analyst, write
a PSR and include
support material so that
CDC can duplicate the
problem.
Rerun the job. If the
problem recurs, inform
a site analyst, write
a PSR and include
support material so that
CDC can duplicate the
problem.
Ensure accuracy of
command.
None.
Wait for the HELL07
prompt to appear. If
the prompt does not
appeaar, check to ensure
that you have a SCOPE 2
job active.
Retry the APPSW
command. If the error
recurs, inform your site
analyst.
Increase maximum field
length with MFL command
or SETMFL macro.
None.
Remove the second NETON
request or add the
missing NETOFF request.
Inform site analyst.
Correct error in
application and retry.
Correct name in the
application NETON call
or add the application
name to RHF's
configuration.
ROUTINE
RESEX
Correct error
application.
in
RESEX
RESEX
RESTART
HELL07
TLX
CPM
RHF
RHF
RHF
Inform site analyst.
Inform site analyst.
RHF
RHF
60459680 H B - 6 3 |
![](asset-294.png)
MESSAGE
RHF, INVALID MINACN/MAXACN ON NETON.
RHF, INVALID SSF UCP ADDRESS address
RHF, INVALID TEXT ADDRESS address.
RHF, NETON SECURITY VIOLATION
RHF, NO APPLICATION ADDRESS IN RHF
CALL—EXTRA CHARGE
RHF, QUEUED MESSAGE LIMIT EXCEEDED
ROLLOUT FILE BAD.
ROUTE COMMAND ERROR.
ROUTE COMPLETE.
ROUTE COMPLETE. JSN IS jsn.
ROUTE *DC* INCOMPATIBLE WITH *EC*.
ROUTE INCORRECT *DO* PARAMETER.
ROUTE INCORRECT *EC* PARAMETER.
ROUTE INCORRECT *FC* PARAMETER.
ROUTE INCORRECT *IC* PARAMETER.
ROUTE INCORRECT KEYWORD.
ROUTE INCORRECT *OT* PARAMETER.
ROUTE INCORRECT SPACING CODE.
ROUTE INCORRECT *ST* PARAMETER.
ROUTE *OT* NOT ALLOWED.
ROUTE *PRI* IGNORED.
SIGNIFICANCE
The value for the minimum or maximum ACN in
the NETON request is outside the range
specified for the application. RHF aborts
the application.
System error.
System error.
An application is not validated to do a
NETON request. RHF aborts the application.
Informative message indicating an
application issued an RHF request (other
than NETON) without specifying an
application table address in the RHF call.
The application is charged less if it
specifies its application table address in
each RHF call.
An application exceeded the maximum number
of supervisory messages that are queued in
RHF. RHF aborts the application.
A job could not be rolled out correctly.
Format of the command is incorrect.
Informative message indicating ROUTE
operation has completed.
A ROUTE command queued a job for input.
The routed job has the job sequence name
jsn.
You specified a DC/EC combination that is
not valid.
The DO=lid parameter on the ROUTE command
has an incorrect format.
lid Logical identifier of remote
mainframe.
You specified an incorrect external
characteristics code on the ROUTE command.
The forms code specified on the c
not valid. \
You specified an incorrect internal
characteristics code on the ROUTE command.
Command contains a duplicate or incorrect
keyword.
A system table contains an incorrect value
for the job's origin type.
The SC=xx parameter on the ROUTE command
specified a spacing code greater than 77B.
The ST=lid parameter on the ROUTE command
has an incorrect format.
lid Logical identifier of remote
mainframe.
Your program is not system origin and only
system origin jobs can use the OT parameter.
Informative message listed for NOS/BE
compatibility.
ACTION
Correct the minimum or
maximum ACN in the
application's NETON
request.
Inform site analyst.
Inform site analyst.
None.
Modify the application
to issue more frequent
NETGET's for the
supervisory messages
queued in RHF.
Inform site analyst.
Check error log dayfile
for the job that was
aborted and the location
of the bad rollout file.
Check the ROUTE command
format in section 9.
None.
None.
If the DC parameter
implies a print or punch
disposition, the EC
parameter must
correspond.
Correct the format of
your DO=Lid
specification.
Correctly specify the
EC=ec parameter on the
ROUTE command.
Check the command format
and reenter command.
Correctly specify the
IC=ic parameter on the
ROUTE command.
Check the ROUTE command
format in section 9.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Correct the spacing code
specified on the ROUTE
command.
Correct the format of
your ST=Ud
specification.
Do not attempt to use
the OT parameter unless
you have system origin
privileges.
None.
ROUTINE
RHF
RHF
RHF
RHF
RHF
1RI
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
| B - 6 4 60459680 H
![](asset-295.png)
MESSAGE
ROUTE *REP* GT 31. DEFAULT USED.
ROUTE *ST* IGNORED.
ROUTE *TID* AND *FM/UN* CONFLICT.
ROUTE *TID/FM/UN* and *ID* CONFLICT.
ROUTE *TID=xx - VALUE IGNORED.
ROUTE UNDEFINED SERVICE CLASS.
ROUTE UNKNOWN PI PARAMETER, DEFAULT USED.
filename ROUTED. JSN IS jsn.
RPV - PREVIOUS ERROR CONDITIONS RESET.
RTIME nnnnnn.nnn SECS.
RUN COMPLETE.
SC ONLY PARAMETER VALID WITH JSN.
SCP INCORRECT TRANSFER ADDRESS.
SECONDARY APPLICATION ABORTED CONNECTION.
SECONDARY APPLICATION CONNECTION LIMIT.
SECONDARY APPLICATION FAILED.
SECONDARY APPLICATION NETTED OFF.
SECONDARY APPLICATION NOT AVAILABLE.
SECONDARY APPLICATION PROCESSING COMPLETE.
SECONDARY APPLICATION REFUSED CONNECTION.
SECURE FILES - CHECKPOINT ABORT.
SIGNIFICANCE
The repeat count specified was greater than
31; it has been set to 0. This condition
does not abort the program.
Informative message listed for NOS/BE
compatibility.
The TID parameter was specified with either
the FM or UN parameter. Neither one of
these parameters can be specified along
with TID.
The ID parameter was specified with the
TID, FM, or UN parameter.
Informative message listed for NOS/BE
compatibility.
The specified service class was not
recognized.
The ROUTE command contains an incorrect PI
parameter.
filename is the name of the file which was
routed, jsn is the job sequence name (JSN)
assigned to the file.
Normal message on RPV reset call.
Dayfile message output by RTIME command
giving the real-time seconds count.
Completion message for jobs in all
subsystems except batch.
You included an OT, L, or OP parameter
along with a JSN parameter on a CLASS
command. If you specify a JSN parameter,
the only other valid parameter for CLASS is
the SC parameter.
The SCP SSCR (RA + 51B) word contains
incorrect parameters on the completion
address for an SF.REGR, SF.SWPI or SF.SWPQ
function is no longer within the SCP field
length.
You intentionally or unintentionally
aborted the secondary connection. Possible
causes are security conflict or entry of a
BYE,ABORT command.
The application you specified on an APPSW
command is busy with the maximum allowable
number of terminal connections.
Your secondary application has failed,
probably due to a system problem.
The application was brought down by the
network operator.
The secondary application requested on an
APPSW command is either temporarily
unavailable or is not supported at your
site.
The connection to your secondary
application has been terminated normally.
The application refused to accept your
connection, possibly as a result of a
validation problem or security conflict.
Indicates a local file being checkpointed
had secure file status set.
ACTION
Use a repeat count less
than 32.
None.
Refer to section 9 for
the correct format of
the ROUTE command.
Refer to section 9 for
the correct format of
the ROUTE command.
None.
Correct and retry.
Check with central site
personnel to determine
the correct value to be
specified. The file was
routed with site default.
None.
None.
None.
None.
Correct the CLASS
command parameters and
resubmit.
Correct code error in
SCP.
If the abort was
unintentional and you
cannot establish a
cause, see your site
analyst.
Try again later.
Check with your site
analyst or try again
later.
Check with your site
analyst or try again
later.
Check with your site
analyst.
None.
Check with your site
analyst.
None.
ROUTINE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
ROUTE
MFILES
RPV
1AJ
CLASS
1AJ
TLX
TLX
TLX
TLX
CHKPT
zifi^v
60459680 H B-65
![](asset-296.png)
MESSAGE
SECURE MEMORY, DUMP DISABLED.
SECURITY CONFLICT.
SECURITY VIOLATION ON FILE filename AT
address.
SERVICE CLASS FULL.
SERVICE CLASS FULL.
SERVICE CLASS REQUIRED WITH JSN.
SERVICE LIMIT EXCEEDED.
SFM ABORTED.
SFM FAST ATTACH SYSTEM SECTOR ERROR.
SFM I/O SEQUENCE ERROR.
SFP CALL ERROR.
SFP/DOO BAD ERROR TEXT.
SFP/DOO ERROR TEXT NOT FOUND.
SFP/DOO ERROR TEXT NOT ON MASS STORAGE.
SFP/DOO INVALID MESSAGE NUMBER.
SFP/xxx INCORRECT FUNCTION CODE.
SFP/xxx INCORRECT ORIGIN CODE.
SIGNIFICANCE
You either attempted to dump memory
protected by the system, or entered a
memory dump request after a protected
command or from a terminal.
An attempted operation within the job would
have resulted in a violation of security
access levels or categories. The cause is
described in the immediately preceding
dayfile message.
One of the following:
You issued an OPEN request that
specified an access level for a file
that is not valid for your job.
You attempted to write on a direct
access permanent file whose access
level is lower than that of your job.
You attempted to change a job to service
class for which the service class limit has
already been reached.
The number of jobs in a particular service
class has reached its limit.
You entered a CLASS command with a JSN
parameter but did not include an SC
parameter. If the JSN parameter is
specified, an SC parameter must also be
included.
Your job exceeded the field length limits
for a job in its service class.
An error flag was set at SFM's control
point.
An unrecoverable error was detected when
trying to read the system sector of the
file being entered into fast attach
status. The file was entered, but, the
system sector pointers were not set. This
file may not be dumped properly by *PFDUMP*
when this occurs.
Action has been requested on a busy file.
System error.
The specified system text is not in the
correct format.
The specified system text could not be
found.
The specified system text does not reside
on mass storage.
The specified message number could not be
found on the system text.
The specified function code to the program
xxx is not defined.
Dayfile message indicating that the
function was incorrect for the job's origin.
ACTION
Refer to Security
Control in section 3 and
the load/dump Memory
commands in section 11.
To obtain memory dumps
from an interactive job,
include the dump command
in a procedure or in an
ENTER command.
Correct and retry.
Set the access level of
the file to the correct
value and retry.
Resubmit the CLASS
command at a later time.
Retry loging in at a
later time or contact
site administrator to
increase number of jobs
allowed in particular
service class.
Correct the CLASS
command parameters and
resubmit.
Reduce the job's field
length requirements and
resubmit.
Inform site analyst.
Inform site analyst.
ROUTINE
1AJ
Wait until file is not
busy and retry.
Write a PSR, including
a dump or support
materials to allow CDC
to duplicate the
problem.
RebuiId system text
using correct format.
Ensure the system text
specified is correctly
installed on the system.
If it is, write a PSR.
Move system text to mass
storage.
Ensure that 000 was
called with the correct
message number.
Ensure the correct
function code was used.
Write a PSR.
1AJ
1MS
CLASS
IAFEX
CLASS
1AJ
SFM
SFM
SFM
SFP
SFP
SFP
| 8 - 6 6 60459680 H
![](asset-297.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
/^$P*N
SFP/xxx PARAMETER ERROR.
SFP/PFE I/O SEQUENCE ERROR.
SFP/RPV UNABLE TO RESET, NOT REPRIEVED.
SFP/SRP SPECIAL REQUEST PROCESSING ERROR.
SFP/STS UNKNOWN DEVICE TYPE/NAME.
SHARE TABLE ERROR.
jsn SHARE TABLE MISMATCH.
SINGLE FRAME ERROR.
SL NOT VALIDATED.
SMP - ABORTED DUE TO ROLLOUT REQUEST
SPCW CALL ERROR.
SPECIAL REQUEST PROCESSING ERROR.
*SRU LIMIT*
ENTER S TO CONTINUE OR STOP TO ENO JOB STEP.
TYPED AHEAD INPUT MUST BE REENTERED.
STACK PURGING NOT DESELECTABLE.
pfn STAGE INITIATED.
STATION DOWN
STATUS ERROR, filename AT address.
STEP CONDITION.
Dayfile message indicating that the
parameter address was outside the field
length.
Action was requested on a file that was
already busy.
Dayfile message indicating that an attempt
was made to reset when the job had not been
reprieved.
Dayfile message indicating that the SPCW
word was busy.
The device code is not recognized by the
system.
System error.
A system error occurred while processing
the job with the specified job sequence
name (jsn).
A frame (NRZI only) containing all zeros
was read; data will be at least one frara
short. The dayfile message STATUS ERROR,
filename AT address precedes this message
and specifies the file (filename) and the
address.
The SRU limit requested exceeds that for
which you are authorized.
The rollout request flag is set in the
job's control point area. This may
happen as a result of terminal I/O or
*DIS* dropping while SMP is running.
A DNP= type call was made, and the program
called is either not in the CLD or does not
have a DMP= entry point defined.
Error encountered in *SPCW* call word.
You have exceeded your system resource unit
(SRU) limit during a terminal session.
You attempted to change the purging bit
with the EREXIT function. This cannot be
done on 6000 or CYBER 70 systems.
The file does not reside on disk. It is
currently being staged from alternate
storage to disk.
The SCOPE 2 station is not currently
executing.
An error was encountered during magnetic
tape processing. A second message line
describes the error in more detail.
Step mode flag set in the PSD register
caused the program to interrupt at the end
of a program instruction with an exchange
jump to EEA (the error exit address in the
exchange package).
If the code is yours,
find the source of
the error and fix it.
If the code is CDC's,
wrote a PSR.
Wait until the file is
not busy and retry.
If the code is yours,
find the source of the
error and fixt it.
If the code is CDC's,
write a PSR.
Write a PSR, including
a dump or support
materials to allow CDC
to duplicate the
problem.
Check device code for
validity.
Reenter the command or
rerun the job. If the
problem recurs, inform
yopur site analyst or
contact Central Software
Support.
Reenter the command or
rerun the job. If the
problem recurs, inform
your site analyst or
contact Central Software
support.
Retry or inform site
analyst.
Request smaller SRU
limit.
None.
Inform site analyst.
Inform site analyst.
To continue, allocate
nnnnn additional SRUs
with S,nnnnn command or
enter S alone to
allocate an
installation-defined
number of SRUs.
None.
Wait until stage
operation is complete.
Try to reenter the
command at a later time.
Retry or inform site
analyst.
Inform site analyst.
SFP
SFP
RESEX
RESEX
1MT
CPM
1AJ
1AJ
IAFEX
CPM
QUEUE7
1MT
1AJ
60459680 H B-67
![](asset-298.png)
MESSAGE
SUBMIT COMPLETE. JSN IS jobseq
SUBMIT ERROR - RETRY
SUBMIT ERROR - RETRY
SUBMIT FILE EMPTY.
SUBMIT NOT CALLED FROM HELL07
SUBSYSTEM ABORTED.
SYSTEM ABORT.
SYSTEM CHECKPOINT ABORT.
SYSTEM ERROR.
SYSTEM ERROR.
SYSTEM ERROR.
SYSTEM ERROR.
SYSTEM ERROR - NOTIFY SITE ANALYST.
SYSTEM FULL.
SYSTEM PROCEDURE ACCESS ERROR.
SYSTEM PROLOGUE NOT FOUND.
SYSTEM SECTOR ERROR.
SYSTEM SOFTWARE RERUN THRESHOLD EXCEEDED.
TABLE OVERFLOW.
SIGNIFICANCE
The SUBMIT command successfully queued the
file for input. The job sequence name
(JSN) for the job is jobseq.
An internal error occurred during SUBMIT
processing.
An internal error occurred during SUBMIT
processing.
An EOR or EOF was encountered on the submit
file before any data was found.
A SCOPE 2 job requiring terminal I/O was
not submitted through HELL07.
Your job was connected (either long term
connection or wait response set) to a
subsystem which aborted.
Possible causes include the following.
- Incorrect USER command.
- Attempt to access a restricted subsystem.
- Operator evicted job.
- Unrecognizable error flag.
- SSJ= block outside field length.
- 1RI detected a bad rollout file.
- 1R0 detected an unrecoverable extended
memory parity error during rollout of a
job's extended memory field length.
A subsystem has aborted due to a CHECK
POINT SYSTEM request initiated by the
operator.
A software or hardware system error
occurred. This message follows a
more specific message in the
dayfile.
ACTION
None.
Reenter the SUBMIT
directive. If the error
recurs, inform the site
analyst.
Reenter the SUBMIT
directive. If the error
recurs, inform the site
analyst.
Rewind submit file,
verify format of data
and that the file is a
local file, and retry
operation.
Resubmit the job through
HELL07.
Retry later.
If the cause was an
incorrect USER command
or an attempt to access
a restricted subsystem,
correct the job and
rerun. Otherwise,
inform a site analyst.
Refer to action for
the associated
message.
The command is not recognized by the system. Retry command.
LFM cannot complete the requested LFM
function because the calling program has a
DMP= entry point.
Requested function cannot be completed
because the calling program has a DMP=
entry point.
An internal software error has occurred.
System table is full; no new logins are
being accepted at this time.
Informative message indicating that the
system prologue did not execute.
A system prologue was defined but could not
be accessed.
The system sector of an indirect access
permanent file contains an error (error log
and dayfile message). This indicates that
the file has been destroyed.
The job has been rerun the maximum number of
times due to a software error. The maximum
is n-1, where the default for n is 2
(defined by MSER in common deck COMSMSC).
The job field length is too small to hold
the tables for processing the GTR command.
Inform site analyst
or write a PSR and
include support
material so that
CDC can duplicate
the problem.
Contact Central Software
Support.
Write a PSR and include
support materials to
allow CDC to duplicate
the problem.
Wait a few minutes and
try to login again.
Inform site analyst.
Inform site analyst.
Inform site analyst. If
many of these errors
occur, the site analyst
should perform a full
PFDUMP, total INITIALIZE,
and full PFLOAD on the
device.
Analyze the job output,
dumps, and listings to
determine cause.
Increase field length
and rerun job.
ROUTINE
SUBMIT
HELL07
DROP
HELL07
HELL07
1AJ
1AJ
1CK
MODVAL
PFM
IAFEX
BLANK
RESEX
LFM
DROP
QGET
IAF
CHARGE
CHARGE.
1AJ
GTR
,***5V
B-68 60459680 H
![](asset-299.png)
MESSAGE
TAPE BLANK LABELED.
TAPE BLOCK DEFINITION ERROR.
TAPE CLEANER FAULT, filename AT address.
r
TAPE FORMAT PROBABLY WRONG.
TAPE FUNC REJ function.
TAPE READ/WRITE ERROR (BLANK).
TCS INCORRECT REQUEST.
pfn TEMPORARY ERROR, TRY LATER.
TERMINAL BUSY.
TERMINAL INTERRUPT.
TERMINAL NOT ACTIVE.
TERMINAL TIME OUT - JSN=aaaa.
TERMINAL TIMEOUT IN nn SECONDS.
THE STATION IS NOT LOGGED INTO SCOPE 2
THIS CONNECTION IS ALREADY LOANED.
TIME LIMIT.
r
•TIME LIMIT*
ENTER T TO CONTINUE OR STOP TO END JOB STEP.
TYPED AHEAD INPUT MUST 8E REENTERED.
SIGNIFICANCE
Dayfile message indicating that the blank
label operation successfully completed.
You attempted to define data block size via
the FC or C keyword or noise block size via
the NS keyword in such a manner that the
system is unable to correctly define the
size of the data block. The omission of
the FC or C parameter on a command where it
is required also causes this message to be
issued.
Recovery from the tape CLEANER FAULT error
failed and TERMINATE,est. was entered; or,
the tape is not assigned to a job and the
tape cleaner failed to return to the parked
or stowed position after a tape load
operation or a high speed rewind operation.
Magnet will automatically unload the tape
and turn off the drive.
This message is issued in addition to one
of the following messages:
- BLOCK SEQUENCE ERROR, filename AT addr.
- BLOCK TOO LARGE, filename AT addr.
- WRONG PARITY, filename AT addr.
Tape drive rejected the attempted
function. Printed on the preceding line is
the name of the current program or command
buffer.
The BLANK label operation was unable to
complete successfully.
The translate commands (TCS) program was
called with an incorrect function code.
The system has detected a temporary
problem which prevents it from staging
your file (pfn) from permanent storage.
You attempted to send a message to a
terminal which was receiving output or had
an input request outstanding. The message
was lost.
RECLAIM processing was terminated due to a
terminal user break.
You attempted to send a message to an
inactive terminal.
The terminal has been logged off after no
input was received in the
installation-defined timeout period.
No input was received for several minutes.
The system will log you out after nn
seconds if no input is entered.
The SCOPE 2 station is not active.
This error indicates an abnormal condition
is occuring in IAF.
The execution time limit for a job step
expired resulting in job termination.
ACTION
None.
The system detected that the time limit for
the job step has expired.
Ensure accuracy of
command.
Mount the tape on a
different tape drive.
Ensure accuracy of
format (F) parameter on
command or macro.
Press the space bar to
retry the function.
Retry with the same tape
or use a different tape.
Correct the call to TCS
and retry.
Wait a few minutes and
try to att ach t he file
again.
Retry operation at a
later time.
None.
None.
Attempt recovery or log
in again.
Enter CR to prevent
logout.
Reenter the command
later when the station
is executing.
Inform site analyst.
If a time limit was set
for the job, include a
SETTL command requesting
a longer time limit for
the job step. If the
job step time limit was
the maximum for which
you are validated,
request a larger time
limit or decrease the
amount of processing to
be performed by the job
step.
To continue, reset time
limit with T,nnnnn
command or enter T alone
to set time limit to an
installation-defined
default.
ROUTINE
BLANK
RESEX
1MT
1MT
CTI
BLANK
1AJ
IAFEX
RECLAIM
IAFEX
IAFEX
IAFEX
QUEUE7
TLX
1AJ
IAFEX
60459680 H B-69
![](asset-29a.png)
MESSAGE
TIME LIMIT.
TIMEOUT.
SIGNIFICANCE
The job has reached its CPU time limit.
The user has not responded to a login
prompt whithin the system-specified time
interval (usually about 2 minutes) and the
terminal was disconnected.
ACTION ROUTINE
In c r e a s e y o u r jo b ' s ti me R E CL A I M
limit.
Respond more quickly to NVF
prompts.
TL NOT VALIDATED.
TLX - RPV ALREADY SET.
TN MUST BE SPECIFIED.
TN OR DN MUST BE SPECIFIED.
TOO MANY ARGUMENTS.
TOO MANY ARGUMENTS.
TOO MANY FILES
TOO MANY LI8RARY NAMES SPECIFIED.
TOO MANY PARAMETERS.
TOO MANY PERMANENT FILES.
TOO MANY USER LIBRARIES SPECIFIED.
TOO MANY 7000 JOBS...SUBMIT LATER
TOO MUCH INDIRECT ACCESS FILE SPACE.
TOO SMALL BUFFER SPACE
TOTAL ASSIGNED COUNT ERROR.
The time limit requested exceeds that for
which you are authorized.
Your program tried to set extended reprieve
when it was already set.
A COMPACT, DUMP, or REMOVE directive was
entered without a TN option specification.
A RECLAIM operation was attempted which
required a dump file name or tape number,
but neither was specified.
The number of arguments on the command
exceeds that allowed by the program.
The number of arguments in the command
exceeds GOB.
You have attempted to route a second file
to SCOPE 2 when you already have a file
routed to SCOPE 2.
The number of libraries specified on the
LIBRARY command exceeds the maximum of 24.
The current global library set remains in
effect.
More parameters were entered (including
null parameters) than are allowed for
command.
The number of files in your catalog exceeds
your limit.
The number of user libraries specified
exceeds the number allowed based on the
number of system libraries specified. The
current global library set remains in
effect.
The SCOPE 2 limit for the number of
concurrent connected jobs has been
reached. The system will continue to
reject the SUBMIT directive until the
connected job count is reduced.
The cumulative size of the indirect access
files in your catalog exceeds your limit.
Internal error.
System error (sum of individual resource
assigned counts differs from total assigned
count in demand file entry).
Request smaller time
limit.
None.
Correct the directive
and retry.
Retry after specifying
the file name or tape
number.
Reformat the command
with an allowable number
of arguments.
Check format of command
and reduce the argument
count.
Wait until the first job
completes before
submitting another job.
Correct the command.
Ensure accuracy of entry.
Purge one or more
permanent files to
allow you to
save or define
additional files.
Correct the command.
CPM
TLX
Retry later.
Purge or shorten
one or more indirect
access files to
allow additional
permanent file space.
Submit a PSR with
information on how
to duplicate the
problem.
Reenter the command or
rerun the job. If the
problem recurs, inform
your site analyst or
RECLAIM
RECLAIM
SUBMIT
TCS
1AJ
HELL07
LIBRARY
GTR
IAFEX
NOTE
PFM
LIBRARY
HELL07
PFM
IEDIT
RESEX
TOTAL DEMAND COUNT ERROR. System error (sum of individual resource
demand counts differs from total demand
count in demand file entry).
Reenter the command or
rerun the job. If the
problem recurs, inform
your site analyst or
contact Central Software
support.
^^*\
B-70 60459680 H
![](asset-29b.png)
/§ssfey MESSAGE
TRACK LIMIT.
TRACK LIMIT, LVLX.
TRAILER BLOCK COUNT ERROR, filename AT
address.
TRMDEF COMPLETE.
>!^^5v
TRMDEF ERRORS.
TRMDEF REQUIRES JOB TO BE ON-LINE
TTest, ASSIGNED TO filename, VSN=vsn.
T76 RETURNED UNKNOWN ERROR OF nn
UNABLE TO DROP JOB.
UNABLE TO PROCESS TERMINAL FILE.
UNABLE TO READ IQFT FILE.
SIGNIFICANCE
No allocatable tracks remain on your
permanent file equipment (error log and
dayfile message).
1MS is waiting for temporary file mass
storage space on any mass storage device
with access level LVLX.
The block count in the E0F1 or EOV1 label
did not match the block count maintained by
the tape executive during the read
operation.
The TRMDEF command was processed with no
errors.
Errors were found in the TRMDEF command.
Additional error messages are listed at the
terminal or, if the L parameter was
included, on the output file specified by L.
A TRMDEF command was issued while the job
-was detached. This caused the job to be
suspended. When the job is recovered, this
message is issued and the command processed.
The specified file name is assigned to the
tape volume with the specified VSN that is
mounted on tape drive TTest (the
seven-track (MT) or a nine-track (NT) tape
unit with EST ordinal est).
A system error has occurred between NOS and
the SCOPE 2 station, nn is a two-digit
error code meaningful to the site analyst.
You attempted to drop the job associated
with your terminal. It is not possible.
The file you specified in a SECHDR command
is currently assigned to a terminal.
An attempt to initialize inactive queues
failed because the IQFT file could not be
read.
ACTION
None; job will con
tinue as tracks
become available.
If problem persists,
contact Central
Software Support.
Inform site analyst.
Inform site analyst.
ROUTINE
PFM
1NS
1HT
None.
Correct error and retry.
None.
Informative message.
Processing of the tape
file can begin.
Reenter the command. If
the same message is
returned, inform the
site analyst.
If you want to drop
another one of your
jobs, use ENQUIRE,JSN to
ascertain their job
names.
Assign the file to an
appropriate device and
reenter the command.
Retry operation.
TRMDEF
TRMDEF
QUEUE7
DROP
SECHDR
INS
NSI
UNABLE TO RECOVER YOUR JOB
UNDEFINED ORIGIN TYPE
UNDEFINED SERVICE CLASS.
The SCOPE 2 job was either in execution and
could not be rerun, or, due to certain file
functions performed prior to the recovery
mode, was not recoverable.
Origin type mnemonic specified is undefined.
You specified an undefined service class
value for the SC parameter on the CLASS
command.
None.
Correct origin type and
retry.
Correct the SC parameter
value and resubmit.
HELL07
CLASS
CLASS
UNIDENTIFIED PROGRAM FORMAT.
UNIT HAS MOTION PROBLEMS.
The file you requested to be loaded was ir
an unrecognizable format.
The tape unit cannot properly write the
tape. The dayfile message STATUS ERROR, -
filename AT address precedes this message
and specifies the file (filename) and the
address.
Check the format of the 1AJ
file.
R e s ub m it y o u r j ob , u si n g 1 M T
a different tape unit or
inform site analyst.
UNIT HUNG UP ON EOP OR BUSY, filename AT
address.
Unit did not receive EOP on unit busy. Inform site analyst. 1MT
UNIT PROBLEMS. Unit check bit is set in detailed status
(67x units only). The dayfile message
STATUS ERROR, filename AT address precedes
this message and specifies the file
(filename) and the address.
Try another unit or
inform site analyst.
UNKNOWN ACCESS CATEGORY NAME. You specified an undefined access category
name on a SETPFAC command.
Reenter the command with
the correct access
category name(s).
60459680 H B - 7 1 |
![](asset-29c.png)
MESSAGE
UNKNOWN ACCESS LEVEL NAME.
UNKNOWN CODE ccc, FILE filename, RECORD
recordnumber, LINE linenumber.
UNKNOWN DEVICE TYPE - filename.
UNKNOWN OPTION - x.
UNKNOWN SECONDARY APPLICATION.
UNLABELED TAPE REQUIRED - filename.
UNNECESSARY CIO FCT. nnn ON filename AT
address.
UNRECOGNIZABLE TYPE SPECIFIED.
UNRECOGNIZED BACKSPACE CODE.
UNRECOGNIZED CODE SET PARAMETER.
UNRECOGNIZED TERMINAL MODEL.
UNRECOGNIZED TERMINATION CONDITION.
UNRECOVERABLE ERROR ON filename.
UNRECOVERED MASS STORAGE ERROR.
UNSUPPORTED VALUE ON - xx.
UNTERMINATED PROCEDURE CALL.
UNUSUAL END-OF-FILE ENCOUNTERED.
UPDATED - type/name
UPROC COMPLETE.
**** USE *FILINFO* IN PLACE OF *PRM* CALL
SIGNIFICANCE
The job specified an undefined access
level name.
Character code ccc is not a valid character
code in the character code set specified by
PC=cs1 in the FCOPY command.
filename
recordnumber
linenumber
File that contains the
code.
Record that contains the
code.
Line that contains the
code.
File filename was specified as either the
old file or the correction file and is not
a mass storage file.
You specified an undefined option in a
SECHDR command.
x undefined option specified.
On an APPSW command, you specified a
secondary application that does not exist.
An S tape used for E, B, or X tape
conversion must be unlabeled.
The read or write CIO function specified by
nnn was unnecessary, since your I/O buffer
was already full (read) or empty (write)
and no data could be transferred for this
CIO call. The message is issued to the job
dayfile only if analyst logging is enabled
on the system (console entry).
The type of the source file was not valid.
The specified backspace code was not 0, 1,
2, or 3.
Parameters PC=cs1 and NC=cs2 specify an
unsupported conversion.
You entered an invalid terminal model
mnemonic as a parameter in the SCREEN
or LINE command.
The specified termination record count or
record type was not recognized.
An unrecoverable error such as wrong
parity, density change, or ready drop was
detected on the input file.
A command or overlay calls a system library
program. During the load, an unrecoverable
read error occurred.
The value of the attribute is recognized
but not supported by TRMDEF.
xx Attribute mnemonic.
A BEGIN or name call to an interactive
procedure did not have a terminator. One
or more parameters may be incorrect or
omitted.
GTR detected an EOF mark not preceded by an
EOR mark.
The record with type and name on the old
file was replaced with the matching record
from the replacement file.
The prolog you specified in the UPROC
command has been successfully assigned to
your user name.
You used a *PRM* call to obtain file
permission data.
ACTION ROUTINE
Reenter the command with MLSEXEC
the correct access level MSI
name. PFS
RESEX
PFILES
Correct file and retry.
Choose an old file and a
corr ec tio n file that
reside on mass storage.
Reenter the command with
correct option.
Correctly specify a
secondary application.
Use unlabeled tape.
Ignore or correct
program to be more
efficient.
Check type of source
file.
Refer to the COPYB
coramand description,
correct the error, and
retry.
Verify conversion and
retry.
Retry with valid
mnemonic.
Refer to the COPYB
command description,
correct the error, and
retry.
Either the tape was bad
or the tape drive is
malfunctioning.
Inform site analyst.
None.
Check parameters displayed
on screen and verify or
correct before proceeding.
Dump file to determine
file format error.
None.
None.
Use a *FILINF0* call to
obtain the desired
information.
FCOPY
LIBEDIT
TLX
COPYB
1MS
L072
COPYB
FCOPY
CONTROL
COPYB
COPYB
1AJ
TRMDEF
CCL
GTR
COPYL
COPYLM
MODVAL
/"*^>>.
B-72 60459680 H
![](asset-29d.png)
MESSAGE SIGNIFICANCE ACTION ROUTINE
/gP5\
**** USE *FILINFO* IN PLACE OF *STS* CALL
USE SCOPY FOR FILE STRUCTURE.
USER ACCESS NOT POSSIBLE - CONTACT
NETWORK ADMIN.
USER ACCESS NOT VALID.
USER ACCESS NOT VALID.
USER ACCESS NOT VALID.
USER ACCESS NOT VALID.
USER ACCESS NOT VALID.
USER ACCESS NOT VALID.
USER ACCESS NOT VALID.
USER BREAK TWO ENCOUNTERED.
USER CANNOT SWITCH FROM SECONDARY
APPLICATION.
USER COMMAND HAS NOT BEEN EXECUTED.
USER DAYFILE PROCESSED.
USER DIRECTIVE INCORRECT.
USER LIBRARY NOT FOUND.
USER LIBRARY NOT ON MASS STORAGE.
60459680 H
You used a *STS* call to obtain file
allocation data.
You entered R parameter on the LIST
command. The function of the LIST,R
command has been replaced by the SCOPY
command.
Either the application rejected the
connection, or the security count was
exhausted, or an invalid application
name was specified in the local
configuration file (LCF).
You tried to perform an operation for which
you are not authorized. Possible causes
include attempts to access a file or
equipment which you are not authorized to
access.
You tried to perform an operation for which
you are not authorized. Possible causes
include attempts to
- Run a system origin job from nonsystem
origin.
- Access a restricted subsystem without
proper validation.
- Use the V carriage control character
without validation.
The user name or password could not be
validated, or a secondary USER command was
encountered while secondary USER commands
were disabled.
You attempted to use RECOVER in a
noninteractive job.
You made an unauthorized call to a utility
reserved for system origin privileged users.
The SRU or time limit request is outside of
your validated range.
One of the following:
You are not authorized to create
direct access or indirect access
files.
You are not authorized to access
auxiliary devices.
Your job made a CATLIST request for
permit information on a file that
has a higher access level than that
of your job.
Informative message.
You attempted to enter an APPSW command
from a secondary application.
A SUBMIT cUSER directive could not be
processed because your job had not
processed a USER command before calling
SUBMIT.
The job's dayfile dump is complete.
You did not furnish the accounting data
needed to process the job.
The requested entry point is in the
directory file, but the associated user
library is not present.
The requested entry point is in the
directory file, but the associated user
library is not on mass storage.
Use *FILINF0* calls to
obtain the desired data.
Enter SC0PY,fn. for file
structure information.
Contact the network
administrator.
Ensure accuracy of
command or determine
proper validation
requirements via LIMITS
command.
Ensure accuracy of
command or macro, or
determine proper
validation requirements
via LIMITS command.
Verify that user name
and password are valid.
If secondary USER
commands are disabled,
ensure that no secondary
USER commands are
present.
Initiate an interactive
job to use RECOVER.
Ensure that you have
system origin privileges
before using this
utility.
Retry with a lower value.
Contact your site
administration about
obtaining the necessary
validations. For
CATLIST request,
resubmit the request
after raising your job's
access level.
None.
To return to your
primary application, log
out of your secondary
application. If you
wish to switch to a
third application, you
can enter another APPSW
command from your
primary application.
Enter a valid USER
command, then retry
SUBMIT.
Check file and add a
USER command.
Regenerate the user
library.
Assign the user library
to a mass storage device.
SFP
IAFEX
DSD
EXUBUT
EXCSLV
MSI
QFSP
RESEX
1MA
IAFEX
CPM
RECOVER
FOTD
SUBSYST
CONTROL
PFM
1AJ
TLX
SUBMIT
DAYFILE
SUBMIT
1AJ
1AJ
B-73
![](asset-29e.png)
MESSAGE
USER NOT VALIDATED FOR DETACHED SERVICE
CLASS.
USER NOT VALIDATED FOR INTERACTIVE SERVICE
CLASS.
USER NOT VALIDATED FOR SECONDARY
APPLICATION.
USER PROLOGUE NOT FOUND.
USER RETRY LIMIT.
USER SECURITY COUNT EXHAUSTED.
USER VALIDATION LIMIT EXCEEDED.
VALIDATION FILE BUSY - TRY AGAIN LATER
cmd VALUE INAPPROPRIATE
VE ENTRY REQUIRED.
VERIFY ARGUMENT ERROR.
VERIFY ERRORS.
VERIFY FILE NAME CONFLICT - filename.
VERIFY FL ABOVE USER LIMIT.
VERIFY GOOD.
VSN FILE ERROR.
WAIT
SIGNIFICANCE
User is not validated for detached service
class (DI).
User is not validated for interactive
service class (TS).
You submitted an APPSW command specifying
an application for which you are not
validated.
Although a user prologue was defined,
it could not be accessed.
Four unsuccessful attempts at login were
made after which the terminal was
disconnected from the system.
The security count for the user name
specified has been decremented to zero.
You are denied all access to the operating
system until the operator resets your
security count.
A validation limit has been reached for a
job step or account block. The Limit is
either a time limit or an SRU limit.
The validation routine (MODVAL) was unable
to access the validation file to perform
the requested UPROC, PASSWOR, or CHVAL
operation.
The value you specified in the terminal
definition command cmd is not appropriate
for your terminal.
A level 0 deadstart is required to add or
change a CMRDECK VE entry.
One or more of the parameters specified in
a VERIFY was not recognized.
Verification errors were encountered during
comparison of date/records/files.
Either you tried to process two files
having the same name or you specified a
reserved file name.
Field length for L or F tape verify exceeds
your current maximum.
Verify completed with no errors found.
System error (VSN file entry does not match
job identification).
The system is waiting for system resources
to become available.
The network is unable to accept any further
data from your terminal. Data that was
entered is discarded. This is normally a
temporary situation caused by buffer
shortages in the host or the network.
ACTION
Have site administrator
validate user for
detached service class
if appropriate.
Have site administrator
validate user for
interactive service
class if appropriate.
To check your current
validations, enter a
LIMITS command. If you
require validation for
additional applications,
see your site
administration.
Delete the prologue
definition or create a
prologue file.
Obtain accurate login
information before
attempting to log in.
Inform site analyst if
problem persists.
Contact site personnel
to reestablish access.
If appropriate, have
site administrator
increase validation
limits.
Try again later.
Choose an appropriate
value (refer to appendix
J).
Level 0 deadstart is
required.
Compare the parameters
specified with the
command description.
Check output file for
errors.
Correct the command so
all files have a unique
name.
Use MFL to increase
maximum field length or
reduce block size on L
or F tapes.
None.
Reenter the command or
rerun the job. If the
problem recurs, inform
your site analyst or
contact Centrat Software
Support.
None.
Wait for the REPEAT,
message.
IAFEX
IAFEX
TLX
CHARGE
NETVAL
CPM
IAFEX
MODVAL
CCP
REC
VERIFY
VERIFY /£<3Sy
VERIFY
RESEX
IAFEX
CCP
B-74 60459680 H
![](asset-29f.png)
MESSAGE
pfn WAITING ALTERNATE STORAGE EXEC.
WAITING FOR DATABASE NON-BUSY.
WAITING FOR MAGNET.
WAITING FOR NFL.
WAITING FOR PN=packname, type.
WAITING FOR RESOURCE FILE.
WAITING FOR RESOURCES.
WAITING FOR SERVICE CLASS TO CHANGE TO x.
WAITING FOR STORAGE.
WAITING FOR STORAGE (ECS).
WAITING FOR STORAGE (EM).
WAITING FOR VALIDATION FILE.
WAITING FOR VSN= vsn, type.
WAITING - INACCESSIBLE DEVICE.
WAITING ON TRACK LIMIT.
WAITING - SERVICE LIMIT.
SIGNIFICANCE
The file must be staged from alternate
storage to disk and the alternate storage
executive is not currently available to
perform the stage operation.
The specified database is busy (for
example, it may be attached in write mode
to another job). RECLAIM continues to
attempt to attach the file at ten second
intervals until the file becomes available
or you interrupt RECLAIM.
The job is waiting for the magnetic tape
subsystem to be activated.
Informative message stating that your job
has been delayed and/or rolled out
waiting for NFL space. The job has not
been aborted; it will eventually continue.
The message is visible via ENQUIRE.
The job is waiting for the operator to
mount pack packname on device type type.
The job is waiting for the resource demand
file or VSN file to become available.
The job is waiting for sufficient resources
to allow assignment of the tape/pack
without causing a system deadlock.
Service class x has reached its service
limit, and job is waiting for a place in it.
Issued to DSD B and J displays. BIO is
waiting to increase its field length or for
a buffer to become available.
The job is waiting for additional extended
memory to become available.
The job is waiting for additional central
memory to be made available.
The job is waiting for the validation file
to become available to process a UPROC,
PASSWOR or CHVAL command.
The job is waiting for the operator to
mount the tape with VSN vsn on the
specified type (MT, HD, PE, or GE). VSN=
SCRATCH indicates that any scratch tape is
acceptable.
Your job has been rolled out waiting for an
inaccessible mass storage device. The
device is off, down, or is encountering
hardware errors.
The job is waiting for additional tracks on
the familyname device containing the
resource demand and VSN files.
The job has reached a service limit for
central memory or extended memory field
length.
ACTION ROUTINE
Wait for executive to be PFM
started or inform site
operator that the
alternate storage
executive should be
initialized.
Wait for the specified RECLAIM
database to become
available or terminate
RECLAIM processing.
Wa it f or t h e o p er a to r t o R ES E
activate MAGNET or
terminate job.
None. PFM
W a i t u n t i l t h e o p e r a t o r R E S E X
mounts the requested
pack or terminate job.
Wait until resource file RESEX
becomes available or
terminate job. To
operator: If job is not
rolled out and this
message persists, inform
site analyst or drop the
job. If the operator
decides to override an
interrupted job at this
point, the preview data
in the demand file is
not cleared and the E,P
display continues to
show the VSN request
associated with the job
until you log off or
issue a subsequent
request for tape or pack.
Wait until the resources RESEX
become available or
terminate job.
None. CLASS
None. 110
Wait for additional 1MA
storage or terminate job.
Wait for additional IMA
storage or terminate job.
Try again later. MODV
Wa i t f or t h e o p e ra to r t o R E S EX
mount the tape or
terminate the job.
Inform site analyst. 1RJ
Wait for the additional RESEX
tracks or terminate job.
Detach the job for later 1TA
processing or abort the
job step.
60459680 H B - 7 5 |
![](asset-2a0.png)
MESSAGE
WRITE-DOWN OF DATA PROHIBITED.
WRITE ID BURST FAILURE, filename AT address.
WRITE ON READ-ONLY FILE filename AT address.
WRITE OVER LABEL ILLEGAL.
WRITE TAPE MARK ERROR.
I WRITE TAPE MARK FAILURE, filename AT
address.
I WRITE VERIFY FAILURE, filename AT address.
WRONG PARITY, filename AT address.
XD/XT EXCEEDS MAXIMUM.
XL BUFFER/FET PARAMETER ERROR, filename
AT address.
YOUR PASSWORD WILL BE EXPIRED yy/mm/dd.
ZZZZZLD NOT ON MASS STORAGE.
200 BPI WRITE INCORRECT.
7000 EXITING
7000 JOB EARLY ABORT
7000 JOB ERROR - ERROR=xxx
SIGNIFICANCE
One of the following:
On an APPEND or REPLACE command or
macro, the access level of the local
file is higher than the access level
of the permanent file.
On a DEFINE command or macro, the
access level of a local file having
the same name as the file specified
has a lower access level than the
job.
- On a CHANGE, PERMIT, or SETPFAC
command or macro, the access level
of the specified permanent file is
lower than that of the job.
The tape driver is unable to correctly
write the PE (1600 cpi) or GE (6250 cpi)
identification tracks or the automatic
read amplitude (ARA) burst at load point.
Either you attempted to write on a file
with write lock-out, or the direct access
file was not attached in write mode.
You attempted to write over the V0L1 label.
The tape subsystem was unable to write a
tape mark on the tape being written,
probably as a result of a bad tape.
An error occurred after six attempts to
write a tape mark and read it back.
The tape was positioned properly, but
the current block cannot be read
because of a triple track error.
A seven-track tape is being read in
opposite parity from which it was written.
The XD parameter for a password or file
permission is more than the maximum number
of days past the current date, or the XT
parameter is larger than the maximum
allowed.
One of the following:
- HDR1 label in extended label buffer or
FET contains a nonnumeric display code
value in a numeric field.
- Character count in header word preceding
labels in the extended label buffer does
not equal 80.
Ypu should change your password prior to
this date. If you donot change your
password prior to this date, you will
not be able to login.
The directory file ZZZZZLD does not reside
on mass storage.
The tape unit (667 or 677) cannot record
data at 200 bpi.
Indicates normal completion of a SCOPE 2
job step.
A submitted job aborted before it was able
to connect to the terminal.
The SCOPE 2 connected job encountered error
condition xxx, as described in the Record
Manager section of the SCOPE 2 Diagnostic
Handbook.
ACTION
Retry using a higher
access level for the
permanent file (APPEND
or REPLACE), or change
the job's access level
and then retry (DEFINE,
CHANGE, PERMIT, or
SETPFAC).
ROUTINE
PFM
Load the tape on another
drive or use a different
tape.
Reattach file in write
mode or clear write
interlock.
Have the operator blank
label the tape.
Replace tape and try
again. If problem
persists, try another
tape drive. If problem
still occurs, inform
site analyst.
Clean the tape drive or use
a cleaned or new tape.
Clean the tape drive or use
a cleaned or new tape.
Ensure accuracy of
format parameter (F> on
command or macro.
Correct XD or XT
parameter and retry.
Correct condition that
caused error and retry.
Contact site personnel
if you are not familiar
with your site policy
regarding passwords.
Assign the directory
file to mass storage.
Specify a different tape
density.
None.
Check the job's dayfile
for an error indication.
Refer to the SCOPE 2
Diagnostic Handbook.
1MT
1MS
IAFEX
1MT
1MT
1MT
1MT
1MT
PFM
1MT
CHARGE
1AJ
1MT
HELL07
HELL07
HELL07
B-76 60459680 H
![](asset-2a1.png)
0^ MESSAGE
USER NOT VALIDATED FOR DETACHED SERVICE
CLASS.
USER NOT VALIDATED FOR INTERACTIVE SERVICE
CLASS.
USER NOT VALIDATED FOR SECONDARY
APPLICATION.
USER RETRY LIMIT.
USER SECURITY COUNT EXHAUSTED.
USER VALIDATION DENIED.
VALIDATION FILE BUSY - TRY AGAIN LATER
cmd VALUE INAPPROPRIATE
VERIFY ARGUMENT ERROR.
VERIFY ERRORS.
VERIFY FILE NAME CONFLICT - filename.
VERIFY FL ABOVE USER LIMIT.
VERIFY GOOD.
VSN FILE ERROR.
WAIT
WAIT..
SIGNIFICANCE
User is not validated for detached service
class (DI).
User is not validated for interactive
service class (TS).
You submitted an APPSW command specifying
an application for which you are not
validated.
Four unsuccessful attempts at login were
made after which the terminal was
disconnected from the system.
The security count for the user name
specified has been decremented to zero.
You are denied all access to the operating
system until the operator resets your
security count.
The job calling CVL is not valid to do so.
Either the job must be system origin, or
the user must have system origin
privileges. Sumbit the job when the system
is in engineering mode. In addition, the
user must be validated to run on-line
diagnostics.
The validation routine (MODVAL) was unable
to access the validation file to perform
the requested UPROC, PASSWOR, or CHVAL
operation.
The value you specified in the terminal
definition command cmd is not appropriate
for your terminal.
One or more of the parameters specified in
a VERIFY was not recognized.
Verification errors were encountered during
comparison of date/records/files.
Either you tried to process two files
having the same name or you specified a
reserved file name.
Field length for L or F tape verify exceeds
your current maximum.
Verify completed with no errors found.
System error (VSN file entry does not match
job identification).
The system is waiting for system resources
to become available.
The network is unable to accept any further
data from your terminal. Data that was
entered is discarded. This is normally a
temporary situation caused by buffer
shortages in the host or the network.
ACTION ROUTINE
Have site administrator IAFEX
validate user for
detached service class
if appropriate.
Have site administrator IAFEX
validate user for
interactive service
class if appropriate.
T o c h e c k y o u r c u r r e n t T L X
validations, enter a
LIMITS command. If you
require validation for
additional applications,
see your site
administration.
Obtain accurate login NETVAL
information before
attempting to log in.
Inform site analyst if
problem persists.
Contact site personnel CPM
to reestablish access.
I n s u r e t h e u s e r i s v a l i d C V L
to run on-line
diagnostics. If so,
submit the job from the
console, or if the user
has system origin
privileges, set
engineering mode (Refer
to ENABLE command in
Analysis Handbook).
Try again later. MODVAL
Choose an appropriate CCP
value (refer to appendix
J).
Compare the parameters VERIFY
specified with the
command description.
C h e c k o u t p u t fi l e f o r V E R I F Y
errors.
Correct the command so VERIFY
all files have a unique
name.
U s e M F L t o i n c r e a s e V E R I F Y
maximum field length or
reduce block size on L
or F tapes.
None. VERIFY
Reenter the command or RESEX
rerun the job. If the
problem recurs, inform
your site analyst or
contact Central Software
Support.
None. IAFEX
Wait for the REPEAT.. CCP
message.
(
60459680 F B-77
![](asset-2a2.png)
MESSAGE
pfn WAITING ALTERNATE STORAGE EXEC.
WAITING FOR MAGNET.
WAITING FOR NFL.
WAITING FOR PN=packname, type.
WAITING FOR RESOURCE FILE.
WAITING FOR RESOURCES.
WAITING FOR SERVICE CLASS TO CHANGE TO x.
WAITING FOR STORAGE.
WAITING FOR STORAGE (ECS).
WAITING FOR STORAGE (EM).
WAITING FOR VALIDATION FILE.
WAITING FOR VSN= vsn, type.
WAITING - INACCESSIBLE DEVICE.
WAITING ON TRACK LIMIT.
SIGNIFICANCE
The file must be staged from alternate
storage to disk and the alternate storage
executive is not currently available to
perform the stage operation.
The job is waiting for the magnetic tape
subsystem to be activated.
Informative message stating that your job
has been delayed and/or rolled out
waiting for NFL space. The job has not
been aborted; it will eventually continue.
The message is visible via ENQUIRE.
The job is waiting for the operator to
mount pack packname on device type type.
The job is waiting for the resource demand
file or VSN file to become available.
The job is waiting for sufficient resources
to allow assignment of the tape/pack
without causing a system deadlock.
Service class x has reached its service
limit, and job is waiting for a place in it.
Issued to DSD B and J displays. BIO is
waiting to increase its field length or for
a buffer to become available.
The job is waiting for additional extended
memory to become available.
The job is waiting for additional central
memory to be made available.
The job is waiting for the validation file
to become available to process a UPROC,
PASSWOR or CHVAL command.
The job is waiting for the operator to
mount the tape with VSN vsn on the
specified type (MT, HD, PE, or GE). VSN=
SCRATCH indicates that any scratch tape is
acceptable.
Your job has been rolled out waiting for an
inaccessible mass storage device. The
device is off, down, or is encountering
hardware errors.
The job is waiting for additional tracks on
the familyname device containing the
resource demand and VSN files.
ACTION ROUTINE
Wait for executive to be PFM
started or inform site
-operator that the
alternate storage
executive should be
ilitialized.
Wait for the operator to RESEX
activate MAGNET or
terminate job.
None. PFM
Wait until the operator RESEX
mounts the requested
pack or terminate job.
Wait until resource file RESEX
becomes available or
terminate job. To
operator: If job is not
rolled out and this
message persists, inform
site analyst or drop the
job. If the operator
decides to override an
interrupted job at this
point, the preview data
in the demand file is
not cleared and the E,P
display continues to
show the VSN request
associated with the job
until you log off or
issue a subsequent
request for tape or pack.
Wa it u nt i l t h e r e so u r c e s R E S E X
become available or
terminate job.
None. CLASS
None. 110
Wait for additional 1MA
storage or terminate job.
Wait for additional 1MA
storage or terminate job.
Try again later. MODVAL
Wait for the operator to RESEX
mount the tape or
terminate the job.
Inform site analyst. 1RJ
Wait for the additional RESEX
tracks or terminate job.
■/tfS^\
B-78 60459680 F
![](asset-2a3.png)
MESSAGE
WRITE-DOWN OF DATA PROHIBITED.
WRITE ON READ-ONLY FILE filename AT address.
WRITE OVER LABEL ILLEGAL.
WRITE TAPE MARK ERROR.
WRONG PARITY, filename AT address.
XD/XT EXCEEDS MAXIMUM.
XL BUFFER/FET PARAMETER ERROR, filename
AT address.
ZZZZZLD NOT ON MASS STORAGE.
200 BPI WRITE INCORRECT.
7000 EXITING
7000 JOB EARLY ABORT
7000 JOB ERROR - ERROR=xxx
/$&&\
SIGNIFICANCE
One of the following:
On an APPEND or REPLACE command or
macro, the access level of the local
file is higher than the access level
of the permanent file.
On a DEFINE command or macro, the
access level of a local file having
the same name as the file specified
has a lower access level than the
job.
- On a CHANGE, PERMIT, or SETPFAC
command or macro, the access level
of the specified permanent file is
lower than that of the job.
Either you attempted to write on a file
with write lock-out, or the direct access
file was not attached in write mode.
You attempted to write over the VOL1 label.
The tape subsystem was unable to write a
tape mark on the tape being written,
probably as a result of a had tape.
A seven-track tape is being read in
opposite parity from which it was written.
The XD parameter for a password or file
permission is more than the maximum number
of days past the current date, or the XT
parameter is larger than the maximum
allowed.
One of the following:
- HDR1 label in extended label buffer or
FET contains a nonnumeric display code
value in a numeric field.
- Character count in header word preceding
labels in the extended label buffer does
not equal 80.
The directory file ZZZZZLD does not reside
on mass storage.
The tape unit (667 or 677) cannot record
data at 200 bpi.
Indicates normal completion of a SCOPE 2
job step.
A submitted job aborted before it was able
to connect to the terminal.
The SCOPE 2 connected job encountered error
condition xxx, as described in the Record
Manager section of the SCOPE 2 Diagnostic
Handbook.
ACTION
Retry using a higher
access level for the
permanent file (APPEND
or REPLACE), or change
the job's access level
and then retry (DEFINE,
CHANGE, PERMIT, or
SETPFAC).
ROUTINE
PFM
Reattach file in write
mode or clear write
interlock.
Have the operator blank
label the tape.
Replace tape and try
again. If problem
persists, try another
tape drive. If problem
still occurs, inform
site analyst.
Ensure accuracy of
format parameter (F) on
command or macro.
Correct XD or XT
parameter and retry.
Correct condition that
caused error and retry.
Assign the directory
file to mass storage.
Specify a different tape
density.
Check the job's dayfile
for an error indication.
Refer to the SCOPE 2
Diagnostic Handbook.
1MS
IAFEX
1MT
1MT
1MT
1MT
1AJ
1MT
HELL07
HELL07
HELL07
/fff^ y
60459680 F B-79
![](asset-2a4.png)
![](asset-2a5.png)
GLOSSARY
Abort
To terminate a program, job or job step
when an error condition (hardware or
software) exists from which the program
or computer cannot recover.
Access Category
Refer to File Access Category, Job
Access Category Set, and System Access
Category Set.
Access Level
A property of each file, job, and equip
ment on a secured system that is used to
indicate the sensitivity of information
in the file or job, or the sensitivity of
information that can be processed by the
equipment. On a secured system, there
are up to eight access levels correspond
ing to increasing levels of sensitivity.
You are authorized to access some or all
of those levels. Refer also to Equipment
Access Levels, File Access Level, Job
Access Level, and System Access Levels.
Access Level Limits
Application
A program resident in a host computer
that provides an information storage,
retrieval, or processing service to a
remote user via the data communication
network. IAF is an example of an
application.
Application Switching
The process of leaving the control of one
application and entering the control of
another, without going through another
complete login sequence.
Argument
Refer to Parameter.
ASCII
American National Standard Code for
Information Interchange. The standard
character set and code used for informa
tion interchange between systems.
0^>\
Refer to Job Access Level Limits.
Account Block
That portion of a session from login to
logoff or entry of a CHARGE command
which signals a new account block.
Allocatable Device
A storage device allocated by the system
without operator intervention that can
be shared by more than one job.
Alphanumeric
Consisting of alphabetic or numeric
characters only.
Auxiliary Device
Mass storage permanent file device used
to supplement storage provided by the
normal permanent file devices associated
with the system (refer to Family Device),
BASIC
1.
2.
Beginner's Ail-Purpose Symbolic
Instruction Code, an elementary
programming language.
The subsystem that uses the BASIC
compiler.
60459680 C C-l
![](asset-2a6.png)
Beginning-of-Information (BOI) Checkpoint
A file boundary that marks the beginning
of a file. You can reference the BOI by
name. For a labeled tape file on a
single volume, the HDRl represents BOI.
If the file is a multivolume (multireel)
tape file, BOI is the HDRl label of the
first volume. If the tape file is an
ANSI multifile file, BOI is the HDRl
associated with the beginning of the
multifile.
B i t
An abbreviation of binary digit. It is a
single digit, 0 or 1, in a binary number.
Also used to represent the smallest unit
of information. A central memory word
(one storage location) contains 60 bits.
Block
The process of writing to a magnetic tape
or mass storage file a copy of your job's
central memory, the system information
used for job control, and the names and
contents of all assigned files that are
identified in a CHECKPT request.
Checkpoint File
File on which the results of a partially
completed job are dumped when a check
point request is processed.
Command
A sequence of words and characters that
call a system routine to perform a job
step. The command must conform to format
spec ificati ons . Yo u can usually pl ace a
comment after the command terminator.
BOI
Blocking is the grouping of user records
for efficiency in transfer between memory
and storage devices. For magnetic tapes,
it is the information between interrecord
gaps.
Refer to Beginning-of-Information,
bpi
An abbreviation for bits per inch.
Refer to fci.
Byte
Command Record
The first, and possibly only, record of
a job file consisting of command images
that start with the Job command and end
with the first EOR, EOF, or EOI. Also
refers to a procedure containing
commands.
Compile
To translate a program from a higher
level programming language (for example,
FORTRAN or BASIC) into machine instruc
tions called object code.
Control Character
A group of 12 bits. Five bytes comprise
a 60-bit central memory word. Bytes are
numbered 0 to 4 from the left.
Catalog
The list of names of permanent files be
longing to a particular user name; this
list also contains information about the
permanent files.
Character
Any alphabetic, numeric, or special
symbol that can be encoded. This term
applies to the graphic characters for an
input or output device, and to uniquely
encoded control characters used by a
terminal.
C-2
1. A terminal-dependent character that
is a part of interactive status
commands and terminal definition
commands. It gives these commands a
preemptive status so that they are
processed immediately.
2. A character whose occurrence within
a file queued for printing, affects
carriage control. Examples are the
carriage return and line feed
characters.
Control Point
The portion of central memory that is
assigned to a job. When a job is allo
cated a portion of central memory, it
becomes eligible for assignment to the
central processor for execution.
60459680 G
>*^s\
![](asset-2a7.png)
Control Statement Default
0S^>\
c
Refer to Command.
Control Statement Record
Refer to Command Record,
cpi
Characters per inch. A measure of
density.
CYBER Loader
The utility that prepares programs for
execution by placing program instruction
and data blocks in central memory.
CYBER Record Manager (CRM)
A software product that allows a variety
of record types, blocking types, and file
organizations to be created and accessed.
Products like COBOL 5, FORTRAN Extended
4, FORTRAN 5, Sort/Merge 4, Sort/Merge 5,
ALGOL 5, and DMS 170 use CRM to manage
execution time input/output. Neither the
input/output of the operating system nor
that of most of the system utilities such
as COPY or SKIPF is implemented through
CYBER Record Manager. All CYBER Record
Manager file processing requests ulti
mately pass through the operating system
input/output routines.
D a y fi l e
A chronological file created during job
execution which forms a permanent
accounting and job history record. Day-
file messages are generated by operator
action or, with some exceptions, when
commands are processed. A copy of the
dayfile is printed with the output for
each job. You must explicitly request
i t i n a n i n te r act i ve j ob.
A system supplied option used when you do
not supply the option.
Detached Job
An interactive origin job that you have
dissociated from your terminal by using
the DETACH command. It continues to
execute under system control. You can
reattach an executing detached job with
the RECOVER command.
Device
Peripheral equipment.
Direct Access File
A NOS permanent mass storage file that
can be attached to the your job. All
changes to this file are made on the file
itself rather than a temporary copy of
the file (compare with Indirect Access
File).
Directive
An instruction subordinate to a system
command.
Display Code
A 6-bit character code set used to repre
sent alphanumeric and special characters.
Disposition Code
A two-character mnemonic that indicates
the manner in which the system is to
dispose of a queued file. The DC=dc
parameter of the LDI, QGET, ROUTE,
SETJOB, and SUBMIT commands specify a
disposition code.
EBCDIC
Deadstart
The process of initializing the system
by loading the operating system library
programs and any of the product set from
magnetic tape or disk. Deadstart re
covery is reinitialization after system ■
failure.
Extended Binary Coded Decimal Interchange
Code. An 8-bit code which represents a
set of 256 characters.
ECS
Extended Core Storage.
Memory.
Refer to Extended
jiPn
60459680 G C-3
![](asset-2a8.png)
Empty PRU/Record
A PRU that contains no user data. Refer
also to Zero-Length PRU.
End-Of-File (EOF)
A boundary within a sequential file, but
not necessarily the end of a file that
can be referenced by name. The actual
end of a named file is defined by EOI.
For labeled tape, EOF and EOI (denoted
by the E0F1 label) are the same. For
multifile tape files, EOF and EOI do not
correspond. In the product set manuals,
an end-of-file is also referred to as an
end-of-partition.
End-Of-Information (EOI)
The end of data on a file. Information
appearing after this point is not
considered part of file data. In card
decks, a card with a 6/7/8/9 multiple
punch in column one. On mass storage
devices, the position of the last written
data. On labeled tape, it is the E0F1
label. CYBER Record Manager defines.end-
of-information in terms of file residency
and organization.
End-Of-Record (EOR)
An indicator that marks the end of a
logical record. Also referred to as
end-of-section.
End-Of-Tape (EOT)
A reflective strip near the end of a
magnetic tape. It is used to signal
termination of operations on a particular
tape volume. At least 5.5 meters (18
feet) of tape must follow this marker.
Entry Point
A location within a program or procedure
that can be referenced from other pro
grams. Each entry point has a unique
name with which it is associated.
EOR
Refer to End-Of-Record.
EOF
EOI
Refer to End-Of-File.
Refer to End-Of-Information.
EOT
| C - 4
Refer to End-Of-Tape.
Epilogue
A program that executes at the end of
your job or, in the case of a project
epilogue, at the end of an account block.
Equipment Access Levels
A range of access levels specified for
each equipment on a secured system. In
order for a file to be stored or output
on a given equipment, the file's access
level must be within the equipment
access levels for the defined equipment.
Error Flag
A character or bit that signals the
occurrence or presence of an error.
EST Ordinal
The number designating the position of an
entry within the equipment status table
(EST) established at each installation.
Devices are identified in operator com
mands by EST ordinals. The EST ordinal
is sometimes referred to as equipment
number.
Exchange Package
A table that contains information used
during job execution. It is printed as
part of the output when a job aborts.
Executable Object Code
Machine language instructions that can be
executed directly by the machine. A com
piled program is composed of executable
object code.
Extended Core Storage (ECS)
Refer to Extended Memory.
60459680 G
/r*fiS«SV
/^^P^\
![](asset-2a9.png)
Jpw*N
Extended Instruction Stack Purging
Extended instruction stack purging
applies to models 825, 835, and 855 only.
It causes the instruction lookahead regi
sters to be purged under a wider range of
conditions than normal. Under normal
conditions, the lookahead registers for
models 825, 835, and 855 are purged by
the execution of a return jump instruc
tion (010), UEM read instruction (Oil),
exchange jump instruction (013), or
unconditional branch instruction (02).
Under extended instruction stack purging,
these registers are also purged by the
execution of any conditional jump
instruction (03 through 07) or any
central memory store instruction (50
through 57 with i = 6 or 7). The
instruction s th at cause i ns tr uc ti on
stack purging vary from model to model
for other computer systems (refer to the
hardware reference manual for the indi
vidual computer system).
Extended Memory
Optional additional memory. Variously
called extended core storage (ECS),
extended semiconductor memory (ESM),
unified extended memory (UEM), large
central memory (LCM), and large central
memory extended (LCME), depending on the
model of the computer system. Extended
memory contains 60-bit words. It has a
large amount of storage and fast transfer
rates. Extended memory can be used only
for program and data storage, not for
program instructions. Special hardware
instructions exist for transferring data
between central memory and extended
memory.
Family Device
Mass storage permanent file device asso
ciated with a specific system. A family
may consist of 1 to 63 logical devices.
Normally, a system runs with one family
of permanent file devices available.
However, additional families may be
introduced during normal operation. This
enables users associated with the addi
tional families to access their permanent
files via the alternate family.
Family Name
The name that is associated with a group
of permanent file devices.
fci
Flux changes per inch. A measure of
density used with magnetic tapes. Each
flux change records two bits of
information (per track); 3200 fci
encodes 6400 bits of information. If
you subtract 150 bits for error
checking, 3200 fci is equal to 6250 cpi
(assuming 1 bpi per track translates
into 1 cpi per frame).
FET
Refer to File Environment Table.
Field Length (FL)
The central memory and extended memory
assigned an executing job.
F i l e
1. A set of information that begins at
beginning-of-information (BOI), ends
at end-of-information (EOI), and is
referenced by a local file name.
2. That portion of a multifile file
terminated by an end-of-file (EOF).
3. Data recorded on a magnetic tape
beginning after an HDRl label and
ending before an E0F1 label.
NOS commands requiring a parameter that
is a file name refer to definition 1.
Commands requiring a parameter that
specifies the number of files refer to
definition 2. Definition 3 applies only
to labeled magnetic tapes.
File Access Category
A property of a permanent file used by
the creator of the file on a secured
system to restrict access of the file to
a particular group of users. A secured
system supports up to 32 access categor
ies, and you are authorized to use some,
all, or none of those categories. Refer
also to Job Access Category Set and
System Access Category Set.
60459680 G C-5
![](asset-2aa.png)
File Access Level FIT
A property of each file on a secured
system used to indicate the sensitivity
of information contained on the file. A
file is assigned the current job access
level by default when it is created or
stored; the file creator may specify any
access level for that file that is
within the set of access levels valid
for the job, the system, the file
cr ea to r, a nd ( fo r in te ra ctiv e jobs ) the
communication line to the host
mainframe. If you access a file on a
secured system, you must be validated
for the access level of the file. Refer
also to Access Level, Job Access Level,
and Job Access Level Limits.
File Environment Table (FET)
A table within a program's field length
through which the program communicates
with operating system input/output
routines. One FET exists for each file
in use by the program.
File Information Table (FTT)
A table through which a user program
communicates with CYBER Record Manager.
For direct processing through CRM, you
must initiate establishment of this
tab le . A ll file p r oc es sin g e xe cu tes o n
the basis of information in this table.
You can set FIT fields directly or use
parameters in a file access call that
sets the fields indirectly. Some product
set members set the fields automatically.
File Set
One or more tape files referred to by
the set identifier on a tape assignment
command or macro. A file set may consist
o f :
1. One file recorded on a single volume.
2. More than one file recorded on a
single volume.
3. One file recorded on more than one
volume.
Refer to File Information Table.
Flag
FNT
A character or bit that signals the
occurrence or presence of a particular
condition.
Refer to Local File Name Table.
FORTRAN
1. Formula Translation, a high-level
language consisting of symbols and
statements that can be used to
create a program closely resembling
mathematical notation.
2. The subsystem that uses the FORTRAN
Version 5 compiler.
Frame
A tape recording unit made up of one bit
from each tape track (7 bits for 7-track
tape and 9 bits for 9-track tape) . Each
frame on a coded tape usually represents
one character.
Generation
The position of a file within a series
of files, each file developed from the
preceding file. The generation number
and generation version number of a tape
file can be entered in its HDRl label.
Global Library Set
A set of user libraries you specify on
the LIBRARY command. The system condi
tionally searches these libraries when
it attempts to process a command.
Graphic
A character that can be printed or
displa ye d. Re fer t o Con tr ol Ch aracter.
4. More than one file recorded on more
than one volume.
All files within a file set have the same
set identifier in their HDRl labels.
C-6
lb st
A computer that executes an application.
60459680 C
![](asset-2ab.png)
0^\
IAF
Refer to Interactive Facility.
Indirect Ac cess Fi le
A NOS permanent file that you access by
making a temporary copy of the file (GET
or OLD command). You create or alter it
by saving or substituting the contents
of an existing temporary file (REPLACE
or SAVE command).
Input File Type
The file type the system assigns to file
INPUT. Its first record is a command
record which may be followed by records
containing data, directives, or programs
used by job steps.
Instruction Stack Purging
The process of clearing the instruction
s ta c k i n t h e c e nt r a l p roc e ss o r. I t
affects the speed and accuracy of the
central processor.
Interactive Facility (IAF)
An application that provides a terminal
operator with interactive processing
capability. The interactive facility
makes terminal input/output and file
input/output appear the same to an
executing program.
Interrecord Gap
Space skipped between the writing of data
blocks on magnetic tape.
Interruption Sequence
The character or sequence of characters
that causes an executing program to be
interrupted (also called the user break
1).
Job
A set of commands and the data and
directives used by those commands. A
batch job must begin with the Job and
USER commands. An interactive job is
all activity associated with a terminal
session from login to logout unless you
detach a job during the session. After
a job detachment, the terminal session
becomes a new job.
Job Access Category Set
On a secured system, a set of access
categories is set when the job is
initiated. This set is the intersection
of your set of validated access
categories and the system access
category set. Refer also to File Access
Category and System Access Category Set.
Job Access Level
On a secured system, each job has an
a cc e ss l ev e l. T h is is the d ef a ul t
access level that is assigned to files
that are created or stored in the job.
A job's initial access level is the
lower access level limit for the job.
The job's access level is automatically
raised to the access level of any file
from which information is read. You can
also change the job access level. Refer
also to Job Access Level Limits.
Job Access Level Limits
An upper limit and a lower limit that
determine the range of access levels
that are valid for a particular job on a
secured system. All files used in a
given job must have an access level
within the job's access level limits.
Job Sequence Name (JSN)
The unique, system-defined name assigned
to every executing job or queued file.
The JSN is a string of four alphabetic
characters.
Job Step
An individual command, procedure or
loader sequence. A group of job steps
forms a job stream, command record, or
procedure file.
Label
A block at the beginning or end of a
magnetic tape volume or file, which
serves to identify or delimit that
volume or file.
60459680 C C-7
![](asset-2ac.png)
Level Number
An octal number (0, 1, or 17) in the
terminating marker of a PRU. A level
number of 17 designates an EOF. A level
number of 0 designates an EOR. A level
number of 1 designates that the line of
data is from a terminal and is not an
empty line.
Library
1. A collection of programs or routines.
2. A file containing records that are
accessed individually.
3. A file searched by CYBER Loader for
entry points referenced by a program.
4. A file containing compressed records
in Modify or Update format.
Library File
A read-only file that can be accessed by
several users simultaneously or a file
you specify on a LIBRARY command.
LID
Refer to Logical Identifier.
Line
Local File Name
The file name assigned to a file while it
is local (assigned) to a job. The name
is contained in the local file name
table.
Local File Name Table (FNT)
A system-managed table that contains the
local file name, the file type, and other
job control information.
Locked File
A file on which you cannot write.
Logical Device
One or more physical disk units known to
the system as a single device.
Logical Identifier (LID)
A three-character, alphanumeric string
used to identify a particular mainframe
in a loosely coupled network. LIDs are
identified by your site.
Logical Record
A data grouping that consists of zero or
more PRUs and ends with a short PRU or a
zero-length PRU.
/ffiSsv
A unit of data terminated by a zero-byte
terminator. Unit used in interactive
input/output, line printer output, and
card reader input.
Login
The procedure used at an interactive
terminal to gain access to the system.
Line Mode Logout
A mode of job interaction in which the
basic unit of interaction is a line of
data. Contrast with Screen Mode.
Load Point
Metallic strip marking the beginning of
the recordable portion of a magnetic
tape. Data, including labels, is written
after the load point.
The procedure used to end a terminal
session.
Loosely Coupled Network (LCN)
A network of physically connected
computer systems. The LCN environment
allows jobs, data files, and messages to
be transmitted from one computer system
to another.
Loc al Fil e
Any file that is currently associated
with a job. Local files include all
temporary files and attached direct
access files.
C-8
Macro
A sequence of source statements that are
saved and then assembled whenever needed
through a macro call.
60459680 C
![](asset-2ad.png)
Mass Storage
Magnetic disk or extended memory that
can be accessed randomly as well as
sequentially.
Master Device
Mass storage device that contains your
permanent file catalog entries; all your
indirect access files; and all, part, or
none of your direct access files.
Multifile File
A file containing more than one logical
file. It begins at BOI and ends at EOI.
On a labeled tape, a multifile file is
delimited by corresponding HDRl and E0F1
labels.
Multifile Set
A tape file set having more than one
tape file.
Object Code
Executable machine language instructions.
An object code program need not be
recompiled each time it is executed.
Order-Dependent
Used to describe items which must appear
in a specific order.
Order-Independent
Used to describe items which need not
appear in any specific order. Param
eters, particularly those with keywords,
may be order-independent.
Origin Type
A job attribute that indicates how a job
entered the system. The four origin
types are interactive origin, batch
origin, remote batch origin, and system
origin.
Network
A data and message switching and routing
system used to provide communication
between terminals, applications, and
mainframes.
Network Operator (NOP)
The network operator manages the communi
cations elements of the network. Network
operator functions may be performed at
the system console, or at a remote
terminal.
Packet-Switching Network (PSN)
A system that provides data communication
service between different terminals and
computer systems. The PSN is usually
licensed as a common carrier. GTE
Telenet is an example of a PSN.
Subscribers use a protocol defined by a
standards body such as CCITT to interface
with a PSN. The packet assembly/
disassembly (PAD) access defines the
terminal interface. The X.25 protocol
defines the PSN interface with NOS.
Noise Panel
Any tape block less than the minimum
acceptable block size for its data
format. Noise is discarded by the
system.
Nonallocatable Device
A device (such as a magnetic tape unit,
card reader, card punch, or line printer)
which can be used only by one job at a
time.
A formatted screen defined using the
panel definition utility. An
application program uses a panel to
display data or to request user input at
the terminal.
Parameter
A value that follows a command name or
function name and that alters the
behavior of the command or function.
60459680 D C-9
![](asset-2ae.png)
yrS^.
P a r i t y
In writing data, an extra bit is either
set or cleared in each byte so that every
byte has either an odd number of set bits
(odd parity) or an even number of set
bits (even parity). Parity is checked
on a read for error detection and
possible recovery.
Passive Procedure
A procedure that does not have the
par am e te r- p ro mp t in g c ap a bi lit y. I f t he
call to the procedure contains errors,
the job step terminates and the procedure
is not executed.
Password
Physical Record Unit (PRU)
The amount of information transmitted by
a single physical operation of a speci
fied device. For mass storage files, a
PRU is 64 central memory words (640 char
acters); for magnetic tape files, the
size of the PRU depends upon the tape
format. A PRU that is not full of user
data is called a short PRU; a PRU that
has a level terminator but no user data
is called a zero-length PRU.
Post Radix
A letter following a numeral that
indicates the base numbering system.
PP
1. A system access word that must be
used in addition to the user name at
log in.
2. A file access word that controls
access to a p articul ar file by
alternate users.
Peripheral Processor (PP)
The hardware unit within the host com
puter that performs physical input and
output through the computer's data
channels.
Permanent File
A mass storage file that is cataloged by
the system so that its location and
identification are always known to the
system. Permanent files cannot be
destroyed accidentally during normal
system operation. They are protected by
the system from unauthorized access
according to privacy controls specified
when they are created.
Permanent File Device
Mass storage defined by your site to hold
permanent files.
Permanent File Family
Permanent files which reside on the
family devices of a specific system.
Refer to Peripheral Processor.
Prefix Character
A charact er t hat has a specia l signi fi
cance to a program or the operating
system and is used in front of a string
of characters.
Primary File
A temporary file created with the OLD,
NEW, LIB (interactive jobs only), or
PRIMARY command. The primary file is
assumed to be the file on which most
system operations are performed unless
another file is specified. There can be
only one primary file associated with
your j ob.
Private Auxiliary Device
Auxiliary device associated with a speci
fic user name. Only that user name may
create files on the device, although
other users may be permitted to access
files which reside on the device.
Procedure
A user-defined set of instructions that
can be referenced by name. The
instructions consist of procedure
directives and system commands.
«**SX
C-10 60459680 C
![](asset-2af.png)
/fl^^N
0iffi$\
Procedure File
A file containing one or more procedures,
Project Epilogue
An epilogue that executes any time you
end an account block.
Project Prologue
A prologue that executes any time you
initiate a new account block.
Prologue
A program the system executes any time
you initiate a job (user prologue and
system prologue) or initiate a new
account block (project prologue).
PRU
Refer to Physical Record Unit.
PRU Device
A magnetic tape file or a mass storage
device. Records on these devices are
written in physical record units (PRUs).
PSN
Refer to Packet-Switching Network.
Public Auxiliary Device
Auxiliary device available for access by
all validated users knowing the correct
pack name. Additional validation is
required to create or replace files on
an auxiliary device.
Queue Priority
A number that controls the scheduling of
a job to and from the rollout queue rela
tive to other jobs of the same origin
type.
Queued File
A file you have submitted for job entry
or a file of job output waiting for
processing. The queued file may have a
print, punch, wait, or input disposition.
Random Access
Access method by which any record in a
file can be accessed at any time.
Applies only to mass storage files with
an organization other than sequential.
Compare with Sequential Access.
Random Access File
A file whose records are accessed through
a directory containing the address of
each record.
Read-Only Permission
If you have read-only permission on a
file, you can read and execute the file.
You cannot write, modify, append, or
purge the file.
Record
A unit of information. In CYBER Record
Manager and its language processors, a
record is a unit of information produced
by a single read or write request. Eight
different record types exist within CRM.
You define the structure and character
istics of records within a file by
declaring a record format.
A NOS record is a second-level subdivi
sion of a file. It is the smallest
subdivision that NOS recognizes. A NOS
record can consist of a group of CRM
records.
Recovery
The process by which you reattach a job
to the terminal. You could have explic
itly detached the job using the DETACH
command or the job could have been de
tached because of a system failure or
terminal disconnection before logout.
You can initiate recovery processing
with the RECOVER command.
Reference Address (RA and RAE)
RA is the absolute central memory address
that is the starting or zero relative
address assigned to a program. Addresses
within the program are relative to RA.
60459680 C C-ll
![](asset-2b0.png)
/ffis^y
RA+1 is used as the communication word
between the user program and the system.
RAE is the absolute extended memory
starting address assigned to a program.
Remote Host
A computer connected to your local host
so as to permit permanent file and queue
file transfers between hosts.
Remote Host Facility (RHF)
An application program that allows you .
to transfer files to and from other
mainframes connected to a loosely
coupled network (LCN).
Rolled Out
The status of an executing job that has
been temporarily removed from central
memory.
Rubout Characters
Characters created by pressing the RUB
OUT key on the terminal. These are con
sidered null input by the system and are
required in paper tape output.
Scheduling Priority
Security Administrator
A secured system prevents users and
operators from performing certain
functions that could result in the
unauthorized disclosure of information.
These functions can only be performed by
a person who is designated a security
a dmi n i st r a to r. A s e c uri t y a d min i s tr a t or
is always authorized to access the
highest level of information stored on
the system. This person performs
functions in the areas of installation,
user validation, system operation, and
system maintenance.
Security Count
The number of security violations you
have left before you are denied access
to the system.
Security Unlock Status
This status of the system console
applies only to a secured system and
must be set by a security
administrator. The console must be in
security unlock status in order for the
security administrator to perform
certain functions that are restricted on
a secured system.
/./iSSjk
The variable associated with an executing
job that controls the scheduling of the
job for CPU time.
Screen Mode
Sequence Number
1. Number at the beginning of each line
o f a fi l e .
A mode of job interaction in which the
basic unit of interaction is a screen of
data. Contrast with Line Mode.
Secured System
A system in which a mandatory security
mechanism has been enabled during
deadstart. A secured system protects
in fo rm ati on by en fo rcing re st ri ctio ns
based on access levels and access
categories, and restricts many sensitive
system functions to security
administrators.
2. For tape labels, number indicating
position of a file within a file set.
Sequential Access
A method in which only the record
located at the current file position can
be accessed. Refer to Random Access.
Sequential (SQ) File
A file in which records are accessed in
the order in which they occur. Any file
can be accessed sequentially.
C-12 60459680 F
![](asset-2b1.png)
Service Class
A job classification based on a job's
origin type or job's status. It deter
mines how a job is serviced as it flows
through the system.
Short PRU
A PRU that does not contain the maximum
amount of character data allowed for a
PRU. Refer to Zero Length PRU.
Source Code
Code input to the computer for later
translation into executable machine
language instructions (object code).
Special Editing Mode
A variation of normal input mode (other
than transparent input mode) in which
the cancel input character, backspace
character, and line feed character are
not treated as special characters but
are passed to IAF as input data.
SRU
Refer to System Resource Unit.
Standard Labeled Tape
A tape with labels conforming to American
National Standard Magnetic Tape Labels
for Information Interchange X3.27-1969.
Also called a system labeled tape.
String
A sequence of characters.
Subsystem Flag
A character or bit that tells the system
that a particular subsystem is associated
w i t h a fi l e .
System Access Category Set
On a secured system, a set of access
categories is set during level 0
deadstart. This set may consist of
some, all, or none of the 32 possible
access categories. While the system is
running, you may only use access
categories that are within the set of
system access categories. Refer also to
File Access Category and Job Access
Categories.
System Access Levels
On a secured system, a range of access
levels is set during level 0 deadstart.
This range may contain some or all of
the ei ght p ossib le acc ess l ev els. While
the system is running, you may only use
access levels that are within the range
of system access levels.
System File
A file that can be accessed only by a
system program.
System Resource Unit (SRU)
A unit of measurement of system usage.
The number of SRUs includes the central
processor time, memory usage, and input/
output resources used for a given job.
Tape Format
A parameter that specifies the internal
recording format of a magnetic tape.
Tape Mark
A delimiter written on tapes under
operating system control to separate
label groups, files, and/or labels.
Interpretation depends on the tape
format.
Temporary File
A file that is assigned to your job and
vanishes once you release it or at job
termination. Local copies of indirect
access permanent files are temporary
files; direct access permanent files
assigned to your job are not temporary
files.
Terminal Name
A network-supplied name used to identify
the terminal to the network operator.
60459680 C C-13
![](asset-2b2.png)
Termination Sequence
The character or sequence of characters
that causes an executing program to be
terminated (also called the user break
2).
Time Slice
The amount of CPU or CM time a job is
allowed to use before the system lowers
its priority to allow other jobs to
execute.
Timed/Event Rollout
A condition where an executing job that
has been temporarily removed from central
memory but will be rolled back into
central memory only when a specified
event (such as a file is no longer busy)
or a specified time period has elapsed.
Transparent Input Mode
An input mode in which all characters
entered at the terminal are sent to IAF
as 7-bit codes (or as 8-bit codes, de
pending on the parity) without transla
tion. Normally, characters entered at
the terminal are translated and stored
as 6-bit and/or 12-bit display codes.
This mode is initiated either with the
0006 control byte or with the IN=X,
IN=XK, or IN=XP terminal definition
commands. In former interactive systems
this mode was referred to as binary mode.
Transparent Submit Mode
The mode used in a submit file to
transfer information that contains
reformatting directives without
processing the directives.
User Break 2
Refer to Termination Sequence.
User Index
A number the system assigns each user
name and uses for internal record
keeping.
User Index Hash
A string of four alphabetic characters
derived from your user index that serves
as the default user job name (UJN) for
i nt era ct i ve j ob s . I t a pp ear s o n t he
banner page/card of all line printer and
card punch output. You can ascertain
your user index hash with the ENQUIRE
command.
User Job Name (UJN)
In general, the user-defined name for an
executing job or queued file. If you
fail to specify a UJN, the system uses
your index hash. The UJN must be a
string of seven or fewer alphanumeric
characters. Unlike the job sequence
name (JSN), the UJN for jobs is not
always unique.
User Name
A one to seven-character name that iden
tifies the user to the system and for
which there is assigned a user index
that allows access to permanent files.
User Number
Refer to User Name.
Unsecured System
A system in which the security mechanism
has not been enabled during deadstart.
The restrictions based on access levels
and access categories are not enforced
on an unsecured system.
User Break 1
Refer to Interruption Sequence.
Validation File
File containing validation information
for all users (user names, passwords,
resources allowed, and so on).
Volume
A reel of magnetic tape. A given file
can be comprised of more than one volume,
C-14 60459680 C
![](asset-2b3.png)
Volume Serial Number (VSN)
A on e- to si x- ch ar ac te r i de nt ifi er th at
identifies the volume of magnetic tape
to the system.
VSN
Refer to Volume Serial Number.
In 6-bit display code, two colons create
12 bits of zeros in the 64-character set.
If two consecutive colons occur in a
file that contains zero-byte terminated
records, they might be stored in the
lower order portion of a word and create
a zero-byte terminator.
Word
r
A group of bits (or 6-bit characters) be
tween boundaries imposed by the computer
system. A word is 60 bits in length.
The bits are numbered 59 through 0
starting from the left. It is also
composed of five 12-bit bytes, numbered
0 through 4 from the left.
Zero Byte Terminator
The 12 bits of zero in the low order
position of a central memory word that
are used to terminate a line of coded
information. A record with such a
terminator in CYBER Record Manager is a
zero-byte record (Z type record).
0S^\
Write Interlock
Write interlock ensures that only one
person at a time can attach a direct
ac ce ss fi le in w rit e mo de. A d ir ect
access file that is attached in write
mode i s in w ri te interl oc k.
Write Ring
A circular device inserted into a tape
re el in di catin g to th e ta pe u ni t th at it
can write on that reel. NOS checks for
the presence of a write ring if you
r eq u e st i t .
Zero Length PRU
A PRU that contains system information,
but no user data. Under NOS, a zero-
length PRU defines EOF.
6/7/8/9 Multipunch
A card with the characters 6, 7, 8, and 9
multipunched in column 1. Signifies a
card deck EOI.
XMODEM
XMODEM is the industry standard error
checking communications protocol used to
transfer files to and from microcomputers
and mainframes. Also known as the
Christensen protocol.
Files created interactively at a terminal
and by commands that manipulate coded
lines contain zero-byte terminated
records. The image of cards input
through a card reader also has such a
terminator.
6/7/9 Multipunch
A card with the characters 6, 7, and 9
multipunched in column 1. Signifies a
card deck EOF.
7/8/9 Multipunch
A card with the characters 7, 8, and 9
multipunched in column 1. Signifies a
card deck EOR.
0O^^\
60459680 H C-l 5
![](asset-2b4.png)
0*%
![](asset-2b5.png)
JfP^V
SAMPLE JOB OUTPUT
This appendix lists the output information printed for the sample job shown below. The job
consists of the following commands.
OUTPUT.
USER,STARSKY,HUTCH.
GET,PFL.
ITEMIZE,PFL.
This job generates three pages of output. The first page is the banner page (shown on D-2),
the second is the output generated by ITEMIZE (shown on D-3), and the third is the dayfile
(shown on D-4).
60459680 C D-l
![](asset-2b6.png)
OPERATING SYSTEM = NOS 2 crtndate
UJN - OUTPUT FAMILY
CREATING JSN - ABNS USER NAME
PRINTED - yy/mm/dd 13.48.33.
- M A T H J O B O R I G I N - B A T C H .
- STARSKY SERVICE CLASS - BATCH.
l l l t U U M JJJJJJJJJJJJ L 4444444444 4444444444 ttt"9XXXXXX •JM NN s*<rs«ssss
4,4444*44444 4 JJJtJJJJJJJJ I 44444444444 444444444444 B X 9 sa^tjaqqn NNN t>'N ssss^st'sf
* J J I 4 P » 8X NNNN NN s s s
A J J I A P B ox N M I N NN ss
A J J I A f a «x I N N N NN ss
* J J L 4 C i BX I N N N NN ss
1 J J 1 A P X RK M N N N NN ss
1 J J L t pqcinn^naneBn N N N N h N sssssssrsss
«AMA4AAAt* A J J L 44(41444444 44444444444A Pmi«B?11H9 NN NNNN s*sr«'ss<5
i « f U > / M i l 4 J J L AA4AA4AAAAA 44444444444A P X PR NN NNN *.*,
4 J J I A P l 9° NN NN S<=
1 J J I A P X nq NI NN *s
t J J I A P X Q9 NN NN SS
A J J J J I L L L 4 A » S PX NN NN s s s
> JIJJIJJ ILLILLLLLLLL 4 a p,*xxax9xxxxt> NN NN SSSSSS^'S'
4 J J J J J 1 LLULUllLL 4 A IMMHMH NN NN S<S<<SSS<5
The first line indicates the version of the operating system, the creation date of that
version (crtndate), the printing date (yy/mm/dd), and the time of day the printing occurred.
The second line contains the user job name (UJN), as specified on the Job command; family
name, and job origin.
The third line contains the job sequence name (JSN), the user name associated with the job,
and the job's service class.
The first four block letters indicate the user index hash and the last four, the job's JSN.
.tfflSSV
D-2 60459680 C
^*5^5V
![](asset-2b7.png)
f^ f^ . .
REC
ITEMIZE OF PFL
NAME TYPE
1INSTALL PROC
2BUILD PROC
3UPGRADE PROC
4TRMINAL PROC
5JOB PROC
6 ISF PROC
7PRO PROC
8PL PROC
9GROUP PROC
10 XED PROC
11 EDPROC PROC
12 RWF PROC
13 CALC PROC
14 EDREC PROC
15 BACKUP PROC
16 FTN PROC
17 AJFILE PROC
18 AJL PROC
19 MOD PROC
20 GENPL PROC
21 EDITPL PROC
22 PAS PROC
23 REL PROC
24 CMP PROC
25 PSR PROC
26 PSRFEAT PROC
27 HPSR PROC
28 SPRO PROC
29 DINDEX PROC
30 RINDEX PROC
31 INDEX PROC
32
33
AJLIST
* EOF *
PROC
FILE
LENGTH CKSUM
62 6454
65 3131
42 1242
442 5125
22 6332
51 1240
46 5362
56 1450
37 0104
133 0376
42 6700
17 0002
20 6034
72 6640
107 1373
112 3504
34 2403
34 5236
203 7326
32 0565
55 7101
152 7203
37 7154
40 5164
125 6613
47 3106
21 5610
26 5174
61 3156
60 1331
124 4474
27 2560
DATE
** UNLABELED **
COMMENTS yy/mm/dd. 10.16.57. PAGE
ITEMIZE
SUM 3332
60459680 C D-3
![](asset-2b8.png)
ABNS CDC NETWORK OPERATING SYSTEM. NOS 2 16.58.59. yy/mm/dd.
16.58.55.OUTPUT.
16.58.55.USER,STARSKY,.
16.58.55.CHARGE,*.
16.58.55.* CHARGE(1514/5612PAY)
16.58.56.$PROLOG,PR0C2,,.
16.58.56.$SETFS/PROC2/FS=AD.
16.58.57.PROC2.
16.58.58.IFE,0T.EQ.TX0,0THER0T.
16.58.58.ENDIF,0THER0T.
16.58.58.IFE,$$.NE.$$,END.
16.58.58.ENDIF,END.
16.58.58.SREVERT.CCL
16.58.58.GET/PFL.
16.58.58.ITEMIZE,PFL.
16.58.58. ITEMIZE COMPLETE.
16.58.58.UEAD, 0.002KUNS.
16.58.58.UEPF, 0.057KUNS.
16.58.58.UEMS, 0.770KUNS.
16.58.58.UECP, 0.070SECS.
16.58.58.AESR, 2.186UNTS.
16.58.58.$OUT(*/OP=E)
16.58.58. NO FILES PROCESSED.
16.58.59.$DAYFILE(OUTPUT,JT=D)
16.59.00.UCLP, 42, 070, 0.256KLNS.
,.JS^%V
The first line lists the job's JSN (ABNS); a site-selected, system or machine identifier;
the time of job termination (16.58.59); and the current date. The dayfile includes a
listing of the commands, system-supplied status messages, and program output, if any.
Spaces precede status messages and program output. Each line includes the time the message
was issued to the dayfile.
Six of the last nine lines specify the type and amount of system resources the job used.
This job used 0.002 kilounit of application activity, 0.057 kilounit of permanent file
activity, 0.770 kilounit of mass storage activity, 0.070 seconds of central processor time,
and 2.186 system resource units. The first two numbers after UCLP give the machine
identifier as 42 and the EST ordinal of the printer as 070. The job produced 0.256 kiloline
(256 lines) of printable output.
The $0UT and $DAYFILE commands are system-supplied and ensure that the job's dayfile is
printed.
Depending on the resources used, additional information may be included in the dayfile.
Refer to Job Completion in section 3 for the formats of these messages.
D-4 60459680 C
![](asset-2b9.png)
jgpSy
TERMINAL CHARACTER CONVERSION
Normal input mode from an ASCII code terminal uses a 63- or 64-character set where all
lowercase alphabetics are converted to uppercase characters. Under ASCII mode, the
characters 74 and 76 represent the beginning of a 74xx or 76xx escape sequence. Under
normal mode, the characters 74 and 76 are treated as data rather than escape codes. ASCII
and normal modes apply to both input and output.
0^*\
DATA INPUT
The manner in which the system interprets the characters entered from a terminal depends on
whether you request ASCII or normal mode. For example, if you enter
aAbBcCdDeEfF
when in ASCII mode, the central memory equivalent is:t
B i t p o s i t i o n 5 9 4 7 3 5 2 3 1 1 0
Code
Character
Code
Character
76 01 01 76 02 02 7 6 0 3 03 76
A.BC
a b c
0 4 0 4 76 05 05 76 0 6 0 6 00 00
end-of-line
/p^v.
tPartial words are zero-filled; partial bytes are blank-filled.
60459680 H E-l
![](asset-2ba.png)
However, if you enter the characters in normal mode, the characters are mapped into the
64-character subset of the ASCII character set that contains only uppercase letters; then
the central memory equivalent is:
Bit position
Code
Character
Code
Character
59
F F
47 35 23 11
end-of-line
01 01 02 02 03 03 04 04 05 05
A A B B C C D D E E
06 06 00 00 00 00 00 00 00 00
Refer to appendix A for further description of the code sets for interactive jobs,
DATA OUTPUT
Data output is in either a 64/63- or 128-character set, depending on whether the terminal is
in normal or ASCII mode. When the terminal is in normal mode, the codes 74 and 76 represent
data rather than escape codes. In ASCII mode, 74 and 76 are treated as the beginning of an
escape sequence.
Data can also be transmitted to or from a terminal through a paper tape reader. Refer to
appendix N.
/tTtfst^v
/ ^ ^ k
E-2 60459680 C
![](asset-2bb.png)
00^\,
CARD FILE DATA CONVERSION
Data within the system is stored in binary or coded format. Binary data is variable length
central memory images. Coded data consists of display-code characters. Each coded line is
stored as an even number of characters. If an odd number of characters is entered the
system appends a space to make it even. '
This appendix describes the formats for punch cards. It also describes the conversion
performed by the system on data transferred between the system and card readers and punches.
When using the 64-character set, avoid using consecutive colons (00 characters). It is
possible for these colons to be interpreted as an end-of-line. An end-of-line is defined as
12 to 66 zero bits, right-justified in one or two central memory words. If consecutive
colons appear in the lower 12 bits of a central memory word, they are interpreted as an
end-of-line rather than as colons.
Example:
The following characters are punched on a coded card beginning in column 1.
:::::::::A::::::::AA
This appears in memory as follows:
B i t p o s i t i o n 5 9 4 7 3 5 2 3 1 1 o
Code 00 00 00 00 00 0 0 00 00 00 01
Character : : : : : : : : : A
Code 00 00 00 00 0 0 0 0 00 00 01 01
Character : :
Code 00 00 00 00 0 0 0 0 00 00 00 00
Character end-of-lin<
0^S
60459680 C F-l
![](asset-2bc.png)
However, if the characters were copied with the COPYSBF utility, the following appears.
B i t p o s i t i o n 5 9 4 7 3 5 2 3 1 1 0
Code
Character
Code
Character
Code
Character
5 5 0 0 0 0 0 0 0 0 0 0 00 00
end-of-line
end-of-line
0 0 0 0
01 00 00 00 00 00 00 00 00 01
A : : : ' : : : : A
01 55 00 00 00 00 00 00 0 0 0 0
Because the COPYSBF utility shifts each line one 6-bit character to the right and adds a
space, copying nine colons puts 12 zero bits in the last byte of the first word. This is
interpreted as an end-of-line.
NOTE
If a colon is the last character of an input
line, the system appends a space to preserve
the colon and then appends an end-of-line.
If needed, a second space is added to ensure
an even number of 6-bit characters. Refer
to figure F-l.
INPUT CARD FILE FORMATS
The system reads cards in coded and binary formats. The following conditions apply in both
formats.
• A card with a 7/8/9 punched in column 1 is an EOR mark.
• A card with a 6/7/9 punched in column 1 is an EOFf mark.
• A card with a 6/7/8/9 punched in column 1 is an EOI mark.
The remainder of each card is ignored except for columns 79 and 80 of the EOR and EOF
cards. These columns can contain the keypunch conversion mode for the input records that
follow.tt Conversion modes are discussed in Coded Cards.
yrffeflllt^W
tThe 6/7/9 keypunch mark is not supported by RBF.
ttHASP terminals can support other forms of separator cards such as /*E0R and /*E0I. (Refer
to the Network Products Remote Batch Facility Reference Manual.)
F-2 .60459680 C
![](asset-2bd.png)
^^*s
CODED CARDS
Cards are read in Hollerith punch code. The 3447 card reader controller converts the
Hollerith code to internal BCD code and passes the data to the card reader driver. The
driver converts the data from internal BCD code to display code. Up to 80 characters can be
transferred per card. Trailing blank characters are deleted. If a line has an odd number
of characters, one trailing blank is added to make it even. In order to preserve the colon
(008) of the 64-character set, a trailing blank byte is either retained or appended as the
last character in an even line. Examples of coded card conversion are shown in figure F-l.
Conversion Modes
Two conversion modes, 026 and 029,f exist for the Hollerith punch code. All data is
r converted in the system default keypunch mode unless a conversion mode change is specified.
This change can be specified on any of the following cards.
The job card, 7/8/9 card (EOR mark), and 6/7/9 (EOF mark) can contain the keypunch
conversion mode in columns 79 and 80. A 26 punched in columns 79 and 80 indicates that all
subsequent cards are converted in 026 mode. A 29 indicates that subsequent cards are
converted to 029 mode. Each conversion change remains in effect until another change card
is encountered or the job ends. The user can switch between 026 and 029 mode as often as
desired. If 26 or 29 does not appear in columns 79 and 80 of the job card, the initial
keypunch mode of that job is the system default mode. If 26 or 29 does not appear on a
7/8/9 or 6/7/9 card, no conversion change is made, and the most recent keypunch mode remains
jpps, in effect.
Keypunch mode can also be changed by a card containing a 5/7/9 punch in column 1. A blank
(no punch) in column 2 indicates 026 conversion mode; a 9 punch in column 2 indicates 029
mode. The conversion change remains in effect until another change card is encountered or
the job ends.
Literal Input
The 5/7/9 card also allows literal input when 4/5/6/7/8/9 is punched in column 2. Literal
input allows 80-column binary data to be read while transmitting input in coded mode. Cards
are read (16 central memory words per card) until a card identical to the previous 5/7/9
card (4/5/6/7/8/9 in column 2) is read. The next card can then specify the new conversion
mode.
In order to maintain system integrity, an end-of-information card always terminates
80-column binary input (literal input). Either of the following is interpreted as an
end-of-information card even though it appears in a literal input record.
• A card with 6/7/8/9 punched in column 1 and with columns 2 through 80 blank.
e A card with 6/7/8/9 punched in columns 1 and 80 and with columns 2 through 39 and
columns 41 through 79 blank. Column 40 may be punched or left blank.
tThese codes are ignored by a 200 User Terminal since conversion mode is selected by a
hardware switch. (Refer to the Network Products Remote Batch Facility Reference Manual.)
60459680 C
![](asset-2be.png)
/£$$?$!\
•80 CHARACTERS-
r•■
FOR 63 AND 64 CHARACTER SETS
|<l 8 WORDS (80 CHARACTERS) ■
: c : c : c:
60 BITS OF
BINARY ZEROS
IjJ
EO L
■79 CHARACTERS-
rD r
■ 7 WORDS (70 CHARACTERS)-
= : i 1 1 —
- * | W O R D 8 W O R D 9
"9 CHARACTERS | f (''ntfj^l^ps
ONE BLANK IS RETAINED
TO MAKE AN EVEN
NUMBER OF CHARACTERS
13
-56 CHARACTERS- - 5 WORDS (50 CHARACTERS) -
rj c ] c : 1 31
24 BITS
I OF
I ZEROS
mm
NO TRAILING BLANK
IS RETAINED SINCE
THERE IS AN EVEN
NUMBER OF CHARACTERS
EO L
100 IN DISPLAY CODE)-
-79 CHARACTERS-
FOR 64 CHARACTER SET ONLY
' |o 7 WORDS (70 CHARACTERS)-
— • ] W O R D 8 W O R D 9
9 CHARACTERS r * r ' I 4 8 B I T S O F
■ *, I BINARY ZEROS
JJ LTT
jXj
12 CHARACTERS WITH
: AS THE TWELFTH
CHARACTER
: (00)
BLANK (55) ADDED
TO SEPARATE : FF
TRAILING ZEROS mJLi n » i l - l I —
JJ
1 WORD
10 CHAR.
EO L
BLANK ADDED TO
MAKE AN EVEN
NUMBER OF
CHARACTERS
„-' 36 BITS
r ' I O F B I N A R Y
I I Z E R O S
1 C H A R A C T E R - » | I I I I | f
|X|
11 CHARACTERS WITH
: AS THE ELEVENTH
CHARACTER
BLANK (55) ADDED
TO SEPARATE : FROM
TRAILING ZEROS .JJw EOL
BLANK ADDED TO
MAKE AN EVEN NUMBER
I OF CHARACTERS
(
1 WORD
10 CHAR. WORD 2
IX
CE
48 BITS OF
I BINARY ZEROS
I I I
EOL
BLANK (55) ADDED
TO SEPARATE : FROM
TRAILING ZEROS
THIS MAKES AN EVEN
NUMBER OF CHARACTERS
Figure F-l. Examples of Coded Card Conversion
,-^KS\
F-4 60459680 C
![](asset-2bf.png)
BINARY CARDS
Binary cards are denoted by a 7/9 punch in column 1 and can contain up to 15 central memory
words. The 3447 card reader controller reads the binary data and passes it to the card
reader driver in 12-bit codes. Each card column row corresponds to a bit position. The
driver checks the checksum figure if this option is specified. The driver then passes the
data to the central memory buffer.
The fields within a binary card are:
Column(s) Description
1
3 through 77
78
79 and 80
7/9 punch indicates a binary card.
4 punch ignores checksum punch in column 2.
Rows 0, 1, 2, and 3 contain the binary equivalent of the word count
of the card.
Binary data checksum (modulo 4095).
Fifteen central memory words of binary data.
Blank.
24-bit binary card sequence number.
SUMMARY
The following punches appearing in column 1 of a card have the corresponding meaning to the
car d reader dr iv er.
Punch
7/ 8/9
6 / 7 / 9
6 / 7 / 8 / 9
5 / 7 / 9
7/9
Not 7 and 9
Represents
End-of-record (optional conversion mode change).
End-of-file (optional conversion mode change).
End-of-information.
Conversion mode change/read 80-column binary.
Binary card.
Coded card.
PUNCH FILE FORMATS
Punched cards can be in three formats,
• Coded (Hollerith punch).
• Binary.
• Absolute binary.
60459680 C F-5
![](asset-2c0.png)
The following conditions apply to all three formats.
• When an EOR is encountered, a card is punched with a 7/8/9 in columns 1 and 80.
This card is offset.
9 When an EOF is encountered for a file, a card is punched with a 6/7/9 in columns 1
and 80; the remainder of the card is blank. This card is offset.
• When an EOI is encountered on a file, a card is punched with a 6/7/8/9 in columns 1
and 80; the remainder of the card is blank. This card is offset.
• If a compare error is encountered, the erroneous card and the following card are
offset. These two cards are repunched until no error Is detected. An EOI card with
6/7/8/9 punches in columns 1 and 80 contains a binary count in column 40 of the
number of compare errors.
• During the punching of each file, the system maintains a count of the number of
cards punched for the file. If the number exceeds the limit for which the user is
validated, punching of the file is terminated. A special banner card with the word
LIMIT is punched and offset as the last card of the deck.
The following methods are used by the system to punch each of the three forms of cards.
CODED CARDS (PUNCH)
With the exception of decks punched via the ROUTE command, the keypunch mode (026 or 029) of
coded cards depends on the job origin type. If the job is of local batch origin, decks are
punched in the initial keypunch mode (that is, the mode specified on the job card or set by
system default). For all other job origin types, decks are punched in the system default
keypunch mode.
BINARY CARDS (PUNCH B)
The card punch driver retrieves 15 words of binary data from central memory. The driver
then generates a checksum for the data and issues a card number. The card punch controller
receives the binary data and punches it on the card unchanged, that is, in 12-bit codes.
Each row in a card column corresponds to a bit position. The driver formats the binary card
in the following manner.
Column(s) Contents
1 7/9 punch denotes binary card.
Rows 0, 1, 2, and 3 contain the binary equivalent of the word count
of the card.
2 Binary data checksum (modulo 4095).
3 through 77 Fifteen central memory words of binary data.
78 Blank.
79 and 80 24-bit binary card sequence number.
F-6 60459680 C
![](asset-2c1.png)
ABSOLUTE BINARY CARDS (P8)
Absolute binary cards are central memory images in 12-bit codes. Each row in a card column
corresponds to a bit position. Sixteen central memory words are punched per card with no
special punches or fields added.
60459680 C F_7
![](asset-2c2.png)
/^I\
)
![](asset-2c3.png)
ANSI TAPE LABEL FORMATS
0r^*>
/^^*V
ANSI labels perform two functions. They provide information that uniquely identifies a file
and the reel on which it resides, and they mark the BOI and EOI of a file and the beginning
and end of a reel.
ANSI labels are designed to conform to the American National Standard Magnetic Tape Labels
for Information Interchange X3.27-1969. All labels are 80 characters long and are recorded
at the same density as the data on the tape. The first three characters of an ANSI label
identify the label type. The fourth character indicates a number within a label type.
Labels padded to longer than 80 characters and which otherwise meet the ANSI X3.27-1969
standard are not processed by NOS as ANSI labels. Tapes with padded labels can be processed
as unlabeled tapes by using the F, S, or L format (in this case, the label data is read or
written by a user program).
The following is a summary of each label type, name, function, and whether or not it is
required.
Type No
VOL
UVL 1-9
HDR
HDR 2-9
UHL
EOF
EOF 2-9
UTL
EOV
EOV 2-9
Name
Volume header label
User volume label
File header label
File header label
User header label
End-of-file label
End-of-file label
User trailer label
End-o f-volume label
End-of-volume label
Used As
Beg inning-of-volume
Beg inning-of-volume
Beginning-of-information
Beginning-of-information
Beg inning-of-informa tion
En d- of -i nf or ma ti on
End-o f-info rma tion
En d- of -i nf or ma ti on
End-o f-volume
End-o f-volume
Required/Optional
Required
Optional
Required
Optional
Optional
Required
Optional
Optional
Required when
appropriate
Optional
REQUIRED LABELS
The VOL1, HDRl, and E0F1 labels are required on all ANSI-labeled tapes. In addition, an
E0V1 label is required if the physical end-of-tape reflector is encountered before an E0F1
label is written or if a multifile set is continued on another volume. In the descriptions
of the contents of these labels, n is any numeric digit and a is any letter, digit, or any
of the following special characters.
tAny member of the CDC 6-bit subset of the ASCII character set.
60459680 C G-l
![](asset-2c4.png)
Space
&
/ : ]
( ;
Some fields are optional. An optional field which does not contain the designated
information must contain blanks. Fields which are not described as optional are required
and written as specified, n-type fields are right-justified and zero-filled, and a-type
fields are left-justified and blank-filled.
VOL 1—VOLUME HEADER LABEL
The volume header label must be the first label on a labeled tape. All reels begin with a
V0L1 label. If two or more reels belong to a volume set, the file section field in the
following HDRl label gives the actual reel number.
^/iSSV
VOL volume serial number
va reserved
reserved
reserved
owner
identification
owner identification (oid)
oid reserved
reserved
reserved lsl
«*^^y
G-2 60459680 C
![](asset-2c5.png)
Character
Position Field Name
1-3 Label
identifier
Length
(in Characters) Contents
Must be VOL.
Default
Checked on
Read
Yes
Checked on
Overwrite
No
4
5-10
yfP^V
12-31
32-37
Label number
Volume serial
number
A c c e s s i b i l i t y
(va)
Reserved for
future standard
ization
Reserved for
future standard
ization
20
Must be 1.
Volume identification
assigned by owner to
identify this physical
r e e l o f ta p e . I f t h e
volume serial number
is all blanks, the
tape is a scratch tape.
An a character which
indicates the restric
tions , If any, on
who may have access
to the information
on the tape. A
blank means un
limited access.
Any other character
means special
handling, in the
manner agreed
between the inter
change parties.
Refer to the
BLANK command.
Must be blanks.
Must be blanks.
As read from
existing label
Blank (un
limited access)
Yes
Yes, if the
file was
assigned by
volume serial
number.
No (refer to
BLANK command.
No
No
Yes
No No
No
38-51 Owner identi
fication (oid)
1A Any a characters
identifying the
owner of the physical
volume.
family
name, user
name
Refer to dis
cussion of fa
field of HDRl.
Yes
52-79
80
Reserved for
future standard
ization
Label standard
level (lsl)
28 Must be blanks.
A 1 means the labels
and data formats on
this volume conform
to the requirements
of the ANSI standard.
A blank means the
labels and data for
mats on this volume
require the agreement
of the interchange
pa r t i e s.
No
60459680 C G-3
![](asset-2c6.png)
HDRl—FIRST FILE HEADER LABEL
The first file header label must appear before each file. When a file is continued on more
than one volume, the file header label is repeated after the volume header label on each new
volume for that file. If two or more files are grouped in a multifile set, each HDRl label
indicates the relative position of its associated file within the set.
HDR file identifier (fi)
file identifier (fi)
fiset identification
file section
number (secno)
secno
fi l e
sequence number generation number gvn
gvn creation date expiration date
expiration
date fa block count
system code
system code reserved
^X^WlV
G-4 60459680 C
![](asset-2c7.png)
Character
Position Field Name
Label
identifier
Length
(In Characters)
3
Contents
1_3 Must be HDR.
it Label number Must be 1.
5-21 F i l e i d e n t i fi e r
(fl)
17 Up to 17 a chara
used as the file
Default
22-27
/#^N
32-35
S e t i d e n t i fi c a t i o n 6
28-31 File section
number (secno)
File sequence
number
tiflcation (fileid)
parameter on the
LABEL command.
Up to six a characters
used as the setid
parameter on the
LABEL command. To
conform to the ANSI
tape standard, this
value is the same
for all files of
a m u l t i fi l e s e t .
Four n characters
identifying the file
section number.
The file section
number of the first
HDRl label of a file
is 0001. If the file
extends to more than
one volume, this
n u m b e r i s i n c r e
mented by one for
each subsequent
v o l u m e . T h i s v a l u e
c o r r e sp o n ds t o t h e
secno parameter on
the LABEL command.
F o u r n c h a r a c t e r s u s e d
as t h e s e q no p a ra me t e r
on the LABEL command -
This parameter specif-
fies the position of
a fi l e w i t h i n a fi l e
s e t . T h i s v a l u e i s
0001 for the first file,
0002 for the second,
a n d s o o n . I n a l l t h e
labels for a given file,
this field contains the
same number.
Blank
B l a n k ; a n
appended file
is given the
same set iden
tification as
its preceding
file.
0001
Checked on
Read
Yes
Checked if
specified.
C h e c k e d I f
specified.
Checked on
Overwrite
No
No
No
No
Checked if
specified.
No
0001 Checked if
specified.
60459680 C G-5
![](asset-2c8.png)
Character
Position
36-39
Field Name
Generation
number
(optional)
Length
(in Characters) Contents
Four n characters
specifying the gen
e r a t i o n n u m b e r o f a
file. This is the
genno parameter of
the LABEL command.
This value is 0001
for the first genera
tion of a file, 0002
for the second, and
Checked on
Default
0001
Checked on
Read
Checked if
specified.
Overwrite
No
40-41 Generation
version
n u m b e r ( g r n )
Two n characters used
to distinguish suc
cessive iterations
of the same genera
tion. The generation
version number of
the first attempt to
create a file is 00.
This value corre
sponds to the gvn
parameter of the
LABEL command.
00 Yes No
42-47 Creation date
48-53 Expiration date
Date the file was Current date
created; it is re
corded as a space
f o l l o w ed b y t wo n
characters for the
year followed by
t h r e e n c h a r a c t e r s
for the day within
the year. This value
c o r r e sp o n ds t o t h e
edate parameter of
the LABEL command.
The file is considered Current date
expired when today's
da t e Is t h e s am e a s o r
l a t e r t h a n t h e d a t e
given in this field.
When this condition is
satisfied, the remainder
of the volume may be
overwritten. Thus, to be
effective on multifile
volumes, the expiration
d a t e o f a fi l e m u s t b e
earlier than or the same
as the expiration date of
Yes. The crea
tion date is
meaningful only
on read opera
tions; on write
operations, the
current date is
always used.
Yes
G-6 60459680 C
■^®\
![](asset-2c9.png)
Character
P o s i t i o n Field Name Length
(in Characters)
54 A c c e s s i b i l i t y
( f a )
5 5- 6 0 B lo c k c ou n t
61- 73 Syst em c ode
Contents
all preceding files on
the volume. The ex
piration date is writ
ten in the same format
as the creation date.
It corresponds to the
rdate parameter of the
LABEL command.
An a character which
indicates the restric
tions, if any, on who
may have access to
the information in
this file. A blank
means unlimited ac
c e s s . I f f a i s A ,
only the owner of
the NOS written
tape can access the
fi l e . I f f a i s a n y
other character, all
future accesses to
the tape must specify
this character as
the fa parameter.
File accessibility is
not checked for sys
tem origin jobs.
Default
Checked on
Read
Checked on
Overwrite
Blank (un
limited access) Yes, if a
NOS written
tape.
Yes
6 Must be zeros.
13 Thirteen characters NOS ver-est
identifying the op (ver is the
erating system that system version
reco r d e d t hi s fi l e . number and est
The tape is con is the EST ordi
sidered to have nal of the unit
been written under on which the
NOS if the first 10 fi le w a s
characters match the w r i t t e n ) .
default.
No No
No
74-80 Reserved for
future stan
dardization
Must be spaces. No
z^B>v
60459680 C G-7
![](asset-2ca.png)
EOF!—FIRST END-OF-FILE LABEL
The end-of-file label is the last block of every file. It is the system end-of-information
for the file. A single tape mark precedes E0F1. A double tape mark written after the E0F1
label marks the end of a multifile set.
EOF file identifier (fi)
file identifier (fi)
fiset identification
file section
number (secno)
secno
file
sequence number generation number gvn
gvn creation date expiration date
expiration
date fa block count
system code
system code reserved
Character
Position Field Name
1-3 Label
identifier
4Label number
Length
(in Characters)
5-54 Same as corre
sponding fields
ih HDRl (optional)
50
Contents
Must be EOV.
Must be 1.
Same as the corresponding
fields in HDRl.
Default
Checked on
Read
Yes
Yes
Same as HDRl.
55-60
61-80
Block count
Same as corre
sponding fields
iii HDRl (optional)
20
Six n characters specifying
the number of data blocks
between this label and the
preceding HDR label group.
This total does not include
labels or tape marks.
Same as corresponding fields
in HDRl.
Yes
Same as HDRl.
G-8 60459680 C
![](asset-2cb.png)
ziP^s
EOV1—FIRST END-OF-VOLUME LABEL
The end-of-volume label is required only if the physical ehd-of-tape reflector is
encountered before an E0F1 label is written or if a multifile set is continued on another
volume. E0V1 is preceded by a single tape mark and followed by a double tape mark.
0@&\.
fi
secno
gvn
E O V 1 file identifier (fi)
file identifier (fi)
set identification
fi l e
sequence number
file section
number (secno)
generation number
creation date
expiration
date fa
gvn
expiration date
block count
system code
system code reserved
Character
Position Field Name
1-3. Label
identifier
4Label number
J0^\ 5-54
55-60
61-80
Length
(in Characters)
Same as corre
sponding fields
in HDRl (optional)
Block count
Same as corre
sponding fields
in HDRl (optional)
50
20
Contents
Must be EOF.
Must be 1.
Same as the corresponding
fields in HDRl.
Six n characters specifying
the number of data blocks
between this label and the
preceding HDR label group.
This total does not include
labels or tape marks.
Same as corresponding fields
in HDRl.
Default
Checked on
Read
Yes
Yes
Same as HDRl.
Same as HDRl.
60459680 C G-9
![](asset-2cc.png)
OPTIONAL LABELS
Six types of optional labels are allowed. They are additional file header (HDR2-9),
end-of-file (EOF2-9), user volume (UVLa), header (UHLa), and trailer (UTLa) labels.
HDR2 THROUGH HDR9—ADDITIONAL FILE HEADER LABELS t
HDR2 through HDR9 labels may immediately follow HDRl. Their format is:
Character
Position
1-3
Field Name
Label
identifier
Label number
Length
(in Characters) Contents
HDR
2-9
4 Label number 1
5-80 76
Only the label identifier and the label number are checked on read.
EOF2 THROUGH EOF9—ADDITIONAL END-OF-FILE LABELS t
E0F2 through E0F9 labels may immediately follow E0F1. Their format is:
Only the label identifier and the label number are checked on read.
EOV2 THROUGH EOV9—ADDITIONAL END-OF-VOLUME LABELS t
E0V2 through E0V9 labels may immediately follow E0V1. Their format is:
Default
Written
HDR
2-9
Character
Position Field Name
Label
identifier
Leng th
(in Characters)
3
Contents
EOF
Default
Written
1-3 EOF
4Label number 2-9 2-9
5-80 76
Character Length Default
Position Field Name (in Characters) Contents Written
1-3 Label
identifier
EOV EOV
4Label number 2-9 2-9
5-80 76
tThese are reserved for operating system use. Attempts by user programs to generate them
will produce undefined results.
'*^%V
s^k.
G-10 60459680 C
![](asset-2cd.png)
/P^N
Refer to section 3 in Volume 4, Program Interface, for a description of the use of E0V2
labels in conjunction with CLOSER, REWIND, and UNLOAD macros.
USER LABELS
User labels may immediately follow their associated system labels. Thus, user volume labels
(UVLa) may follow V0L1, user header labels (UHLa) may follow the last HDRn label, and user
trailer labels (UTLa) may follow the last EOVn or EOFn label. Their format is:
Character
Position
1-3
Field Name
Label
identifier
Label number
Length
(in Characters)
5-80 User option 76
Contents
UVL, UHL, or UTL.
Must be 1, 2, 3, 4,
and so on, consec
utively for UVL labels.
For other labels, any
a character.
Any a characters.
Default
Written
UVL, UHL,
or UTL.
Only the label identifier and the label number are checked on read. The system checks the
number of user labels of a label type; a maximum of 64 is allowed.
j^PS.
60459680 C G-ll
![](asset-2ce.png)
![](asset-2cf.png)
0^\
/$sB*?\
LINE PRINTER CARRIAGE CONTROL H
Appendix H provides information required to prepare files for printing.t The information
includes the following:
• NOS-supported paper lengths.
• Carriage control characters.
• Punched tape channel formats (non-PFC printers only).
• PFC, EVFU, and VFU arrays.
For the 5870 Non-Impact Printer, applicable information in this section is contained under
Printed Data below and in table H-l. Note that the Q, R, S, T, and V carriage control
characters are not supported by the 5870 printer. If encountered in a print file, these
characters are ignored.
Default characteristics for the 5870 printer, such as the print font, page length, and print
density are determined by the site. Check with your site administration for this
information.
For further information on the functional characteristics of the 5870 printer, refer to the
5870 Site Reference Manual.
PRINTED DATA
All data to be printed is in coded format in a file within the print queue. The data
consists of either 6-bit or 12-bit codes. Data recorded using the 6/12-bit display code set
(refer to appendix A) should be converted to the 7-bit ASCII code set (refer to the FCOPY
command in section 9) before being routed to a line printer.
The system extracts data until an end-of-line occurs or until 137 characters are retrieved.
End-of-line is 12 or more zero bits in the rightmost byte of a central memory word.
PAPER LENGTH
580 LINE PRINTERS
NOS supports two paper lengths for 580 line printers, standard (14 inches x 11 inches) and
short (14 inches x 8 1/2 inches). Files routed to a line printer must be properly formatted
for the paper length used on the specified printer.
TThe information in this appendix does not apply to remote batch line printers.
60459680 H H_!
![](asset-2d0.png)
When printing on standard paper size, you have the option of specifying a print density of
either 6 or 8 lines per inch. At 6 lines per inch, a maximum of 64 lines per page can be
printed on standard paper. At 8 lines per inch, a maximum of 84 lines per page can be
printed on standard paper.
All output printed on short paper is printed at a density of eight lines per inch. The
carriage control characters used to specify print density (S and T) are ignored. A maximum
of 66 lines can be printed on one page of short paper; overflow lines, if any, are printed
on the following page.
A system default print density is used if you do not specify one for your print file. The
system default is site selectable using the SPD IPRDECK entry; refer to NOS 2 Analysis
Handbook for more information on SPD IPRDECK entry.
533/536 AND 585 PRINTERS
The 533/536 and 585 printers are supported by the Printer Support Utility (PSU). These
printers can accommodate 8 1/2-, 11-, and 12-inch paper sizes. Modifying the EVFU load file
(for 533/536 printers) or the VFU load procedure (for 585 printers) enables these printers
to use other paper sizes. Refer to the NOS 2 Analysis Handbook for more information on PSU,
and the EVFU load file. Refer to the CDCNET Network Configuration and Site Administration
Guide for more information on the VFU load procedure.
Unlike the 580 printers, the 533/536 and 585 printers support both six and eight lines per
inch print densities for short paper output, as specified by the S and T carriage control
characters.
CARRIAGE CONTROL
You can control the format of printer output using the carriage control characters listed in
table H-l and table H-2. The system interprets the first character in a line as the
carriage control character and that character is not printed.t The remainder of the line
is then printed, except when a Q, R, S, T, or V carriage control character is specified.
The Q, R, S, T, and V format controls remain in effect until changed; all other carriage
control characters must be supplied for each line they control.
Line spacing is normally done in auto eject mode; that is, creases in the paper are skipped
by the line printer's automatic line spacing mechanism if the paper is loaded properly.
Auto eject mode must be turned off if you want to select format channels to advance printing
from a position above the bottom of form to a position beyond the next top of form.
The 585 printers support all carriage control characters. The 533/536 printers support all
carriage control characters except V. Note that a page eject is issued to the 533/536 and
585 printers whenever the print density is changed or when auto page eject is either set or
cleared. Also, for 533/536 printers, auto page eject is set to ON whenever the print
density is changed.
The system limits the number of lines you can print from a given file (refer to the LIMITS
command). Your site can further limit the number of lines you can print by establishing a
minimum number of lines per page for which you will be charged. During the printing of each
file, the system maintains a count of the number of lines printed or skipped for the file.
If the number exceeds the limit for which you are validated, printing of the file is
terminated. The informative diagnostic LINE LIMIT EXCEEDED is printed. If a job's dayfile
is p art of t he te rmi nat ed fil e, the day fil e is s ubs equ en tly prin ted .
t To print a file in which the first character of each line is not a carriage control
character, refer to the COPYSBF command in section 9.
H"2 60459680 H
![](asset-2d1.png)
Table H-l. Carriage Control Characters for 512/580 and 5870 Printers
Character
space
1
0
+
/
2
PM
Q
R
sttt
Tttt
V
8
7
6
5
4
3
H
G
F
E
D
C
512/580
Line
Charge
Page
Size
2
3
1
1
Page
Size/2T
0
0
0
0
Page
Sizet
1
2
2
3
3
4
1
2
2
3
3
4
5870
Line
Charge Action
Single space.
Eject page before printing.
Skip one line before printing (double space).
Skip two lines before printing (triple space).
Suppress carriage advance before printing (overprint).
Sup pr es s carr ia ge adv an ce after p ri nt in g (overpri nt).
Skip to last line of form (format channel 12) before printing.
Stop printer and display the rest of the line at the operator
console; used to issue a change forms request or other
instructions to the operator.
Clear auto eject;tt remainder of line is not printed.
Set auto eject; remainder of line is not printed.ttttt
Print 6 lines per inch (remainder of line is not printed) .ttttt
Print 8 lines per inch (remainder of line is not printed).ttttt
Eject page before printing on a 580 PFC printer; loads a
user-specified PFC array .tttt ttttt
Skip to top of page (format channel 1) before printing.
Skip two lines (format channel 2) before printing.
Skip three lines (format channel 3) before printing.
Skip four lines (format channel 4) before printing.
Skip five lines (format channel 5) before printing.
Skip one page (format channel 6) before printing.
Skip to top of page (format channel 1) after printing.
Skip two lines (format channel 2) after printing.
Skip three lines (format channel 3) after printing.
Skip four lines (format channel 4) after printing.
Skip five lines (format channel 5) after printing.
Skip one page (format channel 6) after printing.
t Page size is 64 lines per page if 6 lines per inch is selected or page size is 85
lines per page if 8 lines per inch selected,
tt When printing at 8 lines per inch, a Q carriage control character also causes a 580
printer to revert to 6 lines per inch (except when short paper is used),
tttNo line feed after printing; for all other control characters, a line feed is issued
after printing. The S and T control characters are ignored when short paper is
specified; short paper output is printed at 8 lines per inch,
ttttYou must be properly validated to use the V carriage control character,
tttttNot supported by the 5870 Non-Impact Printer.
60459680 H H-3
![](asset-2d2.png)
Table H-2. Carriage Control Characters for 585 Printers (Sheet 1 of 2)
Character
space
1
0
+
/
2
PM
Q
R
S
T
V
8
7
6
5
4
3
9
X
Y
Z
585
Line Charge
Page Sizet
2
3
0
0
tt
ttt
tttt
tttt
tttt
tttt
tttt
t
2
3
4
5
6
7
8
9
10
Action
Single space.
Eject page before printing.
Skip one line before printing.
Skip two lines before printing.
Sup pr es s carr ia ge ret ur n befo re pri nt in g (ove rp ri nt ).
Suppress carriage return after printing (overprint).
Skip to last line of form (format channel 12) before printing.
Stop printer and display the rest of the line at the operator
console; used to issue a change forms request or other
instructions to the operator.
Clear auto eject; remainder of line is not printed .ttttt
Set auto eject; remainder of line is not printed .ttttt
Print 6 lines per inch; remainder of line is not printed .ttttt.
Print 8 lines per inch; remainder of line is not printed .ttttt
Eject page before printing; loads a user specified vertical
format unit (VFU). ttttt
Skip to top of page (format channel 1) before printing.
Skip two lines (format channel 2) before printing.
Skip three lines (format channel 3) before printing.
Skip four lines (format channel 4) before printing.
Skip five lines (format channel 5) before printing.
Skip six lines (format channel 6) before printing.
Skip to format channel 7 before printing.
Skip to format channel 8 before printing.
Skip to format channel 9 before printing.
Skip to format channel 10 before printing.
t Number of lines remaining on the page. Page size is 66 if 6 lines per inch is
selected and 88 if 8 lines per inch is selected.
tt Half the number of lines remaining on the page,
ttt Number of lines remaining on the page minus 2. If the number of lines remaining on
the page is less than 2, count page size.
Number of lines according to required paper movement: 0 if format effector is ignored
or discarded; 1 if line is printed with single spacing; number of lines remaining if a
VFU load with page eject is required.
Causes page eject when action is complete. Undefined or unsupported control
characters are discarded. Lines containing control characters redefining an existing
condition are processed with the unsupported format effector action specified by your
site.
H-4 60459680 H
![](asset-2d3.png)
Table H-2. Carriage Control Characters for 585 Printers (Sheet 2 of 2)
Character
W
U
A
B
H
G
F
E
D
C
I
J
K
L
M
N
585
Line Charge
t
12
t
tt
t
2
3
4
5
6
7
8
9
10
t
12
Action
Skip to format channel 11 before printing.
Skip to format channel 12 before printing.
Eject page after printing.
Sk ip to la st line of fo rm af te r p ri nt in g.
Skip to top of page (format channel 1) after printing.
Skip two lines (format channel 2) after printing.
Skip three lines (format channel 3) after printing.
Skip four lines (format channel 4) after printing.
Skip five lines (format channel 5) after printing.
Sk ip six li nes (for mat ch ann el 6 ) afte r prin ting .
Skip to format channel 7 after printing.
Skip to format channel 8 after printing.
Skip to format channel 9 after printing.
Skip to format channel 10 after printing.
Skip to format channel 11 after printing.
Skip to format channel 12 after printing.
tNumber of lines remaining on the page. Page size is 66 if 6 lines per inch is
selected and 88 if 8 lines per inch is selected,
tt Number of lines remaining on the page minus 2. If the number of lines remaining on
the page is less than 2, count page size.
/$pfe\
r60459680 H H-4.1
![](asset-2d4.png)
FORMAT CHANNEL SELECTION ON NON-PFC PRINTERS
Non-PFC line printers, other than 533/536 and 585 printers, use a punched tape loop to
control carriage advancement. Figure H-l shows the released tape format for printers using
the standard paper size at 6 lines per inch. Figure H-2 shows the tape format for short
paper printers.
The format tape shown in figure H-l can be ordered as customer engineer's part number
44682683.
Each line, or frame, in the tape format represents one line of printer output. Notice, in
figure H-l, that frames 132 through 134 are identical to frames 0 through 2. To form a
continuous loop, the ends of the tape are fastened together with the first three frames (0
through 2) superimposed over the last three frames (132 through 134). This leaves a tape
loop consisting of 131 frames. The tape format in figure H-l represents two pages of
64-line printer output. The blank lines at frames 64 and 65, and at frames 130 and 131,
represent spaces for the creases between pages.
Each channel controls a specific carriage control operation. Channel 1, for example,
provides for top of page spacing, channel 3 controls triple spacing of lines, and channel 12
spaces to the bottom of the page.
For postprint operations, when the carriage control character in column 1 of a print line
specifies a channel number, the printer checks that format channel, in the current frame,
for a punch. If a punch is found, the printer prints the line. If no punch is found, the
printer advances the punched tape loop (and, at the same time, the printer carriage) until a
punch is found in that channel in a subsequent frame. At that point, the printer prints the
line.
As an example of format channel usage, assume that the printer carriage is positioned at the
second line of a page (frame 1 of the format tape). Also assume that the second output line
contains a carriage control character of 2. The printer checks frame 1 and finds no punch
in channel 12, so it advances to the next frame containing a punch in channel 12. The next
punch occurs in frame 63 (line 64); therefore, the second output line is printed as the last
line on the page.
FORMAT CHANNEL SELECTION ON 533/536 PRINTERS
Format channel selection for 533/536 and 585 printers is defined by the EVFU load file and
the VFU load procedure respectively. Refer to the NOS 2 Analysis Handbook for a description
of the EVFU load file. Refer to the CDCNET Network Configuration and Site Administration
Guide for a description of the VFU load procedure.
H_4'2 60459680 H
![](asset-2d5.png)
/#*N
/pf^
Frame
0
Channelq Fram
12 11 10
X X 68
1X69
2XX70
3XXX71
4X X X72
5XX73
6X X XX74
7XX75
8XX X X76
9X X X77
10 78
11 79
12 80
13 81
14 82
15 83
16 84
17 85
18 86
19 87
20 88
21 89
22 90
23 91
24 92
25 93
26 94
27 95
28 96
29 97
30 98
31 99
32 100
33 101
34 102
35 103
36 104
37 105
38 106
39 107
40 108
41 109
42 110
43 111
44 112
45 113
46 114
47 115
48 116
49 117
50 118
51 119
52 120
53 121
54 122
55 123
56 124
57 125
58 126
59 127
60 128
61 129
62 130
63 131
64 132
65 133
66 134
67
12
Channels
11 10
Figure H-l. Carriage Control Tape Format (Standard Paper Length; 6LPI)
60459680 D H-5
![](asset-2d6.png)
Frame
0
Channels Frame
70
Channels
12 11 10 8 | 7 12 11 10 -5
XX X X X
1X71
2XX72
3X X 73
4XX X X 74
5X X 75
6XX X 76
7X X 77
8X X X X X 78
9X X 79
10 80
11 81
12 82
13 83
14 84
15 85
16 86
17 87
18 88
19 89
20 90
21 91
22 92
23 93
24 94
25 95
26 96
27 97
28 98
29 99
30 100
31 101
32 102
33 103
34 104
35 105
36 ld6
37 107
38 108
39 109
40 110
41 111
42 112
43 113
44 114
45 115
46 116
47 117
48 118
49 119
50 120
51 121
52 122
53 123
54 124
55 125
56 126
57 127
58 128
59 129
60 x • 130
61 131
62 132
63 133
64 134
65 135
66 136
67 137
68 138
69
Figure H-2. Carriage Control Tape Format (Short Paper Length; 8 LPI)
H-6 60459680 D
![](asset-2d7.png)
CARRIAGE CONTROL ARRAYS
Line spacing on a printer is controlled by a carriage control array. This array has the
following forms for the various printers:
• Programmable format control (PFC) array for 580 printers.
• Carriage control tape for non-PFC 580 printers.
• Electronic vertical format unit (EVFU) for 533/536 printers.
• Vertical format unit (VFU) for 585 printers.
The selection of an array for any printer is dependent on the print density and the paper
length to be used. You can specify one of several arrays already defined by the system
using the SC parameter on the ROUTE command. These arrays are described in the NOS 2
Analysis Handbook. You can also select a user-specified PFC or VFU array to control print
spacing. You must have validation to use a user-specified PFC array (refer to the LIMITS
command). A user-specified array remains in effect until another array is encountered or
the end-of-file is reached. The print density for printers using standard sized paper is
selected using the S or T carriage control characters. 580 printers using short paper
always use a print density of 8 lines per inch and ignore S and T.
A user-specified array begins with the control character V. When a V is encountered, the
prin ter ejects th e page. For no n-P FC 580 printers, the rest of the li ne is ignored. F or
PFC 580 printers, if your are not validated to use the V carriage control character, the
print operation aborts and you receive an appropriate message in your output file.
ARRAY SYNTAX
An array consists of a string of alphanumeric characters that can be used to redefine some
or all of the format channels of the previously specified array. An array for output at 6
lines per inch occupies one line of up to 132 characters plus the terminator for 580
printers, up to 127 characters for 585 printers. An array for 8 lines per inch may occupy
one or two lines. For printing on standard length paper, an array for 8 lines per inch can
consist of up to 176 characters on 580 printers, 127 characters on 585 printers (88 lines
per page). For short paper printers, an array for 8 lines per inch must not exceed 136
characters plus the terminator for 580 printers, 127 characters for 585 printers (68 lines
per page).
Column 1 of an array must contain the carriage control character V. The second character of
the array determines which array is changed and may be one of the following values.
Value
6
8
C
Description
6 lines per inch; the entire array specification occupies one line.
8 lines per inch; the entire array specification occupies one line.
8 lines per inch; the array specification continues onto a second
line. The second line begins in column 3; columns 1 and 2 of the
second line are ignored.
60459680 H H - 7 •
![](asset-2d8.png)
><S^^V
The array must be terminated by the letter 0. Starting in column 3 and continuing up to the
column that precedes the array terminator (letter 0), each column in the array represents
one line of printer output. A format channel indicator placed in one of these columns in a
user-specified array changes the format channel in effect for the corresponding output
line. If an array column is left blank, the format channel for the corresponding line
remains unchanged. The channel indicators that can be inserted in these columns are as
follows.
Character Significance
Specifies top of form code (channel 1); mandatory entry in column 3
of the array (representing output line 1). Delete previous
channels.
B through L Specify format channels 2 through 12, respectively. Delete
previous channels.
M S p e c i fi e s a u t o p a g e e j e c t . A p p l i e s t o 5 8 5 p r i n t e r s o n l y .
N Specifies bottom of form code (channel 12). Applies to 585
p r i n t e rs o n l y.
0
X
Blank
Array terminator.
Remove the channel format previously in effect for the line.
Applies to 585 printers only.
No channel is specified; the channel format previously in effect
for the line remains unchanged.
Each channel number referenced in your PFC array must appear in the PFC array previously in
effect. Channel specifications can be repeated within an array.
NOTES
If a PFC array contains an invalid
character, the array line is printed, and
the printing of the file is terminated.
Other arrays with invalid characters are
ignored, and the file is printed using the
carriage control array previously loaded
into the printer.
If a VFU array contains an invalid
character, the line containing the V control
character is processed according to the
undefined format effector action.
H-8 60459680 H
![](asset-2d9.png)
Following are some examples of invalid array specifications:
Invalid Array Error
V6BCD 0 Does not contain an A in column 3.
VBA C DEO Second character is not 6, 8, or C.
V8ABWC0 Contains an invalid character (W).
V6A 0 Contains a zero for the terminator.
RESERVED FORMAT CHANNELS
For printers that support format channels, three channels are reserved for specific carriage
control operations. Channel 1 is always used to position the paper to the top-of-form. Two
additional site selected channels are also reserved: one for positioning the paper to the
logical bottom-of-form, and one for skipping over the perforations between forms (auto page
eject). Each of these channels may appear only once in a VFU array. By default, both the
bottom-of-form and auto-page-eject channels will be placed two lines above the physical end
of the form. If the operator or user changes form size or print density, the bottom-of-form
and auto-page-eject channels are moved to accomodate the change in the number of lines on
the form. If the auto-page-eject option is changed, then the auto-page-eject channel is
removed and restored in the VFU array.
EXAMPLE
The following is an example of an array used to print a special 8-line form.
Suppose you want to print on the top, fifth, and bottom lines of an 8-line form (at 8 lines
per inch print density). Load the following array:
Columns: 123456789 10 11 12
V 8 A B N O
Since columns 4, 5, 6, 8, 9, and 10 are blank, the format channels for these columns remain
unchanged from the array previously in effect. You might want to put an X or a dummy
channel indicator (that is, a valid channel indicator that is not otherwise referenced in
the file), such as a K, into these columns to ensure that the B and N channel indicators
appear only where intended.
After loading the example array above, output lines beginning with an 8 or H (format channel
1) are printed at the top of the form, lines beginning with a 7 or G (format channel 2) are
printed at the fifth line, and lines beginning with a 2 (format channel 12) are printed at
the bottom of the form.
0Ss^\
60459680 H H-9
![](asset-2da.png)
![](asset-2db.png)
OBSOLETE TAPE FORMATS
The B, E, and X format coded tapes are no longer supported by NOS. The following
description of the physical and logical characteristics of the obsolete tapes is Included as
a reference for you if you use the TCOPY command.
B (BLOCKED) FORMAT
Characteristics
Header
Mode
Block size (PRU size)
yf^\
Logical end-of-record
Logical end-of-file
Logical end-of-information
En d- of -r ee l
Noise
Special considerations
Description
Unlabeled.
Coded.
The block size cannot exceed 5120 frames. If the
tape unit will not allow an odd number of frames to
be written, the system will append a space. Unless
you specify otherwise when you request a tape, the
system will assume the maximum block size is 150
frames.
For a write operation, there is no logical
end-of-record. For a read operation, end-of-record
status is returned when a tape mark is encountered.
An additional read operation returns end-of-file
status.
Tape mark.
None.
Refer to option 2 under End-Of-Tape/End-Of-Reel
Conditions.
Any block containing fewer than 18 frames is
considered noise, and is, therefore, ignored.
4 of a
• B-formatted tapes cannot be labeled.
• A w r it e o p era t io n w i ll s to p e i th e r a t a z er o b y te (en d -o f -l i ne) i n b yt e
CM word or at a multiple of CM words (rounded up) based on the frame or
characte r cou nt.
• For control word reads, byte count and unused bit count will be set
appropriately. For regular reads, EOL is guaranteed.
• For a c on tro l wo rd w ri te o per at ion , no en d- of- li ne p roce ss ing is do ne. Da ta i s
blocked on tape using the specified frame count. Likewise for a control word
read operation, no end-of-line processing is done; data is transferred to you
as it is re ad .
60459680 C 1-1
![](asset-2dc.png)
y£51£V
E (LINE IMAGE) FORMAT
Charac ter 1st ic s Description
Header
Mode
Block size (PRU size)
Logical end-of-record
Logical end-of-file
Logical end-of-information
End-of-reel
Noise
Special considerations
Unlabeled.
Coded.
The block size cannot exceed 5120 frames. If the
tape unit will not allow an odd number of frames to
be written, the system will append a space. Unless
you specify otherwise when you request the tape, the
system assumes the maximum block size is 136 frames.
For a write operation, there is no logical
end-of-record. For a read operation, end-of-record
status is returned when a tape mark is encountered.
An additional read operation returns end-of-file
status.
Tape mark.
None.
Refer to option 2 under End-Of-Tape/End-Of-Reel
Conditions.
Same as for B-formatted tapes.
/ < ^ \
• E- fo rma tt ed ta pes c ann ot be l abe le d.
• For a write operation, a block of data will stop either at a zero byte
(end-of-line) in byte 4 of a CM word or at the multiple of CM words (rounded
up) based on the frame or character count. The system will then space-fill the
buffer to the number of frames specified. Thus, the amount of data written
will exactly equal the amount specified.
• For a read operation, if there is an odd number of characters, the system will
space-fill the last 6 bits of the last byte and delete all trailing spaces.
For control word reads, byte count and unused bit count will be set
appropriately. For regular reads, EOL is guaranteed.
• For a control word write operation, no end-of-line processing is done. Data is
blocked on tape using the specified frame count. Likewise for a control word
read operation, no end-of-line processing is done; data is transferred to you
as it is rea d.
1-2 60459680 C
![](asset-2dd.png)
/^jS5!\
0$t*t\
X (EXTERNAL) FORMAT
Characteristics
Header
Mode
Block size (PRU size)
Logical end-of-record
Logical end-of-file
Logical end-of-information
En d- of -r ee l
Noise
Special considerations
• X-formatted tapes cannot
• A l l n i n e - t r a c k t a p e s a r e
Description
Unlabeled.
Binary.
Actual data block size can range from 0 to 512
(lOOOg) CM words in exact multiples of CM words.
Any block containing fewer than 512 CM words
represents a logical end-of-record. If a logical
record consists of an exact multiple of 512 words,
the block that denotes the logical end-of-record
consists solely of a 48-bit block terminator.
Tape mark.
None.
Refer to option 1 under End-Of-Tape/End-Of-Reel
Conditions.
Any block containing fewer than eight frames for
seven-track tapes or six frames for nine-track tapes
is considered noise, and is, therefore, ignored.
be labeled.
written in an even multiple of bytes
END-OF-TAPE/END-OF-REEL CONDITIONS
[ The following is a description of the processing options for end-of-tape conditions. You
can select one of these options by default by specifying the data format or you can specify
an option via the PO keyword on a LABEL, ASSIGN, or REQUEST command.
Option P0"= Option Description
1 I Rewrites the block on which the end-of-tape condition is
sensed as the first block on the next volume, if the
system senses the EOT during a write operation. During a
read operation, the block on which the EOT occurred is
ignored and reading continues on the next volume. If a
tape mark and the EOT are sensed at the same time, the EOT
is ignored.
60459680 C 1-3
![](asset-2de.png)
^xsss^
Option P0» Option Description
2 P Writes a trailer sequence following the block on which the
EOT is sensed, if the system senses the EOT during a write
operation. Any data that occurs following the block on
which EOT is sensed, yet before the tape mark, is
ignored. During a read operation, the system transfers
the block on which the EOT is sensed to your job. The
read operation resumes on the next reel. If a tape mark
and the EOT are sensed at the same time, the EOT is
ignored.
The system Is concerned only with the block on which the EOT is sensed. If tapes written
using these options are transferred to another system, any data that occurs on the reel
after this block should be ignored.
>*^!*V
1-4 60459680 C
![](asset-2df.png)
NAM/CCP TERMINAL DEFINITION COMMANDS J I
r
INTRODUCTION
The NAM/CCP network, through which terminals access a host and its applications (like IAF),
can support many types of terminals. All supported terminals are grouped by the network
into 18 standard terminal classes. Each terminal class has specific operating
characteristics, also referred to as terminal characteristics. These terminal
characteristics, taken together, make up a terminal definition and are predefined by the
network to closely match the operating characteristics of actual terminals. The network
accepts changes to any of these terminal definitions through terminal definition commands.
These commands specify one or more parameters, each of which may give a new value to a
terminal characteristic. Tables J-l and J-2 list these terminal definitions, the default
values, and possible values for each of the 18 classes.
The tables use the following abbreviations when identifying the terminal types for each
terminal class:
Abbreviation
HASP
HAZ
Terminal
Terminals using the Houston Automatic Spooling Program
communication protocol.
Hazeltine.
POST
PRE
Tek
TTY
UT
X.25
X3.64
HASP terminals that only support postprint format control.
HASP terminals that only support preprint format control.
Tektronix (teletypewriter emulation).
Teletype•
User Terminal.
Terminals connected to a packet switching network (PSN) using the
X.25 communication protocol.
Terminals conforming to the ANSI X3.64 standard.
When a terminal logs in to the network, either the network assumes it to be of a certain
terminal class or assigns it a terminal class that resembles the terminal's actual
characteristics. If you do not know the terminal class in use, you can enter the CH command
(described in this appendix) to ascertain the terminal class and some of the characteristics
of your terminal. In either case, if the characteristics of your terminal do not match
those of its assigned terminal class, you can change the values of the terminal
characteristics or even change the terminal class by using the terminal definition commands
described in this appendix. You can enter terminal definition commands any time the
terminal is connected to the network (refer to login/logout procedures in Volume 1,
Introduction to Interactive Usage).
60459680 G J-l
![](asset-2e0.png)
When you use a terminal definition command to change a value, that change remains in effect
until the terminal is disconnected from the network or another terminal definition command
is used to change the value. Even application switching and logout do not change the values
of the terminal characteristics if the terminal has not been disconnected from the network.
Disconnecting your terminal from the network (that is, disconnecting the phone and redialing
on dial-up terminals or turning a dedicated terminal off and then on again) causes all
terminal characteristics to be reset to site-defined default values. The site defines these
values using the Network Definition Language (NDL).
You can also reset your terminal's characteristics by entering the TC command. The TC
command resets your terminal characteristics to the default values specified by the
Communications Control Program (CCP). Note that CCP-defined values may differ from the
site-defined NDL values.
It is also possible to change terminal definitions using the TRMDEF command or by using
control byte 16 from an interactive job. Section 8 describes the TRMDEF command under
Terminal Definition Commands. Refer to Volume 4, Program Interface, for information on
control bytes.
J-2 60459680 D
![](asset-2e1.png)
/$^\
TERMINAL DEFINITION COMMAND FORMAT
This section describes the general format of a terminal definition command. The specific
format of each command appears later In this appendix.
General formats:
ct keyword=valuet
ct keywordi^valuei ct keyword2=value2...ct keywordn=valuen
Parameter Description
ct Represents the network control character for your terminal as defined by
the CT terminal definition command. Table J-l gives the default network
control character for your terminal .tt
keyword Represents a mnemonic associated with a terminal characteristic.
value Specifies a particular value associated with the terminal definition
mnemonic. Table J-2 gives the range of values for each terminal
definition keyword. On some commands the =value portion of the command
is optional and defaults to =Y.
keyword^. Same as keyword,
value^ Same as value.
The second format allows you to make multiple terminal definitions in one line. If the line
extends beyond character position 54, the results are unpredictable. Also, if you change
the network control character ct in a concatenated group of commands, the CT command does
not take effect until the remaining commands in the group have been processed.
As with all commands described in this manual, you must press the message transmission key
In order for the system to process your command. Appendix K shows the default message
transmission keys for the various terminal classes. This appendix describes how you can
change the message transmission key (refer to the EB and EL commands).
Example:
To change the page width of a 200 User Terminal, enter these characters
%PW=50
and press the SEND key. The % character is the network control character, PW is the keyword
associated with page width, 50 is the new page width for the terminal, and the SEND key is
the message transmission key for a 200 User Terminal.
jtThe spaces shown are for clarity only. Do not include spaces when you enter a terminal
definition command.
ttYou must press the ATTN key on a 2741-compatible terminal before entering this character.
60459680 C j_3
![](asset-2e2.png)
pj^S^y
I
RESTRICTIONS
You should not enter terminal definition commands while output is in progress. The network
may not be able to perform such commands immediately.
The network presets all user-adjustable terminal characteristics any time you establish a
connection to the network. The site administrators choose these preset values.
Additionally, when a terminal is disconnected from the network and then reconnected, the
network resets any terminal characteristics you have changed to their preset values.
To enter a terminal definition command at asynchronous terminals from which you can enter
more than one line before transmitting (IN=BK is specified), the terminal definition command
must be the last input line in the transmission. If the input is from paper tape (IN=PT is
specified), the tape reader must stop. Unpredictable results can occur if more input
follows the terminal definition command in the transmission block.
Characters or character codes you specify for the value portion of terminal definition
commands are subject to the following restrictions:
• You cannot use the following ASCII characters (or their character codes) in the
value portion of the AB, CN, BS, Bl, B2, CT, EB, or EL commands:
any lowercase or uppercase alphabetic character
any digit 0 through 9
NUL
SOH
STX
DEL ,-^^s
space
o The ASCII characters or character codes you specify for the AB, BS, Bl, B2, CN, CT,
EB, and EL terminal definitions must all be different, except that AB and CN can
have the same value and EB and EL may have the same value.
• If output flow control is used, do not use DCls and DC3s in the AB, CN, BS, Bl, B2,
CT, EB, or EL commands.
TERMINAL DEFINITION COMMANDS ^\
This subsection describes the function and format of each terminal definition command. The
headings consist of the command name (a two-character mnemonic) followed by the terminal
attribute it defines. Generally, the format descriptions do not show the default values or
ranges of values since they vary with terminal class. Tables J-l and J-2 show this
information. If you are unable to find the key on your keyboard that corresponds to a
particular character given in table J-l, consult the documentation for your terminal.
This section refers to categories of terminal classes to which commands apply. The
categories are as follows:
Category Terminal Classes
Asynchronous 1 through 8
M o d e 4 1 0 , 1 1 , 1 2 , 1 3 , 1 5
H A S P 9 , 1 4
Bisynchronous 16, 17
X . 2 5 P S N 1 , 2 , 3 , 5 , 6 , 7 , 8
3270 18
J-4 60459680 D
![](asset-2e3.png)
/SjSP^S
(AB) - ABORT OUTPUT BLOCK CHARACTER
The AB command specifies the character used to abort an output block. When you enter this
character from the terminal as the only character in a line, the current transmission block
of output to the terminal is discarded.
Format:
ct AB=ab
Parameter Description
c t R e pr e s en t s t h e n e two r k c o nt r o l c har a c te r f or y o ur t e rm i n al a s d e fine d b y
the CT terminal definition command.
ab Specifies the new abort output block character. This character must
differ from the characters defined for BS, Bl, B2, CT, EB, and EL.
This command only applies to asynchronous terminals and is not valid for X.25 PSN terminals.
(AR) - AUTOMATIC CHARACTER RECOGNITION
The AR command allows you to change the terminal's character set or its line speed, in many
cases, by means of a switch on the terminal or a removable type ball. You can enter this
command any time after the system prompts you for input, even before you enter your user
name during login.
Format:
ct AR
Parameter Description
c t R e pr e s en t s t h e n e two r k c o nt r o l c har a c te r f or y o ur t e rm i n al a s d e fine d b y
the CT terminal definition command.
After entering the AR command, you must select the terminal speed and enter a carriage
return. The system acknowledges the carriage return operation and indicates that the line
speed recognition is complete by returning two line feeds. If your terminal cannot change
its line speed, no line feed responses occur. At this point, enter a closing parenthesis
followed by a carriage return so that the system can recognize the terminal's new character
set. When the system recognizes the new character set, it issues a line feed and the
message AR ACCEPTED., to indicate you can continue. This is also the auto-re cognition
procedure used to connect the terminal to the system (refer to the login/logout procedures
in Volume 1, Introduction to Interactive Usage).
This command only applies to asynchronous terminals and is not valid for X.25 PSN
terminals. X.25 PSN terminals use the ASCII code and character set.
jm^m^ Ky
60459680 D J-5
![](asset-2e4.png)
(BF) - BLOCKING FACTOR
The BF command sets the size of intermediate data blocks that will be delivered to the
■ application.
Format:
ct BF=bf
Parameter
ct
bf
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies the blocking factor. You can specify the following values
for bf:
bf Description
0 Selects a line feed character and a character count of 100
as data-forwarding signals.
1 Selects a character count of 100 as a data-forwarding
signal.
2 Selects a character count of 200 as a data-forwarding
signal.
I Regardless of the blocking factor, an end-of-line character (usually a carriage return)
forwards data to the application.
(BR) - BREAK KEY AS USER BREAK 1
The BR command determines if the BREAK key (interruption key for interactive output) also
functions as the interruption sequence (user break 1 sequence) when entered during output
and as the cancel character when entered during input.
Format;
ct BR=option
Parameter
ct
option
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Determines if this feature is enabled or disabled. A value of Y
enables and a value of N disables this feature.
This command only applies to asynchronous terminals. For X.25 PSN terminals, the BREAK key
can only function as the interruption sequence whether entered during input or output.
J-6 60459680 H
![](asset-2e5.png)
J^V
(BS) - BACKSPACE CHARACTER
The BS command specifies the character used to delete the previous input character.
Format:
ct BS=bs
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
bs Specifies the new backspace character. This character must differ rom
the characters currently defined for AB, Bl, B2, CN, CT, EB, and EL.
It is possible to backspace only to the beginning of the current physical line; additional
backspaces are disregarded. When a page width of 0 is selected, the network assumes a page
width of 100 characters for backspacing. If the page width is in the range 20 through 56,
backspacing into previous physical lines is sometimes permitted.
This command only applies to asynchronous terminals only.
(Bl) - INTERRUPTION OR USER BREAK 1 CHARACTER
The Bl command specifies the character that, when entered as the only character in a logical
line (interruption character followed by the message transmission key), causes program
interruption.
Format:
ct Bl=ubl
Parameter Description
c t R e p r e s e n t s t h e n e t w o r k c o n t r o l c h a r a c t e r f o r y o u r t e r m i n a l a s d e fi n e d
by the CT terminal definition command.
ubl Specifies the new user break 1 character. This character must differ
from the characters currently defined for AB, BS, B2, CN, CT, EB, and
EL.
The interruption sequence is discussed in section 16. The BR command determines whether the
BREAK key can also function as the Bl character.
This command does not apply to bisynchronous 2780 and 3780 terminals.
60459680 H j-7
![](asset-2e6.png)
/rf5St\
(B2) - TERMINATION OR USER BREAK 2 CHARACTER
The B2 command specifies the character that, when entered as the only character in a logical
line (termination character followed by the message transmission key), causes program
termination.
Format:
ct B2=ub2
Parameter Description
c t R e p r e s e n t s t h e n e t w o r k c o n t r o l c h a r a c t e r f o r y o u r t e r m i n a l a s d e fi n e d
by the CT terminal definition command.
u b 2 S p e c i fi e s t h e n e w u s e r b r e a k 2 c h a r a c t e r. T h i s c h a r a c t e r m u s t d i f f e r
from the characters currently defined for AB, BS, Bl, CN, CT, EB, and
EL.
The termination sequence is discussed in section 16.
This command does not apply to bisynchronous 2780 and 3780 terminals.
(CH) - DISPLAY TERMINAL CHARACTERISTICS
The CH command displays some of the terminal's current characteristics.
Format:
ct CH
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
The CH command produces a display in the following format:
TC=tc,BS=bs,CN=cn,AB=ab,Bl=ubl,B2=ub2,EL=el,EB=eb
where the variable portions appear as ASCII characters if printable, mnemonics (for example,
STX) if nonprintable, or N/A if the attribute is not applicable.
J-8 60459680 F
![](asset-2e7.png)
(Cl) - CARRIAGE RETURN IDLE COUNT
The CI command specifies the number of idle characters to be inserted into the output stream
after a carriage return.
Format;
ct CI=ci
yS&^s
r
Parameter
ct
ci
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies the new carriage return idle count. This value can be from
0 to 127 or the string CA. A value of CA restores the carriage return |
idle count to the default value.
When the network produces a carriage return, the network outputs the specified number of
idle characters before outputting the next line. This allows time for the carriage return
function and ensures that characters are not lost because of printing attempts during the
carriage return operation.
This command only applies to asynchronous terminals.
(CN) - CANCEL CHARACTER
The CN command specifies the character used to cancel the logical line currently being input.
Format:
ct CN=cn
Parameter
ct
cn
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies the new cancel character. This character must differ from
the characters currently defined for BS, Bl, B2, CT, EB, and EL.
When you enter the cancel character as the last character in a line, the entire logical line
in progress is cancelled. The system responds to a cancel line character by printing *DEL*
on the next line and positioning the carriage to the beginning of a new line. The BR
command determines whether the BREAK key can also function as the CN character.
This command does not apply to bisynchronous 2780 and 3780 terminals.
60459680 H J-9
![](asset-2e8.png)
(CP) - CURSOR POSITIONING AFTER INPUT
The CP command determines whether or not the system sends the terminal a response to the
line feed key, the EL character, and the EB character.
Format:
ct CP=option
Parameter
ct
option
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Indicates whether to send a response to the terminal or not
of Y indicates yes and N indicates no.
A value
This command applies only to asynchronous terminals (except 2741s). If CP=Y and IN=KB are
selected, the system responds to the line feed key by sending a carriage return and responds
to an EL or EB character by sending the cursor positioning response specified by the EL or
EB command. If IN=BK is selected or you are at an X.25 PAD terminal, the system responds
only to the EB character by sending the cursor positioning response selected by the EB
command.
^■tSsV
(CT) - NETWORK CONTROL CHARACTER
The CT command specifies a network control character for the terminal. When you enter this
character as the first character of a logical line, it signals that what follows is a
terminal definition command or a special command that the network forwards to your
application with a preemptive status (refer to the interactive status commands in section 8)
Format:
ct CT=char
Parameter Description
ct Represents the current network control character for your terminal.
char Specifies the new network control character. This character must
differ from the characters currently defined for AB, BS, Bl, B2, CN,
EB, and EL.
If you enter the CT command in a line with multiple terminal definitions, the new value char
does not take effect until the complete line is processed.
J-10 60459680 C
![](asset-2e9.png)
(DL) - DELIMITERS FOR SINGLE-MESSAGE TRANSPARENT INPUT MODE
The DL command specifies the delimiters that terminate single-message transparent input
mode. When you initiate transparent input mode (IN=X, IN=XK, or IN=XP), the network reads
your input and sends it to the system without translation until it encounters a delimiter.
If your terminal's parity is set to even, odd, or zero (PA=E, 0, or Z), the parity bit is
stripped (set to zero) before the characters are sent to the host, although no translation
occurs. If your terminal's parity is set to none or ignore (PA=N or I), the parity bit is
not stripped. See the NAM/CCP Terminal Interfaces Reference Manual for more information on
transparent input and parity. The first delimiter encountered terminates transparent input
mode.
Format:
ct DL=Xxx,Ccount,TO
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
Xxx Specifies the 2-digit hexadecimal code (xx) of the character you want
as a delimiter. The network does not send the character as part of
the input data. When you specify a hexadecimal code above 7F, you
must have previously set your terminal's parity to none (PA=N) or
ignore (PA=I); otherwise the network cannot detect the code when it
occurs in a transparent mode message. If the terminal's parity is set
to none, the 8-bit hexadecimal code input from the terminal is matched
against the 8-bit hexadecimal code specified as the delimiter (xx).
If the ter min al's pa rit y is set to ignore, t he bottom 7 b its of the
terminal input are matched against the bottom 7 bits of the specified
delimiter (xx).
Ccount
TO
Specifies a decimal value (count) from 1 to 4095 that functions as a
ch aract er c ount d eli mi ter. T hes e va lu es a re v ali d wit hi n th e
network. However, unless changed during installation, the maximum
logical input line length in IAF (2500 characters) limits you.
Specifies that a timeout of between 200 and 400 milliseconds will be a
transparent mode delimiter.
You can select any of the three types of delimiters: character delimiter (specify Xxx),
character count delimiter (specify Ccount), and timeout delimiter (specify TO).
The parameter values for DL are order-independent and optional. However, you must specify
at least one of the parameter values. You can omit trailing commas if you do not specify
all three types of delimiters.
Entering this command with any number of new delimiters cancels all transparent mode input
delimiters already in effect, including those specified with the XL command.
The DL command applies only to asynchronous and mode 4 terminals. Terminal class 4 is
configured with the RETURN key as the only transparent mode terminator and mode 4 terminals
are configured with the SEND or ETX key as their only transparent mode terminator. For X.25
devices, the PAD forwarding signal always acts as a transparent mode terminator in addition
to any other options selected.
60459680 G J-ll
![](asset-2ea.png)
/ * ^ & V
(EB) - END-OF-BLOCK CHARACTER
The EB command defines the end-of-block character and defines the cursor-positioning
response to that character. The EB character acts as the message transmission key for
terminals operating in block mode (refer to the IN command).
Format:
ct EB=eb,cpr
Parameter
ct
eb
cpr
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies the new end-of-block character. You can specify the
following values for eb:
eb Description
Xxx Specifies the 2-digit hexadecimal code xx of the character
you want as the end-of-block delimiter. This character
must differ from the characters currently defined for AB,
BS, Bl, B2, CN, and CT.
EB Selects the default end-of-block character or character
sequence.
EL Selects the current logical end-of-line character.
Specifies the cursor-positioning response to the EB character. You
can specify the following values for cpr:
cpr Description
CR Send a carriage return to the terminal.-
LF Send a line feed to the terminal.
CL Send a carriage return and a line feed to the terminal.
N O S e n d n o r e s p o n s e .
The two EB parameters (EB=eb and cpr) are optional and order-independent. If you omit one,
the system retains its previous value.
| This command is valid only for asynchronous terminals and mode 4 terminals, except for paper
tape devices and 2741 terminals. The end-of-block character for mode 4 terminals is ETX and
I is not changeable. If you specify the char form of the eb parameter, it is only effectiveif it occurs as the last c har acter i n a line.
The CP command enables or disables the cursor-positioning response specified by the cpr
parameter.
J-12 60459680 H
![](asset-2eb.png)
/p^v
(EL) - END-OF-LINE CHARACTER
The EL command defines the logical end-of-line character (carriage return) and defines the
cursor-positioning response to that character. It also defines the message transmission key
for asynchronous terminals not operating in block mode (refer to the IN command).
Format:
ct EL=el, cpr
Parameter
ct
el
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies the new logical end-of-line character. You can specify the
following values for el:
cpr
el Description
Xxx Specifies the 2-digit hexadecimal code xx of the character
you want as the end-of-line delimiter. This character
must differ from the characters currently defined for AB,
BS, Bl, B2, CN, and CT.
EB Selects the current end-of-block character or character
sequence.
E L S e l e c t s t h e d e f a u l t l o g i c a l e n d - o f - l i n e c h a r a c t e r.
Specifies the cursor-positioning response to the EL character. You
can specify the following values for cpr:
cpr Description
CR Send a carriage return to the terminal.
LF Send a line feed to the terminal.
C L Sen d a car ri a ge r et u rn a nd a l i ne fee d t o t he t er m in a l.
N O S e n d n o r e s p o n s e .
The two EL parameters (el and cpr) are optional and order-independent. If you omit one, the
system retains its previous value.
This command does not apply to 2741, HASP, 3270, and bisynchronous 2780 and 3780 terminals;
the cpr parameter does not apply to mode 4 or X.25 PSN terminals; and the char specification
does not apply to mode 4 terminals.
The CP command enables or disables the cursor-positioning response specified by the cpr
parameter.
0^*1.
60459680 G J-13
![](asset-2ec.png)
(EP) - ECHOPLEX MODE
The EP command enables or disables the echoing of input characters back to the terminal.
Format:
ct EP=option
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
option Specifies whether to enable (Y) or disable (N) input echoing.
Some terminals can perform their own character echoing, such as terminals with a HALF/FULL 1
duplex switch. If the switch is in the HALF position, set the EP value to N, and the
terminal echoes the input. If the switch is in the FULL position, set the EP value to Y and
the network echoes the input.
You can use the EP command and full-duplex mode as a security measure. If you are in
full-duplex mode and EP is Y during login, the system echoes all of your input except your
password. This is not true, however, if you enter your user name and password on the same
line.
I This command only applies to asynchronous terminals (except 2741s). ^^
(FA) - FULL ASCII INPUT MODE
The FA command enables or disables the full-ASCII input mode.
Format:
ct FA=option
Parameter Description /^
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
option Specifies whether to enable (Y) or disable (N) the full-ASCII input
mode.
In full-ASCII input, all 128 ASCII characters, including NUL, DEL, STX, LF, and all BLK and
message-forwarding signals (which are normally discarded), are sent to the host. Exceptions
to this are the following characters:
• NULs, DELs and LFs when encountered as the first character of an input line or as
the character following a message-forwarding signal
• CRs that follow LFs when inputting from paper tape
• DC3s that follow the EL character when inputting from paper tape
• DCls and DC3s when output control (0C=Y) is selected
J-l* 60459680 H
![](asset-2ed.png)
In full-ASCII mode, the network does not recognize the terminal functions associated with
the mnenomics Bl, B2, CN, AB, and BS. The network does recognize terminal definition
commands and other commands beginning with the CT character.
If SE is in effect when you select FA or if FA is in effect when you select SE, FA takes
precedence and SE will not be effective until FA is turned off. If full-ASCII mode is
enabled when you select transparent input mode, the network suspends the full-ASCII mode
until the transparent input mode terminates.
This command only applies to asynchronous and mode 4 terminals.
(HC) - HOST CONNECTION
The HC command disconnects you from your current host and establishes a new host
connection. The new host connection can be selected by an HN command or by the HC command
(HC=hostname). The HC command is equivalent to HS or HN followed by TM.
Format:
ct HC=hostname
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
hostname Specifies the name of the host to which you want your terminal
connected.
The host selected is used until you change it or until your terminal is disconnected from
the host.
(HD) - DISPLAY OF HOST NODES
The HD command causes the host availability display (HAD) to be displayed at your terminal.
The HAD lists all paths you can select to connect your terminal to a host.
Format:
ct HD
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
60459680 G j-15
![](asset-2ee.png)
y*E«^5v
The HAD has the following format:
message CONTROL CHARACTER=ct
NPU NODE=npu TERMINAL NAME=terminal
HOST
hOSt;
host'
NODE
node]
node-
SELECTED/
CONNECTED
conditio^
condition2
STATUS
status^
status2
hostn noden conditionn status,
| prompt response
The variable items in the display have the following descriptions.
I
Item
message
ct
npu
terminal
host^
node.}
conditio^
status^
prompt
message
Description
A message describing the status of your current host connection.
Network control character currently defined for your terminal.
The node number of the Network Processing Unit (NPU) your terminal
is connected to.
The name of your terminal.
Represents the 1- to 7-character name of a host. The field may be
blank.
Represents a node number (1-31).
Indicates that you have selected node;} (S), that you are connected
to the host using node.} (C), or that nodejL has been automatically
selected and the connection to the host is in progress (SA).
Represents AVAILABLE or NOT AVAILABLE.
Action to take in response to a host status message.
J-16 60459680 H
![](asset-2ef.png)
(HN) - HOST NODE SELECTION
The HN command sets or changes the host or the path (node) to a host through which your
terminal is connected. This command does not disconnect you from your current host
connection. You must log out or disconnect with the Secure Login command or TM terminal
definition command before you can connect to the new selection.
Format:
ct HN=node
Parameter
ct
node
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies a node number. The default is the node the network
processing unit is presently using to access its supervisor (CS).
The host availability display (HAD) lists all nodes your terminal can use. Refer to the HD
command for a description of the HAD.
(HS) - HOST SELECTION
The HS command selects a host which is connected to your terminal. The host availability
display (HAD) shows the available hosts (refer to the HD command).
Format:
ct HS=hostname
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
hostname Specifies the name of the host to which you want your terminal
connected. The valid entries appear in the HAD.
Your terminal uses the path to host with the least traffic. The path selected is used until
either you change it or until your terminal is disconnected from the host.
60459680 D J-17
![](asset-2f0.png)
/^^Sx
(IC) - FLOW CONTROL FOR INPUT DEVICES
The IC command specifies whether the terminal recognizes DC3s as a stop signal and DCls as a
resume signal for terminal input.
Format:
ct IC=option
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
option Specifies whether to enable (Y) or disable (N) input control.
| Input control applies to asynchronous terminals, including paper tape devices (except 2741s).
(IN) - INPUT DEVICE AND TRANSMISSION MODE
The IN command identifies the input device and the transmission mode of the device. As the
input device, you can specify one of the following:
• A keyboard.
• A p ap er tap e re ade r.
As the input transmission mode, you can specify either:
• Normalized line mode (one message or logical line per terminal transmission block).
• Normalized block mode (one or more logical lines or messages collected into a block
before it is transmitted).
• Transparent mode (input is not edited or translated by the network).
.^«^K
J"18 60459680 H
![](asset-2f1.png)
Format:
ct IN=»in
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
in Specifies the input device and transmission mode. You can specify the
following values for in:
*n Description
BK Selects block mode as from a form terminal and normalized
input mode.
KB Selects a keyboard in character or line mode and
normalized input mode.
PT Selects paper tape and normalized input mode.
X Selects the current input device and transparent input
mode.
XK Selects the keyboard and transparent input mode.
XP Selects paper tape and transparent input mode.
When the IN value is XK, XP, or X, terminal input is sent to the host in transparent mode
blocks. Transparent mode continues until the system encounters a previously defined
transparent mode terminator.
When the IN value is XK and transparent mode terminates, the IN value automatically reverts
to KB. When the IN value is XP and transparent mode terminates, the IN value automatically
reverts to PT. When the IN value is X and transparent mode terminates, the IN value
automatically reverts to the value that was previously in effect.
\ Whe n th e IN v alue is PT or XP, the ne two rk s end s th e X- ON cod e to st art the pape r ta pe
reader automatically after the end of a message is output to the terminal and the message
empties the terminal's output queue.
The IN command is not applicable to HASP, 3270, or bisynchronous 2780 and 3780 terminals.
2741 terminals can only select IN=KB, IN=X, and IN=XK. Mode 4 terminals, which are always
in block mode, and X.25 PSN terminals cannot select PT or XP mode.
r
/ps^s
60459680 H j-19
![](asset-2f2.png)
(Ll) - LINE FEED IDLE COUNT
The LI command specifies the number of idle characters to be inserted into the output stream
following a line feed.
Format:
ct LI=value
Parameter Description
ct Represents the network control character for your terminal as defined by
the CT terminal definition command.
value Specifies the new line feed idle count. This value can be from 0 to 127
or the string CA. A value of CA restores the line feed idle count to
the default value.
The line feed idle count is similar to the carriage return idle count (CI), except that the
idle characters are output after a line feed instead of after the carriage return.
This command only applies to asynchronous terminals.
(LK) - LOCKOUT OF UNSOLICITED MESSAGES
The LK command determines whether unsolicited messages from the network operator appear at
your terminal.
Format:
ct LK=option
Parameter Description
ct Represents the network control character for your terminal as defined by
the CT terminal definition command.
option Specifies whether to lock out unsolicited messages. A value of Y locks
out the messages and a value of N allows the messages to appear.
/tfa^v
J_2° 60459680 H
![](asset-2f3.png)
(MS) - MESSAGE TO NETWORK OPERATOR
The MS command sends a message to the network operator.
Format:
ct MS=message
Parameter
ct
message
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies your message to the operator. You can use any string of 50
characters or less.
If you are having problems with the network (such as difficulty connecting to IAF), you
communicate these problems to the network operator using the MS command.
(OC) - FLOW CONTROL FOR OUTPUT DEVICES
The OC command specifies whether the terminal generates DC3s as a stop signal to the network
and DCls as a resume signal for terminal output.
Format:
ct 0C=option
Parameter
ct
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
option Specifies whether to enable (Y) or disable (N) output control.
If the network receives a DC3 while output control is enabled, it suspends output until it
receives a DC1.
Output control applies to asynchronous terminals, including paper tape devices (except
2741s).
(OP) - OUTPUT DEVICE SELECTION
The OP command specifies the type of output device.
Format:
ct 0P=op
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
60459680 H J-21
![](asset-2f4.png)
Parameter Description
op Specifies the output device. You can specify the following values for
op:
op Description
DI Specifies a display device.
PR Specifies a printer.
PT Specifies a paper tape punch.
You can punch a tape in any mode, but the network does not provide the proper X-OFF
characters unless OP has a value of PT.
If you select OP=PR, the network does line folding and page bounding for asynchronous and
X.25 PSN terminals. If OP=DI, the network assumes the terminal performs these functions
itself.
This command only applies to asynchronous terminals (except 2741s). OP=PT does not apply to
X.25 PSN terminals.
(PA) - PARITY PROCESSING
The PA command specifies the parity processing to be performed by the network.
Format:
ct PA=pa
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
p a S p e c i fi e s t h e t y p e o f p a r i t y p r o c e s s i n g . Yo u c a n s p e c i f y t h e
following values for pa:
pa Description
E Set parity bit for even parity during output, and check
for even parity (except for X.25 PSN terminals) and set
pari ty bit to zero o n in put .
N In transparent mode, do not set or check the parity bit
because it is part of the input or output data. In
normalized mode, set the parity bit to zero on input and
output.
0 Set parity bit for odd parity during output, and check for
odd parity (except for X.25 PSN terminals) and set parity
bit to zero on input.
J-22 60459680 H
![](asset-2f5.png)
Parameter Description
Pa Description
ZSet parity bit to zero on output and check parity bit
against zero on input.
I In transparent mode, do not set or check the parity bit
because it is part of the input or output data. Ignore
the parity bit when checking for transparent input mode
delimiters. In normalized mode, set the parity bit to
zero on input and output.
This command only applies to asynchronous terminals (except 2741s). For X.25 PSN terminals,
the parity bit is set to 0 and not checked for input.
(PG) - PAGE WAITING
The PG command enables or disables page waiting at the terminal during output. If you
enable page waiting, the terminal stops at the end of each output page for your
acknowledgement (a null input line) before output continues. (In order for the PG command
to be effective, page length (PL) must be non-zero.)
Format:
ct PG=option
Parameter Description
ct Represents the network control character for your terminal as defined
by the CT terminal definition command.
option Specifies whether to enable (Y) or disable (N) page waiting.
When you enter a null input line to get the next page of output, the null input line has no
other meaning.
Page waiting does not apply to bisynchronous 2780 or 3780 terminals or to HASP terminals.
(PL) - PAGE LENGTH
The PL command establishes the maximum number of physical lines that can be printed as one
page. If the output device type is PR, the network automatically positions the carriage to
the top of the form after PL lines have been output.
Format:
ct PL=pl
Parameter Description
c t R e p r e s e n t s t h e n e t w o r k c o n t r o l c h a r a c t e r f o r y o u r t e r m i n a l a s d e fi n e d
by the CT terminal definition command.
pl Specifies the page length. You can specify 0 or any value from 8 to
255. PL=0 selects an infinitely long page.
The PL value must be nonzero if you want to enable page waiting, since page waiting only
occurs after the number of lines defined by pl-1 are output.
60459680 H j-23
![](asset-2f6.png)
(PW) - PAGE WIDTH
The PW command establishes the maximum number of characters that the terminal prints on one
■ output line. If the output device type is PR, the system automatically starts a new line
after pw characters have been output.
Format:
ct PW=pw
Parameter
ct
pw
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Specifies the page width. You can specify a value of 0 or any value
from 20 to 255. PW=0 selects an infinitely long line.
(RC) - RESET TERMINAL CHARACTERISTICS
The RC command resets your terminal to the NDL-specifled default values. Normally you would
use this command after disconnecting from a host connection for which you had altered one or
more terminal characteristics.
Format:
ct RC
Note that a terminal can also be automatically reconfigured each time the terminal is
disconnected from a host if the terminal is on a line for which automatic reconfiguration
has been specified by the network administrator.
(SE) - SPECIAL EDITING MODE
The SE command enables or disables the special editing variant of normalized input mode.
Format:
ct SE=option
Parameter
ct
option
Description
Represents the network control character for your terminal as defined
by the CT terminal definition command.
Enables (Y) or disables (N) special editing operations.
When special editing Is in effect, any backspace character entered is stored for transmission
to the host. Similarly, a line feed entry produces a normal line feed operation at the
terminal and the network stores the line feed character code for transmission to the host.
A backspace followed by a line feed causes the system to output a bell and to position the
cursor below the last character entered.
This command is only valid for asynchronous terminals but not for X.25 PSN terminals.
J-24 60459680 H
![](asset-2f7.png)
(TC) - TERMINAL CLASS COMMAND
The TC command specifies a terminal class for your terminal. The terminal class associates
your terminal with a predefined set of terminal characteristics. To effectively use a
terminal class, choose a terminal class whose default terminal definition corresponds to the
characteristics of your terminal.
Format:
ct TC=tc
Parameter Description
c t R e p r e s e n t s t h e n e t w o r k c o n t r o l c h a r a c t e r f o r y o u r t e r m i n a l a s d e fi n e d
by the CT terminal definition command.
t c S p e c i fi e s t h e t e r m i n a l c l a s s . T h e v a l u e t c c a n b e f r o m 1 t o 1 8 .
The following list associates terminal class values with terminal types:
tc Terminal Type
1 M33, M35, M37, M38 teletypes
2 CDC 713-10, 722, 751-1, 752, 756
3 CDC 721, 722-30
4 I B M 2 7 4 1
5 M40 teletypes
6 Hazeltine 2000
7 Terminals conforming to the
ANSI X3.64 standard (DEC VT100,
TeleVideo 924, 950, 955)
8 Tektronix 4010, 4014
9 HASP protocol, postprint
format control
tc Terminal Type
10 200 User Terminal
11 CDC 714-30
12 CDC 711-10
13 CDC 714-10/20
14 HASP protocol, preprint format
control
15 CDC 734, 731-12
16 IBM 2780
17 IBM 3780
18 IBM 3270
A terminal that is not shown as belonging to a terminal class may still be operational. The
terminal can be assigned to a terminal class having similar characteristics and the
terminal's definition can be modified as necessary to correctly define the operational
characteristics of the terminal.
If your terminal is on an auto-recognition line and its terminal class is other than 4, 10,
13, or 18, you can use the TC command to change its terminal class to ensure proper
operation.
If you include a TC command in a sequence of terminal definition commands, enter the TC
command first as it resets all other terminal characteristics.
/j$pfe\
60459680 H J-25
![](asset-2f8.png)
(TM) - TERMINATING A TERMINAL-HOST CONNECTION
I The TM command terminates the connection between your terminal and a host.
Format:
ct TM
Parameter Description
ct Represents the network control character for your terminal as defined by
the CT command.
You can use the TM command if your application does not respond to your input. The system
responds to the TM command in the following manner:
I HOST DISCONNECTED CONTROL CHARACTER=ct
ENTER INPUT TO CONNECT TO HOST
J-26 60459680 H
![](asset-2f9.png)
(XL) - MULTIMESSAGE TRANSPARENT MODE
The network provides a transparent mode that allows you to remain in transparent input mode
even after message blocks have been forwarded to the application. The XL command specifies
the multimessage-forwarding signal and the terminator for transparent input mode. If your
terminal's parity is set to even, odd, or zero (PA=E, 0 or Z), the parity bit is stripped
(set to zero) before the characters are sent to the host, although no translation occurs.
If your terminal's parity is set to none or ignore (PA=N or I), the parity bit is not
stripped. See the NAM/CCP Terminal Interfaces Reference manual for more information on
transparent input and parity.
Format:
ct XL=Xxx,Ccount,TO,Yyy
Parameter Description
ct Represents the network control character for your terminal as defined by
the CT terminal definition command.
Xxx Selects the character with the two-digit hexadecimal representation xx
as the message-forwarding signal. If you do not specify a value yy, the
occurrence of two successive characters defined by xx acts as a
terminator for transparent input mode. When you specify a hexadecimal
code above 7F, you must have previously set your terminal's parity to
none (PA=N) or ignore (PA=I); otherwise the network cannot detect the
code when it occurs in a transparent mode message.
Ccount Selects a decimal value from 1 to 4095 as a character count that
functions as a message-forwarding signal. These values (1 to 4095) are
valid with the network. However, unless changed during installation,
the maximum logical input line length in IAF (2500 characters) limits
you.
TO Selects timeout as a transparent input mode terminator.
Yyy Selects the character with the two-digit hexadecimal representation yy
as a terminator for transparent input mode when it follows xx. When you
specify a hexadecimal code above 7F, you must have previously set your
terminal's parity to none (PA=N) or ignore (PA=I); otherwise the network
cannot detect the code when it occurs in a transparent mode message.
Yyy, if specified, must follow the Xxx parameter; otherwise, it is ignored. The parameters
are otherwise order-independent. You must specify at least one of Xxx or TO to select a
transparent mode terminator. When it immediately follows the character defined by Xxx on
input, the character defined by yy terminates transparent input mode. The characters
defined by Xxx and Yyy can be identical or you can omit Yyy. In either case, two successive
input characters defined by Xxx are required to terminate transparent mode.
The message-forwarding signals and mode terminators are not sent to the host.
The XL command applies only to asynchronous and mode 4 terminals. Terminal class 4 is
configured with the RETURN key as the only transparent mode delimiter and terminator, and
mode 4 terminals are configured with the SEND or ETX key as their only transparent mode
delimiter and terminator. For devices connected through X.25, the PAD forwarding signal
always acts as a transparent mode delimiter in addition to any other options selected.
This command does not apply to HASP and bisynchronous terminals.
60459680 H J-27
![](asset-2fa.png)
Table J-l. Default Terminal Definitions
Mne
monic Description
Terminal Types
TTY
M33
CDC
713-10,
722,751-1,
752,756
CDC
721,
722-30
IBM
2741
TTY
M40-2
HAZ
2000
X3.64
DEC
VT100
Te k
4000
X.25
any
HASP
POST
CDC
200
UT
CDC
714-30
CDC
711-10
CDC
714-10,
714-20
HASP
PRE
CDC
734
IBM
2780
IBM
3780
IBM
3270
TC Terminal class (0) 10 11 12 13 14 15 16 17 18
AB Abort output block CAN CAN CAN CAN CAN CAN CAN na na na na na na na na na na na
BF Blocking factor (1) na na na na
BS Backspace character BS BS BS BS none BS BS BS (1) na na na na na na na na na na
Bl User break 1 DLE DLE DLE DLE DLE DLE DLE (I) na na : ( 6 )
B2 User break 2 DC4 DC4 DC4 DC4 DC4 DC4 DC4 (1) na na )(7)
BR Break as user break 1
(and cancel character)
na (1) na na na na na na na na na na
CI Carriage return idles (1) na na na na na na na na na na
CN Cancel character CAN CAN CAN CAN CAN CAN CAN (1) na na
CP Cursor positioning na na na na na na na na na na na
CT Network control
character
ESC ESC ESC ESC ESC ESC (1)
DL Single-message trans
parent input mode
Character delimiter CR CR CR NL CR CR CR CR (0 na (4) (4) (4) (4) na (4) na na na
Character count
delimiter
2043 2043 2043 na 2043 2043 2043 2043 (O na na na na na na na na na na
Timeout delimiter No No No na No No No No (1) na na na na na na na na na na
EB End-of-block
Character EOT EOT EOT na EOT EOT EOT EOT (2) na (4) (4) (4) (4) na (4) na na na
Cursor positioning CL CL CL na CL CL CL CL No na No No No No na No na na na
EL End-of-logical line
Character CR CR CR NL CR CR CR CR (1) na (5) (5) (5) (5) na (5) na na na
Cursor positioning LF LF LF na LF LF LF LF No na No No No No na No na na na
EP Echoplex mode na na na na na na na na na na na na
FA Full ASCII input mode na na na na na
IC Input device flow
c o n t r o l
na na na na na na na na na na na na
IN Input device KB KB KB KB KB KB KB KB BK na BK BK BK BK na BK na na KB
LI Line feed idles (1) na na na na na na na na na na
LK Lockout NOP messages (1) No No No No No No No na na
OC O u t p u t de v i c e flo w
control na na na na na na na na na na na na
OP Output device PR DI DI PR DI DI DI DI (1) na na na na na na na na na na
PA Parity processing na (3) na na na na na na na na na na
PC Page waiting (1) na na na na
PL Page length 24 30 24 27 24 35 (1) 13 16 16 lb 13 24
PW Page width 72 80 80 132 80 74 80 74 (1) 80 80 80 80 80 80 80 80 120 80
SE Special editing mode na na na na na na na na na na na
XL Multimessage
transparent input mode No No No No No No No No No na No No No No na No na na na
(0) Terminals belong to terminal classes 1 through 3
(1) Same as for the terminal if it were not connected
(2) End-of-packet sequence (M bit is reset to zero).
(3) The parity bit is ignored on input and is gencrat
(4) ETX (resulting from the SEND key).
(5) ESC A (resulting from the CARRIAGE RETURN key).
(6) Program attention key 1 is a valid user break 1.
(7) Program attention key 2 is a valid user break 2.
or 5
via
ed f o
through
3 packe
r ou t p u
8.
-swlt
a s f
ching r
o r t h e
letwor
basic termlilal type.
J-28 60459680 H
![](asset-2fb.png)
<4H
O
9)
Qi
rC
tn
o
Ti
0)
o
<d
G
■a
M
0)
H
K
O
M-l
CO
9)
60
I
H
0)
ta
9)
s
(0
M
Ri
04
I
O Ci
S3 r*
a s 3.3 3 C S C
S S S 3 S
3 3 3 SSC
C C S S C
CCS
2 8 A 3 C C 3 C
4 3 C C 3 S C
2 S A 3 C S C
u
gNN
A S C C
3 3 3 C C 3 3 C
C M t M < M
^ C M y .
C A C
_ z o.
«■% Z • CT>
c c c > ; c A 3 ^ >^ C
- - . C M ^ ~ / - > y »
C A c c c
. z o >
; - o >
r£ A 3 -■> Z .->
C > t C
* - . C J « - « y - N ^
cAccc>;ca5c
z o > / - . Z . - .
, - > C M ^ > . y ^ , - .
C A C C C
_ z o >
Z - e r ,
>:c AS ~ Z « - s
C f c
•^ CM *-N o > « - >
CACCCS3A3C
«-. CM «■> .-. /-^
C A C C C
. z o t
■ - o >
:£ A3 r ~ i Z ^
^ >T c
C A C C C
- v , - > Z •
C C f t o «■% z ^-»
A3 c >: c
C A C C C
- - > ^ z - o n » - * Z ^
A3 C *- C
S 3
3 S
A 1, — J r n r t
w U U v . . — J I O c- l
A J, - I J » t n -Jo <-l
A J. _ _ J o o n
w C d U ^ —i _) cq cn
~ « J a c n -«Jo cn
A 3 w I d U w - J m « n
•^ sa u —.
s - u u • _ - w U U w
w C J W w v U H w
J < W r t
u n t a
« v S
p C Q w
§ 2
3 3 St
t »
CO c o
c a - a
•H kl S
M M 8
a 3 B G
s s
0 ) J - >
8-3
S£ «l
u
a A <u
3Cl tl
3 t J
AJ • J X
a m
C S3
r-> ,4
a
"fi Sc R °
W 0 CJ
»a
C VM tl
J 2 cd to
u
3 2
t o
C > >J 01 M
c / i <£3 CO CQ a.
o — CM Pl *» tftiON
60459680 G J-29
![](asset-2fc.png)
M-t
0)
a
C4
Xt
cd
H
3§
m c n SM
A i n
O C M
CM LO
• I O
O C M
ca
a
00 eg
a
o
5S
m c n
CM
O
f.
oA
BS
H C M .
CM IO
3 3 3 S 3 3 3 a3ao• i O
O C M
tO ct
cs
a c n
c j t > .
CO U"> C M IO
IO
3SH SM* ▶T«in
O C M
-LO
O C M
<t
oCS
B
o a
C O U
Si..,
£3 CM IO
9a3 S 3 !M
-IO
O C M -» • O
r H k l
z °O ©
O - 4 C M
S 1 1 c o m C M IO
rn
1
O - » - c f
>i BM s- O C M
-IO
O C M
cn
oO t t l
4J
r ^ C - .
S 5 S S
omo a
C J - 1
e o i o C M IO
k i t i
£ e o
3»« 9- >? O C M
• I O
O C M
cn
o
ki
r*. O - r f
« - a
• H C 3
e o e g
O
cn
cn
cU
S 3 - i
C O t o CM LO »<
3SM Sm" >^ • I O
O C M
• I O
O C M ~1 ■a k i
3
r-
CM IO
LO
ONS
c a i o
3>< SM s-
»io
O C M
« I O
O C M
cn
o
k l o
tl
k i - a
eu h a t i
e g k t
a
ti 33
CB Cu
CM IO
•LO
O C M Ot e g a
■£ e o
o 4 7
m o a
a
c
1/1 _
C M > » ,^ „, »-MO CM CO
■h - r f
kl
li 8 CM CM CM « M
0 - o
tO CM CM CM IO
— L O jj CM t i > %
X I k l
E-IO • e k i
£*8 CTN o z C O I O CM
It
CM CO
Cu
Cu
Ot
oC k o
• 3 " *
3° !H
•cr A3 sm" SM NW P^ O C M
- 1
- t m t i • •
m M M
a k i k i
-IO
2uS OZ C O I O C M IO
cn
CM CO fc Ol
o
■»a s s
t i k i u
S°£ iH j r f "
■er A3 sm" SM NM >i
• I O
O C M
"IO
O C M tr
• I
- . I O C k t l t l
O . B B
e o e o
•I LO
o
C M O
ot o z CO LO CM LO
cn
CM CO Cu fc Ot
o
•* k . C B
° 2 S
s ° Srf »i S" •» A3 Sm" SM
iri
NW 6- O C M
• t o
O C M >-" — I O
t i u u
C O k l k l
e g - H - r f
• u 3 3
to 0 0 k l o C O
CM
CM LO
cn Ot
o u o
z z z ^Ot ^^ OZ C O I O CM CO
Cu
CU fc
*8*" s* sf A3 SM* 8m"
>n
N C d >< • I O
O C M
-LO
O C M >i
- 1
T I O
X c & S .
_, Ot
k i e g .
e g e g * o *
W C M
Ot C O I O C M IO I O k l C l
38>^
CQ
* X A3 Sm"
O S M
t k a >^ O C M
-IO
O C M >? •» CM CM
C k > > ▶. a
U t l J O J l 3
o u
K t ] t j t l
Atn Ot c n t i a t t i u o
o **? Ot Cu fe u w
a S JL Ot o z C O I O CM LO CM CO Cu •» J S k l o O k l
R C M C M
u r » c m >r Srf" sh >» A3 Sm" SM N C d >h"
-IO
O C M C5 CM SH
- I
—1 IO 9 U 8 S 3
O E C B
k i k i o o e g
x ! t l c j c j c j
k i k i
- 1 t O IO U k l k l / - .
o - * m
HITIN Ot
cn fc fc Ot
o" 2 8 8 3
U IN ■Ot o z CO LO CM IO CM CO •» c j i : o « 5a c n - c m «» A3 -LO -IO - 1
C J - * C M " O S" Srf* ix SM !m N C d !n O C M O C M >. — I O t n c j k i f c u
NNN I S 1 t l C J t l
r» e g C O 3 9 T D
• H c m e g
to O - i k l k l K
• r f - r f u
A
CM IO
<n Ot
6S Ol
o t - . ^, OZ e o l o CM CO fc fc •» H H J S
C j I H I M I H
5 C J - r f - r f C O
■r f C O • Z ,
f c e g a t l
8 % 5 » : 5 - 8
f>^ Srf
sr A3 Sm BM NW >^ -IO
O C M
• I O
O C M t*
• I
— , I O
ki
tl
■8
B"8 kl
ki
Ti
kl
a
atw
O
c3 o eo C k l B kl ki u g t i • t i f c
o3
o
eg tl (kl I 3 ■rf aO k l b £ W t l
e p f c fi k i
B I M 0 1 • C l C J4J Ck LM tl eo (0 a t i
CL, tl tl 01 to ■rl « T i - o o • A 3 . r a a i
H l < « u Z X k l f c•H ■8Ti tl cj •a CJ tl eo a t i
fc •C •r4 r i 0 0 k l k l •o u u C J c j c j q
i u 5 k > » • f c i s
OaM■rf ti •h •8 ° s a e g t l t l
art t> 5» •o tl tl kl «i kl a u ii k l W c j A O i J M H o a
o eg cQikicjcQCuikt
2Kaotl ti •a •a Ck •rf ■ot H « u o a ri
tl • O - H tt ti ki tl m t l
2 a
• r f n
fi *
n a
i . k i 25 r H f c e n
rt LM k l o >, ti e g q f c o » . « • c e c Q
Enliilessi^
Ck
.8 —i
k l k l
i. a
ti
tl
ccj
2 »
Ck kl
k l c
14
tl
eo eo
IO
t l t o
00 CM
a c d
3 B
CJ irf £ t i
c j - a
Cd s. s o
n o •rf ss s, 8, 10
Pu CO
u
C J ( 3 <->*t r-N»«-t^>^^
c o
z a Cm
cd
CJ
r. ▶Ht. ft, CO £ $ O - » C M C O - » I O M > 1 —
J-30 60459680 G
![](asset-2fd.png)
/fPffey
DELIMITING AND TRANSMITTING TERMINAL INPUT K
You can transmit input to an application in normalized mode (also called character mode) or
transparent mode (also called binary mode). Appendix J describes how you delimit and
transmit input in transparent mode (refer to the DL and XL commands), however the default
input mode for all supported terminal classes is normalized mode. The remainder of this
appendix describes how to delimit and transmit terminal input in normalized mode under the
default conditions of the various terminal classes. (Appendix J also describes how you can
change these defaults).
PHYSICAL END-OF-LINE (LINE FEED)
In terminal classes 1 through 8, you can terminate a physical line of input (block) with a
line feed key. The network also terminates a physical line of output whenever the page
width of a terminal is reached and OP=PR (refer to the PW and OP command in appendix J).
The network may respond to the line feed key by advancing the cursor or carriage to the
beginning of the next line (refer to the CP command in appendix J).
LOGICAL END-OF-LINE (CARRIAGE RETURN)
You terminate a logical line of input with a carriage return key. A logical line can
consist of one or more physical lines but not vice versa. The carriage return key advances
the cursor or carriage to the beginning of the next line.
MESSAGE TRANSMISSION
You transmit your input to the network with the message transmission key. For terminal
classes 1 through 8 operating in character or line mode (IN°KB), the message transmission
key is the carriage return key. Hence, for these terminal classes, logical lines are
transmitted separately. When the delimiter for the logical end-of-line and the transmission
key are different (as with block mode devices, including PSN and mode 4 terminals), the
terminal stores logical lines until you press the transmission key. The terminal then sends
the single transmission consisting of multiple logical lines to the network. The network in
turn sends each logical line to the application separately. The message transmission key
always acts as a carriage return if not immediately preceded by one.
Table K-l shows the keys used by the various terminal classes to perform the three functions
just described.
60459680 C K_!
![](asset-2fe.png)
.■^^V
Table K-l. Default Message Delimiters and Transmission Keys
Function
Terminal Class Physical End-of-
line (line feed) Logical End-of-line
(carriage return)
Message
Transmission Keyt
1LINE FEED
\1
RETURN RETURN
2RETURN RETURN
31NEXT NEXT
4ATTN RETURN RETURN
5NEW LINE RETURN RETURN
6LF CR CR
7LINE FEED RETURN RETURN
8LF RETURN RETURN
9Variestt Variestt Variestt
10 None RETURN SEND
11 None RETURN SEND
12 None NEW LINE ETX
13 None NEW LINE ETX
14 Variestt Variestt Variestt
15 None NEW LINE SEND
16 None EM EOT
17 None EM EOT
18 None Enter Enter
tlf in block mode, refer to terminal documentation for tei
Those listed are for character and line modes. ■minal key equivalences.
ttTerminals operating under HASP protocol use different keyrs for this purpose.
....
/KSSSjV
K-2 60459680 D
![](asset-2ff.png)
/ f ^ v
PASSIVE PROCEDURsES
Passive procedures are procedures that do not have the parameter-prompt ing capability. If
the procedure call contains errors, the job step terminates and the procedure is not
executed. In most respects, however, the structure and behavior of passive and
parameter-prompt ing procedures are highly similar. This appendix shows only the areas in
which passive procedures differ from the parameter-prompting varieties. Section 4 contains
a detailed description of parameter-prompting procedures.
.PROC DIRECTIVE
This format of the .PROC directive does not provide for parameter prompting nor will the
system give parameter descriptions or other help.
Format:
PROC,pname,p1,p2,...,pn.
Parameters Detseription
pname Name of the procedure; one to seven alphanumeric characters. As with
file names, the name of a procedure should begin with a letter.
Pi Optional formal parameters whose keywords are used in the b?dy of the
procedure. Depending on the parameters specified in the procedure call,
keywords in the procedure body can be removed, left as they are,
replaced by a value specified in the procedure call, or replaced by
first or second default values as specified on the procedure header
parameter (refer to keyword substitution in this secticn).
The maxjtaua number of procedure header keywords is defined by the
installation. The default is 50.
The following are the acceptable formats for pj.
Format
keyword
keyword^
key wo r d=de fa ul 11
keyword=defaultl/default2
keyword=/de fa ul t2
keyword»#DATA (CDC graphics: keyword=
keyword=#FILE (CDC graphics: keyword^
Example
FILE1
FILE1=
FILEl-LGO
FILE1=LG0/0LD
FILE WOLD
5 DATA) FILE1=#DATA
= FILE) FILE1=#FILE
keyword A 1- to 10-character keyword.
60459680 C L-l
![](asset-300.png)
/<«$k
Parameters Description
defaultl A 1- to 40-character first default value. If
defaultl contains special characters, it must be
$-delimited. This default value replaces the
keyword in the procedure body if this parameter is
omitted from the procedure call.
default2 A 1- to 40-character second default value. If
default2 contains special characters, it must be
$-delimited. This default value replaces the
keyword if the procedure call specifies a parameter
value identical to the keyword.
defaultl and default2 could be either of the following special values.
#FILE Special default value used for keyword if an
overriding value is not specified on the procedure
call. If this default value is used, keyword within
the procedure body references the record that
immediately follows the procedure record on the file.
If the procedure resides on a library and is called
by a name call form of the BEGIN command, keyword is
replaced by a null value.
//DATA Special default value used for keyword if an
overriding value is not specified on the procedure
call. If this default value is used, keyword within
the procedure body references a data file created
within the procedure by the .DATA directive (refer
to .DATA directive in section 4).
PROCEDURE AND PARAMETER DESCRIPTIONS
You cannot include the .HELP or .ENDHELP directive in your procedure body. Hence, you
cannot provide the procedure caller with a description of the procedure or any of its
parameters unless the caller has already entered an error-free procedure call.
PARAMETER MATCHING
When a procedure is called, the system must match each parameter on the call command to a
parameter on the procedure header command. The system uses two methods of parameter
matching; order-dependent and order-independent.
ORDER-DEPENDENT PARAMETER MATCHING MODE
Parameter matching always begins in order-dependent mode (refer to Order-Independent
Parameter Matching Mode for information on changing parameter matching modes). The system
compares, in order, each parameter on the BEGIN command with the parameter in that position
on the procedure header directive. The system then substitutes the selected parameters into
the procedure body.
All possible parameter substitutions in order-dependent mode are summarized in table L-l. ySE!?s\
The table shows each parameter format on the BEGIN command, each parameter format on the
procedure header, and the substitution resulting from each combination. In the table the
L-2 60459680 C
![](asset-301.png)
jgspP^N
word value indicates that the parameter in the BEGIN command (called value) is different
than the corresponding keyword and/or defaults on the procedure header. Keyword in the
BEGIN Command Parameter Format heading means the keyword in the BEGIN command is identical
to the keyword in the procedure header parameter.
Assuming that all parameter matches between the BEGIN command and the procedure header are
valid for order-dependent mode (table L-l), the system completes parameter matching in
order-dependent mode.
In order-dependent mode, the system ignores excess parameters on the BEGIN command.
Use table L-l with the following examples to clarify the meaning of the table entries
(keyword, defaultl, default.2, value, and null).
Examples: Parameter Matching in Order-Dependent Mode.
Procedure on File
Named MYFILE
.PR0C,SAMPL1,L,M,N=XY.
REWIND, L,A,M,N.
Call and Substitution
BEGIN,SAMPL1,MYFILE.
y i e l d s
REWIND,L,A,M,XY.
BEGIN,SAMPL1,MYFILE,„N.
y i e l d s
REWIND,L,A,M,N.
Explanation
When parameters are omitted on
the BEGIN command, the system
uses the defaults from the
procedure header (L, M, and XY).
Omitted parameters indicate use
of the procedure header defaults
(L and M). N overrides the pro
cedure header default (XY).
BE GIN,SAMPL1,MYFILE,$*$,C.
yields
REWIND,*,A,C,XY.
.PR0C,SAMPL2,LFN1=,LFN2, BEGIN,SAMPL2,MYFILE.
SBF=/SBF. yields
COPY SBF,LFN1,LFN2. C0PY„LFN2.
Special characters must be
$-delimited. The asterisk (*)
replaces M. The system uses the
procedure header default (XY)
for the omitted parameter.
Omitted parameters indicate use
of procedure header defaults
(LFN2 and null substitution for
LFNI and SBF).
BEGIN,SAMPL2,MYFILE,„SBF.
y i e l d s
COPYSBF,, LFN2.
Omitted parameters indicate use
of procedure header defaults
(null and LFN2). The BEGIN
command parameter, SBF, indi
cates use of the second default
of the SBF procedure header
parameter (SBF). The linking
character ( ) connects COPY
and SBF to make COPYSBF.
.PROC,SAMPL3,PFN,
P1=/$M=W$.
ATTACH,PFN/P1.
BEGIN,SAMPL2,MYFILE,F0RMS,0UTPUT.
yields
COPY,FORMS,OUTPUT.
BEGIN,SAMPL3,MYFILE,TAXES,P1.
y i e l d s
ATTACH,TAXES/M=W.
FORMS replaces LFNI and OUTPUT
replaces LFN2. Since the third
parameter is omitted, the system
uses the procedure header de
fault (null).
TAXES replaces PFN and the char
acter string M=W replaces Pl.
60459680 C L-3
![](asset-302.png)
Table L-l. Parameter Substitution In Order-Dependent Mode
BEGIN Command Parameter Format
omitted keyword value $value$
Procedure
Header
Parameter
Format
keyword
keyword^
keyword=defaultl
keyword=defaultl/default2f
keyword
null
defaultl
defaultl
keyword
keyword
keyword
default2
value
value
value
error
value
value
value
error
^ Switches keyword substitution to order-independent mode for all subsequent parameters.
Example 1:
The following procedure is on file PROCFIL. It prepares a file for processing. If the file
is local, it is rewound. If it is not local, the system searches for the file in your
permanent file catalog. If the file is not found, the procedure reverts and aborts.
.PROC,PREPARE,FNAME=,M=R.
IF, FILE (FNAME,AS),PREP1.
REWIND, FNAME.
REVERT. FNAME PREPARED.
ENDIF,PREP1.
ATTACH, FNAME/#M=M,NA.
IF,FILE(FNAME,.N0T.AS),PREP2.
GET,FNAME/NA.
IF, FILE (FNAME,. NOT. AS ),PREP3.
REVERT,ABORT. FNAME NOT FOUND.
ENDIF,PREP3.
ENDIF, PREP 2.
REVERT. FNAME PREPARED.
EXIT.
REVERT,ABORT. PREPARE ERRORS.
Prepare file TEST with the following command.
BEGIN,PREPARE„TEST.
L-4 60459680 C
![](asset-303.png)
Since PROCFIL is the default file, it does not have to be specified and is noted by
successive commas.
The following is a segment of the dayfile that results when the BEGIN command is processed
08.26.45. $BEGIN,PREPARE„TEST.
08.26.46.IF,FILE(TEST,AS),PREP1.
08.26.46. ENDIF,PREP1.
08.26.46.ATTACH,TEST/M=R,NA.
08.26.46. TEST IS INDIRECT ACCESS, AT 000121
08.26.46.IF,FILE(TEST,.NOT.AS),PREP2.
08.26.46.GET,TEST/NA.
08.26.47.IF,FILE (TEST,.NOT.AS),PREP3.
08.26.47. ENDIF,PREP3.
08.26.47.ENDIF,PREP2.
08.26.47.REVERT. TEST PREPARED.
Example 2: Parameter Matching in Nested Procedures (Order-Dependent Parameter Matching Mode)
The substitutions made in a procedure that calls a second procedure are shown in figure
L-l. The resultant dayfile is shown on the right side of the figure.
GET,PROGRAM1.
BEGIN,EXECUTE,PFILE1,PR0GRAM1,PRINT.
PFILE1
.PR0C,EXECUTE,NAME,0UT.
FTN5,I=NAME,L=0UT.
LGO.
IF,EF=0,DR0P.
BEGIN,LISTING,PFILE2,0UT.
ENDIF, DROP.
PFILE2
.PROC,LISTING,OUTFILE=0UT.
REWIND,0UTFILE.
C 0PY SB F, OUT F ILE , OUT PUT.
RES
16.
16.
16.
16.
16.
16.
16.
16.
16.
16.
16.
16.
16.
16.
16.
ULTANT
01.08.
01.08.
01.09.
01.10.
01.10.
01.11.
01.11.
01.12.
01.12.
01.12.
01.13.
01.13.
01.13.
01.13.
01.13.
DAYFILE
GET,PR0GRM1.
BEGIN,EXECUTE,PFILE1,PR0GRM1,PRINT.
FTN5,I=PR0GRM1,L=PRINT.
.043 CP SECONDS COMPILATION TIME
LGO.
STOP
.038 CP SECONDS EXECUTION TIME
IF,EF=0,DR0P.
BEGIN,LISTING,PFILE2,PRINT.
REWIND,PR INT.
COPYSBF,PRINT,OUTPUT.
END OF INFORMATION ENCOUNTERED.
$REVERT.CCL
ENDIF,DROP.
$REVERT.CCL
Figure L-l. Keyword Substitution in Two Procedures
60459680 C L-5
![](asset-304.png)
»^^^v
ORDER-INDEPENDENT PARAMETER MATCHING MODE
The system switches to order-indpendent mode to match the remainder of the parameters if in
comparison of a BEGIN command parameter and a procedure header parameter one of the
following occurs.
• A BEGIN command parameter is in the format keyword" or keyword=value.
• A procedure header command parameter is in the format keyword=default/default2.
For each BEGIN command parameter, matching always begins in order-dependent mode. Once in
order-independent mode, the system matches each keyword of the BEGIN command to the
identical keyword in the procedure header command, regardless of order.
The following commands illustrate the parameter combinations that result in switching from
order-dependent mode to order-independent mode.
Procedure on Default
File PROCFIL
.PROC, SALES,TAX,TOTAL=,
FLAG=A.
COPYL, TAX,TOTAL, HOLD,, FLAG.
REPLACE,H0LD=TAX.
Call and Substitution
BEGIN,SALES„TAX,TOTAL=SUM,FLAG.
y i e l d s
COPYL,TAX,SUM,HOLD„A.
REPLACE,HOLD=TAX.
,PROC,TAXES,TAX=FED/MN, BEGIN,TAXES„TAX,DEDUCT.
DEDUCT,FLAG=A. yields
COPYL,TAX,DEDUCT,HOLD„FLAG. COPYL,MN,DEDUCT,HOLD„A.
REPLACE,H0LD=TAX. REPLACE,H0LD=MN.
Explanation
Parameter matching starts in
order-dependent mode. The
BEGIN parameter TOTAL=SUM
switches the mode to order-
independent mode. FLAG is
then matched in order-
independent mode, which
yields A.
The TAX=FED/MN procedure
parameter switches the mode
to order-independent mode.
All parameters will be
matched in order-independent
mode.
All possible parameter substitutions in order-independent mode are summarized in table L-2.
The table shows each parameter format on the BEGIN command, each parameter format on the
procedure header command, and the substitution resulting from each combination.
In the table the word value indicates that the parameter in the BEGIN command (called value)
is different than the keyword and/or defaults on the procedure header command. Use table
L-2 with the following examples to clarify the meaning of the table entries (keyword,
defaultl, default2, value, and null).
''*"^\
L-6 60459680 C
![](asset-305.png)
Examples of Parameter Matching:
Call and Substitution
Procedure on Default
File PROCFIL
.PROC,SAMPL1,L,M,N=XY.
REWIND,L,A,M,N.
r
.PROC,TRACE,IN,OUT,
TC=E0I,N=1.
COPY,IN,OUT,„TC,N.
.PR0C,SAMPL4,FILE1,
EC=B6/A6,DC=LP,REP=0.
REWIND,FILE1.
ROUTE,FILE1,#DC=DC,
#EC=EC,#REP=REP.
BEGIN, SAM PL1,,L=SW ITCH.
y i e l d s
REWIND,SWITCH,A,M,XY.
BEGIN,SAMPL1,,L=CHANG,M,N.
or
BEGIN,SAMPL1„L=CHANG,N,M.
y i e l d s
REWIND,CHANG,A,M,XY.
BEGIN,SAMPL1„L=FLIP,M=B,N=Z.
yields
REWIND,FLIP,A,B,Z.
BEGIN,TRACE„IN=,OUT=HOLD,N=.
y i e l d s
COPY,,HOLD,,,EOI,.
BEGIN,SAMPL4„C0IN.
y i e l d s
REWIND,COIN.
ROUTE,C0IN,DC=LP,EC=B6,REP=0.
BEGIN, SAMPL4„C0IN,EC,DC,REP.
y i e l d s
REWIND,COIN.
ROUTE,COIN,DC=LP,EC=A6,REP=0.
Explanation
The L=SWITCH BEGIN parameter
switches parameter matching mode
to order-independent mode.
Order-independent mode uses the
procedure header defaults for
omitted BEGIN parameters. Order-
dependent and order-independent
modes work identically for
omitted BEGIN parameters.
The L=CHANG parameter switches
parameter matching to order-
independent mode. In order-
independent mode the order of the
BEGIN parameters does not
matter. M matches with M, and
the N BEGIN keyword indicates
substitution of the procedure
header default (XY).
BEGIN parameters in the form
keyword53value always override
procedure header parameters.
FLIP replaces L, B replaces M,
and Z replaces XY.
The IN= parameter switches
parameter matching to order-
independent mode. All BEGIN
commands in the form keyword=
u se n ul l s ubs t i tu t i on.
COIN is substituted in order-
dependent mode. EC=B6/A6
switches the mode to order-
independent mode. The omitted
parameters indicate use of the
procedure header defaults (order-
dependent and order-independent
modes work alike for omitted
BEGIN parameters).
EC=B6/A6 switches the mode to
order-independent mode. Specify
ing the keyword on the BEGIN
command produces the same result
as omitting them (refer to pre
vious example) except for the
double default procedure param
eter, EC=B6/A6. If EC is
omitted, B6 is used. If EC is
spec ifled, A6 is used.
60459680 C L-7
![](asset-306.png)
Table L-2. Parameter Substitution In Order-Independent Mode
BEGIN Command Parameter Format
value
omitted keyword keyword= keyword=value
or
$value$t
Procedure
Header
keyword keyword keyword null value error
Parameter
Format keyword= null null null value error
keyword=default1 defaultl defaultl null value error
keyword=default1/
default2
defaultl default2 null value error
t Assumes the parameter is entered under order-independent mode.
Example 1:
The following procedure is the same procedure as Example 2 in Order-Dependent Parameter
Matching Mode. It resides on file PROCFIL. It routes a specified file (FNAME) to the
specified equipment (default is any CDC-graphics line printer).
.PROC,PRINTR,FNAME,REP=0,DC=LP,EC=B6.
REWIND,FNAME.
ROUTE,FNAME,=DC,#REP=REP,#EC=EC.
REVERT. FNAME ROUTED.
EXIT.
REVERT,ABORT. PRINTR PARAMETER ERRORS.
The following command calls the procedure PRINTR. The system matches COLOR in
order-dependent form. DC=SB switches the mode to order-independent mode. SB indicates the
file is to be punched.
BEGIN,PRINTR,,COLOR,DC=SB,EC=SB.
The following is a segment of the dayfile that results when the BEGIN command is processed.
15.27.26.$BEGIN,PRINTR„C0L0R,DC=SB,EC=SB.
15.27.27.REWIND,COLOR.
L5.27.27.R0UTE,COL0R,DC=SB,REP=0,EC=SB.
15.27.27.ROUTE COMPLETE.
15.27.28.REVERT. COLOR ROUTED.
L-8 60459680 H
![](asset-307.png)
Example 2: Parameter Matching in Nested Procedures (Order-Dependent and Order-Independent
Parameter Matching Modes)
As shown in figure L-2, procedures ROUT and PREPARE reside on the default file PROCFIL. A
BEGIN command within ROUT calls PREPARE. In procedure ROUT the substitution for the FNAME
parameter (TEST) is passed to procedure PREPARE by the BEGIN command. The resulting dayfile
is on the right side of figure L-2.
BEGIN,R0UT„TEST,EC=A9,SBF.
PROCFIL
.PROC,ROUT,FNAME=L,SBF=/SBF,REP=0,
EC=B6,DC=LP.
BEGIN,PREPARE„ #FNAME=FNAME.
CO PY_SBF, FNAME, HOLD.
REWIND,HOLD.
IF,$EC$.EQ.$A9$,JUMP.
FCOPY,P=HOLD,N=TEMP.
RENAME,HOLD=TEMP.
ENDIF, JUMP.
REWIND,HOLD.
ROUTE,HOLD,#DC=DC,#EC=EC,#REP=REP.
REVERT. FNAME -> PRINTER.
EXIT.
REVERT,ABORT. ROUT ERRORS.
-EOR-
Resultant Dayfi le
15.27.50.$BEGIN,R0UT„TEST,EC=A9,SBF.
15.27.50 .BEGIN,PREPARE„FNAME=TEST.
15.27.51.IF,FILE(TEST,AS),PREP1.
15.27.51.REWIND,TEST.
15.27. 51. REVERT. TEST PREPARED.
15.27.51.COPYSBF,TEST,HOLD.
15.27.52. EOI ENCOUNTERED.
15.27.52.REWIND,H0LD.
15.27.52.IF,$A9$.EQ.$A9$,JUMP.
15.27.52.FCOPY,P=HOLD,N=TEMP.
15.27.52. FCOPY COMPLETE.
15.27.52.RENAME,H0LD=TEMP.
15.27.52.ENDIF,JUMP.
15.27.52.REWIND,H0LD.
15.27.52.R0UTE,H0LD,DC=LP,EC=A9,REP=0.
15.27.53. ROUTE COMPLETE.
15.27. 53. REVERT. TEST -> PRINTER.
-EOR-
.PROC,PREPARE,FNAME=,M=R.
IF,FILE(FNAME,AS),PREP1.
REWIND,FNAME.
REVERT. FNAME PREPARED.
ENDIF,PREP1.
ATTACH,FNAME/#M=M,NA.
IF,FILE (FNAME,.NOT.AS),PREP2.
GET,FNAME/NA.
IF,FILE(FNAME,.N0T.AS),PREP3.
REVERT,ABORT. FNAME NOT FOUND.
ENDIF,PREP3.
ENDIF,PREP2.
REVERT. FNAME PREPARED.
EXIT.
REVERT,ABORT. PREPARE ERRORS.
BEGIN calls procedure ROUT. The SBF=/SBF parameter switches parameter matching to
order-independent mode. The first command of ROUT is a BEGIN command that calls pro
cedure PREPARE. The parameters are matched in order-independent mode. PREPARE readies
a file for processing. If the file is local, it is rewound. If it is not local, the
system searches for the file in your permanent file catalog. If the file is not found,
the procedure re ver ts and aborts. If the file is fou nd, processing conti nues wi th the
second command in procedure ROUT. The file is prepared for printing. Since the file is
to be printed with the ASCII graphic 95-character set (EC=A9), the file must be changed
to a 12-bit ASCII code file (FCOPY). The procedure then routes the file to the printer
and reverts to the command following the BEGIN command.
C* Figure L-2. Keyword Substitution in Nested Procedures
60459680 C L-9
![](asset-308.png)
/S^JN
![](asset-309.png)
PAPER TAPE OPERATIONS M
GENERAL DESCRIPTION
Paper tape is used for preparing input off-line (when, time is not charged) and entering it
on-line (when time is charged). This ensures accuracy and speed when most needed. An input
tape can include programs, data, and commands. Accordingly, it is possible for the entire
terminal operation, after login, to be run from paper tape.
^ TELETYPEWRITER
This discussion assumes a typical teletypewriter (model 33) with a paper tape punch and a
paper tape reader.
The paper tape punch has four buttons with the following labels and use.
Button Description
ON Turns the punch on.
OFF Turns the punch off.
REL. Releases the feedwheel so you can freely move the tape through the punch
head.
B.SP. Backspaces the tape one row of holes each time it is pressed. This is
used to make corrections when preparing a tape off-line (refer to
Corrections in this sec tion).
The paper tape reader has one switch with four positions. Position labels and use are as
follows:
Position Pcscript ion
START Starts the reader. After switch Is momentarily held in this position,
it snaps back to the AUTO position and reading continues.
S T O P I m m e d i a t e l y s t o p s r e a d i n g .
AUTO This position is used in conjunction with the input and processing of
commands and data in tape mode (refer to Tape Mode in this section). It
allows the tape reader to be turned off and on so that processing of
each command or line of data can be completed before additional input is
entered.
FREE Releases the feedwheel so you can freely slide the tape in and out of
the read head.
NOTE
On teletypewriters lacking an AUTO position,
reading must be manually restarted each time
it has been stopped.
60459680 C M-l
![](asset-30a.png)
CONTROL CHARACTERS
Each line of input from paper tape must end with a particular sequence of control
characters. These are punched by functional keys on the teletypewriter keyboard. The
control characters used with paper tape are as follows:
C h a r a c t e r D e s c r i p t i o n
@ M e s s a g e t e r m i n a t o r . T h i s i s t h e R E T U R N k e y o n t h e m o d e l 3 3 . I t
moves the print head to the beginning of the line and informs IAF
that this line of input is completed.
LF Line feed. This is the LINE FEED key on the keyboard. It advances
the paper roller one line. In normal mode, IAF sends a signal that
initiates this feed; in tape mode, this signal is not sent and is
therefore required on tape.
CTRL/X-OFF X-off. The appearance of this character on the tape during reading
turns the tape reader off. This character is punched by holding
down the CTRL key and pressing the X-OFF key.
RO(n) Rubout. This is the RUB OUT key on the keyboard. It punches a full
row of holes. This row is interpreted as null by the system, and
hence this character is used for spacing and overpunching errors.
The n parameter specifies the minimum number of times this character
should be punched in sequence.
NUL Null. This is the ASCII character represented by a feed hole only ^
(blank tape). It may be used as a fill character.
INPUT LINES
The following line formats are used to enter programs, data, and commands. The left half of
the page shows an example of the input; the right half of the page shows the control
characters that immediately follow the last input character. Each line is terminated with
three rubouts to provide separation from the next line and to allow time for the carriage to
return to the left margin. While it is possible that adequate separation is provided with
less than three rubouts, this is the recommended number. ,<^*\
PROGRAM UNE
100 PROGRAM TEST @) LF R0(3)
DATA LINE
? 12.44,18.31,29.08 @ LF CTRL/X-OFF R0(3)
(The ? is supplied by IAF. The remainder of the line comes from the tape.
X-OFF turns the reader off to allow this data to be processed before the next
line is read.)
COMMAND LINE
CATLIST, L0»F @ LF CTRL/X-OFF R0(3)
( X - O F F t u r n s t h e r e a d e r o f f t o a l l o w p r o c e s s i n g o f t h e c o m m a n d t o b e c o m p l e t e d ' * s ^ \
before the next line is read.)
M-2 60459680 C r
![](asset-30b.png)
PUNCHING TAPE OFF-LINE
The following procedure is used to punch a tape when the teletypewriter terminal is not
logged in.
1. Place the teletypewriter in local mode.
2. Turn the paper tape punch on by pressing the ON button located on the punch.
3. Prepare a tape leader of about 30 rubouts (3 inches) either by simultaneously
pressing the RUB OUT and REPT keys or, if the terminal has the capability by
punching blank tape. '
4. With a pencil, trace the arrow above the punch output onto the tape. This
identifies the start of the tape for reading. (It is possible to put the tape in
the reader backwards.)
5. Type in the input lines with their appropriate control characters.
6. Add a 3-inch trailer of rubouts or blank tape and tear the tape off.
7. Turn the teletypewriter off.
TAPE MODE
To read and process data and commands from tape, it is necessary that the tape reader be
turned off, to allow time for processing, then be restarted. By entering tape mode, you
enable IAF to synchronize tape input with its processing.f
You enter tape mode by using the TRMDEF command (section 8) or a terminal definition command
(appendix K) to change the input device to a paper tape reader. To do this with the TRMDEF
command, enter:
TRMDEF,IN=PT
To perform the same operation with a terminal definition command, press the ESC keytt
(assuming a model 33 teletypewriter is being used) and enter
IN=PT
The TRMDEF command can specify the input device to be in character mode (PT or KB) only to
specify the input device is in transparent input mode (XP, XK, or X), a terminal definition
command must be used. For all other paper tape operations, the TRMDEF command and terminal
definition commands can be used interchangeably. The remainder of this section will use the
TRMDEF command in examples.
The network acknowledges entry into tape mode with the response "IN ACCEPTED." If the
reader switch is in the AUTO position, reading begins automatically; if the reader switch is
in the OFF position, reading does not begin until it is manually initiated by momentarily
moving the switch to START.
tYou cannot use paper tape mode from terminals connected to a packet switching network
^ if OVi ) •
ffThe ESC key is the default control character for terminal class 1. It must be pressed to
signal the entry of a terminal definition command. Because the control character differs
for some terminals, refer to appendix J for the default values for all terminal classes.
60459680 C M_3
![](asset-30c.png)
/C^^K
You can exit from tape mode by using the TRMDEF command or a terminal definition command to
change the input device back to the keyboard. This can be done with TRMDEF by entering:
TRMDEF, IN=KB
The paper tape punch can also be defined as the output device using the TRMDEF command or a
terminal definition command. This can be done by entering:
TRMDEF, OP»PT
You specify this command to enter tape mode for out put ting information to paper tape. This
mode provides the proper X-OFF characters when punching the tape. You can exits this mode
by using the TRMDEF command or a terminal definition command to change the output device
back to a printer. This can be done by entering:
TRMDEF, OP=PR
PUNCHING A TAPE ON-LINE
To punch a tape with information already contained in a system file, the following procedure
is used.
1 . I f n o t l o gg e d i n, l o g i n .
2. If not in tape mode, enter TRMDEF,OP=PT.
3. Type in LIST if the primary file is to be punched; type in UST,F=lfn if a local
file other than the primary file is to be punched. Do not press @.
4. Turn the punch on.
5. Run a leader of rubouts or blank tape.
6. Press @)» The file is listed and punched simultaneously. The network adds the
appropriate control characters at the end of each line.
7. Run a trailer of rubouts or blank tape. y<«^
CORRECTIONS
When punching a tape off-line, corrections can be made by backspacing over the incorrect
punch (use the B.SP. button on the punch) and punching a rubout over the error (use the RUB
OUT key on the keyboard). Then punch in the correct character.
It is also possible to make corrections by using the backspace key as in normal, on-line
operation. However, the error and/or any overtyping appear in the printout. When line
numbers are being used, an erroneous line can be retyped (and repunched) with the same line
n\mber. Although the erroneous and correct versions appear in the printout, IAF retains
only the last occurrence of the specific numbered line during processing.
M-4 60459680 C
![](asset-30d.png)
0^\.
Example:
In this example, the input tape contains only program lines,
before and after the tape is read. Commands and input are typed
The following is the tape as punched. The left half of the page shows the printed copy
produced as the tape is punched; the right half of the page shows the control characters
entered at the end of each line but not printed.
100 LET FACT0R=1
110 INPUT N
120 FOR 1=1 TO N
130 LET FACT0R=FACT0R*I
140 PRINT FACTOR
150 NEXT I
160 END
LF
LF
<£3> LF
@ L F
LF
LF
LF
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(30)
To demonstrate the use of this tape, you must be logged in under the null subsystem. You
position the tape in the reader and set the reader switch to AUTO. The following is the
printout that results. The right half of the page contains explanations of the action.
basic -^
READY.
new, f act 1 -**■
trmdef,in=pt
100 LET FACTORS
110 INPUT N
120 FOR 1=1 TO N
130 LET FACT0R=FACT0R*I
140 PRINT FACTOR
150 NEXT I
160 END
By typing this command, you enter
the BASIC subsystem.
You type in this line to establish a
new primary file with the name FACT1,
As soon as this command is typed in
and takes effect, the tape reader
goes on and the entire tape (seven
lines) is read in. The
reader runs through the trailer of
rubouts and then turns itself off.
READY.
trmdef,in=kb
READY.
You change the input device back to
the keyboard.
run
Z^PP^
ILLEGAL STATEMENT AT 100
ILLEGAL STATEMENT AT 130
ILLEGAL STATEMENT AT 140
BASIC COMPILATION ERRORS
100 let f=1 —
130 let f=f*i
140 print f
■You type in RUN and receive the
diagnostics
shown. BASIC variables cannot be
more than two characters.
You type in the corrective coding
shown.
60459680 C M-5
![](asset-30e.png)
run
? 5
1
2
6
24
120
You in itiate a nother run wi th the
RUN command. IAF replies with ?.
You enter a 5 and receive the
desired printout.
RUN COMPLETE,
trmdef,op=pt - -You want to punch a new tape
containing this corrected program.
You select paper tape as your output
mode.
READY,
list
100 LET F=1 -*
110 INPUT N
120 FOR 1=1 TO N
130 LET F=F*I
140 PRINT F
150 NEXT I
160 END
READY. -*■
-You type LIST but do not press the
@. You turn on the paper tape
punch and run off a leader of blank
tap e. Yo u t hen p r es s t he | @. T hi s
punches a CR on the tape and the
network responds with LF and NUL
punches. These three punches are
not part of the file, and you must
replace them with rubouts if you use
the tape for subsequent input.
IAF begins the listing with a
sequence of CR, NUL(n), LF, and
NUL(m).t BRIEF mode suppresses this
sequence.
IAF punches the tape as it lists the
file. IAF terminates each line with
CR, NUL(n), LF, NUL(m), DC3, and
NUL(2).ft
IAF punches READY, after it has
punched the contents of the file. A
CR-NUL(n)-LF-NUL(m) punch sequence
precedes and follows this message.
flf you enter this tape as input, the CR and LF should be rubbed out, so that the system
does not read them as an empty line. The system ignores all NULs.
.ttRefer to table K-l in appendix K to find n, the carriage return idle count, and m, the
line feed idle count, for your terminal class.
M-6 60459680 C
![](asset-30f.png)
Example:
In this example, the input tape contains not only a program but also the commands to
execute, modify, list, and save that program and the input data used by that program.
The following is the complete tape as punched. The left half of the page gives the printed
copy produced as the tape is punched; the right half of the page shows the control
characters entered at the end of each line but not printed.
FORTRAN
NEW,DEMO
100 PROGRAM DEMO
110 DIMENSION 11(5)
120 READ 10, (II(J),J=1,5)
130 10 FORMAT (515)
140 PRINT 20, (II(J),J=1,5)
150 20 F0RMAT(5I10)
160 END
RUN
1111122222333334444455555
SAVE,DEM0=TAPE1
135 DO 1 1=1,5
137 II(I)=11(I)+4444
139 1 CONTINUE
RESEQ,100,5
LIST
RUN
1111122222333334444455555
REPLACE,DEM0=TAPE1
R0C30)
@ :LF
@LF
@ ,LF
_@LF
@ L F
@LF
<§). IF
® L F
®LF
@ LF
^®LF
@> LF
®LF
@ LF
®LF
@ LF
@)LF
@ LF
©,LF
CTRL/X-OFF
CTRL/X-OFF
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
CTRL/X-OFF
CTRL/X-OFF
CTRL/X-OFF
R0(3)
R0(3)
R0(3)
CTRL/X-OFF
CTRL/X-OFF
CTRL/X-OFF
CTRL/X-OFF
CTRL/X-OFF
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(3)
R0(30)
To execute this tape, you log In to IAF, position the tape in the reader, set the reader
switch to AUTO, type the command TRMDEF,IN=PT and, upon pressing|@ , start the reading of
the tape. You then observe the remainder of the action without intervention.
/»»»
60459680 C M-7
![](asset-310.png)
The following is the printout of the execution of the tape,
contains explanations of the action.
The right half of the page
FORTRAN
NEW,DEMO
100 PROGRAM DEMO ^e-
110 DIMENSION 11(5)
120 READ 10, (II(J),J=1,5)
130 10 FORMAT (515)
140 PRINT 20, (II(J),J=1,5)
150 20 FORMAT(5110)
160 END
RUN -^
? 1111122222333334444455555
1 1 1 1 1 2 2 2 2 2
SRU 0.130 UNTS.
RUN COMPLETE.
SAVE,DEM0=TAPE1 -«
33333 44444 55555
135 DO 1 1=1,5 -«
137 II(I)=II(I)+4444
139 1 CONTINUE
RESEQ,100,5 -*-
SRU 0.576 UNTS.
When this line is read, the reader
stops. As soon as FORTRAN is
established as the current
subsystem, IAF turns the reader back
on.
When this line is read, the reader
s to p s. Af ter a n ew pri mar y fi le
called DEMO is established, IAF
turns the reader back on.
•The seven lines of the program are
read without interruption.
After the command to run the program
is read, the reader is turned off.
After processing reaches the READ
statement (line 120) and after IAF
prints ?, IAF turns the reader on,
and the line of data is read. Then
the reader is turned off to allow
data processing.
Resulting printout:
After the SAVE command is read, the
reader is turned off. A copy of the
program DEMO is made an indirect
access permanent file with the name
TAPE1. Then the reader is turned
back on.
These three lines of modification
are read in from the tape without
interruption.
After the RESEQ command is read, the
reade r is turned off. When rese-
quencing is accomplished according
to specifications, the reader is
turned back on.
/ * ^ \
M-8 60459680 C
>^K
![](asset-311.png)
LIST-*
00100 PROGRAM DEMO
00105 DIMENSION 11(5)
00110 READ 10, (II(J),J=1,5)
00115 10 F0RMAT(5I5)
00120 DO 1 1=1,5
00125 II(I)=II(I)+4444
00130 1 CONTINUE
00135 PRINT 20, (II(J),J=1,5)
00140 20 FORMAT(5110)
00145 END
-After the LIST command is read from
tape, the tape reader is turned
off. Then IAF lists the primary
file which contains the previous
modifications in resequenced
format. When the listing is com
pleted, the reader is turned on
again.
RUN-*-
? 1111122222333334444455555
-After the RUN command is read in,
the reader is turned off, and the
modified program is executed. IAF
prints the ? and then turns the
reader on. The line of data is read
in from the tape and the reader
turned off. The data is processed
and results printed.
15555 26666 37777 48888 59999
SRU 1.185 UNTS.
RUN COMPLETE.
REPLACE,DEM0=TAPE1 -*■-This last command is read in and the
reader turned off. A copy of this
revised version of DEMO replaces the
old one that was made an indirect
access permanent file under the name
TAPE1. It is now the indirect
access permanent file that is
referenced by the name TAPE1.
The reader is turned back on. It
runs through the trailer of rubouts
and then turns itself off.
If, at this point, you have no more
tapes to run, exit tape mode by
entering the TRMDEF,IN=KB command.
60459680 C M-9
![](asset-312.png)
j i . . . ; i
0*%
![](asset-313.png)
MASS STORAGE DEVICE STATISTICS
The mass storage devices supported by the system and the size
access files are as follows:
Device
Code Device PRUs
D B n 8 8 5 - 4 2 D i s k S t o r a g e S u b s y s t e m
( f u l l - t r a c k ; l < n < 3 )
D C n 8 9 5 - 1 / 2 D i s k S t o r a g e S u b s y s t e m
(full-track; l<n<2)
DDn 834 Disk Storage Subsystem
( f u l l - t r a c k ; l < n < 8 )
D E E x t e n d e d M e m o r y
DFn 887 Disk Storage Subsystem
( f u l l - t r a c k ; l < n < 3 )
DGn 836 Disk Storage Subsystem
( f u l l - t r a c k ; l < n < 3 )
DHn 887 Disk Storage Subsystem
( f u l l - t r a c k ; l < n < 2 )
Din 844-21 Disk Storage Subsystem
(half-track; l<n<8)t
DJn 844-4x Disk Storage Subsystem
(half-track; Kn<8)
DKn 844-21 Disk Storage Subsystem
(full-track; Kn<8)
DLn 844-4x Disk Storage Subsystem
( f u l l - t r a c k ; l < n < 8 )
D M n 8 8 5 D i s k S t o r a g e S u b s y s t e m
(half-track; Kn<3)
DP Distributive Data Path to 16
Extended Memory
of blocks allocated for direct
Block Size
CM Words Characters
n*640 n*40960 n*409600
n*704 n*45056 n*450560
n*160 n*10240 n*102400
16 1024 10240
n*608 n*38912 n*389120
n*564 n*36096 n*360960
n*704 n*45056 n*450560
n*107 n*6848 n*68480
n*227 n*14528 n* 145280
n*112 n*7168 n*71680
n*227 n*14528 n*145280
n*640 n*40960 n*409600
1024 10240
tHalf-track is a recording mode that accesses alternate PRUs during a disk revolution;
full-track recording mode accesses consecutive PRUs. Half-track mode needs two revolu
tions to access all PRUs on a physical track; full-track mode needs only one revolution.
60459680 H N-l
![](asset-314.png)
Device
Code
DQn
DV
Device PRUs
885-11/12 Disk Storage Subsystem n*640
(full-track; Kn<3)
DW
819 Disk Storage Subsystem
(single density)
819 Disk Storage Subsystem
(double density)
400
800
Block Size
CM Words
n*40960
25600
51200
Characters
n*409600
256000
512000
In this table, n indicates the unit count for multiunit devices and x is 1 or 4.
If your validation permits (refer to LIMITS Command, section 7), the maximum size of an
indirect access file is the device limit less the space allocated for catalog information
and other files.
The size of a direct access file is limited by the device and by your validation. There are
no other system limitations.
'*cS%
| N - 2 60459680 H
![](asset-315.png)
INTERACTIVE TRANSFER FACILITY (ITF)
jr^tafuffn.
0^\
ITF allows you to connect your interactive terminal to a remote CYBER 200 computer system
linked to your host mainframe by a loosely coupled network (LCN). If you want to submit
batch jobs or want to retrieve or otherwise manipulate permanent files, you can use the
Interactive Facility (IAF) (refer to Submitting Jobs to Remote hosts in section 3).
SELECTING THE ITF APPLICATION
You select the ITF application in the same manner as you would any Network Access Method
(NAM) application, such as IAF or RBF. You specify ITF for the application name during
login to NOS. If you are logged into IAF, you can switch to ITF by specifying ITF on the
BYE, GOODBYE, HELLO, LOGIN, or LOGOUT command.
SELECTING A REMOTE CYBER 200 SYSTEM
Once you select ITF, you receive an ITF banner at your terminal. The following is an
r" example of the two-line ITF banner:
ITF 1.0 - psr level
TERMINAL T103, CONNECTION 12
Your site may automatically connect you to a remote host. If you are not automatically
connected to a remote host, ITF prompts you for the logical identifer (LID) of the remote
host you want to access.
The LID is a three-character name your site has associated with that remote host. The
prompt has the following form:
^ ENTER LID (OR ?):
In response to this prompt, enter one of the following:
Entry Description
lid Specifies the three-character LID your site has associated with
the remote host you are attempting to reach.
? Requests a list of acceptable entries.
carriage return Selects the default LID as defined by your site.
If the connection to the remote host cannot be established (for example, you enter an
invalid LID), ITF so informs you. Unless otherwise directed by your site, ITF will then
prompt you again for a LID. Your site may automatically switch you to another application,
such as IAF, instead of prompting you for another LID.
60459680 C 0-1
![](asset-316.png)
If ITF establishes a connection to the remote host, it displays the following status message:
ITF, CONNECTED TO HOST pid ON ACN n/TCN m
where pid is the physical identifier (PID) of the remote host and n and m are connection
numbers used by the system. Sometimes the PID is identical to the LID you specify.
PROCESSING YOUR JOB ON THE REMOTE CYBER 200
Once your terminal is under the control of the remote host, it gives you the following login
prompt:
ENTER CYBER 200 LOGON
You can then log in and proceed with your interactive job. All of your terminal input is
transmitted to the remote host and all data from the remote host is displayed at your
terminal. You have the following limitations.
• You cannot use transparent input mode (that is, do not enter the IN=X, IN=XK, or
IN=XP terminal definition command).
• Input lines longer than 999 characters are truncated without a comment.
• The termination sequence (user break 2) disconnects your terminal from the remote
host.
To terminate your CYBER 200 job and disconnect from the remote host, enter the $BYE command.
r*^%\
TERMINATING YOUR ITF SESSION
Your site may automatically connect you to another application, such as IAF, any time you
disconnect from the remote host. If not, your terminal returns to the control of ITF. ITF
then prompts you for another LID. To end your ITF session, enter one of the following:
Entry
BYE
BYE, application
Description
Ends your ITF session and logs you out of NOS.
Ends your ITF session and switches you to the specified
application. The following are some valid applications:
application
IAF
MCS
PLATO
RBF
TAF
TVF
Description
I n t e r a c t i v e F a c i l i t y
Message Control System
PLATO-NAM Interface
Remote Batch Facility
Transaction Facility
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
0-2 60459680 H
![](asset-317.png)
SAMPLE ITF SESSION
The following is an example of an ITF terminal session: B2C is the LID of the
remote CYBER 200 computer system:
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978, 198X.
YY/MM/DD. HH.MM.SS. T19A11
CDC NETWORK OPERATING SYSTEM NOS 2
FAMILY: ,usernam,passwrd,itf
ITF 1.0 - psr level
Terminal T19A11, Connection 2
ENTER LID (OR ?): b2c
CITF, connected to host B2C on ACN 1/TCN 2.1
PLEASE ENTER CY200 LOGONlogon 111111 a 99999999
OS 2.1 RSYS21L1 VSYS21L1 I 09837.0412 ACTVE NONE
NIL
WARNING***ATTACHED POOLSfiles.
NAME D OWNER SUF ACS TYPE DT FC BT RT FO ORI.DATE LEN UNIT
12FILES *L0CAL A XR PD MS S C U S YY/MM/DD 00228 OE
ALL DONESbye
BYE
CITF, terminal connection ended by host B2C.11
ENTER LID (OR ?):bye
ITF, CONNECT TIME 00.01.15.
LOGGED OUT.
60459680 G 0-3
![](asset-318.png)
![](asset-319.png)
/piS\
FILE TRANSFERS USING XMODEM
XMODEM is an industry standard communications protocol used to transfer files between CYBER
mainframes and microcomputers. With XMODEM you can upload and download binary files as well
as ASCII text files. To use XMODEM, the microcomputer communication software must use the
Christensen protocol.
XMODEM COMMAND
r
The XMODEM command initiates the file transfer between NOS and microcomputers. Certain
parameters must be specified on the XMODEM command or XMODEM will prompt for them. Other
parameters, if not specified, will be given default values.
You can define a configuration file (described later in this section) to change the default
values for many of the command parameters as well as terminal characteristics. Some of the
default values normally used by XMODEM can be superceded by values specified in your
configuration file. If a value is specified in the command and in the configuration file,
the command value supercedes the configuration file value.
Format:
XMODEM,FN=fn,TD=td,FT=ft,LF=lf,SP=sp,EC=ec,FM=fm,CF=cf.
or
XMODEM,fn,td,ft,If,sp,ec,fm,cf.
Parameter
FN=fn
TD=td
FT=ft
Description
Name of the file to be transferred. The file to be transferred from
the CYBER to the micro may be local or permanent. If the file is not
specified, XMODEM prompts for the file name.
Transfer direction. If TD=S is specified, the file is sent from the
CYBER to the micro. If TD=R is specified, the file is sent from the
micro to the CYBER. If this parameter is not specified, XMODEM
prompts for it.
File type. If this parameter is not specified, XMODEM prompts for it.
A Specifies a 6/12-bit display code text file on the CYBER to or
from 8-bit ASCII on the micro.
Specifies a 6-bit display code text file on the CYBER to or from
8-bit ASCII on the micro.
Specifies a 7-bit ASCII code text file on the CYBER to or from
8-bit ASCII code on the micro.
Specifies a text file. XMODEM uses the current character code set
mode of your CYBER job.
jg^V
60459680 G P - l •
![](asset-31a.png)
Parameter
LF=lf
SP=sp
EC=ec
Description
B Specifies a CYBER binary file.
M Specifies a micro binary file.
S Specifies automatic selection (receive only),
in the first block determines the file type. Special characters
This parameter determines whether an end-of-line on text files sent to
the micro is transmitted as carriage return and line feed (LF=YES) or
only as a carriage return (LF=NO). Default is LF=YES. The default
value may be changed with the configuration file (refer to the
subsection Configuration File later in this section).
This parameter determines whether or not the first block transmitted
will be a special file type block. The default is SP=NO. If SP=YES
is specified, the special block is transmitted. The default may be
changed by the configuration file. For more information on the SP
parameter, refer to Limitations and Considerations subsection.
Error checking (CRC or CHECKSM). The receiver determines the error
checking mode. If TD=S is specified, the micro determines whether to
use CRC or CHECKSM. Default is EC=CRC.
FM=fm
CF=cf
File markers. FM may be set to NOS, CPM, or MSDOS. FM determines
what file markers are recognized or transmitted in text files by the
CYBER. This parameter has no effect on the binary files.
If FM=NOS is specified; #EOR, //EOF, and #EOI are recognized or
transmitted to indicate end-of-record, end-of-file, and
end-of-information, respectively. If used, a 4-character file marker
must appear as the first and only marker on the line.
If FM=CPM or FM=MSDOS is specified, end-of-records and end-of-flies
are ignored on the text files transmitted from a CYBER to a micro.
The end-of-information is transmitted as a CTRL/Z character. On files
received from a micro, XMODEM recognizes a CTRL/Z character as the
end-of-information. #EOR, #EOF, and #EOI are still recognized.
FM=NOS is the default. The default may be changed with the
configuration file (refer to the subsection Configuration File later
in this section).
Configuration file. This optional parameter specifies the name of a
configuration file. The specified configuration file restores your
terminal characteristics after an XMODEM file transfers.
When the CF parameter is used, XMODEM will accept the values for
certain command parameters and terminal characteristics from the
specified configuration file. The format and contents of the file are
discussed in the Configuration File subsection later in this section.
The configuration file may be local or permanent.
• P - 2 60459680 G
![](asset-31b.png)
y^N
USING XMODEM IN PROMPTING MODE
Type in the command:
XMODEM
You will receive the prompt:
HOST TO SEND (S) OR RECEIVE (R) A FILE?
Enter S to send a file from the CYBER to a micro, or R to receive a file from a micro. You
may enter the entire words SEND or RECEIVE.
SENDING A FILE FROM A CYBER
If you selected the transfer direction of SEND, the next prompt will be:
PLEASE ENTER THE FILE NAME.
The file you specify must be a local or a permanent disk file. If the file is empty or
cannot be read, the file name prompt is repeated.
XMODEM will then ask:
I s t h e fi l e -
B - Cyber binary
M - Micro binary
T - Text — Display code (upper case only)
A - Text — 6/12 Display code ASCII (upper/lower case)
E - Text — 8/12 ASCII
After you select a valid option, XMODEM will print the approximate number of blocks to be
transferred and indicate that it is ready to start the transfer. At this point, you should
enter the appropriate commands on the micro to initiate the file transfer.
XMODEM on the CYBER will acknowledge an ASCII NAK, a capital C, or an ASCII CAN (CTRL/X).
If a NAK is received by the CYBER, the file transfer takes place using the checksum method
of error checking. If a capital C is received, the error checking is done using CRC method
of error checking. If a CTRL/X is received, the transfer aborts, and you are back at the
NOS command prompt.
If 10 characters are received and none are among the expected three, the transfer aborts
with the error message:
NO INITIAL NAK RECEIVED.
If a CTRL/X is received at any time during the transfer, the transfer aborts.
60459680 G P-3
![](asset-31c.png)
RECEIVING A FILE FROM A MICRO
If you elected to receive a file from a micro, XMODEM prompts:
PLEASE ENTER THE FILE NAME.
Enter the local file name under which you wish to have the file stored on NOS. If the file
name is invalid or you cannot write to it, XMODEM repeats the prompt.
Next, you are asked:
I s t h e fi l e -
B - Cyber binary
M - Micro binary
T - Text — Display code (upper case only)
A - Text — 6/12 Display code ASCII (upper/lower case)
E - Text — 8/12 ASCII
S - Auto-select file type
After you select a valid option, you should enter the micro commands necessary to start the
transfer. XMODEM on the CYBER sends out an ASCII NAK or capital C (depending on the value
set for the command parameter EC) until it either receives a block from the micro or has
tried 10 times to initiate the transfer. After 10 tries, XMODEM aborts.
If a CTRL/X (ASCII CAN) is received as the first character in a block, XMODEM aborts, and
you are back at the NOS command prompt.
yfi«m^\
CONFIGURATION FILE
XMODEM can accept the values of some parameters from a configuration file. With this file,
you can change the default values for parameters LF, SP, EC, and FM. You can also reset
certain terminal characteristics.
These are the rules for the configuration file entries:
One parameter entry per line is allowed.
Uppercase and lowercase characters may be used.
Blanks are not significant.
Lines beginning with an asterisk (*) are considered as comment lines.
Each line may optionally be terminated by a period.
Comments may follow the period on the same line.
• P-4 60459680 G
![](asset-31d.png)
The following are the parameters you can specify:
Keyword Possible values
LF
SP
EC
FM
PA
EP
IC
OC
AC
Example:
EC = CRC.
SP = NO.
LF = Y.
EP = N.
OC = Y.
YES, NO, Y, N
YES, NO, Y, N
CRC, CHECKSM, CR, CM
Description
Line feed issued after carriage return.
Default is YES.
Spe ci a l file t y pe blo ck i ss ue d . D ef au l t i s
NO.
Error checking. Maximum parameter length
is 7 characters. Default is CRC.
NOS, CPM, MSDOS, N, C, M File marker type. Default is NOS.
NONE, EVEN, ODD, ZERO,
N, E, 0, Z
YES, NO, Y, N
YES, NO, Y, N
YES, NO, Y, N
decimal number
Set error checking.
Value to which parity will be reset upon
termination of XMODEM file transfer.
Default is NONE.
Echoplex value set at termination of file
transfer. Default is NO.
Input flow control reset value. Default is
YES.
Ou tp ut fl ow co ntrol re se t va lu e. D ef au lt
is YES.
Attention character (affects CDCNET
terminals only). Refer to the CDCNET
Terminal Interface Usage Manual.
60459680 G P - 5 •
![](asset-31e.png)
FILE TRANSFER NOTES
There are three types of files that can be transferred: text files, CYBER binary files, and
micro binary files. The processing of file markers and carriage control indicators (line
feed, for example) depends on the type of file being transferred and the direction of
transfer.
TEXT FILES
Text files have either an ASCII carriage return or a carriage return and a line feed
appended to the end of each line when transferred from a CYBER to a micro.
When a file is transferred from a micro to a CYBER, carriage returns are translated into ^^^
zero byte terminators, and an ASCII line feed is ignored if it immediately follows a ^"**s%
carriage return. If the FM=CPM or FM=MSD0S parameter is specified, XMODEM recognizes a
CTRL/Z character as the end-of-information and also recognizes i/EOR, #EOF, and #EOI file
markers. If FM=NOS is specified, XMODEM recognizes or transmits #EORs, #EOFs, and #EOIs.
To be recognized, a 4-character file marker must appear as the first and only characters on
a line.
If a file received by the CYBER is transferred as a display code text file (uppercase only),
lowercase alphabetic characters are translated as uppercase. Untranslatable characters are
set to asterisks (*), except for the ASCII NULL character, which is ignored.
CYBER BINARY
A CYBER binary file is transferred eight bits at a time. The file is blocked during
transmission, with the first character being the length of the block or an EOR/EOF/EOI
marker. If an EOR/EOF marker is found, the next character is again a block length or an
EOR, EOF, or EOI. The maximum block size is 240 (decimal). A value of 253 indicates an
EOR, 254 indicates an EOF, and 251 indicates an EOI. Only files that are transferred from
CYBER to a micro as CYBER binary files can be transferred from a micro to a CYBER as CYBER
binary files, otherwise unpredictable results can occur.
Any data received by the CYBER after the EOI marker is received is acknowledged but
discarded.
MICRO BINARY
A micro binary file received by the CYBER is stored as 8/12-bit ASCII. Each 8-bit ASCII
character received is stored on the CYBER as a 12-bit ASCII character with the high order
bit set. When the file is transmitted back to the micro, any zero character is ignored.
Thus, a NULL character must be represented as 4000B. The high order bit is optional on all
other .characters. A file processed by FCOPY meets these requirements, except that end of
lif.es (since they are zero) are ignored. This method is necessary to guarantee that the
file is sent back to the micro exactly as it was received.
• P - 6 6 0 4 5 9 6 8 0 G '
![](asset-31f.png)
LIMITATIONS AND CONSIDERATIONS
The following are general tips on using XMODEM:
• Since the XMODEM protocol is an 8-bit protocol, parity must be set to NONE. XMODEM
internally issues a TRMDEF,PA=N. However, data networks such as local area networks
may force a specific parity. Such networks must be configured for transparent data
transmission. If they are configured to force parity other than NONE, XMODEM will
not work. The communications path must be capable of transmitting all 256 ASCII
characters.
• Echoplex must be set to OFF (EP=N). If EP=Y is set, each character sent to the
CYBER is echoed back, and the micro cannot distinguish between echoed data and real
data transmitted by the CYBER. XMODEM internally turns echoplex off. As there is
no way for XMODEM to determine the current setting of echoplex, it normally leaves
it off after the transmission. This can be altered by using the configuration file
(described earlier). Some data networks may echo data themselves, rather than
having the CYBER front end echo the data. XMODEM cannot disable this echoing. You
must disable the echoing.
• Some micros, such as the APPLE,t require the high order bit in each character to
be set for some files. This is also true of some word processors, such as
WORDSTAR. If the file is transferred as a 6/12-bit display code text file to the
CYBER, the high order bit is lost because these character sets do not support all
256 ASCII characters. To get around this problem, you can either write a program on
the micro to restore the high order bit, or you can transfer the file to the CYBER
as an 8/12-bit ASCII file, or as a micro binary file.
• If the SP parameter is set to YES, the first block transmitted from the CYBER to the
micro is of this form:
SOH+200B/filetype/255D-filetype/123D/zeros
Where SOH is an ASCII SOH, and file type is
00 - Text
04 - Micro binary
08 - Cyber binary
The 123 is included to ensure that the checksum does not match so that micros which
do not recognize this block will respond with a NAK (Negative Acknowledge). This
block is recognized by ASCII Expressft for the Apple. If the special block is not
supported by your micro's transfer program, it will be considered an invalid block
and will be NAKed. If this block is NAKed three times, the transfer will proceed
with the data.
If the first block received by the CYBER is of this form and the file type was set
to auto-select, the file type in the block is used to determine the file type used
f or t he t ra n sf e r. I f a n i n val id fi le t yp e i s d e te c ted , m icr o b i na r y fi le i s u sed .
If the auto-select mode is set and no special file type block is received by the
CYBER, a file type of TEXT with 6/12-bit display code is used.
tA registered trademark of Apple Computer, Inc.
ttA registered trademark of United Software Industries, Inc.
60459680 G p-7
![](asset-320.png)
Although the CYBER implementation supports most common extensions to the XMODEM
protocol, it does not support batch mode. If you try to transfer files using batch
mode, the transfer terminates.
As input timeout has not been implemented in NOS, XMODEM does not timeout after 10
seconds and does retransmit the last block. The protocol requires the receiver to
timeout, but the sender may not always timeout. This causes problems only when the
micro is the sender and the micro does not timeout. Most XMODEM packages available
for micros timeout in both directions; so this limitation will not normally cause
any problems.
• P-8 60459680 G
![](asset-321.png)
INDEX
jfi9?\
/$te\
AAM (See Advanced Access Method)
AB command J-5
Abbreviated job status command 8-17
Abort C-l
Abort output character 16-5; J-5
Aborting output 16-5
ABS rec or d type 15-3 ,6
Absolute binary card output F-7
ACCESS command 8-12
Access level C-l
Access level, equipment C-4
Access subsystem 8-12,20.1,37
Account block 3-11; 7-4,59,63; C-l
Account dayfile 3-18; 7-4
Accounting for system resources 3-8; 7-4
Accumulated central processor time
| 3-18; 7-10,17
ACF record type 15-3
A d d e r a c t i v i t y 3 - 1 8
Address out of range error 6-23
Advanced Access Method (AAM) 1-6
AEMP (See Matrix Array Processor (MAP),
resource usage)
AESR (See System Resource Unit (SRU)
Allocatable device C-l
Alphanumeric C-l
ALTER command 8-42
Alternate storage subsystem 2-15,16
ANSI labeled tapes 2-8; 12-9,13,19; G-l
ANSI X3.64 standard terminal 16-1; J-25
APPEND command 10-7
APPEND mode 10-8
Appending files 10-7
Application C-l
Application, resource usage 3-18
Application switching 3-5; 8-18,19,21;
C-l; J-2
APPSW command 8-18,19
AR command J-5
ARG= entry point 15-43
Argument C-i
ASCFL code 9-23
ASCII C-l
ASCII code set 9-23; A-l,12
ASCII command 8-2; A-3
A SC I I g ra p hi c c h ar act er set s A -l
ASCII graphic 63-character set A-l,2
ASCII graphic 63/64-character set 9-46; A-l
ASCII graphic 64-character set 9-48;
A-l,2,3
ASCII graphic 95-character set 9-46,48;
A-l,2,3
ASCII mode 8-2,4; A-3; E-l
ASCII 128-character set A-l,3
ASCII, 7-bit code 9-23; A-l
ASCII63 code 9-23
ASCII64 code 9-23
ASCII8 code 9-23
ASCII88 code 9-23
Assembler language 1-5
ASSIGN command 2-15; 9-2; 12-5
Asynchronous terminal output 16-5
Asynchronous terminals J-4
ATTACH command 10-7
ATTN key, IBM 2741 terminal 16-8
AUTO command 8-3
Auto-drop status 9-56
Auto eject mode H-2
Auto mode 8-3
Automatic line spacing H-2
Auxiliary device 2-15,16; 10-4; C-l
B format tapes 9-59,64; 1-1
Backspace character 16-3; J-7
BAM (See Basic Access Method)
Banner page 9-54,55; D-2
BASIC C-l
Basic Access Method (BAM) 1-6
BASIC command 8-12
BASIC subsystem 8-12
BATCH command 8-13
B a t c h j o b 3 - 1
Batch subsystem 8-13
BCD code A-l2
BEGIN command 4-41,53
Beginning-of-information (BOI) 2-3,4; C-2
BF command J-6
Binary card F-l,5
Binary dump 11-1
Binary file 15-14
Binary input mode K-l
Bi nary mo de 2- 7; 9- 7
Bisynchronous terminals J-4
Bit C-2
BKSP command 9-4
BLANK command 12-9
Blank label, magnetic tape 12-9
B l o c k C - 2
BLOCK command 7-2
60459680 H Index-1
![](asset-322.png)
Block count G-8,9
Block mode J-18
Block size 12-13; N-l
Block size, terminal input J-6
Blocking factor J-6
BOI (See Beginning-of-information)
BR command J-6
BREAK key 16-5; J-6
BRIEF command 8-4
BS command J-7
BUFFER OUT statement, FORTRAN 2-7
BYE command 3-4; 8-19
Byte C-2
Bl command J-7
B2 command J-8
Cancel character J-9
Cancel line character 16-4,5
CAP record type 15-3,15
C a r d , b i n a r y F - l , 5 , 6
Card, coded F-l,3
Card deck, physical file structure
2-5,6
Card file 2-6
Card file data conversion F-l
C ar d for m at s F -2
Card punch 1-4
Card, punch format F-l
Card reader 1-4
Cards punched, record of 3-19
Carriage control array H-7
Carriage control characters H-2,3,4,5
Carriage control tape H-3
C a r r i a g e r e t u r n J - 1 2 , 1 3 ; K - l
C a rr i a g e r e tur n f unc t i on 1 6 -3
Catalog C-2
CATALOG command 15-3,5
Catalog track 2-7
CATLIST command 8-28; 10-3,10
.CC directive 4-33
CCCCCCO file 13-1
CCP (See Communications Control Program)
CDC graphic 63/64-character set 9-47
CDC 711-10 terminal 16-1; J-25
CDC 713-10 terminal 16-1; J-25
CDC 714-10/20 terminal 16-1; J-25
CDC 714-30 terminal 16-1; J-25
CDC 721 terminal 16-1; J-25
CDC 722-30 terminal 16-1; J-25
CDC 722 terminal 16-1; J-25
CDC 731-12 terminal 16-1; J-25
CDC 732-12 terminal 16-1; J-25
CDC 734 terminal 16-1; J-25
CDC 751-1 terminal 16-1; J-25
CDC 752 terminal 16-1; J-25
CDC 756 terminal 16-1; J-25
Index-2
CDCNET 3-2; 8-9; 16-1
CDCNET network 8-10
CEJ/MEJ (See Central/Monitor exchange jump)
Central library directory 5-5
Central memory allocation 1-3
Central memory (CM) 1-2
Central memory dump 11-1,5,7,9,10
Central memory, presetting 7-55
Central memory resident (CMR) 1-3
Central memory time slice 3-12
Central processor time, accumulated
3-18; D-4
Cent ra l proces sor u nit ( CPU ) 1-2
CFO command 7-4
CH command J-8
CHANGE command 10-15
Character C-2
Character code set conversion 9-23; A-l
Character conversion E-l
Character echoing J-14
Character input mode K-l
Character set
Anomalies A-2
ANSI standard A-l
ASCII A-l
ASCII graphic 63-character set A-l
ASCII graphic 64-character set 9-48;
A-l
ASCII graphic 95-character set 9-48;
A-l
ASCII 128-character set A-l
Batch job A-2,3,7
CDC graphic 63-character set A-l,3
CDC graphic 64-character set A-l,3
Conversion for magnetic tapes 9-23;
A-l 2
Definition A-l
Interactive job 8-2,6.2; A-2,3,5
NOS-supported A-l
Recognition J-5
Character set mode 8-4
CHARGE command 7-4
Charge number 7-4
Checkpoint 9-38; 13-1; C-2
Checkpoint dump 13-1,3
Checkpoint file 9-38; 12-8,14; 13-1; C-2
Christensen protocol P-l
CHVAL command 7-5
CI command J-9
CKP command 13-1
CLASS command 7-7
CLEAR command 9-5
Clock cycle count 7-22.1
CM (See Central memory)
CMR (See Central memory resident)
CN command J-9
COBOL, RECORDING MODE IS BINARY statement
2-7
60459680 H
/**»«S%y
![](asset-323.png)
n-
COBOL, RECORDING MODE IS CODED statement
2-7
COBOL, sign overpunch convention A-2
Code set
ASCII A-l
Conversion
Definition
Display code
NOS-supported
9-23; A-l
A-l
A-l
A-l
A-2
5-2
5-3
5-2
6-bit display code 8-2,6.2; A-l
6/12-bit display code 8-2,6.2; A-l
Code set conversion 9-23; A-10
Coded card conversion F-4
Coded card output F-6
Coded file 9-13,51
Coded line 2-7
Coded mode 2-7; 9-7
Colon, code set representation
Colon representation F-l
Command
Continuation line 5-2
Format 5-2,3
I n t e r a c t i v e s t a t u s 8 - 1 6
Multiple entry 7-21
Prefix character
Processing 5-1
Syntax 5-2
Terminator 5-2
Terminator character
Command processing
Dollar ($) prefix 5-2
Operating system format
Product set format 5-2
Separator characters 5-2
Slant (/) option 5-2
Terminator character 5-2
Command processing flow 5-5
Command record
J o b 3 - 1 ; C - 2
Procedure 4-3,4,5
Commands
File maintenance 14-1
Global library file 5-1
Iterative G-31
Load/dump memory 3-13
Local file 5-1
Primary file editing 5-2; 8-39
Product set 5-1
Protected 3-13
Skipping 6-17,18,30
Subsystem selection 8-11
System 5-1
Tape management 12-1
Terminal definition J-l
COMMENT command 7-9
Comment (*) directive 4-40.1
COMMON command 10-16
9-26
9-26
5-2
Communications Control Program (CCP)
3 -2 ; 16- 1 ; J -l, 2
COMPASS 1-5; 7-39
COMPASS compressed output
Compile C-2
Compiler language 1-5
Compressed output, COMPASS
Connect time 3-4
Connection status 6-7
Constants 6-5
Continuation line, command
Control byte 16-9
Control character C-2
Control character, character set
Control point C-3
Control registers 6-8
Control registers, flow control command
6-25; 7-16
Control statement C-3
Conversion, code set 9-23; A-10,12
Conversion mode F-3
Conversion mode, 9-track tape 12-7,14
COPY command 2-7; 9-5
A-l
COPYBF command 9-11
COPYBR command 9-12
COPYCF command 9-13
COPYCR command 9-15
COPYEI command 9-16
Copying files
Binary mode 9-7
Coded files 9-13,15,51
Coded mode 9-7
Multifile files 9-10,11
Multirecord files 9-12
Octal copy 9-62
Processing options 9-10,62
Record replacement 15-7
Tape files 9-59
Termination 9-7,10
Verification 9-10
Copying records 15-7
COPYL command 15-3,7
COPYLM command 15-3,7
COPYSBF command 9-17; F-2
COPYX command 9-18
.CORRECT directive 4-23
Correspondence code 8-2
CP command J-10
CPU mode error 6-22
CPU priority 7-64
CPU (See Central processor unit)
CPU time, accumulated 7-10,17; D-4
CPU time limit 7-64
CPUMTR 1-3
CRM (See CYBER Record Manager)
CSET command 8-4
CT command J-10
60459680 H Index-3
![](asset-324.png)
ct D command
ct E command
ct S command
CTIME command
8-16
8-17
8-17
7-10
CTR L/F c ha ra ct er 16- 6
CTRL/P character 16-6
CTRL/T character 16-6
Cursor positioning J-10
CYBER control language level 6-7
CYBER loader 1-6; 7-60; 15-32,33; C-3
CYBER Record Manager (CRM) 1-6; 2-2,3;
9-1; 10-8; 15-1; C-3
CYBER 200 Computer System 3-6
Data blocks, network J-6
.DATA directive 4-3,4,14,34.1
//DATA symbol 4-14,34.2
Database file 2-15
Date 6-7
Day of the week 6-7
Dayfile 7-10; C-3; D-4
Account 3-18
Job 3-18
DAYFILE command 7-10
D C1 J - 18 , 2 1
D C3 J - 18 , 2 1
DDP (See Distributive data path)
Deadlock 7-51,52
Deadstart C-3
DEC VT100 terminal 16-1; J-25
Default C-3
Deferred batch jobs 7-68
Deferred routing 9-35,44,45,46
DEFINE command 10-17
DELETE command 8-44
Deleting input lines 16-4
Delimiters for input K-l
Detach command 8-16
Detached interactive job
Device C-3
Assignment 7-57
Auxiliary 2-16; 10-29
Family 2-15
Mass storage 2-15
Type 6-13,14,15; 7-51; 9-2; 10-4.1; N-l
DIAL command 8-20.1
Direct access file 2-11,14; 10-7,17; C-3
2-12; 8-16,30; C-3
Directory
Library 5-5
Random access 15-24
DIS code 9-23
Disk, auxiliary 7-51,52,57
Disk physical file structure 2-5
Disk storage subsystems 1-4; N-l
Display code C-3
Display code, 6-bit 8-2; 9-23; A-l
Display code, 6/12-bit 9-23; A-l
DISPLAY command 6-16.4
Disposition code C-3
Disposition code, ROUTE command 9-44
Distributive data path (DDP) 1-4; N-l
DIS63 code 9-23
DIS64 code 9-23
DL command J-l1
DMB command 11-1
DMB Extended memory error 11-4
DMB output 11-3
DMD command 11-5
DMDECS command 11-6
DMP command 11-6.1
DMPECS command 11-7
DOCMENT command 9-20
DROP command 7-12.1
DROPDS command 10-21
Dropping jobs 7-12
D T f unc t i o n 6 - 1 4
Dual processors 3-18; 7-64
Dual-state, NOS/VE 3-5
Dump 9-62; 10-33
Central memory 11-1,5,6.1,9,10
Checkpoint 13-1,3
Exchange package 11-1,5,6.1
Extended memory 11-1,6,7
Field length 11-1
Dump memory commands 11-1
DUP command 8-45
E format tapes 9-59,64; 1-2
EB command J-l2
EBCDIC code A-l2; C-3
EBCFL code 9-23
Echoing J-14
Echoplex mode J-14
ECS (Extended Core Storage; See Extended
EDIT command 14-1
EEA (See Error exit address)
EFFECT command 8-4
EL command J-13
ELSE command 6-17
.ELSE directive 4-38
Empty PRU/record C-4
End-of-block character J-12
End-of-file (EOF) 2-3,4; 9-51; C-4; F-2
End-of-file label G-l,8,10
End-of-information (EOI) 2-3,4; C-4; F-2
E n d - o f - l i n e F - 2 ; H - l ; K - l
End-of-line byte A-2; F-l
End-of-line character J-13
End-of-record (EOR) 2-3,4; 9-51; C-4; F-2
End-of-reel 1-3
End-of-tape (EOT) 12-4,5; C-4; G-l; 1-3
End-of-volume label G-l,9,10
^um*$.
Index-4 60459680 H
![](asset-325.png)
0^\
r
.ENDHELP directive 4-24,31
ENDIF command 6-18
.ENDIF directive 4-38
ENDW command 6-19
ENQUIRE command 2-12; 7-13; 9-50
ENTER command 7-21
.ENTER directive 4-24
Entry point, definition C-4
Entry point, library directory 15-33
Entry point listing 15-5,15
.EOF directive 4-38
EOF (See End-of-file)
E O Fn l a b e l G - l ,10
E0F1 label 2-8,9; 12-9,11; G-8
EOI (See End-of-information)
.EOR directive 4-38
EOR (See End-of-record)
EOT (See End-of-tape)
EOVn label G-l,10
E0V 1 lab el 2-8 ,9 ; G -9
EP command J-14
Epilogue C-4
Epilogue, project C-ll
Equipment access level C-4
Equipment status table (EST) 3-19
ERRMSG command 7-22
Error codes, system 6-9,10
Error exit mode 6-22
Error flag 6-8,25; C-4
Error messages B-l
E rr o r p ro ces sin g 3 -12 ; 5 -7; 6-2 3
EST ordinal C-4; D-4
EST (See Equipment status table)
EVFU load file H-2,4.2
EVICT command 9-22
.EX directive 4-9,38
Exchange package 3-12; C-4
Exchange package dump 11-1,5,6.1
Executable object code C-5
EXECUTE command 8-13
EXECUTE mode 10-8
Execute subsystem 8-13
Execution time 1-2
EXIT command 3-12; 5-7; 6-19
Exit mode 6-8
Exit processing 5-7
.EXPAND directive 4-6,33,34.2
EXPLAIN command 8-20.1
Extended instruction stack purging C-5
Extended memory 1-3; 7-25; C-5; N-l
Extended memory dump 11-1,6,7
Extended memory error 11-4
Extended memory field length (FLE) 3-9
Extended memory preservation 7-44
Extended memory reference address (RAE)
Extended stack purging 7-39
External references, library directory 15-33
F tape format 2-9; 9-10
FA command J-14
Family 2-15; D-2
Family device 2-15; C-5
Family name 6-8.1; 7-74; C-5
F C I 1 2 - 4 ; C - 5
FCOPY command 2-7; 9-23; A-12
FET (See File environment table)
Field length, extended memory (FLE) 3-9
Field length (FL) 1-2; 3-9; 7-24,39,57; C-5
Load/Dump 11-1
Field length, maximum (MAXFL) 3-9; 7-39
Field length, running (RFL) 3-9; 7-40
F i l e
Append operations 8-51; 10-7
Assignment to device 9-2
Backspacing 9-4
Backup copy 10-3
Copying 8-51; 9-5,16,17,62; 15-7
Copying lines 8-49,52
Creation 2-12,13
C rea t i on d a te 1 0 -13 ; G -8 , 9
Definition 2-1; C-5
Device residence 2-7,15,16
Editing 14-1,14,18
Execution 8-35
E x t e r n a l c h a r a c t e r i s t i c s 9 - 4 6
External documentation 9-20
Generation number G-8,9
Information 15-5
Internal characteristics 9-48
Internal documentation 9-20
Listing record information 15-14
Locked 9-26,65
Logical 2-1,2
Maintenance 15-7,11
Organization 2-3
Overwriting data 9-35
P a c k i n g 9 - 3 6
Physical structure, by device type 2-5
Positioning 9-4,43,56,57,58
Printed output formatting 2-12
Printing 9-46
Purging 10-31,32
R e f o r m a t t i n g 9 - 2 7
Releasing 9-5,22,42,56,64
Replacement 10-45
Resequencing 9-39
Retrieval 10-7,20,21,28
Rewinding 9-43
Routing 7-36; 9-31,35,44
Simultaneous user access 10-8,9
Sorting 9-40,58
Status 7-15,27; 9-56
S t o r i n g 1 0 - 4 5 , 4 6
Structure 2-1
Structure, CRM logical 2-3
60459680 H Index-5
![](asset-326.png)
F i l e
Structure reporting 9-51
Subdivisions 2-1,2,3
Subsystem association 8-12; 10-5
Terminology 2-3
Transfer between mainframes
9-31,49,50; 10-21
Ty p e s 2 - 1 1
Verification 15-35
Verifying 9-65
File access category 3-14; C-5
File access level 3-14; C-6
File access mode 2-14; 10-8,10
F ile a cce s s ab i l ity c h ar a c te r, t a p e 1 2 -1 0 , 15
File attribute 6-12
File, binary 15-14
F i l e , c a r d 2 - 6
File catalogue 10-10
File, checkpoint 9-38; 13-1
File, coded 9-13,51
FILE command, CRM 2-7
File, database 2-15
File, direct access 2-13,14; 10-7,17
File directory 15-1
File environment table (FET)
File expiration date G-8,9
FILE function 6-12,13
File header label G-l,4,10
F i l e , i n d i r e c t a c c e s s 2 - 1 4 ;
Fi le i nf ormat io n ta ble (F IT)
File marks 2-5; 9-36,51,68
File, mass storage 2-6,15
File, multifile 2-3,4
File name 2-1
File n ame table (FNT) 5-5
File password 10-4.1
File, permanent 2-13,14; 10-10,15,45,46
Fil e permissi on mod e 10-5,30
File permit category 10-3
File, primary 2-13; 9-37
File, private 10-3
File, program library 2-17
File, public 10-3
File, queued 7-45; 9-31,44
File residence 2-15; 10-4.1,29
F i l e , s e m i - p r i v a t e 1 0 - 3
File sequence number, tape 12-15
File set C-6
File symbol 4-14
File, SYSTEM 10-16
File, temporary 2-12
File transfers
Mainframe-mainframe 10-23
Mainframe-micro Pl
File types 2-11
File, user library 2-17
FIT (See File information table)
FL (See Central memory field length)
C-6
10-7,20; C-7
C-6
Flag C-6
FLE (See Extended memory field length)
Flow control command
Continuation lines 6-2
C o n t r o l r e g i s t e r s 7 - 1 6
Expressions 6-2
Format 6-2
Functions 6-12
Ope ra nds 6 -2
O p e r a t o r s 6 - 2
Symbolic names 6-7,25
Syntax 6-2
. F n d i r e c t i v e 4 - 2 4 . 1
FNT (See File name table)
Format channel selection H-4.2
Format controls, 580 line printer H-l
Format effectors 8-4
Forms code 9-47
FORTRAN C-6
FORTRAN, BUFFER OUT statement 2-7
FORTRAN command 8-14
FORTRAN subsystem 8-14
Frame C-6
FSE command 14-2
FTNTS command 8-15
FTNTS subsystem 8-15
Full-ASCII mode 8-2; J-14
Full-duplex mode J-14
Full Screen Editor (FSE) 14-2
Batch mode 14-2
GE tape density 7-54
Generation C-6
GET command 10-20
GID (See Record group identifier)
Global error flag 6-8,25
Global library set 5-5; 6-13; 15-43; C-6
GO command 7-22
GOODBYE command 3-4; 8-21
Graphic C-6
Graphic character A-l
GTR command 15-3,11
GTR directives 15-12
HAD (See Host availability display)
Half-duplex mode J-14
Hardware, System 1-1
HAS P te rmi na l s 16- 1; J -l ,4 , 25
HAZ terminal J-l
Hazeltine 2000 terminal 16-1; J-l,25
HC command J-15
HD command J-15
HD tape density 7-54
HDRn label G-l,10
/• ■sSSSX
Index-6 60459680 H
![](asset-327.png)
I HDRl label 2-8,9; 12-9,11,15; G-4
HELLO command 3-5; 8-21
HELLO7 command 3-5,6.1; 8-22
HELP command 8-26
.HELP directive 4-25
Help, online 8-26
HELPME command 8-26
HHA (See Highest high address)
Highest high address (HHA) 3-9
HN command J-17
Hollerith punch code F-3
Hollerith punch output F-5
Host availability display (HAD)
3-5; J-15,16
Host node selection J-15,18
HTIME command 7-22.1
I format tapes 2-9,10; 9-10,59,64
IA F (See Inte ra ct iv e Fa ci li ty )
IBM 2741 terminal 16-1,8; J-25
IBM 27 80 16-2; J-25
IBM 3780 16-2; J-25
IC command J-18
| . I C d i r e c t i v e 4 - 3 4 . 1
Idle characters J-9
| IF command 6-20
.IF directive 4-4,38
.IFE directive (See .IF directive)
Immediate job status command 8-17
I m p l i c i t r e m o t e r o u t i n g 9 - 4 8
Implicit routing 9-50
IN command J-18
Indefinite operand error 6-23
Indirect access file 2-14; 10-7,20; C-7
Input data E-l
I n p u t d e vice s e l e c t i o n J - 1 8
Input disposition 2-11; 9-44
Input file 2-11; 3-11; C-7
I N P U T, fi l e 3 - 1 1
I n p u t fl o w c o n t r o l J - 1 8
Input line
Correction 16-3
Deletion 16-4
Entry before prompt 16-4
Length 16-3
Te r m i n a t i o n 1 6 - 3
I n put p r o mpt 1 6 - 4
Input queue 2-11
Input transmission mode J-18
Instruction stack purging 7-39; C-7
Interactive Facility (IAF) 1-1; 3-2,4,6;
8-4; 16-1; C-7; J-l,25
Interactive job 3-1
Interactive job origin 3-6.2
Interactive job subsystem 6-11
Int eractiv e stat us c om mands 8- 1,16; 16 -4
Interactive Transfer Facility (ITF) 3-6
Interrecord gap C-7
Interruption character 16-6; J-7
Interruption sequence 16-4,6,7; C-7; J-6,7
ITEMIZE command 15-3,14
Iterative command 6-31
IT F (S ee In te racti ve Tr an sf er F ac ilit y)
Job C-7
Accumulated CPU time 7-10
Checkpoint 13-1
Completion 3-17
Control 3-9
Dropping 7-12
Entry 3-1; 7-25,68
E r r o r p r o c e s s i n g 6 - 2 3
E x i t p r o c e s s i n g 5 - 7
Field length 1-2; 3-9; 7-24,35,57
Initiation 3-1
Output 3-19; D-l
Output processing 2-12; 7-62
Remote routing 3-6; 9-31,44; 10-21
Resource demand 7-14,51
Resource usage 3-18; 7-17,59,64,67
Restart 13-1
Scheduling 3-9
Scheduling priority 3-6.2
Security 3-13
Status 7-13,21,73; 8-17,31
Summation of activity 3-18
Suspension 7-62,63,65
Te r m i nat i o n 2 - 11 ; 3 - 1 ; 5 - 7 ; 7 - 6 2
Time limit 7-24
Timeout period 3-4
Job access category set C -7
Job access level C-7
Job card 7-23
Job command 3-6.1; 7-23
Job communication area 5-4
Job control
Command limit 3-11
Error 3-12
Input file 3-11
Rollout 3-12
SRU limit 3-11
Time limit 3-11
J o b fi l e 2 - 1 1
J o b i n p u t fi l e 3 - 1 1
Job, interactive 3-1
Job name 3-7
J o b o r i g i n t y p e 3 - 6 . 2; 6 - 7 ; D - 2
Job priority 2-12; 3-7,9; 7-23,24,64
Job processing parameters 7-23
Job, remote batch 9-50
Job, rolled out 3-12
Job scheduler 7-58
60459680 H Index-7
![](asset-328.png)
Job sequence name (JSN) 3-6.2; 7-18; C-7;
D-2
J o b s e r v i c e c l a s s 3 - 6 . 2
J o b s t e p C - 7
I nt e rr u pti o n s eq u enc e 1 6 -6
SRU limit 3-11
Suspension 16-7
Time limit 3-11; 7-64
Job termination 2-11
JSN (See Job sequence name)
KEY command 8-5
Keypunch conversion mode
KRONREF command 14-4 2-6; F-3
L format tapes 2-9,10; 9-10; 12-2
L tape format 2-7
Label C-7
ANSI G-l
Magnetic tape 2-8; 12-11,19; G-l
O p t i o n a l G - l , 1 0
Required G-l
User G-ll
LABEL command 2-7; 12-11
Label standard level 12-10
Labeled tape 12-7,13
LBC command 11-8
LCN (See Loosely coupled network)
LDI command 7-26
| LEN function 6-16
LENGTH command 7-27
Level number C-8
LI command J-20
LIB command 8-26
LIBEDIT command 15-3,17
LIBEDIT directives 15-20
LIBGEN command 15-32
Library 2-17; 15-1; C-8
Creation 15-17,34
Global library set 15-43
Maintenance 15-17,34
Processing examples 15-37
Program 14-5,8,14
S ys t em 1 5-4 3
User 15-33,34,43
LIBRARY command 15-43
Library directory
E n t r y p o i n t s 1 5 - 3 3
Extenal references 15-33
Library file 2-13; C-8
Library file type 2-11
Library maintenance 15-1
L i b r a r y r e c o r d t y p e 1 5 - 2 , 3
Library search order 15-44
L i b r a r y, u s e r 1 5 - 1 , 3 3
Structure 15-33
LIBRARY, user name 2-17
LID (See Logical identifier of mainframe)
LIMITS command 7-28
Line C-8
Length 16-3
Logical 16-3
Physical 16-3
LINE command 8-6.1
Line feed J-12,13; K-l
Line feed function 16-3
Line feed idles J-20
Line mode 8-6.1; C-8
Line numbers 8-3,39; 9-40,58
Line printer 1-4
Auto eject mode H-2
Carriage control characters H-2,3
Character sets 9-47; A-3
Paper size H-l
Print trains A-3
Punched tape loop H-4
533/536 9-48; A-4; H-l
580 H-l,4
5 8 5 9 - 4 8
Line printer carriage control H-l
Line sequence number 9-40
Line speed recognition J-5
Lines printed, record of 3-19
Lines printed, total 3-19
Linked host 7-36
LIST command 8-28,46
Listing record information 15-14
Listing tape labels 12-19
LISTLB command 12-19
LISTLID command 7-36
LIST80 command 9-26
Literal card input F-3
Literal string 5-3; 6-5
LK command J-20
Load/dump memory commands 3-13; 11-1
Load point C-8
Loader information 7-16
Loading
Binary data 11-8
Central memory 11-9
O c t a l l i n e s 11 - 8
Loading (also see CYBER Loader) Central
memory 1-6
LOC command 11-8
Local batch job 3-6.2
Local file 2-12; C-8
Creation 2-12,13
Local file name C-8
Local file name table (FTN) C-8
Local file type 2-11
LOCK command 9-26
Locked file C-8
X^^Sy
Index-8
■/e**^>\
60459680 H
![](asset-329.png)
/P&>S
/JfSV^
jflf?wtr*\
Lockout of messages J-20
Logical device 2-6; C-8
Logical identifier of mainframe (LID)
7-36; C-8
Logical line 16-3; K-l
Logical record C-8
Logical track 2-6
Login 3-2,5; 8-28; C-8
LOGIN command 8-28
Logout 3-4,5; 8-21,29; C-8
LOGOUT command 3-4; 8-29
Logout display 3-4; 8-20
Loopback 7-38
Loosely coupled network (LCN) C-8
L072 command 9-27
MA (See Monitor address)
MACHINE command 7-39
Machine identifier 3-19; 6-8.1; D-4
Macro C-8
M a gne t i c t a p e 1 - 4
ANSI labels 12-2,9
ANSI standard labeled 2-8,9
Assignment 12-1,5,21
Blank label 12-9
Block size 12-13
Block terminator 2-10
Checkpoint dump 13-2
Checkpoint file 12-8,14
Code set A-12
Command rules 12-2
Conversion mode for 9-track tapes 12-7,14
Copying 2-7
Creating files 12-5
Data formats 2-5,9; 1-1
Density 2-8; 7-54; 12-6,13
Density specification 12-2
Device type 12-6
Error processing 12-3
Error recovery 2-10
Expiration date 12-16
File accessability character 12-10,15
File positioning 12-11
File sequence number 12-15
F i l e s e t c o n fi g u r a t i o n s 2 - 8
Generation number 12-15
Generation version number 12-16
Label 2-8; 12-9,11; G-l
Label standard level 12-10
Label verification 12-11
Labeled 9-59,64; 12-7,13,21
Load point 12-2
Maximum block size 9-62
Multifile set 2-9; 12-11,15
Multivolume set 12-25
Noise block 9-62
N o i s e s i z e 1 2 - 8 , 1 4
Nonstandard labeled 2-8
Obsolete tape formats 1-1
O v e r w r i t i n g l a b e l s 1 2 - 11
Parity 2-7,8,10
P a r i t y E r r o r 1 2 - 3
P h y s i c a l fi l e s t r u c t u r e 2 - 5
Processing option 12-3
Recording mode 2-7
Section number 12-15
Set identifier 12-15
Tape mark 2-8
Trailer sequence 12-4
Unlabeled 9-4; 12-7,13
Unloading 12-5
Verification 12-11
Volume name 12-25
Write ring 12-4
7-track 2-7,8
9-track 2-7,8
Magnetic tape activity 3-18
Magnetic tape file 9-43
MAP (See Matrix Array Processor)
Mass storage C-9
M as s s t o ra g e a c ti v it y 3 -1 8 ; D -4
Mass storage, Alternate 2-15,16
Mass storage device 1-4; 2-15; N-l
Mass storage file 2-6
Master device C-9
Master user 14-11,12
Matrix Array Processor (MAP) 3-8
Resource usage 3-18
MAXFL (See Field length, maximum)
Memory)
MERGE file 14-16
Message Control System (MCS) 3-6
M es s age d el i m it e rs K - 2
Message lockout, operator J-20
Message to network operator J-21
Message transmission key J-12,13; K-l,2
MFL command 7-39
MFLINK
Directives 10-23
Interactive use 10-27
MFLINK command 3-6,6.1; 10-22
MFQUEUE
Directive prefix character 9-31
Routing directive 9-33
MFQUEUE command 3-6,6.1; 9-31
Microcomputer file transfers P-l
MODE command 6-22
Mode 4 terminals J-4
MODIFY command 14-5
MODIFY mode 10-8
MODIFY utility 14-8
MOVE command 8-48
MS command J-21
MSF (See Mass Storage Facility)
60459680 H Index-9
![](asset-32a.png)
Multifile file 2-3,4; C-9
Multifile set C-9
Multimainframe configuration
M33 teletype 16-1; J-25 1-3; 2-15
M35 teletype
M37 teletype
M38 teletype
M40 terminal
16-1; J-25
16-1; J-25
16-1; J-25
16-1; J-25
1-1; 7-38
J-10,21
1-5
NAM (See Network Access Method)
NAM/CCP network commands 8-26
NDL (See Network Definition Language)
Network 16-1; C-9; J-l
Applications 3-6; 7-32
Configurations 7-36
Processing modes 1-1
Network access device 1-5
Network Access Method (NAM)
Network control character
Network Definition Language (NDL)
Network operator (NOP) C-9
Network processing unit (NPU)
Network type 6-8.1
NEW command 9-34
NEWPL file 14-16
No abort option 10-3
No-auto-drop status (ND) 8-27; 9-56
.NOCLR directive 4-31
NOEXIT command 3-12; 5-7; 6-24
Noise C-9
Noise size 12-8,14
Nonallocatable device C-9
NOP (See Network operator)
NORERUN command 7-40
Normal mode 8-2,4,7; A-3; E-l
NORMAL mode 8-4; A-3
Normalized input mode J-18; K-l
NOS/VE dual-state system 3-6
NOSORT command 8-29
NOSTEXT file 14-4
NOTE command 7-40
.NOTE directive 4-31
NPC= entry point 5-2; 15-43
NULL command 8-15
Numeric string 6-5
NUM function 6-16
Object code C-9
OC command J-21
OFFSW command 7-41
OLD command 10-28
OLDPL file 14-17
ONEXIT command 5-7; 6-24
Online manuals 8-20.1,26
J-2,24
15-3,6,15
15-3,6,15
15-24,33
15-3,6,13
14-8
ONSW command 7-42
OP command J-21
Operand overflow error 6-23
Ope ra nds 6 -5
Operand underflow error 6-23
Operating system level 6-7
Operating system value 6-11
Operating system version D-2
O P L fi l e 1 4 - 4
OPL record type
OPLC record type
OPLD directory
OPLD record type
OPLEDIT command
O r i g i n t y p e C - 9
OUT command 9-35
Output
Cards punched 3-19
Data E-2
Device selection J-21
F l o w c o n t r o l J - 2 1
Lines printed 3-19
Listing identification 2-2
Print file code conversion A-3
Printed H-l
P ro c e ss i ng 2 -1 2 ; 7 - 62
Queued job 2-12
Remote batch 2-12
Suppression of headers 8-4
Suspension 16-5,7
OUTPUT file 2-11; 3-19; 7-68; 9-44,45
Output line
Aborting 16-5
Length 16-3
OVCAP record type 15-4
OVL record type 15-3
OVWRITE command 9-35
PA command J-22
PACK command 9-36
Pack name 10-3,29
Packet-switching network (PSN) 16-1; C-9
PACKNAM command 10-29
Page boundary 16-5
Page density 6-7
.PA G E dir ec ti v e 4-3 2
Page length 6-7; J-23
P a ge s i z e 6 - 7
Page wait 16-5; J-23
Page width 6-7; J-24
Panel compilation 14-10
Panel definition file 14-10
Panel, full screen C-9
PANELIB 8-36
Paper length, line printer H-l
Paper size, line printer H-l
^\
Index-10 60459680 H
![](asset-32b.png)
Paper tape
Control characters M-2
Corrections M-4
Input lines M-2
Operation M-l
Punch M-l
Punching off-line M-3
Punching online M-4
Reader M-l
Parameter C-9
K ey w o rd 5 -4
Order-dependent 5-4
Order-independent 5-4
Parity C-10
Magnetic tape 2-7,10
Parity processing J-22
Passive procedure 4-1; C-10; L-l
PASSWOR command 7-42
Password C-10
Batch 7-42
Changing 7-42
I n t e r a c t i v e 7 - 4 2
Pause bit 7-4,22,44
PAUSE command 7-44
PBC command 11-9
PDU command 14-10
PE tape density 7-54
Peripheral equipment 1-4,5
Peripheral processor library 5-5
Peripheral processor (PP) 1-4; C-10
Permanent file 2-13,14; 10-10,15,45,46;
C-10
P e r m a n e n t fi l e a c t i v i t y 3 - 1 8 ; D - 4
P erm a n en t fi le c a tal o g 2 - 12
Permanent file device C-10
P e r man e n t fi l e f a m i l y C - 1 0
Permit category 10-3
PERMIT command 10-30
Personal identifier 3-3,13
| PFC array, 580 line printer 9-48.2; H-l,6
PFC printer H-l
PFC (See Programmable format control)
PG command J-23
Physical line 16-3; K-l
Physical mainframe identifier (PID) 7-36
Physical record unit (PRU) 2-4; C-10; N-l
PID (See Physical identifier of mainframe)
PL command J-23
Plot disposition 2-11; 9-45
Post radix C-10
POST terminal J-l
PP record type 15-3
PP (See Peripheral processor)
PPU record type 15-3
Pr efi x ch ar act er, co mma nd 5- 2
$ Prefix, command 5-2
P r e fi x t a b l e 1 5 - 2 5
Prefix table, record 15-2,35
PRIMARY command 9-37
Primary file 2-13; C-10
Changing lines 8-42
Creation 9-34
Editing 8-1,39
Inserting lines 8-42
Line number overlap 8-41
T y p e 2 - 1 1
//PRIMARY value 4-14
Print density H-l,7
P r i n t d i s p o s i t i o n 2 - 11 ; 9 - 4 4
Print trains A-3
Printer carriage control H-l
Printing files 9-46
Priority, job 3-9
Priority, scheduling 3-7
Private auxiliary device C-10
Private file 10-3
.PROC directive 4-2
Interactive format 4-11
Menu format 4-22
PROC record type 15-3
Procedure C-10
Branching directives 4-38
Call 4-41
Checklist entries 4-13
Checklist patterns 4-14,15,16
Command record 4-4
Command section 4-3
Concatenation character 4-8
Data section 4-3,6,34.1
//DATA value 4-14
Default termination sequence 4-51
D i r e c t i v e s y n t a x 4 - 9
Directives 4-2
Expansion control directives 4-33
Expansion processing 4-4,8
File directives 4-34.1
File search order 4-42
//F IL E v alu e 4 -1 4
Formatting and Help directives 4-23
Formatting section 4-2
Help section 4-2
Inhibit character 4-6,7
Interactive help processing 4-25
I n t e r a cti v e p a r a m e t e r e n t r y 4 - 4
Interactive parameter format 4-12
Menu 4-22
Menu help processi ng 4-25
Nesting level 4-1,14; 6-9
Noninteractive 4-1; L-l
Order-dependent parameter processing
4-53
Order-independent parameter processing
4-53
Parameter matching modes 4-53; L-2
Parameter substitution L-2
Passive L-l
60459680 H Index-11
![](asset-32c.png)
/^Sfev
//PRIMARY value 4-14
Processing 4-3
Prologue (See Prologue)
Requesting help 4-46
Special parameter values 4-14
Structure 4-2
Termination 4-41,47,51
Procedure file C-ll
Residence 4-2
Search order 4-42
Procedure header directive 4-2
I n t e r a c t i v e f o r m a t 4 - 11
Interactive parameter format 4-12
Menu format 4-22
PROFILC file 14-11
PROFILE command 14-11
PROFILE directives 14-12
P ro g ra m l i br a ry 2-1 7 ; 1 4- 5 ,1 4
Programmable format control (PFC)
I 9-48.2; H-l
Project number 7-4
Project profile file 14-11
| Prologue 7-4,30,31,73; C-ll
Prologue, project C-ll
.PROMPT directive 4-32
PROTECT command 7-44
Protected command 3-13
PRU device C-ll
PRU (See Physical record unit)
PSN (See Packet-switching network)
Public auxiliary device C-ll
Public file 10-4
Punch disposition 2-11; 9-45
PUNCH file 2-11; 3-19; 9-45; F-5,6
PUNCHB file 2-11; 3-19; 9-45; 11-9; F-6
PURGALL command 10-31
PURGE command 10-32
PW command J-24
P8 file 2-11; 3-19; 9-45; F-7
QGET command 7-45
QTF (See Queued File Transfer Facility)
Queue priority C-ll
Q ue u e d fi l e 2 -11 ; 7 - 45 ; 9 -31 , 35, 4 4; C -l l
Queued File Transfer Facility (QTF) 3-6
Queued job output 2-12
QUEUE7 command 7-46
RA (See Reference address)
RAE (See Extended memory reference address)
Random access 15-1,2; C-ll
Random access directory 15-11,17
Random access file C-ll
RBF (See Remote Batch Facility)
RBR command 11-9
RC command J-24
READ command 8-49
READ mode 10-8.1
Read-only permission C-ll
READAP mode 10-8
READMD mode 10-8
READUP mode 10-8
Real-time clock 7-58
RECLAIM command 10-33
Database 10-33
Directive options 10-39
Directives 10-36
Output listing 10-44
Record C-ll
Checksum 15-6,15
Comments field 15-6,15
Copying 15-7
Creation date 15-6,15
File subdivision 2-3
Length 15-6,15
Name 15-15
P r e fi x t a b l e 1 5 - 2 , 2 5
S-type 15-1
Ty p e 2 - 3; 1 5 - 3 ,1 5 , 1 6
U-type 15-1
Record group identifier (GID) 15-21
R e c o r d s p l i t t i n g 9 - 9 , 1 0
Recording mode
Binary 2-7
Coded 2-7
RECORDING MODE IS BINARY statement, COBOL
2-7
RECORDING MODE IS CODED statement, COBOL
2-7
Records, relocatable 15-7
RECOVER command 8-30
Recoverable job 3-4; 8-30
Recoverable jobs 3-3
Recovery C-ll
Recovery processing 8-30,32
Reel number G-2
Reference address (RA) 1-2
Reference address (RA and RAE) C-ll
Reference record identifier (RID) 15-21
REL record type 15-3,6,15
Releasing file space 9-22
Releasing files 9-5,42,56,64
Relocatable records 15-7
Remote Batch Facility (RBF) 1-1; 3-1,6
Remote batch job 3-6.2; 9-50
Remote host 7-36; 9-31; C-12
Remote Host Facility (RHF) 7-38; C-12
Removable packs 7-57
RENAME command 9-37
REPLACE command 10-45
Replacing files 10-45
REQUEST command 9-38; 12-21
■/*s%
Index-12
,^^^\
60459680 H
![](asset-32d.png)
00^**-
RERUN command 7-50
RESEQ command 9-40
R es e r va t i on b loc k 2 - 7
I Reserved format channels H-9
RESOURC command 7-51,55
Resource demand 7-14,51,54,56; 9-42
Resource limits 7-29
Resource overcommitment 7-55
I Resource usage 7-16.1,59,64,67; D-4
Resource usage, record of 3-18
Restart 13-1,2
RESTART command 13-2
RETURN command 7-54; 9-42
REVERT command 4-41,51
REWIND command 9-43
Rewinding files 9-43
RFL command 7-40,57
RFL= entry point 15-43
RFL (See Running field length)
RID (See Reference record identifier)
Rolled out C-12
ROLLOUT command 7-58
Rollout control 3-12
ROUTE command 3-6,6.1; 9-44
Routing files 9-31,44
RTIME command 7-58
Rubout M-2
Rubout characters C-12
RUN command 8-35
Running field length (RFL) 3-9; 7-40
S tape format 2-7,9,10; 9-10; 12-2
S-type record 15-1
Satellite coupler 1-5
SAVE command 10-46
Scheduler 3-9; 7-58
Scheduling priority 2-12; 3-6.2,7,9; C-12
SCOPE 2 Operating System 3-7; 7-46; 8-22
SCOPE 2 Station Facility (SSF) 7-38
SCOPY command 9-51
Scratch files 2-1
SCREEN command 8-7
Screen formatting 8-36; 14-10
Screen mode 8-7; C-12
Scrolling mode 8-6.1
SDM= entry point 15-43
SE command J-24
SECHDR command 9-54
Secure login command 8-36
Secured mode 3-13
Secured system 9-55; 10-48,49; C-12
Security access categories 10-48
Security access level 7-33,61; 9-3,55;
10-2,49; C-l
Security administrator C-12
Security count C-12
Security features 3-13; 8-36; 9-54,55;
10-48,49
Security permissions 7-33
Security unlock status C-12
Semi-private file 10-4
Sense switch 6-12; 7-41,42,73
Separator, command 5-2
Sequence number C-12; G-4,8,9
Sequential access 15-1; C-12
Sequential (SQ) file C-12
S e r v i c e c l a s s 2 - 1 2 ; 3 - 6 . 2 , 7 ;
7-5,7,18,23,33; C-13; D-2
SET command 6-25
.SET directive 4-34
Set identification G-4,8,9
Set identifier 12-15
SETASL command 7-59
SETCORE command 7-60
SETFAL command 9-55
SETFS command 9-56
SETJAL command 7-61
SETJOB command 7-62
SETJSL command 7-64
SETPFAC command 10-48
SETPFAL command 10-49
SETPR command 7-64
SETTL command 7-64
SHELL command 7-66
SHELL permissions 7-32
Shell program 7-66
Short PRU C-13
SHOW command 8-36
SI format tapes 2-9,10; 9-10,59,64
SKIP command 6-30
SKIPEI command 9-56
SKIPF command 9-57
SKIPFB command 9-57
Skipping commands 6-16,17,18
SKIPR command 9-58
Software, system 1-5
SORT command 9-58
Sort flag 8-29
Sorting files 8-29; 9-40,58
Source code C-13
Special editing mode 8-2; C-13; J-24
SRU (See System resource unit)
Stack purging 7-39
Standard labeled tape C-13
STIME command 7-67
Store and forward 7-38
Storing files 10-45,46
STR function 6-16.1
STRB function 6-16.2
STRD function 6-16.3
String C-13
SUBMIT command 7-68
Directives 7-68
Transparent submit mode 7-68
60459680 H Index-13
![](asset-32e.png)
Submit file 7-68
Subsystem 6-7; 8-11; 10-5
Subsystem, default 8-15
Subsystem flag C-13
I Subsystem selection commands 8-1,11
SWITCH command 7-73
Symbolic names, Flow control command
I 6-7,25
Syn chronou s term in al o ut pu t 16 -5
SYSEDIT, SC directive 5-2
System access category set C-13
System access level C-13
System code G-4,8,9
System error codes 6-9,10
S y s t e m fi l e C - 1 3
SYSTEM File 10-16
System library 5-2; 10-16; 15-43
System monitor 1-3
System origin job 3-6.2
System prologue 7-30
System resource unit (SRU) 3-8;
7-59,64,67; C-13; D-4
Limit 3-11
Resource usage 3-18
I System resource usage 7-16.1
System resources, accounting of 3-8; 7-4
System security features 3-13; 8-36
System symbols, cross reference listing 14-4
System text 14-4
SYSTEXT file 14-5
TAF (See Transaction Facility)
Tape assignment 12-5,21
Tape density 7-54
Tape density identifier 7-54
Tape format C-13
Tape formats 2-7,9; 12-13; 1-1
Tape formats, obsolete 1-1
Tape management 12-1
Tape mark C-13
Tape marks 2-8; 12-2
Tape owner identification G-2
Tape (See also Magnetic tape)
Tape Verification Facility (TVF) 3-6
TA P E n fi l e 11 - 1 0
TC command J-2,25
TCOPY command 2-7; 9-59
TDU command 8-8.1
TDUMP command 9-62
Tek terminal J-l
Tektronix 4010/4014 terminal 16-1; J-25
Teletypewriter (TTY) 16-1; J-l
| Televideo terminals 8-6.2,8; 16-1
Temporary file C-13
Terminal
Categories J-4
Index-14
Character conversion E-l
Characteristics 8-9; J-l
Classes 16-1; J-l,24,25
Control 16-9
Definition commands 16-2
Display of characteristics J-8
Input/output conventions 16-2
Name C-13
Output 16-5
Session 3-3
Te r m i n a l a t t r i b u t e s 8 - 9
Terminal character set-mode 6-6
Terminal characteristics 3-5; J-l
Terminal characteristics, CCP default J-2
Terminal characteristics, NDL default
J-2,24
Terminal classes J-l
Terminal control commands 8-2
Terminal definition commands 16-4; J-l
Terminal definition file 8-6.1,7,8.1
Terminal display mode 6-8.1 |
Te r m i n a l i d e n t i fi e r ( T I D ) 2 - 1 2
Terminal messages 7-40
Terminal output
Asynchronous 16-5
Synchronous 16-5
Term in at in g a h ost-t er mi na l co nn ec tion J -2 6
Terminating input lines 16-3
Te r min a ti o n c h ara c ter 1 6- 6 ; J - 8
Termination sequence 16-4,6; C-14; J-8
Terminator, command 5-2,3
TERMLIB 8-6.1,7,8.1
TEXT command 8-37
Text editor facility 14-1
Te x t e d i t o r s 1 4 - 1 , 1 8
Text mode 8-37
TEXT record type 15-3
TID (See Terminal identifier)
Time of the week 6-7
Time slice C-14
Timed/Event rollout C-14
TIMEOUT command 8-9
Timeout period 3-5
Timeout status 8-9
TM command J-26
T r a c k s 2 - 7
Transaction Facility (TAF) 1-1; 3-6
Transferring files between mainframes
9-31,49,50; 10-22
Transmission key K-l
Transmitting input K-l
Transparent input mode C-14; J-l1,18,27;
K-l
Transparent submit mode 7-68,70; C-14
TRMDEF command 8-9; 16-2; J-2
TTY (See Teletypewriter)
TVF (See Tape verification facility)
Type of network 6-8.1 |
60459680 H
S**^$K
/•**™^\
![](asset-32f.png)
/^^V
U-type record 15-1
UCF record type 15-4
UCLP (See Output, Lines printed)
UCLV (See Output, Lines printed)
UCPC (See Output, Cards punched)
UEAC (See Application, Job usage)
UEAD (See Adder activity)
UECP (See Accumulated central processor time)
UEMS (See Mass storage activity)
UEMT (See Magnetic tape activity)
UEPF (See Permanent file activity)
UHLa G-ll
UHLa label G-l
UJN (See User job name)
ULIB command 15-34
ULIB directory 15-32,33
ULIB record type 15-3,6
Unlabeled tape 12-7,13
UNLOAD command 7-54; 9-64
UNLOCK command 9-65
UPDATE command 14-14
UPDATE mode 10-8
UPL record type 15 -15
UPLx record type 15-4
UPROC command 7-73
US code A-3
USECPU command 7-74
User break processing 16-4
User break 1 16-6; C-14; J-6,7
User break 2 16-6; C-14; J-8
USER command 7-74
User header label G-l
User index 7-30; C-14
User index hash 3-8; 7-14; C-14; D-2
User job name (UJN) 3-8; 7-18,23,62;
C-14; D-2
User label G-ll
User library 2-17; 15-1,32,33,34,43
User name 2-14; C-14
User name, alternate 10-5
User name LIBRARY 8-22,26
User number C-14
Us er permissions 7 -3 1
User program 1-5
User prologue (See Prologue)
User trailer label G-l
User validation 3-8; 7-28,74
User validation limits 7-5
User volume label G-l
Using XMODEM P-l
U T t e r m i n a l J - l
UTLa G-ll
UTLa label G-l
U V L a G - l l
UVLa label G-l
Validation file C-14
Validation limits 7-28
VERIFY command 9-65
Verifying files 9-65; 15-35
VFU load procedure H-2,4.2 |
VFYLIB command 15-3,35
Volume C-14
Volume accessibility character, tape 12-10.1 |
Volume header label G-l,2
Vo l u m e s e r i a l n u m b e r ( V S N ) 1 2 - 1 ,6, 11 , 2 5 ; |
C-15; G-2
V0L1 label 2-8,9; 12-1,9; G-l,2
VSN command 12-25
VSN (See Volume serial number)
VSOS (See Virtual Storage Operating System)
Wait disposition 2-11,12; 9-45
Wait-if-busy option 10-6
WBR command 11-10
Weekday 6-7
WHATJSN command 8-37
WHILE command 6-31
Word C-15
WRITE command 8-51
Write interlock 2-15; 9-26,65; C-15
WRITE mode 10-8.1
W r i t e r i n g C - 1 5
WRITEF command 9-68
WRITEN command 8-52
WRITER command 9-68
X command 8-38
X format 1-3
X format tapes 9-59,64
X.25 Public data network 7-36,38
X . 2 5 t e r m i n a l s J - 4
XEDIT command 14-18
XL command J-27
XMODEM command 8-38; P-l
X3.64 terminal J-l
YANK status 15-6,15
Zero byte terminator C-15
Zero length PRU C-15
ZZ ZDUM P fil e 3- 12; 11-5 ,6 ,7
ZZZZDMB file 11-1,3
ZZZZTRM 8-6.1,7
ZZZZZLD file 13-1
ZZZZZxx files 13-1
60459680 H Index-15
![](asset-330.png)
026 punch code A-3; F-3
029 punch code A-3; F-3
200 User Terminal 16-1; J-25
2741 terminal, ATTN key 16-8
5/7/9 multipunch F-3,5
533/536 printer 9-48; A-4; H-l,2,4
580 line printer
Carriage control array H-7
Format controls H-l
PFC array H-l
Spacing code 9-48.2
5 8 5 l i n e p r i n t e r 9 - 4 8 ; H - l , 2
5870 Non Impact Printer 9-44; H-l
6-bit display code 8-2; 9-23
6/12-bit display code 8-2; 9-23
6/7/8 /9 m ultip un ch 2- 6; C -1 5; F- 2
6/7/9 multipunch 2-6; C-15; F-2
6PP record type
63-character set
64-character set
7-bit ASCII code
7/8/9 multipunch
7/9 multipunch
7PP record type
15-4
A-l
A-l
9-23; A-l
2-6; 3-1; C-15; F-2
F-5
15-4
77 table (see Prefix table, record) 15-2
7700 table (see Prefix table, record) 15-2
9-54,55; 10-48,49
9 5 - c h a r a c t e r s e t A - l
/"^^?\
Index-16 60459680 H
![](asset-331.png)
MANUAL TITLE:
PUBLICATION NO.
NAME:
COMMENT SHEET
Control Data NOS Version 2 Reference Set,
Volume 3, System Commands
60459680 REVISION:
/ f P ^ \
COMPANY:
STREET ADDRESS:
CITY: .STATE: ZIP CODE:
This form i$ net intended to be used as an order blank. Control Data Corporation welcomes your evaluation of
this manual. Please indicate any errors, suggested additions or deletions, or general comments below (please
include page number references).
D Please Reply D No Reply Necessary
NO POSTAGE STAMP NECESSARY IF MAILED IN U.S.A.
FOLD ON DOTTED LINES AND TAPE
![](asset-332.png)
FOLD
BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO 8241 MINNEAPOLIS. MN
POSTAGE WILL BE PAID BY ADDRESSEE
CONTRpL DATA
Technology and Publications Division
ARH219
4201 North Lexington Avenue
Saint Paul, MN 55126-6198
FOLD
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
FOLD FOLD