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
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
REVISION RECORD
REVISION
(04-26-82)
B
(01-27-83)
(10-11-83)
(10-05-84)
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.
T h i s m a n u a l r e fl e c t s N O S 2 . 2 a t P S R l e v e l 5 9 6 . T h i s r e v i s i o n i n c o r p o r a t e s t h e f o l l o w i n g f e a t u 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
s t a t i o n ; a n d t h e I n t e r a c t i v e Tr a n s f e r F a c i l i t y ( I T F ) . B e c a u s e o f e x t e n s i v e c h a n g e s t o t h i s m a n u a l ,
change bars and dots are not used. This revision obsoletes all previous editions.
T h i s m a n u a l r e fl e c t s N O S 2 . 3 a t P S R l e v e l 6 1 7 . T h i s r e v i s i o n i n c o r p o r a t e s t h e f o l l o w i n g f e a t u r e s :
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
(03-28-85)
(12-16-85)
(09-30-86)
H
(04-23-87)
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
t e r m i n a l d e fi n i t i o n c o m m a n d , a n d t h e f o l l o w i n g f e a t u r e s : s u p p o r t o f C Y B E R 1 8 0 m o d e l 9 9 0 ; s u p p o r t o f
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.
T h i s m a n u a l r e fl e c t s N O S 2 . 5 . 2 a t P S R l e v e l 6 7 8 . T h i s r e v i s i o n d o c u m e n t s s u p p o r t f o r t h e Te l e v i d e o
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.
Publication No.
60459680
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
Te c h n o l o g y a n d P u b l i c a t i o n s D i v i s i o n
4201 North Lexington Avenue
Saint Paul, MN 55126-6198
or use Comment Sheet in the back of
this manual.
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
3
4
5/6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
1-1
1-2
1-3
1-4
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
60459680 H
HH
HH
H
H
H-
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
H.
H-
4-6
4-7
4-8
HEHG'
H-
4-9
4-10
4-11
4-12
4-13
4-14
4-15
4-16
HH-
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-26
4-27
4-28
4-29
4-30
4-31
4-32
4-33
4-34
4-34.1
4-34.2
4-35
4-36
4-37
4-38
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-14
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-18
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-46
7-47
7-48
7-49
7-50
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
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
REV
PAGE
8-35
8-36
8-37
8-38
8-39
8-40
8-41
8-42
8-43
8-44
8-45
8-46
8-47
8-48
8-49
8-50
8-51
8-52
9-1
9-2
9-3
9-4
9-5
9-6
9-7
9-8
9-9
9-10
9 - 11
9-12
9-13
9-14
9-15
9-16
9-17
9-18
9-19
9-20
9-21
9-22
9-23
9-24
9-25
9-26
9-27
9-28
9-29
9-30
9-31
9-32
9-33
9-34
9-35
9-36
9-37
9-38
9-39
9-40
9-41
9-42
9-43
9-44
9-45
9-46
9-47
9-48
9-48.1
9-48.2
9-49
9-50
9-51
REV
F.
PAGE
9-52
9-53
9-54
9-55
9-56
9-57
9-58
9-59
9-60
9-61
9-62
9-63
9-64
9-65
9-66
9-67
9-68
10-1
10-2
10-3
10-4
10-4.1/10-4.2
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
10-26
10-27
10-28
10-29
10-30
10-31
10-32
10-33
10-34
10-35
10-36
10-37
10-38
10-38.1
10-38.2
10-39
10-40
10-41
10-42
10-43
10-44
10-44.1/
10-44.2
10-45
10-46
REV
D.
H.
H-
HH-
D.
H'
H-
H-
H-
H•
PAGE
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 - 1 0
12-1
12-2
12-3
12-4
12-5
12-6
12-7
12-8
12-9
12-10
12-10.1/
12-10.2
1 2 - 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
12-22
12-23
12-24
12-25
12-26
13-1
13-2
13-3
13-4
14-1
14-2
14-3
14-4
14-5
14-6
14-7
14-8
14-9
14-10
14-11
14-12
14-13
14-14
14-15
14-16
14-17
14-18
14-19
15-1
15-2
15-3
15-4
REV
H-
PAGE
15-5
15-6
15-7
15-8
15-9
15-10
1 5 - 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
16-1
16-2
16-3
16-4
16-5
16-6
16-7
16-8
16-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
REV
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
PAGE
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
REV
PAGE
J-17
J-18
J-19
J-20
J-21
J-22
J-23
J-24
J-25
J-26
J-27
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
N-2
0-1
0-2
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
REV
PAGE
REV
PAGE
REV
PAGE
HHH-
HH-
J$$0&\
60459680 H
5/6
/^%
PREFACE
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
^^s
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.
4$$$!\
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
fi l e s . O t h e r t o p i c s c o v e r e d i n c l u d e p h y s i c a l t e r m i n a l c o n n e c t i o n , a n d l o g i n / l o g o u t
procedures.
Volume 2, Guide to System Usage, describes the general concepts of NOS and some of the
u t i l i t i e s u s e d w i t h N O S . To p i c s 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
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
St.
Paul,
Avenue
MN
North
5 5 11 2
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
From other countries: (612) 851-4131
The preceding numbers are for help on product usage. Address questions about physical
pac k a g i n g a n d /o r d i s tr i b u ti o n o f p r i n te d 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
^^
"^
/pifev
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
/p*V
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
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
t e r m i n a t o r.
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
c a r r i a g e t o t h e fi r s t c h a r a c t e r p o si ti o n o n th e n e xt l i n e .
• ■•—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
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
Publication Number
APEX IV Reference Manual
84002550
APL Version 2 Reference Manual
60454000
APT IV Version 2 Reference Manual
17326900
BASIC Version 3 Reference Manual
19983900
CDCNET Conceptual Overview
60461540
CDCNET Terminal Interface Usage Manual
60463850
COBOL Version 5 Reference Manual
60497100
Common Memory Manager Version 1 Reference Manual
60499200
COMPASS Version 3 Reference Manual
60492600
Conversion Aids System Version 2 Reference Manual
19265358
CYBER Database Control System 2 Database Administrator
Reference Manual
60485200
CYBER Database Control System Version 2 Application
Programming Reference Manual
60485300
CYBER Interactive Debug Version 1 Reference Manual
60481400
CYBER Loader Version 1 Reference Manual
60429800
60459680 H
11 I
Control Data Publication
I 12
Publication Number
CYBER Record Manager Advanced Access Methods Version 2
Reference Manual
60499300
CYBER Record Manager Basic Access Methods Version 1.5
Reference Manual
60495700
CYBER 70 Model 71 Computer System Hardware Reference Manual
60453300
CYBER 70 Model 72 Computer System Hardware Reference Manual
60347000
CYBER 70 Model 73 Computer System Hardware Reference Manual
60347200
CYBER 70 Model 74 Computer System Hardware Reference Manual
60347400
CYBER 170 Computer Systems Models 171 through 175
(Levels A, B, C) Model 176 (Level A) Hardware Reference Manual
60420000
CYBER 170 Computer Systems Models 720, 730, 740, 750, and 760,
Model 176 (Level B/C) Hardware Reference Manual
60456100
CYBER 170 Computer System Model 825
Hardware Reference Manual
60469350
CYBER 170 Computer Systems Models 835, 845, and 855
Hardware Reference Manual
60469290
CYBER 170 Computer Systems Models 865 and 875
Hardware Reference Manual
60458920
Data Base Utilities Version 1 Reference Manual
60498800
Data Catalogue 2 Reference Manual
60483200
DDL Version 3 Reference Manual, Volume 1
60481900
DDL Version 3 Reference Manual, Volume 2
60482000
DDL Version 3 Reference Manual, Volume 3
60482100
FORM Version 1 Reference Manual
60496200
FORTRAN Common Library Mathematical Routines Reference Manual
60498200
FORTRAN Data Base Facility Version 1 Reference Manual
60482200
FORTRAN Extended Version 4 Reference Manual
60497800
FORTRAN Extended Version 4 to FORTRAN Version 5 Conversion
Aids Program Version 1 Reference Manual
60483000
FORTRAN Version 5 Common Library Mathematical Routines
Reference Manual
60483100
FORTRAN Version 5 Reference Manual
60481300
General Purpose Simulation System V (GPSS)
General Information Manual
84003900
60459680 H
Control Data Publication
Publication Number
Information Management Facility Version 1 Application
Programming Reference Manual
60484500
Message Control System Version 1 Reference Manual
60480300
Modify Version 1 Reference Manual
60450100
Network Access Method Version 1/Communications Control
Program Version 3 Terminal Interfaces Reference Manual
60480600
Network Access Method Version 1
Host Application Programming Reference Manual
60499500
Network Access Method Version 1 Network
Definition Language Reference Manual
60480000
NOS Full Screen Editor User's Guide
60460420
NOS Version 2 Administration Handbook
60459840
NOS Version 2 Application Installation Handbook
84002760
NOS Version 2 Applications Programmer's Instant
60459360
NOS Version 2 Diagnostic Index
60459390
NOS Version 2 Installation Handbook
60459320
NOS Version 2 Network Terminal User's Instant
60459380
NOS Version 2 Operator/Analyst Handbook
60459310
NOS Version 2 Reference Set, Volume 1,
Introduction to Interactive Usage
60459660
NOS Version 2 Reference Set, Volume 2, Guide to System Usage
60459670
NOS Version 2 Reference Set, Volume 4, Program Interface
60459690
NOS Version 2 Security Administrator's Handbook
60460410
NOS Version 2 System Maintenance Reference Manual
60459300
NOS Version 2 System Overview
60459270
NOS Version 2 Systems Programmer's Instant
60459370
NOS Version 2 Tape Management System (TMS) User Reference Manual
60463110
On-Line Maintenance Software Reference Manual
60454200
Pascal Version 1.1 Reference Manual
60497700
PERT/Time Version 2 Reference Manual
60456030
Query Update Version 3 Reference Manual
60498300
60459680 H
13
Control Data Publication
Publication Number
Remote Batch Facility Version 1 Reference Manual
60499600
Remote Host Facility Access Method Reference Manual
60459990
Remote Host Facility Usage
60460620
SORT/MERGE Version 5 Reference Manual
60484800
SYMPL Version 1 Reference Manual
60496400
TAF/CRM Data Manager Version 1 Reference Manual
60459510
TAF Version 1 Reference Manual
60459500
TAF Version 1 User's Guide
60459520
Text Editor Version 1 Reference Manual
60436100
TOTAL-CDC Version 2 Reference Manual
76070300
Update Version 1 Reference Manual
60449900
XEDIT Version 3 Reference Manual
60455730
5870 Printer User's Reference Manual
60462720
6000 Series Computer Systems Hardware Reference Manual
60100000
8-Bit Subroutines Reference Manual
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
CONTENTS
/0$£\
0l^f\
1. SYSTEM DESCRIPTION
1-1
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
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. FILES
2-1
File Names
File Structure
CYBER Record Manager File Structure
NOS File Structure
Physical File Structure
Card Files
Mass Storage Files
Magnetic Tape Files
File Types
Input Files
Queued Files
Local Files
Primary Files
Direct Access Files
Library Files
Permanent Files
Indirect Access Permanent Files
Direct Access Permanent Files
Mass Storage File Residence
Family Devices
Au xi l i a ry D e vi ce s
Alternate Storage Subsystems
Libraries
User Name Library
Program Libraries
User Libraries
2-1
2-1
2-3
2-3
2-4
2-6
2-6
2-7
3. JOB FLOW AND EXECUTION
3-1
J o b I n i t i a t i o n a n d Te r m i n a t i o n
3-1
60459680 H
2-11
2-11
2-11
2-12
2-13
2-13
2-13
2-13
2-14
2-14
2-15
2-15
2-16
2-16
2-17
2-17
2-17
2-17
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
Va l i d a t i o n
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
S e c u r i t y C o n fl i c t P r o c e s s i n g 3 - 1 7
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
. E X PA N D
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
Va l u e s
4-14
15 |
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
. PA G E
Directive
4-32
.PROMPT
Directive
4-32
Expansion Control Directives 4-33
.CC
Directive
4-33
. E X PA N D
Directive
4-33
.IC
Directive
4-33
.SET
Directive
4-34
File
Directives
4-34.1
. D ATA
Directive
4-34.1
.EOF (or .EOP) Directive 4-38
.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
Command
Command
Exit
PROCESSING
5-1
Format
Processing
Flow
Processing
5-2
5-5
5-7
6. FLOW CONTROL COMMANDS 6-1
Command
Syntax
Operators
Arithmetic
Operators
Relational
Operators
Logical
Operators
String
Operators
Order
of
Evaluation
Operands
Constants
Numeric
Strings
Literals
Symbolic
Names
Functions
6-2
6-2
6-2
6-3
6-4
6-4
6-5
6-5
6-5
6-5
6-5
6-7
6-12
FILE
Function
DT
Function
LEN
Function
NUM
Function
STR
Function
STRB
Function
STRD
Function
Command
Descriptions
BEGIN
Command
D I S P L AY
Command
ELSE
Command
ENDIF
Command
ENDW
Command
EXIT
Command
IF
(or
IFE)
Command
MODE
Command
NOEXIT
Command
ONEXIT
Command
REVERT
Command
SET
Command
SKIP
Command
WHILE
Command
6-12
6-14
6-16
6-16
6-16.1
6-16.2
6-16.3
6-16.3
6-16.3
6-16.4
6-17
6-18
6-19
6-19
6-20
6-22
6-24
6-24
6-24
6-25
6-30
6-31
7. JOB CONTROL COMMANDS 7-1
BLOCK
Command
7-2
CFO
Command
7-3
CHARGE
Command
7-4
C H VA L
Command
7-5
CLASS
Command
7-7
COMMENT
Command
7-9
CTIME
Command
7-10
D AY F I L E
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
MACHINE
Command
MFL
Command
NORERUN
Command
NOTE
Command
OFFSW
Command
ONSW
Command
PA S S W O R
Command
PA U S E
Command
PROTECT
Command
QGET
Command
QUEUE7
Command
RERUN
Command
RESOURC
Command
Deadlock
Prevention
Single
Resource
Use
Ta p e
Units
Resource Overcommitment
Altering Resource Requirements
Unit
Assignment
RFL
Command
ROLLOUT
Command
RTIME
Command
S E TA S L
Command
SETCORE
Command
SETJAL
Command
SETJOB
Command
SETJSL
Command
SETPR
Command
SETTL
Command
SHELL
Command
STIME
Command
SUBMIT
Command
SWITCH
Command
UPROC
Command
USECPU
Command
USER
Command
7-39
7-39
7-40
7-40
7-41
7-42
7-42
7-44
7-44
7-45
7-46
7-50
7-50
7-52
7-54
7-54
7-55
7-56
7-57
7-57
7-58
7-58
7-59
7-60
7-61
7-62
7-63
7-64
7-64
7-66
7-67
7-68
7-73
7-73
7-74
7-74
8. COMMANDS FOR INTERACTIVE JOBS 8-1
Te r m i n a l
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
S u b s y s t e m S e l e c t i o n C o m m a n d s 8 - 11
ACCESS
Command
8-12
60459680 H
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
8-12
8-13
8-13
8-14
8-15
8-15
8-16
8-16
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. FILE MANAGEMENT COMMANDS
9-1
ASSIGN Command
BKSP Command
9-2
9-4
8-17
17
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
10. PERMANENT FILE COMMANDS
Common Parameters
APPEND Command
ATTACH Command
CATLIST Command
CHANGE Command
COMMON Command
18
9-5
9-5
9-10
9-10
9-10
9-11
9-12
9-13
9-15
9-16
9-17
9-18
9-20
9-22
9-23
9-26
9-26
9-27
9-31
9-31
9-33
9-34
9-35
9-35
9-36
9-37
9-37
9-38
9-40
9-42
9-43
9-44
9-44
9-50
9-51
9-54
9-55
9-56
9-56
9-57
9-57
9-58
9-58
9-59
9-62
9-64
9-65
9-65
9-68
9-68
DEFINE Command
GET Command
DROPDS Command
MFLINK Command
MFLINK Directives
APPEND Directive
ATTACH Directive
CHANGE Directive
CHARGE Directive
DEFINE Directive
DROPDS Directive
GET Directive
PACKNAM Directive
PERMIT Directive
PURGE Directive
REPLACE Directive
SAVE Directive
USER Directive
Interactive Use of MFLINK
OLD Command
PACKNAM Command
PERMIT Command
PURGALL Command
PURGE Command
RECLAIM Command
Magnetic Tapes
Command Format
RECLAIM Output
REPLACE Command
SAVE Command
SETPFAC Command
SETPFAL Command
10-17
10-20
10-21
10-22
10-23
10-24
10-24
10-24
10-25
10-25
10-25
10-25
10-25
10-26
10-26
10-26
10-26
10-26
10-27
10-28
10-29
10-30
10-31
10-32
10-33
10-34
10-35
10-44
10-45
10-46
10-48
10-49
11. LOAD/DUMP MEMORY COMMANDS
11-1
DMB Command
DMD Command
DMDECS Command
DMP Command
DMPECS Command
LBC Command
LOC Command
PBC Command
RBR Command
WBR Command
11-1
11-5
11-6
11-6.1
11-7
11-8
11-8
11-9
11-9
11-10
12. TAPE MANAGEMENT
12-1
Tape Assignment
10-1 Command Rules
Processing Options
10-2 ASSIGN Command
10-7 BLANK Command
10-7 LABEL Command
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
13.
C H E C K P O I N T / R E S TA RT
CKP
R E S TA RT
Command
Command
13-1
13-1
13-2
14. SYSTEM UTILITY COMMANDS 14-1
EDIT
FSE
KRONREF
MODIFY
OPLEDIT
PDU
PROFILE
U P D AT E
XEDIT
15.
Command
Command
Command
Command
Command
Command
Command
Command
Command
LIBRARY
MAINTENANCE
14-1
14-2
14-4
14-5
14-8
14-10
1 4 - 11
14-14
14-18
15-1
Library File Access Methods 15-1
Library
Record
Types
15-2
C ATA L O G
Command
15-5
COPYL and COPYLM Commands 15-7
GTR
Command
1 5 - 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
D AT E
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
NEW
Directive
NOINS
Directive
NOREP
Directive
NOREW
Directive
OLD
Directive
RENAME
Directive
REPLACE
Directive
REWIND
Directive
TYPE or NAME Directive
VFYLIB
Directive
LIBEDIT
Output
LIBGEN
Command
ULIB
Command
VFYLIB
Command
Library Processing Examples
LIBRARY
Command
Maximum Size of Global Library
Set
Library
Search
Order
Examples
15-28
15-28
15-28
15-29
15-29
15-29
15-29
15-30
15-30
15-31
15-31
15-31
15-32
15-34
15-35
15-37
15-43
15-43
15-44
15-44
16. TERMINAL INPUT/OUTPUT 16-1
Te r m i n a l s
16-1
Input/Output
Conventions
16-2
Input
From
Te r m i n a l
16-2
Length of Output/Input Lines 16-3
Te r m i n a t i n g
Input
Line
16-3
Correcting
Input
Line
16-3
Deleting
Input
Line
16-4
Entering Input Before Prompts 16-4
Page
Wait
16-5
Suspending
Output
16-5
Aborting
Output
Block
16-5
Interrupting
Job
Step
16-6
Te r m i n a t i n g
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
A-l
Character Set Anomalies
Character Set Tables
Interactive Jobs
Batch Jobs
Jobs Using Line Printers
Jobs Using Magnetic Tape:
A-2
A-2
A-3
A-3
A-3
A-l 2
B. DIAGNOSTIC MESSAGES
B-l
C. GLOSSARY
60459680 E
C-l
D. SAMPLE JOB OUTPUT
TERMINAL CHARACTER CONVERSION
D-l
E-l
Data Input
Data Output
E-l
E-2
F. CARD FILE DATA CONVERSION
F-l
Input Card File Formats
Coded Cards
Conversion Modes
F-2
F-3
F-3
19
/^s^\
Literal Input
Binary Cards
Summary
Punch File Formats
Coded Cards (Punch)
Binary Cards (Punch B)
Absolute Binary Cards (P8)
F-3
F-5
F-5
F-5
F-6
F-6
F-7
(AR) - Automatic Character
(AR)
R
e
Recognition
(BF) - Blocking Factor
(BF)
Break Key as User Break 1
(BR)
(BS)
Backspace Character
(Bl)
Interruption or
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 SingleMessage Transparent Input Mode
(EB) - End-of-Block Character
(EL) - End-of-Line Character
(EP) - Echoplex Mode
(FA) - Full-ASCII Input Mode
(HC) - Host Connection
(HD) - Display of Host Nodes
(HN) - Host Node Selection
(HS) - 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 TerminalHost Connection
(XL) - Multimessage Transparent
Mode
G . A N S I TA P E L A B E L F O R M AT S G - l
Required
Labels
G-l
V O L 1 - Vo l u m e H e a d e r L a b e l 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
|
I
|
I
Printed
Data
Paper
Length
580
Line
Printers
533/536
and
585
Printers
Carriage
Control
Format Channel Selection on
Non-PFC
Printers
Format Channel Selection on
533/536
Printers
Carriage
Control
Arrays
Array
Syntax
H-4.2
H-7
H-7
e rp vl e d
ER xeas m
H-9
I.
Format
O B S O L E T E TA P E
Channels
F O R M AT S
B
(Blocked)
Format
E
(Line
Image)
Format
X
(External)
Format
E n d - o f - Ta p e / E n d - o f - R e e l C o n d i t i o n s
J. NAM/CCP TERMINAL DEFINITION
COMMANDS
Introduction
Te r m i n a l D e fi n i t i o n C o m m a n d F o r m a t
Restrictions
T e r m i n a l D e fi n i t i o n C o m m a n d s
(AB) - Abort Output Block
Character
20
H-l
H-l
H-l
H-2
H-2
H-4.2
1-1
1-1
1-2
1-3
1-3
J-l
J-l
J-3
J-4
J-4
K.
DELIMITING AND TRANSMITTING
TERMINAL INPUT
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
Physical End-of-Line (Line Feed)
Logical End-of-Line (Carriage Return)
Message Transmission
K-l
K-l
K-l
J-5
60459680 H
jgg^N.
L. PASSIVE PROCEDURES
.PROC
Directive
Procedure and Parameter Descriptions
Parameter
Matching
Order-Dependent Parameter
Matching
Mode
Order-Independent Parameter
Matching
Mode
L-l
0. INTERACTIVE TRANSFER FACILITY (ITF) 0-1
L-l
L-2
L-2
L-2
L-6
0-2
0-2
P. FILE TRANSFERS USING XMODEM
P-l
General Description
Te l e t y p e w r i t e r
Control Characters
Input Lines
Punching Tape Off-Line
Tape Mode
Punching a Tape On-Line
Cor r ec t io n s
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 C o n fi g u r a t i o n F i l e
M-2 File Transfer Notes
M-3
Te x t
Files
M-3
CYBER
Binary
M-4
Micro
Binary
M-4 Limitations and Considerations
N. MASS STORAGE DEVICE STATISTICS
N-l
M. PAPER TAPE OPERATIONS
0-1
0-1
Selecting the ITF Application
Selecting a Remote CYBER 200 System
Processing Your Job on the
Remote CYBER 200
Terminating Your ITF Session
P-l
P-3
P-3
P-4
P-4
P-6
P-6
P-6
P-6
P-7
INDEX
FIGURES
1-1
2-1
2-2
2-3
2-4
3-1
3-2
4-1
4-2
4-3
4-4
4-5
5-1
7-1
Central Memory Allocation
Logical Structure of Files
NOS and CRM File Terminology
Sample Card File Structure
Use of ANSI Labels
FORTRAN Compile and Execute Deck
Submitting Jobs to Remote Hosts
Procedure File Structure
TESTPN with Valid Entry
TESTPN with Invalid Entry
Summary of Checklist Entries
Calling a Procedure
Command Processing Flow
QUEUE7 Execute Queue Sample
Listing
7-2 QUEUE7 Input Queue Sample Listing
7-3 QUEUE7 Output Queue Sample Listing
1-3
2-2
2-3
2-6
2-8
3-2
3-6.1
4-3
4-5
4-5
4-15
4-41
7-4
15-1
15-2
15-3
15-4
F-l
H-l
H-2
5-6
L-l
7-47
7-48
7-49
L-2
Resource Commitment Processing
( S i m p l i fi e d )
7-53
Random Access File Structure 15-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
0^\
V
60459680 G
21
TABLES
2-1 Physical File Structure on
D i ff e r e n t D e v i c e s
2-2 Data Representation on
Magnetic Tape
3-1 User Job Access Levels
4-1 Procedure Directives
4 - 2 Programmable Function Keys for
Procedures
4 - 3 Help on Procedure Calls
9-1 Range of Permissible Formats
for the COPY Command
9-2 Code Set-Line Terminator
Reference Chart
9-3 Compatible File Structures for
the VERIFY Command
10-1 Access Mode Granted When
Attaching a Currently Attached
Direct Access File
A - l Character Sets for Interactive
Jobs
A-2 Character Sets for Batch Jobs
A-3
2-5
A-4
2-7
3-15
4-10
A-5
A-6
4-25
4-48
H-l
9-6
H-2
9-24
J-l
J-2
9-67
K-l
10-10
L-l
A-5
A-7
L-2
ASCII to 6/12-Bit Display Code
Conversion
Nine-Track ASCII Coded Tape
Conversion
Nine-Track EBCDIC Coded Tape
Conversion
Seven-Track Coded Tape
Conversions
Carriage Control Characters for
512/580 and 5870 Printers
Carriage Control Characters for
585
Printers
D e f a u l t T e r m i n a l D e fi n i t i o n s
Parameter Ranges for Terminal
D e fi n i t i o n
Commands
Default Message Delimiters
and Transmission Keys
Parameter Substitution in
Order-Dependent Mode
Parameter Substitution in
Order-Independent Mode
A-10
A-l3
A-l4
A-l5
H-3
H-4
J-28
J-29
K-2
L-4
L-8
'*^^S\
22
60459680 H
SYSTEM DESCRIPTION
NOS is capable of several concurrent processing modes. The following are the processing
modes available.
• Local batch.
• Remote batch.
• Transaction.
/ff^x
• 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),
Tr a n s a c t i o n F a c i l i t y ( TA F ) , a n d I n t e r a c t i v e F a c i l i t y ( I A F ) .
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).
Pe ri p h e ra l p ro ce sso rs.
Peripheral equipment.
0^^.
60459680
E
1-1
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 r e f e r e n c e t o a n a d d r e s s o u t s i d e t h e j o b ' s fi e l d l e n g t h r a n g e c a u s e s a h a r d w a r e e r r o r /
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
t i m e i s s i m i l a r.
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
CENTRAL
MEMORY
CENTRAL
MEMORY
RESIDENT
ABSOLUTE
ADDRESS
REFERENCE
ADDRESS (p)
RA
RA + p
0*£p\
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
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
N E T W O R K O P E R AT I N G S Y S T E M N O S 2
FAMILY: ,usernam,passwrd,iaf
YOUR PASSWORD WILL BE EXPIRED YY/MM/DD
JSN: ADYE, NAMIAF
RECOVERABLE JOBCS)
JSN
UJN
S TAT U S
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:
GOODBYE or BYE or LOGOUT
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
The following is a description of the variable items in the logout display:
Item
Description
username User name you entered during login.
h h . m m . s s . T h e fi r s t o c c u r r e n c e o f h h . m m . s s . i n d i c a t e s t h e t i m e o f
logout. The second occurrence indicates the length of time
your terminal was connected to IAF.
jsn
Yo u r
job
sequence
name.
s . s s s A m e a s u r e o f t h e s y s t e m r e s o u r c e s u s e d w h i l e c o n n e c t e d t o I A F.
xxxxxxxx A count of the total number of input and output characters read
from, or written to, your terminal.
ct
The
had
The
network
host
control character for your terminal. (The network
c o n t r o l c h a r a c t e r f o r s p e c i fi c t e r m i n a l m o d e l s a r e l i s t e d i n
Ta b l e J - l . )
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.
jpffiv
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
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
w h i c h y o u s u b m i t j o b s t o a r e m o t e h o s t d e p e n d o n y o u r s y s t e m c o n fi g u r a t i o n , t h e t y p e o f >
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
fi l e
must
be
written
in
6/12-bit
display
code.
/
3-6
60459680 G
JOB ORIGIN TYPES
When a job enters the system, the system determines the job origin type according to the
m e a n s u s e d f o r j o b i n i t i a t i o n . I t s o r i g i n i d e n t i fi c a t i o n r e m a i n s w i t h t h e j o b t h r o u g h o u t
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
System
Symbol
SYO
Interactive
Local
batch
Remote
batch
IAO
BCO
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's
class
job's
job in the
scheduling
assignment
origin type
system is assigned a service class. This service class determines the
priority as the job flows through the system. You can make this service
or you can let the system assign it a default service class based on the
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
60459680 F
Two-character
Mnemonic
Deadstart
DS
System
SY
Local batch
BC
Remote batch
RB
Interactive
TS
Detached interactive
DI
Network supervisor
NS
Subsystem
SS
Maintenance
MA
One-character
Mnemonic
A
3-6.1/3-6.2
Figure 3-2 summarizes the methods of submitting jobs to remote hosts.
Type of Job Being Submitted
Command/Application
Special Host Type/
Connection Type
Job Command
(ST=lid parameter)
ROUTE Command
(ST=lid parameter)
Batch
No special
requirements.
HELL07 Command
Batch (with interactive I/O)
SCOPE 2 system.
MFQUEUE Command
Batch (with special routing requirements)
RHF (LCN, CDCNET,
or CCP).
ITF Application
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
JOB ORIGIN TYPES
When a job enters the system, the system determines the job origin type according to the
m e a n s u s e d f o r j o b i n i t i a t i o n . I t s o r i g i n i d e n t i fi c a t i o n r e m a i n s w i t h t h e j o b t h r o u g h o u t
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 se c t i o n 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's
class
job's
job in the system is assigned a service class. This service class determines the
scheduling priority as the job flows through the system. You can make this service
assignment or you can let the system assign it a default service class based on the
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:
Two-character
Mnemonic
One-- c h a r a c t e r
Mnemonic
Deadstart
DS
A
System
SY
Local batch
BC
Remote batch
RB
Interactive
TS
Detached interactive
DI
Network supervisor
NS
Subsystem
SS
Maintenance
MA
Service Class
| 3-6.2
60459680
#R*^
Service
Class
Communication
Two-character
Mnemonic
task
One-character
Mnemonic
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
ascertain how your site has prioritized the service classes
each origin type by using the CLASS command. To determine
the ENQUIRE command. The system denotes the service class
the SC field of the ENQUIRE output.
is site-determined. You can
you are authorized to use for
the service class of a job, use
with a one-character mnemonic in
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
i n c l u d e s n o t o n l y y o u r j o b fi l e , b u t fi l e s y o u e x p l i c i t l y r o u t e f o r d i s p o s a l d u r i n g y o u r
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
characters.
appears as
appendix D
assigns every job a unique JSN. Each JSN consists of four alphabetic
The banner page of batch output prominently displays the job's JSN: the JSN
the last four characters of the eight characters in block letters (refer to
for a sample banner page).
y ^ V
#^N
60459680
D
3-7
, / fl S s ^ 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
*
*
^
^
0eas,
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
priority jobs are being serviced. This action may include rolling out low priority jobs or
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.
T h e r u n n i n g fi e l d l e n g t h ( R F L ) i s i n i t i a l l y s e t t o z e r o , i n d i c a t i n g s y s t e m c o n t r o l o f fi e l d
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).
I
60459680 C
3-9
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
l e n g t h f o r C M o n l y. To s e t t h e i n i t i a l
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.
MAXFL
MFL
RFL
Field
Length
JOB,CM60000.
USER,USERABC,1234.
60000
60000
60000
60000
0
0
3200
3200
The CM parameter sets
the MAXFL and MFL
values. The system
s e t s t h e fi e l d l e n g t h
as required for pro
cessing the command.
GET,ABSPROG,RELPROG.
60000
60000
2500
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
40000 The absolute program
on file ABSPROG is
executed within a
40000-word field
length.
MFL,50000.
60000
60000 40000
2300 The user issues an
MFL command to set
the maximum field
length for the follow
ing relocatable load.
RELPROG.
60000
50000
50000 If more than a 50000w o r d fi e l d l e n g t h i s
required, the job
aborts.
Command
3-10
Explanation
60459680 C
INPUT RLE CONTROL
B a t c h j o b s , w h e n i n i t i a t e d , h a v e a fi l e n a m e d I N P U T ( i n p u t fi l e t y p e ) . T h i s fi l e c o n t a i n s
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
e x e c u t i o n t e r m i n a t e s o r e n t e r s 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 ^ rthe
S ™ SETJOB
* t h e / y scommand.
5 e m s u s PYou
e n d cannot
s o r t eresume
r m i n a t ejobs
s t h suspended
e j o b a c c oinr dthis
i n g fashion
t o t h e from
param
e t epoint
r v a lof
ues
ot
the
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
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
o p e r a t o r. T h e j o b ' s p r i o r i t y i n c r e a s e s w h i l e t h e j o b w a i t s . N o r m a l l y, a l l o t h e r f a c t o r s
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
secti o n 6 ) . Th e d e fa u l t e r r o r e x i t m o d e 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.
T*&&!\
3-12
60459680 C
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
APPEND
ASSIGN
ATTACH
BEGIN
BLANK
CATALOG
CATLIST
CHANGE
CHARGE
CHVAL
CLASS
CLEAR
COPY
COPYBF
COPYBR
COPYCF
COPYCR
COPYEI
COPYSBF
COPYX
DAYFILE
DEFINE
DISPLAY
EDIT
ELSE
ENDIF
ENDW
ENQUIRE
EXECUTEt
IF or (IFE)
LABEL
LDSET
LIBEDIT
LIBLOAD
LIBTASK
LIMITS
LOAD
FSE
GET
OVWRITE
PACKNAM
MAP
MFLINK
MFQUEUE
NEW
OLD
OUT
SECHDR
PASSWOR
PERMIT
PROFILE
PURGE
RECOVER
REDUCE
REPLACE
REQUEST
RESOURC
RESTART
RETURN
REVERT
REWIND
SATISFY
SAVE
SCOPY
SET
SETFS
SKIP
SORT
SUBMIT
TCOPY
UNLOAD
UPROC
USER
VERIFY
VFYLIB
VSN
WHILE
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
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
m u s t b e v a l i d a t e d f o r t h e f i l e ' s s e c u r i t y a c c e s s l e v e l a n d f o r a l l o f t h e f i l e ' s a c c e s s ■a S ^ \
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
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
l e v e l o f y o u r fi l e s . H o w e v e r, t h e a c c e s s l e v e l o f d i r e c t a c c e s s fi l e s o r t a p e fi l e s c a n n o t
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
i n f o r m a t i o n t o i t i f y o u h a v e s p e c i a l a u t h o r i z a t i o n . T h e a c c e s s l e v e l o f a l o c a l fi l e i s
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
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
t h e fi l e s .
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
t h e fi l e s .
RESPONSIBILITIES FOR DATA SECURITY
In a secured system, security access levels and
accesses a file, begins a job, or attempts to
job. This ensures that only those persons who
categories you have assigned to your files can
continuous protection of your data.
categories are checked whenever a user
alter the security parameters of a file or
are validated for the access levels and
access them. A secured system thus provides
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.
/^^v
|
3_i6
60459680
G
• 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 for
a c cthe
e s saccess
o n e olevel
f you
p e r m a ncategory
e n t fi l e ssetf r of
o m the
a jfile.
ob that is not validated
orr access
• 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
3. All equipment assigned to the job is released.
4 . A l l l i b r a r y fi l e s a t t a c h e d t o t h e j o b a r e r e l e a s e d .
5 . A l l s c r a t c h ( l o c a l ) fi l e s p a c e u s e d b y t h e j o b i s r e l e a s e d .
6. All direct access permanent files attached to the job are released; the status
i n f o r m a t i o n f o r t h e s e fi l e s i s u p d a t e d .
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
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.
m i M a c h i n e i d e n t i fi e r .
es Equipment status table (EST) ordinal of the output device.
^ ^ T h e U C LV s u m m a t i o n i s i s s u e d i f t h e V c a r r i a g e c o n t r o l c h a r a c t e r w a s u s e d
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
0X*\
0^*\
PROCEDURES
A NOS procedure is
performs a specific
file as a procedure
additional procedure
a sequence of NOS commands, residing in a separate record or file, that
task or sequence of tasks. A procedure header directive identifies the
file, and a number of other procedure directives allow you to control
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
( d i r e c t o r i n d i r e c t a c c e s s ) , o r f r o m a l o c a l o r g l o b a l l i b r a r y s e t . Yo u r s i t e m a y a l s o
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
d i ff e r fr o m t h e n o n i n t e r a c t i v e f o rma t (d e scri b e d i n Ap p e n d i x L ) i n th a t th e i n te r a cti ve
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.
r*
60459680
D
4-i
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
in this section.
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.
T h e fi r s t l i n e o r l i n e s o f a p r o c e d u r e i s t h e p r o c e d u r e h e a d e r , w h i c h c o n s i s t s o f a s i n g l e " c a ^ \
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
,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
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
p ri ma ri l y th e co mma n d s re stri cte d to entry from interactive terminals (refer to se ction 8).
yf^*N
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
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
s y s t e m d e f a u l t h e l p t e x t , i f a n y , f o l l o w e d b y p r o c e d u r e - d e fi n e d h e l p t e x t . ]
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
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.
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
/0^^\
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/
R E V E RT, N 0 L I S T.
D a y fi L e :
testpn,888
INVALID PROJECT NUMBER
/ d a y fi L e , f r = t e s t p n , o p = 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
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
p ro ce d u re . In se rti n g a .EXPAN D ,OFF d i re cti ve su sp e n d s d i re cti ve p ro ce ssi n g a n d p a ra me te r ^ ^
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
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
i^SN
60459680
D
4-7
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.
10.31.01. STOP
10.31.01. 5600 FINAL EXECUTION FL.
10.31.01 0.000 CP SECONDS EXECUTION TIME.
10.31.01.
C O M M E N T.
T E S T,
1 0 . 3 1 . 0 1 . S R E V E R T. C C L
I,
TESTI,
II.
"^
'
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
character set).
Usage
rules
for
the
concatenation
character
are:
• Expansion processing removes all concatenation characters from the procedure file
except those included in a $-deliraited literal string and those preceded by a #
c h a r a c t e r.
• 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.
b e g i n , l i n k , fi l e l , s u f fi x = s b f , l f n l = p l a n , l f n 2 = s c h e m e .
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
>*s«^k
b e g i n , l i n k , fi l e l , s u f fi x = e i , l f n l = m a z e , I f n 2 = t a x e s .
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.
jst^\.
• 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
/*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
Procedure header
.PROC
Specifies the procedure name, defines parameters, and
enables parameter prompting.
Formatting
.CORRECT
.PROMPT
Specifies the prompt to follow an incorrect parameter
e n t r y.
Specifies the prompt to appear before a parameter entry
is made.
Specifies a label for programmable function key Fn.
Inhibits the automatic clearing of the screen while the
procedure executes.
Specifies a message to appear on the screen while the
procedure executes.
Specifies the string to precede the page number on the
screen.
Specifies the text for the general request for input.
Help
.ENDHELP
.HELP
Marks the end of the help section of the procedure.
Specifies help text for the procedure or a parameter.
Expansion
Control
.CC
Specifies the concatenation character to be used in the
procedure body.
Terminates skipping initiated by a matching .IF or
initiates skipping until a matching .ENDIF is found.
Terminates skipping initiated by a matching .IF or
.ELSE.
Submits a single command to the system for immediate
execution.
Terminates or restores procedure expansion for
subsequent lines of the procedure.
Allows conditional expansion of the procedure body.
Specifies the inhibit character to be used in the
procedure body.
.ENTER
.Fn
.NOCLR
.NOTE
.PAGE
.ELSE
.ENDIF
.EX
.EXPAND
.IF
.IC
File
.DATA
.EOF
.EOR
Comment
4-10
Function
.*
C r e a t e s a l o c a l fi l e .
Inserts an end-of-file mark in a (.DATA) file created
by the procedure or in the procedure command record.
Inserts an end-of-record mark in a (.DATA) file created
by the procedure or in the procedure command record.
Identifies comments in the procedure.
60459680 F
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
can
the
with
.PROC directive must be the first line of the procedure and must begin in column 1. It
be continued on one or more succeeding lines by ending the continued line, or beginning
continuation line, with a non-blank separator character. The .PROC directive must end
a period (.).
In this section we describe the interactive and menu formats of the .PROC directive,
noninteractive format is described in Appendix L.
The
Interactive Format
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.
/jP^N
• Supplies descriptions for each parameter to be used in prompting the procedure
c a l l e r.
Format:
.PROC,pname*I"title",pi,p2,...,pn.ck.
Parameter
Description
pname
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.
title
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
4 8 0 b i t s . T h e t i t l e fi e l d c a n b e n u l l ( " " ) o r o m i t t e d . I f o m i t t e d ,
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
Parameter
Description
P i S p e c i fi e s o p t i o n a l p a r a m e t e r s . T h e m a x i m u m n u m b e r o f p a r a m e t e r s i s
50. Each parameter p^^ has the following form:
keywrd"descriptionl,=( checklist)
or
keywrd'description'=(checklist)
k e y w r d S p e c i fi e s t h e k e y w o r d o f t h e p a r a m e t e r, k e y w r d
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
c h e c k l i s t . T h i s v a l u e i s s p e c i fi e d b y a
parameter on the procedure call or by default
a c c o r d i n g t o c h e c k l i s t s p e c i fi c a t i o n s . 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.
d e s c r i p t i o n S p e c i fi e s a n o p t i o n a l t e x t s t r i n g t h a t t h e s y s t e m
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
t h e p r o c e d u r e i s a l o c a l fi l e .
4-12
60459680 H
Parameter
Description
c h e c k l i s t S p e c i fi e s a l i s t o f t h e a c c e p t a b l e v a l u e s a n d
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
fi r s t m a t c h d e t e r m i n e s t h e s u b s t i t u t i o n .
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.
c k S p e c i fi e s a 1 - t o 1 0 - c h a r a c t e r c o m m e n t k e y w o r d . T h e k e y w o r d m u s t b e
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:
pstring
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
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
4-14
S i g n i fi c a n c e
#DATA
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.
#FILE
S p e c i fi e s t h e fi l e c o n t a i n i n g t h i s p r o c e d u r e .
//PRIMARY
S p e c i fi e s t h e p r i m a r y fi l e .
60459680 H
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
Description
Allows entry of any character string up to 40 characters. The
string replaces keyword.
Entry of character string causes a null substitution.
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.
S p e c i fi e s t h a t t h e p a r a m e t e r i s o p t i o n a l . N o s u b s t i t u t i o n
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 Any alphabetic characters
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.
*Sm..n(chars )=t
or
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
Checklist Patterns
Checklist Pattern
*Am..n=value
*Am..n=
*Am..n
Description
S p e c i fi e s t h e s u b s t i t u t i o n f o r k e y w r d r e g a r d l e s s o f t h e s p e c i fi c a
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
d i r e c t i v e ( r e f e r t o . D ATA D i r e c t i v e f o r t h e n a m e o f t h i s fi l e ) . I f
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
c u r r e n t p r i m a r y fi l e .
If *Am..n= is in the checklist, a null value replaces keywrd. 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.
*Fm..n=value
*Fm..n=
*Fm..n
4-16
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.
60459680 H
/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
d i r e c t i v e ( r e f e r t o . D ATA D i r e c t i v e f o r t h e n a m e o f t h i s fi l e ) . I f
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
c u r r e n t p r i m a r y fi l e .
If *Fm..n= is in the checklist, a null value replaces keywrd. 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.
EXEC is called:
EXEC,I=CARDS,L=PRINT.
The procedure body becomes:
FTN5,I=CARDS,B=LG0,L=0UTPUT.
*K=value
*K=
*K
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
c h a r a c t e r s f o r v a l u e . Yo u m u s t d e l i m i t s p e c i a l c h a r a c t e r s , o t h e r
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
d i r e c t i v e ( r e f e r t o . D ATA D i r e c t i v e f o r t h e n a m e o f t h i s fi l e ) . I f
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
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
=
C O M M E N T.
#P1=P1,
(*K),P2=(*K=X),P3=(*K=0.
#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
/^p^\
Checklist Pattern
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
*N=value
*N=
*N
*D=value
*D=
*N
Specifies the substitution for keywrd when there is no parameter
entry for p^ on the procedure call. If *Ns=value or *D=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.
Yo u m u s t d e l i m i t s p e c i a l c h a r a c t e r s , o t h e r t h a n a s t e r i s k s ( * ) , w i t h
dollar
signs.
|
I
I
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
d i r e c t i v e ( r e f e r t o . D ATA D i r e c t i v e f o r t h e n a m e o f t h i s fi l e ) . I f
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
c u r r e n t p r i m a r y fi l e .
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
If no format of the *N or *D entry is in the checklist, p. is a |
required parameter and interactive prompting occurs when it is
omitted from the procedure call. Specifying some form of the *N or ■
* D e n t r y m o r e t h a n o n c e i n a s i n g l e c h e c k l i s t i s a n e r r o r. |
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
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
o r c h a r a c t e r s r e p r e s e n t e d b y k . m . . n s p e c i fi e s t h e m i n i m u m a n d
*Sm..n/k=value maximum values for the length of the string entered on the
*Sm..n/k= procedure call. The default for m is 1 and for n is 40. The
*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
A
B
D
AB
AD
Characters
All alphabetic characters
All
octal
characters
All decimal characters
All alphabetic and octal characters
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
s t r i n g o f 0 t o 4 0 u p p e r c a s e c h a r a c t e r s f o r v a l u e . Yo u m u s t d e l i m i t < > ^ \
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
d i r e c t i v e ( r e f e r t o . D ATA D i r e c t i v e f o r t h e n a m e o f t h i s fi l e ) . I f
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
c u r r e n t p r i m a r y fi l e .
■■^*K
4-20
60459680 H
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
0*%
Checklist
Pattern
Description
I f * S m . . 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:
r
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.
jt$$bz\
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
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
d i r e c t i v e ( r e f e r t o . D ATA D i r e c t i v e f o r t h e n a m e o f t h i s fi l e ) . I f
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.
If
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.
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
Format:
.PROC,pname*M"title",keywrd=(selections).ck.
Parameter
Description
pname
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.
title
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
4 8 0 b i t s . T h e t i t l e fi e l d c a n b e n u l l ( " " ) o r c o m p l e t e l y o m i t t e d . I f
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.
keywrd
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.
selections
Defines the menu selections. A maximum of 50 selections can be
defined for a menu. The definitions must have the following format:
0^U\
num^Hdescript|",...,numn"descriptn"
n u m * D e fi n e s a n i n t e g e r n u m b e r t h a t i d e n t i fi e s t h e m e n u
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
s p e c i f y a n u l l d e s c r i p t i o n ( " " ) o r o m i t t h i s fi e l d .
This description appears whenever the system displays
the menu.
ck
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
A menu has the following format:
title
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 ^s y s t e m u s e s a d e f a u l t p r o m p t a s j u s t s h o w n . A d d i t i o n a l l y, t h e s y s t e m c e n t e r s a l l l i n e s w h e n ^ 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
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
T h i s d i r e c t i v e s p e c i fi e s t h e t e x t fi e l d .
Format:
.CORRECT,text.
.CORRECT=text.
Parameter
text
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
t r u n c a t i o n w i t h a n e l l i p s i s ( n o t r u n c a t i o n o c c u r s i n l i n e m o d e ) . Yo u c a n s u p p r e s s d i s p l a y |
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
■*"«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:
text
parameter description
T h i s d i r e c t i v e s p e c i fi e s t h e t e x t fi e l d .
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.
'*^S\
4-24
60459680 H
.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
Table 4-2. Programmable Function Keys for Procedures
Default Label
Key
Function
Fl
FWD
Pages forward through screens of parameters or menu
selections.
F2
BKW
Pages backward through screens of parameters or menu
selections.
F3
HELP FWD
Pages forward through screens of .HELP text.
F4
HELP BKW
Pages backward through screens of .HELP text.
F5
HELP
Displays .HELP text at the bottom of the screen.
F6
QUIT
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
P r o c e d u r e C a l l s l a t e r i n t h i s s e c t i o n . I f s p e c i fi e d , . H E L P d i r e c t i v e s m u s t i m m e d i a t e l y
precede the .ENDHELP directive.
Formats:
0&>\
.HELP.
.HELP,,NOLIST.
.HELP,parm.
.HELP,parm,NOLIST.
Parameter
Description
NOLIST
Suppresses the display of some of the .HELP text during help
p ro c e s s i n g .
parm
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.
■g^S\
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
>*^\
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 p ro mpt fo r a va l u e . Th e p ro mpt includes the descriptive string specified with the
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.
• T h e c u r r e n t v a l u e , i f a n y, o f t h e p a r a m e t e r.
•
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
/^**
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),
r D C ' D I S P O S I T.HELP.
I O N C O D E " = ( * N = L P, L P, P R , L R , L S , L T ) .
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 I L E ( F, . N O T. L O ) , P F.
GET,F.
.ELSE,PF.
r
R E W.ENDIF,PF.
I N D , F.
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
P RBEGIN,PRINT,PRINT?
I N T, ?
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?
r
60459680
H
4~27
The following is a sample of the dialogue generated by the .PROC and .HELP directives:
/begin,pri nt,print?
T h i s p r o c e d u r e r o u t e s a p e r m a n e n t fi l e t o t h e s e l e c t e d l i n e p r i n t e r .
PARAMETERS FOR PRINT ARE F, DC
ENTER F FILE NAME? ?
ALLOWABLE VALUE(S)
MUST BE A FILE NAME
T h e n a m e o f t h e p e r m a n e n t fi l e t o b e r o u t e d .
E N T E R F F I L E N A M E ? d a t a fi l
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?
T h i s p r o c e d u r e r o u t e s a p e r m a n e n t fi l e t o t h e s e l e c t e d l i n e p r i n t e r .
PARAMETERS FOR PRINT ARE F, DC
FILE NAME? ?
ALLOWABLE VALUE(S)
MUST BE A FILE NAME
T h e n a m e o f t h e p e r m a n e n t fi l e t o b e r o u t e d .
F I L E N A M E ? d a t a fi l
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
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
F FILE NAME:
DC DISPOSITION CODE:
yjpfet.
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
Specify values and press NEXT when ready
F FILE NAME
ALLOWABLE VALUE (S)
MUST BE A FILE NAME
The name of the permanent file to be routed.
F5 |HELP 1 F6 JQUIT
JsPN
60459680 H
4-29
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
F6 QUIT
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
.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
m e s s a g e S p e c i fi e s a 1 - t o 4 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. 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
m e s s a g e S p e c i fi e s a 1 - t o 4 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 s c r e e n
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
.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
text
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
text
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
^|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 S p e c i fi e s t h e n e w c o n c a t e n a t i o n c h a r a c t e r.
.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
-
Parameter
^
Description
ON
Specifies that subsequent lines of the procedure will be expanded
n o r m a l l y. T h i s i s t h e d e f a u l t v a l u e .
OFF
S p e c i fi e s t h a t n o p a r a m e t e r s u b s t i t u t i o n s o r d i r e c t i v e p r o c e s s i n g w i l l
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
e ff e c t u n t i l t h e p r o c e d u r e t e r m i n a t e s o r u n t i l y o u e n t e r a n o t h e r . I C d i r e c t i v e . T h e d e f a u l t
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
S p e c i fi e s t h e n e w i n h i b i t c h a r a c t e r.
.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
Description
keywd^
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.
s t rexp^
May be any valid CCL expression, usually but not necessarily an
expression which produces a string result. If the result of
s t r e x p j ^ i s n o t a s t r i n g b u t a v a l u e , t h e v a l u e i s l e f t - j u s t i fi e d
and considered a string. The resulting string in either case is
substituted for any occurrences of keywd^ in subsequent
statements of the procedure.
.'J-S5!Ni
4-34
60459680 H
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
T h e fi l e d i r e c t i v e s e i t h e r c r e a t e l o c a l fi l e s d u r i n g p r o c e d u r e e x p a n s i o n t i m e o r p l a c e fi l e
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:
. D ATA , l f n .
j0JHfeS
60459680
H
4-34.Ii
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
w r i t t e n . I f a fi l e n a m e d l f n i s a l r e a d y a s s i g n e d t o t h e j o b , i t i s
returned, and new local file lfn is created. You cannot specify INPUT
f o r l f n . I f l f n i s n o t s p e c i fi e d , t h e . D ATA fi l e c a n b e r e f e r e n c e d i n
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
d i r e c t i v e t o c o n d i t i o n a l l y i n c l u d e l i n e s i n t h e d a t a fi l e .
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:
• A n o t h e r . D ATA d i r e c t i v e .
• A n e n d - o f - r e c o r d ( n o t a n . E O R d irective) 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.
A f t e r t h e d a t a fi l e i s w r i t t e n , i t i s r e w o u n d .
4-34.2
60459680
H
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 0 0 F I N A L E X E C U T I 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
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.
-EORPROGRAM 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 . 0 8 . 3 7 . S T O P
11 . 0 8 . 3 7 . 5 6 0 0 F I N A L E X E C U T I O N F L .
11.08.37. 0.000 CP SECONDS EXECUTION TIME.
11.08.37.REPLACE,FTN0UT
11.08.37.$REVERT.CCL
4-36
60459680 E
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 . 0 6 . 5 1 . S T O P
11 . 0 6 . 5 1 . 5 6 0 0 F I N A L E X E C U T I O 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
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:
I
.EOF.
. 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 interchangeably
.EOR directive with
is valid
only directive.
after a .DATA directive. The .EOS directive
may be used
the .EOR
Format:
.EOR.
|
/*^\
)
.EOS.
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
.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
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
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:
0^
60459680
H
4-40.1/4-40.2
|
*%
*%
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.
Procedure
.PR0C,APR0C*I,
BEGIN, APROC'
REVERT.
Interactive Command
Procedure
.PR0C,BPR0C*I.
Procedure
.PR0C,CPR0C*I.
BEGIN,BPROC
BEGIN, CPROC
REVERT.
REVERT.
Figure 4-5. Calling a Procedure
60459680 D
4-41
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:
B E G I N , p n a m e , p fi l e , p j , p 2 , . . . , p n . c o m m e n t
or
- p n a m e , p fi l e , p i , p 2 , . . . , p n . c o m m e n t
or
pname,pj,p2,...,pn.comment
or
p fi l e , p i , p 2 , . . . , p n . c o m m e n t
The first format is the full BEGIN command format that can be used in either batch or
a t t e m p t i njobs.
g t o When
l o c a t e you
fi l e use
p fi l ethis
:
(interactive
format, the system uses the following search order when
• 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
a s t h e fi r s t f o r m a t .
The third and fourth formats are the name call formats in which the command name BEGIN can
be omitted.
4
42
60459680
E
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.
fi l e . T h e s y s t e m e x e c u t e s t h e fi r s t p r o c e d u r e o n p fi l e .
Parameter
pfile is the name of a local
Description
p n a m e S p e c i fi e s t h e p r o c e d u r e n a m e f r o m t h e p r o c e d u r e h e a d e r d i r e c t i v e . I f p n a m e
is omitted from the first format, two consecutive commas must be specified.
T h e d e f a u l t p r o c e d u r e i s t h e r e c o r d a t t h e c u r r e n t p o s i t i o n o f p fi l e . I f
pfile is at its end-of-information, the system rewinds pfile and uses the
fi r s t p r o c e d u r e o n p fi l e . I f p fi l e i s I N P U T, t h e fi l e i s n o t r e w o u n d .
p fi l e S p e c i fi e s t h e n a m e o f t h e fi l e c o n t a i n i n g t h e p r o c e d u r e . T h e fi l e n a m e
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.
00^\
I f p fi l e i s o m i t t e d f r o m t h e fi r s t f o r m a t , t h e i n s t a l l a t i o n - d e fi n e d d e f a u l t
file name is used (PROCFIL is the default).
P i S p e c i fi e s a n o p t i o n a l p a r a m e t e r t h a t m a y a f f e c t t h e s u b s t i t u t i o n t o b e m a d e
for a keyword used in the procedure. The value you specify is compared to
the appropriate checklist specified for this parameter in the procedure
h e a d e r. T h e c h e c k l i s t e n t r i e s a r e c h e c k e d i n a l e f t - t o - r i g h t f a s h i o n a n d
the first match determines the substitution. Refer to the .PROC Directive
i n t h i s s e c t i o n f o r m o r e d e t a i l s o n p a r a m e t e r s u b s t i t u t i o n . T h e s p e c i fi c
formats for p^ are described later in this subsection.
/j^N
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
For interactive procedures (*I), optional parameters p^ can have the following formats:
Pi
Description
k e y w r d S p e c i fi e s a p a r a m e t e r i d e n tical to a keyword on the procedure header.
Substitution is controlled by the *K entry in the checklist for the
parameter.
k e y w r d ? S p e c i fi e s i n t e r a c t i v e B E G I N p r o c e s s i n g ( r e f e r t o R e q u e s t i n g H e l p o n
or Procedure Calls later in this section).
1
keywrd= Removes keywrd in the procedure body (null substitution) unless overridden
b y a c h e c k l i s t s p e c i fi c a t i o n .
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
/0SS*\
Pi
Description
v a l U n l e s s o v e r r i d d e n b y a c h e c k l i s t s p e c i fi c a t i o n , a s s i g n s t h i s 0 - t o
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
Meaning
val
Substitutes the string val itself.
val+
Substitutes the decimal value associated with val.
val+D
Substitutes the decimal value associated with val,
val+B
Substitutes the octal value associated with val.
NOTE
If you specify a parameter p^ on a name
c a l l t o a l o c a l fi l e , n e i t h e r t h e k e y w o r d
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
c h o i c e S p e c i fi e s a m e n u s e l e ction that appears on the procedure header. The menu
selection must be an unsigned integer.
c h o i c e ? S p e c i fi e s i n t e r a c t i v e h e l p p r o c e s s i n g ( r e f e r t o R e q u e s t i n g H e l p o n P r o c e d u r e
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 job.
.PR0C,TEST1*I,FK.
COMMENT. FK
60459680 H
4-45
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,*.
1 0 . 1 5 . 3 5 . C O M M E N T. *
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:
• R e q u e s t h e l p i n f o r m a t i o n a b o u t 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
• 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 ^ " • Yo u r t e r m i n a l i s i n l i n e m o d e a n d y o u e n t e r t h e t e r m i n a t i o n o r i n t e r r u p t i o n
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.
r
As 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 parameterprompting dialogue. Still, the comment must follow a terminator (refer to the last example
in this subsection).
0$^>\
60459680
E
4-47
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
Re s u i t
Procedure Call
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
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
s p e c i fi c a t i o n s a r e i n e r r o r, e r r o r m e s s a g e s a p p e a r i n t h e d a y fi l e . I n e i t h e r c a s e , t h e
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
^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
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
procedure and
command had
procedure. The
to appear in
the command record of the calling
executes the command com as if the
actually appeared in the calling
EX parameter causes the REVERT command
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
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.
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
REVJOB1 attaches an
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.
4-52
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
60459680 H
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
n o n f a t a l e r r o r.
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
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 = O U T P U T, * 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.
Ar€Stj^>^
4-54
60459680
H
COMMAND PROCESSING
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
j o b fi l e . I n i n t e r a c t i v e j o b s , y o u e n t e r t h e c o m m a n d s d i r e c t l y a t t h e t e r m i n a l . T h i s
section describes command processing and how the commands affect other aspects of job
pr oc es s in g .
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.
Global Library File Commands
These commands call programs or procedures on
files that have been specified in a LIBRARY
command.
System Commands
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
Library utility commands
Loader commands*
Product Set 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.
tRefer to the CYBER Loader Reference Manual.
60459680 D
5-1
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
L I S T,
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
fi l e
EXTRACT
is
a
local
fi l e
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.
T h e t h i r d fi e l d
performed. The
valid terminator
are present). In
(optional)
parameter
character
interactive
c o n t a i n s p a r a m e t e r s w h i c h f u r t h e r d e fi n e t h e o p e r a t i o n t o b e ^ .
field is set off from the name field by a separator character. A "*^\
must follow the third field (or the second field if no parameters '
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
L I B E D I T , a n d t h e l i k e ) r e a d t h i s c o m m e n t s fi e l d f o r d i r e c t i v e s . '
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
Operating System Format
1 . Va l i d s e p a r a t o r s a r e
+
-"/
=
,(
Product Set Format
1. Same as for the operating system
format.
and any other character with a display
code value greater than 44g except
* ) $ . and blank.
2 . Va l i d t e r m i n a t o r s a r e
. )
0^\
2. Same as for the operating system
format.
3. Letters, numbers, and the * are
the only characters allowed in the
p a r a m e t e r fi e l d . T h e o n e e x c e p t i o n
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.
3. Same as for the operating system
format.
4. All embedded blanks within a command
e x c e p t t h o s e a p p e a r i n g i n l i te ra l s
are ignored.
4. Same as for the operating system
format.
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.
5. Same as for the operating system
format.
6. Parameters, separators, and termi
n a t o r s a r e s t o r e d i n t h e j o b ' s fi e l d
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.
6. Parameters are stored in their dis
play code equivalent beginning at
RA+2. Separators and terminators are
stored as follows:
Character
Code (Octal)
1
2
3
4
5
6
>((SWSy
60459680 E
5-3
Operating System Format
Product Set Format
Character
Code (Octal)
»
10
) or .
17
Other valid
separators
16
Refer to section 10 of Volume 4,
Program Interface, for more
information.
7. File names are one to seven alpha
numeric characters.
7. File names are one to seven alpha
numeric characters. In some products,
file names beginning with a numeric
character are invalid.
8. Not NOS/BE compatible.
8. NOS/BE compatible.
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 orderindependent 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
,^s>!\
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.
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.
5.
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.
6.
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
s e a r c h e s f u r t h e r.
7.
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.
8.
If the command name is not found during any of the above searches, the command is
declared invalid and the job is aborted.
9.
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
PROCESS FIELD
LENGTH CONTROL
(SEE SECTION 3)
KD
SEARCH GLOBAL
LIBRARY SET FOR
COMMAND NAME
READ A
COMMAND
COMMAND PROCESSOR
SEARCHES ITS LIST OF
COMMAND NAMES FOR
SPECIAL COMMAND
LOAD PROGRAM
TO CENTRAL
MEMORY
STORE COMMAND
AND COMMAND
ARGUMENTS IN
JOB'S FIELD
LENGTH
PROCESS
SPECIAL
REQUEST
EXECUTE
PROGRAM
SEARCH PP LIBRARV
FOR NAME. IF NAME
IS VALID PP
PROGRAM NAME
USE NOS FORMAT
FOR PROCESSING
PARAMETERS
_J
USE NOS FORMAT
FOR PROCESSING
PARAMETERS
SEARCH FNT FOR
FILE ASSIGNED TO
THIS JOB
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
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
e x i t fl a g .
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-
/ ^ X
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 * A f t e r a s e cSecurity
u r i t y c oFeatures
n fl i c t , t hine section
s y s t e m 3.d o e s n o t a l w a y s a l l o w E X I T p r o c e s s i n g . R e f e r t o
/fSN
60459680
E
5-7
/^%
FLOW CONTROL COMMANDS
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
c o n t r o l , y o u c a n u s e e r r o r fl a g s , fi l e a t t r i b u t e s , o r o t h e r j o b a t t r i b u t e s . T h e fl o w
control commands and a brief description of each appear in the following list:
Command
Description
BEGIN Initiates processing of a procedure.t
D I S P L AY E v a l u a t e s a n e x p r e s s i o n a n d d i s p l a y s t h e r e s u l t i n t h e d a y fi l e o f t h e
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.
E N D I F 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 m a t c h i n g I F, S K I P, o r E L S E c o m m a n d .
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.
ONEXIT Enables EXIT error processing.
0$®$*\
R E V E RT R e t u r n s p r o c e s s i n g f r o m a p r o c e d u r e t o t h e c o m m a n d r e c o r d o f p r o c e d u r e
that called it.
SET Assigns values to special symbolic names.
S K I P S k i p s t o t h e fi r s t m a t c h i n g E N D I F c o m m a n d .
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
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
The following are t h e a r i t h m e t i c o p e r a t o r s .
Operator
Operation
+
Addition.
-
Subtraction.
*
Multiplication.
/
Division.
**
Exponentiation.
Leading -
Negation. This operato
Leading +
Ignored.
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
.EQ.
Operation
Equal to.
^
.NE.
Not equal to.
<
. LT.
Less than.
>
. G T.
Greater than.
_< .LE.
Less than or equal to.
> .GE.
Greater than or equal to.
60459680 H
6-3
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
truncated from the result string.
Operator
Operation
• E Q V. E q u i v a l e n c e ( c o m p l e m e n t o f t h e l o g i c a l s u m ) .
.OR.
.AND.
Inclusive
AND
OR
(logical
(logical
sum).
product).
•XOR. Exclusive OR (logical difference).
. 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
/ / . C AT. C o n c a t e n a t i o n o f t w o s t r i n g s i n t o o n e s t r i n g . ( E i t h e r / / o r . C AT. m a y
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
expression. If GOODY and 101 were supplied as values for PI and
be true, and the NOTE command would be included and executed. If
for PI, the .IF statement would be false, resulting in the execution
and then of the DISPLAY command.
string in the .IF
P2, the .IF statement would
BADNEWS were substituted
of the REVERT command
^
6-4
60459680
H
^
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
i n t e g e r.
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
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.
Va l i d
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
r i g h t - j u s t i fi e s t h e d i s p l a y c o d e v a l u e o f t h e s t r i n g . I f t h e s t r i n g i s t h e r e s u l t o f t h e ^ \
S T R , S T R B , o r S T R D f u n c t i o n , i t i s l e f t - j u s t i fi e d a n d d i s p l a y e d a s a c h a r a c t e r s t r i n g . '
Example:
/display,$Lit$
49748 141124B
/display,$a$
1 1B
/display,1
1 1B
/display,$1$
28 34B
/display,$$$$
43 53B
/ d i s p l a y, l i t e r a l
CCL157- UNKNOWN NAME - LITERAL
/display,STR(SREALLY A STRINGS).
REALLY A STRING
/
6
-^^Sv
6
60459680
H
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
Yo u r
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).
y f fl S ? ^
WEEKDAY The day of the week returned as a numerical value.
MON Monday (numerical value =1).
TUE Tuesday (numerical value =2).
WED Wednesday (numerical value - 3).
THU Thursday (numerical value =4).
FRI Friday (numerical value =5).
S AT S a t u r d a y ( n u m e r i c a l v a l u e = 6 ) .
SUN Sunday (numerical value =7).
60459680 E
6-6.1/6-6.2
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.
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).
r
Most symbolic names have an initial value of zero. The exceptions are shown in the
following list:
Name
Description
C S E T Te r m i n a l c h a r a c t e r s e t m o d e ( N O R M A L = 0 o r A S C I I = 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 AY T h e d a y o f t h e m o n t h .
D AY S N u m b e r o f d a y s s i n c e J a n u a r y 1 , 1 9 7 7 .
H I D T w o - c h a r a c t e r m a c h i n e i d e n t i fi e r ( 6 - b i t d i s p l a y c o d e ) .
M O N T H T h e m o n t h o f t h e y e a r.
N W K Te r m i n a l n e t w o r k c o n n e c t i o n .
OT
Yo u r
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
Yo u r
job's
SL
Te r m i n a l
service
display
class.
mode.
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).
/gpN
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
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
fl a g .
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
d a y fi l e .
EF
Previous
EFG
Global
error
error
fl a g .
fl a g .
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.
SS Subsystem for an Interactive job.
/^^V
6-8
60459680
H
Symbolic names whose values are set by the operating system.
Name
0^\
Description
CMN
Central memory RFL setting divided by 100g (refer to RFL Command
in section 7).
CS
Connection status.
CSET
Terminal character set mode (NORMAL=0 or ASCII=1).
DATE
The date in the form yymmdd.
DAY
The day of the month.
DAYS
Number of days since January 1, 1977.
DSC
Flag indicating that skipped commands are to be entered in the
d a y fi l e .
ECN
Extended memory RFL setting divided by IOOO3 (refer to RFL
Command in section 7).
EF
P r e v i o u s e r r o r fl a g .
FAMILY
Current family name.
FL
Current CM field length.
HID
Tw o - c h a r a c t e r m a c h i n e i d e n t i fi e r ( 6 - b i t d i s p l a y c o d e ) .
MFL
Maximum CM field length.
MFLL
Maximum extended memory field length.
MONTH
The month of the year. (January = 1, February = 2, etc.)
NWK
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.
n
60459680 H
OT
Job origin type.
SC
Service class of the job.
SL
Terminal display mode (LINE or SCREEN).
SPS
System page size (in lines).
SPW
System page width (in characters).
SPD
System page density (in lines per inch).
6-8.1/6-8.2
Name
SSM
Description
Operating system security mode (0 means unsecured. 1 means
secured).
SYS Host operating system.
TIME Current time of day (hhmm).
VER Operating system version number (6-bit display code).
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
PNL
Description
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
Description
EFG
G l o b a l e r r o r fl a g .
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
i n d i c a t e s a n e r r o r, a n d a z e r o v a l u e i n d i c a t e s n o e r r o r. F o r d e t a i l e d e r r o r
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.
N a m e Va l u e ( O c t a l )
60459680 H
Description
TIE
User break 1.
TAE
User break 2.
ARE
A r i t h m e t i c e r r o r.
ITE
SCP invalid transfer address.
PSE
Program stop error.
PPE
PPU abort.
6-9
/^tf&w£$V
Name
Value (Octal)
CPE
PCE
Description
CPU abort.
10
PPU call error.
11
Reserved for installation.
MLE
14
Message limit.
TLE
15
Ti m e l i m i t e r r o r.
FLE
16
F i l e l i m i t e r r o r.
TKE
17
Tr a c k l i m i t e r r o r.
SRE
20
SRU limit error.
FSE
22
Forced error; set by operator entry of ERR. under
D I S u t i l i t y.
RCE
23
Job hung in auto recall.
ODE
24
Operator drop.
IDE
25
Idledown.
SPE
26
Reserved for your site.
STE
27
Suspension timeout.
ECE
30
Extended memory parity error.
RSE
31
Recovered system (level 3).
SSE
32
Subsystem aborted.
RRE
34
Operator rerun.
OKE
35
Operator kill.
DRE
37
Deadstart rerun.
RAE
40
Recovery abort.
JSE
41
Job step abort.
SVE
42
S e c u r i t y c o n fl i c t .
SYE
43
System abort.
PEE
44
CPU parity error.
SWE
45
Software error.
^*ES\
6-10
60459680 G
N a m e Va l u e ( O c t a l )
Description
ORE
46
Override error condition.
MXE
47
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
Value
Description
NORMAL
0
Uppercase characters only.
ASCII
1
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
60459680 G
Value
Description
JAN
January.
FEB
February.
MAR
March.
APR
April.
MAY
May.
JUN
June.
JUL
J u l y.
AUG
August.
SEP
September.
OCT
10
October.
NOV
11
November.
DEC
12
December.
6-10.1
Symbolic names with fixed values that can be compared to the terminal's network
connection (NWK) value within an expression.
Name
Value
Description
NONE
Terminal has no NAM connection.
CCP
Terminal is connected using NAM/CCP.
CDCNET
Terminal is connected using NAM/CDCNET.
Symbolic names with fixed values that can be compared with the origin type (OT)
value within an expression.
Name
Va l u e
Description
BCO
Local batch origin.
IAO
Interactive origin.
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:
Name
6-10.2
Value
Description
SYSC
System service class.
BCSC
Local batch service class.
RBSC
Remote batch service class.
TSSC
Interactive service class.
DISC
Detached interactive service class.
NSSC
Network supervisor service class.
SSSC
Subsystem service class.
MASC
10
Maintenance service class.
CTSC
11
Communication task service class.
IOSC
12
Installation service class 0.
use
13
Installation service class 1.
I2SC
14
Installation service class 2.
I3SC
15
Installation service class 3.
DSSC
77
Deadstart service class.
60459680 G
Symbolic names with fixed values that can be compared with the terminal display mode
(SL) value within an expression.
Name
Va l u e
LINE
0
Line mode.
SCREEN
1
Screen mode.
Description
Symbolic name with a fixed value that can be compared with the host operating system
(SYS) value within an expression.
Name
0^\
Value
Description
NOS
Network Operating System.
NOSB
Network Operating System/Batch Environment.
SC2
SCOPE 2 Operating System.
Symbolic names with a fixed value that you can compare with the subsystem for an
interactive job (SS).
Name
Value
Description
ACCESS
The access subsystem.
BASIC
The BASIC subsystem.
BATCH
The batch subsystem.
EXECUTE
The execute subsystem.
FORTRAN
The FORTRAN 5 subsystem.
FTNTS
The FORTRAN Extended 4 subsystem,
NULL
The null subsystem.
0^\
60459680 G
6-11
Symbolic names with true or false values. True is 1; false is 0.
Name
Description
F
Fixed value of 0 (false).
FALSE
Fixed value of 0 (false).
SWn
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
/) •
T
Fixed value of 1 (true).
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
F r i d a y.
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
o t h e r t h a n 1 o r 0 . T h e l i s t o f fi l e a t t r i b u t e s f o l l o w s t h e d e s c r i p t i o n o f t h e F I L E f u n c t i o n
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.
/*S%v
6-12
60459680 H
Format:
FILE(Ifn,expression)
Parameter
Description
lfn
Name of the local file for which attributes are being determined.
expression
E i t h e r a s p e c i a l FIL E fu n c ti o n a ttr i b u te o r a n e x p r e s s i o n , c o n s i s ti n g
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.
/gptev
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.
/S^^N
E Q E S T o r d i n a l o f t h e e q u i p m e n t o n w h i c h t h e fi l e
r e s i d e s . I f t h e fi l e i s n o t a s s i g n e d t o a d e v i c e , i t
has an EST ordinal of zero.
EX File has execute permission.
FS File size in PRUs.
GL File
is
IN
type
File
a
global
is
l i b r a r y.
input.
LB File is on a labeled tape.
LI
60459680 H
File
is
a
system
library
fi l e .
6-13
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.
P T F i l e t y p e i s p r i m a r y.
QF File type is queued.
RA File has read append permission.
RD File has read permission.
RM File has read modify permission.
RU File has read update permission.
TP File is on magnetic tape.
TT
File
is
assigned
to
a
terminal.
/B^t
UP File has update permission.
WR File has write permission.
ZL File has zero length.
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
Format:
FILE(lfn,DT(dt))
Parameter
Description
l f n N a m e o f t h e fi l e f o r w h i c h d e v i c e r e s i d e n c e i s b e i n g d e t e r m i n e d .
dt A two-character mnemonic identifying the device, which may be any one
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).
D M 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 ( h a l f - t r a c k ) .
D P D i s t r i b u t i v e d a t a p a t h t o e x t e n d e d m e m o r y.
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).
DW 819 Disk Storage Subsystem (double-density).
MT Magnetic tape drive (seven-track).
NE
Null
equipment.
NT Magnetic tape drive (nine-track).
TT
60459680
Interactive
terminal.
H
6-15
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(string)
Parameter
Description
string
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
string
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
.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
Description
strexp
May be any legal CCL expression, usually but not necessarily a
l i t e r a l . L i t e r a l s a r e l e f t - j u s t i fi e d , a n d m a y b e a n y l e n g t h u p t o t h e
maximum line length. Nonliteral values are treated normally during
evaluation of the expression. However, a numeric result will be
l e f t - j u s t i fi e d a n d t r e a t e d a s a s t r i n g .
lc
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
e q u i v a l e n t t o 1 . A p o s i ti v e v a l u e g r e a te r th a n th e l e n g th o f s tr e x p
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
left if re is positive or from the right if negative. A positive
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
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
Description
numexp
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
t h a n 1 0 c h a r a c t e r s a n d w i l l b e r i g h t - j u s t i fi e d a n d b i n a r y - z e r o fi l l e d
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$.
lc
Specifies which character of numexp is to be the leftmost in the
r e s u l t i n g s t r i n g . F o r f u r t h e r e x p l a n a t i o n o f t h i s p a r a m e t e r, r e f e r t o
the description of the STR function.
Specifies which character of numexp is to be the rightmost in the
r e s u l t i n g s t r i n g . F o r f u r t h e r e x p l a n a t i o n o f t h i s p a r a m e t e r, r e f e r t o
the description of the STR function.
Example:
Each of the following expressions will produce the string $102$.
STRB($ABC$,-5,-3).
STRB(10203B,-5,-3).
• 6-16.2
60459680 H
/*^%K
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
Description
numexp
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
t h a n 1 0 c h a r a c t e r s a n d w i l l b e r i g h t - j u s t i fi e d a n d b i n a r y - z e r o fi l l e d
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$.
lc
Specifies which character of numexp is to be the leftmost in the
r e s u l t i n g s t r i n g . F o r f u r t h e r e x p l a n a t i o n o f t h i s p a r a m e t e r, r e f e r t o
the description of the STR function.
Specifies which character of numexp is to be the rightmost in the
r e s u l t i n g s t r i n g . F o r f u r t h e r e x p l a n a t i o n o f t h i s p a r a m e t e r, r e f e r t o
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 •
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.
1 2 . 5 6 . 2 6 . D I S P L A Y, S T R D ( R 1 + R 2 ) .
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
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 ■
g e n e r a t i n g d i s p l a y c h a r a c t e r s t r i n g s . T h e o t h e r D I S P L AY c o m m a n d s s p e c i f y n u m e r i c 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
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 use the FILE function to determine if a file named TEST1 is local to
t h e j o b . I f t h e fi l e i s l o c a l , i t i s c o p i e d t o t h e O U T P U T fi l e ; i f i t i s n o t , i t i s a s s u m e d
to be an indirect access permanent file, and a local copy is obtained and copied to OUTPUT.
60459680
H
6-17
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
n o t i n i t i a l l y a l o c a l fi l e .
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
i n i t i a l l y a l o c a l fi l e .
15.40.19.IF,FILE(TEST1,LO),LABEL1.
1 5 . 4 0 . 1 9 . C 0 P Y S B F, T E S T 1 , 0 U T P U T.
15.40.21.
END
OF
15.40.21.ELSE,LABEL1.
15.40.21 .ENDIF,LABELL
I N F O R M AT I O N
ENCOUNTERED.
tttmr
y
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:
E N D I F, l a b e l .
Parameter
Description
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.
^
\
y^&Sk
6-18
60459680
D
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
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.
Refer to WHILE Command in this section for an example of ENDW command use.
0ftoi\
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
command to prevent execution of the EXIT
command executed in this way terminates
procedures if nesting has occurred, but
values.
the EXIT command be preceded by a SKIP or REVERT
command in the case where no error occurs. An EXIT
the executing procedure as well as all calling
does not restore control registers to their previous
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
IF (OR IFE) COMMAND
The IF command conditionally skips one or more commands.
Formats:
IF,condition.command.
I F, c o n d i t i o n , l a b e l .
Parameter
Description
c o n d i t i o n S p e c i fi e s a n e x p r e s s i o n t h a t i s e i t h e r t r u e o r f a l s e . T h e s e p a r a t o r
following condition in the first format must be a terminator.
command Specifies a valid command.
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. 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
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.
z^PN
T
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.
1 2 . 5 7 . 0 3 . O N E X I T.
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
command to determine if the color the BEGIN command substituted for COLOR
Different processing is done for the colors red and blue. Any other color
# character in the comment line inhibits substitution for the word (COLOR)
(refer to Parameters and the Procedure Body in section 4).
uses the IF
is red or blue.
is ignored. The
it precedes
.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
60459680
F
6-21
/*^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.
R E V E R T.
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
/eS^
^)
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\
SECONDS
JOB STEP SRU
ACCOUNT BLK SRU
DAYFILE MESSAGES
COMMANDS
MASS STORAGE
n
60459680 H
64
31808
31808
993
NO LIMIT
59008
7-17
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
sc
fi e l d :
Service Class
S
System
B
Batch
R
Remote batch
T
Interactive
D
Detached interactive
N
Network supervisor
C
Communication task
M
Maintenance
0
Installation class
1
Installation class
2
Installation 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
NI Not interactive
blank Queued
7-18
60459680
D
/e^\
Parameter
Description
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).
l i d 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 h a t i s t o
p r o c e s s t h e j o b . T h i s i s a t h r e e - c h a r a c t e r,
site-defined mnemonic.
ujn The user job name (UJN) of the job. It is either the
name you assigned the job or it is your user index hash
if you did not assign the job a name.
/fP*N
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
STATUS
A B C F. B . . B C . . L D I J O B
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.
Example:
/enqui re,ujn
/sP^S
JSN SC CS DS LID UJN
STATUS
ABCH.B. .BC.M42.LEVEL
ABCB.T.ON.BC. .AJLA
ABCI.B. .BC.M42.LDIJ0B
A B C F. B . . B C . . L D I J O B
INPUT QUEUE
EXECUTING
PRINT QUEUE
WAIT QUEUE
EXECUTING MESSAGE
Do not specify the UJN=ujn parameter with any parameter other than
0=lfn2.
r
J S N = j s n R e t u r n s a d e t a i l e d r e p o r t o f t h e j o b w i t h t h e s p e c i fi e d j o b s e q u e n c e
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
Parameter
Description
Example:
/en quire,j sn=abcb
A B C B . T. O N . B C . . E X E C U T I N G U J N = A J L A L E V E L = LV L O
S R U S = 2 . 5 7 3 . S R U L I M I T = N 0 L I M I T. 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
s p e c i fi c a t i o n s .
Example:
/enqui re,j sn=abcf
A B C F. B . . B C . . W A I T Q U E U E U J N = L D I J O B L E V E L = LV L 0
P R U L E N G T H * 3 2 . D C = T T. F C = . I D = 0 . E C =
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
J S N S C C S D S L I D S TAT U S J S N S C C S D S L I D S TAT U S
A B C H . B . . B C . M 4 2 . I N P U T Q U E U E A B C B . T. O N . B C . . E X E C U T I N G
A B C I . B . . B C . M 4 2 . P R I N T Q U E U E A B C F. B . . B C . . W A I T Q U E U E
Do not specify the JSN=jsn parameter with any parameter other than
0=1fn2.
F N = l f n j R e t u r n s t h e s t a t u s o f l o c a l fi l e l f n l ( r e f e r t o t h e O P = F p a r a m e t e r ) .
0 = l f n 2 W r i t e s t h e o u t p u t o n f i l e l f n 2 » T h e d e f a u l t i s O U T P U T. I f y o u
specify only the 0=lfn2 parameter in a batch job, the
0P=pjp2...pn parameter defaults to 0P=A.
7-20
60459680
D
'
/**^\
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
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
s t a t u s S p e c i fi e s w h e t h e r e r r o r m e s s a g e s g e n e r a t e d b y c o m m a n d s w i t h i n 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.
J s n S p e c i fi e s t h e j o b s e q u e n c e n a m e ( J S N ) o f t h e j o b w h o s e p a u s e b i t y o u
w a n t to c l e a r.
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
HTIME COMMAND
The HTIME command issues a dayfile message
count for the job. A clock cycle on the model
instructions require a certain number of clock
Reference Manual. This command can be used
giving the model 176 accumulated clock cycle
176 is 27.5 nanoseconds. COMPASS
cycles to execute as described in the COMPASS
for performance comparisons.
Format:
HTIME.
The resulting dayfile message has the following format. The cycle count is in kilocycle
units.
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 |
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
u j n , p r i o r i t y, t i m e l i m i t , m e m o r y, x m e m o r y, l i d , l e v e l . p u n c h m o d e
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
Description
ujn
Alphanumeric user job name (UJN) of one to seven characters. This
name identifies the individual jobs being run under the same user
name.
P=priority
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.
SC=class
Specifies the service class to be assigned to the job. The value
class must be one of the following values:
class Description
SY
60459680 F
System
7-23
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).
A L = l e v e l S p e c i fi e s t h e m a x i m u m s e c u r i t y a c c e s s l e v e l y o u r j o b c a n a t t a i n .
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 = t i m e l i m i t S p e c i fi e s t h e c e n t r a l p r o c e s s o r j o b s t e p t i m e l i m i t i n s e c o n d s .
Values can range from 1 to 77777. Decimal is the default base.
Octal values from 1 to 77777s (* t0 32767) can be entered if
f o l l o w e d b y a B s u f fi x . T h e d e f a u l t l i m i t i s 6 4 ( 1 0 0 g ) . f D e c i m a l
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
section 3).
C M = m e m o r y S p e c i fi e s t h e m a x i m u m o c t a l fi e l d l e n g t h f o r t h e j o b ( r e f e r t o F i e l d
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
Parameter
Description
A value containing an 8 or 9 or the suffix D is interpreted as
decimal.
>ff\
EC=xmemory
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,
ST=lid
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 h o s t t o w h i c h y o u a r e
routing the specified job. The LID must be a three-character
alphanumeric string defined by site personnel. The local host is
the default.
You must have special authorization to use this parameter (refer to
the LIMITS command).
p u n c h m o d e S p e c i fi e s t h e c o n v e r s i o n m o d e f o r c a r d d e c k s . T h i s p a r a m e t e r m u s t
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
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
L D I , l f n , i d , O P, d c , u n , f m .
The parameters in the first format are order-independent. Those in the second format are
order-dependent.
Parameter
Description
FN=lfn
Specifies the name of the file containing the job(s) to be submitted.
LOAD is the default.
ID=id
S p e c i fi e s t h e i d e n t i fi e r o f t h e l o c a l d e v i c e w h i c h w i l l r e c e i v e j o b
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.
OP=OP
Directs the system to enter the job sequence name (JSN) of each job in
the dayfile of the job that issued the LDI command.
DOdc
Specifies the disposition of output for each job that is queued for
input•
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).
NO Discards all output.
TO Queues the output with a wait disposition.
UN=un
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
.^^S\
Parameter
Description
F M - f m S p e c i fi e s t h e f a m i l y n a m e o f t h e r e m o t e b a t c h u s e r t o w h o m t h e s y s t e m
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
l f n N a m e o f a fi l e a s s i g n e d t o t h e j o b .
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
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=lfn
Description
S p e c i fi e s t h e fi l e w h i c h r e c e i v e s t h e v a l i d a t i o n i n f o r m a t i o n . T h e
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
/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.
P R U s a v a i l a b l e f o r a l l i n d i r e c t fi l e s .
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
fi l e s a l l o w e d i n y o u r c a t a l o g . Whenever you initiate a permanent file operation, the
system assigns a limit, which can vary with the service class of your job.
r
60459680 D
7-29
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.
/piP*N
60459680 D
7-37
y<:*«\
Attributes listed in the ATTRIBUTE column can be listed by name or by mnemonic.
Attribute Name
Mnemonic
Description
HOST
H Indicates that this is the local host (that is, the host
you are logged into).
LINKED
L Indicates that this host is linked to your local host.
STORE FORWARD
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.
VALIDATION
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.
LOOPBACK
B Indicates that the LID is a loopback LID (used for test
purposes).
Entries that can be listed in the RHF, NAM, and SSF columns are as follows:
Entry
S i g n i fi c a n c e
IN
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.
NA
Indicates that the subsystem is not available or that no link exists to this
PID throught this subsystem.
OUT
Indicates that the link to the PID is out of service due to a network fault
condition.
DISABLED
Indicates that the link to the PID has been disabled by the console operator.
7-38
60459680 D
MACHINE COMMAND
Some programs that ran on mainframes other
run on the models 815, 825, 835, 845, and
most likely to run incorrectly on models 815,
with tight instruction-modification loops. The
programs to run correctly on these models.
than models 815, 825, 835, 845, and 855 will not
855 until changes are made in your job. Programs
825, 835, 845, and 855 are COMPASS programs
MACHINE command will enable some of these
Format:
MACHINE,EP=state.
Parameter
Description
E P = s t a t e S p e c i fi e s w h e t h e r e x t e n d e d s t a c k p u r g i n g i s s e l e c t e d . E P = O N s e l e c t s
it and EP=OFF disables it.
/H^v
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
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
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 w h i c h c o n t a i n s t h e s p e c i fi e d l i n e s .
Default is OUTPUT.
N R I n h i b i t s r e w i n d o f l f n . D e f a u l t i s t o r e w i n d t h e fi l e a t t h e
beginning and end of NOTE command execution.
/ S p e c i fi e s t h e d e l i m i t i n g c h a r a c t e r u s e d t o s e p a r a t e t h e i n d i v i d u a l
e n t r i e s t h a t b e c o m e l i n e s i n t h e fi l e . I t c a n b e a n y c h a r a c t e r. I t
m u s t i m m e d i a t e l y follow a period or right parenthesis. Multiple
delimiters generate blank lines.
l i n e i S p e c i fi e s t h e c h a r a c t e r s t r i n g w h i c h c o n s t i t u t e s o n e l i n e o f d a t a i n
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
N O T E c o m m a n d s , e a c h w i t h a n N R , c a n b e u s e d . T h i s s e r i e s s h o u l d b e f o l l o w e d w i t h a PA C K '
command since each NOTE command writes an EOR.
7-40
60459680
D
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:
O F F S W, s w i t c h ! , s w i t c h 2 s w i t c h ^ j s n .
Parameter
Description
s w i t c h i S p e c i fi e s t h e s w i t c h ( e s ) t o b e c l e a r e d . Yo u m u s t d e n o t e e a c h s w i t c h
switchi by an integer in the range of 1 through 6. If you specify 0
for this parameter, the system clears all sense switches.
j s n S p e c i fi e s t h e j o b s e q u e n c e n a m e ( J S N ) o f t h e j o b w h o s e s e n s e s w i t c h ( e s )
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
fi e l d .
Refer to the description of the ONSW command for further information on sense switch
settings.
60459680
D
7-41
•
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:
O N S W, s w i t c h ! , s w i t c h 2 , . . . ^ w i t c h n , j s n .
Parameter
Description
s w i t c h . ^ S p e c i fi e s t h e s w i t c h ( e s ) t o b e s e t . Yo u m u s t d e n o t e e a c h s w i t c h
switch^ by an integer in the range of 1 through 6. If you specify 0
for this parameter, the system sets all sense switches.
j s n S p e c i fi e s t h e j o b s e q u e n c e n a m e ( J S N ) o f t h e j o b w h o s e s e n s e s w i t c h e s
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
fi e l d .
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
interactive job. If your site does not use password randomization, the origin type of your ^^
job must match the type of password you want to change. In other words, an interactive ^)
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
Parameter
Description
oldpassword
Specifies the old password. This is a required parameter if
password randomization is used.
newpassword
Specifies the new password. The new password must be not more than
seven characters long. Your site determines the minimum length of
p a s s w o rds (4 is the default). This is a required parameter if
password randomization is used.
XD=expiredate
Specifies the expiration date for the
expiredate must be a 6-digit string of
mm, dd are 2-digit year, month, and
The latest date you can specify and
site-determined.
password. The value
the form yymmdd, where yy,
day designators, respectively.
the default expiration date are
You must have special authorization to specify an expiration date
for password (refer to the LIMITS command).
XT=expireterm
S p e c i fi e s t h e l i f e o f t h e p a s s w o r d i n d a y s . I f y o u s p e c i f y 0 , t h e
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
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
want
to
set.
*
You must check the status of the pause bit to effectively use this command. The program
tust because
becaZ8^the
b6C^SVhe.PaUSe
bU cleared.
±S Set'You
Similarly,
doeschecks
not proceed
just
pause bit has been
can writethea program
program that
the status
4 ° ! P ^ g ^ r i n t e r f ^ e ) : 3 1 ' 8 * " " " ^ t 0 ^ ^ ^ ( r e f e r C ° ^ « < * "■ - c ^ n ^ l u m ^ 8
sft^i/ffnf0 def^ine/hfher a PAUSE °r G0 command has bee* entered, write a program to
ka w
H
whenever
h e n e v e rthef l T
PAUSE/GO
J j j £ / S ? f command
" " V ? " * "sets/clears
8 y S t e m the
u npause
c o n d i tflag
i ^ a l(bit
l y c12
l e aofr sword
b i t RA)
1 * 3 Henrp
If word
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
y o u r ^ b i s z ^ r o V d l t t h " ^ T * ? * * " • ' - W a r i l y, t h e e x t e n d e d m e m o r y a s s i g ' 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.
--^^s.
7-44
60459680 E
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
PR
PU
PL
WT
Description
Print
Punch
Plot
Wait
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.
0%B>i.
60459680
E
7_45
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
Description
ID=pid
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
L=lfn
Specifies the name of the file to receive the QUEUE7 output. The
default is OUTPUT.
Pi
Specifies the SCOPE 2 queues (input, output, execute, or punch) to be
d i s p l a y e d . Va l i d o p t i o n s f o r P l a r e l i s t e d b e l o w. F r o m o n e t o f o u r
options can be specified. The default is E.
Ei
Description
A
Lists jobs found in all queues (E, I, 0, and P).
E
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
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.
Description
help
I D D i s p l a y s p h y s i c a l i d e n t i fi e r s f o r a l l S C O P E 2 m a i n f r a m e s i n
the network.
SYNTAX Displays the QUEUE7 command format,
or
S
/queue7,e
JOBS
6/
52/
70
R(Z),1.
ORD ACTION
ID
TYPE
JOB BG
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 STAT
FIRST ACTION MESSAGE/LAST DAYFILE MESSAGE
3 M06/**
REPONSE
0
7
26
JOBXXXZ 4000 M06/**
PAUSE. DO NOT GIVE A GO. TESTING ON 606
PA US
4 M06/**
RESPONSE
0
7
26
JOBXXXZ 4000 M06/**
PAUSE. DO NOT GIVE A GO. TESTING ON 606
PA US
5 M06/**
RESPONSE
0
7
26
JOBXXXZ 4000 M06/**
TESTING ON 606
PAUSE. DO NOT GIVE A GO.
PA US
QUEUE7 COMPLETE
Figure 7-1. QUEUE7 Execute Queue Sample Listing
Column headers for the QUEUE7 execute queue listing have the following meanings:
Header
Description
ORD
The job ordinal.
ACTION ID
T h e s t a t i o n / t e r m i n a l i d e n t i fi e r o f t h e t e r m i n a l f r o m w h i c h t h e j o b e x p e c t s
a response; present only when the job requires a response.
JOBNAME
Job name of the executing job.
PRTY
Priority of the job; must be in the range of 0 to 7777g.
JOB ORIGIN
S t a t i o n / t e r m i n a l i d e n t i fi e r o f t h e t e r m i n a l f r o m w h i c h t h e j o b w a s
submitted.
TIME USED
CPU seconds used by the job.
TIME LEFT
CPU seconds remaining for execution.
LCM IN USE
Number of LCM buffers in use by the job.
JOB STAT
Current processing state of the job.
BG
Indicates that the job will be scheduled as a background priority job.
60459680 D
7-47 |
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 -REQUIREMENTS TIME DEPEND BG
O R I G I N M T N T YD YL SM SN SP LIMIT
107Z JOBXXXZ
110Z JOBXXXZ
M06/** 1002 0 0
M06/** 1002 0 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
0
0
0
0
10
10
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
J$$!0?\
Column headers for the QUEUE7 input queue listing have the following meanings:
O R D I n p u t q u e u e s u f fi 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 C O P E 2 p h y s i c a l
i d e n t i fi e r .
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.
D E P E N D A t w o - c h a r a c t e r d e p e n d e n c y i d e n t i fi e r a s s p e c i fi e d o n t h e j o b c a r d .
BG Indicates that the job will be scheduled as a background priority job,
/queue7,o
SFTS 10/ 172/
ORD FILENAME
/fPN.
111Z JOBXXXZ
STATION M06
INPUT
2
OUTPUT 1
PUNCH
0
172 H(Z) ,0,103
FILE PRTY
DESTIN
M06/** 4003
M02 MFF M05
0
0
0
0
0
0
0
0
0
DISP FORM
CODE CODE
FILE
SIZE
FILE IN
TRANSFER
PR
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
Column headers for the QUEUE7 output queue listing have the following meanings:
O R D O u t p u t q u e u e o r d i n a l s u f fi 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 C O P E 2 p h y s i c a l
i d e n t i fi e r .
FILENAME File name of the output file as specified on the job card.
F I L E D E S T I N S t a t i o n / t e r m i n a l i d e n t i fi e r o f t h e t e r m i n a l t o w h i c h t h e o u t p u t fi l e i s t o
be routed.
PRTY File priority; must be in the range from 0 to 7777g.
DISP CODE File disposition code.
FORM CODE Forms code of the file.
FILE SIZE File length in PRUs.
F I L E I N I n d i c a t e s w h e t h e r o r n o t t h e fi l e i s c u r r e n t l y b e i n g t r a n s f e r r e d t o 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.
packs are always available to all users.
I Nonremovable auxiliary packs should not be specified on the RESOURC command; non removable
/<^^\
7-50
60459680
F
Format:
RESOURC,rt1=u1/levelx,rt 2=u2/level2 rtn=u=n/leveln.
Parameter
rt^
Description
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 Seven-track magnetic tape unit
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; lv
7-60
60459680 F
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
A L = l e v e l S p e c i fi e s t h e s e c u r i t y a c c e s s l e v e l y o u w a n t a s s i g n e d t o t h e j o b .
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
v a l i d p a r a m e t e r s p e c i fi c a t i o n s .
60459680 D
7-61 |
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
Description
UJN=ujn
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.
DC=dc
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.
OP=op
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
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
w i t h i n a b a t c h j o b i s t h e n t e r m i n a te d (re fe r to Exi t Pro ce ssi n g i n se cti o n 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
Description
Increases the SRU limit by 64 units. Job execution continues. The
64-unit increment can be changed by your site.
S,nnnnn
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
^%\
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
p r i o r i t y.
SETPR,p.
Parameter
p
Description
S p e c i fi e s
the
p r i o r i t y,
1
<
p
<
70g.
"^)
Upon job initiation, a job is assigned the maximum priority allowed for its service class.
( T h e i n s t a l l a t i o n d e fi n e s t h e s e p r i o r i t y v a l u e s . ) I f a j o b ' s C P U p r i o r i t y i s l o w e r t h a n
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
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, n n n n n 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 b y n n n n n d e c i m a l s e c o n d s .
Job execution continues. You can enter octal seconds by specifying a B
after the number.
T»* Increases the central processor time limit to your maximum. Job
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
00110
00120
00130
00140
00150
PROGRAM T
DO 6 1=1,2500
DO 6 J=1,4000
A=1
6 CONTINUE
END
READY.
s e t 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
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
l o a d i n g t h e p r o g r a m f r o m a l o c a l fi l e , t h e p r o g r a m m u s t b e ^
stored in ABS-type records. (Refer to section 15 for a ^^%
description of record types.)
7-66
60459680 D
/i|f«£-\
G Allows global library load of the shell program.
S Allows system library load of the shell program.
T S p e c i fi e s t h a t t h e s y s t e m m o n i t o r c o m m a n d s d i r e c t l y f r o m t h e
terminal.
B S p e c i fi e s t h a t t h e s y s t e m m o n i t o r c o m m a n d s o u t s i d e
procedures.
C S p e c i fi e s t h a t t h e s y s t e m m o n i t o r c o m m a n d s i n s i d e p r o c e d u r e s .
T h e fi r s t f o r m a t d i s a b l e s s h e l l c o n t r o l .
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
d a y fi l e .
Format:
STIME.
Dayfile message format:
STIME nnnnnn.nnn UNTS.
60459680
D
7-67
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
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 t o b e s u b m i t t e d t o t h e s y s t e m f o r
processing as a batch job. The first record of the file must be in
6 - b i t d i s p l a y c o d e . T h e d e f a u l t i s t h e j o b ' s p r i m a r y fi l e .
q Specifies disposition of job output (OUTPUT, 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.
N O o r N D i s c a r d j o b o u t p u t a t j o b t e r m i n a t i o n u n l e s s t h e fi l e s
have been explicitly routed (default value for
i n t e r a c t i v e o r i g i n j o b s ) . T h e d a y fi l e i s n o t w r i t t e n t o
file OUTPUT.
RB=un or Route job output to the remote batch or interactive
E = u n u s e r s p e c i fi e d b y t h e u s e r n a m e u n . T h e d e f a u l t f o r u n
is the user name associated with the submitting job.
T O J o b o u t p u t ( i n c l u d i n g t h e d a y fi l e ) i s q u e u e d w i t h a w a i t
disposition.
N R N o r e w i n d o p t i o n ; t h e s u b m i t fi l e a n d t h e fi l e s p e c i fi e d o n a c R E A D
r e fo r m a tti n g d i r e c ti v e 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
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
ujn,parameters.
ln4
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
Description
Indicates that the submit file is to be reformatted and selects the
following default reformatting directives. The default directives
r e m a i n i n e ff e c t u n t i l s p e c i fi e d o t h e r w i s e .
cNOTRANS (disabled by cTRANS)
cSEQ (disabled by cNOSEQ)
c PA C K ( d i s a b l e d b y c N O PA C K )
T h e c J O B d i r e c t i v e m u s t b e t h e fi r s t l i n e o f t h e s u b m i t fi l e . I f
o m i t t e d , t h e fi l e i s n o t r e f o r m a t t e d . I f l i n e n u m b e r s a r e i n c l u d e d i n a
submit file, the file must begin with a cJOB directive.
cUSER
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.
cCHARGE
Inserts a CHARGE command that is identical to the CHARGE command
currently in effect for the submitting job. If no CHARGE command is in
e ff e c t f o r t h e s u b m i t t i n g j o b , t h i s d i r e c t i v e h a s n o e ff e c t o n t h e
SUBMIT file.
60459680 E
7-69
Directive
Description
cEOR Indicates that an end-of-record mark is to be placed at this point in
t h e s u b m i t fi l e d u r i n g r e f o r m a t t i n g .
c E O F I n d i c a t e s t h a t a n e n d - o f - fi l e 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
t h e s u b m i t fi l e d u r i n g r e f o r m a t t i n g .
cSEQ Indicates that the following lines may be preceded by line numbers and
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).
c P A C K R e q u e s t s t h a t a l l s u c c e e d i n g e n d - o f - r e c o r d a n d e n d - o f - fi l e m a r k s b e ^
removed (default value). This directive applies only to internal EOR
and EOF marks that currently exist. The cEOR and cEOF reformatting
d i r e c t i v e s a r e n o t a ff e c t e d .
c N O PA C K R e v e r s e s t h e e f f e c t o f t h e c PA C K d i r e c t i v e . R e q u e s t s t h e s y s t e m n o t
to discard succeeding internal end-of-record and end-of-file marks
that currently exist.
cTRANS Requests transparent submit mode. In transparent
ignores reformatting directives until an EOR or
encountered. The EOR or EOF mark cannot
cEOR or cEOF directive. SUBMIT performs the
transparent submit mode processing.
submit mode, SUBMIT
EOF mark is
be a mark to be created by a ^^^
following procedure for
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.
Return
to
step
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
Directive
Description
The cTRANS directive is typically used in conjunction with the cREAD
directive. The cREAD directive copies the contents of an existing
fi l e i n t o t h e s u b m i t fi l e a t t h e l o c a t i o n o f t h e c R E A D d i r e c t i v e .
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
w a s s e l e c t e d r e m a i n s i n e ff e c t a f t e r i t i s s e l e c t e d .
cNOTRANS
Reverses the effect of the cTRANS directive and informs the system
t h a t t h e s u b m i t fi l e i s t o b e e x a m i n e d o n a l i n e - b y - l i n e b a s i s . A l 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
i n t h e s u b m i t fi l e .
B e c a r e f u l i n p l a c i n g t h i s d i r e c t i v e i n t h e s u b m i t fi l e . I f
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.
/SP^N
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
e n c o u n t e r e d o n l f n . I f t h e fi l e t o b e r e a d i s n o t c u r r e n t l y l o c a l t o
the job, the system automatically attempts a GET and then an ATTACH on
t h e fi l e . I f l f n i s n o t s p e c i fi e d i n t h e d i r e c t i v e , TA P E 1 i s
a s s u m e d . I f t h e fi l e s p e c i fi e d c a n n o t b e f o u n d o r t h e r e a d fi l e 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.
I f t h e c PA C K d i r e c t i v e
internal EOR marks are
effect, all internal EOR
proper position during
60459680 D
i s i n e ff e c t w h e n t h e fi l e l f n i s r e a d , a l l
removed. If the cNOPACK directive is in
marks are read into the submit file in the
reformatting.
7-71 |
Directive
Description
Unless transparent submit mode is in effect when file lfn is read,
e a c h l i n e o f t h a t fi l e i s a l s o c h e c k e d f o r a r e f o r m a t t i n g d i r e c t i v e .
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
f o r t h e fi l e b e i n g r e a d . M o r e o v e r, o n l y t h o s e d i r e c t i v e s t h a t
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.
c R E W I N D , l f n R e q u e s t s t h a t t h e s y s t e m r e w i n d fi l e l f n t o t h e b e g i n n i n g - o f i n f o r m a t i o n ( B O I ) . I f l f n i s n o t s u p p l i e d , TA P E 1 i s a s s u m e d . T h i s
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
I n d i c a t e s t h a t t h e p r e fi x c h a r a c t e r i s t o b e c h a n g e d f r o m
(current prefix character) to c2 (new prefix character). The new
prefix character code is used to recognize all subsequent reformatting
directives until further changed.
c^
j
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
oth e r w i s e b y th e d i s p o s i ti o n p a r a m e te r ). This includes the dayfile output. Therefore, ma ke
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.
- D AY F I L E , l f n .
REPLACE,lfn.
7-72
60459680
D
SWITCH COMMAND
The SWITCH command sets the sense switches for reference by one of your programs.
Format:
SWITCH,switchj,switch2,...,switchn,jsn.
Parameter
Description
s w i t c h ^ S p e c i fi e s t h e s w i t c h ( e s ) t o b e s e t . Yo u m u s t d e n o t e e a c h s w i t c h
switch^ by an integer in the range of 1 through 6. If you specify 0
for this parameter, the system sets all sense switches.
j s n S p e c i fi e s t h e j o b s e q u e n c e n a m e ( J S N ) o f t h e j o b w h o s e s e n s e s w i t c h e s
w i l l b e c h a n g e d , j s n i s a n o p t i o n a l p a r a m e t e r, i t s d e f a u l t i s t h e
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
p fi l e O n e o f y o u r p e r m a n e n t fi l e s t h a t c o n t a i n s t h e d e s i r e d p r o l o g u e . I f
pfile contains more than one procedure, the system executes only the
fi r s t o n e . I f y o u o m i t t h e F N = p fi l e p a r a m e t e r o r g i v e p fi l e t h e v a l u e
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
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 U s e e i t h e r c e n t r a l p r o c e s s o r.
1 Use CPU 0.
2 Use CPU 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
Specifies an alphanumeric password. Its maximum length is seven
characters; its minimum length is defined by the installation.
familyname
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
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 a l i d a t i o n l i m i t s s t i l l r e fl e c t t h o s e o f t h e u s e r n a m e s p e c i fi e d a t j o b i n i t i a t i o n ( r e f 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
p lgi ceist l yt od i st ha e
b l etde)r.m i n a l a n d t h e d a y fi l e a n d w i t h E X I T
rstep is abp
o rrot ec e
d s swi ni tgh eanpapbrl e
o dp r i(autnel e smse sesx a
On an unsecured system with secondary USER commands disabled, any secondary USER command
w i l l b e i n v a l i d a n d a b o r t s t h e j o b . T h i s i s n o t a s e c u r i t y c o n fl i c t a n d t h e s e c u r i t y c o u n t
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
d e f a u l t f a m i l y.
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
|
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
d e f a u l t f a m i l y.
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.
■^5v
7-76
60459680
D
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
AUTO
BRIEF
CSET
EFFECT
KEY
LINE
NORMAL
SCREEN
TDU
TIMEOUT
TRMDEF
• Subsystem Selection Commands
ACCESS
BASIC
BATCH
EXECUTE
FORTRAN
FTNTS
NULL
• Interactive Status Commands
ctD
ctE
ctS
• Job Processing Commands
APPSW
BYE
0^\
DIAL
EXPLAIN
GOODBYE
HELLO
HELL07
HELP
HELPME
LOGOUT
NOSORT
RECOVER
REDO
RUN
Secure Login
SHOW
TEXT
WHATJSN
LIB
LIST
LOGIN
XMODEM
Primary File Editing Commands
ALTER
DELETE
DUP
LIST
MOVE
READ
RESEQ
WRITE
WRITEN
60459680 G
8-1
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
y*$^m5v
AUTO COMMAND
The AUTO command automatically generates five-digit line numbers.
Format:
A U TO , n n n n n , i i i i
Parameter
Description
Specifies the beginning line number; default value is 00100.
i i i i
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.
yfl^Stey
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
User enters cancel line character.
User enters entire line.
User enters cancel line character.
User completes the line.
User enters cancel line character.
00100 PROGRAM HEADER
00110 WRITE 1000
00230 1000 FORMAT(15X,'HEADINGS')
00240 WRITE 2000
00250 2000 FORMAT (15X,'AlfTH0R',9X,'TITLE',15X,
0 0 2 6 0 + ' P U B L I S H E R ' , 6 X , ' C 0 S T')
00270 STOP
00280 END
READY.
60459680 C
8-3
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
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:
Va l u e
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 - s u 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 |
i s s p e c i fi e d ) , a l l f o r m a t e ff e c t o r s a r e s u p p o r t e d e x c e p t
those that specify carriage positioning after output.
S p e c i fi c a l l y, t h e s l a n t ( / ) a n d p e r i o d ( . ) e f f e c t o r s a r e
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
t e r m i n a l . K E Y i s u s e d t o c r e a t e , e d i t , d i s p l a y, o r l o a d a d e fi n i t i o n fi l e .
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,
e d i t i n g , o r l o a d i n g t h e d e fi n i t i o n fi l e .
Format:
K E Y, o p t i o n , fi l e n a m e .
or
KEY?
/jfp&V,
60459680 H
8-5
Parameter
option
Description
Any of the following options.
Op ti o n
Description
HELP Gives a brief description of each option available. The
filename parameter is ignored.
C H E C K C h e c k s t o s e e i f f u n c t i o n k e y d e fi n i t i o n s a r e a l r e a d y
l o a d e d i n t o t h e t e r m i n a l . I f n o t , t h e d e fi n i t i o n s i n fi l e
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.
E D I T I n i t i a t e s c r e a t i o n o r e d i t i n g o f a k e y d e fi n i t i o n fi l e .
KEY first searches for a local file by the specified name,
t h e n f o r a n i n d i r e c t a c c e s s p e r m a n e n t fi l e . I f fi l e n a m e
d o e s n o t e x i s t , i t i s c r e a t e d . T h e e d i t e d fi l e i s s a v e d
or replaced at completion of editing.
L O A D L o a d s k e y d e fi n i t i o n s i n t o t h e t e r m i n a l f r o m t h e s p e c i fi e d
fi l e .
P R I N T C r e a t e s a l o c a l fi l e c a l l e d K E Y P R N T o n w h i c h t h e k e y
d e fi n i t i o n s a r e l i s t e d f r o m t h e s p e c i fi e d fi l e n a m e .
fi l e n a m e T h e n a m e o f t h e k e y d e fi n i t i o n fi l e . D e f a u l t i s K E Y D E F S .
? L i s t s t h e o p t i o n s a n d p r o m p t s y o u f o r a n o p t i o n a n d fi l e n a m e .
The KEY command may appear in a procedure file.
/*^^\
8-6
60459680 F
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;
c h a r a c t e r i s t i c s o f t h i s t e r m i n a l a r e p r e l o a d e d i n t o t h e s y s t e m s o t h a t n o d e fi n i t i o n fi l e i s
required). The system uses the following search order in attempting to find the definition
fi l e :
• 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
d e fi n i t i o n s .
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
Parameter
Description
T M = m o d e l S p e c i fi e s t h e t e r m i n a l m o d e l . T h e v a l u e s p e c i fi e d f o r m o d e l i s t h e
terminal mnemonic defined in the terminal definition file or the
terminal mnemonic for one of the following preloaded terminal
d e fi n i t i o n s :
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
ADM5 Lear Siegler ADM5 terminal.ttt
T V 9 2 4 Te l e V i d e o 9 2 4 t e r m i n a l . t t t t t t
T V 9 5 0 Te l e V i d e o 9 5 0 t e r m i n a l . t t t t t t
T V 9 5 5 Te l e V i d e o 9 5 5 t e r m i n a l . t t t t t t
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.
8-6.2
60459680 H
^SS^.
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;
c h a r a c t e r i s t i c s o f t h i s t e r m i n a l a r e p r e l o a d e d i n t o t h e s y s t e m s o t h a t n o d e fi n i t i o n fi l e i s
required). The system uses the following search order in attempting to find the definition
fi l e :
• 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
d e fi n i t i o n s .
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
|
Parameter
Description
T M = m o d e l S p e c i fi e s t h e t e r m i n a l m o d e l . T h e v a l u e s p e c i fi e d f o r m o d e l i s t h e
terminal mnemonic defined in the terminal definition file or the
terminal mnemonic for one of the following preloaded terminal
d e fi n i t i o n s :
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
ADM5 Lear Siegler ADM5 terminal.ttt
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 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
TDU COMMAND
The TDU command calls an interactive procedure to compile a terminal definition file and
s t o r e t h e c o m p i l e d d e fi n i t i o n ( i n l o a d c a p s u l e f o r m ) i n a u s e r l i b r a r y. T h e u s e r l i b r a r y
can later be accessed by a SCREEN or LINE command to define terminal characteristics to the
system.
T h e u s e r l i b r a r y t o r e c e i v e t h e l o a d c a p s u l e m u s t b e a l o c a l fi l e . I f t h e l i b r a r y fi l e y o u
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:
T D U , I = d e fi n i t i o n , L = l i s t i n g , L I B = l i b r a r y
Parameter
Description
I = d e fi n i t i o n S p e c i fi e s t h e t e r m i n a l d e fi n i t i o n fi l e . T h e fi l e m u s t b e i n 6 / 1 2 - b i t
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.
L I B = l i b r a r y S p e c i fi e s t h e l i b r a r y fi l e t o r e c e i v e t h e l o a d c a p s u l e . T h e d e f a u l t
name is TERMLIB. To be used by the SCREEN and LINE commands, the
l i b r a r y fi l e m u s t b e a l o c a l fi l e o r a n i n d i r e c t a c c e s s fi l e c a l l e d
TERMLIB.
The TDU command may appear in a procedure file.
0S^*,
60459680 F
8-8.1/8-8.2
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:
T R M D E F, L = l f n , t C l = v i , . . . , t c n = v n
Parameter
Description
L=lfn
S p e c i fi e s a n o p t i o n a l fi l e o n w h i c h t h e t e r m i n a l r e d e fi n i t i o n
i n f o r m a t i o n i s w r i t t e n . I f l f n i s o m i t t e d , fi l e O U T P U T i s a s s u m e d ,
If another file is specified, the changes are implemented when the
fi l e i s l i s t e d o r c o p i e d t o t h e t e r m i n a l .
tCi=Vi
S p e c i fi e s t h e t e r m i n a l c h a r a c t e r i s t i c t o b e c h a n g e d , t c i i s s p e c i
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
n a l c h a r a c t e r i sti c i n ta b l e J-l . It ca n b e a d e ci ma l va l u e , a co d e d
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.
Description
Any alphanumeric character (a character with a display
code in the range from 0 through 44g).
>^P^V
60459680 G
8-9
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
Examples
T R M D E F, I N = P T T h i s c o m m a n d c h a n g e s t h e i n p u t d e v i c e t o a p a p e r t a p e r e a d e r, t h u s
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 timeout
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
i n t h e v a l i d a t i o n fi l e ( r e f e r t o t h e L I M I T S
command). You can also set the subsystem in
your prologue with the SET command.
60459680
G
8 - 11
|
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
c t c t i 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 d e fi n e d f o r t h e t e r m i n a l ( r e f e r t o
the CT command in appendix J). Do not include a space between ct and
x. We show one here only for clarity.
x x can be the letter D, E, or 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 during a terminal session. To detach the job during output, first enter the interrup
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.
0H^\
Examples
T R M D E F, I N = P T T h i s c o m m a n d c h a n g e s t h e i n p u t d e v i c e t o a p a p e r t a p e r e a d e r, t h u s
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 timeout
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.
yf^N
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
i n t h e v a l i d a t i o n fi l e ( r e f e r t o t h e L I M I T S
command). You can also set the subsystem in
your prologue with the SET command.
J $ < f fi s < \
60459680 G
8 - 11 |
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
c c c S p e c i fi e s a c o m m a n d t o b e e x e c u t e d a f t e r t h e s y s t e m e x e c u t e s t h e B A S I C
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
BATCH COMMAND
The BATCH command selects the batch subsystem,
batch subsystem.
You cannot use the RUN command under the
Format:
BATCH,fl
Parameter
fl
Description
S p e c i fi e s t h e i n i t i a l r u n n i n g fi e l d l e n g t h f o r s u b s e q u e n t j o b s t e p s .
Entering this value is equivalent to entering the RFL.fl command
( r e f e r t o s e c t i o n 7 ) . I f fl i s o m i t t e d , 0 i s a s s u m e d . I f y o u
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
c c c S p e c i fi e s o n e c o m m a n d t o b e e x e c u t e d a f t e r t h e s y s t e m e x e c u t e s t h e
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
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.
S AV E , l f n / S S = E X E C U T E
_.
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
TAX the primary file. The file name (TAX) is a valid parameter with the OLD command.
I In this example, the user selects the FORTRAN subsystem and makes a copy of permanent file
8-14
60459680
F
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
c c c S p e c i fi e s a c o m m a n d i n a d d i t i o n t o t h e F T N T S c o m m a n d . A n y v a l i d
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
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
c t c t i 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 d e fi n e d f o r t h e t e r m i n a l ( r e f e r t o
the CT command in appendix J). Do not include a space between ct and
x. We show one here only for clarity.
r ^ ^ \
x x can be the letter D, E, or 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 during a terminal session. To detach the job during output, first enter the interrup
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 fatal error aborts the job.
8-16
60459680
D
0^\
• The job requests input from the terminal or queues output to the terminal.
• T h e j o b e x c e e d s i t s t i m e l i mi t o r SR U l i mi t.
• 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
EXECUTE System is currently processing your command.
IDLE System is waiting for you to enter a command.
WAIT System is waiting for system resources to become available.
60459680 E
8-17
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
a p p l S p e c i fi e s o n e o f t h e f o l l o w i n g N A M a p p l i c a t i o n s :
appl
IAF
Description
Interactive
F a c i l i t y.
I T F I n t e r a c t i v e Tr a n s f e r F a c i l i t y.
MCS Message Control System.
P L AT O P L AT O - N A M I n t e r f a c e .
R B F R e m o t e B a t c h F a c i l i t y.
TA F
Transaction
F a c i l i t y.
T V F T e r m i n a l V e r i fi c a t i o n F a c i l i t y .
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 S p e c i fi e s t h a t a n y c h a r a c t e r s f o l l o w i n g t h e c o m m a n d t e r m i n a t o r a r e
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
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
I f I A F i s y o u r p r i m a r y a p p l i c a t i o n , a p p l s p e c i fi e s a n a p p l i c a t i o n t o
which you wish to be connected. The following are some supported
applications:
appl
Description
ITF
I n t e r a c t i v e T r a n s f e r F a c i l i t y.
MCS
Message Control System.
PLATO
PLATO-NAM Interface.
RBF
Remote Batch Facility.
TAF
T r a n s a c t i o n F a c i l i t y.
TVF
Te r m i n a l Ve r i fi c a t i o n F a c i l i t y.
VEIAF
N O S / V E I n t e r a c t i v e F a c i l i t y.
If IAF is your secondary application, you have the following options
for the appl parameter:
appl
Description
o m i t t e d I f y o u o m i t t h e a p p l p a r a m e t e r, y o u r t e r m i n a l i s
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
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
JSN-jsn
SRU-S
Characters=xxxxx KCHS
IAF
CONNECT
TIME
LOGGED OUT.
hh.mm.ss.
s.sss
hh.mm.ss.
The following describes the variable items in the logout information:
Item
Description
username User name.
h h . m m . s s . Ti m e o f d a y t h i s c o m m a n d w a s e n t e r e d .
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 a c t i v i t y s i n c e l o g i n t o I A F.
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
DIAL COMMAND
The DIAL command sends a one-line message to another terminal user.
Format:
DIAL,jsn,sss
Parameter
jsn
Description
Specifies the job sequence name (JSN) of the terminal to receive the
message.
s s s S p e c i fi e s t h e o n e - l i n e m e s s a g e .
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 |
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
0^\
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
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
fi l e .
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
obtain status information, or
directives. The termination
can be entered only In run
8-22
control mode prompt (**), you can submit a job, drop a job,
temporarily exit from HELL07 using the following HELL07
directive, *E0F directive, *E0P directive, and *E0S directive
mode. All other directives can be entered only in control mode.
60459680
D
iff^SN
Directive
ub2
(termination
directive)
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.
JP\
DROP,J
or
DR.
Drops a SCOPE 2 job prior to normal termination. You can then enter a
status request to determine when drop completion has occurred.
END or E
Disconnects the terminal from HELL07 and drops any SCOPE 2 job active
at the time the END directive is issued.
*EOF
Inserts an end-of-information designator into terminal input data.
*EOP
Inserts an end-of-partition designator into terminal input data.
*EOS
Inserts an end-of-section designator into terminal input data.
EXIT
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.
PROMPT,status
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.
00t\,
Status
\
RESUME or R
Description
ON
The automatic prompt is activated (default).
OFF
The automatic prompt is deactivated.
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
Directive
STATUS or S
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:
jobname
Name of last job submitted to SCOPE 2.
id
Your user ID.
status
I n d i c a t e s t h e s t a t u s o f t h e j o b i d e n t i fi e d b y
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.
S TO P I n d i c a t e s j o b h a s a b o r t e d .
SUBMIT, lfn
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.
/"SSHSv
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
8-24
60459680 D
/g$fSVy
Example:
The sample job below reads interactive input from a terminal and writes the input
i n f o r m a t i o n t o t h e o u t p u t fi l e . T h e s a m p l e j o b i s c o n t a i n e d i n a l o c a l fi l e c a l l e d
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
Source Exif Data:
File Type : PDF
File Type Extension : pdf
MIME Type : application/pdf
PDF Version : 1.3
Linearized : No
Page Count : 818
Creator : ScanSnap Manager
Producer : Mac OS X 10.5.8 Quartz PDFContext
Create Date : 2009:10:21 10:21:55Z
Modify Date : 2009:10:21 10:21:55Z
EXIF Metadata provided by EXIF.tools