NOS_2_Reference_Set_Vol_3_System_Commands_60459680H_Apr87 NOS 2 Reference Set Vol 3 System Commands 60459680H Apr87

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)

(03-28-85)

(12-16-85)

(09-30-86)

H

(04-23-87)

Publication No.

60459680

DESCRIPTION

Manual released. This manual reﬂects 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 reﬂects NOS 2.1 at PSR level 580. This revision Incorporates the MFLINK, MFQUEUE,

SHELL, and new terminal deﬁnition commands; menu-generating procedures and new procedure

directives; support of 885-42 disk drives; as well as numerous usability changes. Because of

extensive changes to this manual, change bars and dots are not used. This manual obsoletes all

previous editions.

Th i s m an u a l re ﬂ e c t s N O S 2 . 2 a t P S R l ev e l 596 . T h i s re v i s i o n i n c o r p or a t e s t h e f ol l o w i n g f e a tu r e s :

enhanced system security; service class assignment by users; a multihost network; full screen

editing; screen mode input for procedures and other applications; an expansion of online help,

including online manuals; equipment status table expansion; project prologues and epilogues; SCOPE 2

station; and the Interactive Transfer Facility (ITF). Because of extensive changes to this manual,

change bars and dots are not used. This revision obsoletes all previous editions.

Th i s ma n u a l r e ﬂ e ct s N OS 2 .3 a t P S R l e ve l 61 7 . T h i s r e vi s i o n i n co r p o ra t e s t h e f o l l o wi n g f e a t u r es :

834 disk subsystem support; 639 magnetic tape unit support; PSU printer support; FSE enhancements;

NOS procedure enhancements, and the following new system commands: BLOCK, EFFECT, ERRMSG, LISTLID,

RECLAIM, REDO, SHOW, and TDU. This manual obsoletes all previous editions.

This manual reﬂects NOS 2.4.1 at PSR level 630. This revision documents the KEY command and the

following new features: support of CYBER 180 Models 840, 850, and 860; 895 disk subsystem support;

5870 Non-Impact Printer support; NOS/VE dual-state support; and NOS procedure enhancements.

This manual reﬂects NOS 2.4.3 at PSR level 647. This revision documents the APPSW command, the RC

terminal deﬁnition command, and the following features: support of CYBER 180 model 990; support of

836 disk subsystem; enhancements to 533/536 printer support; support of CDCNET version 1; disk error

recovery enhancements (ENQUIRE output); AUTO command internal 0003 byte processing.

This manual reﬂects NOS 2.5.1 at PSR level 664. This revision documents the XMODEM and DROPDS

command and the following features: support of print train Images, security enhancements, and

miscellaneous technical corrections.

This manual reﬂects NOS 2.5.2 at PSR level 678. This revision documents support for the Televideo

terminal and the 585 printer, new user messages related to enhancements to tape error recovery,

changes to several procedure directives, and the addition of the .SET directive and the STR, STRB,

and STRD functions.

REVISION LETTERS I. O, Q, S, X AND Z ARE NOT USED.

Address comments concerning this

manual to:

by Control Data Corporation

Printed in the United States of America

Control Data Corporation

Technology and Publications Division

4201 North Lexington Avenue

Saint Paul, MN 55126-6198

or use Comment Sheet in the back of

this manual.

LIST OF EFFECTIVE PAGES

New features, as well as changes, deletions, and additions to information in this manual, are indicated by bars in the margins or by a dot

near the page number if the entire page is affected. A bar by the page number indicates pagination rather than content has changed.

PAGE REV

Front Cover

Inside Front

Cover

Title Page

2

3H-

4 H

5/6 H-

7 H

8 H

9 H

10

11

12 H-

13

14

15 H.

16 H-

17

18 H-

19 E-

20 H-

21 G'

22 H-

1-1

1-2

1-3 H-

1-4 H-

1-5

1-6

2-1

2-2

2-3

2-4

2-5

2-6

2-7

2-8

2-9

2-10

2-11

2-12

2-13

2-14

2-15

2-16

2-17

3-1

3-2

3-3

3-4

3-5

3-6

3-6.1

3-6.2

3-7

3-8

3-9

PAGE

3-10

3-11

3-12

3-13

3-14

3-15

3-16

3-17

3-18

3-19

4-1

4-2

4-3

4-4

4-5

4-6

4-7

4-8

4-9

4-10

4-11

4-12

4-13

4-14

4-15

4 - 1 6

4-17

4-18

4-19

4-20

4-21

4-22

4-22.1

4-22.2

4-23

4-24

4-24.1/4-24.2

4-25

4 - 2 6

4 - 2 7

4 - 2 8

4-29

4-30

4-31

4-32

4-33

4-34

4-34.1

4-34.2

4-35

4 - 3 6

4 - 3 7

4 - 3 8

4-39

4-40

4-40.1/4-40.2

4-41

4-42

REV PAGE

4-43

4-44

4-45

4-46

4-47

4-48

4-49

4-50

4-51

4-52

4-53

4-54

5-1

5-2

5-3

5-4

5-5

5-6

5-7

6-1

6-2

6-3

6-4

6-5

6-6

6-7

6-8

6-8.1/6-8.2

6-9

6-10

6-10.1

6-10.2

6-11

6-12

6-13

6 - 1 4

6-15

6-16

6-16.1

6-16.2

6-16.3

6-16.4

6-17

6-18

6-19

6-20

6-21

6-22

6-23

6-24

6-25

6-26

6-27

6-28

6-29

6-30

6-31

7-1

REV

G

H

D

E

H

D

E

H

D

H

D

E

C

E

D

H

G

H

E

H

D

E

H

F

D

H

D

H

D

H

PA G E

7-2

7-3

7-4

7-5

7-6

7-7

7-8

7-9

7-10

7-11

7-12

7-12.1/7-12.2

7-13

7-14

7-15

7-16

7-16.1/7-16.2

7-17

7 - 1 8

7-19

7-20

7-21

7-22

7-22.1/7-22.2

7-23

7-24

7-25

7-26

7-27

7-28

7-29

7-30

7-31

7-32

7-33

7-34

7-35

7-36

7-37

7-38

7-39

7-40

7-41

7-42

7-43

7-44

7-45

7 - 4 6

7 - 4 7

7 - 4 8

7 - 4 9

7 - 5 0

7-51

7-52

7-53

7-54

7-55

7-56

REV

H

D

H

D

E

D

G

D

H

D

E

F

E

H

D

G

D

F

E

D

E

D

F

D

PAGE

7-57

7-58

7-59

7-60

7-61

7-62

7-63

7-64

7-65

7-66

7-67

7-68

REV

7-69

7-70

7-71

7-72

7-73

7-74

7-75

7-76

8-1

8-2

8-3

8-4

8-5

8-6

8-6.1

8-6.2

8-7

8-8

8-8.1/8-8.2

8-9

8-10

8-11

8-12

8-13

8-14

8-15

8-16

8-17

8-18

8-19

8-20

8-20.1/8-20.2

8-21

8-22

8-23

8-24

8-25

8-26

8-27

8-28

8-29

8-30

8-31

8-32

8-33

8-34

60459680 H

PAGE REV

8-35

8-36

8 - 3 7

8-38

8 - 3 9

8-40

8-41

8-42

8-43

8-44

8 - 4 5

8-46

8 - 4 7

8 - 4 8

8 - 4 9

8 - 5 0

8-51

8 - 5 2

9 - 1

9 - 2

9 - 3

9 - 4

9 - 5

9 - 6

9 - 7

9 - 8

9-9

9-10

9 - 11

9 - 1 2

9 - 1 3

9 - 1 4

9 - 1 5

9 - 1 6

9 - 1 7

9-18

9-19

9-20

9-21

9-22

9 - 2 3

9 - 2 4

9 - 2 5

9 - 2 6

9 - 2 7

9-28

9-29

9-30

9-31

9 - 3 2

9 - 3 3

9 - 3 4

9-35

9-36

9-37

9-38

9-39

9-40

9-41

9-42

9-43

9-44

9 - 4 5

9-46

9-47 F.

9-48

9-48.1

9-48.2

9 - 4 9

9-50

9 - 5 1

PAGE REV

9 - 5 2

9 - 5 3

9 - 5 4

9 - 5 5

9 - 5 6

9 - 5 7

9 - 5 8

9 - 5 9 D.

9 - 6 0 H.

9 - 6 1

9 - 6 2

9 - 6 3

9 - 6 4

9 - 6 5

9 - 6 6

9-67

9 - 6 8

10-1

1 0 - 2

1 0 - 3

10-4

10-4.1/10-4.2 H-

10-5

10-6

10-7

10-8

10-8.1/10-8.2

10-9

10-10

10-11

10-12

10-13

10-14

10-15

10-16

10-17

10-18

10-19

10-20

10-21

10-22

10-22.1/

10-22.2

10-23

10-24

10-25 H-

10-26 H-

10-27

10-28

10-29

10-30

10-31

10-32

10-33 D.

10-34 H'

10-35 H-

10-36

10-37

10-38

10-38.1

10-38.2 H-

10-39

10-40

10-41 H-

10-42

10-43

10-44

10-44.1/

10-44.2 H •

10-45

10-46

PAGE REV

10-47

10-48

10-49

11-1

11 - 2

11 - 3

11 - 4

11 - 5

11 - 6

11-6.1/11-6.2

11 - 7

11 - 8

11 - 9

11-10

12-1

1 2 - 2

1 2 - 3

1 2 - 4

1 2 - 5

1 2 - 6

1 2 - 7

1 2 - 8

1 2 - 9

12-10

12-10.1/

12-10.2

12-11

12-12

12-13

12-14

12-15

12-16

12-16.1/

12-16.2

12-17

12-18

12-19

12-20

12-21 H-

12-22

12-23

12-24

12-25

12-26

13-1

1 3 - 2

13-3

13-4

14-1

14-2

14-3

14-4

14-5

14-6

14-7

14-8

1 4 - 9

14-10

14-11

14-12

14-13

14-14

14-15

14-16

14-17

14-18

14-19

1 5 - 1

15-2

1 5 - 3

1 5 - 4

PAGE REV

1 5 - 5

1 5 - 6

15-7

1 5 - 8

15-9

15-10

15-11

15-12

15-13

15-14

15-15

15-16

15-17

15-18

15-19

15-20

15-20.1/

15-20.2

15-21

15-22

15-23

15-24

15-25

15-26

15-27

15-28

15-29

15-30

15-31

15-32

15-33

15-34

15-35

15-36

15-37

15-38

15-39

15-40

15-41

15-42

15-43

15-44

15-45

1 6 - 1

1 6 - 2

16-3

1 6 - 4

16-5

1 6 - 6

1 6 - 7

1 6 - 8

1 6 - 9

A-l

A - 2

A - 3

A - 4

A - 5

A - 6

A - 7

A - 8

A - 9

A-10

A-ll

A- 12

A-13

A- 14

A- 15

B-l

B - 2

B - 3

B - 4

PAGE REV

B-5

B - 6

B - 7

B - 8

B - 9

B- 10

B-ll

B- 12

B- 13

B- 14

B- 15

B- 16

B- 17

B- 18

B- 19

B- 20

B- 21

B- 22

B- 23

B- 24

B- 25

B- 26

B- 27

B- 28

B- 29

B- 30

B-31

B- 32

B-33

B-34

B- 35

B-36

B- 37

B-38

B- 39

B-40

B- 41

B- 42

B- 43

B- 44

B- 45

B- 46

B- 47

B- 48

B- 49

B- 50

B- 51

B- 52

B-5 3

B- 54

B- 55

B- 56

B-57

B-58

B-5 9

B-60

B- 61

B-62

B-63

B-64

B-65

B-66

B- 67

B- 68

B- 69

B- 70

B- 71

B-7 2

B- 73

B-7 4

B- 75

.^T^osX

-■^^^v

60459680 H

PAGE REV

B-76

C-l

C-2

C-3

C-4

C-5

C-6

C-7

C-8

C-9

C-10

C-ll

C-12

C-13

C-14

C-15

D-l

D-2

D-3

D-4

E-l

E-2

F-l

F-2

F-3

F-4

F-5

F-6

F-7

G-l

G-2

G-3

G-4

G-5

G-6

G-7

G-8

G-9

G-10

G-ll

H-l

H-2

H-3

H-4

H-4.1

H-4.2

H-5

H-6

H-7

H-8

H-9

1-1

1-2

1-3

1-4

J-l

J-2

J-3

J-4

J-5

J-6

J-7

J-8

J-9

J-10

J-ll

J-12

J-13

J-14

J-15

J-16

PAGE REV

J-17

J-18

J-19

J-20

J-21

J-22

J-23 H-

J-24

J-25 H-

J-26

J-27 H-

J-28

J-29

J-30

K-l

K-2

L-l

L-2

L-3

L-4

L-5

L-6

L-7

L-8

L-9

M-l

M-2

M-3

M-4

M-5

M-6

M-7

M-8

M-9

N-l H-

N-2

0-1

0-2 H-

0-3

P-l

P-2

P-3

P-4

P-5

P-6

P-7

P-8

Index-1

Index-2

Index-3

Index-4

Index-5

Index-6

Index-7

Index-8

Index-9

Index-10

Index-11

Index-12

Index-13

Index-14

Index-15

Index-16

Comment Sheet

Inside Back

Cover

Back Cover

PAGE REV PAGE REV PAGE

J$$0&\

60459680 H 5/6

/^%

PREFACE

^^s

4$$$!\

This manual describes the Network Operating System (NOS) Version 2. NOS can operate on the

following computer systems:

CDC CYBER 180 Computer Systems

Models 810, 830, 835, 840, 845, 850, 855, 860, 870, 990, and 995

CDC CYBER 170 Computer Systems

Models 171, 172, 173, 174, 175, 176, 720, 730, 740, 750, 760, 815, 825, 835, 845, 855,

865, and 875

CDC CYBER 70 Computer Systems

Models 71, 72, 73 and 74

6000 Computer Systems

AUDIENCE

Volume 1, Introduction to Interactive Usage (60459660), is written for the novice.

Volume 2, Guide to System Usage (60459670), is written for the applications or systems

programmer who is unfamiliar with NOS.

Volume 3, System Commands (60459680), is written for all NOS users.

Volume 4, Program Interface (60459690), is written for the experienced COMPASS applications

programmer or systems programmer.

The reader of each volume should have a knowledge of the material contained in the previous

volumes.

ORGANIZATION

The NOS reference set describes the external features of NOS 2. This reference set

comprises four separate volumes.

Volume 1, Introduction to Interactive Usage, shows a user at an interactive terminal how to

enter, run, and correct programs, and how to create, retrieve, and maintain permanent

ﬁles. Other topics covered include physical terminal connection, and login/logout

procedures.

Volume 2, Guide to System Usage, describes the general concepts of NOS and some of the

utilities used with NOS. Topics included are job processing, ﬁle concepts, procedures,

magnetic tape processing, Modify, and ﬁle 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 speciﬁc improvements, and to report any errors. If the

comment sheet has already been used, you can mail your comments to:

Control Data Corporation

Publications and Graphics Division ARH219

4201 Lexington Avenue North ^^

St. Paul, MN 55112 "^

Additionally, if you have access to SOLVER, an online facility for reporting problems, you

can use it to submit comments about the manual. Declare your problem type as DOC and use

NS2 as the product identiﬁer.

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

ﬁnd that the product does not perform as described, call us at one of the following numbers

and a support analyst will work with you.

From USA and Canada: (800) 345-9903

Fro m ot her c ou n tr ie s: (61 2) 8 51- 41 31

The preceding numbers are for help on product usage. Address questions about physical

packaging and/or distribution of printed materials to Literature and Distribution Services

at the following address:

Control Data Corporation

Literature and Distribution Services

308 North Dale Street

St. Paul, Minnesota 55103

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

CONVENTIONS

REFERENCES TO OTHER MANUALS IN THE NOS REFERENCE SET

Throughout this manual, references to Volumes 1, 2, and 4 of the NOS Reference Set are in

the form: refer to section n, (volume name). If a volume number is not speciﬁed, the

reference is to Volume 3.

60459680 H

/pifev

/p*V

180-CLASS MAINFRAMES

Some of the CYBER 170 Computer Systems share many of the functional and architectural

attributes of the CYBER 180 Computer Systems. Speciﬁcally, CYBER 170 Models 815, 825, 835

845, and 855 fall into this category. It is sometimes convenient to refer to the'cYBER 180'

models and these CYBER 170 models collectively. This manual uses the term 180-class

mainframes to refer to this collection.

EXTENDED MEMORY

Extended memory for model 176 is large central memory extended (LCME). Extended memory for

the 180-class mainframes and the models 865 and 875 is uniﬁed 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 speciﬁed. Uppercase

characters represent terminal output; lowercase characters represent user input

unless otherwise noted. (However, user input that is displayed within the text of

this manual is shown in uppercase characters). The vertical spacing in examples

does not necessarily coincide with the spacing that appears on your terminal.

• Program examples are written either in FORTRAN 5 or BASIC 3 (hereafter referred to

as just BASIC).

• This manual uses commas to delimit command parameters and periods to terminate y

commands. For clarity, however, commands that appear in text use an opening

parenthesis for their initial delimiter and a closing parenthesis for their

terminator.

COMMAND FORMAT

Interpret uppercase characters within command formats literally. Lowercase characters are

variables and are described immediately following the line that shows the command format.

SPECIAL KEYBOARD ENTRIES

This manual uses special notation to represent certain keyboard entries:

• @ denotes the message transmission key on the keyboard. Depending on the terminal

class, this key may be the RETURN, CR, CARRIAGE RETURN, NEW LINE, SEND, or ETX key.

For some terminal classes, the RETURN or NEW LINE key also denotes a message

terminator, but the message is kept in the terminal buffer until the corresponding

SEND or ETX key is pressed, sending all messages in the buffer to IAF. Appendix K

supplies more information. IAF and the network respond to the @) by positioning the

carriage to the ﬁrs t chara cter po sitio n on the ne xt l ine.

• ■•—designates the backspace character.

• The notation CTRL/x directs you to press the control key (which is labeled CTRL,

CNTL, CNTRL, or similar characters) on the terminal and, while holding this key

down, press the key speciﬁed 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 ofﬁces or Control Data Literature

Distribution Services (308 North Dale, St. Paul, Minnesota 55103).

If you need a brief description of the product commands and their parameters, you should

refer to the NOS 2 Applications Programmer's Instant.

Control Data Publication

APEX IV Reference Manual

APL Version 2 Reference Manual

APT IV Version 2 Reference Manual

BASIC Version 3 Reference Manual

CDCNET Conceptual Overview

CDCNET Terminal Interface Usage Manual

COBOL Version 5 Reference Manual

Common Memory Manager Version 1 Reference Manual

COMPASS Version 3 Reference Manual

Conversion Aids System Version 2 Reference Manual

CYBER Database Control System 2 Database Administrator

Reference Manual

CYBER Database Control System Version 2 Application

Programming Reference Manual

CYBER Interactive Debug Version 1 Reference Manual

CYBER Loader Version 1 Reference Manual

Publication Number

84002550

60454000

17326900

19983900

60461540

60463850

60497100

60499200

60492600

19265358

60485200

60485300

60481400

60429800

60459680 H 11 I

Control Data Publication Publication Number

CYBER Record Manager Advanced Access Methods Version 2

Reference Manual

CYBER Record Manager Basic Access Methods Version 1.5

Reference Manual

CYBER 70 Model 71 Computer System Hardware Reference Manual

CYBER 70 Model 72 Computer System Hardware Reference Manual

CYBER 70 Model 73 Computer System Hardware Reference Manual

CYBER 70 Model 74 Computer System Hardware Reference Manual

CYBER 170 Computer Systems Models 171 through 175

(Levels A, B, C) Model 176 (Level A) Hardware Reference Manual

CYBER 170 Computer Systems Models 720, 730, 740, 750, and 760,

Model 176 (Level B/C) Hardware Reference Manual

CYBER 170 Computer System Model 825

Hardware Reference Manual

CYBER 170 Computer Systems Models 835, 845, and 855

Hardware Reference Manual

CYBER 170 Computer Systems Models 865 and 875

Hardware Reference Manual

Data Base Utilities Version 1 Reference Manual

Data Catalogue 2 Reference Manual

DDL Version 3 Reference Manual, Volume 1

DDL Version 3 Reference Manual, Volume 2

DDL Version 3 Reference Manual, Volume 3

FORM Version 1 Reference Manual

FORTRAN Common Library Mathematical Routines Reference Manual

FORTRAN Data Base Facility Version 1 Reference Manual

FORTRAN Extended Version 4 Reference Manual

FORTRAN Extended Version 4 to FORTRAN Version 5 Conversion

Aids Program Version 1 Reference Manual

FORTRAN Version 5 Common Library Mathematical Routines

Reference Manual

FORTRAN Version 5 Reference Manual

General Purpose Simulation System V (GPSS)

General Information Manual

60499300

60495700

60453300

60347000

60347200

60347400

60420000

60456100

60469350

60469290

60458920

60498800

60483200

60481900

60482000

60482100

60496200

60498200

60482200

60497800

60483000

60483100

60481300

84003900

I 12 60459680 H

Control Data Publication

Information Management Facility Version 1 Application

Programming Reference Manual

Message Control System Version 1 Reference Manual

Modify Version 1 Reference Manual

Network Access Method Version 1/Communications Control

Program Version 3 Terminal Interfaces Reference Manual

Network Access Method Version 1

Host Application Programming Reference Manual

Network Access Method Version 1 Network

Deﬁnition Language Reference Manual

NOS Full Screen Editor User's Guide

NOS Version 2 Administration Handbook

NOS Version 2 Application Installation Handbook

NOS Version 2 Applications Programmer's Instant

NOS Version 2 Diagnostic Index

NOS Version 2 Installation Handbook

NOS Version 2 Network Terminal User's Instant

NOS Version 2 Operator/Analyst Handbook

NOS Version 2 Reference Set, Volume 1,

Introduction to Interactive Usage

NOS Version 2 Reference Set, Volume 2, Guide to System Usage

NOS Version 2 Reference Set, Volume 4, Program Interface

NOS Version 2 Security Administrator's Handbook

NOS Version 2 System Maintenance Reference Manual

NOS Version 2 System Overview

NOS Version 2 Systems Programmer's Instant

NOS Version 2 Tape Management System (TMS) User Reference Manual

On-Line Maintenance Software Reference Manual

Pascal Version 1.1 Reference Manual

PERT/Time Version 2 Reference Manual

Query Update Version 3 Reference Manual

Publication Number

60484500

60480300

60450100

60480600

60499500

60480000

60460420

60459840

84002760

60459360

60459390

60459320

60459380

60459310

60459660

60459670

60459690

60460410

60459300

60459270

60459370

60463110

60454200

60497700

60456030

60498300

60459680 H 13

Control Data Publication

Remote Batch Facility Version 1 Reference Manual

Remote Host Facility Access Method Reference Manual

Remote Host Facility Usage

SORT/MERGE Version 5 Reference Manual

SYMPL Version 1 Reference Manual

TAF/CRM Data Manager Version 1 Reference Manual

TAF Version 1 Reference Manual

TAF Version 1 User's Guide

Text Editor Version 1 Reference Manual

TOTAL-CDC Version 2 Reference Manual

Update Version 1 Reference Manual

XEDIT Version 3 Reference Manual

5870 Printer User's Reference Manual

6000 Series Computer Systems Hardware Reference Manual

8-Bit Subroutines Reference Manual

Publication Number

60499600

60459990

60460620

60484800

60496400

60459510

60459500

60459520

60436100

76070300

60449900

60455730

60462720

60100000

60495500

DISCLAIMER

This product is intended for use only as

described in this document. Control Data

cannot be responsible for the proper

functioning of undescribed features or

undeﬁned parameters.

I " 60459680 H

CONTENTS

/0$£\

0l^f\

1. SYSTEM DESCRIPTION

System Hardware

Central Processor Unit

Central Memory

Job Field Length

Central Memory Resident

Extended Memory

Peripheral Processors

Peripheral Equipment

System Software

User Programs

Operating System

CYBER Loader

CYBER Record Manager

2. FILES

1-1

1-2

1-3

1-4

1-5

1-6

2-1

File Names 2-1

File Structure 2-1

CYBER Record Manager File Structure 2-3

NOS File Structure 2-3

Physical File Structure 2-4

Card Files 2-6

Mass Storage Files 2-6

Magnetic Tape Files 2-7

File Types 2-11

Input Files 2-11

Queued Files 2-11

Local Files 2-12

Primary Files 2-13

Direct Access Files 2-13

Library Files 2-13

Permanent Files 2-13

Indirect Access Permanent Files 2-14

Direct Access Permanent Files 2-14

Mass Storage File Residence 2-15

Family Devices 2-15

Auxiliary Devices 2-16

Alternate Storage Subsystems 2-16

Libraries 2-17

User Name Library 2-17

Program Libraries 2-17

User Libraries 2-17

3. JOB FLOW AND EXECUTION 3-1

Job Initia ti on and Terminati on 3-1

Batch Jobs 3-1

Interactive Jobs 3-2

Login 3-2

Logout and Application

Switching Procedure 3-4

Submitting Jobs to Remote Hosts 3-6

Job Origin Types 3-6.2

Job Service Classes 3-6.2

Job Names 3-7

Job Sequence Name (JSN) 3-7

User Job Name (UJN) 3-8

Validation 3-8

Accounting 3-8

Job Scheduling 3-9

Job Control 3-9

Field Length Control 3-9

Input File Control 3-11

Time Limit Control 3-11

SRU Limit Control 3-11

Command Limit Control 3-11

Rollout Control 3-12

Error Control 3-12

Security Features 3-13

Memory Protection 3-13

System and File Access Controls 3-13

Security Access Levels 3-14

Security Access Catagories 3-16

Responsibilities for Data Security 3-16

Security Conﬂict Processing 3-17

Job Completion 3-17

4. PROCEDURES 4-1

Procedure File Residence and Search

Order 4-2

Procedure Structure 4-2

Procedure Processing 4-3

Interactive Parameter Entry 4-4

Procedure Expansion 4-4

.EXPAND Directive 4-6

Inhibit Character 4-6

Concatenation Character 4-8

.EX Directive 4-9

Execution of the Command Record 4-9

Procedure Directives 4-9

Procedure Header (.PROC) Directive 4-11

Interactive Format 4-11

Checklist Entries 4-13

Special Values 4-14

60459680 H 15 |

Checklist Patterns 4-16

Menu Format 4-22

Formatting and Help Directives 4-23

.CORRECT Directive 4-23

.ENDHELP Directive 4-24

.ENTER Directive 4-24

.Fn Directive 4-24.1

.HELP Directive 4-25

.NOCLR Directive 4-31

.NOTE Directive 4-31

.PAGE Directive 4-32

.PROMPT Directive 4-32

Expansion Control Directives 4-33

.CC Directive 4-33

.EXPAND Directive 4-33

.IC Directive 4-33

.SET Directive 4-34

File Directives 4-34.1

.DATA Directive 4-34.1

. E O F ( o r . E O P ) D i r e c t i v e 4 - 3 8

.EOR (or .EOS) Directive 4-38

Branching Directives 4-38

.ELSE Directive 4-38

.ENDIF Directive 4-39

.EX Directive 4-39

.IF (or .IFE) Directive 4-40

.COMMENT (.*) Directive 4-40.1

Calling a Procedure (BEGIN Command) 4-41

Requesting Help on Procedure Calls 4-46

Ending a Procedure (REVERT Command) 4-51

Parameter Matching Modes 4-53

Order-Dependent Mode 4-53

Order-Independent Mode 4-53

5. COMMAND PROCESSING 5-1

Command Format 5-2

Command Processing Flow 5-5

Exit Processing 5-7

6. FLOW CONTROL COMMANDS 6-1

Command Syntax 6-2

Operators 6-2

Arithmetic Operators 6-2

Relational Operators 6-3

Logical Operators 6-4

String Operators 6-4

Order of Evaluation 6-5

Operands 6-5

Constants 6-5

Numeric Strings 6-5

Literals 6-5

Symbolic Names 6-7

Functions 6-12

FILE Function 6-12

DT Function 6-14

LEN Function 6-16

NUM Function 6-16

STR Function 6-16.1

STRB Function 6-16.2

STRD Function 6-16.3

Command Descriptions 6-16.3

BEGIN Command 6-16.3

DISPLAY Command 6-16.4

ELSE Command 6-17

ENDIF Command 6-18

ENDW Command 6-19

EXIT Command 6-19

IF (or IFE) Command 6-20

MODE Command 6-22

NOEXIT Command 6-24

ONEXIT Command 6-24

REVERT Command 6-24

SET Command 6-25

SKIP Command 6-30

WHILE Command 6-31

7. JOB CONTROL COMMANDS 7-1

BLOCK Command 7-2

CFO Command 7-3

CHARGE Command 7-4

CHVAL Command 7-5

CLASS Command 7-7

COMMENT Command 7-9

CTIME Command 7-10

DAYFILE Command 7-10

DROP Command 7-12.1

ENQUIRE Command 7-13

ENTER Command 7-21

ERRMSG Command 7-22

GO Command 7-22

HTIME Command 7-22.1

Job Command 7-23

LDI Command 7-26

LENGTH Command 7-27

LIMITS Command 7-28

Resource Limits 7-29

Other Characteristics 7-30

User Permissions 7-31

Network Applications 7-32

Local Applications 7-32

Privileged Network Applications 7-32

Shell Permissions 7-32

Security Permissions 7-33

Security Access Categories 7-33

Security Access Levels 7-33

Service Classes 7-33

Default Service Classes 7-33

LISTLID 7-36

16 60459680 H

/*^^\

MACHINE Command 7-39

MFL Command 7-39

NORERUN Command 7-40

NOTE Command 7-40

OFFSW Command 7-41

ONSW Command 7-42

PASSWOR Command 7-42

PAUSE Command 7-44

PROTECT Command 7-44

QGET Command 7-45

QUEUE7 Command 7-46

RERUN Command 7-50

RESOURC Command 7-50

Deadlock Prevention 7-52

Single Resource Use 7-54

Tape Units 7-54

Resource Overcommitment 7-55

Altering Resource Requirements 7-56

Unit Assignment 7-57

RFL Command 7-57

ROLLOUT Command 7-58

RTIME Command 7-58

SETASL Command 7-59

SETCORE Command 7-60

SETJAL Command 7-61

SETJOB Command 7-62

SETJSL Command 7-63

SETPR Command 7-64

SETTL Command 7-64

SHELL Command 7-66

STIME Command 7-67

SUBMIT Command 7-68

SWITCH Command 7-73

UPROC Command 7-73

USECPU Command 7-74

USER Command 7-74

8. COMMANDS FOR INTERACTIVE JOBS 8-1

Terminal Control Commands 8-2

ASCII Command 8-2

AUTO Command 8-3

BRIEF Command 8-4

CSET Command 8-4

EFFECT Command 8-4

KEY Command 8-5

LINE Command 8-6.1

NORMAL Command 8-7

SCREEN Command 8-7

TDU Command 8-8.1

TIMEOUT Command 8-9

TRMDEF Command 8-9

Using TRMDEF with NAM/CDCNET 8-10

Examples 8-11

Subsystem Selection Commands 8-11

ACCESS Command 8-12

BASIC Command

BATCH Command

EXECUTE Command

FORTRAN Command

FTNTS Command

NULL Command

Interactive Status Commands

Detach Command (ctD)

Immediate Job Status

Command (ctE)

Abbreviated Job Status

Command (ctS)

Job Processing Commands

APPSW Command

BYE Command

DIAL Command

EXPLAIN Command

GOODBYE Command

HELLO Command

HELL07 Command

HELL07 Directives

HELP Command

HELPME Command

LIB Command

LIST Command

LOGIN Command

LOGOUT Command

NOSORT Command

RECOVER Command

REDO Command

RUN Command

Secure Login Command

SHOW Command

TEXT Command

WHATJSN Command

X Command

XMODEM Command

Primary File Editing Commands

Parameter Format

Suppressing Editing Responses

Line Number Overlap

Inserting Lines

ALTER Command

DELETE Command

DUP Command

LIST Command

MOVE Command

READ Command

RESEQ Command

WRITE Command

WRITEN Command

9. FILE MANAGEMENT COMMANDS

ASSIGN Command

BKSP Command

8-12

8-13

8-14

8-15

8-16

8-17

8-18

8-19

8-20.1

8-21

8-22

8-26

8-28

8-29

8-30

8-34

8-35

8-36

8-37

8-38

8-39

8-40

8-41

8-42

8-44

8-45

8-46

8-48

8-49

8-51

8-52

9-1

9-2

9-4

60459680 H 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

9-5 DEFINE Command 10-17

9-5 GET Command 10-20

9-10 DROPDS Command 10-21

9-10 MFLINK Command 10-22

9-10 MFLINK Directives 10-23

9-11 APPEND Directive 10-24

9-12 ATTACH Directive 10-24

9-13 CHANGE Directive 10-24

9-15 CHARGE Directive 10-25

9-16 DEFINE Directive 10-25

9-17 DROPDS Directive 10-25

9-18 GET Directive 10-25

9-20 PACKNAM Directive 10-25

9-22 PERMIT Directive 10-26

9-23 PURGE Directive 10-26

9-26 REPLACE Directive 10-26

9-26 SAVE Directive 10-26

9-27 USER Directive 10-26

9-31 Interactive Use of MFLINK 10-27

9-31 OLD Command 10-28

9-33 PACKNAM Command 10-29

9-34 PERMIT Command 10-30

9-35 PURGALL Command 10-31

9-35 PURGE Command 10-32

9-36 RECLAIM Command 10-33

9-37 Magnetic Tapes 10-34

9-37 Command Format 10-35

9-38 RECLAIM Output 10-44

9-40 REPLACE Command 10-45

9-42 SAVE Command 10-46

9-43 SETPFAC Command 10-48

9-44 SETPFAL Command 10-49

9-44

9-50

9-51

9-54 11. LOAD/DUMP MEMORY COMMANDS 11-1

9-55

9-56 DMB Command 11-1

9-56 DMD Command 11-5

9-57 DMDECS Command 11-6

9-57 DMP Command 11-6.1

9-58 DMPECS Command 11-7

9-58 LBC Command 11-8

9-59 LOC Command 11-8

9-62 PBC Command 11-9

9-64 RBR Command 11-9

9-65 WBR Command 11-10

9-65

9-68

9-68 12. TAPE MANAGEMENT 12-1

10. PERMANENT FILE COMMANDS

Common Parameters

APPEND Command

ATTACH Command

CATLIST Command

CHANGE Command

COMMON Command

18

Tape Assignment

10-1 Command Rules

Processing Options

10-2 ASSIGN Command

10-7 BLANK Command

10 -7 LAB EL C omm and

10-10 LISTLB Command

10-15 REQUEST Command

10-16 VSN Command

12-1

12-2

12-3

12-5

12-9

12-11

12-19

12-21

12-25

60459680 H

13. CHECKPOINT/RESTART 13-1

CKP Command 13-1

RESTART Command 13-2

14. SYSTEM UTILITY COMMANDS 14-1

EDIT Command 14-1

FSE Command 14-2

KRONREF Command 14-4

MODIFY Command 14-5

OPLEDIT Command 14-8

PDU Command 14-10

PROFILE Command 14-11

UPDATE Command 14-14

XEDIT Command 14-18

15. LIBRARY MAINTENANCE 15-1

Library File Access Methods 15-1

Library Record Types 15-2

CATALOG Command 15-5

C O P Y L a n d C O P Y L M C o m m a n d s 1 5 - 7

GTR Command 15-11

ITEMIZE Command 15-14

LIBEDIT Command 15-17

Command Format 15-18

LIBEDIT Directives 15-20

ADD Directive 15-23

BEFORE Directive 15-24

BUILD Directive 15-24

COMMENT Directive 15-25

COPY Directive 15-25

DATE Directive 15-25

DELETE Directive 15-26

FILE Directive 15-26

IGNORE Directive 15-27

INSERT or AFTER Directive 15-27

LIBGEN Directive 15-28

LIST Directive 15-28

NEW Directive 15-28

NOINS Directive 15-28

NOREP Directive 15-29

NOREW Directive 15-29

OLD Directive 15-29

RENAME Directive 15-29

REPLACE Directive 15-30

REWIND Directive 15-30

TYPE or NAME Directive 15-31

VFYLIB Directive 15-31

LIBEDIT Output 15-31

LIBGEN Command 15-32

ULIB Command 15-34

VFYLIB Command 15-35

Library Processing Examples 15-37

LIBRARY Command 15-43

Maximum Size of Global Library

Set 15-43

Library Search Order 15-44

Examples 15-44

1 6 . T E R M I N A L I N P U T / O U T P U T 1 6 - 1

Terminals 16-1

Input/Output Conventions 16-2

Input From Terminal 16-2

Length of Output/Input Lines 16-3

Terminating Input Line 16-3

Correcting Input Line 16-3

Deleting Input Line 16-4

E n t e r i n g I n p u t B e f o r e P r o m p t s 1 6 - 4

Page Wait 16-5

Suspending Output 16-5

Aborting Output Block 16-5

Interrupting Job Step 16-6

Terminating Job Step 16-6

Continuing a Suspended Job 16-7

Using ATTN on IBM 2741 Terminals 16-8

Control Bytes 16-9

APPENDIXES

A. CHARACTER SETS

Character Set Anomalies

Character Set Tables

Interactive Jobs

Batch Jobs

Jobs Using Line Printers

Jobs Using Magnetic Tape:

A-l

A-2

A-3

A-l 2

D. SAMPLE JOB OUTPUT

TERMINAL CHARACTER CONVERSION

Data Input

Data Output

D-l

E-l

E-2

B. DIAGNOSTIC MESSAGES

C. GLOSSARY

B-l

C-l

F. CARD FILE DATA CONVERSION

Input Card File Formats

Coded Cards

Conversion Modes

F-l

F-2

F-3

60459680 E 19

/^s^\

Literal Input F-3 (AR)

Binary Cards F-5 Re

Summary F-5 (BF)

Punch File Formats F-5 (BR)

Coded Cards (Punch) F-6 (BS)

Binary Cards (Punch B) F-6 (Bl)

Absolute Binary Cards (P8) F-7

(AR) - Automatic Character

Recognition

(BF) - Blocking Factor

G . A N S I T A P E L A B E L F O R M A T S G - l

Required Labels G-l

VOL 1 - Volume Header Label G-2

HDR1 - First File Header Label G-4

E0F1 - First End-Of-File Label G-8

E0V1 - First End-Of-Volume Label G-9

Optional Labels G-10

HDR2 through HDR9 - Additional

File Header Labels G-10

E0F2 through E0F9 - Additional

End-Of-File Labels G-10

E0V2 through E0V9 - Additional

End-Of-Volume Labels G-10

User Labels G-ll

H. LINE PRINTER CARRIAGE CONTROL H-l

Printed Data H-l

Paper Length H-l

580 Line Printers H-l

| 533/536 and 585 Printers H-2

Carriage Control H-2

Format Channel Selection on

I Non-PFC Printers H-4.2

Format Channel Selection on

| 533/536 Printers H-4.2

Carriage Control Arrays H-7

Array Syntax H-7

I Reserved Format Channels H-9

Example H-9

I. OBSOLETE TAPE FORMATS 1-1

B (Blocked) Format 1-1

E (Line Image) Format 1-2

X (External) Format 1-3

End-of-Tape/End-of-Reel Conditions 1-3

J. NAM/CCP TERMINAL DEFINITION

COMMANDS J-l

Introduction J-l

Terminal Deﬁnition Command Format J-3

Restrictions J-4

Terminal Deﬁnition Commands J-4

(AB) - Abort Output Block

Character J-5

(HD)

(HN)

(HS)

K.

Break Key as User Break 1

Backspace Character

I n t e r r u p t i o n o r

User Break 1 Character

(B2) - Termination or

User Break 2 Character

(CH) - Display Terminal

Characteristics

(CI) - Carriage Return Idle Count

(CN) - Cancel Character

(CP) - Cursor Positioning after

Input

(CT) - Network Control Character

(DL) - Delimiters for Single-

Message Transparent Input Mode

(EB) - End-of-Block Character

(EL) - End-of-Line Character

(EP) - Echoplex Mode

(FA) - Full-ASCII Input Mode

(HC) - Host Connection

- Display of Host Nodes

- Host Node Selection

- Host Selection

(IC) - Flow Control for Input

Devices

(IN) - Input Device and

Transmission Mode

(LI) - Line Feed Idle Count

(LK) - Lockout of Unsolicited

Messages

(MS) - Message to Network

Operator

(OC) - Flow Control for Output

Devices

(OP) - Output Device Selection

(PA) - Parity Processing

(PG) - Page Waiting

(PL) - Page Length

(PW) - Page Width

(RC) - Reset Terminal

Characteristics

(SE) - Special Editing Mode

(TC) - Terminal Class Command

(TM) - Terminating a Terminal-

Host Connection

(XL) - Multimessage Transparent

Mode

DELIMITING AND TRANSMITTING

TERMINAL INPUT

Physical End-of-Line (Line Feed)

Logical End-of-Line (Carriage Return)

Message Transmission

J-5

J-6

J-7

J-8

J-9

J-10

J-ll

J-l 2

J-13

J-14

J-15

J-17

J-18

J-20

J-21

J-2 2

J-23

J-24

J-25

J-26

J-27

K-l

20 60459680 H

jgg^N.

0^\

V

L. PASSIVE PROCEDURES L-l 0. INTERACTIVE TRANSFER FACILITY (ITF) 0-1

.PROC Directive L-l

Procedure and Parameter Descriptions L-2

Parameter Matching L-2

Order-Dependent Parameter

Matching Mode L-2

Order-Independent Parameter

Matching Mode L-6

Selecting the ITF Application

Selecting a Remote CYBER 200 System

Processing Your Job on the

Remote CYBER 200

Terminating Your ITF Session

P. FILE TRANSFERS USING XMODEM

0-1

0-2

P-l

M. PAPER TAPE OPERATIONS

General Description

Teletypewriter

Control Characters

Input Lines

Punching Tape Off-Line

Tape Mode

Punching a Tape On-Line

Corrections

M-l XMODEM Command

Using XMODEM in Prompting Mode

M-l Sending a File from a CYBER

M-l Receiving a File from a Micro

M-2 Conﬁguration File

M-2 File Transfer Notes

M-3 Text Files

M-3 CYBER Binary

M-4 Micro Binary

M-4 Limitations and Considerations

P-l

P-3

P-4

P-6

P-7

N. MASS STORAGE DEVICE STATISTICS N-l

INDEX

1-1 Central Memory Allocation

2-1 Logical Structure of Files

2-2 NOS and CRM File Terminology

2-3 Sample Card File Structure

2-4 Use of ANSI Labels

3-1 FORTRAN Compile and Execute Deck

3-2 Submitting Jobs to Remote Hosts

4-1 Procedure File Structure

4-2 TESTPN with Valid Entry

4-3 TESTPN with Invalid Entry

4-4 Summary of Checklist Entries

4-5 Calling a Procedure

5-1 Command Processing Flow

7-1 QUEUE7 Execute Queue Sample

Listing

7-2 QUEUE7 Input Queue Sample Listing

7-3 QUEUE7 Output Queue Sample Listing

FIGURES

1-3 7-4

2-2

2-3 15-1

2-6 15-2

2-8 15-3

3-2 15-4

3-6.1

4-3 F-l

4-5

4-5 H-l

4-15

4-41 H-2

5-6

L-l

7-47

7-48 L-2

7-49

Resource Commitment Processing

(Simpliﬁed) 7-53

R a n d o m A c c e s s F i l e S t r u c t u r e 1 5 - 2

LIBEDIT Input and Output 15-18

User Library Structure 15-33

Maximum Size of Global Library

Set 15-43

Examples of Coded Card

Conversion F-4

Carriage Control Tape Format

(Standard Paper Length; 6LPI) H-5

Carriage Control Tape Format

(Short Paper Length; 8LPI) H-6

Keyword Substitution in Two

Procedures L-5

Keyword Substitution in

Nested Procedures L-9

60459680 G 21

TABLES

2-1 Physical File Structure on

Different Devices

Data Representation on

Magnetic Tape

User Job Access Levels

Procedure Directives

Programmable Function Keys for

Procedures

Help on Procedure Calls

Range of Permissible Formats

for the COPY Command

Code Set-Line Terminator

Reference Chart

Compatible File Structures for

the VERIFY Command

10-1 Access Mode Granted When

Attaching a Currently Attached

Direct Access File

Character Sets for Interactive

Jobs

Character Sets for Batch Jobs

2-2

3-1

4-1

4-2

4-3

9-1

9-2

9-3

A-l

A-2

2-5

2-7

3-15

4-10

4-25

4-48

9-6

9-24

9-67

10-10

A-5

A-7

A-3

A-4

A-5

A-6

H-l

H-2

J-l

J-2

K-l

L-l

L-2

ASCII to 6/12-Bit Display Code

Conversion A-10

Nine-Track ASCII Coded Tape

Conversion A-l3

Nine-Track EBCDIC Coded Tape

Conversion A-l4

Seven-Track Coded Tape

Conversions A-l5

Carriage Control Characters for

5 1 2 / 5 8 0 a n d 5 8 7 0 P r i n t e r s H - 3

Carriage Control Characters for

585 Printers H-4

Default Terminal Deﬁnitions J-28

Parameter Ranges for Terminal

Deﬁnition Commands J-29

Default Message Delimiters

and Transmission Keys K-2

Parameter Substitution in

Order-Dependent Mode L-4

Parameter Substitution in

Order-Independent Mode L-8

22

'*^^S\

60459680 H

SYSTEM DESCRIPTION

/ff^x

NOS is capable of several concurrent processing modes. The following are the processing

modes available.

• Local batch.

• R em ot e b at ch .

• Transaction.

• Interactive.

The network processing modes (remote batch, transaction, and interactive) operate through

the Network Access Method (NAM) communications software. These processing modes are

implemented, respectively, by the following NAM applications: Remote Batch Facility (RBF),

Transaction Facility (TAF), and Interactive Facility (IAF).

The primary emphasis of this manual is interactive and local batch processing. For the

other processing modes, consult the appropriate manuals listed in the preface.

NOS, like all operating systems, is the interface between you and the capabilities of system

hardware components. The remainder of this section describes the hardware and software that

make up a NOS-controlled computer system. In most cases, you need not understand the

operation of system hardware or the internal operation of system software. This manual

describes these topics only as general background for understanding NOS commands.

SYSTEM HARDWARE

NOS can operate within the CYBER 180, CYBER 170, CYBER 70, and 6000 Computer Systems (refer I

to the preface for an exhaustive list of model numbers). The primary hardware components of ■

each system are the following.

Central processor unit(s).

Central memory.

Extended memory (optional).

Peri phe ral processors.

Peripheral equipment.

0^^.

60459680 E 1-1

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 ﬁeld 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 ﬁeld length (the CM words in which the

job resides and executes). The ﬁeld length is adjusted during job execution as described

in section 3. Figure 1-1 shows a job ﬁeld length within CM.

A reference to an address outside the job's ﬁeld length range causes a hardware error /

condition and job termination.

The maximum ﬁeld length depends on the CM size and installation parameters used to control

memory usage. The system assigns the CPU to jobs requiring CPU activity. Rapid switching

of CPU control between jobs enables them to execute concurrently. The exact amount of time

allowed for each job depends on system activity and system parameter settings. Thus, the

time required to complete a job may vary from run to run, although the actual CPU execution

time is similar.

When a job completes, aborts, or rolls out (that is, its execution is suspended), the ﬁeld

length is released, cleared, and made available to another job.

1-2 60459680 C

CENTRAL

MEMORY

ABSOLUTE

ADDRESS

REFERENCE

ADDRESS (p)

CENTRAL

MEMORY

RESIDENT

USER

JOB

RA

RA + p 0*£p<FL

RA + FL FL

FIELD

LENGTH

(FL)

Figure 1-1. Central Memory Allocation

Central Memory Resident

The portion of CM reserved for system use is called central memory resident (CMR). It

contains system tables, directories, and the CM portion of the system monitor (CPUMTR),

EXTENDED MEMORY

Extended memory for NOS computer systems (refer to preface), can be used for the following

purposes.

• As a directly accessible memory device via FORTRAN or COMPASS statements for

extended memory data storage and retrieval (refer to the FORTRAN 5 Reference Manual

or appendix D of Volume 4, Program Interface).

• As storage for frequently accessed small files (refer to ASSIGN command in section 7

and Permanent File Commands in section 9).

• As an alternate system device for st ori ng copi es of fre que ntly used routines.

• As a link between mainframes in a multimainframe configuration.t

You must be authorized to use extended memory (refer to LIMITS command in section 7).

fModel 176 cannot use extended memory to link mainframes,

60459680 H 1-3

PERIPHERAL PROCESSORS

The peripheral processors (PPs) process communications between CM and individual peripheral

devices. They also perform system control functions. A peripheral processor can:

• Read and write CM.

• Read and write extended memory indirectly via CM or directly via the distributive

data path (DDP).T

• Transfer data to and from peripheral devices through the data channels.

NOS supports a variety of PP conﬁgurations. Each computer system supports a different

range of conﬁgurations. To determine the conﬁgurations supported by your computer system

consult the appropriate system hardware reference manual listed in the preface.

PERIPHERAL EQUIPMENT

Peripheral equipment varies among installations but usually includes card readers and

punches, line printers, mass storage devices, and magnetic tape units. NOS supports the

following equipment models.

405 Card Reader

415 Card Punch

533/536 Printer

580-12, 580-16, and 580-20 Line Printers

585 Printer

5870 Non-Impact Printer

834/836 Disk Storage Subsystem

844-21 Disk Storage Subsystem

844-41/44 Disk Storage Subsystems

885-11/12 Disk Storage Subsystems

885-42 Disk Storage Subsystem

887 Disk Storage Subsystem

895-1/2 Disk Storage Subsystem

819 Disk Storage Subsystem

Mass Storage Subsystem (MSS)

7990 Mass Storage Extended Subsystem (MSE)

639, 667, 669, 677, 679, and 698 Magnetic Tape Units

tDDP does not apply to peripheral processors for models 176, 865, 875, and 180-class

mainframes.

1-4 60459680 H

^e^

0S&\

/00^X\

(

255x Network Processing Units

26xx Device Interfaces

380-170 Network Access Device

6683 Satellite Coupler

SYSTEM SOFTWARE

Software executed within a computer system can be divided between software that is built

into the system during system initialization and software that executes as jobs within the

running system. Software present when the system begins running includes the operating

system and products such as compilers, CYBER Loader, and CYBER Record Manager.

USER PROGRAMS

A user program is a group of CPU instructions that perform a certain task or calculate a

result. A user program can be written in a language at any of three levels.

• Compiler languages provide you with a language suited to your particular needs. The

program statements are translated by the appropriate compiler (FORTRAN, COBOL,

ALGOL, and so on), which generates assembler language or machine language

instructions. Programs written in compiler languages may be machine-independent.

• Assembler languages provide a one-to-one relationship between instructions and

machine operation. Mnemonics are provided for each instruction. These languages

are machine-dependent. Much of the NOS system is written in COMPASS, the assembler

language of the CYBER 180, CYBER 170, CYBER 70, and 6000 Computer Systems.

• Hardware instructions are interpreted directly by the computer. Each hardware

instruction is a binary number. Most users are rarely concerned with instructions

written at this level except when program debugging requires interpreting memory

dumps.

OPERATING SYSTEM

NOS is a group of programs that supervise and coordinate the operation of system hardware

and the execution of products and user programs. The following lists some of the functions

of NOS.

• Loading and scheduling of user programs.

• Job validation and accounting.

• Command translation.

• File retrieval, manipulation, routing, and storage.

• Job input and output.

• Normal and abnormal job termination.

• Memory dumps.

60459680 G I"5

CYBER Loader

CYBER Loader prepares programs for execution. Following your directions, it allocates

memory for a program, loads the program modules into their appropriate locations, generates

a load map, and initiates program execution. It can load subdivided programs for more

efﬁcient use of memory. Refer to the CYBER Loader Reference Manual for more information.

CYBER Record Manager

CYBER Record Manager (CRM) is the interface between program input/output (I/O) functions and

NOS physical I/O functions. NOS commands do not use CRM. Some of the products that use CRM

are COBOL 5, FORTRAN Extended 4, FORTRAN 5, Sort/Merge 5, PL/I (Programming Language I), and

DMS-170.

The functions of CRM are divided between the Basic Access Methods (BAM) and Advanced Access

Methods (AAM). BAM handles sequential and word-addressable ﬁle organizations; AAM handles

indexed sequential, direct access, and actual key ﬁle organizations. Refer to the

appropriate CYBER Record Manager manual listed in the preface.

1-6 60459680 C

FILES

0^\

A ﬁle is a collection of information addressable by name. All NOS data processing involves

operations performed on ﬁles. Files can be differentiated by their name, structure, or

ﬁle type or by whether they are assigned to a job (NOS jobs are described in section 3).

FILE NAMES

A ﬁle name consists of unique string of seven or less alphanumeric characters. Although

NOS allows ﬁle names that begin with a digit, many of its products (FORTRAN 5 and COBOL 5,

for example) do not support such ﬁle names. Refer to the product reference manual listed

in the preface for details.

Examples:

A Al TAPE DUMP12 COMPILE

NOS uses many internal scratch ﬁles. Most of these scratch ﬁles have names beginning with

the letters ZZ or SCR. Avoid using a name starting with these letters for any of your ﬁles.

The following ﬁle names are signiﬁcant because they are associated with system-managed

ﬁles that are assigned to your job.

INPUT OUTPUT PUNCH PUNCHB P8

Refer to the description of File Types for more information.

FILE STRUCTURE

A ﬁle consists of a well-deﬁned set of data. Its physical representation varies markedly

with the device upon which it resides. For instance, the physical structure of a ﬁle on

magnetic tape is only remotely similar to its physical structure on disk. To facilitate the

manipulation of ﬁle data by user and system programs, the system imposes a logical

structure on a ﬁle that does not vary with device residence.t

A logical ﬁle consists of a contiguous series of data (physically, the data is not always

contiguous). A ﬁle always has a beginning of information and an end of information. It

can be subdivided into a maximum of three levels. Figure 2-1 illustrates the structure of a

ﬁle with one, two, and three levels of subdivisions. NOS and its products (refer to

sec ti on 1 ) al l u se th is ba sic s tru ct ur e f or a l og ica l ﬁle .

tThere are differences in logical structure that depend on device residence, but these

differences are of interest only to a COMPASS programmer. These differences are described

in Volume 4, Program Interface.

60459680 H 2-1

NOS and some of its products do differ in both the levels of ﬁle subdivision they recognize

and the names of the subdivisions. One of the most prominent of these products is CYBER

Record Manager (CRM). It handles input and output for some widely used products like

FORTRAN 5 and COBOL 5. The next two subsections contrast the treatment that NOS and CRM

give a logical ﬁle.

Beginning of

Information End of

Information

Third-level Subdivision Data

Second-level Subdivision

I c cc c c cc c c c clc clc cl ccccccccc cccccccccccc ccccccccc

c c |c c c clc c c cl

First-level Subdivision

cccccccccccccccc cccccccccc c c c le c c cl

Figure 2-1. Logical Structure of Files

2-2

60459680 C

'*s^\

CYBER RECORD MANAGER FILE STRUCTURE*

CRM recognizes all three levels of ﬁle subdivision. It calls a ﬁrst-level subdivision a

partition, a second-level subdivision a section, and a third-level subdivision a record.

Through CRM, you can specify a ﬁle organization, a blocking type, and a record type for

your data. The ﬁle organization determines how records are accessed, the blocking type

determines how CRM records are grouped on their storage media, and the record type deﬁnes

the smallest unit of data CRM can retrieve. Refer to the CRM manuals listed in the preface

for a detailed description.

NOS RLE STRUCTURE

NOS recognizes only two levels of ﬁle subdivision, the ﬁrst and second levels.t NOS calls

a ﬁrst-level subdivision a ﬁle and a second-level subdivision a record. The record is the

smallest recognizable unit for both CRM and NOS but the term does not always refer to the

same subdivision for the two processors. Figure 2-2 illustrates the differences in

terminology.

ﬁle

processor

ﬁrst-level

subdivision

second-level

subdivision

third-level

subdivision

NOS

CRM

ﬁ l e

partition

record

section record

Figure 2-2. NOS and CRM File Terminology

Since NOS terms a ﬁrst level subdivision a ﬁle, a NOS ﬁle can contain more than one

l o g i c a l ﬁ l e ; i f i t d o e s , i t i s c a l l e d a m u l t i ﬁ l e ﬁ l e . A m u l t i ﬁ l e ﬁ l e b e g i n s a t

be gi nni ng -of -i nfo rm ati on ( BO I) a nd e nds at e nd-o f- inf or mat io n (E OI) . A ﬁ le w it hin a

multiﬁle ﬁle begins either at BOI or after the end-of-ﬁle (EOF) of the preceding ﬁle.

It ends at its EOF.

Each ﬁle consists of zero or more logical records of information. A record is zero or more

60-bit CM words. A record begins at the BOI, after an EOF, or after the end-of-record (EOR)

of the preceding record. It ends at its EOR. The following is the structure of a

single-record ﬁle.

BOI data EOR EOF EOI

BOI data EOR EOI

Most simple ﬁles, like text ﬁles, have one of these two formats.

fThis is true for NOS commands but, at the program level, NOS does recognize third-level

subdivisions.

0^\

60459680 C 2-3

The following is the structure of a multirecord, multiﬁle ﬁle.

BOI data EOR data EOR EOF data EOR data EOR EOF EOI

The last EOF in a ﬁle may or may not be present depending upon the program used to create

the ﬁle.

PHYSICAL RLE STRUCTURE

When NOS stores a ﬁle, it automatically converts the ﬁle to a structure that will conform

to the physical characteristics of the storage medium. The logical ﬁle and record marks

are converted to physical BOI, EOR, EOF, and EOI indicators.

The basis of all physical ﬁle structures is the physical record unit (PRU), the minimum

amount of data that can be read or written in a single device access. Table 2-1 lists the

PRU size, and record and ﬁle mark indicators for each supported storage device.

2-4 60459680 C

0^*\

Table 2-1. Physical File Structure On Different Devices

Record and Pile Mark Indicators

Device

Magnetic disk

or extended

memory

Card deckst

PRU Size

64 CM words.

One card.

Interactive Terminal

Magnetic

tapetttt

(Internal)

SI

(System

internal)

(Stranger)

(Long block

stranger)

(Foreign)

One line.

512 CM words;

each PRU in

cludes a 48-bit

terminator.

BOI

PRU 1 or random

address 1 of

the disk (count

ing from 0).

First card in

the deck.

None.

EOR

PRU of less

than 64 words

w i t h a l in k t o

the next PRU.

Card with a

7/8/9 punch

in column 1.

Remote Batch

Facility

(RBF)/HASP can

also use /*E0R.

EOF

Zero-length

PRU (no data)

with special

link to next

PRU.

Card with

6/7/9 punch

in column l.tt

EOI

Zero-length

PRU with no

forward link.

If labeled, tape

mark following

HDR1 label. If

unlabeled, load

point.tt

512 CM words;

each PRU of

less than 512

words has a

48-bit

terminator.

Maximum of 512

CM words; (refer

to BS parameter

on COPY command

in section 9

and to appendix

J in volume 4).

No maximum

deﬁned (refer

to BS param

eter on COPY

command in

section 9 and

to appendix J

in volume 4).

Determined by

C or FC param

eter on ASSIGN,

LABEL, or

REQUEST command.

If labeled, tape

mark following

HDR1 label. If

unlabeled, load

point .ttt

If labeled, tape

mark following

HDR1 label. If

unlabeled,

load point .tt

If labeled, tape

mark following

HDR1 label.

If unlabeled,

load point.ttt

Load point.

On input, one

nonnull line of

data with EOR

l e ve l 1 . .

A PRU of less

than 512 words

with level

number of 0.

A PRU of less

than 512 words

with level

number between

0 and I63.

End of each

PRU.

End of each

PRU.

None.

On input,

one null line

of input.

Zero-length

PRU whose

terminator

contains a

level number

of 178.

Zero-length

PRU whose

terminator

contains a

level number

of 17

Tape mark.ttt t

Tape mark.ttttt

Tape mark.

Card with

6/7/8/9 punch

in column 1.

RBF/HASP can

also use /*E0I.

None.

Tape mark fol

lowed by an

E0F1 label.

Tape mark fol

lowed by an

E0F1 label.

If labeled, a

tape mark fol

lowed by an

E0F1 label. If

unlabeled, there

is no EOI in

dicator.

If labeled, a

tape mark fol

lowed by an

E0F1 label. If

unlabeled, there

is no EOI in

dicator.

None.

tFor more information, refer to appendix F.

ttThe 6/7/9 card is not recognized in a remote batch Job. In an RBF job the end-of-ﬁle marker is a card with a

7/8/9 punch in column 1 and a level number of 17s in columns 2 and 3. RBF/HASP can also use a card with /*E0R in

columns 1 through 5 and a level number of 17g in columns 6 and 7.

tttln the case of multivolume tape ﬁles, BOI is the HDRl label of the ﬁrst volume. In the case of an ANSI multiﬁle,

++ BOI Is the HDRl label associated with the beginning of the multiﬁle.

*II or more lnformation, refer to section 12 and appendix G.

tttttOn labeled tapes, interchange standards require that tape marks be used only to delimit tape label groups.

60459680 E 2-5

Cord Files

The physical ﬁle and record indicators in a card ﬁle are shown in ﬁgure 2-3 and listed in

table 2-1. Although card decks do not have a deﬁned PRU size, a card is the minimum data

unit. NOS can read and punch cards in coded (Hollerith), binary, and absolute binary

formats as described in appendix F. Coded cards are punched in 026 or 029 keypunch mode.

The system uses the installation default keypunch mode (chosen by the installation) for

reading cards unless a 26 or 29 is punched in columns 79 and 80 of a job, EOR, or EOF card,

indicating that the subsequent cards are punched in that mode. NOS can punch up to 80

characters on a coded card and up to 150 characters (15 CM words) on a binary card.t

EOF

E O R * A

BOI

.•-'G5%.

Figure 2-3. Sample Card File Structure

Mass Storage Files

Mass storage ﬁles are stored on disk or extended memory.

To use NOS, you do not need to know the physical structure of mass storage; you do need to

know its logical structure, which contains the concepts of logical devices and logical

tracks. A logical device is one or more physical disk units known to the system as a single

device. A logical track is a ﬁle allocation unit determined by the device type.

t Keypunch mode selection is not supported for jobs entered through a 200 User Terminal or

similar remote batch terminal except for HASP.

2-6 60459680 C

Each permanent ﬁle on mass storage is accessed via a catalog track containing the permanent

ﬁle catalog of its owner. Indirect access ﬁles (refer to Permanent Files) must reside on

the same device as their catalog; direct access ﬁles may reside on another device. Space

is allocated for mass storage ﬁles in units called reservation blocks. An indirect access

ﬁle reservation block is always 64 words (one PRU). A direct access ﬁle reservation block

is a logical track. The maximum size of your mass storage ﬁle is determined by your

validation limits (refer to LIMITS Command in section 6).

0F^\

Magnetic Tape Files

You may write information on magnetic tapes in either coded mode or binary mode. Coded mode

operations involve data conversion from NOS-supported character sets to external character

sets as shown in table 2-2. Coded mode is applicable largely for S and L tape formats.

Binary mode operations copy ﬁles with no character set conversion and can be used for any

tape format.

The term coded mode should not be confused with coded line. A coded line is deﬁned as a

line of 160 characters or less, terminated by a zero byte. Similarly, coded and binary mode

should not be confused with coded and binary ﬁles. A coded ﬁle is a NOS system ﬁle coded

in 6-bit display code, 6/12-bit display code, or 7-bit ASCII code. A binary ﬁle is simply

a ﬁle containing binary information. Coded ﬁles can be copied in coded or binary mode;

binary ﬁles can be copied only in binary mode.

The only NOS commands recommended for coded mode operations are COPY, FCOPY, and TCOPY. Any

of the copy commands can be used for binary mode copies. For CYBER Record Manager (CRM)

ﬁles, the CM parameter on the FILE command is used to select coded or binary mode. For

FORTRAN programs, use the BUFFER 0UT(n,l) statement to select binary mode and the BUFFER

0UT(n,0) statement to select coded mode. For COBOL programs, use either the RECORDING MODE

IS BINARY statement or the RECORDING MODE IS CODED statement.

The representation of data in memory and on tape depends on the number of tracks (seven or

nine), the recording mode (binary or coded), and the speciﬁcation of the CV=cv parameter on

the LABEL command. Table 2-2 shows how the data representation varies with these factors.

Table 2-2. Data Representation on Magnetic Tape

0r*\

Number of

Tracks Binary Mode

1 . O d d p a r i t y.

2. Groups of four 6-bit

characters in memory are

written without conversion

on three-frame units on tape*

1 . O d d p a r i t y.

2. Each 6-bit character in

memory is written without

conversion.

Coded Mode

1 . O d d p a r i t y.

2. Each 6-bit character in

memory is translated into

an 8-bit equivalent on tape.

You can choose EBCDIC

or ASCII by specifying

CV=EB or CV=AS on a LABEL

command.

1• Even parity.

2. Each 6-bit character in

memory is translated to

its BCD equivalent on

tape. The % character is

lost in the translation.

60459680 E 2-7

I Tap e De nsity

You can select 200- (read only), 556-, or 800-characters-per-inch (cpi) density for

seven-track tapes or 800-, 1600-, or 6250-character-per-inch (cpi) density for nine-track

tapes, provided these densities are available with the site hardware. NOS automatically

processes tape parity errors and end-of-tape conditions unless you select other processing

options (refer to Processing Options in section 12). You can also control error processing

by using the EO parameter on a FILE command.

Tape Labels

Tape labels identify and delimit tape volumes and tape ﬁles. Tape marks begin and end most

tape labels. A tape mark is a special bit sequence written and recognized by a tape unit.

NOS processes ANSI standard and nonstandard labeled tapes. Nonstandard labeled tapes are

those whose format or content do not conform to the ANSI standard described in appendix G.

NOS skips to the ﬁrst tape mark when reading a nonstandard labeled tape if the tape

assignment statement speciﬁes the LB=NS parameter (refer to section 12). All information

after the ﬁrst tape mark is then handled as data. Any tape marks occurring after the ﬁrst

tape mark are handled as appropriate for the tape format (refer to table 2-1).

File set conﬁgurations (* means tape mark):

Single ﬁle on single volume

(A)

VOL1 HDRl

(A)

File A data IL EOF1

Single ﬁle on more than one volume

(A)

Volume

1

Volume

2

VOL1 HDR1 File A data

(A)

VOL1 HDR1 File A data

IL EOV1

(A)

EOF1

More than one ﬁle on a single volume

(A)

VOL1 HDRl File A data }l

(A) (B)

EOF1 HDR1 File B data

(B)

EOF1

More than one ﬁle on more than One volume

(A) (A) (B)

Volume

1

Volume

2

Volume

3

VOL1 HDR1 File A data EOF1 HDR1 File B data EOV1

(B)

VOL1 HDRl File B data EOV1

(B)

VOL1 HDRl File B data

(B) (C)

EOF1

(C)

HDR1 File C data EOF1

Figure 2-4. Use of ANSI Labels

^*^^.

^5^SV

2-8 60459680 H

ANSI standard labels as deﬁned by NOS are those that conform to the American National

Standard Magnetic Tape Labels for Information Interchange X3.27-1969 standard. NOS can

create or verify ANSI labels if the LABEL command assigns the tape ﬁle. Label veriﬁcation

ensures that the correct volume has been mounted. ANSI labels separate multiﬁle set ﬁles

and indicate if a ﬁle continues on another volume.

The ANSI label EOF indicates end-of-information for a ﬁle within a ﬁle set. The use of

ANSI labels to delimit ﬁles within ﬁle sets is illustrated in ﬁgure 2-4.

An ANSI-labeled tape must have the following labels. Other optional labels are described in

appendix G.

Label Location

V0L1 Beginning of volume.

HDRl Beginning of information. If the ﬁle continues on to another volume, the

HDRl label is repeated. It must follow the V0L1 label and precede the

continuation of the ﬁle information.

E0F1 End of information.

E0V1 End of volume (required only if the ﬁle continues on another volume).

Appendix G gives the tape label formats.

Tape Data Formats

NOS can read and write data on magnetic tape in any of the following formats.

Format Mnemonic

Internal (NOS default) I

System internalt si

Stranger S

Long block stranger L

Foreign p

These data formats differ in their PRU (block) size and in their record and ﬁle mark

indicators (refer to table 2-1). Other format differences are as follows:

tNOS/BE system default tape format (binary mode only)

60459680 E 2-9

y e ^ ^ v

Tape

Format Labels I/O Mode Tape

P a r i t y Noise Sizet

I Labeled or unlabeled Binary or

codedtt

Odd

Seven-track: <eight frames

Nine-track: <six frames

SI Labeled or unlabeled Binary onlyttt Odd

Odd

Seven-track: <eight frames

Nine-track: <six frames

Labeled or unlabeled Binary

Coded 7-track

Coded 9-track

Labeled or unlabeled Binary

Coded 7-track

Coded 9-track

Unlabeled (labels read Binary

as data) Coded 7-track

Odd

Even

Odd

User-selected;

default is < 18 frames

Odd

Even

Odd

Use r-selec te d;

default is < 18 frames

Odd

Eventttt Use r-selec te d;

default is < 18 frames

NOS terminates all blocks on I format types and all blocks that are not a full PRU on SI

format tapes with a 48-bit block (PRU) terminator. The terminator contains the total number

of bytes in the block (including the terminator itself), the number of blocks since the last

HDRl label, and the level number of the block. This terminator enables read operations on I

format tapes to check whether the number of bytes read and the block number expected match

the byte count and block number in the terminator. If either does not match, the system

attempts to recover the missing data. This feature prevents dropped or fragmented blocks

and provides a higher degree of reliability than other data formats.

Tapes should be read with the same format speciﬁed as when they were written. Data is then

recovered in its original form. For some formats, NOS writes extra bits which are discarded

when the tape is read. I format nine-track tapes are always written with an even multiple

of 12-bit bytes per block. SI format nine-track tapes may have an extra 4 bits written per

block to preserve the lower 4 bits of a CM word. (A 60-bit CM word would be written in

eight frames, 8 bits per frame.)

All nine-track tapes are written with odd parity. Binary seven-track tapes have odd parity;

coded seven-track tapes have even parity. If a parity error is detected on an F format

seven-track tape, the recording mode (binary or coded) is automatically switched to allow

reading of mixed mode tapes.

Volume 4, Program Interface, describes tape formats in greater detail.

tTape blocks read that are smaller than the noise size are discarded. An attempt to write

a block smaller than the noise size produces an error message. Refer to the NS=ns

parameter of the LABEL command,

ttSpeciﬁcation of coded mode aborts the job step; refer to TCOPY Command in section 9.

tttI/O mo de b it is ig no re d.

ttttl/O mode on write for F format is speciﬁed in the control word and is returned in the

control word on read.

2-10 60459680 E

y#«^\

■I

RLE TYPES

The system maintains several tables for each job. Every ﬁle assigned to a job has an entry

in one or more of these tables. A table entry for a ﬁle includes the ﬁle name, the device

on which the ﬁle resides, ﬁle type, and its current position and status.

The system assigns one or more of the following ﬁle types to ﬁles associated with a job:

I n p ut ﬁ l e t y p e

Queued ﬁle type

Local ﬁle type

Primary ﬁle type

Direct access ﬁle type

Library ﬁle type

INPUT FILES

An input ﬁle is also called a job ﬁle because it contains user-supplied commands and data

for a job (refer to section 3). Initially, input ﬁles exist on mass storage in the input

queue. A ﬁle enters the input queue directly when a local or remote batch job enters the

system or indirectly when a user job submits another job via an LDI, ROUTE, or SUBMIT

command. The input ﬁle for an interactive job is normally assigned to the terminal and is

used by an interactive job to read data entered at the terminal into the program. A user

job refers to its input ﬁle by the ﬁle name INPUT (refer to Input File Control in section

QUEUED FILES

A ﬁle is queued as a result of one of the following events:

• Generally, whenever you enter a LDI, OUT, ROUTE, MFQUEUE, or SUBMIT command. Refer

to the description of each individual command for cases where the command fails to

queue a ﬁle.

• Job termination. The system automatically queues files named OUTPUT, PUNCH, PUNCHB,

and P8; deferred routed ﬁles; and other system-reserved output ﬁles if they are

assigned to the job. In interactive jobs, however, the ﬁles OUTPUT, PUNCH, PUNCHB,

and PB are not automatically queued.

A queued ﬁle can have one of ﬁve dispositions:

Input

P l o t

P r i n t

Punch

Wait

60459680 D 2_n

'"^%\

Your job's origin type determines the default processing of your queued job output. Jobs

originating at a central site card reader are queued to a line printer with the same

system-deﬁned identiﬁer as the card reader. Similarly, the system queues remote batch

output to the remote batch terminal where the job originated. The system gives each remote

batch terminal a unique terminal identiﬁer (TID) when it logs in and uses this TID for

queueing ﬁles originating from the terminal. You can determine the default destination of

batch output for your jobs by using the ENQUIRE command and specifying either the JSN=jsn or

UJN=ujn parameter. ENQUIRE shows the default destination in the DS ﬁeld of its display.

RB indicates remote batch routing and BC indicates routing to the batch devices at the

central site.

You can override the default queueing of job output with the LDI, QGET, ROUTE, SETJOB, or

SUBMIT command (refer to section 7).

Queued ﬁles with an input disposition wait until they are scheduled for execution. The

service class of the job determines the scheduling priority of an input ﬁle.

For queued ﬁles with plot, print, or punch dispositions, their priority grows as they wait

in the queue. Such ﬁles are processed when the appropriate device becomes available and

when the ﬁle's priority is higher than all other ﬁles queued to that device. Refer to the

ROUTE command in section 9 for an enumeration of disposition codes for plotting, printing,

and punching.

A ﬁl e wi th a pr in t di sposi ti on m ust be f or matt ed fo r li ne p ri nting . Mo st sy stem ut il ities

format ﬁle OUTPUT for printing, but you must include the appropriate printer control

characters when you create a ﬁle to route to a printer (refer to the COPYSBF command and to

appendix H). Files with uppercase and lowercase characters require special processing

(refer to the FCOPY command). Appendix D contains the printer output from a sample job.

A queued ﬁle with a wait disposition awaits further speciﬁcations from you. The system

queues output from detached interactive jobs with a wait disposition unless you specify a

different disposition. You can explicitly queue ﬁles with a wait disposition with the LDI,

ROUTE, SETJOB, and SUBMIT commands.

A ﬁle remains queued on mass storage until one of the following occurs:

• The system resource it requires becomes available and the file's priority is the

highest of all queued ﬁles with the same disposition.

• You remove the file with the QGET or DROP command.

• Site perso nnel re move it if it resid es i n the queue too long (site-d etermine d).

You can get a list of your queued ﬁles with the ENQUIRE command (refer to section 7).

LOCAL FILES

Files of local ﬁle type are temporary ﬁles. Although all ﬁles assigned to a job are

considered local to the job, the local ﬁle type includes only those ﬁles assigned to your

job that are not given one of the other ﬁle types.

You can create a local ﬁle in many ways. The following list shows some implicit methods of

creating a local ﬁle:

• Name the file for the first time in a copy command or in a read or write command

within a program. A local ﬁle created in this manner always resides on mass

storage.

2-12 60459680 E

J ^ N

• Name the file for the first time in an ASSIGN or REQUEST command that assigns the

local ﬁle to mass storage or to an interactive terminal or name the ﬁle in an

ASSIGN, LABEL, or REQUEST command that assigns the local ﬁle to magnetic tape.

• Name the file in a GET command generating a local mass storage file.

• Name the file as the output file in a compiler-or assembler-call command.

• Name the file as the list or output file in one of the file editing commands (MODIFY

or EDIT, for example).

To save the contents of a local mass storage ﬁle, you issue a SAVE or REPLACE command to

copy the local ﬁle to a permanent indirect access ﬁle or an APPEND command to copy the

local ﬁle onto the end of an existing permanent indirect access ﬁle. Data written on a

local ﬁle assigned to magnetic tape is written on the tape for later access. Local ﬁles

are released upon job completion.

PRIMARY FILES

The primary ﬁle is a temporary mass storage ﬁle designated as the primary ﬁle by a

PRIMARY, NEW, or OLD command. Only one primary ﬁle can exist for a job at a time. Some

commands use the primary ﬁle as the default ﬁle when a ﬁle name is not speciﬁed,

rewinds the primary ﬁle before each job step. NOS

DIRECT ACCESS FILES

You assign a direct access permanent ﬁle to your job by issuing an ATTACH or DEFINE

co mm an d. W he n you d eﬁ ne t he ﬁ le or whe n y ou a tt ac h th e ﬁl e i n a mode pe rm ittin g ﬁ le I

modiﬁcation, you can write on the permanent ﬁle. Refer to Permanent Files in this section.

LIBRARY FILES

A li br ar y ﬁ le i s a r ea d- on ly ﬁl e t ha t se ve ra l u se rs c an access si mu lt an eo us ly. T hi s ﬁ le

type should not be confused with system library programs or with public permanent ﬁles

stored under user name LIBRARY. Refer to Libraries in this section for a description of the

uses of the term library in NOS.

You must be authorized to access a library ﬁle.

If authorized, you can read a library ﬁle after naming it in a COMMON command.

PERMANENT FILES

Your permanent ﬁles reside on mass storage until you purge them or until your site archives

them (contact your computer center for their archiving procedures). The system maintains a

separate permanent ﬁle catalog for each user name and it contains entries for all of your

permanent ﬁles created under the user name you are using to access the system. A catalog

entry includes the ﬁle name, its location on mass storage, its length, permission modes,

and access history. Unless another user name is speciﬁed, the system directs all permanent

ﬁle requests to the ﬁles of the user speciﬁed on the last USER command (or speciﬁed in

the login of an interactive job).

60459680 E 2_n

User names (refer to Validation in section 3) that contain asterisks represent users with

automatic read-only permission to ﬁles in the catalogs of other users. The user name must

match the other user name in all characters not containing asterisks. For example, the user

with user name *AB*DE* can access the catalogs of the following users.

• UABCDEF

• UABDDEE

• MABCDE1

The device residence of permanent ﬁles and their backup copies are described under Mass

Storage File Residence in this section.

The two types of permanent ﬁles, indirect access permanent ﬁles and direct access

permanent ﬁles, are described in the following paragraphs.

INDIRECT ACCESS PERMANENT FILES

You access an indirect access permanent ﬁle by naming it in an OLD or GET command. The

system copies the permanent ﬁle from mass storage to a temporary ﬁle (primary or local

ﬁle type). To alter an indirect access permanent ﬁle, you make the changes to the

temporary copy and then enter the REPLACE command which writes the temporary copy over the

indirect access permanent ﬁle. You create an indirect access permanent ﬁle by naming a

temporary ﬁle in a SAVE or REPLACE command. '-1^\

Mass storage for indirect access permanent ﬁles is allocated in 640-character blocks (64 CM

words). Because of its small allocation block size, indirect ﬁles are most economical for

relatively small ﬁles.

The maximum size of an indirect access ﬁle is determined either by your validation limits

(refer to the LIMITS command), or by the device limitations described in Mass Storage Files

i n t his s ec t ion .

DIRECT ACCESS PERMANENT FILES

You access a direct access permanent ﬁle directly, not through a temporary copy. Data is

written directly on the permanent ﬁle.

You create a direct access permanent ﬁle with a DEFINE command, which determines its name

and residence and the default access mode available to other users. Other users may, if you

permit, access the ﬁle with an ATTACH command. A number of users can attach the ﬁle

concurrently, but only one user at a time can change the ﬁle. To change the ﬁle, you must

attach it in modify, update, append, or write access mode. If you attach the ﬁle in write

mode, no other user can attach that ﬁle concurrently.

Even if a ﬁle is currently attached to a job, you can purge the ﬁle from the permanent

ﬁle catalog with a PURGE command. However, the purged direct access ﬁle remains attached

to the job until it is released by a RETURN, CLEAR, UNLOAD, OLD, or NEW command or until the

job ends.

2-14 60459680 C

jps=v

r

Mass storage for direct access permanent ﬁles is allocated in large blocks; the block size

depends on the mass storage device type on which the ﬁle resides (refer to Mass Storage

Files in this section). Because of their large allocation block size and the write

interlock feature, direct access ﬁles are often used for database ﬁles.

The maximum size of a direct access ﬁle is determined by your validation limits (refer to

LIMITS Command in section 7), or by the device limitations described in Mass Storage Files

i n t his s ec t ion .

MASS STORAGE FILE RESIDENCE

For most mass storage ﬁle operations, you need not be concerned about the speciﬁc device

on which your ﬁle resides. However, under certain circumstances, you may wish to override

the default device residence for local or permanent ﬁles.

With the ASSIGN command, you can assign a local ﬁle to either a speciﬁc device or to a

device category if you are so authorized.

Every permanent ﬁle you create resides either in your family of permanent ﬁle devices, on

an auxiliary device, or on an alternate storage subsystem. Unless you specify otherwise, |

all permanent ﬁles are saved in your family. Refer to the NOS 2 Analysis Handbook for

further details.

FAMILY DEVICES

A family consists of a set of mass storage devices. Normally, a system has only one family

(the default family) of permanent ﬁle devices. However, because families are

interchangeable between NOS systems, several families may be active on one system, or a

system may be part of a multimainframe system. For example, consider an installation with

two systems, A and B. System B provides backup service to system A. If system A failed,

its family of permanent ﬁle devices could be introduced into system B without interrupting

current operations on system B.

You identify your family by supplying a one- to seven-character family name. You can

specify a family name on the USER command. If you are authorized to use secondary USER

commands (refer to the USER command), you also specify a family name on a USER command in

interactive jobs. If your family is the system's default family, you may, but need not,

supply the family name. When the family name is omitted, the system uses the system default

family name. If your family has been introduced into another system, you must supply your

family name.

If you choose to save ﬁles on family devices, you have the option of either using the

system default device type or specifying another type of permanent ﬁle device.

60459680 H 2-15

/■"^^V

AUXILIARY DEVICES

An auxiliary device is a supplement to the mass storage provided by family devices. It is

identiﬁed by a one-to-seven-character pack name. An auxiliary device is not necessarily a

disk pack that can be physically removed as the pack name implies. Rather, an auxiliary

device can be any mass storage device supported by the system and deﬁned as such by the

installation. Each auxiliary device is a self-contained permanent ﬁle device; all direct

and indirect access ﬁles represented by the catalogs on the device reside on the device.

Auxiliary devices may be deﬁned as public or private. Anyone who supplies the appropriate

pack name can create, replace, and access ﬁles on a public device. Only one user, the

owner, can create and replace ﬁles on a private auxiliary device, but others may access or

replace those ﬁles as permitted by the owner.

ALTERNATE STORAGE SUBSYSTEMS **)

Disk is the usual residence of permanent mass storage ﬁles. However, if your installation

has an alternate storage subsystem, some direct access ﬁles can be stored there. An

alternate storage subsystem is well suited for the storage of ﬁles that are accessed

infrequently. Accessing a ﬁle residing on alternate storage takes a few extra seconds,

because the ﬁle must be retrieved and copied (staged) to disk. You can specify the

preferred residence of your direct access ﬁles with the PR parameter on the DEFINE, CHANGE,

or SAVE commands. You can ascertain the residence of your ﬁles with the CATLIST command.

In the CATLIST output, ﬁle names surrounded by parentheses indicate that these ﬁles reside

on alternate storage rather than on disk.

Usually, when attaching a ﬁle from alternate storage, the system suspends the job until the

ﬁle has been staged and assigned to the job. (You can determine the status of your staging

request for an alternate storage ﬁle with the ENQUIRE or cE command.) However, if you

specify the RT parameter on the ATTACH, GET, or OLD command, the job continues processing

while the ﬁle from alternate storage is being staged to disk. You must then issue a second

ATTACH, GET, or OLD command to assign the ﬁle to your job after staging. You can then

check that the ﬁle has been attached by using either the FILE function (refer to section 6)

or a LENGTH or ENQUIRE command.

If a permanent ﬁle is lost or destroyed, site personnel can recover the ﬁle by loading its

backup copy. Generally, sites perform regular dumps of permanent ﬁles to magnetic tape to /*^

serve as the permanent ﬁle backup. By specifying the BR parameter on the DEFINE, CHANGE, '

or SAVE command, you can choose to have a tape backup copy of your direct access ﬁle kept

even if the ﬁle resides on alternate storage. You also can choose to have the alternate

storage ﬁle copy serve as a backup, or you can require no backup copy of your ﬁle.

2-16 60459680 H

yﬂSii^Vy

LIBRARIES

As deﬁned in the glossary (appendix C), the term library has several meanings. The

applicable meaning for the term must be determined from its context. The following

describes some NOS libraries.

USER NAME LIBRARY

Files stored under user name LIBRARY need not be libraries themselves. An installation

saves programs or text as ﬁles under user name LIBRARY so that authorized users can access

them from a centralized location. You can access those ﬁles by specifying the ﬁle name

and the alternate user name LIBRARY on their permanent ﬁle request or by issuing a LIB

command for indirect access ﬁles.

PROGRAM UBRARIES

A program library is a collection of compressed source deck images stored in Modify or

Update format. You access these compressed source decks through MODIFY or UPDATE commands

(refer to section 15).

USER UBRARIES

User libraries are the ﬁles named in the LIBRARY, SATISFY, LIBLOAD, or LDSET loader command

or in program binaries. These ﬁles are searched by CYBER Loader to satisfy external

references within a program it is loading. They contain compiled or assembled routines.

The ﬁrst record of a user library is a ULIB record; the last record is an OPLD record.

Section 15 describes commands that create, catalog, and manipulate user libraries.

60459680 G 2-17

JOB FLOW AND EXECUTION

The primary job types are batch and interactive. A batch job is a ﬁle of commands and

data. Its ﬁrst record, called the command record, contains lines of text that specify NOS

commands. Every batch job begins with a Job command and a USER command. The end of the

command record is marked by an EOR (or an EOI if there is no data in the job).

If records follow the command record, they contain program, data, or directive input for the

commands. As each command requiring user input is processed, the system reads the next

record in the input ﬁle (unless the command speciﬁes otherwise). These records must be in

the same order as the commands that use them.

For example, ﬁgure 3-1 illustrates a job ﬁle. In this job ﬁle, the ﬁrst two commands

are processed by system routines that require no additional user input. The third command,

FTN5(G0), requests the compilation and execution of a FORTRAN 5 program. The compiler reads

the FORTRAN 5 source program from the second record of the input ﬁle. After successful

compilation, the system executes the program. Because the program reads data from the input

ﬁle, it takes input data from the third record of the input ﬁle. Normal job termination

occurs when the system reads the command record EOR (the ﬁrst 7/8/9 card).

You can also consider an interactive job to be a ﬁle of commands and data. You do not

submit the ﬁle to the system as a unit, but enter input one command at a time from a

terminal. Generally, the system processes each command as soon as you enter it. However,

you may group commands in a procedure and those commands are executed together when you call

the procedure.

JOB INITIATION AND TERMINATION

The methods of job entry and termination differ for interactive and batch jobs.

BATCH JOBS

You can enter a batch job in the following ways:

• Enter a job file through a local card reader.

• Enter a job file through a remote batch terminal.

• Enter a job file using the HELLO7, LDI, MFQUEUE, ROUTE, or SUBMIT command from an

interactive or another batch job.

To enter a job ﬁle through a remote batch terminal, you must use the Remote Batch Facility

(RBF). Consult the Network Products Remote Batch Facility Version 1 Reference Manual for

details. Section 7 describes the LDI and SUBMIT commands. Section 9 describes the MFQUEUE

and ROUTE commands.

Unless abnormally terminated, your batch job ends after the system executes the last command

in the command record of your job ﬁle.

60459680 H 3-1

/■"^fev

DATA

RECORD

PROGRAM

RECORD

COMMAND

RECORD

Hll * -DATA DECK

SOURCE DECK

USER,NAM,PASS

FTNJOB.

/«*rSs?\

Figure 3-1. FORTRAN Compile and Execute Deck

INTERACTIVE JOBS

To enter an interactive job, you must use the Interactive Facility (IAF). Volumes 1 and 2

of this reference set give a more detailed description of login and logout procedures for

interactive jobs. Section 16 describes terminal and input/output conventions.

Login

Before you can login to a host computer, you must establish a connection with the network

software. If you need information on how to connect to Communications Control Program (CCP)

software, refer to Volume 2, Guide to System Usage. If your network uses CDCNET, refer to

the CDCNET Terminal Interface Usage manual.

Once you have established a network connection, you can begin the login sequence.

3-2 60459680 F

/0K>\

The following example shows an abbreviated login sequence.t Your entries appear in

lowercase characters.

WELCOME TO THE NOS SOFTWARE SYSTEM.

COPYRIGHT CONTROL DATA 1978,198X.

YY/MM/DD. HH,MM,SS T02A57

NETWORK OPERATING SYSTEM NOS 2

FAMILY: ,usernam,passwrd,iaf

YOUR PASSWORD WILL BE EXPIRED YY/MM/DD

JSN: AEYT, NAMIAF

READY.

The second line of the login sequence gives the original copyright date of NOS software and

the copyright date of your version of NOS. The third line gives the current date and time,

and the name of your terminal.

After the system validates your user name and password, it assigns your job a job sequence

name (JSN). The JSN in this example is AEYT.

If you have recoverable jobs in the system, the system initiates a recovery dialogue with

you immediately after it logs you in.

["note]

Using a network to recover a job other than

the one you were using before the job was

disconnected may not always work. For this

reason, we recommend that you always use

the same network to recover a job.

t This manual assumes that your system does not require the entry of a personal identiﬁer.

For more information about the personal identiﬁer 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

NETWORK OPERATING SYSTEM NOS 2

FAMILY: ,usernam,passwrd,iaf

YOUR PASSWORD WILL BE EXPIRED YY/MM/DD

JSN: ADYE, NAMIAF

RECOVERABLE JOBCS)

JSN UJN STATUS TIMEOUT

AARQ AN2A SUSPENDED 26 MIN.

AASF AN2A SUSPENDED 28 MIN.

ENTER GO TO CONTINUE CURRENT JOB,

RELIST TO LIST RECOVERABLE JOBS,

OR DESIRED JSN: go

READY.

Additionally, some sites may require you to enter charge information during login (refer to

CHARGE command in section 7).

Logout and Application Switching Procedure

When you have ﬁnished using IAF, you can either log out or switch to another application.

The logout procedure disconnects you from the host. Application switching ends your session

with IAF but allows you to continue processing under the control of another application

(such as RBF).

To terminate your terminal session, enter one of the following:

GOOD BYE or B YE or LOGO UT

The system responds by printing:

UN=username LOG OFF hh.mm.ss.

JSN=jsn SRU-S s.sss

CHARACTERS=xxxxxKCHS

IAF CONNECT TIME hh.mm.ss.

LOGGED OUT.

This display is followed by additional logout information provided by network software.

t This manual assumes that your system does not require the entry of a personal identiﬁer.

For more information about the personal identiﬁer 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:

jpfﬁv

Item Description

username User name you entered during login.

hh.mm.ss. The ﬁrst occurrence of hh.mm.ss. indicates the time of

logout. The second occurrence indicates the length of time

your terminal was connected to IAF.

jsn Your job sequence name.

s.sss A measure of the system resources used while connected to IAF.

x x x x x x x x A c o u n t o f t h e t o t a l n u m b e r o f i n p u t a n d o u t p u t c h a r a c t e r s r e a d

from, or written to, your terminal.

ct The network control character for your terminal. (The network

control character for speciﬁc terminal models are listed in

Table J-l.)

had The host availability display (HAD). The HAD appears if you

have enabled it with the HD terminal deﬁnition command (refer

to appendix J) or if you are operating in a multihost

environment.

IAF automatically logs out the terminal if no activity has been registered in a site-deﬁned

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 conﬁgurations 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 conﬁgure these computer systems, and the means by ""^s

which you submit jobs to a remote host depend on your system conﬁguration, the type of >

remote host, and the nature of the jobs. In all cases, however, you must have special

authorization to submit such jobs (refer to the LIMITS command in section 7).

In general, you can submit a batch job to a remote host by specifying the remote host with

the ST=lid parameter of the Job command or the ROUTE command. If the remote host is a

SCOPE 2 system and the batch job requires interactive input or output, use the HELL07

command. If the remote host is connected through the Queued File Transfer Facility (QTF)

and the batch job has special routing requirements (requirements not provided by ROUTE

parameters), use the MFQUEUE command. If you want to retrieve or change the attributes of

permanent ﬁles 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 ﬁle to the NOS/VE batch '*S\

input queue. The ﬁle 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

means used for job initiation. Its origin identiﬁcation remains with the job throughout

job processing. The job origin type determines how the job is handled and how it exits from

the system.

The four origin types and their system symbols are as follows (system symbols are described

in section 6):

Origin Type Symbol

System SYO

Interactive IAO

Local batch BCO

Remote batch RBO

System origin jobs originate at the system console, interactive jobs all enter through IAF,

local batch jobs enter through central site batch devices, and remote batch jobs enter

through RBF.

If you are so authorized (refer to the LIMITS command), you can also initiate jobs using the

HELL07, MFQUEUE, LDI, ROUTE, or SUBMIT commands. Depending on how you specify the

parameters of these commands, the resulting jobs can either be local batch or remote batch

in origin type.

JOB SERVICE CLASSES

Every job in the system is assigned a service class. This service class determines the

job's scheduling priority as the job ﬂows through the system. You can make this service

class assignment or you can let the system assign it a default service class based on the

job's origin type and your validation limits (the privileges your site has granted you).

Unless changed by your site, the system has the following 14 service classes:

Service Class

Deadstart

System

Local batch

Remote batch

Interactive

Detached i nter acti ve

Network supervisor

Subsystem

Maintenance

60459680 F

Two-character

Mnemonic

One-character

Mnemonic

ADS

SY

BC

RB

TS

DI

NS

SS

MA

3 - 6 . 1 / 3 - 6 . 2

Figure 3-2 summarizes the methods of submitting jobs to remote hosts.

Command/Application Type of Job Being Submitted

Special Host Type/

Connection Type

Job Command

(ST=lid parameter)

ROUTE Command

(ST=lid parameter)

Batch No special

requirements.

HELL07 Command B atch ( wit h inte ra cti ve I/ O) SCOPE 2 system.

MFQUEUE Command Batch (with special routing requirements) RHF (LCN, CDCNET,

or CCP).

ITF A pp lic at ion Interactive VSOS system

(CYBER 200).

MFLINK Command Part of a batch or interactive job

(permanent ﬁle 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

means used for job initiation. Its origin identiﬁcation remains with the job throughout

job processing. The job origin type determines how the job is handled and how it exits from

the system.

The four origin types and their system symbols are as follows (system symbols are described

in section 6):

Origin Type Symbol

System SYO

Interactive IAO

Local batch BCO

Remote batch RBO

System origin jobs originate at the system console, interactive jobs all enter through IAF,

local batch jobs enter through central site batch devices, and remote batch jobs enter

through RBF.

If you are so authorized (refer to the LIMITS command), you can also initiate jobs using the

HELL07, MFQUEUE, LDI, ROUTE, or SUBMIT commands. Depending on how you specify the

parameters of these commands, the resulting jobs can either be local batch or remote batch

in origin type. >e^%\

JOB SERVICE CLASSES

Every job in the system is assigned a service class. This service class determines the

job's scheduling priority as the job ﬂows through the system. You can make this service

class assignment or you can let the system assign it a default service class based on the

job's origin type and your validation limits (the privileges your site has granted you).

Unless changed by your site, the system has the following 14 service classes:

Service Class

Deadstart

System

Local batch

Remote batch

Interactive

Detached i nter acti ve

Network supervisor

Subsystem

Maintenance

| 3-6.2

Two-character One--character

Mnemonic Mnemonic

A

DS

SY

BC

RB

TS

DI

NS

SS

MA

60459680

,/**«^\

#R*^

y^V

# ^ N

Two-character One-character

Service Class Mnemonic Mnemonic

Communication task CT C

Installation class 0 10 0

Installation class 1 II 1

Installation class 2 12 2

Installation class 3 13 3

The scheduling priority associated with each service class is site-determined. You can

ascertain how your site has prioritized the service classes you are authorized to use for

each origin type by using the CLASS command. To determine the service class of a job, use

the ENQUIRE command. The system denotes the service class with a one-character mnemonic in

the SC ﬁeld of the ENQUIRE output.

Your site allows you to use only a subset of the service classes. The LIMITS command shows

you which service classes you can use. Further, your site can restrict the use of certain

service classes to jobs of certain origin types. The CLASS command displays this

information.

You can assign a service class to a job in the following ways:

• Use the CHVAL command to specify default assignments for your jobs according to

origin type. The system uses one of these default assignments if you do not

otherwise make a service class assignment in a job. The LIMITS command shows what

your default service class assignments are for each origin type.

• Use the SC=class or P=priority parameter of the Job command for batch jobs.

• Use the CLASS command to change the service class of your current job.

• Use the SCL=scl parameter of the ROUTE command for jobs to be initiated by that

command.

JOB NAMES

Every job in the system receives a job sequence name (JSN) and a user job name (UJN). This

includes not only your job ﬁle, but ﬁles you explicitly route for disposal during your

job, such as ﬁles routed to a line printer. These job names are the primary job

identiﬁers for both the system and you. Many system commands use the JSN and UJN as

parameters. You can get a list of the JSN and UJN of all your active jobs by using the

ENQUIRE command.

JOB SEQUENCE NAME (JSN)

The system assigns every job a unique JSN. Each JSN consists of four alphabetic

characters. The banner page of batch output prominently displays the job's JSN: the JSN

appears as the last four characters of the eight characters in block letters (refer to

appendix D for a sample banner page).

60459680 D 3-7

,/ﬂSs^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 speciﬁed, the UJN for batch jobs defaults to the

UJN speciﬁed 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 speciﬁc 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 dayﬁle 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

ﬁle at any time during the job by issuing the ENQUIRE command. The format of SRU

information written in the dayﬁle is given under Job Completion in this section.

tNot currently supported by the system but reserved for future

3-8 60459680 C

0eas,

I

JOB SCHEDULING

When a job enters the system, it is queued for input and waits for the required system

resources to become available or its priority to grow. The job's priority depends on its

service class. The system priorities are system-deﬁned 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-deﬁned limit. The job scheduler periodically scans the queued

jobs and active jobs to determine whether action is necessary to ensure that the highest

priori ty jobs a re be ing s er viced . T hi s act io n may inc lude rolli ng out lo w pri ority j obs o r

rolling in higher priority jobs. The job scheduler is also activated to analyze the system

status whenever there are changes (for example, when the ﬁeld 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 ﬂow

of the command processing is illustrated in ﬁgure 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 ﬁeld length (central memory) assigned to a job, adjusting it

according to the requirements of each job step. CYBER Loader further adjusts the ﬁeld

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 inﬂuence the ﬁeld length assigned to your

job by using the CM parameter of the Job command and the MFL and RFL commands.

The maximum ﬁeld 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 ﬁeld length is the smaller of MAXFL or the value you

speciﬁed with the MFL command.

The running ﬁeld length (RFL) is initially set to zero, indicating system control of ﬁeld

length. The RFL command changes RFL. RFL cannot exceed the current MFL.

To set the initial ﬁeld length for a job step, the system uses the ﬁrst value set by one

of the following.

• Predefined initial field length for a system routine or on a global library set

(RFL = special entry point).

•Highest high address (HHA) from EACP loader table (54 table) (refer to the CYBER

Loader Reference Manual).

60459680 C 3-9

RFL value, if nonzero.

The smaller of the MFL or the installation-deﬁned default value (release value

50000B).

NOTE

The system automatically assigns a ﬁeld

length for CM only. To set the initial

ﬁeld 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 ﬁeld length (expressed in octal) used to process each command.

Command

JOB,CM60000.

USER,USERABC,1234.

MAXFL

60000

MFL

60000

RFL

0

Field

Length

3200

GET,ABSPROG,RELPROG. 60000 60000 2500

Explanation

The CM parameter sets

the MAXFL and MFL

values. The system

sets the ﬁeld length

as required for pro

cessing the command.

GET command retrieves

copies of an absolute

program and a relocat

able program.

RFL,40000. 60000 60000 2300 The user issues an

RFL command to set

t h e ﬁ e l d l e n g t h f o r

execution of the abso

lute program that

follows.

ABSPROG. 60000 60000 40000

MFL,50000. 60000 600 00 40000

RELPROG. 60000 50000

40000 The absolute program

on ﬁle ABSPROG is

executed within a

40000-word ﬁeld

length.

2300 The user issues an

MFL command to set

the maximum ﬁeld

length for the follow

ing relocatable load.

50000 If more than a 50000-

word ﬁeld length is

required, the job

aborts.

3-10 60459680 C

INPUT RLE CONTROL

Batch jobs, when initiated, have a ﬁle named INPUT (input ﬁle type). This ﬁle contains

the commands and other input records required for job execution. INPUT is a locked ﬁle.

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 ﬁle named INPUT, you should

ﬁrst issue a RETURN(INPUT) command. This command changes the name of the ﬁle from INPUT

to INPUT* and leaves it assigned to your job. You may then write on ﬁle INPUT. The change

of name caused by the RETURN command applies only if the ﬁle has an input ﬁle type (refer

to File Types in section 2). /K

For interactive jobs, ﬁle INPUT* is present at the beginning of the session and cannot be

returned with a RETURN command. You can create and manipulate a ﬁle called INPUT at any

time, although various products, such as the Full Screen Editor, require special processing

in order to handle ﬁles named INPUT or OUTPUT as data ﬁles.

TIME LIMIT CONTROL

The system sets a default time limit for each job step unless the Job command or the SETTL

command speciﬁes a job step time limit. This time limit is the amount of central processor

time that any one job step is allowed. You cannot increase the limit beyond that for which

you are authorized.

While a job is using the central processor, the CPU time is accumulated and checked against

the time limit for each job step. If the job's origin type is not interactive, the job in

execution terminates or enters exit processing when the time limit is reached. Interactive

jobs are suspended, after which you can increment the time limit and resume execution from

the point of suspension (refer to SETTL Command for an example). In the case of a detached

S^rS™ * the/ys5em susPends or terminates the job according to the parameter values

ot the SETJOB command. You cannot resume jobs suspended in this fashion from the point of

suspension; they enter exit processing.

SRU LIMIT CONTROL

The system sets a limit on the number of system resource units (SRU) that a job step or an

account block can accumulate. An SRU includes central processor time, central memory usage

permanent ﬁle 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 ﬁeld length (both CM

and extended memory), the job control area, and the control registers (exchange package) are

written to mass storage. The program remains on mass storage until it is rolled back into

memory. Execution resumes from the point where rollout occurred. The amount of time the

job is allowed to occupy CM is called the central memory time slice. The central memory

time slice is a system parameter that can be changed only by the system operator; time

slices vary for each origin type. Whether a job is rolled out when its time slice expires

depends on several factors.

• Whether there are jobs waiting for execution.

• Whether the jobs that are waiting have a higher priority.

• Whether jobs that are waiting require more field length than would be available if

all jobs of lower priority were rolled out.

When a job is rolled out, it is assigned a priority. The priority assigned is a system

parameter that depends on a job's service class and can be changed only by the system

operator. The job's priority increases while the job waits. Normally, all other factors

being equal, the job with the highest priority is selected to be rolled in.

ERROR CONTROL

When job step activity ceases, the system must determine the next command to process. If

activity ceased due to normal termination, the next command processed is the next command in

sequence. If an error caused activity to cease, the system issues the appropriate dayﬁle

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 dayﬁle messages. The ﬁrst 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 ﬁle ZZZDUMP, for

interactive jobs (refer to section 14). ZZZDUMP is not rewound before or after the dump.

After issuing the appropriate dayﬁle 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 indeﬁnite operand)'errors are allowed and program execution continues (refer to

section 6). The default error exit mode speciﬁes that all errors terminate the job.

The EREXIT, RECOVR, REPRIEVE, and MODE macros control error processing in COMPASS programs..

The SETLOF macro speciﬁes ﬁle completion procedures when a job step abort occurs. These

macros are described in Volume 4, Program Interface.

TNot applicable to model 176.

3-12

T*&&!\

60459680 C

0^^\

SECURITY FEATURES

A NOS computer system provides extensive protection of information contained in your jobs

and ﬁles. Most notably, it protects the central memory associated with your active jobs

and it enforces job and ﬁle access controls.

MEMORY PROTECTION

A job cannot dump or directly change the contents of the job ﬁeld length immediately after

a protected command or a user program. The following is a list of protected commands and a

list of load/dump memory commands:

Protected Commands

APL COPYCF IF or (IFE) PASSWOR SECHDR

APPEND COPYCR LABEL PERMIT SET

ASSIGN COPYEI LDSET PROFILE SETFS

ATTACH COPYSBF LIBEDIT PURGE SKIP

BEGIN COPYX LIBLOAD RECOVER SORT

BLANK DAYFILE LIBTASK REDUCE SUBMIT

CATALOG DEFINE LIMITS REPLACE TCOPY

CATLIST DISPLAY LOAD REQUEST UNLOAD

CHANGE EDIT MAP RESOURC UPROC

CHARGE ELSE MFLINK RESTART USER

CHVAL ENDIF MFQUEUE RETURN VERIFY

CLASS ENDW NEW REVERT VFYLIB

CLEAR ENQUIRE OLD REWIND VSN

COPY EXECUTEt OUT SATISFY WHILE

COPYBF FSE OVWRITE SAVE

COPYBR GET PACKNAM SCOPY

Load/Dump Memory Commands

CKP

DMB

DMD

DMDECS

DMP

DMPECS

LBC

LOC

PBC

RBR

WBR

In an interactive job, you cannot enter a load/dump memory command individually or as the

ﬁrst command of a procedure. If you attempt to change or dump protected memory, the system

issues an informative message to the dayﬁle 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 identiﬁer 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

ﬁle access controls based on user names, ﬁle passwords, and permissions granted by the

owner of the ﬁle. The controls based on ﬁle passwords and permissions are discretionary;

they are set at the discretion of the ﬁle 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 ﬁle. 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 ﬁle on a secured system has a single security access level and

may have one or more access categories associated with it. To access a ﬁle, the user job

must be validated for the file's security access level and for all of the file's access ■aS^\

categories.

SECURITY ACCESS LEVELS

A security access level limits the disclosure of sensitive information to persons who are

authorized to access information at the level of sensitivity indicated by that access

level. A secured system supports up to eight security access levels. The number of access

levels to be used, the names of those levels, and the degree of sensitivity associated with

each level are selected by your site. The access levels are ordered so that the most

sensitive information is associated with higher access levels. (The access levels have

numerical values of 0 through 7; the corresponding released default names are LVLO through

LVL7.) You are validated for a set of security access levels (normally a contiguous range

of levels, such as LVLO through LVL4).

The system associates a set of access levels with each job. This set is the intersection of

your validated set of access levels, the range of levels currently valid for the system, the

range of access levels allowed for your job's origin type, and, if speciﬁed 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 ﬁle 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 ﬁle 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 ﬁle has a security access level. Unless you specify otherwise, each ﬁle you create

will have the same access level as your job at the time you create the ﬁle. You can always

raise the access level of your ﬁles (refer to the SETFAL and SETPFAL commands) to any level

for which your job is validated, but you must have special permission to lower the access

level of your ﬁles. However, the access level of direct access ﬁles or tape ﬁles cannot

be changed while they are assigned to your job. If the access level of such a ﬁle is lower

than that of your job, you can always read information from the ﬁle but can only write

information to it if you have special authorization. The access level of a local ﬁle is

automatically raised to the current job access level whenever an operation is performed on

t h e ﬁ 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 ﬁ l e ) .

Your job's access level is automatically raised whenever you read information from a ﬁle

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 ﬁle that has access level

LVL3 and read information from that ﬁle. 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 speciﬁcally validated, a secured system does not allow you to write

information from a ﬁle with a higher access level into a ﬁle with a lower access level.

Example 4: You attempt to copy a portion of a ﬁle whose access level is LVL2 to a ﬁle

whose access level is LVL3. A secured system allows this operation.

Example 5: You attempt to copy a portion of a ﬁle whose access level is LVL3 to a ﬁle

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 ﬁles (for informational purposes),

but the system does not use those levels to restrict access to the ﬁles, nor does it

propagate those levels to your job or to other ﬁles. 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-deﬁned 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 ﬁle (using the SAVE or DEFINE command), the ﬁle 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

ﬁles (refer to the SETPFAC command). Access categories restrict the access of your

permanent ﬁles to those users who are validated for all of the categories you have set for

the ﬁles.

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 ﬁle ABC,

which has an access level of LVL3. You then make ﬁle ABC public. Any user in your

family who is validated for access level LVL3 and the categories CAT06 and CAT22 can

then access ﬁle ABC.

On an unsecured system, you may assign access categories to your permanent ﬁles for

informational purposes, but the system does not use those categories to restrict access to

the ﬁles.

RESPONSIBILITIES FOR DATA SECURITY

In a secured system, security access levels and categories are checked whenever a user

accesses a ﬁle, begins a job, or attempts to alter the security parameters of a ﬁle or

job. This ensures that only those persons who are validated for the access levels and

categories you have assigned to your ﬁles can access them. A secured system thus provides

continuous protection of your data.

Although the system will automatically assign an access level and an access category set to

each ﬁle you create, you are responsible for ensuring that the access level and access

category set assigned to each of your ﬁles is appropriate. Your site should provide

guidelines for the use of the different access levels and categories it has established.

All of the NOS security mechanisms depend on the protection of your user password. NOS

provides the following mechanisms to help protect your password during interactive login:

• You should always use the secure login procedure (described in section 8) to ensure

that you are communicating with the system-supplied login mechanism.

| 3_i6 60459680 G

/^^v

• If possible, you should set your terminal to full duplex and enable echoplex mode

(refer to the EP terminal deﬁnition command). The network temporarily disables

echoplex when you enter your password during login. If you use the abbreviated

login sequence, all ﬁelds 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 dayﬁle.

Although NOS encrypts your user password after login, the programs you execute can affect

the security of your ﬁles 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 identiﬁes the operation as a security conﬂict and issues a SECURITY CONFLICT

message. A security conﬂict causes the job step to be aborted and decrements your security

count (you are given a speciﬁc 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 conﬂict 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 conﬂict arises in the following cases in addition to those

listed above:

• An attempt to set an invalid access level on a file or job.

r e A n a t t e m p t t o a c c e s s o n e o f y o u r p erma n e n t ﬁ l es f r o m a j o b t h at i s n o t v a l i d a ted

for the access level or access category set of the ﬁle.

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

• An attempt to set an access level for a file or job which is lower than the current

access level of the ﬁle 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 conﬂict 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. All library ﬁles attached to the job are released.

5. All scratch (local) ﬁle space used by the job is released.

6. All direct access permanent ﬁles attached to the job are released; the status

information for these ﬁles is updated.

7. The following summations of job activity are added to the end of the job dayﬁle.

This information is also issued to the associated account dayﬁle 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 deﬁnes 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 ﬁles queued for printing.

• Lines printed in kilolines:

hh.mm.ss.UCLP, mi,es, xxxxxx.xxxKLNS.

or

hh.mm.ss.UCLV, mi,es, xxxxxx.xxxKLNS.

mi Machine identiﬁer.

es Equipment status table (EST) ordinal of the output device.

^^ The UCLV summation is issued if the V carriage control character was used

0^ (refer to appendix H).

9. The following information is issued to the account dayﬁle only.

• Cards punched in kilocards:

hh.mm.ss.jsn. UCPC, mi,es, xxxxxx.xxxKCDS.

10. For batch jobs, the job dayﬁle is copied to the end of ﬁle OUTPUT. If OUTPUT does

not exist or if it is a deferred routed ﬁle with EC=A9 speciﬁed, the dayﬁle is

copied to another ﬁle that the system queues for printing.

11. All deferred routed ﬁles are queued for disposal. The ﬁles named OUTPUT, PUNCH,

PUNCHB, and P8 are also queued for disposal in batch jobs. The system does not

automatically queue ﬁles 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^*\

r*

PROCEDURES

A NOS procedure is a sequence of NOS commands, residing in a separate record or ﬁle, that

performs a speciﬁc task or sequence of tasks. A procedure header directive identiﬁes the

ﬁle as a procedure ﬁle, and a number of other procedure directives allow you to control

additional procedure processing options.

Once you have created a procedure and stored it in a permanent ﬁle, 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 ﬁle, a permanent ﬁle

(direct or indirect access), or from a local or global library set. Your site may also

provide procedures of general use that you can call from system libraries or from user name

LIBRARY. A procedure can be called from another procedure up to a maximum of 50 nested

procedures.

A procedure called from a batch job functions much like a program subroutine. You can pass

parameters to the procedure on the procedure call (BEGIN command). The procedure accepts

any data passed to it, performs its processing functions, and returns control to the calling

job or procedure.

When called from an interactive job, a NOS procedure functions like a user-deﬁned system

command. Once you have made the procedure ﬁle local to your job, you can execute the

procedure simply by entering the procedure or ﬁle name, followed by any parameters you may

have deﬁned for the procedure.

Although NOS supports both interactive and noninteractive procedure formats (noninteractlve

procedures are also called passive procedures), any NOS procedure can be called from either

a batch or interactive job. The interactive procedure formats described in this section

differ from th e no ninte rac tive fo rmat (d escribed in App endix L) in t hat the inte ractive

formats provide the end user with various types of interactive help and parameter prompts.

The major features of NOS interactive parameter formats are:

Two Interactive Formats

As the procedure writer, you can choose between the parameter-prompting (*I) or the menu

(*M) interactive formats. The parameter-prompting format prompts the user to enter

required parameter values. The menu format displays a list of possible parameter values

and prompts the user to select one of the values by number.

Procedure Prompting

If the user fails to enter a required parameter value, or enters an invalid value, the

system prompts the user to enter a correct value.

60459680 D 4-i

Interactive Help

Both interactive formats give the user easy access to system-generated, as well as

procedure-deﬁned help for a procedure and its parameters.

Parameter Validation

The interactive formats provide an easy way of deﬁning 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 ﬁle. Several procedures, or a collection

of procedures and programs, can exist on the same ﬁle. Procedures can be stored on local

ﬁles, indirect access or direct access permanent ﬁles, system libraries, or user name

LIBRARY. Procedures can also reside on magnetic tape as well as mass storage.

The procedure search order is dependent on the form of the BEGIN command used to call the

procedure. For more information on the search order, refer to the BEGIN command description

i n t his s ec t ion .

PROCEDURE STRUCTURE

A procedure ﬁle can be divided into ﬁve sections, as shown by the example in Figure 4-1.

The ﬁrst 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 ﬁfth (Data) section may contain programs, procedures, or other data to be

referenced by the procedure.

The ﬁrst line or lines of a procedure is the procedure header, which consists of a single "ca^\

procedure header (.PROC) directive. The procedure header names the procedure, indicates .'

whether the system will prompt for required parameter values, deﬁnes what the prompts will

consist of, and deﬁnes 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 identiﬁed 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 deﬁne 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

yf^*N

The command section consists of procedure directives and system commands you want to be

executed. Most system commands are allowed within a procedure. The exceptions are

prim ari ly the co mma nds restricted t o entry f rom interactive ter min als (refer to section 8 ).

The data section consists of information you want written to a local ﬁle or ﬁles 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 identiﬁes each local ﬁle 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 speciﬁed in the procedure

header. Each value the user enters is veriﬁed against the validation requirements

speciﬁed 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 modiﬁed by directives in the

formatting section.

If the user requests help for the procedure or for a parameter (by entering a ? following

the procedure call or following a parameter prompt), the system displays the applicable /r*^K

system default help text, if any, followed by procedure-deﬁned help text. ]

The interactive parameter entry portion of procedure processing is completed when the user

enters a carriage return after having correctly entered all required parameter values. If

the user correctly enters all required values on the procedure call, no formatting or help

directives (except .NOTE and .NOCLR) are processed, and procedure expansion begins

immediately.

PROCEDURE EXPANSION

Procedure expansion is performed only on the procedure command and data sections. During

procedure expansion, the system:

• Processes all directives in the command and data section.

• Substitutes parameter values specified by the user, or by the .PROC directive, for

each occurrence of the corresponding parameter keyword in the command and data

sections.

• Creates a scratch file, called the procedure command record, which contains the NOS

commands from the procedure command section as modiﬁed by directive processing and

parameter substitution.

•Creates a separate local ﬁle 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

ﬁle (the procedure command record), containing NOS commands ready to be executed, and a

local ﬁle for each .DATA ﬁle 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 deﬁne 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 ﬁgures 4-2 and 4-3. These ﬁgures show the command records

resulting from valid and invalid entries for the procedure in ﬁgure 4-1.

Note that at the end of processing in either ﬁgure 4-2 or 4-3, a listing of the user's

local jobs would show a ﬁle called APPL. This ﬁle is created as a result of the .DATA

directive in procedure TESTPN from ﬁgure 4-1.

/0^^\

Procedure Command record:

RETURN,LISTFIL,LG0.

FTN5,I=APPL,L=LISTFIL,B=LG0.

LGO.

REVERT,N0LIST.

Dayﬁle:

testpn,prj/2201

APPL COMPLETE

/dayﬁ Le,fr=testpn,op=m

10.18.53.TESTPN,PRJ/2201.

10.18.54.RETURN,LISTFIL,LG0.

10.18.55.FTN5,I=APPL,L=LISTFIL,B=LG0.

10.18.55. 62700 CM STORAGE USED.

10.18.55. 0.009 CP SECONDS COMPILATION TIME.

10.18.55.LGO.

10.18.56. END APPL

10.18.56. 14300 MAXIMUM EXECUTION FL.

10.18.56. 0.007 CP SECONDS EXECUTION TIME.

10.19.21.DAYFILE,FR=TESTPN,0P=M

USER DAYFILE PROCESSED.

/

Figure 4-2. TESTPN with Valid Entry

Procedure Command record:

NOTE./INVALID PROJECT NUMBER/

REVERT,N0LIST.

Dayﬁ Le:

testpn,888

INVALID PROJECT NUMBER

/dayﬁ Le,fr=testpn,op=m

10.19.51.TESTPN,888.

10.19.51.NOTE./INVALID PROJECT NUMBER/

10.20.03.DAY FILE,FR=TESTPN,0P=M

USER DAYFILE PROCESSED.

/

Figure 4-3. TESTPN with Invalid Entry

60459680 E 4-5

Following are some tools you can use to further control procedure expansion:

• .EXPAND Directive

• Inhibit Character

• Concatenation Character

• .EX Directive

.EXPAND Directive

The .EXPAND directive allows you to suspend expansion processing for one or more lines of a

procedure. Inserting a .EXPAND,OFF directive suspends directive processing and parameter ^^

substitution for subsequent lines of the procedure until the end of the procedure or until a )

.EXPAND,ON directive appears.

An especially useful application of the .EXPAND directive is to inhibit expansion of a

procedure in a .DATA ﬁle. Normally, calling a procedure ﬁle initiates expansion of the

entire ﬁle, including the data section. However, if the data section contains another

procedure ﬁle, you may not want the .DATA ﬁle 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 ﬁle. Inserting a .EXPAND,OFF directive immediately after the .DATA directive

causes the .DATA ﬁle 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 deﬁne 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

i^SN

The inhibit character placed before a concatenation character InhibLts processing of

the concatenation operatLon; the concatenation character remains Intact. In this

case, the inhibit character does not prevent parameter substitution of a keyword

following the concatenation character.

Expansion processing strips all Inhibit characters from the procedure command record

with two exceptions:

those appearing in a $-dellralted literal string.

those appearing In a sequence of two or more Inhibit characters. When they

appear in sequence, only the ﬁrst 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 ﬁle parameter Is written as #1=1,

procedure expansion will remove the #, leave the ﬁrst 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 ﬁle

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 ﬁle 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 ﬁle PROCFIL.

.PROC,INHIBIT*I,I=(*N=TEST).

GET,I.

FTN5,#I=I,L=0

LGO.

COMMENT. I, Ul, Ul, UUU

60459680 D 4-7

If procedure INHIBIT is called by the command:

begin,inhibit

The resulting dayﬁle segment is:

10.31.00.BEGIN,INHIBIT.

10.31.00.GET,TEST.

10.31.OO.FTN5,I=TEST,L=0

10.31.00. 56000 CM STORAGE USED.

10.31.00. 0.011 CP SECONDS COMPILATION TIME.

10.31.00.LGO.

1 0 . 3 1 . 0 1 . S T O P

1 0. 3 1. 0 1. 5 60 0 F I NA L E X EC U TI O N F L.

10.31.01 0.000 CP SECONDS EXECUTION TIME.

10.31.01. COMMENT. TEST, I, TESTI, II. "^

10.31.01.SREVERT.CCL '

Concatenation Character

The concatenation character allows parameter substitution for a substring of a character

string. The default concatenation character is _ (or r-*" if you are using a CDC graphic

char ac ter s et) .

Usage rules for the concatenation character are: >*s«^k

• Expansion processing removes all concatenation characters from the procedure file

except those included in a $-deliraited literal string and those preceded by a #

character.

• After removal of a concatenation character, the preceding and following character

strings are concatenated by shifting the remainder of the line one character to the

left. For example, if PROG is a parameter keyword for which the user enters a value

of NEW, the string PR0G_B becomes NEWB after expansion processing.

Following is an example of concatenation character usage.

Procedure LINK resides on ﬁle 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 ﬁrst BEGIN command does a COPYSBF of ﬁle PLAN to ﬁle

SCHEME. The next BEGIN command does a C0PYEI of ﬁle MAZE to ﬁle TAXES. Each resulting

dayﬁle follows the BEGIN command.

begin,link,ﬁlel,sufﬁx=sbf,lfnl=plan,lfn2=scheme.

08.00.17.$BEGIN,LINK,FILE1,SUFFIX=SBF,LFN1=PLAN,LFN2=SCHEME.

08.00.18.REWIND,PLAN.

08.00.18.C0PYSBF,PLAN,SCHEME.

08.00.18. EOI ENCOUNTERED.

08.00.18.$REVERT.CCL

4-8 60459680 G

jst^\.

begin,link,ﬁlel,sufﬁx=ei,lfnl=maze,Ifn2=taxes.

08.03.23.$BEGIN,LINK,FILE1,SUFFIX=EI,LFN1=MAZE,LFN2=TAXES.

08.03.23.REWIND,MAZE.

08.03.24.C0PYEI,MAZE,TAXES.

08.03.24. EOI ENCOUNTERED.

08.03.24.SREVERT.CCL

.EX Directive

The .EX directive immediately terminates expansion processing and executes the command

included in the directive. No further expansion processing is performed, and the procedure

command record is not executed.

The most common use of .EX is to initiate immediate processing of a menu procedure option as

shown in the following example:

.PR0C,APR0C*M

,PARM=

(1-0PT1",

2"0PT2",

3"0PT3").

.EX.BEGIN,PARM,LIBFILE.

EXECUTION OF THE COMMAND RECORD

At completion of expansion processing, the system increments the procedure nesting level

count and begins execution of the procedure command record.

When all commands in the procedure command record have been processed, the system executes a

system- or user-supplied REVERT command, decrements the procedure nesting count, and returns

control to the calling job or procedure.

PROCEDURE DIRECTIVES

Procedure directives have these general syntax features:

• They all have a period as a prefix character.

• You can use a comma or an opening parenthesis as a separator within directives.

• You can use a period or a closing parenthesis as a terminator. You must use a

period or closing parenthesis as a terminator if you append comments to the

directive.

• A procedure directive can span more than one line. No line can contain more than

150 6-bit characterst and each line to be continued must either end with a nonblank

separator or the succeeding line must begin with a nonblank separator.

• Unless otherwise stated, the system reads the characters you enter in directives as

6-bit display code (uppercase characters only). You can enter the text for help

information and prompts in uppercase and lowercase characters (6/12-bit display

code).

tThis value can be changed during installation.

60459680 F 4-9

/*5fi&»i

The detailed descriptions of the procedure directives later in this section include any

exceptions to the general syntax features just cited.

Procedure directives can be grouped by function into six basic types. The directives are

listed by type in table 4-1.

Table 4-1. Procedure Directives

Directive Type Directive Function

Procedure header .PROC Speciﬁes the procedure name, deﬁnes parameters, and

enables parameter prompting.

Formatting .CORRECT Speciﬁes the prompt to follow an incorrect parameter

entry.

.ENTER Speciﬁes the prompt to appear before a parameter entry

is made.

.Fn Speciﬁes a label for programmable function key Fn.

.NOCLR Inhibits the automatic clearing of the screen while the

procedure executes.

.NOTE Speciﬁes a message to appear on the screen while the

procedure executes.

.PAGE Speciﬁes the string to precede the page number on the

screen.

.PROMPT Speciﬁes the text for the general request for input.

Help .ENDHELP Marks the end of the help section of the procedure.

.HELP Speciﬁes help text for the procedure or a parameter.

Expansion .CC Speciﬁes the concatenation character to be used in the

Control procedure body.

.ELSE Terminates skipping initiated by a matching .IF or

initiates skipping until a matching .ENDIF is found.

.ENDIF Terminates skipping initiated by a matching .IF or

.ELSE.

.EX Submits a single command to the system for immediate

execution.

.EXPAND Terminates or restores procedure expansion for

subsequent lines of the procedure.

.IF Allows conditional expansion of the procedure body.

.IC Speciﬁes the inhibit character to be used in the

procedure body.

F i l e .DATA Cre ate s a loca l ﬁle .

.EOF Inserts an end-of-ﬁle mark in a (.DATA) ﬁle created

by the procedure or in the procedure command record.

.EOR Inserts an end-of-record mark in a (.DATA) ﬁle created

by the procedure or in the procedure command record.

Comment .* Identiﬁes comments in the procedure.

4-10 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 deﬁnes any restrictions on values that can

be entered for the parameters.

The .PROC directive must be the ﬁrst line of the procedure and must begin in column 1. It

can be continued on one or more succeeding lines by ending the continued line, or beginning

the continuation line, with a non-blank separator character. The .PROC directive must end

with a pe ri od (. ).

In this section we describe the interactive and menu formats of the .PROC directive,

noninteractive format is described in Appendix L. The

Interactive Format

/jP^N

This directive enables the interactive processing of a procedure call (refer to Requesting

Help on Procedure Calls later in this section). The directive:

• Designates procedure parameters as optional or required.

• Designates permissible values and correct syntax for each parameter through a

checklist.

• Supplies descriptions for each parameter to be used in prompting the procedure

caller.

Format:

.PROC,pname*I"title",pi,p2,...,pn.ck.

Parameter Description

pname

t i t l e

Speciﬁes 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.

Speciﬁes the procedure title. The system assumes that your title is

in 6/12-bit display code, which supports uppercase and lowercase

characters. The title string can be a maximum of 40 lowercase

(12-bit) characters, 80 uppercase (6-bit) characters, or any

combination of lowercase and uppercase characters that does not exceed

480 bits. The title ﬁeld can be null ("") or omitted. If omitted,

the default title used in the screen mode parameter display is the

procedure name pname.

The system displays the title whenever the procedure is called and

required parameters are not supplied.

60459680 E 4-11

Parameter Description

Pi Speciﬁes optional parameters. The maximum number of parameters is

50. Each parameter p^^ has the following form:

keywrd"descriptionl,=( checklist)

or

keywrd'description'=(checklist)

keywrd Speciﬁes the keyword of the parameter, keywrd

can be a string of 1 to 10 alphanumeric

characters. The occurrences of keywrd in the

procedure body are replaced by a value that

conforms to the speciﬁcations made in the

check li st . Th is va lue i s s pe ci ﬁe d b y a

parameter on the procedure call or by default

according to checklist speciﬁcations.t

If keywrd is surrounded by dollar symbols

($keywrd$), any dollar symbols which surround or

are contained within the parameter value will be

retained as a part of the value. Note that when

the user is prompted for the value in screen

mode, the value entered will be treated as a

literal value even if it is not surrounded by

dollar symbols.

description Speciﬁes an optional text string that the system

displays when prompting for a parameter. The

title string can be a maximum of 40 lowercase

(12-bit) characters, 80 uppercase (6-bit)

characters, or any combination of lowercase and

uppercase characters that does not exceed 480

bits. In screen mode, the system will display a

maximum of 40 characters. The description ﬁeld

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 speciﬁed on the call, or

the procedure is a local ﬁle.

4-12 60459680 H

Parameter Description

checklist Speciﬁes a list of the acceptable values and

syntax for p±. The checklist must be enclosed

in parentheses. The value speciﬁed 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

ﬁrst match determines the substitution.

If the checklist is omitted, the system assumes

that any uppercase 1- to 40-character value is

valid. The detailed description of acceptable

checklist entries is in the following paragraphs.

ck Speciﬁes a 1-to 10-character comment keyword. The keyword must be

immediately preceded and followed by periods with no intervening

spaces. This is an optional parameter. The system substitutes

comments speciﬁed 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 signiﬁcance as described under Parameter Matching Modes

later in this section.

CHECKUST ENTRIES

Entries in the parameter checklist are of three types: simple values, equivalenced values,

and checklist patterns. A single checklist can contain any combination of entry types and

multiple entries of the same type.

A simple value is an entry of the form:

p s t r i n g

where pstring is any 1- to 40-character string. If pstring contains nonalphanumeric

characters other than asterisks (*), it must be enclosed in literal delimiters ($). |

A simple value speciﬁes 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 speciﬁes 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 ﬁve checklist patterns that can be used in the checklist. Each pattern deﬁnes a

set of restrictions to be placed on values entered by the user. The ﬁve checklist patterns

are summarized in ﬁgure 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 speciﬁes that a parameter value entered by the user will be substituted for the

parameter keyword if the value meets the requirements deﬁned by *p.

The *p= form speciﬁes 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 speciﬁes 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 speciﬁed in an equivalenced value entry in a

*p=pvalue checklist pattern. These special values are:

Special Value

#DATA

#FILE

//PRIMARY

Signiﬁcance

Speciﬁes the name of the local ﬁle 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 ﬁle name used will be ZZCCLAA,

ZZCCLAB, ZZCCLAC, or so on depending on the nesting level of the

procedure.

Speciﬁes the ﬁle containing this procedure.

Speciﬁes the primary ﬁle.

4-14 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

*Sm..n(chars )=t

or

Description

Allows entry of any character string up to 40 characters. The

string replaces keyword.

Entry of ch aracter str in g cau ses a nul l sub stituti on .

Entry of character string replaces keyword with value.

Allows entry of a valid NOS ﬁle name. The ﬁle name replaces

keyword.

Entry of a ﬁle name causes a null substitution.

Entry of a ﬁle 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.

Speciﬁes that the parameter is optional. No substitution

results.

Speciﬁes that omission of the parameter causes null

substitution.

Speciﬁes 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 deﬁnes all allowable alphanumeric or special

characters, k can be any of the following mnemonic

abbreviations:

A A n y a l p h a b e t i c c h a r a c t e r s

B Any octal characters

D Any decimal characters

AB Any alphabetic and octal characters

AD Any alphabetic and decimal characters

To include an asterisk (*) as a member of the set, append an

asterisk to the mnemonic. For example, D* speciﬁes any

decimal character and * as allowable characters.

Entry of allowable characters causes a null substitution.

*Sm..n/k=t

*Sm..n(chars)=valuet Entry of allowable characters replaces keyword with value.

or

*Sm..n/k=value

pstring

pstring=

pstring=pvalue

Entry of string pstring replaces keyword with pstring.

Entry of string pstring causes a null substitution

Entry of string pstring causes pvalue to replace

keyword.

t The speciﬁcation m..n is optional and deﬁnes the minimum and maximum length of the

character string or ﬁle 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

speciﬁed, 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

*Fm..n=value

*Fm..n=

*Fm..n

Description

Speciﬁes the substitution for keywrd regardless of the speciﬁca

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

speciﬁed 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 ﬁle created by the .DATA

directive (refer to .DATA Directive for the name of this ﬁle). If

value is //FILE, all occurrences of keywrd in the procedure body are

replaced by the name of the ﬁle that contains the procedure. Any

data read from this ﬁle begins with the record immediately

following the record that houses the procedure. If the procedure

resides on a library and is called by a name call form of the BEGIN

command, keywrd is replaced by a null value. If value is //PRIMARY,

all occurrences of keywrd in the procedure body are replaced by the

current primary ﬁle.

If * Am .. n= is in t he che cklis t, a nu ll val ue re place s keywr d. If

*Am..n is speciﬁed, whatever is speciﬁed on the procedure call

replaces keywrd.

If you specify some form of the *A entry more than once in a single

checklist, the system uses the leftmost entry.

Example:

.PR0C,EB0C*I,P1=(*A5),P2=(*A10..15),P3=(*A20..) .

In this procedure header directive, PI allows entry of a character

string 0 to 5 characters long, P2 allows a string 10 to 15

characters long, and P3 allows a string 20 to 40 characters long.

Specifies that the parameter entry for p£ on the procedure call be

a ﬁle name that conforms to the operating system format for a local

ﬁle name. m..n speciﬁes the minimum and maximum length of the

ﬁle 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 ﬁle name is speciﬁed on the procedure

call. You can specify any 0- to 40-character string for value.

You must delimit special characters, other than asterisks (*), with

dollar signs.

4-16 60459680 H

/ffSN.

Checklist Pattern Description

If value is //DATA, all occurrences of keywrd in the procedure body

are replaced by the name of the data ﬁle created by the .DATA

directive (refer to .DATA Directive for the name of this ﬁle). If

value is //FILE, all occurrences of keywrd in the procedure body are

replaced by the name of the ﬁle that contains the procedure. Any

data read from this ﬁle begins with the record immediately

following the record that houses the procedure. If the procedure

resides on a library and is called by a name call form of the BEGIN

command, keywrd is replaced by a null value. If value is //PRIMARY,

all occurrences of keywrd in the procedure body are replaced by the

current primary ﬁle.

If *F m.. n= i s in th e ch eck list , a n ull va lue rep la ces ke ywrd . If

*Fm..n is speciﬁed, the ﬁle name speciﬁed 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 ﬁle EXEC:

.PR0C,EXEC*I,I=(*F4..7),B=(*N=LG0,*F),

L=(*F=0UTPUT).

FTN5,#I=I,#B=B,#L=L.

*K=value

*K=

*K

EXEC is called:

EXEC,I=CARDS,L=PRINT.

The procedure body becomes:

FTN5,I=CARDS,B=LG0,L=0UTPUT.

Speciﬁes the substitution for keywrd when the parameter entry for

pj on the procedure call is only the keyword keywrd or if the

keyword is entered in response to an interactive prompt. If

*K=value is in the checklist, value replaces keywrd in the

procedure body. You can specify any string of 0 to 40 uppercase

characters for value. You must delimit special characters, other

th an as te ri sk s ( *) , wi th dol la r si gn s.

If value is //DATA, all occurrences of keywrd in the procedure body

are replaced by the name of the data ﬁle created by the .DATA

directive (refer to .DATA Directive for the name of this ﬁle). If

value is //FILE, all occurrences of keywrd in the procedure body are

replaced by the name of the ﬁle that contains the procedure. Any

data read from this ﬁle 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 ﬁle.

/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 ﬁle PROCFIL.

.PROC,KEY*I,P1 = (*K),P2=(*K=X),P3=(*K=0. _.

COMMENT. #P1=P1, #P2=P2, #P3=P3 ^

KEY is called:

BEGIN,KEY„P1,P2,P3.

The procedure body becomes:

COMMENT. P1=P1, P2=X, P3=

The following calls to procedures SUBN1 and SUBN2 illustrate the y=^

left-to-right checking of the checklist and the use of equivalent '=^

patterns. Procedures SUBN1 and SUBN2 are on local ﬁles 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

*N=value

*N=

*N

*D=value

*D=

*N

Description

A *K checklist pattern applies only when the keyword is entered by

itself, or in response to an interactive prompt. It does not apply

when an equivalenced value matching the keyword is entered as shown

in the following call to procedure SUBN1:

subn1,P1=p1

The system writes:

P1-STRING

Speciﬁes the substitution for keywrd when there is no parameter

e n t ry f o r p ^ o n t h e p r o c e d u re c a l l. I f * N s = v a lue o r * D =va l u e i s |

in the checklist, value replaces keywrd in the procedure body. You

can specify any string of 0 to 40 uppercase characters for value. I

You must delimit special characters, other than asterisks (*), with I

dollar signs. I

If value is #DATA, all occurrences of keywrd in the procedure body

are replaced by the name of the data ﬁle created by the .DATA

directive (refer to .DATA Directive for the name of this ﬁle). If

value is //FILE, all occurrences of keywrd in the procedure body are

replaced by the name of the ﬁle that contains the procedure. Any

data read from this ﬁle begins with the record immediately

following the record that houses the procedure. If the procedure

resides on a library and is called by a name call form of the BEGIN

command, keywrd is replaced by a null value. If value is //PRIMARY,

all occurrences of keywrd in the procedure body are replaced by the

current primary ﬁle.

If *N= or *D= is in the checklist, a null value replaces keywrd. I

If *N or *D is in the checklist, no substitution occurs. I

I f n o f o r m a t o f t h e * N o r * D e n t r y i s i n t h e c h e c k l i s t , p . i s a |

required parameter and interactive prompting occurs when it is

omitted from the procedure call. Specifying some form of the *N or ■

*D entry more than once in a single checklist is an error. |

Example:

Procedure SUB is on local ﬁle 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 ﬁrst checklist

pattern determines whether the value is displayed.

*Sm..n(chars)=value Speciﬁes that the parameter entry for pA on the procedure call

*Sm..n(chars)= may consist of a string of characters selected (in any order) from

*Sm..n(chars) the set of characters represented by chars or from the set of

or characters represented by k. m..n speciﬁes the minimum and

*Sm..n/k=value maximum values for the length of the string entered on the

* S m . . n / k = p r o c e d u r e c a l l . T h e d e f a u l t f o r m i s 1 a n d f o r n i s 4 0 . T h e

*Sm..n/k maximum value for n is 40. chars represents a set of up to 40

uppercase alphanumeric and/or special characters. Special

characters other than asterisks must be $-delimited. k selects one

of the following sets:

k Characters

A All alphabetic characters

B All octal characters

D All decimal characters

A B A l l a l p h a b e t i c a n d o c t a l c h a r a c t e r s

AD All alphabetic and decimal characters

To include one or more asterisks as members of the set, append an

asterisk to the mnemonic. For example, AB* speciﬁes 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 speciﬁed on the procedure call. You can specify any

string of 0 to 40 uppercase characters for value. You must delimit <>^\

special characters, other than an asterisk (*), with dollar signs. '

If value is //DATA, all occurrences of keywrd in the procedure body

are replaced by the name of the data ﬁle created by the .DATA

directive (refer to .DATA Directive for the name of this ﬁle). If

value is //FILE, all occurrences of keywrd in the procedure body are

replaced by the name of the ﬁle that contains the procedure. Any

data read from this ﬁle begins with the record immediately

following the record that houses the procedure. If the procedure

resides on a library and is called by a name call form of the BEGIN

command, keywrd is replaced by a null value. If value is //PRIMARY,

all occurrences of keywrd in the procedure body are replaced by the

current primary ﬁle.

■■^*K

4-20 60459680 H

Procedure COPIL will accept one to four letters for the F parameter.

More than one set may be speciﬁed 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 ﬁ 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

r

jt$$bz\

If *Sm..n(chars)= or *Sm..n/k= is in the checklist, a null value is

substituted for keywrd. If *Sm..n(chars) or *Sm..n/k is in the

checklist, the parameter entry for pi on the procedure call

replaces keywrd.

Example:

Procedure COPIL is on local ﬁle COPI:

.PR0C,C0PIL*I,0"0LD FILE NAMEH=(*F,*N=OLD),

R"REPLACEMENT FILE NAME"=(*F,*N=LG0),

NMNEW FILE NAME"=(*F,*N=NEW),

L"LAST REC0RD"=(*F,*N=O,

F,,FLAG"=(*S4( ARTE) ,*N=).

COPYL,0,R,N,L,F.

REVERT.

COPIL is called:

BEGIN,COPIL,COPI,0=OLD,R=MODIFID,

N-NEW,F=AE.

The procedure body becomes:

COPYL,OLD,MODIFID,NEW„AE.

Procedure COPIL will accept one to four letters for the F parameter.

More than one set may be speciﬁed for a parameter. For example,

procedure SET has two sets speciﬁed for the P parameter.

.PR0C,SET*I,P=(*S3(ABC),*S3/D).

Parameter entries could include P=BB, P=BCA, or P=901 but not

P=XZY, P=AZ, P=P or P=A2.

Null sets are not allowed. For example, all the set entries for PI

in the following procedure header are in error.

.PROC,ERROR*I,P1 = (*S,*SO,*S3).

60459680 H 4-21

Checklist Pattern

pstring=pvalue

pstring=

pstring

Description

Speciﬁes 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 speciﬁed 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 ﬁle created by the .DATA

directive (refer to .DATA Directive for the name of this ﬁle). If

pvalue is //FILE, all occurrences of keywrd in the procedure body

are replaced by the name of the ﬁle that contains the procedure.

Any data read from this ﬁle 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 ﬁle.

If pstring= is in the checklist, a null value replaces keywrd.

pstring is in the checklist, pstring replaces keywrd.

Example:

Procedure LABL on a global library ﬁle:

.PR0C,LABL*I,FN"FILE NAME"=C*F),

VSN "VSN OF TAPE"=(*A),

WRITE "YES OR N0"=(YES=W,N0=R).

LABEL,FN,#VSN=VSN,#PO=WRITE,WRITE.

REVERT.

If

Procedure LABL is called:

LABL,FN=STATS,VSN=TAPE24,WRITE=N0.

Procedure body becomes:

LABEL,STATS,VSN=TAPE24,P0=R,R.

Menu Format

This format of the .PROC directive generates a menu when you call the procedure and make no

menu selection, when you make an incorrect selection, or when you request help information

(refer to Requesting Help on Procedure Calls). The presence of the NOLIST parameter on the

.HELP directive suppresses the menu display when you request .HELP information.

.^ssfﬁx

4-22 60459680 H

Format:

.PROC,pname*M"title",keywrd=(selections).ck.

Parameter

pname

t i t l e

0^U\

keywrd

selections

ck

Description

Speciﬁes the procedure name, pname must be a 1- to 7-character

string of alphanumeric characters. Make the ﬁrst character of pname

an alphabetic character to avoid inadvertent editing of the primary

ﬁle on name calls to procedures. You must append *M to pname to

enable menu generation.

Speciﬁes the menu title. The title string can be a maximum of 40

lowercase (12-bit) characters, 80 uppercase (6-bit) characters, or any

combination of lowercase and uppercase characters that does not exceed

480 bits. The title ﬁeld can be null ("") or completely omitted. If

you omit title, the system uses the procedure name pname as the title

when the procedure is called in screen mode. The title appears

whenever the system displays the menu.

Speciﬁes 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.

Deﬁnes the menu selections. A maximum of 50 selections can be

deﬁned for a menu. The deﬁnitions must have the following format:

num^Hdescript|",...,numn"descriptn"

num* Deﬁnes an integer number that identiﬁes the menu

selection in the screen display, num^ can be any

integer up to 10 digits in length. Menu selections

appear in the screen display in the order they are

deﬁned in the .PROC directive, not necessarily in the

order deﬁned by the selection numbers.

descript. Describes the menu selection. The description can be

a maximum of 40 lowercase (12-bit) characters, 80

uppercase (6-bit) characters, or any combination of

lowercase and uppercase characters that does not

exceed 480 bits. In screen mode, the system will

display a maximum of 40 characters. You can also

specify a null description ("") or omit this ﬁeld.

This description appears whenever the system displays

the menu.

Speciﬁes a 1- to 10-character comment keyword. This is an optional

parameter. A period must follow the comment keyword. The system

substitutes comments speciﬁed 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:

t i t l e

num-j. descript.j

nun^. descript2

numn. descriptn

SELECT BY NUMBER OR TYPE Q TO QUIT?

where title, nun^, and descriptj conform to the descriptions given them previously. You

can specify the prompt for a selection using the .PROMPT directive. If you do not, the ^-

system uses a default prompt as just shown. Additionally, the system centers all lines when ^1

in screen mode.

The Q option aborts the procedure call and initiates a search for an EXIT command in the

procedure. If the procedure was called from another procedure, the EXIT commands in the

calling procedure or procedures are also processed.

r ^ ^ K

4~22*2 60459680 G

FORMATTING AND HELP DIRECTIVES

Along with the procedure header, the formatting and help directives further deﬁne 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 speciﬁes the ﬁrst ﬁeld 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 ﬁelds:

text parameter descriptiont

This directive speciﬁes the text ﬁeld.

Format:

.CORRECT,text.

.CORRECT=text.

Parameter

t e x t

Description

Speciﬁes 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 ﬁrst format, any alphanumeric or special characters may be

used except a period or right parenthesis (. or )). Special

characters need not be enclosed in $ signs.

In the second format, any characters may be used (including a period

or right parenthesis), but special characters must be enclosed in

$ signs.

In screen mode, the default text string is:

Please correct

In line mode, the default string is:

Correct

In screen mode, if the prompt is too long, the system truncates the prompt and indicates the

truncation with an ellipsis (no truncation occurs in line mode). You can suppress display |

of the parameter ﬁeld of the prompt by using apostrophes rather than quotation marks around

the description in the procedure header. In screen mode, the prompt appears left-justiﬁed

on the top line of the screen.

This directive does not apply to menu procedures.

tThe description ﬁeld does not appear in screen mode.

60459680 H 4-23

■*"«S^V

.ENDHELP Directive

The .ENDHELP directive speciﬁes 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 speciﬁes 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 ﬁelds:

t e x t parameter description

This directive speciﬁes the text ﬁeld.

Format:

.ENTER,text.

,ENTER=text.

Parameter Description

t e x t S p e c i ﬁ 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 ﬁrst 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 ﬁelds of the prompt by using apostrophes around the description

in the procedure header. In screen mode, the prompt appears left-justiﬁed on the top line

of the screen.

This directive does not apply to menu procedures.

4-24 60459680 H

'*^S\

.Fn Directive

The .Fn directive speciﬁes 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 ﬁ 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 ﬁrst 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

Key

Fl

F2

Default Label

FWD

BKW

F3 HELP FWD

F4 HELP BKW

F5 HELP

F6 QUIT

Function

Pages forward through screens of parameters or menu

selections.

Pages backward through screens of parameters or menu

selections.

Pages forward through screens of .HELP text.

Pages backward through screens of .HELP text.

Displays .HELP text at the bottom of the screen.

Aborts the procedure call and initiates search for an

EXIT command in the current procedure and (if nested) in

the calling procedure(s).

.HELP Directive

The .HELP directive indicates that the text that follows it is information about the

procedure itself or its parameters. The procedure caller can access this information by

entering a question mark as a parameter in a procedure call or by appending a question mark

to the procedure name or a parameter name. When the system encounters a question mark in a

procedure call, it stops processing the call and starts help processing. Therefore,

anything entered after the question mark will not be read. Refer to Requesting Help on

Procedure Calls later in this section. If speciﬁed, .HELP directives must immediately

precede the .ENDHELP directive.

Formats:

0&>\

■g^S\

.HELP.

.HELP,,NOLIST.

.HELP,parm.

.HELP,parm,NOLIST.

Parameter

NOLIST

parm

Description

Suppresses the display of some of the .HELP text during help

processing.

Speciﬁes one of the parameter keywords in an interactive procedure

(*I) or speciﬁes one of the menu selections (choice^) in a menu

procedure (*M).

The ﬁrst and second formats indicate that the text that follows the directive describes the

procedure itself. For interactive procedures in line mode, the NOLIST parameter suppresses I

the display of a parameter list when the caller requests information about the procedure

itself. For menu procedures, the NOLIST parameter suppresses the display of the menu in

line mode.

For interactive procedures, the third, and fourth formats indicate that the text that follows

the directive describes the parameter associated with the keyword parm. The NOLIST

parameter suppresses the display of acceptable parameter values as given in the parameter's

checklist.

60459680 H 4-25

>*^\

For menu procedures, the third and fourth formats indicate that the text following the

directive describes the speciﬁed menu selection. The NOLIST parameter suppresses the

display of the menu after the display of the .HELP text.

The text information starts on the line following the .HELP directive. The text can span

multiple lines and must end with either another .HELP directive or an .ENDHELP directive.

Parameter substitution does not occur within the .HELP text.

The system assumes that your .HELP text is in 6/12-bit display code, which supports

uppercase and lowercase characters. In batch jobs, the system displays .HELP text in

uppercase only.

Interactive (*I) Help

When you request help information about an interactive procedure, the system displays the ^^1

following: '

• The text following the procedure's .HELP directive.

• The parameters that follow the procedure name on the .PROC directive unless

suppressed by the NOLIST parameter of the .HELP directive (.HELP,,NOLIST).

• A prompt fo r a value . The pr omp t includes the de scriptive strin g specified with th e

parameter in the .PROC directive.

When you request information about a particular parameter of an interactive procedure, the ^%

system displays the following: /

• Parameter values that are acceptable according to the parameter's checklist (the

presence of NOLIST on the parameter's .HELP directive suppresses the display of

these values).

• The text that follows the parameter's .HELP directive.

• The current value, if any, of the parameter.

•A prompt for a value. The prompt includes the descriptive string specified with the /*®\

parameter on the .PROC directive. )

Menu (*M) Help

When you request help information about a menu procedure, the system displays the following:

• The text following the procedure's .HELP directive.

• The menu unless suppressed by the NOLIST parameter of the .HELP directive

(.HELP,,NOLIST).

• A prompt for a menu selection.

When you request information about a particular menu selection, the system displays the

following:

• The text following the .HELP directive for that menu selection.

• The menu unless suppressed by the NOLIST parameter of the .HELP directive.

• A prompt for a menu selection.

4-26 60459680 G

^***!\

/^**

r

Line Mode Example:

Procedure PRINT (on ﬁle PRINT) veriﬁes that the selected ﬁle is local before it routes

t h e ﬁ l e t o a p r i n t e r.

| NOTE

The .HELP text uses lowercase and uppercase

characters.

,PROC,PRINT*I,F"FILE NAME"=(*F),

rDC'DISPOSITION CODE"=(*N=LP,LP,PR,LR,LS,LT).

.HELP.

This procedure routes a permanent ﬁle to the selected line printer.

.HELP,F.

The name of the permanent ﬁle to be routed.

.HELP,DC.

The disposition code. DC accepts only the line printer options.

.ENDHELP.

.I F,F ILE (F,. NOT. LO ),P F.

GET,F.

.ELSE,PF.

r REWIND,F.

.ENDIF,PF.

COPYSBF,F,Z.

ROUTE,Z,#DC=DC.

REVERT,NOLIST.

To get a description of procedure PRINT, either append a question mark to the ﬁle name or

enter a question mark as the ﬁrst parameter. If PRINT is a local ﬁle, you can get such a

description by entering any of the following:

PRINT?

r PRINT,?

BEGIN,PRINT,PRINT?

BEGIN,PRINT,PRINT,?

If PRINT is not local, enter any of the following:

BEGIN,PRINT,PRINT?

or

BEGIN,PRINT,PRINT,?

or

GET,PRINT

PRINT,?

or

GET,PRINT

PRINT?

60459680 H 4~27

The following is a sample of the dialogue generated by the .PROC and .HELP directives:

/begin,pri nt,print?

This procedure routes a permanent ﬁle to the selected line printer.

PARAMETERS FOR PRINT ARE F, DC

ENTER F FILE NAME? ?

ALLOWABLE VALUE(S)

MUST BE A FILE NAME

The name of the permanent ﬁle to be routed.

ENTER F FILE NAME? dataﬁ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?

This procedure routes a permanent ﬁle to the selected line printer.

PARAMETERS FOR PRINT ARE F, DC

FILE NAME? ?

ALLOWABLE VALUE(S)

MUST BE A FILE NAME

The name of the permanent ﬁle to be routed.

FILE NAME? dataﬁ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 deﬁned in the previous

example):

PRINT

yjpfet.

F FILE NAME:

DC DISPOSITION CODE: LP

Specify values and press NEXT when ready

/$fj^s F5 | HELP| F6 | QUIT|

If you press the HELP key while the cursor is positioned in the input ﬁeld for ﬁrst

parameter, you get the following screen:

PRINT

F FILE NAME:

DC DISPOSITION CODE: LP

ALLOWABLE VALUE (S)

MUST BE A FILE NAME

The name of the permanent ﬁle to be routed.

Specify values and press NEXT when ready

F FILE NAME

JsPN F 5 | H E L P 1 F 6 J Q U I T

60459680 H 4-29

If you press the HELP key while the cursor is positioned in the input ﬁeld for the second

parameter, you get the following screen:

PRINT

F FILE NAME:

DC DISPOSITION CODE: LP_

Specify values and press NEXT when ready

DC DISPOSITION CODE

ALLOWABLE VALUE(S)

PR

LR

LS

LT

PARAMETER MAY BE OMITTED

The disposition code. DC accepts only the line printer options,

F5 HELP F 6 Q UI T

To get help information about the procedure itself, you can append a question mark to the

name of procedure on the call or press the HELP key again after you get help for any of the

parameters.

PRINT

F FILE NAME:

DC DISPOSITION CODE: _kP_

Specify values and press NEXT when ready

PRINT

This procedure routes a permanent ﬁle 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 speciﬁed to do otherwise, the

system clears the screen at the end of the call, and the screen is blank until the procedure

completes execution or sends output to the terminal.

The .NOCLR directive must be placed before any .HELP directives in the procedure.

Format:

.NOCLR,message.

.N0CLR=message.

Parameter Description

message Speciﬁes a 1- to 40-character text string that appears on the

screen. You can use uppercase and lowercase characters in the string.

In the ﬁrst 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 speciﬁes the message that appears on the screen and in your dayﬁle at

the end of the procedure call (once all required parameters are supplied). Unless speciﬁed

to do otherwise, the system clears the screen at the end of the call (refer to the .NOCLR

Directive), and the screen is blank until the procedure completes execution or sends output

to the terminal.

Format:

.NOTE,message.

,NOTE=message.

Parameter Description

message Speciﬁes a 1- to 40-character text string that appears on the screen

and in your dayﬁle. You can use uppercase and lowercase characters

in the string.

In the ﬁrst 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 speciﬁes the string that precedes the page number for procedure

displays that require more than one screen.

Format:

.PAGE,text.

.PAGE=text.

Parameter

t e x t

Description

Speciﬁes a 0- to 40-character text string. You can use uppercase and

lowercase characters in the string. The default is:

Page

In the ﬁrst 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 deﬁnes 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 ﬁeld immediately follows

this prompt. In line mode, this directive applies only to menu procedures, where the system

produces a screen-like display.

Format:

.PROMPT,text.

.PR0MPT=text.

Parameter

t e x t

Description

Speciﬁes 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 ﬁrst 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 speciﬁes 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 Speciﬁes the new concatenation character.

.EXPAND Directive

The .EXPAND directive terminates or restores procedure expansion for subsequent lines of the

procedure. The .EXPAND directive can be used anywhere in the procedure following the

formatting and help directives.

Format:

EXPAND,option

60459680 H 4-33

-^

Parameter

ON

OFF

Description

Speciﬁes that subsequent lines of the procedure will be expanded

normally. This is the default value.

Speciﬁes that no parameter substitutions or directive processing will

be performed on subsequent lines. In other words, any subsequent

commands or procedure directives will be written to the command record

just as they appear in the procedure ﬁle.

.IC Directive

The .IC directive speciﬁes the character used to inhibit parameter substitution or

directive processing during procedure expansion. The new inhibit character remains in

effect u nt il the procedure t er mi na te s or un ti l you enter a no th er .IC directive. The d ef au lt

inhibit character is the ASCII character // or the CDC graphics character = . The .IC

directive can be placed anywhere in the procedure.

Format:

.IC(n)

Parameter Description

Speciﬁes the new inhibit character.

.SET Directive

The .SET directive allows you to build new parameters using strings and substrings created

by the STR, STRB, and STRD functions and concatenation operations, which are described in

section 6.

Format:

• SETjkeywd^strexpj,... ,keywdi=strexpi,

Parameter

keywd^

strexp^

Description

Deﬁnes a new keyword or references an existing keyword, either

from the .PROC header or from an earlier .SET directive. Keywd^

can be used for substitution in subsequent statements just as if

it had been a formal parameter contained in the .PROC header.

May be any valid CCL expression, usually but not necessarily an

expression which produces a string result. If the result of

strexpj^ is not a string but a value, the value is left-justiﬁed

and considered a string. The resulting string in either case is

substituted for any occurrences of keywd^ in subsequent

statements of the procedure.

4-34

.'J-S5!Ni

60459680 H

j0JHfeS

Example 1:

.PR0C,CATTER*I,P1=(*A),P2=(*S3/D).

.SET,K9=STR($P1$,1,4)//STRD(P2,-1).

.IF,$K9$.EQ.$G00D1$,G0.

NOTE./THE 1ST 4 CHAR OF P1 AND THE LAST OF P2 = K9.

,ELSE,GO.

REVERT,EX.DISPLAY,STR($SORRY, K9 IS NOT G00D1$).

.ENDIF,60.

In this example, two substrings were concatenated to produce one string in the .SET

expression. Every occurrence of keyword K9 in the lines following the .SET directive is

replaced by the string resulting from the concatenation of substrings PI and P2. If GOODY

and 101 were supplied as values for PI and P2, the value of K9 would be set to G00D1. (For

a detailed explanation of how the STR and STRD functions operate, refer to section 6.) The

subsequent .IF statement would be true, causing the NOTE command to be included and

executed. If BADNEWS were substituted for PI, the .IF statement would be false, resulting

in the execution of the REVERT command and then of the DISPLAY command.

Example 2:

.PR0C,VALUES*I,P1=(*S/D),P2=(*S/D).

.SET,V1=STRD(P1+P2),V2=STRD(P1*P2),V3=STRD(P1**P2).

-IF,V1=V2=V3.NOTE./SUM, PRODUCT AND POWER ARE EQUAL.

NOTE./THE SUM OF P1 AND P2 IS V1.

NOTE./THE PRODUCT OF P1 AND P2 IS V2.

N0TE./P1 TO THE POWER OF P2 IS V3.

As this example demonstrates, the .SET directive along with the STRD function can create new

keywords which make it possible to include arithmetic values as strings in subsequent

commands and directives.

FILE DIRECTIVES

The ﬁle directives either create local ﬁles during procedure expansion time or place ﬁle

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 ﬁle when the procedure is called. The data ﬁle can contain program

source code, other NOS procedures, or any other type of data.

Format:

.DATA,lfn.

60459680 H 4-34.Ii

Parameter Description

l f n S p e c i ﬁ e s t h e n a m e o f t h e ﬁ l e o n w h i c h t h e d a t a l i n e s a r e t o b e

wr it te n. I f a ﬁ le n am ed l fn i s alr ea dy as si gned t o th e jo b, it is

returned, and new local ﬁle lfn is created. You cannot specify INPUT

for lfn. If lfn is not speciﬁed, the .DATA ﬁle can be referenced in

the procedure header using the special symbol //DATA.

The default for lfn depends on the nesting level of the procedure. At

the ﬁrst procedure level, the system calls this ﬁle ZZCCLAA; at the

second procedure level, it is ZZCCLAB; and so on.

You can use the .IF, .ELSE, and .ENDIF directives within the data lines following the .DATA

directive to conditionally include lines in the data ﬁle.

File marks generated by .EOR and .EOF directives can subdivide the lines written to the data ^^

ﬁle into records or ﬁles. The sequence of data lines is terminated by one of the

following:

• Another .DATA directive.

• An end-of-record (not an .EOR directive) in the procedure file.

• An end-of-file (not an .EOF directive) in the procedure file.

• An end-of-information in the procedure file.

The data ﬁle created does not include the .DATA directive. Keyword substitution continues

within the data ﬁle unless you insert a .EXPAND directive to suspend expansion processing.

After the data ﬁle is written, it is rewound.

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 ﬁle 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 ﬁle

DATAFIL.

BEGIN,ALPHA,DATAFIL.

A sample of a resulting dayﬁle is:

11.07.59.BEGIN,ALPHA,DATAFIL.

11.07.59.FTN5,I=ZZCCLAA,L=FTN0UT.

11.08.00. 61000 CM STORAGE USED.

11.08.00. 0.015 CP SECONDS COMPILATION TIME.

11.08.00.LGO.

11 . 0 8 . 0 0 . S T O P

11 . 0 8. 0 0 . 5 6 00 F I NAL E X E C UTI O N F L .

11.08.00. 0.000 CP SECONDS EXECUTION TIME.

11.08.00.REPLACE,FTNOUT.

11.08.01.$REVERT.CCL

All input after the .DATA directive (the FORTRAN 5 source program) is written onto the

default temporary ﬁle 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 ﬁle 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 ﬁle PFILE.

.PR0C,BETA*I,

P1 = (*F,*N=#FILE),

LSTFILE=(*F,*N=FTNOUT).

FTN5,I=P1,L=LSTFILE.

LGO.

REPLACE,LSTFILE.

-EOR-

PROGRAM BPROG

statements

■

END

The following call accesses procedure BETA on ﬁle PFILE.

BEGIN,BETA,PFILE.

The following is a segment of the resulting dayﬁle. Parameter substitution occurred within

the procedure but not within the FORTRAN 5 program.

11.08.35.BEGIN,BETA,PFILE.

11.08.36.FTN5,I=PFILE,L=FTN0UT.

11.08.36. 61000 CM STORAGE USED.

11.08.36. 0.013 CP SECONDS COMPILATION TIME.

11.08.36. LGO.

11.08.37. STOP

11.08.37. 5600 FINAL EXECUTION FL.

11.08.37. 0.000 CP SECONDS EXECUTION TIME.

11.08.37.REPLACE,FTN0UT

11.08.37.$REVERT.CCL

4-36 60459680 E

Example 3: Procedure accesses program data from another ﬁle

A procedure may access data outside of the procedure ﬁle. The following procedure is in

the default ﬁle PROCFIL. It uses a GET command to access the program data on ﬁle 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 ﬁle GAMMA.

BEGIN,GAMMA„P1 =TEST.

Parameter substitution occurred within the procedure but not within the FORTRAN 5 program,

as shown in the following dayﬁle segment.

11.06.48. BEGIN, GAMMA,, P1=TEST.

11.06.48.GET,TEST.

11.06.49.FTN5,I=TEST,L=FTN0UT.

11.06.50. 61000 CM STORAGE USED.

11.06.50. 0.013 CP SECONDS COMPILATION TIME.

11.06.50.LGO.

11.06.51. STOP

11 .06 . 5 1. 5 6 0 0 F I NA L E XEC U T IO N F L .

11.06.51. 0.000 CP SECONDS EXECUTION TIME.

11.06.51.REPLACE,FTN0UT=LISTFIL.

11.06. 51.SREVERT.CCL

60459680 D 4-37

I .EOF (or .EOP) Directive

| The .EOF (or.EOP) directive generates an end-of-ﬁle on the data ﬁle created with a .DATA

directive. Wherever an .EOF appears, an actual end-of-ﬁle is recorded when the data ﬁle

is written on the ﬁle speciﬁed in the .DATA directive. The system always writes an

end-of-record at the end of a data ﬁle. If you want an end-of-ﬁle also, you must end the

ﬁle with an .EOF directive. The .EOF directive is valid only after a .DATA directive. The

.EOP directive may be used interchangeably with the .EOF directive.

Format:

.EOF.

I . E O P .

| .EOR (or .EOS) Directive ■*%,

The .EOR (or .EOS) directive is used to separate records in a data ﬁle created with a .DATA

directive. Wherever an .EOR is placed, an actual end-of-record is recorded when the data

ﬁle is written on the ﬁle speciﬁed in the .DATA directive. The system always writes at

least one end-of-record at the end of a data ﬁle, whether or not you specify an .EOR

I directive. The .EOR directive is valid only after a .DATA directive. The .EOS directive

may be used interchangeably with the .EOR directive.

Format:

.EOR. /*^\

| . E O S . )

BRANCHING DIRECTIVES

The branching directives provide conditional inclusion of commands, other directives, or

data lines in the procedure. The function of the .ELSE, .ENDIF, and .IF directives is much

like that of their command equivalents. The branching can appear in any of the four

sections of the procedure body.

.ELSE Directive

The .ELSE directive in conjunction with the .IF directive either terminates or initiates the

skipping of lines in the procedure body.

Format:

•ELSE.label.

Parameter Description

label Speciﬁes 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

0^<K

.ENDIF Directive

The .ENDIF directive terminates skipping initiated by a matching .IF or .ELSE directive

(directives match only if their label parameters are identical).

Format:

.ENDIF,label.

Parameter Description

label Speciﬁes a 1- to 10-character, alphanumeric string. The string

must begin with an alphabetic character.

.EX Directive

The .EX directive submits a single command to the system for immediate execution. The

system performs keyword substitutions in the command before executing the command. No

further procedure directives are normally processed. Although .DATA ﬁles are created, the

command record is never executed. Since the command record is not executed, the procedure

nesting level of your job is not incremented.

Format:

.EX.command.

Parameter Description

command Any valid command. The length of the expanded command cannot exceed

80 characters.

If the command entered by .EX aborts, the system responds as though the command had been

entered from the calling job or procedure.. For example, assume that procedure A calls

procedure B and that procedure B contains a .EX directive. If the command entered by the

•EX directive is erroneous, the system immediately suspends command processing and begins

searching for an EXIT command in procedure A.

The .EX directive is most often used in menu procedures in which the command executed by .EX

is a call (BEGIN command) to another procedure. Since the purpose of the menu procedure is

merely to prompt for a single item of user input, the most efﬁcient way of calling the

resulting procedure is in a .EX directive.

Example:

The following menu procedure initiates one of three nested procedures, (EXEC1, EXEC2, or

EXEC3) depending on the menu item selected.

.PR0C,FIX*M,P=

(1"OPTION 1",

2"0PTI0N 2",

3"0PTI0N 3").

.EX.BEGIN,EXEC_P,PFILE.

REVERT,NOLIST.

r60459680 G 4-39

.IF (or .IFE) Directive

The .IF directive conditionally writes lines from the procedure body to the procedure

command record or the ﬁle associated with the .DATA directive. The .IF directive is to the

procedure command record as the IF command is to the job command record (refer to the IF

command). Before evaluating the conditional expression, the system performs parameter

substitution for the portion of the directive that follows the .IF. Since the system

processes the .IF directive at procedure expansion time, the .IF directive cannot depend

upon the effects of commands in the procedure body.

Formats:

.IF,expression.command.

.IF,expression,label.

Parameter Description

expression Speciﬁes an expression that is either true or false (refer to Command

Syntax in section 6). The separator following expression in the ﬁrst

format must be a terminator.

command Speciﬁes any valid system command.

label Speciﬁes a 1- to 10-character, alphanumeric string. The string must

begin with an alphabetic character. An identical string must appear

in a subsequent .ELSE or .ENDIF directive.

If expression is true, the ﬁrst format writes command in the procedure command record while

the second format processes all lines between the .IF directive and the ﬁrst matching .ELSE

or .ENDIF directive (two directives match only if their label parameters are identical).

If expression is false, the system does not write command in the procedure command record

| (for the ﬁrst format) nor does the system write and process the lines between the .IF

directive and the ﬁrst matching .ELSE or .ENDIF directive (for the second format).

| NOTE

When using the ﬁrst format (.IF,expression,

command.), values for .command, that match a

CCL relational, logical, or string operator

(such as .EQ. or .OR.) are interpreted as

operators, causing the procedure to abort.

To write a valid .IF directive when .command,

matches an operator, terminate the expression

or command with a right parenthesis instead

of a period.

4-40 60459680 H

COMMENT (.*) Directive

The .* directive enables you to document a procedure with internal comments. These comments

do not appear in the dayﬁle when the procedure is processed. The comment, which follows

the .*, can contain any combination of characters.

Format:

,*comment

Parameter Description

comment Represents your comments.

The comment directive can appear anywhere in the procedure body. However, a comment

directive inserted in the help section is considered as part of the help text.

r

i#^*>

60459680 H 4-40.1/4-40.2 |

*%

CALLING A PROCEDURE (BEGIN COMMAND)

The BEGIN command initiates execution of a procedure. When a BEGIN command is entered, the

system begins executing the speciﬁed 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 ﬁrst 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 ﬁrst level nested procedure call.

Batch Job File

AJOB.

USER,USERNAME,PASSWORD.

BEGIN, APROC'

Procedure

.PR0C,APR0C*I,

REVERT.

Interactive Command

Procedure

BEGIN,BPROC

.PR0C,BPR0C*I.

BEGIN, CPROC

REVERT.

Procedure

.PR0C,CPR0C*I.

REVERT.

Figure 4-5. Calling a Procedure

60459680 D 4-41

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 speciﬁed in the procedure header (refer to .PROC Directive earlier in this

section).

The system allows you to input the parameters from a full-screen format if the following

conditions are true:

• Your terminal supports full-screen input for procedures (currently, only a CDC 721).

• Your terminal is in screen mode (refer to the SCREEN command).

• The procedure is interactive; that is, the .PROC directive contains a *M or *I.

• You do not supply required parameters on the procedure call.

Formats:

BEGIN,pname,pﬁle,pj,p2,...,pn.comment

or

-pn am e ,p ﬁl e ,p i, p 2, ... ,p n.c om men t

or

pname,pj,p2,...,pn.comment

or

pﬁle,pi,p2,...,pn.comment

The ﬁrst format is the full BEGIN command format that can be used in either batch or

(interactive jobs. When you use this format, the system uses the following search order when

attempting to locate ﬁle pﬁle:

• local files

• indirect access files in your permanent file catalog

• direct access files in your permanent file catalog

• indirect access files under user name LIBRARY

• direct access files under user name LIBRARY

The second format can be used only from an interactive job. It uses the same search order

as the ﬁrst format.

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.

ﬁle. The system executes the ﬁrst procedure on pﬁle. pﬁle is the name of a local

00^\

/ j ^ N

Parameter Description

pname Speciﬁes the procedure name from the procedure header directive. If pname

is omitted from the ﬁrst format, two consecutive commas must be speciﬁed.

The default procedure is the record at the current position of pﬁle. If

pﬁle is at its end-of-information, the system rewinds pﬁle and uses the

ﬁrst procedure on pﬁle. If pﬁle is INPUT, the ﬁle is not rewound.

pﬁle Speciﬁes the name of the ﬁle containing the procedure. The ﬁle name

pﬁle must be inserted as the second parameter in the ﬁrst 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 pﬁle

(refer to Requesting Help on Procedure Calls later in this section). File

pﬁle is not automatically returned after the procedure executes.

If pﬁle is omitted from the ﬁrst format, the installation-deﬁned default

ﬁle name is used (PROCFIL is the default).

Pi Speciﬁes an optional parameter that may affect the substitution to be made

for a keyword used in the procedure. The value you specify is compared to

the appropriate checklist speciﬁed for this parameter in the procedure

header. The checklist entries are checked in a left-to-right fashion and

the ﬁrst match determines the substitution. Refer to the .PROC Directive

in this section for more details on parameter substitution. The speciﬁc

formats for p^ are described later in this subsection.

If you are using the third or fourth format of the BEGIN command as

previously shown, there is a 7-character restriction on both the keyword

portion and the value portion of the parameter p^.

comment Speciﬁes 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

keywrd Speciﬁes a parameter identical to a keyword on the procedure header.

Substitution is controlled by the *K entry in the checklist for the

parameter.

key wr d? Spe ciﬁes in te ra ct iv e BEGI N processi ng (re fe r to Requ esting H el p on

or Procedure Calls later in this section).

1

keywrd= Removes keywrd in the procedure body (null substitution) unless overridden

by a checklist speciﬁcation.

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 speciﬁes 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 speciﬁed with the last occurrence of the keyword.

4-44 60459680 H

/0SS*\

Pi Description

val Unless overridden by a checklist speciﬁcation, assigns this 0- to

40-character (uppercase only) symbolic name or value to the keyword whose

position in the procedure header parameter list matches the position of this

parameter in the BEGIN command parameter list (refer to Parameter Matching

Modes in this section). Special characters (nonalphanumeric), other than

asterisks (*), must be delimited by dollar signs. This parameter format has

the following variations:

Format

val

val+

val+D

val+B

Meaning

Substitutes the string val itself.

Substitutes the decimal value associated with val.

Substitutes the decimal value associated with val,

Substitutes the octal value associated with val.

NOTE

If you specify a parameter p^ on a name

call to a local ﬁle, neither the keyword

keywrd or the value val can exceed seven

characters.

For menu procedures (*M), the procedure call can contain only one substitution parameter

p^. On such calls, p^ can have one of the following formats:

Pi Description

choice Speciﬁes a menu selection that appears on the procedure header. The menu

selection must be an unsigned integer.

choice? Speciﬁes interactive help processing (refer to Requesting Help on Procedure

or Calls later in this section).

1

If you omit p^, the system displays the menu and prompts for a menu selection.

Example:

The following procedure is accessed by a sequence of BEGIN commands in the command record of

the j ob.

.PR0C,TEST1*I,FK.

COMMENT. FK

60459680 H 4-45

The resulting dayﬁle shows each BEGIN command and the substitutions made. The relevant

segment of the dayﬁle is as follows:

10.15.26.BEGIN,TEST1,FKTEST,20.

10.15.27.COMMENT. 20

10.15.27. RE VERT. CCL

10.15.27.SET,R2=100.

10.15.27.BEGIN,TEST1,FKTEST,FK=R2+.

10.15.28. COMMENT. 100

10.15.28. REVERT.CCL

10.15.28.BE6IN,TEST1,FKTEST,FK=R2+D.

10.15.29.C0MMENT. 100

10.15.29.REVERT.CCL

10.15.29.BEGIN,TEST1,FKTEST,FK=R2+B.

10.15.30.COMMENT. 144

10.15.30. RE VERT. CCL

10.15.30.BE6IN,TEST1,FKTEST,FK.

10.15.31 .COMMENT. FK

10.15.31.RE VERT.CCL

10.15.31.BEGIN,TEST1,FKTEST,FK=.

10.15.32.COMMENT.

10.15.32. REVERT. CCL

10.15.32.BE6IN,TEST1,FKTEST,VALUE.

10.15.33.C0MMENT. VALUE

10.15.33.REVERT.CCL

10.15.34.BEGIN,TEST1,FKTEST,$VALUE-2$.

10.15.34.COMMENT. VALUE-2

10.15.34. REVERT.CCL

10.15.35.BE6IN,TEST1,FKTEST,*.

10.15.35.COMMENT. *

10.15.35.REVERT.CCL

REQUESTING HELP ON PROCEDURE CALLS

After you call a procedure interactively but before the system executes the speciﬁed

procedure, you can have a dialogue with the system about the procedure. This is possible

only if the procedure writer appended the *I or *M to the procedure name in the procedure

header (refer to the .PROC directive described in this section). You can do any of the

following:

• Request help information about the procedure itself.

• Request help information about a procedure parameter.

• Supply omitted parameters.

• Reenter parameter values that are in error.

If the parameter speciﬁcations 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 speciﬁed 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 speciﬁed 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 satisﬁed.

• It is a menu procedure executing in line mode and you enter Q. The system does not

execute the menu. For nested menu procedures, entering Q causes the system to

discontinue expansion of the current procedure and begin searching for an EXIT

command in the calling procedure.

0^" • Your terminal is in line mode and you enter the termination or interruption

character for your terminal (refer to appendix J). The BEGIN command processing

ends and the system does not execute the procedure. For nested procedures,

terminating the dialogue in this way causes the system to search for an EXIT command

in the calling procedure.

• Your terminal is in screen mode and you press the QUIT key. The system does not

execute the procedure. For nested procedures, terminating the dialogue in this way

causes the system to search for an EXIT command in the calling procedure.

rAs with all commands, you can always append a comment after the terminator on the call.

Additionally, you can append a comment to a parameter entry made during a parameter-

prompting dialogue. Still, the comment must follow a terminator (refer to the last example

in this subsection).

0$^>\

60459680 E 4-47

The procedure calls in table 4-3 illustrate the various methods of requesting help on

procedure calls. For convenience, we show the name call format of the BEGIN command.

Table 4-3. Help on Procedure Calls

Procedure Call

Re suit

Interactive

Procedure (*I)

Menu

Procedure (*M)

pname The system prompts for

required parameters or

parameter values in error.

The system displays the

menu and prompts for a

selection.

pname ? The system provides any

.HELP text about the pro

cedure itself and then

prompts for parameters.

The system provides any

.HELP text about the proce

dure itself, displays the

menu, and prompts for a

selection.

pname,? Same as pname? . Same as pname,? .

pname,keywrd? The system provides any

.HELP text for the

parameter associated

with keywrd and then

prompts for parameters.

Not applicable.

pname,choice? Not applicable. The system provides any

.HELP text for that menu

selection, displays the

menu, and prompts for a

selection.

4-48 60459680 H

'^\

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 dayﬁle. If any of the required parameter

speciﬁcations are in error, error messages appear in the dayﬁle. In either case, the

system does not execute the procedure.

The following example shows the interactive entry of parameters.

Example:

Procedure F5 resides on local ﬁle 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 ? bﬁle

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 ? bﬁle

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 ﬂOPTION 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. ﬁnally

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 dayﬁle.

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 dayﬁle.

EX Returns control to the command record of the calling

procedure and executes the command com as if the

command had actually appeared in the calling

procedure. The EX parameter causes the REVERT command

to appear in the job dayﬁle 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 dayﬁle.

If you omit opt, control returns to the command following the calling

BEGIN command. The REVERT command appears in the job dayﬁle but not

at a terminal unless you are under the batch subsystem and the REVERT

is not within a nested procedure call.

Speciﬁes 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 ﬁle called PROCFL. It reverts to the job calling

it if the named ﬁle has no read permission and aborts (causing control to be transferred to

the job EXIT command) if the named ﬁle 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 ﬁle; REVJ0B2 attaches a read or execute ﬁle.

REVJOB1 attaches an

REVJ0B1.

USER,USERNAM,PASSWRD,FAMNAME.

ATTACH,FILE1/UN=ALTUSER,PW=PW1,M=E.

BEGIN,REVTST,PR0CFL,FILE1,XFIL.

COMMENT. RETURNS HERE

EXIT.

COMMENT. EXIT ON ERROR

REVJ0B2.

USER,USERNAM,PASSWRD,FAMNAME.

ATTACH,FILE2/UN=ALTUSER,PW=PW2,M=R.

BEGIN,REVTST,PR0CFL,FILE2,XFIL.

COMMENT. RETURNS HERE

EXIT.

COMMENT. EXIT ON ERROR

The following are the dayﬁle segments produced by REVJOB1 and REVJOB2. REVJOB1

processes the REVERT command and terminates normally. REVJ0B2 processes the

REVERT,ABORT command and terminates by error processing.

17.03.53.REVJ0B1.

17.03.53.USER,USERNAM„FAMNAME.

17.03.53.CHARGE,*.

17.03.53.* CHARGE(1514,5612PAY)

17.03.56.ATTACH,FILE1/UN=ALTUSER,M=E.

17.03.56.BEGIN,REVTST,PR0CFL,FILE1,XFIL.

17.03.56.REVERT.N0 READ PERMISSION

17.03.56.COMMENT. RETURNS HERE

17.03.56.EXIT.

17.05.05.REVJ0B2.

17.05.05.USER,USERNAM„FAMNAME

17.05.05.CHARGE,*.

17.05.05.* CHARGE(1514,5612PAY)

17.05.13.ATTACH,FILE2/UN=ALTUSER,M=R.

17.05.13.BEGIN,REVTST,PR0CFL,FILE2,XFIL.

17.05.13.TDUMP,I=FILE2.

17.05.13. TDUMP COMPLETE.

17.05.13.REVERT,AB0RT. NO READ/MODIFY

PERMISSION

17.05.13.EXIT.

17.05.13.COMMENT. EXIT ON ERROR

4-52 60459680 H

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 ﬁle:

.PROC, ITEM*I,F"LOCAL FILE NAME"= (*N=LG0,*F),

L"NAME OF LIST OUTPUT FILE"= (*N=OUTPUT,*F),

BL"EACH FILE START ON NEW PAGE? YES OR N0'^= (YES=$,BL$,N0=,*N=),

NR"REWIND BEFORE & AFTER? YES OR N0"= (YES=,N0=$,NR$,*N = ).

IT EM IZ E, F, #L =L_BL_N R.

REVERT.

The procedure is called:

ITEM,LIST,,NO,NO.

The parameters are matched in order-dependent mode and the procedure body becomes:

ITEM IZE,LIST,L=OUT PUT, NR.

REVERT.

In order-dependent mode, the system treats excess parameters on the BEGIN command as a

nonfatal error.

ORDER-INDEPENDENT MODE

For each BEGIN command, parameter matching always starts in order-dependent mode. The

system switches to order-independent mode if, in the comparison of a BEGIN command parameter

and a procedure header parameter, one of the following occurs.

• A parameter on the procedure call is in the format keyword=value.

• A reverse slant (\) precedes the parameter on the .PROC directive or the BEGIN

command.

• A slant (/) precedes the parameter on the .PROC directive.

• A slant precedes the parameter on the procedure call and a slant separates any two

parameters on the .PROC directive.

60459680 D 4-53

However, if a slant is speciﬁed 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 speciﬁcation on

the procedure call.

To show order-independent parameter matching, the preceding example is slightly modiﬁed.

An *K entry has been added to the BL parameter checklist to make BL a valid parameter

entry. A reverse slant is used as a separator before the NR parameter to ensure

order-independent mode.

.PR0C,ITEM1*I,F"L0CAL FILE NAME"=(*N=LGO,*F), "^

L"NAME OF LIST OUTPUT FILE"= C*N=OUTPUT,*F), •

\NR"REWIND BEFORE & AFTER? YES OR NO"=(YES=,NO=$,NR$,*N=),

BL"EACH FILE START ON NEW PAGE? YES OR N0"=(YES=$,BL$,N0=,*N=,*K=$,$8L).

ITEMIZE,F,#L=L_BL_NR.

REVERT.

The procedure call (ITEM1 is on a global library ﬁle):

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 speciﬁed in the BL parameter

checklist, the system accepts BL as a parameter entry. The NR parameter must be speciﬁed

as NR=value or omitted.

After the substitution, the procedure body becomes

ITEMIZE,LIST,L=OUTPUT,BL,NR.

REVERT.

4-54 60459680 H

Ar€Stj^>^

COMMAND PROCESSING

Global Library File Commands

System Commands

Jobs entering the system consist of one or more logical records. The ﬁrst logical record

contains system directives (commands) which describe the processing that is to occur in the

job ﬁle. In interactive jobs, you enter the commands directly at the terminal. This

section describes command processing and how the commands affect other aspects of job

processing.

The operating system recognizes four types of commands.

• Local File Commands These commands call programs or procedures on

ﬁles that are assigned to the job. The name of

the command is simply the name of the ﬁle. LGO

is an example. It is the system default local

ﬁle used for retaining object code generated by

one of the language processors.

These commands call programs or procedures on

ﬁles that have been speciﬁed in a LIBRARY

command.

These commands are divided into 10 categories.

Flow control commands

Job control commands

Special commands for interactive jobs

File management commands

Permanent ﬁle commands

Load and dump central memory commands

Tape management commands

System utility commands

Librar y uti li ty comman ds

Loader commands*

The product set commands call the various products

available under NOS. Their formats are given in

the applicable product reference manual and in the

NOS 2 Applications Programmer's Instant.

Since your executing programs can access the command record of your job, it is possible that

they might manipulate items like user names and passwords. Hence, your executing programs

can affect system security.

Product Set Commands

tRefer to the CYBER Loader Reference Manual.

60459680 D 5-1

COMMAND FORMAT

All commands consist of from one to four ﬁelds. The ﬁrst ﬁeld is optional. It is a $ or

/ preﬁx character which precedes the program name. If a $ is present, it indicates that

the speciﬁed program to be executed must be loaded from the system library. Therefore,

even if a local ﬁle of the same name is present or a program or procedure of the same name

resides on one of your global library ﬁles, 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 ﬁrst ﬁeld of all commands. Even in the batch

subsystem, the system places a $ in front of the ﬁle editing commands ALTER, DELETE, DUP

LIST, MOVE, READ, WRITE, and WRITEN. '

If you use a slant in the ﬁrst ﬁeld of local ﬁle or global library ﬁle commands, the

system processes the parameters in operating system format. For global library ﬁle

commands, the presence of an NPC= entry point in the speciﬁed 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 ﬁle and global library ﬁle 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 ﬁle EXTRACT is a local ﬁle and you enter /*^\

/EXTRACT, A,B, 10.

the system treats the ﬁle as a local ﬁle command. The parameters are processed in

operating system format because of the leading slant.

The second ﬁeld contains the name of the program to be executed. The command name can be

any valid ﬁle name.

The third ﬁeld (optional) contains parameters which further deﬁne the operation to be ^.

performed. The parameter ﬁeld is set off from the name ﬁeld by a separator character. A "*^\

valid terminator character must follow the third ﬁeld (or the second ﬁeld if no parameters '

are present). In interactive jobs, the terminator is optional.

The fourth ﬁeld consists of a comments ﬁeld. The comments ﬁeld follows the terminator.

In general, the system ignores this ﬁeld. However, some commands (MODIFY, FSE, GTR

LIBEDIT, and the like) read this comments ﬁeld for directives. '

In general, commands may not be continued beyond a single line. Exceptions are the

execution control commands (described in section 6) and tape management commands (described

in section 12).

Global library ﬁle 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 ﬁle 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

0^\

Operating System Format

1. Valid separators are

+ - " / = , (

and any other character with a display

code value greater than 44g except

* ) $ . and blank.

2. Valid terminators are

. )

3. Letters, numbers, and the * are

the only characters allowed in the

parameter ﬁeld. The one exception

to this rule is the use of literals

(that is, character strings delimited

by dollar signs). Characters other

than letters, numbers, and the * can

be included in literals. No char

acters within a literal have special

meanings; the system merely checks

the syntax of the literal. The

called program must do its own

processing of the literal.

4. All embedded blanks within a command

except those appearing in literals

are ignored.

5. Comments may appear on the command

but they must follow the terminator.

They may contain any character.

Comments are not printed for some

commands.

6. Parameters, s eparators, an d termi

nators are stored in the job's ﬁeld

length beginning at RA+2. The char

acters , . and ) are stored as binary

zero. For all parameters and all valid

separators except the comma, their dis

play code equivalent is stored. Refer

to section 10 of Volume 4, Program

Interface, for more information.

Product Set Format

1. Same as for the operating system

format.

2. Same as for the operating system

format.

3. Same as for the operating system

format.

4. Same as for the operating system

format.

5. Same as for the operating system

format.

6. Parameters are stored in their dis

play code equivalent beginning at

RA+2. Separators and terminators are

stored as follows:

Character

>((SWSy

Code (Octal)

1

2

3

4

5

6

60459680 E 5-3

Operating System Format Product Set Format

Character Code (Octal)

»10

) or . 17

Other valid 16

separators

7. File names are one to seven alpha

numeric characters.

8. Not NOS/BE compatible.

Refer to section 10 of Volume 4,

Program Interface, for more

information.

7. File names are one to seven alpha

numeric characters. In some products,

ﬁle names beginning with a numeric

character are invalid.

8. NOS/BE compatible.

,^s>!\

In general, no parameter can contain more than seven characters. The exceptions include

procedure calls, ﬂow control commands, some tape management commands and system or global

library ﬁle commands with an ARG= entry point.

Depending on the program, the parameters can appear in either order-dependent or order-

independent format. Order-dependent parameters are required when the parameters must be

passed in a speciﬁc 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 speciﬁed.

Order-independent parameters may be passed in any order. This is made possible by the use

of keywords. A keyword is an identiﬁer 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 speciﬁc 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 ﬁrst character of the ﬁrst parameter and the ﬁrst two characters of the

second parameter.

5-4 60459680 E

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

ﬁrst J008 words of your job's ﬁeld length, from RA through RA+77r. Section 1 and

appendix E in Volume 4, Program Interface, describe the ﬁ?st lOOgwords of ?his area.

The following commands produce the same image in the job communication area,

are processed using operating system format. Both commands

PERMIT,FILEABC,USERAAA=R,USERBBB=W.

$PERMIT,FILEABC,USERAAA=R,USERBBB=W.

COMMAND PROCESSING FLOW

The system translates a command by:

1. Reading the command from the job's command record.

2. Verifying the format of the command as described in Command Format.

3. Comparing special command names with the name of the command being processed. If

the command name is CTIME, HTIME, RTIME, *, or STIME, the system processes the

command. r

4.

5.

6.

7.

8.

9.

Searching the ﬁle name table for a ﬁle 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 ﬁle command

with an ARG= entry point. The CPU is requested to begin execution unless special

loader commands follow.

Searching the global library directory for a program name that matches the command

name. If a $ precedes the command name, this step is skipped. If the program is

found, the system proceeds as in step 4; otherwise, the system searches further.

Searching the central library directory for a program name that matches the command

name. If the name is found, the system proceeds as in step 4; otherwise, the system

searches further.

Searching the peripheral processor library directory for a program name that matches

the command name if the command name is a three-character name with the ﬁrst

character alphabetic. If found, the name is placed, with a maximum of two

arguments, as a peripheral processor request, and the system exits to the program.

If the command name is not found during any of the above searches, the command is

declared invalid and the job is aborted.

A command is normally echoed to the dayﬁle except for system commands or global

library commands containing an SDM= entry point in the entry point list.

Figure 5-1 illustrates the ﬂow of command processing.

60459680 E 5-5

READ A

COMMAND

KD

COMMAND PROCESSOR

SEARCHES ITS LIST OF

COMMAND NAMES FOR

SPECIAL COMMAND

PROCESS

SPECIAL

REQUEST

SEARCH GLOBAL

LIBRARY SET FOR

COMMAND NAME

USE NOS FORMAT

FOR PROCESSING

PARAMETERS

SEARCH PP LIBRARV

FOR NAME. IF NAME

IS VALID PP

PROGRAM NAME

SEARCH FNT FOR

FILE ASSIGNED TO

THIS JOB

USE NOS FORMAT

FOR PROCESSING

PARAMETERS

_J

PROCESS FIELD

LENGTH CONTROL

(SEE SECTION 3)

LOAD PROGRAM

TO CENTRAL

MEMORY

STORE COMMAND

AND COMMAND

ARGUMENTS IN

JOB'S FIELD

LENGTH

EXECUTE

PROGRAM

PLACE NAME WITH

UP TO TWO OCTAL

ARGUMENTS AS A

PP REQUEST

EXIT TO PROGRAM \

(NO FL CHANGE) J

Figure 5-1. Command Processing Flow

5-6 60459680 C

/^X

EXIT PROCESSING

When an error condition occurs during a job, the system searches the command record for an

EXIT command.* If the record does not contain an EXIT command, the system terminates the

job if the job is not interactive or returns control to the terminal if the job is

interactive. If the system ﬁnds 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 ﬂag has been set by the NOEXIT command prior to the error, the error ﬂag is

cleared, no search is made for an EXIT command, and processing continues with the next

command. An ONEXIT command can be used to return to error processing mode; it clears the no

exit ﬂag.

The following sequence of commands illustrates this exit processing.

JOBCCC.

USER,SMITH22,SMAL

NOEXIT.

GET,A,B.

ONEXIT.

ATTACH,MASTER/M=W.

SKIPEI,MASTER.

COPYBF,A,MASTER.

COPYBF,B,MASTER.

PACK,MASTER.

COPYSBF,MASTER.

EXIT.

ENQUIRE,F.

-EOR-

-EOI-

This job attempts to make local copies of two indirect access permanent ﬁles and adds them

to a direct access ﬁle. The NOEXIT command suspends error processing, and the job

continues even if ﬁle A or B is not found. The ONEXIT command turns error processing back

on. If any error occurs thereafter, processing skips to the EXIT command and continues with

the ENQUIRE command. If no error occurs after the ONEXIT command, processing continues

until reaching the EXIT command and then the job terminates (ENQUIRE command is not

processed).

r*After a security conﬂict, the system does not always allow EXIT processing. Refer to

Security Features in section 3.

/fSN

60459680 E 5-7

/^%

FLOW CONTROL COMMANDS

0$®$*\

Flow control commands control the processing sequence of commands within the command record

of a job. They can insert commands from a procedure ﬁle, conditionally or unconditionally

skip commands, and control error processing. To determine the conditions for transfer of

control, you can use error ﬂags, ﬁle attributes, or other job attributes. The ﬂow

control commands and a brief description of each appear in the following list:

Command Description

BEGIN Initiates processing of a procedure.t

DISPLAY Evaluates an expression and displays the result in the dayﬁle of the

job.

E L S E Te r m i n a t e s s k i p p i n g i n i t i a t e d b y a f a l s e e x p r e s s i o n w i t h i n a n I F c o m m a n d

or initiates skipping to a matching ENDIF command.

ENDIF Terminates skipping initiated by a matching IF, SKIP, or ELSE command.

ENDW Establishes the end of the loop.

E X I T C o n t r o l s t h e c o m m a n d ﬂ 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 ﬁ e s t h e t y p e o f e r r o r s t h e s y s t e m r e c o g n i z e s f o r E X I T p r o c e s s i n g .

NOEXIT Disables EXIT error processing.

O N E X I T E n a b l e s E X I T e r r o r p r o c e s s i n g .

REVERT Returns processing from a procedure to the command record of procedure

that called it.

SET Assigns values to special symbolic names.

SKIP Skips to the ﬁrst matching ENDIF command.

WHILE Establishes the beginning of a loop. If the associated expression is

true, the loop is processed; if it is false, the loop is not processed.

T Section 4 contains a detailed description of this command.

60459680 D 6-1

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 signiﬁcant 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 (speciﬁed 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, overﬂow

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 he a rith meti c op era tors .

Operator

+Addition.

-Subtraction.

*Multiplication.

/Division.

** Exponentiation.

Leading - Negati on . Th is ope rato

Leading + Ignored.

Operation

RELATIONAL OPERATORS

A relational operator produces a value of 1 if the relationship is true, and 0 if it is

false. The following are the relational operators (either form may be used).

Operator Operation

.EQ. Equal to.

^ . N E . Not equal to.

< . L T . Less than.

> . G T. Greater than.

_< .LE. Less than or equal to.

> . G E . Greater than or equal to.

60459680 H 6-3

LOGICAL OPERATORS

When an expression contains a logical operator, the system evaluates all bits of each

operand. Each bit of the ﬁrst 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-ﬁll to the length of

the longer string for the logical operation, and trailing binary zero characters are

tru ncat ed fr om the resul t stri ng.

Operator Operation

•EQV. Equivalence (complement of the logical sum).

.OR. Inclusive OR (logical sum).

.AND. AND (logical product).

• X O R . E x c l u s i v e O R ( l o g i c a l d i f f e r e n c e ) .

. N O T . N O T .

STRING OPERATORS

String operators operate on string operands. A string operand is the result of one of the

functions STR, STRB, STRD, or of a logical operation involving one or more string operands.

Operator Operation

// .CAT. Concatenation of two strings into one string. (Either // or .CAT. may

be used.)

Example:

.PR0C,CATTER*I,P1=(*A),P2=(*S3/D).

,IF,STR($P1$,1,4)//STRD(P2,-1).EQ.$G00D1$,G0.

NOTE./THE 1ST 4 CHAR OF P1 ARE GOOD AND P2 ENDS IN 1

.ELSE,G0.

REVERT,EX.DISPLAY,STR($SORRY, P1 IS NOT GOODS).

.ENDIF,GO.

In this example, two substrings were concatenated to produce one string in the .IF

expression. If GOODY and 101 were supplied as values for PI and P2, the .IF statement would

be true, and the NOTE command would be included and executed. If BADNEWS were substituted

for PI, the .IF statement would be false, resulting in the execution of the REVERT command

and then of the DISPLAY command.

^^

6-4 60459680 H

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 ﬁrst 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 ﬁnal character. The

ﬁnal character can be a postradix of D or B to indicate the number base of the constant. A

postradix of B denotes an octal integer. D or an omitted postradix denotes a decimal

integer.

Literals

A literal is a $-delimited string of characters or a string containing a $-delimited

string. The literal can be a null string ($$). The maximum length for a literal is 10

characters, unless it appears within the STR function, in which case it may be any length up I

to the maximum length of the line. I

60459680 H 6-5

Special characters can appear in literals but they must appear in the $-delimited portion of

the string. To represent a dollar sign within a literal, you must use double dollar signs.

Valid Literal Invalid Literals

$LITERAL1$ LITERAL1

$5LITERAL$ $LITERAL2

$*LITERAL$ LITERAL3$

$$$LITERAL$ *$LITERAL$

$$$$ $$*LITERAL$

$$LITERAL$ 1

$$$

When a literal appears as an operand in a command, a function, or an expression, the system

processes it as an integer whose value is equal to the display code representation of the

literal value rather than as a character string.

A non-numeric string that appears in an expression to be evaluated must be entered as a

literal; otherwise, the system treats it as an erroneous symbolic name.

Example: "s^.

/IF,AFILE.EQ.AFILE,LABEL.

CCL157- UNKNOWN NAME - AFILE

The above command will execute successfully if the ﬁle names are entered as literals

(that is, as integer values):

/IF,$AFILE$.EQ.$AFILE$,LABEL.

When you instruct the system to display the value of a literal string, the system

right-justiﬁes the display code value of the string. If the string is the result of the ^\

STR, STRB, or STRD function, it is left-justiﬁed and displayed as a character string. '

Example:

/display,$Lit$

49748 141124B

/display,$a$

1 1 B

/display,1

1 1 B

/display,$1$

2 8 3 4 B

/display,$$$$

4 3 5 3 B

/display,literal

CCL157- UNKNOWN NAME - LITERAL

/display,STR(SREALLY A STRINGS).

REALLY A STRING

/ -^^Sv

6 6 6 0 4 5 9 6 8 0 H

yfﬂS?^

Name Description

PW Page width (default=136 characters, minimum=40, maximum=255).

PD Page density (default=6 lines per inch; allowable values are 6 or 8),

SC Your job's service class.

S L Te r m i n a l d i s p l a y m o d e ( 0 = l i n e , l = s c r e e n ) .

S S Yo u r c u r r e n t s u b s y s t e m f o r i n t e r a c t i v e j o b s .

TIME Current time of day in the form hhmm.

VER Operating system version number (6-bit display code).

WEEKDAY The day of the week returned as a numerical value.

M O N M o n d a y ( n u m e r i c a l v a l u e = 1 ) .

T U E T u e s d a y ( n u m e r i c a l v a l u e = 2 ) .

WED Wednesday (numerical value - 3).

THU Thursday (numerical value =4).

FRI Friday (numerical value =5).

SAT Saturday (numerical value =6).

S U N S u n d a y ( n u m e r i c a l v a l u e = 7 ) .

60459680 E 6 - 6 . 1 / 6 - 6 . 2

As noted in the previous example (DISPLAY,LITERAL), nonnumeric strings that are not

$-delimited cannot appear as operands. If they appear as such, the system treats them as

erroneous symbolic names. You can, however, use such strings as parameter values for

procedures.

r

/gpN

SYMBOLIC NAMES

A symbolic name is a system-deﬁned string of characters to which the system or you can

assign a value. The symbolic names represent job or system attributes. You can ascertain

and sometimes change these attributes by using these symbolic names (refer to the various

commands and functions described later in this section).

Most symbolic names have an initial value of zero. The exceptions are shown in the

following list:

Name Description

CSET Terminal character set mode (NORMAL=0 or ASCII=1).

CS Connection status.

D AT E T h e d a t e i n t h e f o r m y y m m d d .

D A Y T h e d a y o f t h e m o n t h .

DAYS Number of days since January 1, 1977.

HID Two-character machine identiﬁer (6-bit display code).

MONTH The month of the year.

NWK Terminal network connection.

OT Your job's origin type.

PD Page density (default=6 lines per inch; allowable values are 6 or 8).

PL Page length (default=60 lines, minimum=!16, maximum=255).

PS Page size (same as page length).

PW Page width (default=136 characters, minimum=40, maximum=255).

SC Your job's service class.

SL Terminal display mode.

S S Y o u r c u r r e n t s u b s y s t e m f o r i n t e r a c t i v e j o b s .

TIME Current time of day in the form hhmm.

VER Operating system version number (6-bit display code).

VERCCL CYBER control language release level displayed as a numeric value.

WEEKDAY The day of the week returned as a numerical value.

60459680 H 6-7

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

dayﬁle (refer to SET Command in this section).

EF Previous error ﬂag.

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

dayﬁle.

EF Previous error ﬂag.

EFG Global error ﬂag.

EM Current exit mode (refer to MODE Command, later in this section).

Rl Control register 1 contents.

RIG Global control register 1 contents.

R2 Control register 2 contents.

R3 Control register 3 contents.

S S S u b s y s t e m f o r a n I n t e r a c t i v e j o b .

/ ^ ^ V

6-8 60459680 H

Symbolic names whose values are set by the operating system.

0^\

Name

CMN

CS

CSET

DATE

DAY

DAYS

DSC

ECN

EF

FAMILY

FL

HID

MFL

MFLL

MONTH

NWK

OT

SC

SL

SPS

SPW

SPD

n

Description

Central memory RFL setting divided by 100g (refer to RFL Command

in section 7).

Connection status.

Terminal character set mode (NORMAL=0 or ASCII=1).

The date in the form yymmdd.

The day of the month.

Number of days since January 1, 1977.

Flag indicating that skipped commands are to be entered in the

dayﬁle.

Extended memory RFL setting divided by IOOO3 (refer to RFL

Command in section 7).

Previous error ﬂag.

Current family name.

Current CM ﬁeld length.

Two-character machine identiﬁer (6-bit display code).

Maximum CM ﬁeld length.

Maximum extended memory ﬁeld length.

The month of the year. (January = 1, February = 2, etc.)

Network type; possible values for NWK are:

0 = Terminal not connected to NAM.

1 = Terminal connected to NAM/CCP.

2 = Terminal connected to NAM/CDCNET.

Job origin type.

Service class of the job.

Terminal display mode (LINE or SCREEN).

System page size (in lines).

System page width (in characters).

System page density (in lines per inch).

60459680 H 6 - 8 . 1 / 6 - 8 . 2

Name

SSM

Description

Operating system security mode (0 means unsecured. 1 means

secured).

SYS Host operating system.

TIME Current time of day (hhmm).

V E R O p e r a t i n g s y s t e m v e r s i o n n u m b e r ( 6 - b i t d i s p l a y c o d e ) .

WEEKDAY The day of the week (Monday = 1, Tuesday = 2, etc.).

• Symbolic name whose value is set by the calling or termination of a procedure.

Name Description

PNL Procedure nesting level (0 when processing the original command

record, 1 when processing a ﬁrst level procedure, and so forth).

Its maximum value is 50.

Symbolic name whose value can be set by the termination of a procedure (refer to SET

Command in this section).

Name

EFG

Description

Global error ﬂag.

Symbolic names with ﬁxed values that can be compared with the error ﬂag value (EF

or EFG) within an expression. These values correspond to error code values. In an

expression, you can check the error ﬂag (EF) for a nonzero value; a nonzero value

indicates an error, and a zero value indicates no error. For detailed error

examination, you can compare EF with a particular symbolic name or its error code

value. You are encouraged to use the symbolic name, because the numeric values can

change in future releases of NOS. The following list contains the errors that allow

exit processing.

Name Value (Octal) Description

TIE User break 1.

TAE User break 2.

ARE Arithmetic error.

ITE SCP invalid transfer address.

PSE Program stop error.

PPE PPU abort.

60459680 H 6-9

/^tf&w£$V

Name Value (Octal)

CPE

PCE 10

11

MLE 14

TLE 15

FLE 16

TKE 17

SRE 20

FSE 22

RCE 23

ODE 24

IDE 25

SPE 26

STE 27

ECE 30

RSE 31

SSE 32

RRE 34

OKE 35

DRE 37

RAE 40

JSE 41

SVE 42

SYE 43

PEE 44

SWE 45

Description

CPU abort.

PPU call error.

Reserved for installation.

Message limit.

Time limit error.

File limit error.

Track limit error.

SRU limit error.

Forced error; set by operator entry of ERR. under

DIS utility.

Job hung in auto recall.

Operator drop.

Idledown.

Reserved for your site.

Suspension timeout.

Extended memory parity error.

Recovered system (level 3).

Subsystem aborted.

Operator rerun.

Operator kill.

Deadstart rerun.

Recovery abort.

Job step abort.

S e c u r i t y c o n ﬂ i c t .

System abort.

CPU parity error.

Software error.

6-10

^*ES\

60459680 G

Name Value (Octal)

ORE

MXE

46

47

Description

Override error condition.

Maximum number of error ﬂags.

Symbolic names with ﬁxed 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 ﬁxed values that can be compared with the terminal character

set-mode (CSET) value within an expression.

Name

NORMAL

ASCII

Value

0

1

Description

Uppercase characters only.

Uppercase and lowercase characters.

Symbolic names with ﬁxed values that can be compared with the month of the year

(MONTH) value within an expression.

Name Value Description

JAN January.

FEB February.

MAR March.

APR April.

MAY May.

JUN June.

JUL July.

AUG August.

SEP September.

OCT 10 October.

NOV 11 November.

DEC 12 December.

60459680 G 6-10.1

Symbolic names with ﬁxed values that can be compared to the terminal's network

connection (NWK) value within an expression.

Name Value Description

Terminal has no NAM connection.

Terminal is connected using NAM/CCP.

Terminal is connected using NAM/CDCNET.

Symbolic names with ﬁxed values that can be compared with the origin type (OT)

value within an expression.

NONE

CCP

CDCNET

Name Value Description

BCO Local batch origin.

IAO I nte r a c ti v e o r i g in.

RBO Remote batch origin

SYO System origin.

Symbolic names with ﬁxed values that can be compared with the service class (SC)

value within an expression:

Description

System service class.

Local batch service class.

Remote batch service class.

Interactive service class.

Detached interactive service class.

Network supervisor service class.

Subsystem service class.

Maintenance service class.

Communication task service class.

Installation service class 0.

Installation service class 1.

Installation service class 2.

Installation service class 3.

Deadstart service class.

Name Value

SYSC

BCSC

RBSC

TSSC

DISC

NSSC

SSSC

MASC 10

CTSC 11

IOSC 12

use 13

I2SC 14

I3SC 15

DSSC 77

6-10.2 60459680 G

0^\

Symbolic names with ﬁxed values that can be compared with the terminal display mode

(SL) value within an expression.

Name

LINE

SCREEN

Value

0

1

Description

Line mode.

Screen mode.

Symbolic name with a ﬁxed value that can be compared with the host operating system

(SYS) value within an expression.

Name Value Description

Network Operating System.

Network Operating System/Batch Environment.

SCOPE 2 Operating System.

Symbolic names with a ﬁxed value that you can compare with the subsystem for an

interactive job (SS).

NOS

NOSB

SC2

Name Value

ACCESS

BASIC

BATCH

EXECUTE

FORTRAN

FTNTS

NULL

Description

The access subsystem.

The BASIC subsystem.

The batch subsystem.

The execute subsystem.

The FORTRAN 5 subsystem.

The FORTRAN Extended 4 subsystem,

The null subsystem.

0^\

60459680 G 6-11

Symbolic names with true or false values. True is 1; false is 0.

Name

F

FALSE

SWn

T

TRUE

Description

Fixed value of 0 (false).

One of six sense switches (n can be from 1 to 6). Their values

are set by the OFFSW, ONSW, and SWITCH commands (refer to section

/) •

Fixed value of 1 (true).

Symbolic names with ﬁxed values that can be compared with the day of the week

(WEEKDAY) value within an expression.

Name Value Description

MON Monday.

TUE Tuesday.

WED Wednesday.

THU Thursday.

FRI Friday.

SAT Saturday.

SUN Sunday.

FUNCTIONS

Functions are used as expressions or operands within expressions in commands. Functions are

| not commands. The functions are FILE, DT, LEN, NUM, STR, STRB, and STRD.

FILE Function

| The FILE function determines whether a local ﬁle has a speciﬁed attribute. The system

returns a value of 1 (true) or 0 (false) depending upon whether the ﬁle has or does not

have the speciﬁed attribute(s). Only the equipment number (EQ) attribute can return values

othe r than 1 or 0. Th e lis t of ﬁ le att ri but es fol low s the desc rip ti on o f the FILE fun cti on

format.

The FILE function must be used as an expression or as a part of an expression in a command.

A left parenthesis must appear before the ﬁle name, a comma must appear between the ﬁle

name and the expression, and a right parenthesis must appear after the expression.

6-12 60459680 H

/*S%v

Format:

FILE(Ifn,expression)

Parameter

lfn

expression

/gptev

/S^^N

Description

Name of the local ﬁle for which attributes are being determined.

Either a special FILE function attribute or an expression, consisting

of logical operators and special FILE function attributes. The

expression must be appropriate for the command in which the FILE

function appears. If the FILE function is part of an IF command or

.IF directive, the expression should be one that can be evaluated as

true or false. If the FILE function is part of the DISPLAY command,

the expression could have a numeric value other than a true or false

value.

The expression within a FILE function cannot include the NUM function,

the symbolic name SS, or another FILE function; the DT function or the

following symbolic names can be used within the expression. Any other

symbolic name within the expression is treated either as an implicit

DT function (refer to DT Function which follows) or as an unidentiﬁed

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 ﬁle 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 ﬁle 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 ﬁle on mass storage.

EQ EST ordinal of the equipment on which the ﬁle

resides. If the ﬁle is not assigned to a device, it

has an EST ordinal of zero.

EX File has execute permission.

FS File size in PRUs.

GL File is a global library.

IN File type is input.

LB File is on a labeled tape.

LI File is a system library ﬁle.

60459680 H 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 ﬁle.

PT File type is primary.

Q F F i l e t y p e i s q u e u e d .

RA File has read append permission.

RD File has read permission.

RM File has read modify permission.

RU File has read update permission.

T P F i le i s o n m a g n e t i c t a p e.

TT File is assigned to a terminal. /B^t

UP F ile has upd a te p e rmi s sio n .

WR File has write permission.

Z L F i l e h a s z e r o l e n g t h .

Example:

The following job segment shows the FILE function being used inside an IF command. The FILE

function determines if ﬁle 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 ﬁle 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

deﬁnes the mnemonics.

>*s^\

6-14 60459680 E

Format:

FILE(lfn,DT(dt))

Parameter Description

lfn Name of the ﬁle for which device residence is being determined.

d t A t w o - c h a r a c t e r m n e m o n i c i d e n t i f y i n g t h e d e v i c e , w h i c h m a y b e a n y o n e

of the following:

Type Equipment

DB 885-42 Disk Storage Subsystem (full-track).

DC 895-1/2 Disk Storage Subsystem (full-track).

DD 834 Disk Storage Subsystem (full-track).

D E E x t e n d e d m e m o r y .

DF 887 Disk Storage Subsystem (4K sector; full track). |

DG 836 Disk Storage Subsystem (full-track).

DH 887 Disk Storage Subsystem (16K sector; full track). I

DI 844-21 Disk Storage Subsystem (half-track).

DJ 844-41/44 Disk Storage Subsystem (half-track).

DK 844-21 Disk Storage Subsystem (full-track).

DL 844-41/44 Disk Storage Subsystem (full-track).

DM 885-11/12 Disk Storage Subsystem (half-track).

DP Distributive data path to extended memory.

D Q 8 8 5 - 11 / 1 2 D i s k S t o r a g e S u b s y s t e m ( f u l l - t r a c k ) .

DV 819 Disk Storage Subsystem (single-density).

D W 8 1 9 D i s k S t o r a g e S u b s y s t e m ( d o u b l e - d e n s i t y ) .

MT Magnetic tape drive (seven-track).

NE Null equipment.

NT Magnetic tape drive (nine-track).

TT Interactive terminal.

60459680 H 6-15

0*&$$\

Example:

The following dayﬁle 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 speciﬁed string,

Format:

LEN(st ri ng )

Parameter

s t r i n g

Description

A string of any length up to the maximum length of a CCL line. If the

string is a literal, the length returned is the length of the string

after the removal of the surrounding dollar signs ($) and of any extra

dollar signs within the string.

NUM Function

The NUM function determines whether a character string is numeric. It evaluates the

character string as true (1) if it is numeric or false (0) if it is not. NUM must be used

as an expression or as part of an expression.

Format:

NUM(string)

Parameter

s t r i n g

Description

A string of 1 to 40 characters. If the string contains one or more

special characters, it must be delimited by dollar signs (for example,

$***$). if delimited by dollar signs, the string is always evaluated

as non-numeric.

Example:

The following procedure uses the NUM function to ensure that the passed parameter, NUMBER,

is numeric. If a non-numeric value is passed, the procedure terminates with an appropriate

message.

6-16 60459680 H

/ ^ ^ \

.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-justiﬁed string of any length up to the maximum CCL line

length. The STR function makes it possible to manipulate character strings greater than 10

characters in length. An STR function result may be compared or combined with the results

of STRB, STRD or other STR functions in a variety of ways.

Format:

STR(strexp,lc,rc)

Parameter

strexp

lc

Description

May be any legal CCL expression, usually but not necessarily a

literal. Literals are left-justiﬁed, and may be any length up to the

maximum line length. Nonliteral values are treated normally during

evaluation of the expression. However, a numeric result will be

left-justiﬁed and treated as a string.

Must be an expression producing a numeric result, either positive or

negative, lc indicates which character of strexp is to be the

leftmost character of the string produced by STR, counting from the

left if lc is positive or from the right if negative. A value of zero

or a negative value which exceeds the length of strexp is treated as

equivalent to 1. A positive value greater than the length of strexp

produces a null string, lc may be omitted if it would reference the

leftmost character of strexp and if re is also omitted. (The

preceding comma must also be omitted when lc is omitted.)

Must be an expression producing a numeric result, either positive or

negative, re indicates which character of strexp is to be the

rightmost character of the string produced by STR, counting from the

l e f t i f r e i s p o s i t i ve o r f r o m t h e r i g h t i f n e g a t i v e . A p o s i t i v e

value greater than the length of strexp is considered equal to the

length. A value of zero or a negative value which exceeds the length

of strexp produces a null string, re may be omitted if it would

reference the rightmost character of strexp. (The preceding comma

must also be omitted when re is omitted.)

In summary, lc and re both reference the string strexp in the same

way: a positive value of n indicates the nth character of strexp

counting from the leftmost character, 1 meaning the ﬁrst 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-justiﬁed string of 1 to 17 characters

representing the octal value of a speciﬁed expression.

Format:

STRB(numexp,lc,rc)

Parameter

numexp

lc

Description

May be any legal CCL expression, usually but not necessarily numeric.

If numexp is or contains a literal, the literal is limited to no more

than 10 characters and will be right-justiﬁed and binary-zero ﬁlled

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

Speciﬁes which character of numexp is to be the leftmost in the

resulting string. For further explanation of this parameter, refer to

the description of the STR function.

Speciﬁes which character of numexp is to be the rightmost in the

resulting string. For further explanation of this parameter, refer to

the description of the STR function.

/*^%K

Example:

Each of the following expressions will produce the string $102$.

STRB($ABC$,-5,-3).

STRB(10203B,-5,-3).

• 6-16.2 60459680 H

STRD Function

The STRD function produces a left-justiﬁed string of 1 to 16 characters representing the

decimal value of a speciﬁed expression.

Format

STRD(numexp,lc,re)

Parameter

numexp

lc

Description

May be any legal CCL expression, usually but not necessarily numeric.

If numexp is or contains a literal, the literal is limited to no more

than 10 characters and will be right-justiﬁed and binary-zero ﬁlled

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

Speciﬁes which character of numexp is to be the leftmost in the

resulting string. For further explanation of this parameter, refer to

the description of the STR function.

Speciﬁes which character of numexp is to be the rightmost in the

resulting string. For further explanation of this parameter, refer to

the description of the STR function.

Example:

The following expression produces a string of $0012$.

STRD(10000+36/3,-4).

COMMAND DESCRIPTIONS

Individual descriptions of the commands follow in alphabetic order,

BEGIN COMMAND

Refer to Calling a Procedure in section 4.

60459680 H 6- 16 .3 •

DISPLAY COMMAND

The DISPLAY command evaluates an expression and sends the result to the job dayﬁle 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 Speciﬁes any valid symbolic name or expression described earlier in

this section.

Example:

The following sample dayﬁle shows several display operations.

12.53.18.DISPLAY/TIME.

12.53.18. 1253 2345B.

12.53.27.SET,R1,=99.

12.53.40.SET,R2,=901.

12.54.05.DISPLAY,R1.

12.54.05. 99 143B.

12.54.16.DISPLAY,R1+R2.

12.54.16. 1000 1750B.

12.55.09.DISPLAY,STR($N0W IS THE TIMES).

12.55.09.NOW IS THE TIME.

12.56.10.DISPLAY,STRB(R1+R2) .

12.56.10.1750.

12.56.26.DISPLAY,STRD(R1+R2). "^

12.56.26.1000. /

12.58.26.DISPLAY,STRB(R1+R2)/STR($B IS EQUAL TO S)//STRD(R1+R2).

12.58.26.1750B IS EQUAL TO 1000.

13.01.32.DISPLAY,STR($FIRSTRATE$,4,6)//STR($RINGER$,2,4).

13.0L32.STRING.

13.01.53.DISPLAY,3/2.

13.01.53. 1 1B

13.02.07.DISPLAY 2**47.

13!o2!07! GT 9999999999 4000000000000000B.

13.02.24.DISPLAY,-2**47.

13.02.24. LT -9999999999 -4000000000000000B.

13.02.38.DISPLAY,2**48.

13.02.38. 0 0B.

13.03.28.DISPLAY,99999999999.

13.03.28. CCL156- STRING TOO LONG - 99999999999

y * ^ \

6-16.4 60459680 H

The ﬁrst DISPLAY command displays the value of the symbolic name TIME. The current time

given is in the form hhmm. The next six lines demonstrate the use of the Rl and R2 symbolic

names. The next 10 lines illustrate the use of the STR, STRB, and STRD functions for ■

generating display character strings. The other DISPLAY commands specify numeric I

expressions. The integer constant in the ﬁnal DISPLAY command has more than 10 digits,

resulting in an error message.

ELSE COMMAND

The ELSE command performs one of the following functions.

• It terminates skipping initiated by a false IF command whose label string matches

that of the ELSE command. If the label string does not match, the ELSE command is

skipped.

•It initiates skipping from the ELSE command to the ENDIF command whose label string

matches that of the ELSE command. This happens for a true IF command.

Neither a SKIP nor an ELSE command terminates skipping initiated by another SKIP or ELSE

command.

Format:

ELSE,label.

Parameter Description

label Speciﬁes a 1- to 10-character alphanumeric string. The string must

begin with an alphabetic character.

Example:

The following commands use the FILE function to determine if a ﬁle named TEST1 is local to

the job. If the ﬁle is local, it is copied to the OUTPUT ﬁle; if it is not, it is assumed

to be an indirect access permanent ﬁle, and a local copy is obtained and copied to OUTPUT.

60459680 H 6-17

If the ﬁle 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 ﬁle 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 dayﬁle segment results when the preceding commands are processed and TESTI is

not initially a local ﬁle.

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 dayﬁle segment results when the preceding commands are processed and TESTI is

initially a local ﬁle.

15.40.19.IF,FILE(TEST1,LO),LABEL1.

15.40.19.C0PYSBF,TEST1,0UTPUT. tttmr

15.40.21. END OF INFORMATION ENCOUNTERED. y

15.40.21.ELSE,LABEL1.

15.40.21 .ENDIF,LABELL

ENDIF COMMAND

The ENDIF command terminates skipping initiated by a SKIP, IF, or ELSE command. In all

cases, the label string on the ENDIF command must match the label string on the command that

initiates the skipping. If the system encounters an ENDIF command with a nonmatching label

string, it ignores that command.

Format:

ENDIF,label.

Parameter Description

label Speciﬁes a 1- to 10-character alphanumeric string. The string must

begin with an alphabetic character.

^\

y^&Sk

6-18 60459680 D

0ftoi\

Example:

When the SKIP command in the following sequence of commands is processed, control skips to

ENDIF, and none of the commands between SKIP and ENDIF are processed.

SKIP,LABEL1.

commands

ENDIF,LABEL1.

ENDW COMMAND

The ENDW command identiﬁes 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 speciﬁed in the WHILE command that begins the

loop.

The ENDW command must have a label string that matches the label string speciﬁed in the

WHILE command that begins the loop.

Format:

ENDW,label.

Parameter Description

label Speciﬁes a 1- to 10-character alphanumeric string. The string must

begin with an alphabetic character.

Refer to WHILE Command in this section for an example of ENDW command use.

EXIT COMMAND

The EXIT command indicates the position in the command record where processing will resume

if an error is encountered prior to the EXIT command. If no error is encountered, the EXIT

command indicates where to terminate normal command processing.

When used in procedures, we recommend that the EXIT command be preceded by a SKIP or REVERT

command to prevent execution of the EXIT command in the case where no error occurs. An EXIT

command executed in this way terminates the executing procedure as well as all calling

procedures if nesting has occurred, but does not restore control registers to their previous

values.

Format:

EXIT.

For additional information, refer to the description of the NOEXIT and ONEXIT commands later

in this section and to the description of exit processing in section 5.

j$^&\

60459680 E 6-19

IF (OR IFE) COMMAND

The IF command conditionally skips one or more commands.

Formats:

IF,condition.command.

IF,condition,label.

Parameter Description

condition Speciﬁes an expression that is either true or false. The separator

following condition in the ﬁrst format must be a terminator.

command Speciﬁes a valid command.

label Speciﬁes a 1- to 10-character alphanumeric string. The string must

begin with an alphabetic character. An identical string must appear in

a subsequent ELSE or ENDIF command.

The ﬁrst format conditionally skips only the command speciﬁed within the IF command. If

condition is true, the system executes the speciﬁed command. If condition is false, the

system skips the command.

NOTE

When using the ﬁrst 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 ﬁrst

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 ﬂag (EF) is 0. In this case, the DISPLAY

command is not executed. If an error occurs, the error ﬂag is not 0, the condition is

true, and control passes to the DISPLAY command; the system then displays the error code in

the error ﬂag 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 ﬁeld length of the job).' The commands that are used

appear ﬁrst and the dayﬁle segment follows.

FTN5,I=FTNPR0G.

SET,EF=0. INITIALIZE ERROR FLAG

NOEXIT.

LGO.

ONEXIT.

IF,EF.NE.O.DISPLAY,EF.

12.57.02.FTN5,I=FTNPROG.

12.57.02. 61000 CM STORAGE USED.

12.57.02. 0.009 CP SECONDS COMPILATION TIME.

12.57.02.SET,EF=0. INITIALIZE ERROR FLAG

12.57.02.NOEXIT.

12.57.02.LGO.

12.57.03. NON-FATAL LOADER ERRORS -

12.57.03. UNSATISFIED EXTERNAL REF — BETA

12.57.03. MODE ERROR.

12.57.03. JOB REPRIEVED.

12.57.03. UNSATISFIED EXT IN FLAG NEAR LINE 2

12.57.03. 7500 MAXIMUM EXECUTION FL.

12.57.03. 0.000 CP SECONDS EXECUTION TIME.

12.57.03. RPV - PREVIOUS ERROR CONDITIONS RESET.

12.57.03. CPU ERROR EXIT AT 400121.

12.57.03. CM OUT OF RANGE.

T 12.57.03.ONEXIT.

12.57.04.IF,EF.NE.0.DISPLAY,EF.

12.57.04.DISPLAY,EF.

12.57.04. 3 3B

Example 2:

The following procedure ﬁle is an indirect access ﬁle called COLORPR. It uses the IF

command to determine if the color the BEGIN command substituted for COLOR is red or blue.

Different processing is done for the colors red and blue. Any other color is ignored. The

# character in the comment line inhibits substitution for the word (COLOR) it precedes

(refer to Parameters and the Procedure Body in section 4).

.PR0C,A*I,C0L0R.

IF,$C0L0R$.EQ.$RED$,L1.

COMMENT. PROCESSING DONE FOR #COLOR OF COLOR

REVERT.

ENDIF, LL

IF,$C0L0R$.EQ.$BLUE$,L2.

COMMENT. PROCESSING DONE FOR 0COLOR OF COLOR

REVERT.

ENDIF,L2.

COMMENT. NO PROCESSING FOR #C0L0R OF COLOR

z^PN

60459680 F 6-21

/ * ^ v

The following commands call procedure A.

BEGIN,A,C OLORPR,BLUE.

BEGIN,A,COLORPR,RED.

BEGIN,A,COLORPR,PINK.

The following dayﬁle segment results when the preceding commands are processed. It shows

the effect of the # character.

08.34.30.BEGIN,A,C0L0RPR,BLUE.

08.34.32.IF,$BLUE$.EQ.$RED$,L1.

08.34.32.ENDIF,L1.

08.34.32.IF,$BLUE$.EQ.$BLUE$,L2.

08.34.32.COMMENT. PROCESSING DONE FOR COLOR OF BLUE

08.34.32. REVERT. /eS^

08.34.33.BEGIN,A,C0L0RPR,RED. ^)

08.34.34.IF,$RED$.EQ.$RED$,L1.

08.34.34.COMMENT. PROCESSING DONE FOR COLOR OF RED

08.34.34.REVERT.

08.34.34.BEGIN,A,C0L0RPR,PINK.

08.34.35.IF,$PINK$.EQ.$RED$,L1.

08.34.35.ENDIF,L1.

08.34.35.IF,$PINK$.EQ.$BLUE$,L2.

08.34.35.ENDIF,L2.

08.34.36.COMMENT. NO PROCESSING FOR COLOR OF PINK

08.34.36.SREVERT.CCL

MODE COMMAND

The MODE command deﬁnes the error conditions that cause the system to exit from normal

processing. When the error that you speciﬁed occurs, the system sets the appropriate error

ﬂag and exits from normal processing to perform any error processing required. If an error

occurs for which you did not select the exit mode processing, the system ignores the error

and continues normal processing.

Format:

MODE,m,n.

Parameter Description

m CPU program error exit mode (0<m<17g). Modes lOg through 173 are

only valid for model 176. Selects the error conditiori(s) for which

normal error processing does and does not occur. If no mode is

selected, the default is 7.

n Included for compatibility with earlier versions of NOS. The system now

ignores the value speciﬁed on the command.

6-22 60459680 D

0S^\

The following values can be supplied for m.

m Normal Error Processing Occurs

0 None.t

1 Address out of range.

2 Operand overﬂow.t

Address out of range or

operand overﬂow.

Indeﬁnite operand.t

Address out of range or

indeﬁnite operand.

Indeﬁnite operand or operand

o v e r ﬂ o w.

Indeﬁnite operand, address out

of range, or operand overﬂow

(default value).

10,11ttt Operand underﬂow or address out

of range.

12,13ttt Operand underﬂow, address out

of range, or operand overﬂow.

14,15 Operand underﬂow, address out

of range, or indeﬁnite operand.

16,17 Operand underﬂow, address out of

range, operand overﬂow, or

indeﬁnite operand.

Error Ignored and Job Continues

Address out of range, operand overﬂow,

indeﬁnite operand, or operand

u n d e r ﬂ o w. t t

Indeﬁnite operand, operand overﬂow,

or underﬂow.

Address out of range, indeﬁnite

operand, or operand underﬂow.

Indeﬁnite operand or operand

under f low .tt

Address out of range oc operand

overﬂow or underﬂow.tt

Operand overﬂow or underﬂow.tt

Address out of range or operand

underﬂow.

Operand underﬂow.

Operand overﬂow or indeﬁnite

operand.

Indeﬁnite operand.

Operand overﬂow.

None.

tOn the model 176, address out of range (m=l) is always selected.

ttOperand underﬂow is applicable only to the model 176.

tttThese modes are valid only on the model 176. Since address out of range (m=l) is always

selected, the two modes are equivalent.

60459680 D 6- 23 •

Descriptions of the error conditions are as follows:

Error Condition Description

Address out of range error. An error caused by an attempt to reference central memory or

extended memory outside of established limits.

Operand overﬂow error. An error resulting when a ﬂoating-point arithmetic unit

receives an operand with an exponent value of +1777g (3777 or

4000 in packed form). This is the largest exponent value that

can be represented in ﬂoating-point format.

Indeﬁnite operand error. An error resulting when a ﬂoating-point arithmetic unit

encounters a calculation it cannot resolve. Examples of

indeﬁnite operand errors are an attempt to divide 0 by 0 and

an attempt to multiply an overﬂow operand by an underﬂow

operand.

Operand underﬂow error. An error resulting when a ﬂoating-point arithmetic unit

receives an operand with an exponent of -1777g (0000 or 7777

in packed form). This is the smallest exponent value that can

be represented in ﬂoating-point format.

For further information about the processing of error mode errors, refer to Error Control in

section 3. For further information on the error conditions described above, refer to the

appropriate CYBER 180, CYBER 170, CYBER 70, or 6000 Computer System reference manual.

NOEXIT COMMAND

The NOEXIT command suppresses EXIT command processing. If an error occurs, control is not

transferred to the command following the next EXIT command. Instead, processing continues

with the next command (unless the error causes the job to unconditionally terminate). Refer

to the description of exit processing in section 5 for more information.

Format:

NOEXIT.

ONEXIT COMMAND

The ONEXIT command reverses the effect of a NOEXIT command. If an error occurs in

processing the commands following ONEXIT, control transfers to the command following the

next EXIT command. Refer to the description of exit processing in section 5 for further

information.

Format:

ONEXIT.

REVERT COMMAND

Refer to Ending a Procedure in section 4.

6-24 60459680 D

/^P^N

SET COMMAND

The SET command assigns a value to a control register, an error ﬂag, or the ﬂag that

determines whether skipped commands are entered in the dayﬁle. Using the SS symbolic name,

it also can change the current interactive subsystem.

Format:

SET,symbolj=expressionj,symbol2=expression2,...,symboln=expressionn

symbol^ One of the following symbolic names. I

Name Description

Rl, R2, or R3 Local control registers. When a procedure is

called, the current values of Rl, R2, and R3 are

passed to the procedure. The values of these

registers may change within the procedure.

However, when processing reverts, these registers

are restored to the values they had when the

procedure was called. The initial value for each I

i s 0 . ■

R1G Global control register. When a procedure is

called or reverts, RIG keeps its current value.

The initial value for RIG is 0. |

EF Local error ﬂag. When a procedure is called, the

current value of the error ﬂag is passed to the

procedure. The value of the error ﬂag may change

within the procedure. However, when the procedure |

reverts, the error ﬂag is restored to the value it

had when the procedure was called. The initial

value for EF is 0.

EFG Global error ﬂag. When a procedure is called or

reverts, EFG keeps i ts current value if it is not

zero. If EFG has a value of zero when the

procedure reverts, the system sets EFG equal to

EF. The initial value of EFG is 0.

DSC Dayﬁle-skipped-command ﬂag. Initially, it is set

to 0, so that commands that are skipped (not

processed) are not entered in the dayﬁle. If DSC

is 1, the system enters skipped commands in the

dayﬁ le with t wo leadi ng peri od s.

PL or PS Page length (or page size). Default is 60 lines.

PW Page width. Default is 136 characters.

PD Page density. Default is six lines per inch.

SS Interactive subsystem indicator. The default of SS

is NULL.

expression Any valid expression. The value derived through evaluation of the

expression is assigned to the symbolic name. Acceptable values for

each symbolic name follow.

60459680 H 6-25

,rf^V

symbol Suggested Value

Rl, R2, R3, or RIG Any integer between -131071 and 131071. If

the value is outside this range, it is

truncated. The values in these registers are

18-bit quantities, 17 digits and a sign. When

truncation occurs, the upper bits are truncated

but the sign bit is always retained. The

system does not issue a message as a result

of the truncation.

EF or EFG Any integer between 0 and 63. The values in

these registers are 6-bit unsigned quantities.

When truncation occurs, the upper bits are

discarded. If the value is greater than 63,

it is truncated. To assign the value deﬁned

by the system for an error condition, set the

error ﬂag to one of the error condition

symbolic names (refer to Symbolic Names at the

beginning of this section). The system sets

the EF ﬂag to the appropriate error code when

an error occurs.

DSC 1 or 0. If the value of the expression is

nonzero, DSC is set to 1. While DSC is 1,

skipped commands are entered in the dayﬁle

preceded by two periods. Some error

processing routines set DSC to 1 so that

skipped commands are written in the dayﬁle.

PL or PS Any integer between 16 and 255.

PW Any integer between 40 and 255.

P D 6 o r 8 . Y o u c a n s e l e c t a p r i n t d e n s i t y o f

either six or eight lines per inch.

SS Any subsystem name (ACCESS, BASIC, BATCH,

EXECUTE, FORTRAN, FTNTS, or NULL).

6-26 60459680 D

/SPN.

Examples:

The ﬁrst three examples use procedures from the following procedure ﬁle. It is an

indirect access permanent ﬁle with the name SETFILE.

,PR0C,P1*I.

DIS PLAY, RL

DISPLAY,R1G.

SET,R1=9.

SET,R1G=888.

-EOR-

.PR0C,P2*I.

GET,ABC.

DISPLAY,EF.

DISPLAY,EFG.

-EOR-

-PR0C,P3*I.

GET,BASIC1.

BASIC.

DISPLAY,EF.

DISPLAY, EFG.

-EOR-

-EOF-

Example 1 - Control Register Use:

The following commands (below on the left side) set and display registers Rl and RIG. A

procedure, PI, is called which displays these registers, resets them, and then reverts to

the command record where they are again displayed.

On the right is the dayﬁle segment resulting from processing of the commands.

SET,R1=1.

SET,R1G=10.

DISPLAY, RL

DISPLAY,R1G.

BEGIN,P1,SETFILE.

DISPLAY,RL

DISPLAY,R1G.

16.34.42.SET,R1=1.

16.34.42.SET,R1G=10.

16.34.43.DISPLAY,R1.

16.34.43. 1 1B

16.34.43.DISPLAY,R1G.

16.34.43. 10 12B

16.34.43.BEGIN,P1,SETFILE.

16.34.44.DISPLAY,R1.

16.34.44. 1 1B

16.34.44.DISPLAY,R1G.

16.34.44. 10 12B

16.34.44.SET,R1=9.

16.34.44,R1G=888.

16.34.44.SREVERT.CCL

16.34.44. DISPLA Y,RL

16.34.44. 1 1B

16.34.45.DISPLAY,R1G.

16.34.45. 888 15708

The Rl and RIG registers retain their setting when the procedure is called. However, after

new values are set in the procedure and control reverts to the command record, Rl returns to

its previous value and RIG retains the value set in the procedure.

60459680 D 6-27

0*m$$$\

Example 2 - Error Flag Use (EFG Nonzero):

The following commands (below on left side) set values in the error ﬂags EF and EFG and

then call a procedure which attempts to access an indirect access permanent ﬁle. Control

reverts to the command record where EF and EFG are displayed to see if any error code

generated is returned via these ﬂags. On the right side is the dayﬁle segment resulting

from the processing of the commands.

NOEXIT. 16.43.35.NOEXIT.

SET,EF=10. 16.43.35. SET,EF=10.

SET,EFG=20. 16.43.35. SET, EFG=20.

DISPLAY,EF. 16.43.35.DISPLAY,EF.

DISPLAY,EFG. 16.43.35. 10 12B

BEGIN,P2,SETFILE. 16.43.35. DISPLAY, EFG.

DISPLAY,EF. 16.43.35 20 24B

DISPLAY.EFG. 16.43.35.BEGIN,P2,SETFILE.

16.43.36.GET,ABC.

16.43.36. ABC NOT FOUND.

16.43.36.DISPLAY,EF.

16.43.36. 6 6B

16.43.36. DIS PLAY, EFG.

16.43.36. 20 24B

16.43.36.$REVERT.CCL

16.43.37.DISPLAY,EF.

16.43.37. 10 12B

16.43.37. DISPLAY, EFG.

16.43.37. 20 24B ^^\

The procedure attempts to get a permanent ﬁle which does not exist. This changes EF to

error code 6. It does not affect EFG. Control reverts to the command record and displays

EF and EFG. EF returns to its initial setting; EFG remains unchanged throughout.

/*^%».

6-28 60459680 D

Example 3 - Error Flag Use (EFG Zero):

To return the error code generated in a procedure to the command record, EFG must be 0

before there is an exit from the procedure. This is demonstrated by the following commands

(below left side).

The dayﬁle segment (on the right) resulting from processing of the commands shows how the

error code is returned.

NOEXIT.

SET,EF=10.

SET,EFG=0.

BEGIN,P3,SETFILE.

DISPLAY,EF.

DISPLAY,EFG.

09.42.52.NOEXIT.

09.42.52.SET,EF=10.

09.42.52.SET,EFG=0.

09.42.52.BEGIN,P3,SETFILE.

09.42.53.GET,BASIC1.

09.42.55.BASIC.

09.42.56. INPUT FILE EMPTY OR MISP0SITI0NED

09.42.56.DISPLAY,EF.

09.42.56. 7 7B

09.42.57.DISPLAY,EFG.

09.42.57. 0 0B

09.42.57.SREVERT.CCL

09.42.58.DISPLAY,EF.

09.42.58. 10 12B

09.42.58.DISPLAY,EFG.

09.42.58. 7 7B

The procedure attempts to compile a BASIC program that is not an INPUT record. This

generates error code 7 in EF but does not affect EFG while control is still within the

procedure. When control reverts to the command record, EF returns to its original setting

and error code 7 is set in EFG.

60459680 H 6-29

/^tSv

Example 4 - DSC Flag Use:

The following commands (below on left side) demonstrate the effect of DSC=0 and DSC=1. On

the right side is the dayﬁle segment resulting from processing of the preceding commands.

SET,DSC=0. 16.49.36

SKIP,LABL1. 16.49.36

COMMENT. SINCE THE DAYFILE SKIP 16.49.36

COMMENT. CONTROL IS SET TO ZERO. 16.49.37,

COMMENT. THESE STATEMENTS WILL NOT 16.49.37

CO MM EN T. AP PE AR IN T HE D AYFIL E. 16 .4 9. 37

ENDIF,LABLL 16.49.37

SET,DSC=1. 16.49.37

SKIP,LABL2. 16.49.37

CO MM ENT. SI NC E T HE DAYF IL E SK IP 16.4 9. 37

COMMENT. CONTROL IS NOW SET TO ONE, 16.49.37

COMMENT. THESE STATEMENTS WILL 16.49.37

COMMENT. APPEAR IN THE DAYFILE AND

COMMENT. EACH WILL BE FLAGGED

COMMENT. WITH TWO INITIAL PERIODS.

ENDIF,LABL2.

,SET,DSC=0.

,SKIP,LABLL

,ENDIF,LABL1.

,SET,DSC=1.

.SKIP,LABL2.

...COMMENT. SINCE THE DAYFILE SKIP

...COMMENT. CONTROL IS NOW SET TO ONE,

...COMMENT. THESE STATEMENTS WILL

...COMMENT. APPEAR IN THE DAYFILE

...COMMENT. AND EACH WILL BE FLAGGED

...COMMENT. WITH TWO INITIAL PERIODS.

,ENDIF,LABL2.

i^^\

SKIP COMMAND

The SKIP command initiates unconditional skipping of succeeding commands. Skipping is

terminated by an ENDIF command that has a label string matching the label string speciﬁed

on the SKIP command. Only an ENDIF command, and not an ELSE command, terminates skipping

initiated by a SKIP command.

Format:

SKIP,label.

Parameter

label

Description

Speciﬁes a 1- to 10-character alphanumeric string. The string must

begin with an alphabetic character.

^"^K

An example of the use of the SKIP command is given after the description of the ENDIF

command.

6-30 60459680 D

<*^\

WHILE COMMAND

The iterative commands WHILE and ENDW bracket a group of commands into a loop that can be

repeatedly processed. The beginning of the loop is identiﬁed by a WHILE command and the

end by an ENDW command. The ENDW command must have a label string that matches the label

string speciﬁed on the WHILE command. The loop is repeated as long as the expression in

the WHILE command is true. If the expression is initially false, control immediately skips

to the ENDW command.

Label strings of all WHILE commands within the command record of a job should be unique.

Duplication of a label string within a command record or within a procedure can produce

unpredictable results. The same label string can be used in a called procedure and in the

calling command record or procedure.

Format:

WHILE,expression,label•

Parameter Description

expression Speciﬁes any valid symbolic name or expression described earlier in

this section. The separator following expression must be a comma.

l a b e l S p e c i ﬁ e s a 1 - t o 1 0 - c h a r a c t e r a l p h a n u m e r i c s t r i n g . T h e s t r i n g m u s t

begin with an alphabetic character.

Example:

The following commands initiate a loop which is repeated ﬁve times.

SET,R1=0.

SET,R2=5.

WHILE,R1.LT.R2,FINISH.

SET,R1=R1+1.

DISPLAY,R1.

ENDW,FINISH.

You can vary the number of repetitions by setting different values in R2.

60459680 D b_3l

0^%

jS^\

JOB CONTROL COMMANDS

The job control commands alter information that controls jobs while in the system and

retrieves information concerning the status of jobs. The commands included in this category

are:

BLOCK

CFO

CHARGE

CHVAL

CLASS

COMMENT

CTIME

DAYFILE

DROP

ENQUIRE

ENTER

ERRMSG

GO

HTIME

Job

LDI

LENGTH

LIMITS

LISTLID

MACHINE

MFL

NORERUN

NOTE

OFFSW

ONSW

PASSWOR

PAUSE

PROTECT

QGET

QUEUE7

RERUN

RESOURC

RFL

ROLLOUT

RTIME

SETASL

SETCORE

SETJAL

SETJOB

SETJSL

SETPR

SETTL

SHELL

STIME

SUBMIT

SWITCH

UPROC

USECPU

USER

You must have speciﬁc authorization to use LDI, PASSWOR, PROTECT, or SUBMIT. You can use

the remaining commands regardless of your authorization. A listing of validation

information can be obtained using the LIMITS command. Although you are allowed to change

several control values for your job (with the Job, RFL, SETPR, and SETTL commands), you can

never specify more than that for which you are validated.

The system uses the USER command and CHARGE command for checking your authorization and

system accounting information. The RESOURC command is used by the system to prevent

deadlocks from occurring when several tapes or packs are used concurrently.

r60459680 H 7-1

BLOCK COMMAND

The BLOCK command deﬁnes one or more lines of 10 by 10 (10 lines by 10 columns) block

letters to be added to a ﬁle. The large, 10-line characters provide easier identiﬁcation

of output listings.

Format:

BLOCK,lfn,rewind,cc./line1/line2/.../linen

Parameter

lfn

rewind

Description

Speciﬁes the name of the local ﬁle to receive the block character

lines. Default is OUTPUT.

Speciﬁes whether or not lfn is rewound before the block character lines

are printed. Values that can be speciﬁed for rewind are R (rewind) and

NR (no rewind). The default is NR.

NOTE

If ﬁle lfn contains data and you specify that lfn

is to be rewound, the block characters written to

the ﬁle will overwrite data at the beginning of the

ﬁle.

line.

Speciﬁes the carriage control character to be inserted before the ﬁrst

line of block characters. The default value is 1 (top of form). The

carriage control characters are described in appendix H (a space, PM,

and special characters are not accepted).

Speciﬁes the delimiting character that separates the block character

lines. The delimiter can be any character and must be the ﬁrst

character following the command terminator. Consecutive delimiters

generate blank lines.

Speciﬁes either a string of up to ten characters which constitute one

line of block characters, or one of the following special values:

Special Value

DATE

TIME

USER

UJN

JSN

Description

Current date.

Current time.

Current user name,

User job name.

Job sequence name,

7-2 60459680 H

j0M&h\

Example:

Following is a BLOCK command and its resulting output:

/block

BLOCK,

/list,

1

,blockf,*myj ob*date

BLOCKF.*MYJOB*DATE

f=blockf

MM MM Y Y Y Y JJJJJJJJ OOOOOOOO BBBBBBBBB

MMMM MMMM Y Y Y Y JJJJJJJJ OOOOOOOOOO BBBBBBBBBB

MM MMMM MM YY YY JJ 00 000 B B B B

MM MM MM YYYY JJ 00 0 00 B B B B

MM MM MM YY JJ 00 0 00 BBBBBBBBB

MM MM YY JJ 00 0 0 0 BBBBBBBBB

MM MM YY J J J J 00 0 0 0 B B B B

MM MM YY J J J J 000 00 B B B B

MM MM YY JJJJJJJ oooooooooo BBBBBBBBBB

MM MM YY JJJJJ oooooooo BBBBBBBBB

88888888 5555555555 11 oooo 22222222 88888888

8888888888 5555555555 II 1111 oooooo II 2222222222 8888888888

8 8 8 8 55 II 11 11 00 00 II 2 2 2 8 8 8 8

8 8 8 8 55 II 11 00 00 II 22 8 8 8 8

88888888 555555555 II 11 00 00 II 222 88888888

88888888 5555555555 II 11 00 00 II 222 88888888

8 8 8 8 55 II 11 00 00 II 222 8 8 8 8

8888888888 555555555 II 1111111111 oooooo II 2222222222 8888888888

88888888 5555555 1111111111 oooo 2222222222 88888888

0

Column one of the listing contains printer carriage control characters 1 and 0.

character produces a form feed; the 0 characters produce double spacing.

The 1

CFO COMMAND

The CFO command sends data to one of your executing jobs. The command places data in

locations RA + 70B through RA + 74B of the program's ﬁeld length. The CPU program

receiving the data must set the CFO ﬂag (bit 14 of RA + 0) to indicate it will accept CFO

data. The CFO command clears the CFO and the PAUSE ﬂags in RA after it places data in the

job's ﬁeld length.

Format:

CFO,jsn.data

Parameter

jsn

data

Description

The job sequence name (JSN) of the job to receive the data.

The data for the job. The data must be 36 characters or less.

/0^S.

60459680 H 7-3

CHARGE COMMAND

The CHARGE command causes the system to record on the account dayﬁle all information

regarding resources used in the previous account block, and designates a new charge and

pro ject n um ber fo r su bs eq uent a ct ivity. Its pu rpose is to co ntrol the ac counting activi ty

of the system for a customer or the installation. An account block is that portion of a job

from one CHARGE command to the end of the job or to another CHARGE command.

Format:

CHARGE,chargenumber,proj ectnumber.

CHARGE,*.

or

CHARGE.

Parameter Description

chargenumber Speciﬁes the charge number assigned to you by your site.

projectnumber Speciﬁes the project number assigned to you by your site.

If you use the third format of this command, the system reads the charge number and the

project number from a record of ﬁle INPUT. This record must be a single line with the

following format:

chargenumber,proj ectnumber

If your job is an interactive job, the system provides some security by overprinting an area

on your terminal and then prompting you to enter your charge and project numbers in this

area.

If you use the second format of this command, the system uses your default charge and

project numbers (refer to the LIMITS command in this section).

The CHARGE command is used in the control of user accounting. The project master user can

impose limits on the SRUs your jobs may accumulate under that project number; can restrict

your access to the system to a certain time of the day; and, in general, can monitor your

use of the system.

If a charge number has a project prologue associated with it, the project prologue is

executed each time the charge number is entered on a CHARGE command. A CHARGE command

entered as the ﬁrst command in the job also causes the system and user prologues, if any,

to be executed. The system prologue is executed ﬁrst, followed by the project and user

prologues. For a CHARGE command other than the ﬁrst CHARGE command in the job, only the

project prologue is executed.

If your site requires that you use a CHARGE command, the system internally processes a

CHARGE,* command when necessary. For interactive jobs, the system executes the CHARGE,*

command each time you login. For batch jobs, the system internally executes a CHARGE,*

command if you do not include a CHARGE command immediately following the USER command. If

you do include a CHARGE command following the USER command, the system uses the charge

number you supply.

| 7-4 60459680 H

■**SS|\

The CHARGE command sets the SRU limits for the account block and the job step to the user

name v alida ti on li mi ts or the accoun t val id ation l imits , whi ch ev er is sma ller. Re fe r to the

SETJSL and SETASL commands later in this section.

In addition to the site requirement for a charge number, you may also be required to enter a

charge number under certain conditions. Speciﬁcally, you may be required to enter an

additional number as a result of an SRU limits exceeded condition or as a result of a

project prologue.

If you are assigned more than one charge or project number, you can include additional

CHARGE commands in your job to record resources used under each charge number-project number

combination. Whenever a new CHARGE command is issued, the SRU information for the previous

charge number and project number is written to an account dayﬁle and then cleared.

However, the other accumulators (central processor time, mass storage activity, and so on)

are not cleared but continue to increment.

For a complete list of accounting messages issued to the job's dayﬁle, refer to Job

Completion in section 3.

CHVAL COMMAND

The CHVAL command redeﬁnes your validation limits or privileges. Currently, you are only

allowed to redeﬁne your default service class assignments.

Format:

CHVAL,UC=otsc.

Parameter Description

UC=otsc Speciﬁes the default service class assignment according to origin

type. The value otsc is the desired service class mnemonic appended to

the mnemonic for the origin type. Do not place a separator between the

mnemonics. The value ot must be one of the following:

ot Description

IA Interactive origin

BC Local batch

RB Remote batch

The value sc must be one of the following:

sc Description

SY System

BC Local batch

RB Remote batch

60459680 H 7-5

Parameter Description

sc Description

TS Interactive

DI Detached interactive

N S N e t w o r k s u p e r v i s o r

MA Maintenance

CT Communication task

In Installation class n (0 <_ n <^ 3)

You must be authorized to use the service class you select. The LIMITS

command shows the service classes you are allowed to use and your

default service class assignments.

Example:

In the following example, the default service class assignment for interactive jobs is

changed from interactive (TS) to detached interactive (DI).

/limits

THE FOLLOWING ARE ALLOWED SERVICE CLASSES -

BATCH (BC)

REMOTE BATCH (RB)

INTERACTIVE (TS)

DETACHED INTERACTIVE (DI)

THE USER DEFAULT SERVICE CLASS

FOR BATCH ORIGIN IS BC

FOR REMOTE BATCH ORIGIN IS RB

FOR INTERACTIVE ORIGIN IS TS

INQUIRY COMPLETE.

/chval,uc=iadi

UPDATE COMPLETE,

/limits

THE FOLLOWING ARE ALLOWED SERVICE CLASSES -

BATCH (BC)

REMOTE BATCH (RB)

INTERACTIVE (TS)

DETACHED INTERACTIVE (DI)

THE USER DEFAULT SERVICE CLASS

FOR BATCH ORIGIN IS BC

FOR REMOTE BATCH ORIGIN IS RB

FOR INTERACTIVE ORIGIN IS DI

INQUIRY COMPLETE.

7-6 60459680 D

CLASS COMMAND

The CLASS command changes the service class of your current interactive job or of a batch

job you have submitted for execution. For interactive jobs, the CLASS command can only

change the service class of the interactive job from which it was entered; it cannot change

an interactive job connected to another terminal. For batch jobs, you can change the

service class of any executing job or any job in the input queue. This includes the job

from which the CLASS command was entered.

The CLASS command also shows the relative priority of the available service classes for a

speciﬁed origin type. Implicitly, the relative priority display also shows which service

classes are allowed within the chosen origin type.

Format:

CLASS,SC»sc,0P°A.

or

CLASS,sc,,,A.

or

CLASS, OT=»ot,L=lfn.

/iP^v

CLASS,,ot,lfn.

or

CLASS,SC=sc,JSN=jsn.

or

CLASS,sc,,,,jsn.

The parameters are order-independent if you specify them in the keyword=value form.

Otherwise, they are order-dependent.

Parameter

SC=sc

Description

Speciﬁes the desired service class for the job. The value sc must be

one of the following:

sc Description

SY System

BC Local batch

RB Remote batch

TS Interactive

y ^ ^ V

60459680 D 7-7

Parameter Description

sc Description

DI Detached interactive

NS Network supervisor

MA Maintenance

CT Communication task

In Installation class n (0 £ n j< 3)

There is no default for this parameter. The service class you specify

must be within your validation limits (refer to the LIMITS command).

0 P = A S e l e c t s t h e a b o r t o p t i o n . T h e c o m m a n d a b o r t s i f t o o m a n y j o b s i n t h e

system already have the service class you speciﬁed. Otherwise, if this

situation occurs, the system rolls out your job and waits until it can

make the desired assignment.

OT=ot Speciﬁes the origin type for which the system shows the relative

priority of the available service classes. The value ot can be any of

the following:

ot Description

SY System origin

IA Interactive origin

B C L o c a l b a t c h o r i g i n

RB Remote batch origin

The default is the origin type of the current job. If you specify OT=ot

along with SC=sc, OT=ot is ignored.

L=lfn Speciﬁes the ﬁle that receives the display generated by this command.

OUTPUT is the default. If you specify L=lfn along with SC=sc, L°lfn is

ignored.

JSN31 jsn Speciﬁes the JSN of an executing job or a job in the input queue.

The ﬁrst and second formats change the service class of your current job. If you use the

ﬁrst or second format and do not specify a valid service class (for instance, you omit that

value), the system displays the relative priority of the service classes available for your

job. F urthe r, if you r job is i nt eractiv e, you receiv e a pro mpt f or a servi ce cla ss.

The third and fourth formats generate a display of the relative priority of the available

service classes for a designated origin type.

The ﬁfth and sixth formats change the service class of an executing batch job or of a job

in the input queue. They cannot be used to change the service class of an interactive job.

z^^k

7-8 60459680 D .^

Example:

r

/ip*\

The following terminal session shows how you can ascertain the relative priority of the

service classes for your current job.

/ c l a s s

AVAILABLE SERVICE CLASSES

RELATIVE PRIORITY

CLASS INPUT FILES EXECUTING JOBS OUTPUT FILES

DI * ****** ***********

10 * ******* ***********

TS *********** ************ *********** CURRENT

ENTER CLASS: di

CLASS COMPLETE.

/

COMMENT COMMAND

The COMMENT command allows you to place a comment in the system dayﬁle and the dayﬁle of

any of your jobs.

Format:

0^*\

V COMMENT,jsn.comment

or

COMMENT.comment

or

*comment

Parameter Description

jsn Speciﬁes the job sequence name (JSN) of the job in whose dayﬁle you

want the comment written. The default is the current job.

comment Speciﬁes the message you want written in the designated dayﬁles.

If you use the third format of the command, the asterisk must be the ﬁrst nonblank

character of the command.

60459680 H 7-9

CTIME COMMAND

The CTIME command requests that the accumulated CPU time for the job be issued to the job's

dayﬁle (in seconds).

Format:

CTIME.

DAYFILE COMMAND

The DAYFILE command causes the system to write the job's dayﬁle to the ﬁle speciﬁed.

F o r p r i n t e d D AY F I L E o u t p u t , y o u c a n s p e c i f y o u t p u t p a g e s i z e a n d p r i n t d e n s i t y u s i n g t h e P L ^

and PD parameters. The DAYFILE command also honors the page length and print density set

for your job using the SET command and the PL and PD symbolic names.

Format:

DAYFILE,L=lfn,FR=string,OP=op,PD=pd,PL=pl,I=inﬁle.

DAYFILE,lfn,string,op,pd,pi,inﬁle.

Parameter Description

L=lfn Speciﬁes the ﬁle on which the dayﬁle is to be written. If L=lfn is

omitted, OUTPUT is assumed. Pagination will occur if listing ﬁle name

is OUTPUT or if the PD or PL parameters are speciﬁed.

FR=string Speciﬁes a character string for which a search is to be made in the

dayﬁle. The op parameter speciﬁes the ﬁeld to be searched.

The string speciﬁed must begin with the ﬁrst character in the ﬁeld to

be searched. The time ﬁeld begins with a blank. -"^

If the string contains characters other than letters and numbers (such

as blanks), it must be enclosed by $ delimiters. A $ within the string

must be entered twice ($$) so it is not interpreted as a delimiter.

Interactive commands entered in the dayﬁle are preceded by a $ unless

you were under the batch subsystem when you issued the command. To

search for a interactive command, the $ preceding the command is

replaced with two $'s, and the command is enclosed by $ delimiters (for

example, $ $ $OLD $).

If the str ing is foun d, t he por tion of t he d ayﬁ le f oll owi ng t he las t

oc cu rr en ce o f the s peciﬁe d s tring is ou tp ut. If t he st ri ng is no t

found, an informative message and the entire dayﬁle is output for jobs

where the output ﬁle is connected to a terminal; where the output ﬁle

is not connected to the terminal, the job receives only the informative

message.

7"10 60459680 D

,^*v

Parameter Description

OP=op Selects search option (single character):

PD=pd

PL=pl

op

T

M

I

Description

Search time ﬁeld for string speciﬁed by FR=string.

Search message ﬁeld for string speciﬁed by FR=string.

Inc re me nt al dump (d ay ﬁl e printed f ro m poin t of la st day ﬁl e

command).

Full dump.

If a literal string (string) is speciﬁed and op is omitted, OP=M is

assumed. If both string and op are omitted, OP=F is assumed unless the

output ﬁle is connected to a terminal. In this case, OP=I is assumed.

Speciﬁes the print density; default is PD=6.

£d

3

4

6

8

Print Density

Double space; 6 lines per inch

Double space; 8 lines per inch

Single space; 6 lines per inch

Single space; 8 lines per inch

Speciﬁes page size; if speciﬁed, the actual page size used is

determined by page density (pd) and the value speciﬁed for pi, as

follows:

pd

3

4

6

8

Page Size

pl / 2

pi / 2

Pl

If this parameter is omitted, page size is determined from system page

size and print density as follows:

pd

3

4

6

8

Default Page Size

30 lines

60 lines

I=inﬁle Speciﬁes a ﬁle which contains a dayﬁle to be used for input. If

I=inﬁle is omitted, the DAYFILE command uses the active dayﬁle for

input.

NOTE

A paginated dayﬁle listing cannot be used

as the input ﬁle (I=inﬁle). Refer to

L=lfn parameter.

jfSN

60459680 E 7 - 11 •

Examples:

DAYFILE,,$ 11.21.$,T.

The dayﬁle is dumped to OUTPUT starting at the last occurrence of 11.21. in the

time ﬁeld.

DAYFILE,I=DAY,FR=$$$GET,STATS.$

The dayﬁle is dumped to OUTPUT starting at the last occurrence of $GET,STATS, in

the message ﬁeld of the previously written dayﬁle named DAY.

The system may place diagnostic messages in the output produced by DAYFILE. They are not

part of the job's dayﬁle from which the DAYFILE output is produced. These messages begin

with NOTICE*** and are described in appendix B.

7-12 60459680 E

DROP COMMAND

/$P^N

The DROP command drops executing jobs or queued ﬁles. You can drop only jobs or queued

ﬁles belonging to you. You cannot drop the job from which you enter the DROP command.

A job or queued ﬁle belongs to you if it is your current job, was created by your current

job, or was created by another job belonging to you. Thus, any job you submit from your

current job belongs to you, even if the USER command in the submitted job has a user name

« * ! ! « » ! U S 6 r n a m e y ° U s P e c i f i e d w h e n Yo u l o g g e d i n ( o r d i f f e r e n t f r o m t h a t o f t h e

ﬁrst USER command if the current job is a batch job).

Format:

DROP,JSN=j sn,DC=q,UJN=ujn,OP=R.

or

DROP,jsn,q,ujn,R.

The parameters are order-independent if you specify the parameters in the keyword=value

form. Otherwise, they are order-dependent.

Parameter

JSN=jsn

UJN=ujn

DC=q

Description

Speciﬁes the job sequence name (JSN) of the job to be dropped.

Speciﬁes the user job name (UJN) of the job to be dropped. You can

specify the JSN, the UJN, or both.

Speciﬁes the disposition of the job to be dropped. You must specify q

if neither the JSN nor the UJN is speciﬁed. In this case, the system

drops all of your jobs with the speciﬁed disposition. If JSN or UJN is

speciﬁed, the default for q is ALL.

WT

PR

PU

PL

IN

EX

ALL

Description

Jobs queued with a wait disposition.

Jobs queued for printing.

Jobs queued for punching.

Jobs queued for plotting.

Jobs queued for input.

Executing jobs.

All jobs belonging to you.

OP=R

Examples:

DROP,ABDA.

DROP,, PR.

DROP.

Directs the system to drop the speciﬁed executing jobs without EXIT

processing but with single-reprieve processing for jobs containing such.

Drops executing job ABDA.

Drops all of your jobs queued for printing.

Incorrect. You must specify a JSN, UJN, or the DC=q parameter.

DROP,JSN=ABFF,OP=R. Drops executing job ABFF with a single reprieve and without EXIT

processing.

60459680 E 7-12.1/7-12.2

0^^y

r

ENQUIRE COMMAND

The ENQUIRE command gives you information about your jobs in the system. For output listing

ﬁles not connected to your terminal, the ENQUIRE command honors the page length and print

density set for your job using the SET command and the PL and PD symbolic names.

Format:

ENQUIRE,OP=p1p2...pn,FN=lfn1,0=lfn2.

or

ENQUIRE,p1p2...pn.

or

ENQUIRE,JSN=jsn,0=lfn2.

or

ENQUIRE,UJN=ujn,0=lfn2.

or

ENQUIRE.

Parameter Description

0P=pip2...p7 Any combination of the following options. You can request a maxi

mum of seven options on a command (for example, ENQUIRE,OP=BDFJLRS.).

Pi Description

A Gives listings of the B, D, R, U, J, L, and F options.

If you specify no parameters or only the 0=lfn2

parameter in a batch job, the OP=pjp2...pn

parameter defaults to OP=A.

B Returns identiﬁcation and priority information. On a

secured system, the system also lists the current job

access level, the upper limit for the job access level,

the lower limit for the job access level, and the

security access categories you can assign to permanent

ﬁles.

60459680 D 7-13

Parameter

Pi

Description

pie:

Description

/enquire,b

SYSTEM ACTIVITY.

USER NAME STARSKY

USER INDEX HASH AN2A

JOB SEQ. NAME ABLE

FAMILY NOSHOP

CHARGE NUMBER 2222

PROJECT NUMBER 666N666

PACK NAME •NONE*.

PACK TYPE DI1

PRIMARY FILE •NONE*.

SUBSYSTEM BATCH.

CPU PRIORITY 30

MAX FL (CM) 203700

MAX FL (EM)

LAST FL (CM)

LAST FL (EM)

Returns a listing of the resources you have demanded and

those which have been assigned (refer to RESOURC Command

in this section 6).

Example:

RESOURCE DEMAND INFORMATION.

RESOURCE DEMAND ASSIGNED

PE

HD

7-14 60459680 D

Parameter

Pi

F

Description

Gives the status of ﬁles assigned to your job.

Example:

/enquire,f

LOCAL FILE INFORMATION.

FILENAME LENGTH/PRUS TYPE STATUS FS

INPUT* IN.* EOR

PROLOG LO. EOR NAD

PROCFIL LO. EOI

INPUT TT.

OUTPUT TT.

PRCFILE LO. EOR NAD

ZZZZZLD LO. EOR NAD

PUBTOOL 835 PM.* EOR NAD

LIBRT 6429 PM.** INACCESS* NAD

TOTAL = 8

An asterisk (*) after the ﬁle type indicates that

the ﬁle is locked. (You cannot write on a locked

ﬁle .) R efe r to t he FI LE f un ct io n i n s ec ti on 6 f or

the meaning of the ﬁle type mnemonics. For

magnetic tape ﬁles (TYPE=TP), the current position

block number is displayed in the LENGTH/PRUS column

instead of the ﬁle length. The Status column

indicates the current position of the ﬁle (I/C

indicates mid- record) and whether the last

operation performed was a write. The entry

*INACCESS* indicates that the ﬁle is inaccessible;

it resides on a mass storage device that is

currently off or down. The FS column indicates

whether a ﬁle has the no-auto-drop status (refer to

the SETFS command). The LEVEL column gives the

se cu ri ty a cc es s le ve l of the ﬁ le.

On an unsecured system, the security access level is |

listed only if it is not null.

c

0S&\

60459680 G 7-15

y^Erc^v

Parameter Description

Pi Description

J Returns the contents of your control registers, error ﬂag

ﬁeld, and succeeding commands.

If the J option is used within a procedure, only the next

commands in the procedure are listed.

Example:

JOB CONTROL REGISTERS

R1 =

R2 =

R3 =

EF =

EFG =

R1G =

JOB PAGE PARAMETERS.

PW = 136

P L = 6 0

P D = 6

PENDING COMMANDS

WHILE,R1<20,C0PY.

COPYELAGENDA.

REWIND,AGENDA.

SET,R1=R1+1.

ENDW,C0PY.

REWIND,ENQWAJ.

COPYSBF,ENQWAJ.

REPLACE,ENQWAJ.

Returns your loader information including the status of

CYBER Interactive Debug utility (refer to the CYBER Loader

Reference Manual).

Example:

LOADER INFORMATION.

MAP OPTIONS = DEFAULT

DEBUG = OFF

GLOBAL LIBRARY SET IS -

LIB 3

7-16 60459680 D

0^\

Parameter Description

Pi Description

Returns your amount of resources used. The resources

listed include CPU time, mass storage activity, magnetic

tape activity, permanent ﬁle activity, and adder

activity. These statistics are factors used in

calculating SRUs used.

Example:

RESOURCES USED.

C P U T I M E 0 . 1 0 7 S E C S .

MS ACTIVITY 0.914 KUNS.

MT A CT IVI TY 0 .0 00 KU N S.

PF ACTIVITY 0.034 KUNS.

ADDER 0.003 KUNS.

SRU 3.157 UNTS.

r

60459680 H 7-16.1/7-16.2 |

Parameter Description

Pi Description

S Re tur ns yo ur acc umu la ted SRUs . T he SRU repr es ent s your

total usage of the system. This unit is derived from

central processor time, I/O activity, adder activity,

and memory usage.

Example:

SRU ACCUMULATOR.

SRU 3.162 UNTS.

Returns accumulated CPU time.

Example:

CPU ACCUMULATOR.

C P U T I M E 0 . 1 1 1 S E C S .

Returns the initial amount of resources available to you

in seconds, job step SRU, account block SRU, and the

remaining resources available for dayﬁle messages, com

mands, and mass storage. These values apply to the

current job and were set at the beginning of the job by

default or by the SETJSL, SETASL, or SETTL commands. As

the job progresses, the system increments the

appropriate resource counters. Secondary USER commands

do not affect these values. Entering a different CHARGE

command affects your account block and job step SRU

limits (refer to the CHARGE command).

0fc>\

Example:

RESOURCE USAGE ALLOWED.

SECONDS 64

JOB STEP SRU 31808

ACCOUNT BLK SRU 31808

DAYFILE MESSAGES 993

COMMANDS NO LIMIT

MASS STORAGE 59008

n60459680 H 7-17

Parameter Description

UJN=ujn Returns a one-line report of each of your jobs with the speciﬁed user

job name (UJN). The report for each job has the following ﬁelds:

jsn sc cs ds lid ujn status executing message

The ﬁelds have the following descriptions:

Field Description

jsn The job sequence name (JSN). It is a four-character,

system-deﬁned name.

sc The service class of the job. One of the following

mnemonics appears in this ﬁeld: /e^\

sc Service Class

SSystem

BBatch

RRemote batch

TInteractive

DDetached interactive

NNetwork supervisor

C Communication task

MMaintenance

0Installation class

1 Installation class

2Installation class

3 Installation class

The connection status (CS) of your job; that is, whether

your job is online and interactive, detached and

interactive, not interactive or queued. The following

values can appear:

cs Description

ON Online and interactive

DT Detached and interactive

N I N o t i n t e r a c t i v e

blank Queued

7-18 60459680 D

Parameter Description

/fP*N

Field Description

ds The default destination of batch output. It indicates

whether batch output will be routed to the central site

(BC) or to a remote batch terminal (RB).

lid The logical identiﬁer (LID) of the mainframe that is to

process the job. This is a three-character,

site-deﬁned mnemonic.

u j n T h e u s e r j o b n a m e ( U J N ) o f t h e j o b . I t i s e i t h e r t h e

name you assigned the job or it is your user index hash

if you did not assign the job a name.

status The overall job status. It indicates whether the job is

executing, whether it has been rolled out, or the queue

in which it now resides.

executing The command that the system is now executing,

message

Example:

/enqui re,uj n= Idi j ob

JSN SC CS DS LID UJN

ABC F.B . . BC . . LD IJO B

STATUS

WAIT QUEUE

EXECUTING MESSAGE

If you specify only the keyword UJN, the system returns a one-line

report for each job associated with your user name.

/sP^S

Example:

/enqui re,ujn

JSN SC CS DS LID UJN

ABCH.B. .BC.M42.LEVEL

ABCB.T.ON.BC. .AJLA

ABCI.B. .BC.M42.LDIJ0B

ABCF.B. .BC. .LDIJOB

STATUS

INPUT QUEUE

EXECUTING

PRINT QUEUE

WAIT QUEUE

EXECUTING MESSAGE

r

Do not specify the UJN=ujn parameter with any parameter other than

0=lfn2.

JSN=jsn Returns a detailed report of the job with the speciﬁed job sequence

name (JSN). The format of the report varies with the status of the

job. If the job is executing, the report includes the JSN, the job's

service class, its connection status, the default destination of its

batch output, the current status of the job, the user job name (UJN),

the job access level (on a secured system only), job resource

information, the executing command, a dayﬁle 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

ABCB.T.ON.BC. .EXECUTING UJN=AJLA LEVEL=LVLO

S RUS = 2 .57 3 . S R U L IM I T = N0 L I M IT. C M F L = 5 0 0 0 . E C S F L = 0 .

DAYFILE=

17.26.55. SUBMIT COMPLETE. JSN IS ABCE.

17.27.07. GET,0PLJ0B.

17.27.21. RE PLACE, CATEGOR.

17.27.32.SUBMIT,OPLJOB,TO.

17.27.32. SUBMIT COMPLETE. JSN IS ABCF.

17.28.04.ROUTE,CATEGOR,DC=IN.

17.28.04. ROUTE COMPLETE. JSN IS ABCH.

17.28.13.ENQUIRE,UJN.

17.28.26. ENQUIRE, JSN.

17.29.04. ENQUIRE, JSN=ABCB.

If the job is a queued ﬁle, the report includes the job's JSN, its

service class, the default destination of its batch output, the

logical identiﬁer (LID) of the mainframe that is to process the job,

its queue residence, its UJN, length in PRUs, and output

speciﬁcations.

Example:

/enqui re,j sn=abcf

ABCF.B. .BC. .WAIT QUEUE UJN=LDIJOB LEVEL=LVL0

PRU LENGTH* 32. DC=TT. FC= . ID= 0. EC=

If you specify the keyword JSN, the system returns a one-line report

on each job associated with your user name. The ﬁelds in the display

are identical to those you get when you specify only the keyword UJN,

except that the UJN ﬁeld and the EXECUTING MESSAGE ﬁelds are omitted.

Example:

/enquire,jsn

JSN S C C S D S L ID STAT US J SN SC C S D S LID S TAT US

ABCH.B. .BC.M42.INPUT QUEUE ABCB.T.ON.BC. .EXECUTING

ABCI.B. .BC.M42.PRINT QUEUE ABCF.B. .BC. .WAIT QUEUE

Do not specify the JSN=jsn parameter with any parameter other than

0=1fn2.

FN=lfnj Returns the status of local ﬁle lfnl (refer to the OP=F parameter).

0=lfn2 Writes the output on file lfn2» The default is OUTPUT. If you

specify only the 0=lfn2 parameter in a batch job, the

0P=pjp2...pn parameter defaults to 0P=A.

7-20 60459680 D '

/**^\

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 ﬁle FPROG, output like that

shown in the ﬁgures 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 dayﬁle. This command has no effect

when issued from a batch job.

The ERRMSG command must be executed from within a procedure. The error message off status

remains in effect until an ERRMSG,ON command is issued, or until your job returns to

interactive command status. The error message off status is not affected by the entry of

subsequent BEGIN or REVERT commands (that is, nested procedures).

Format:

ERRMSG,status

Parameter Description

status Speciﬁes whether error messages generated by commands within a

procedure are displayed at the terminal. Values that can be speciﬁed

for status are OFF (messages are not displayed) and ON (messages are

displayed). The default value is ON.

GO COMMAND

The GO command clears the pause bit of one of your executing jobs. The system may have set

the pause bit because of an error or a request for user input. You can set the pause bit

with one of your programs or with the PAUSE command.

Format:

GO,jsn.

Jsn Speciﬁes the job sequence name (JSN) of the job whose pause bit you

want to clear.

You must check the status of the pause bit to effectively use this command. The program does

not pause just because the pause bit is set. Similarly, the program does not proceed just

because the pause bit has been cleared. You can write a program that checks the status of

the pause bit and waits for that bit to be cleared (refer to the RECALL macro in Volume 4,

Program Interface).

If you want to determine whether a PAUSE or GO command has been entered, write a program to

set bit 13 of word RA and then status it. The system unconditionally clears bit 13 of word

RA whenever the PAUSE/GO command sets/clears the pause ﬂag (bit 12 of word RA). Hence,

when the system clears it, you can check the pause ﬂag. CPU programs that check the pause

ﬂag 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 dayﬁle message giving the model 176 accumulated clock cycle

count for the job. A clock cycle on the model 176 is 27.5 nanoseconds. COMPASS

instructions require a certain number of clock cycles to execute as described in the COMPASS

Reference Manual. This command can be used for performance comparisons.

Format:

HTIME.

The resulting dayﬁle message has the following format. The cycle count is in kilocycle

u n i t s .

HTIME nnnnnnnnnnnn.nnn KCYCLES.

An HTIME command processed on a machine other than the model 176 produces the following

dayﬁle 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, speciﬁes the user job name (UJN) and may

specify job processing parameters. Refer to Job Names in section 3 for the signiﬁcance of

the user job name. The ﬁrst command of a batch job must be a Job command.

Format:

ujn,P=priority,T=timelimit,CM=memory,EC=xmemory,ST=lid,AL=level.punchmode

or

uj n,Ppriori ty,Ttimelimi t,CMmemory,ECxmemory,STlid,ALlevel.punchmode

or

ujn,SC=class,T=timelimit,CM=memory,EC=xmemory,ST=lid,AL=level.punchmode

or

ujn,SCclas s,Ttimelimi t,CMmemory,ECxmemory,STlid,ALlevel.punchmode

or

uj n,priority,timelimit,memory,xmemory,lid,level.punchmode

or

uj n,class,t imelimit,memory,xmemory,lid,level.punchmode

All parameters except the parameter ujn are optional. If you include keywords when you

specify optional parameters, they are order-independent. Otherwise, they are

order-dependent.

Parameter

ujn

P=priority

SC=class

Description

Alphanumeric user job name (UJN) of one to seven characters. This

name identiﬁes the individual jobs being run under the same user

name.

Speciﬁes 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-deﬁned 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-deﬁned 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.

Speciﬁes the service class to be assigned to the job. The value

class must be one of the following values:

class Description

SY System

60459680 F 7-23

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-deﬁned class n (0 < n < 3)

The default for SC=class depends on your default service class

assignments (refer to Job Service Classes in section 3).

AL=level Speciﬁes the maximum security access level your job can attain.

Unless changed by your site, the value level can be any one of the

following names:

LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7

You may not be authorized to use all of these access levels (refer

to the LIMITS command). The default is the lowest access level you

are authorized to use. On an unsecured system, this parameter has

no effect, but the system does ensure that you specify a valid level

name.

T=timelimit Speciﬁes the central processor job step time limit in seconds.

Values can range from 1 to 77777. Decimal is the default base.

Octal values from 1 to 77777s (* t0 32767) can be entered if

followed by a B sufﬁx. The default limit is 64 (100g).f Decimal

values from 32767 to 77777 set the time limit at its maximum. The

time limit set by this parameter must be sufﬁcient for completion

of each of the steps in the job (refer to Time Limit Control in

se ct io n 3 ).

CM=memory Speciﬁes the maximum octal ﬁeld length for the job (refer to Field

Length Control in section 3). The system rounds the value to the

next highest multiple of 100g. The default value is the maximum

ﬁeld length for which you are authorized (refer to the LIMITS

command) or the maximum ﬁeld length available for user jobs

(dependent on machine size), whichever is smaller. The ﬁeld 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

EC=xmemory

> f f \ ST=lid

Description

A value containing an 8 or 9 or the sufﬁx D is interpreted as

decimal.

Speciﬁes 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 ﬁeld 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 sufﬁx D is interpreted as decimal,

Speciﬁ es the logica l id entiﬁer (LID ) of the host to w hi ch y ou a re

routing the speciﬁed job. The LID must be a three-character

alphanumeric s trin g deﬁned by site personnel. The lo cal host is

the default.

You must have special authorization to use this parameter (refer to

the LIMITS command).

punchmode Speciﬁes the conversion mode for card decks. This parameter must

be entered in columns 79 and 80. A 26 indicates that coded cards

are to be converted in 026 mode; 29 indicates cards are converted in

029 mode. This initial keypunch mode can be changed within the job

by a conversion change card (refer to Coded Cards in appendix F)

when reading cards or a ROUTE command when punching cards. If this

parameter is omitted, the installation default keypunch mode is

used. This conversion mode indicator is ineffective for remote

batch jobs entered with mode 4 card readers; it is effective for

remote batch jobs entered with HASP, 2780, and 3780 card readers.

The system issues error messages when parameter speciﬁcations exceed validation limits. It

also issues an error message if an extended memory ﬁeld length is speciﬁed when your

central memory validation limit is less than lOOOOg words. Consult installation personnel

for further installation restrictions based on the machine conﬁguration 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 dayﬁle 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 ﬁle 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 ﬁle. Therefore, SUBMIT directives (/JOB,/USER,/NOSEQ, and so

forth) are not allowed.

Format:

LDI,FN=lfn,ID=id,OP=OP,DC=dc,UN=un,FM=fm.

or

LDI,lfn,id,OP,dc,un,fm.

The parameters in the ﬁrst format are order-independent. Those in the second format are

order-dependent.

Parameter

FN=lfn

ID=id

OP=OP

DOdc

Description

Speciﬁes the name of the ﬁle containing the job(s) to be submitted.

LOAD is the default.

Speciﬁes the identiﬁer of the local device which will receive job

output. The identiﬁer id must be octal and in the range 0 through

67B. If you omit this parameter or specify only the keyword ID,

implicit central site routing occurs (refer to Implicit Routing under

the description of the ROUTE command, section 9).

You may not specify ID=id parameter if you specify the UN=un or FM=fm

parameter.

Directs the system to enter the job sequence name (JSN) of each job in

the dayﬁle of the job that issued the LDI command.

Speciﬁes the disposition of output for each job that is queued for

input•

.^^S\

dc Description

IN Disposes of job output according to the default option for

the job's origin type (refer to Job Origin Types and Service

Classes in section 3).

UN=un

NO Discards all output.

TO Queues the output with a wait disposition.

Speciﬁes 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

Parameter Description

FM-fm Speciﬁes the family name of the remote batch user to whom the system

routes each job's output. You must have special authorization to

specify an alternate family name (refer to the LIMITS command). If

you omit this parameter or specify only the keyword FM, implicit

remote routing occurs (refer to Implicit Routing under the description

of the ROUTE command, section 9).

You may not specify this parameter if you specify the ID=id parameter.

The number of executing jobs and output ﬁles 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 dayﬁle 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 ﬁles.

Format:

LENGTH,lfn.

Parameter Description

lfn Name of a ﬁle assigned to the job.

The information given for the local ﬁle 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 ﬁrst user name and those of the current user name. You

can use the ENQUIRE(OP=U) command to determine what your actual limits would be in such a

case.

Format:

LIMITS,L=lfn.

Parameter

L = l f n

Description

Speciﬁes the ﬁle which receives the validation information. The

default is OUTPUT.

The validation limits show the extent to which you can use various system resources. The

LIMITS output falls into the following categories:

Resource Limits.

Other Characteristics.

User Permissions.

Network Applications.

Privileged Network Applications.

Local Applications.

Shell Permissions.

Security Permissions.

Security Access Categories.

Security Access Levels.

Service Classes.

Default Service Classes.

If there are no entries for a category, the system suppresses the header for that category.

7-28 60459680 D

/P^N

RESOURCE LIMITS

The system indicates the maximum number of speciﬁc 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 ﬁles allowed.

Permanent ﬁles allowed in your catalog.T

PRUs available for any one indirect ﬁle.

PRUs available for any one direct ﬁle.

PRUs available for all indirect ﬁles.

PRUs available per job.

Messages that may be issued to the dayﬁles.

Batch commands that may be processed.

Cards that may be punched per ﬁle.

Lines that may be plotted per ﬁle.

Lines that may be printed per ﬁle.

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

ﬁles allowed in your catalog. Whenever you initiate a permanent ﬁle operation, the

system assigns a limit, which can vary with the service class of your job.

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

/<s*\

yﬂaSv

7-30 60459680 D

USER PERMISSIONS

In addition to specifying resource limits for certain resources, the system lists special

privileges that you possess. The following list contains special privileges you might

possess, including the privilege to: |

Change your passwords.

Use privileged interactive commands.

Create dir ect a cc ess ﬁ le s.

Create indirect access ﬁles.

Have system origin privileges.

Access/create library ﬁles.

Assign magnetic tapes.

Access system without supplying charge/project number.

Access or create ﬁles on auxiliary devices.

Access transaction functions for library updates.

Have unlimited terminal connect time without timeout.

Use sys te m cont rol p oin t faci lit y.

Have special accounting privileges.

Have the BIO subsystem privilege to use the V carriage control character in a I

user-speciﬁed PFC array in a ﬁle. |

Use the PROTECT command.

Transfer permanent ﬁles between hosts.

Transfer queued ﬁles between hosts.

Specify mainframe logical identiﬁers (LIDs) on the Job and ROUTE commands.

Specify charge numbers other than the default charge number.

Deﬁne a password without random characters.

Have remote maintenance privileges.

Specify an alternate family during a job.

Control network processing units (NPUs).

60459680 G 7-31

NETWORK APPLICATIONS

The following are network applications you may be authorized to use:

• Interactive Facility (IAF).

• Remote Batch Facility (RBF).

• Transaction Facility (TAF).

• Message Control System (MCS).

• Terminal Verification Facility (TVF).

• Interactive Transfer Facility (ITF).

LOCAL APPLICATIONS

The system lists local applications you are authorized to use. If there are no such

applications, this category does not appear in the output.

PRIVILEGED NETWORK APPLICATIONS

.<^*^^s

The system lists the privileged network applications you are authorized to use. The /

Communications Supervisor (CS) is one such application.

SHELL PERMISSIONS

The system lists controls applicable to a shell program you write to monitor commands

entered under your user name. The list includes the following:

Clear controls upon loading errors with shell program.

Clear shell processing if screening program aborts.

Local ﬁle load of shell program.

Global ﬁle load of shell program.

System library load of shell program.

Monitor commands from terminal.

Monitor commands outside of procedures.

Monitor commands inside of procedures.

7-32 60459680 D

x^*S

SECURITY PERMISSIONS

There are special security-related permissions you may possess. The list may include any of

the following permissions:

Write unlabeled magnetic tapes.

Write to or extend a ﬁle with an access level lower than your job access level.

Lower ﬁle access levels.

Lower your job access level.

Assign an expiration date for a ﬁle password or ﬁle permission.

Assign an expiration date for your user password.

Execute on-line diagnostics.

Perform security administrator duties.

SECURITY ACCESS CATEGORIES

The system lists the access categories you can associate with your permanent ﬁles. When

you create a permanent ﬁle, the system associates all categories for which you are

authorized with this ﬁle. You can change this association with the SETPFAC command.

SECURITY ACCESS LEVELS

The system lists a set of access levels that determine the access levels at which your jobs

may run and the access levels at which you may create or access ﬁles.

SERVICE CLASSES

The system lists all of the service classes you can assign to a job.

restrict the use of a service class to jobs of certain origin types,

these restrictions with the CLASS command.

You r si te can f urther

You can determine

DEFAULT SERVICE CLASSES

The system lists the service class it initially assigns to your job if you do not specify a

service class on the Job command or ROUTE command. This default assignment can vary with

the origin type of your job. Unlike most other validation limits and privileges, you can

change this default assignment with the CHVAL command.

60459680 D 7-33

The following is an example of a user's validation limits:

r'^N.

/ l i m i t s

LIMITS FOR STARSKY FM/NOSCLSH 83/08/09. 17/11/13/

MAXIMUM NUMBER OF -

MAGNETIC TAPE UNITS THAT MAY BE ASSIGNED 3

REMOVABLE AUXILIARY DEVICES THAT MAY BE ASSIGNED 2

CPU SECONDS ALLOWED FOR EACH JOB STEP UNLIMITED

CENTRAL MEMORY WORDS ALLOWED/100B 2037B

EXTENDED MEMORY WORDS ALLOWED/1000B OB

JOBS THAT CAN BE DETACHED 3

DEFERRED BATCH FILES 8

PERMANENT FILES ALLOWED IN YOUR CATALOG UNLIMITED

PRUS AVAILABLE FOR ANY ONE INDIRECT FILE 192

PRUS AVAILABLE FOR ANY ONE DIRECT FILE 1024

PRUS AVAILABLE FOR ALL INDIRECT FILES 4096

PRUS AVAILABLE FOR JOB 66048

MESSAGES THAT MAY BE ISSUED TO THE DAYFILES 1008

BATCH COMMANDS THAT MAY BE PROCESSED UNLIMITED

CARDS THAT MAY BE PUNCHED PER FILE UNLIMITED

L I N E S T H AT M AY B E P L O T T E D P E R F I L E 5 1 2

LINES THAT MAY BE PRINTED PER FILE UNLIMITED

SRUS ALLOWED PER JOB UNLIMITED

OTHER CHARACTERISTICS -

USER INDEX 5410B

DEFAULT CHARGE NUMBER ASSIGNED 1234

DEFAULT PROJECT NUMBER ASSIGNED 123A456

SYSTEM PROLOGUE 2B

USER PROLOGUE PROLOG

INTERACTIVE SUBSYSTEM BATCH

INTERACTIVE CHARACTER SET MODE NORMAL

7-34 60459680 D

,4*gi^v

/ $ ^ \

THE FOLLOWING ARE VALID USER PERMISSIONS -

CHANGE YOUR PASSWORD

CREATE DIRECT ACCESS FILES

CREATE INDIRECT ACCESS FILES

ACCESS/CREATE LIBRARY FILES

ASSIGN MAGNETIC TAPES

ACCESS OR CREATE FILES ON AUXILIARY DEVICES

TRANSFER PERMANENT FILES BETWEEN HOSTS

TRANSFER QUEUED FILES BETWEEN HOSTS

SPECIFY LID-S ON JOB AND *ROUTE* COMMANDS

CHARGE NOT RESTRICTED TO DEFAULT

DEFINE NON-RANDOMIZED LOGIN PASSWORD

THE FOLLOWING ARE VALID NETWORK APPLICATONS -

INTERACTIVE FACILITY (IAF)

REMOTE BATCH FACILITY (RBF)

TRANSACTION FACILITY (TAF)

TERMINAL VERIFICATION FACILITY (TVF)

THE FOLLOWING ARE VALID SHELL PERMISSIONS -

PROCESS COMMANDS OUTSIDE CCL PROCEDURE

SYSTEM LIBRARY LOAD OF SHELL PROGRAM

THE FOLLOWING ARE VALID SECURITY PERMISSIONS -

WRITE UNLABELED MAGNETIC TAPES

THE FOLLOWING ARE VALID SECURITY ACCESS LEVELS -

ACCESS LEVEL LVLO

THE FOLLOWING ARE ALLOWED SERVICE CLASSES -

BATCH (BC)

REMOTE BATCH (RB)

INTERACTIVE (TS)

DETACHED INTERACTIVE (DI)

THE USER DEFAULT SERVICE CLASS

FOR BATCH ORIGIN IS BC

F O R R E M O T E B A T C H O R I G I N I S R B

FOR INTERACTIVE ORIGIN IS TS

INQUIRY COMPLETE.

/

60459680 F 7-35

LISTLID COMMAND

The LISTLID command lists information on the conﬁguration of your network and on the

availability of hosts in the network. Information available through LISTLID includes:

• Logical identifiers (LIDs) and physical identifiers (PIDs) for hosts in the

network. LIDs are used in certain NOS commands (for example, Job, ROUTE, MFLINK,

and MFQUEUE) to specify the destination host for a job or ﬁle routing operation.

• The subsystem(s) available to provide network communications. This could be any or

all of the following: Remote Host Facility (RHF), Network Access Method (NAM), and

SCOPE 2 Station Facility (SSF).

• Host characteristics such as local host or linked status, store and forward

capabilities, and host availability.t

Note that the site administration has the option of choosing whether information for any

given LID or PID can be listed using the LISTLID command.

Format:

LISTLID,LID=lid,PID=pid,l=lfn

or

LISTLID,ST=lid,PID=pid,1=lfn

Parameter Description

LID=lid Speciﬁes the LID for which information is to be displayed. If LID=lid

or or ST=lid is speciﬁed, information is listed for the speciﬁed LID.

ST=lid (The LID and ST keywords are interchangeable; either may be used, but

not both.) If this parameter is omitted and the PID parameter is also

omitted, information is listed for all LIDs in the network.

PID=pid Speciﬁes that output is to be listed only for LIDs associated with this

PID. If the LID=lid parameter is also speciﬁed, information is listed

only for that LID. ••» If no LID=lid parameter is specified, information is

listed for all LIDs associated with this PID. If only the keyword PID

is speciﬁed, information is listed on all LIDs, grouped according to

their associated PIDs.

L=lfn Speciﬁes that LISTLID output is to be written to ﬁle lfn. If this

parameter is omitted, output is written to ﬁle OUTPUT.

Examples:

LISTLID.

This command lists information on all LIDs in the network for which the site allows

information to be listed. The information is listed in output format 1.

LISTLID,LID=lid,L=lfn.

This command lists information on all LIDs in the network with the name lid except those

that the site does not allow to be listed. The information is listed in output format 1 on

ﬁ l e l f n .

rHosts connected through an X.25 network are always considered available as long as the /**s\

network processing unit (NPU) connecting your host to the X.25 network is available. *

7-36 60459680 E

LISTLID,LID=lid,PID=pid.

This command provides information on the named LID associated with the speciﬁed PID. If

the site does not allow listing of the named LID, or of both the named LID and PID, the

system returns a dayﬁle message indicating that the speciﬁed LID was not found. If the

site allows the LID to be listed but not the PID, LISTLID outputs information using format

2; however, the system will not display the PID name or the names of available subsystems.

Instead, the system replaces those names with the characters .

LISTLID,LID=lid,PID.

This command lists all LIDs with the name lid except those that the site does not allow to

be listed. The speciﬁed LIDs are listed under their associated PIDs using output format 2,

LISTLID,PID.

This command uses output format 2 to list all LIDs, grouped according to their associated

PIDs. Any LIDs that the site does not allow to be listed are omitted from the output. Any

PIDs that cannot be listed are replaced by the characters .

LISTLID,PID=pid.

This command uses output format 2 to list all LIDs associted with the speciﬁed PID. Any

LIDs that the site does not allow to be listed are omitted from the output. If the PID

cannot be listed, pid is replaced with the characters .

LISTLID uses two output formats. Output format 1 is used when the LISTLID command does not

contain a PID parameter.

LID MAINFRAME ATTRIBUTE

LOOPBACK

NETWORK

M64 NOS 964 RHF,SSF

M42 NOS 420 LINKED NONE AVAILABLE

B2C VSOS LINKED RHF

MFZ SC0PE2 LINKED SSF

MSI NOS MSI LINKED NAM

Output format 2 is used when a PID parameter is speciﬁed on the LISTLID command.

• Example of output format 2:

PID LID MAINFRAME TYPE ATTRIBUTE RHF NAM SSF

M64 SN 964 HOST HV IN NA DISABLED

M64

LBK

>piP*N

In output format 2, the attributes listed for each PID are also applicable for each LID

listed under that PID. In the above example, therefore, LID M64 has the attributes H and V,

while LID LBK has the attributes H, V, and B.

60459680 D 7-37

y<:*«\

Attributes listed in the ATTRIBUTE column can be listed by name or by mnemonic.

Attribute Name

HOST

LINKED

STORE FORWARD

VALIDATION

LOOPBACK

Mnemonic Description

H I n d i c a t e s t h a t t h i s i s t h e l o c a l h o s t ( t h a t i s , t h e h o s t

you are logged into).

L Indicates that this host is linked to your local host.

S I n d i c a t e s t h a t y d u c a n t r a n s f e r q u e u e d ﬁ l e s t o t h i s

host through an intermediate linked host.

V Indicates that user validation is performed by the local

host as well as by the destination host. If this

attribute is not listed for your local host, user

validation is performed only by the destination host.

B I n d i c a t e s t h a t t h e L I D i s a l o o p b a c k L I D ( u s e d f o r t e s t

purposes).

Entries that can be listed in the RHF, NAM, and SSF columns are as follows:

Entry

IN

NA

OUT

DISABLED

Signiﬁcance

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 ﬁle transfer to that host.

Indicates that the subsystem is not available or that no link exists to this

PID throught this subsystem.

Indicates that the link to the PID is out of service due to a network fault

condition.

Indicates that the link to the PID has been disabled by the console operator.

7-38 60459680 D

/H^v

MACHINE COMMAND

Some programs that ran on mainframes other than models 815, 825, 835, 845, and 855 will not

run on the models 815, 825, 835, 845, and 855 until changes are made in your job. Programs

most likely to run incorrectly on models 815, 825, 835, 845, and 855 are COMPASS programs

with tight instruction-modiﬁcation loops. The MACHINE command will enable some of these

programs to run correctly on these models.

Format:

MACHINE,EP=state.

Parameter Description

EP=state Speciﬁes whether extended stack purging is selected. EP=ON selects

it and EP=OFF disables it.

Instruction stack purging is extended by specifying ON and is made normal by specifying OFF

and remains in effect until a subsequent MACHINE command or MODE macro alters it. The

initial status of stack purging is site-selectable. For more information on stack purging,

refer to the MODE macro in Volume 4, Program Interface.

To determine if a program will run correctly on models 815, 825, 835, 845, and 855, run the

job with extended stack purging disabled (EP=OFF). If unexpected results occur, do another

run with stack purging extended (EP=ON). When stack purging is extended, the execution time

of the program may be increased. If unexpected results still occur, recode COMPASS programs

or recompile high-level language programs on models 815, 825, 835, 845, and 855.

MFL COMMAND

The MFL command resets the maximum ﬁeld length for each subsequent job step.

Format:

MFL,CM=nnnnnn,EC=mmmm.

or

MFL, nnnnnn, mimum.

Parameter Description

CM=nnnnnn Speciﬁes the maximum central memory ﬁeld length (octal is assumed

unless decimal is speciﬁed by a D sufﬁx or use of the digits 8 or 9).

EC=mmmm Speciﬁes the maximum extended memory ﬁeld length. The value of nrnimm

is the actual extended core ﬁeld length divided by lOOOg.

The ﬁrst 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 ﬁeld length of subsequent job steps.

The value cannot exceed the maximum ﬁeld length for the job nor can it be less than 1500,

the ﬁeld length required for the utility (CONTROL) that processes MFL. If extended memory

is assigned for the job, the CM ﬁeld length cannot be less than 10000. Likewise, the

parameter mmmm sets an upper boundary for the extended memory ﬁeld length of subsequent job

steps and cannot exceed the maximum ﬁeld length for the job. If the value 0 (zero) is

entered for CM or extended memory ﬁeld length, the MFL is set to either the maximum ﬁeld

length for which you are authorized or the ﬁeld length speciﬁed on the Job command,

whichever is smaller.

The MFL command clears any initial running ﬁeld length previously established with the RFL

command or the SETRFL macro and allows the system to determine the ﬁeld length for each

succeeding job step. The system continues to determine ﬁeld 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 ﬁle containing lines of data entered as a character string on

the same line as the command.

Format:

NOTE,lfn,NR./linei/iine2/.../linen

Parameter Description

lfn Speciﬁes the name of the ﬁle which contains the speciﬁed lines.

Default is OUTPUT.

NR Inhibits rewind of lfn. Default is to rewind the ﬁle at the

beginning and end of NOTE command execution.

/ Speciﬁes the delimiting character used to separate the individual

en tr ie s th at b ec ome li ne s in th e ﬁl e. I t can b e an y ch ar ac ter. I t

must immediately follow a period or right parenthesis. Multiple

delimiters generate blank lines.

linei Speciﬁes the character string which constitutes one line of data in

lfn.

I f a ﬁ l e c o n t a i n s m o r e l i n e s t h a n c a n b e e n t e r e d w i t h a s i n g l e N O T E c o m m a n d , a s e r i e s o f - ^ ^ v

NOTE commands, each with an NR, can be used. This series should be followed with a PACK '

command since each NOTE command writes an EOR.

7-40 60459680 D

igpWN,

Example:

The following sequence of commands creates a procedure ﬁle (PFILE) that can insert an input

record after any record in an existing master ﬁle (LISTFIL).

NOTE/PFILE,NR.+.PROC,INSERT*I,N.+GET,LISTFIL.+COPYBR,LISTFIL,NEWLIST,N.

NOTE/PFILE/NR.+COPYBR,INPUT,NEWLIST.+COPYEI,LISTFIL,NEWLIST.

NOTE,PFILE,NR.+REPLACE,NEWLIST=LISTFIL.

PACK,PFILE.

SAVE,PFILE.

To insert an input record after the second record in LISTFIL, the user includes the

following command in the job that contains the new input record.

BEGIN,INSERT,PFILE,2.

OFFSW COMMAND

The OFFSW command clears the sense switches for reference by one of your jobs.

Format:

OFFSW, switch! ,switch2 switch^ jsn.

Parameter Description

switchi Speciﬁes the switch(es) to be cleared. You must denote each switch

switchi by an integer in the range of 1 through 6. If you specify 0

for this parameter, the system clears all sense switches.

jsn Speciﬁes the job sequence name (JSN) of the job whose sense switch(es)

will be changed, jsn is an optional parameter; its default is the JSN

of the current job. The system recognizes the jsn parameter by its

alphabetic characters; therefore, jsn can appear anywhere in the

parameter list and can be omitted without leaving a blank parameter

ﬁeld.

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 ﬁeld in the

control point area and the one in RA are updated separately.

Format:

ONSW,switch!,switch2,...^witchn,jsn.

Parameter Description

switch.^ Speciﬁes the switch(es) to be set. You must denote each switch

switch^ by an integer in the range of 1 through 6. If you specify 0

for this parameter, the system sets all sense switches.

jsn Speciﬁes the job sequence name (JSN) of the job whose sense switches

will be changed, jsn is an optional parameter, its default is the JSN

of the current job. The system recognizes the jsn parameter by its

alphabetic characters; therefore, jsn can appear anywhere in the

parameter list and can be omitted without leaving a blank parameter

ﬁeld.

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

ﬁve) of randomly generated characters to the end of a new password that you select.

If your site uses password randomization, you can enter the PASSWOR command only from an

i n t e r a c t i v e j o b . I f y o u r s i t e d o e s n o t u s e p a s s w o r d r a n d o m i z a t i o n , t h e o r i g i n t y p e o f y o u r ^ ^

j o b m u s t m a t c h t h e t y p e o f p a s s w o r d y o u w a n t t o c h a n g e . I n o t h e r w o r d s , a n i n t e r a c t i v e ^ )

password must be changed from an interactive job, and a batch password must be changed from

a batch or remote batch job.

Format:

PASSWOR,oldpassword,newpassword,XD-expiredate.

or

PASSWOR,oldpassword,newpassword,XT=expireterm.

PASSWOR.

•*5^v

7-42 60459680 D

oldpassword

newpassword

XD=expiredate

XT=expireterm

Parameter Description

Speciﬁes the old password. This is a required parameter if

password randomization is used.

Speciﬁes the new password. The new password must be not more than

seven characters long. Your site determines the minimum length of

passwords (4 is the default). This is a required parameter if

password randomization is used.

Speciﬁes the expiration date for the password. The value

expiredate must be a 6-digit string of the form yymmdd, where yy,

mm, dd are 2-digit year, month, and day designators, respectively.

The latest date you can specify and the default expiration date are

site-determined.

You must have special authorization to specify an expiration date

for password (refer to the LIMITS command).

Speciﬁes the life of the password in days. If you specify 0, the

password expires immediately. If you specify 4095 or *, the

password does not expire. The default expiration term and the

maximum expiration term are site-determined (no site can choose a

value greater than 4095).

You must have special authorization to specify an expiration term

for a password (refer to the LIMITS command).

You cannot specify a new expiration date (using either XD or XT) without also specifying the

oldpassword and newpassword parameters. Also, if you omit both the XD and XT parameters

when you enter the PASSWOR command, the default expiration date is the current date plus the

site-determined expiration term.

The ﬁrst 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

ﬁeld. When entered from a batch job, the system reads the parameters from a record in ﬁle

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

Speciﬁes the job sequence name (JSN) of the job whose pause bit you

w a n t t o s e t . *

You must check the status of the pause bit to effectively use this command. The program

tust becaZ8^ b6C^SVhe.PaUSe bU ±S Set' Similarly, the program does not proceed

just because the pause bit has been cleared. You can write a program that checks the status

4°! P^g^rinterf^e):31'8 *" "" ^ t0 ^ ^^ (refer C° ^ «<*"■ -c^n^lum^8

sft^i/ffnf0 def^ine/hfher a PAUSE °r G0 command has bee* entered, write a program to

H w h e n ever flTJjj£ / S ? f " "V?" *" 8 yStem u n c o n d i t i ^ally c l e a r s b i t 1 * 3 I f wordka whenever the PAUSE/GO command sets/clears the pause ﬂag (bit 12 of word RA) Henrp

nZ on^T^r8 I'' y°,U ^ Ch6Ck the PaUSe flag' CP" ""«"" ^ Sick "because

ss.«™ com^hL^rL^d:17 on N0S 2*but these programs —det— — *

PROTECT COMMAND

I=!^R°^T COnma?d is used to activate or deactivate preservation of the extended memory

your^b is z^roVdlt th" ^T*? **"•'- Warily, the extended memory assig'd L

steps. completion of a job step. With EC=ON, it is preserved between job

section)/6 aUth°rlZed C° USe the PR0TECT command (refer to the LIMITS command in this

NOTE

For mainframes using uniﬁed extended memory (UEM),

the execution of absolute programs or program

overlays always resets UEM to zero regardless of

PROTECT command status.

Format:

PROTECT,EC=state.

or

PROTECT,state.

7-44

--^^s.

60459680 E

0%B>i.

Parameter Description

EC=state Activates or deactivates extended memory preservation. You can specify

two values for state:

state Description

ON Activates the preservation of memory.

OFF Deactivates the preservation of memory. OFF is the default.

QGET COMMAND

_^ The QGET command assigns a queued ﬁle to your job. You must specify the job sequence name

( (JSN) or the user job name (UJN) associated with the queued ﬁle. Unless explicitly routed

elsewhere, the ﬁle remains with your current job. If a local ﬁle already exists with the

same name as the queued ﬁle, 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 Speciﬁes the four-character, system-generated JSN associated with the

queued ﬁle.

DC=q Speciﬁes the disposition of the queued ﬁle. WT is the default.

q Description

PR Print

PU Punch

PL Plot

W T W a i t

UJN=ujn Speciﬁes the UJN associated with the queued ﬁle.

FN=lfn Speciﬁes the local ﬁle name for the queued ﬁle. If speciﬁed, the

JSN is the default local ﬁle name. Otherwise, the default is the UJN.

If you specify neither a JSN nor a UJN or specify a UJN associated with two queued ﬁles

with the same disposition, a fatal system error occurs.

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

ID=pid

L = l f n

Pi

Description

Speciﬁes the physical identiﬁer (PID) of the SCOPE 2 mainframe to be

searched. If no PID is speciﬁed, all mainframes are searched. This

parameter may be speciﬁed with the parameter name (ID) and equal sien

omitted. n 6

Speciﬁes the name of the ﬁle to receive the QUEUE7 output. The

default is OUTPUT.

Speciﬁes the SCOPE 2 queues (input, output, execute, or punch) to be

displayed. Valid options for Pl are listed below. From one to four

options can be speciﬁed. The default is E.

Ei

A

E

Description

Lists jobs found in all queues (E, I, 0, and P).

Execute queue; lists the SCOPE 2 R display. Figure 7-1

provides an example of an execute queue listing.

Input queue; lists the SCOPE 2 R display for input. Figure

7-2 provides an example of an input queue listing.

Output queue; lists the SCOPE 2 H display for output.

Figure 7-3 provides an example of an output queue listing.

Punch queue; lists the SCOPE 2 H display for punch output.

Punch queue listings are the same as output queue listings,

as shown in ﬁgure 7-3.

7-46 60459680 D

JIP^Ny

Parameter

help

Description

Displays the command format or the physical identiﬁers for all

available SCOPE 2 mainframes. The following are valid entries for the

help parameter.

help Description

ID Displays physical identiﬁers for all SCOPE 2 mainframes in

the network.

SYNTAX Displays the QUEUE7 command format,

or

S

/queue7,e

JOBS 6/ 52/ 70 R(Z),1.

ORD ACTION

ID

TYPE

JOBNAME PRTY JOB TIME TIME LCM

O R I G I N U S E D L E F T I N U S E

FIRST ACTION MESSAGE/LAST DAYFILE MESSAGE

J O B B G

STAT

3 M06/**

REPONSE

JOBXXXZ 4000 M06/**

PAUSE. DO NOT GIVE A GO.

0 7 2 6

TESTING ON 606

PA US

4 M06/**

RESPONSE

JOBXXXZ 4000 M06/**

PAUSE. DO NOT GIVE A GO.

0 7 2 6

TESTING ON 606

PA US

5 M06/**

RESPONSE

JOBXXXZ 4000 M06/**

PAUSE. DO NOT GIVE A GO.

0 7 2 6

TESTING ON 606

PA US

QUEUE7 COMPLETE

Column headers

Header

ORD

ACTION ID

JOBNAME

PRTY

JOB ORIGIN

TIME USED

TIME LEFT

LCM IN USE

JOB STAT

BG

60459680 D

Figure 7-1. QUEUE7 Execute Queue Sample Listing

for the QUEUE7 execute queue listing have the following meanings:

Description

The job ordinal.

The station/terminal identiﬁer of the terminal from which the job expects

a response; present only when the job requires a response.

Job name of the executing job.

Priority of the job; must be in the range of 0 to 7777g.

Station/terminal identiﬁer of the terminal from which the job was

submitted.

CPU seconds used by the job.

CPU seconds remaining for execution.

Number of LCM buffers in use by the job.

Current processing state of the job.

Indicates that the job will be scheduled as a background priority job.

7- 47 |

FIRST ACTION MESSAGE/

LAST DAYFILE MESSAGE

If there are action messages for the job, the message is the ﬁrst action

message; otherwise, the message is the last dayﬁle message.

ACTION Indicates that the above message requests an operator

action such as a tape mount.

CFO RESP Indicates that the above message requests the operator to

respond with a CFO type entry.

RESPONSE Indicates that the above message requests the operator to

respond with a command such as GO or DROP.

/queue7,i

SFTS 10/ 172/ 172 H(Z),I,103.

ORD FILENAME FILE PRTY DEVICE

ORIGIN MT NT

-REQUIREMENTS TIME

YD YL SM SN SP LIMIT

DEPEND BG

107Z JOBXXXZ

110Z JOBXXXZ

M06/** 1002 0 0

0 0 1 0

STAT ION M06

INPUT 2

OUTPUT 1

PUNCH 0

M02 MFF M05 MSD

0 0 0 0

MFU UKWN TOT

0 0 2

0 0 1

0 0 0

QUEUE7 COMPLETE

Figure 7-2. QUEUE7 Input Queue Sample Listing

7-48 60459680 D

J$$!0?\

/fPN.

Column headers for the QUEUE7 input queue listing have the following meanings:

ORD Input queue sufﬁxed with the last letter of the SCOPE 2 physical

identiﬁer.

FILENAME File name of the input job as speciﬁed on the job card.

FILE ORIGIN Identiﬁer 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 speciﬁed on the job card.

DEPEND A two-character dependency identiﬁer as speciﬁed on the job card.

B G I n d i c a t e s t h a t t h e j o b w i l l b e s c h e d u l e d a s a b a c k g r o u n d p r i o r i t y j o b ,

/queue7,o

SFTS 10/ 17 2/ 172 H(Z) ,0,103

ORD FILENAME F I L E P R T Y

DESTIN

DISP FORM

CODE CODE

FILE

SIZE

FILE IN

TRANSFER

111Z JOBXXXZ M06/** 4003 PR

STATION M06

INPUT 2

OUTPUT 1

PUNCH 0

M02 MFF M05

0 0 0

MSD MFU UKWN

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 pu t q u e ue o r din a l s ufﬁ x e d w i t h t h e l a s t l e t t e r o f t h e S COP E 2 p h y s i cal

identiﬁer.

FILENAME File name of the output ﬁle as speciﬁed on the job card.

FILE DESTIN Station/terminal identiﬁer of the terminal to which the output ﬁle is to

be routed.

P R T Y F i l e p r i o r i t y ; m u s t b e i n t h e r a n g e f r o m 0 t o 7 7 7 7 g .

DISP CODE File disposition code.

FORM CODE Forms code of the ﬁle.

FILE SIZE File length in PRUs.

FILE IN Indicates whether or not the ﬁle is currently being transferred to a

TRANSFER station; possible values are Y for yes, and N for no.

RERUN COMMAND

The RERUN command sets job rerun status.

Format:

RERUN.

If the RERUN command has been issued, the operator can rerun the job if necessary. This

command is ignored from a interactive origin job.

RESOURC COMMAND

I The RESOURC command is required in any job that uses more than one tape or removable

auxiliary pack concurrently; it prevents deadlocks with other jobs which may need the same

resources. You do not need to use a RESOURC command if you have only one multivolume tape

ﬁle or multipack disk ﬁle because the system treats each as only one resource unit.

I Nonremovable auxiliary packs should not be speciﬁed on the RESOURC command; non removable

packs are always available to all users.

7-50 60459680 F

/<^^\

Format:

RESOURC,rt1=u1/levelx,rt 2=u2/level2 rtn=u=n/leveln.

Parameter Description

rt^ Resource type:

LO 200-cpi, seven-track magnetic tape unit

HI 556-cpi, seven-track magnetic tape unit

HY 800-cpi, seven-track magnetic tape unit

HD 800-cpi, nine-track magnetic tape unit

PE 1600-cpi, nine-track magnetic tape unit

GE 6250-cpi, nine-track magnetic tape unit

MT t S eve n-t rac k ma gne tic ta pe uni t

NTt Nine-track magnetic tape unit (800/1600-cpi)

DBm 885-42 Disk Storage Subsystem (full-track; Km<3)

DCm 895 Disk Storage Subsystem (full-track; l<m<2)

DDm 834 Disk Storage Subsystem (full-track; Km<8)

DGm 836 Disk Storage Subsystem (full-track; l<m<3)

Dim 844-21 Disk Storage Subsystem (Km<8)

DJm 844-41/44 Disk Storage Subsystem (Km<8)

DKm 844-21 Disk Storage Subsystem (full-track; l<m<8)

DLm 844-41/44 Disk Storage Subsystem (full-track; Km<8)

DMm 885-11/12 Disk Storage Subsystem (half-track; l<m<3)

DQm 885-11/12 Disk Storage Subsystem (full-track; Km<3)

DV 819 Disk Storage Subsystem (single-density)

DW 819 Disk Storage Subsystem (double-density)

The value n denotes the number of units (spindles) required for a

particular auxiliary disk ﬁle that you will access in your job. In

this case, the rt^ value must correspond to the R=r speciﬁcation on

the permanent ﬁle command that references the disk pack (refer to

section 10).

Ui Maximum number of units of resource type rti this job will use

concurrently; any rtj^ entry can be changed on subsequent RESOURC

commands. (Refer to Altering Resource Requirements.) An rt=0 entry can

be entered to clear a resource type that is no longer required.

level Speciﬁes the security access level at which you want to access magnetic

tape units. The parameter is ignored for auxiliary disk packs. Unless

changed by your site, level can be one of the following names:

LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7

The default is the current job access level.

On a secured system, the access level you specify must be valid for the

job (ENQUIRE,B returns this information) and for the device to which you

ar e a ss ig ni ng t he ﬁle.

On an unsecured system, the parameter has no effect. The system does,

however, check for valid parameter speciﬁcations.

rtRetained for compatibility with NOS 1.2. Refer to restrictions described under Tape Units

in this section.

60459680 F 7-51

DEADLOCK PREVENTION

The system manages the use of tape units and disk packs so as to prevent deadlocks from

occurring. A deadlock means that the system, by assigning a tape unit or pack to one job,

prevents another job with currently assigned resources from completing. For example, an

installation with two tape units is processing jobs A and B. Each job needs both units

during some phase of processing. Job A is assigned unit 1. If job B were assigned unit 2,

neither A nor B could complete until the other job relinquishes its assigned unit.

To prevent deadlocks from occurring, the system requires that a RESOURC command be included

in any job that uses more than one tape or disk pack concurrently. Thus, in the previous

example, a RESOURC command is required in both jobs. The information supplied by the

commands enables the system to anticipate the deadlock situation and roll out job B until

job A no longer needs both units. When the RESOURC command is executed, the system ﬁrst

checks if the speciﬁed number of units exceeds the number of units you are authorized to

use or the numb er of un it s avai lab le at t he ins tal la tio n.t If e it her of t hes e sit uat ion s

occurs, the system issues an error message to your dayﬁle and aborts the job. (Refer to

ﬁgure 7-4.)

;*&%.

TFor jobs that use only one tape or pack at a time and do not contain a RESOURC command, /tgs^

the system checks validation limits when the request is made. ^

7-52 60459680 D

/gites,

r

Figure 7-4. Resource Commitment Processing (Simpliﬁed)

When the job requests a tape or pack,t the system compares the number of units that jobs

being processed have scheduled via RESOURC commands with the number of units actually

assigned. If it determines that the assignment would cause a deadlock (refer to Resource

Overcommitment), it rolls out the job until a deadlock would not occur. If the assignment

would not cause a deadlock, the system searches for the requested tape or pack. If found,

it is assigned to the requesting job. If the pack is not found and the NA keyword was

included in the request or if the tape is not found, the requesting job is rolled out until

the operator makes the pack or tape available.

tRefer to Permanent File Commands in section 9 for a description of disk pack requests

and to Tape Management Commands in section 12 for a description of tape requests.

60459680 D 7-53

SINGLE RESOURCE USE

A job that uses only one tape or disk pack concurrently does not need to specify resource

demand with a RESOURC command. However, before assigning the same or a different type of

resource, the current single resource (tape or disk pack) must be returned with either the

RETURN or UNLOAD command. To allow more ﬂexible resource handling, both the RETURN and

UNLOAD functions decrement the default resource demand count from one to zero for jobs

requiring only one tape or disk pack concurrently. For those jobs requiring more than one

tape or disk pack concurrently (as speciﬁed by the RESOURC command), UNLOAD does not

decrement the resource demand count; RETURN decrements the resource demand count only when

all concurrent resource demands have been satisﬁed.

TAPE UNITS

The system supports nine-track magnetic tapes in three different densities. In system -^^

commands, you use a 2-character density resource identiﬁer to specify the correct density.

The identiﬁers are as follows:

Identiﬁer Density

H D 8 0 0 c p i

PE 1600 cpi

GE 6250 cpi

The 679-2/3/4 tape units are capable of processing both 800-cpi and 1600-cpi nine-track

tapes; the 679-5/6/7 tape units handle both 1600-cpi and 6250-cpi nine-track tapes. An .^^\

800-cpi nine-track tape cannot be processed on a 1600/6250-cpi unit, and 6250-cpi nine-track '

tape cannot be processed on an 800/1600-cpi unit. The NT resource identiﬁer, retained for

compatibility, can be used only to allocate 800/1600-cpi nine-track units} and cannot be

speciﬁed concurrently in the same job with HD, PE, and GE resource demands. Default

nine-track resource allocation is by density.

Examples:

Assume that an installation has the following tape drive resources:

• Two 679-4 nine-track tape drives (800/1600-cpi densities).

• Two 679-7 nine-track tape drives (1600/6250-cpi densities).

1. If a job makes a tape unit resource request with

RESOURC,NT=3.

the job is aborted with the message

INSUFFICIENT RESOURCES ON SYSTEM,

because only two units (the 679-4s) meet the NT speciﬁcation.

tNT resource demand cannot exceed the number of 800/1600-cpi nine-track drives at the

installation. However, at tape assignment time, a 1600-cpi tape mounted on a 1600/6250-cpi

unit is accepted for NT resource demand if it does not cause overcommitment (potential

deadlock).

7-54 60459680 D

2. If a job makes a tape unit resource request with

RESOURC,NT=1,PE=1.

the job is aborted with the message

CONFLICTING RESOURCE TYPES.

because the NT speciﬁcation cannot be used with a density speciﬁcation

(HD/PE/GE).

3. If a job contains the following commands

LABEL,TAPE,NT,D°PE,VSN=TAPE1.

RESOURC,NT=2.

the job is aborted with the message

CONFLICTING RESOURCE TYPES.

because the LABEL command requested a tape unit by density (the default);

therefore, later commands cannot schedule tape units using the NT speciﬁcation.

Density identiﬁers are provided for seven-track tape units even though these units do not

have alternate densities. This is done for consistency of format. The LO, HI, HY, and MT

resource identiﬁers are all equivalent, and the last speciﬁcation of any one of these is

the seven-track tape unit demand for the job. For example, the resource request

RES0URC(HI=1,HY=2) results in two seven-track tape resources being allocated for the job.

RESOURCE OVERCOMMITMENT

Under certain conditions, the system overcommits resources, provided all jobs with currently

assigned resources can complete. For example, an installation with three tape units is

processing jobs A and B. Included in each job is a RESOURC command scheduling two units.

Job A requests its ﬁrst tape. It is assigned the tape (unit 1) because there are enough

un it s av ai la ble fo r jo b A t o com pl et e. J ob B re qu es ts i ts ﬁ rs t ta pe . It is as si gned t he

tape (unit 2) because either A or B can complete if assigned the last unit, and when the job

that is assigned the last unit completes, the other can then use that unit and also

complete. Job B then requests and is assigned its second tape (unit 3). It completes its

operations (that is, terminates or returns the ﬁles on the tape) and makes the unit

available for job A to complete.

NOTE

In a multimainframe environment, only the

conﬁguration of the machine on which the

job is processed is considered in the

overcommitment algorithm.

60459680 D 7-55

/c^'cSK

ALTERING RESOURCE REQUIREMENTS

The system manages its resources by keeping totals of the number of units of each device

type scheduled and assigned to jobs. The number of units scheduled and the number of units

assigned to a job can vary during job processing.

To change the number of units of a device type scheduled for this job, you can issue another

RESOURC command. When decreasing the number of units scheduled for the job via a RESOURC

command, the total resulting scheduled units must not be less than the number of units

currently assigned to the job. If the resulting total would be less than the number

currently assigned, the system aborts the job with an error message.

If the job has tape and/or removable pack units assigned to it when it attempts to increase

its resource demands, the system determines if the request would cause a deadlock. If it

would, it aborts the job with an error message.

NOTE

Always return all units assigned to your

job before issuing another RESOURC command

to increase resource demands. This action

prevents a possible job abort caused by a

potential deadlock condition.

The scheduled units can also be decreased by a RETURN command if the job, at the time of the ^

return, is using its maximum scheduled units (refer to the description of the RETURN command

in section 9).

Example:

The ﬁrst RESOURC command schedules two 800-cpi, nine-track tape units. The two LABEL

commands assign the tape units to the job. Because the maximum scheduled units were used

concurrently, the RETURN command decreases the scheduled tape units to zero. The second

RESOURC command schedules two 844-21 disk units and one 800-cpi, nine-track tape unit.

SAMSJOB,CM50000,T40.

USER,SJGREEN,WGT.

CHARGE,*.

RES0URC,HD=2.

LABEL,X,D=HD,VSN=TAPE1.

LABEL,Y,D=HD,VSN=TAPE2.

RETURN,X,Y.

RESOURC, DI1=2,HD=1.

-EOI-

**^^V

7-56 60459680 D

UNIT ASSIGNMENT

The method of assigning units depends on the resource type. For example, all tapes and all

private disk packs not accessible by alternate users can only be assigned to one job at a

time. All public packs and those private packs accessible by alternate users are shareable,

and therefore, can be assigned to several jobs at the same time.

On indirect access ﬁle requests, the pack is charged to the job in fulﬁlling its resource

demand only if the request causes the pack to be mounted. For direct access ﬁle requests,

the pack is charged to the job when the ﬁrst ATTACH of a direct access ﬁle is made.

A unit is assigned to a job until the job terminates or all direct access ﬁles residing on

the unit that are assigned to the job are returned. At this point, a tape or a nonshareable

pack can be dismounted. A shareable pack, however, can be dismounted only when there are no

ﬁles residing on the unit that are assigned to any of the jobs sharing the pack.

NOTE

In GET requests for indirect access ﬁles,

a pack is assigned to a job only as long as

the pack is actually being used (that is,

until the system retrieves the local copy

of the ﬁle). Therefore, during a series

of GET requests, the operator may determine

that the pack is not being used and dis

mount it. If you have a direct access ﬁle

on the pack, you can avoid this situation

by attaching the direct access ﬁle before

issuing the GET requests.

A single job cannot have more than 36 removable pack devices attached to the job

concurrently.

RFL COMMAND

The RFL command sets the initial running ﬁeld length for each subsequent job step when

neither the routine for processing that step nor a loader table speciﬁes a ﬁeld length

(refer to Field Length Control in section 3).

Format:

RFL,CM=nnnnnn,EC=mmmm.

or

RFL,nnnnnn,mmmm.

Parameter Description

CM=nnnnnn Speciﬁes the central memory ﬁeld length (octal is assumed unless

decimal is speciﬁed by a D sufﬁx or use of the digits 8 or 9). The

value is rounded up to the nearest multiple of 100g.

Specifying nnnnnn as 0 removes the effect of the previous RFL command

and returns the setting of the ﬁeld length to system control.

EC=mmmm Speciﬁes the extended memory ﬁeld length in octal. The value of

mmmm is the actual extended memory divided by lOOOg.

60459680 D 7-57

The parameters may be speciﬁed positionally, by keyword, or intermixed positionally and by

keyw ord . If i nte rmi xed , the positional pa ram ete rs are evaluated ac cor din g to t heir po sit ion

among all the parameters.

The values of nnnnnn or mmmm cannot exceed the values speciﬁed on the last MFL command or

the maximum allowed for the job.

Prior to the appearance of the RFL command (or SETRFL macro), the system determines the

ﬁeld length for each job step, provided no ﬁeld length is speciﬁed by a system routine or

loader table (refer to Field Length Control in section 3).

ROLLOUT COMMAND

The ROLLOUT command suspends job execution and places the job in the rollout state. This

releases the control point, central memory, and extended memory assigned to the job. You

can specify a time period that must elapse before the job is returned. Otherwise, the job

scheduler usually returns the job to execution when its priority is the highest of the jobs

rolled out (refer to Rollout Control in section 3).

Format:

ROLLOUT,t.

Parameter Description

t Optional time delay measured in job scheduler delay intervals. Values "y,

for t range from 0 to 262080 (777700g) intervals. Although the

default base is decimal, octal values can be speciﬁed by a B sufﬁx.

Typically, a job scheduler delay interval is one second but can be site-determined.

RTIME COMMAND

The RTIME command requests that the time be read from the real-time clock and issued to the

dayﬁle (in seconds). This is the accumulated time since the last system deadstart. ."**%

Format:

RTIME.

The dayﬁle message format is:

RTIME nnnnnn.nnn SECS.

| 7-58 60459680 D

SETASL COMMAND

The SETASL command sets the system resource unit (SRU) limit for an account block. An

account block is the job step sequence whose execution is charged to an account (refer to

SRU Limit Control in section 3). The account is speciﬁed by the charge and project numbers

on a CHARGE command, or if no CHARGE command is required, by the user name on the USER

command. Each user name and each account has an SRU validation limit (refer to the LIMITS

and ENQUIRE commands). Except for interactive jobs, the default account block SRU limit

(set during CHARGE or USER command processing) is the smaller of the user name and the

account validation limits. For interactive jobs, the default limit is 64 SRUs.

Format:

SETASL,s.

Parameter Description

s Maximum number of SRUs allowed for account block execution. Although

the default base is decimal, octal values can be speciﬁed by a B sufﬁx

on the value.

s must be greater than or equal to the current job step SRU limit* and

less than or equal to the SRU limit associated with your user name.

Exceptions to this rule are the asterisk (*) and a value of 32760

(77770B) or greater. These exceptions set the account block SRU limit

to the validation limit.

If the account block SRU limit is reached during account block execution, the system issues

an error message and terminates the job (refer to Exit Processing in section 5).

tThe job step SRU limit must be lowered in the job before the account block SRU limit is

lowered. Refer to the SETJSL command in this section.

60459680 H 7-59

SETCORE COMMAND

The SETCORE command presets each word within the ﬁeld length except for RA+2.

Format:

SETCORE,p.

or

SETCORE,-p.

Parameter Descripton

p Any of the following: (If a minus sign precedes the parameter p, the

complement of p is set in core.)

P

0

ZERO

INDEF

INF

Fill Characters

0

Zeros (0)

Indeﬁnite (1777 0000 0000 0000 0000)

Inﬁnite (3777 0000 0000 0000 0000)

Each word within the ﬁeld length (except for RA+2) is set to p. If p is omitted, the

system assumes p=0.

Calling the CYBER loader destroys the effect of a SETCORE command since the loader uses

memory as a work area.

To preset memory within a load sequence, use a LDSET,PRESET command as described in the

CYBER Loader Reference Manual.

/**^s.

^■S\

y^>v

7-60 60459680 F

SETJAL COMMAND

The SETJAL command changes the security access level of the current job. Initially, your

job has the lowest possible access level that is valid for your job (ENQUIRE,B returns this

information). Refer to Security Features in Section 3 for a detailed discussion of access

levels•

Format:

SETJAL,AL=level.

Parameter Description

AL=level Speciﬁes the security access level you want assigned to the job.

Unless changed by your site, level can be one of the following names:

LVLO, LVLl, LVL2, LVL3, LVL4, LVL5, LVL6, or LVL7

On a secured system, the access level you specify must be valid for the job. In addition,

to lower the access level of your job, you must be authorized to do so (refer to the LIMITS

command).

On an unsecured system, the command has no effect. The system does, however, check for

valid p ar ame te r sp eci ﬁc at io ns .

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

UJN=ujn

DC=dc

OP=op

Description

Changes the job's default UJN to ujn. A UJN must be seven or less

alphanumeric characters. For interactive jobs, the default is the

user index hash (refer to the ENQUIRE command). Otherwise, the

default is the UJN speciﬁed on the Job command.

Speciﬁes 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 Speciﬁes 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.

Speciﬁes 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 speciﬁed by a B sufﬁx on

the value. The value s must be greater than 0 and less than or equal to

the current account block SRU limit, and the SRU limit associated with

your user name. Exceptions to this rule are the asterisk (*) and values

greater than 32760 (77770B). These values set the job step SRU limit at

the validation limit if the account block SRU limit is set at the

validation limit.

The system issues an error message when the job step SRU limit is reached. A job step

within a batc h jo b is then termina ted (re fer to Exit Process ing in sect ion 5). In

interactive jobs, you can increment the SRU limit after receiving the SRU limit message or

terminate the job. If the job is suspended because a job step or the job itself exceeded

its SRU limit, the message

*SRU LIMIT*

ENTER S TO CONTINUE OR STOP TO END JOB STEP.

TYPED AHEAD INPUT MUST BE REENTERED.

is issued. You can enter one of the following:

Entry

S,nnnnn

Description

Increases the SRU limit by 64 units. Job execution continues. The

64-unit increment can be changed by your site.

Increases the SRU limit by nnnnn decimal units. Job execution

continues. You can enter octal units by specifying a B after the octal

number.

S,; Increases the SRU limit to your maximum. Job execution continues.

STOP Terminates the job step. Subsequent commands, if any, are not processed,

Any increase to the SRU limit through either S or S,nnnn is in effect only for the current

job step. When the job step terminates, the account block SRU limit and job step SRU limit

revert to their original values, set by default or by the SETASL and SETJSL commands,

respectively. Entering S,* in response to an SRU LIMIT message could cause the interactive

session in progress to exceed the account block SRU limit set by the SETASL command or by

default. The system then issues an SRU LIMIT message after a job step has begun. To remedy

this situation, use the SETASL command to raise the account block SRU limit above the

current number of accumulated SRUs for the interactive session.

60459680 H 7-63

^%\

The account block SRU limit must be raised before the job step SRU limit can be raised.

Refer to the SETASL command in this section. When a limit occurs, any typed ahead input

will be discarded since it would be processed as a response to the limit message.

SETPR COMMAND

The SETPR command decreases the CPU priority of a job. A user job cannot increase its

priority.

SETPR,p.

Parameter Description

p Speciﬁes the priority, 1 < p < 70g. "^)

Upon job initiation, a job is assigned the maximum priority allowed for its service class.

(The installation deﬁnes these priority values.) If a job's CPU priority is lower than

that of other jobs, the job is assigned control of the CPU only when jobs of a higher

priority do not need it.

SETTL COMMAND

The SETTL command sets the CPU time limit for each subsequent job step. Each user name is ^*^\

validated for a maximum job step time limit (refer to the LIMITS and ENQUIRE commands).

When you do not specify a time limit, the system sets the limit at 64 CPU seconds.t

Interactive jobs can increment their job step time limit to complete job step execution

(refer to Section 8).

Format:

SETTL,t.

Parameter Description

t Maximum number of CPU seconds allowed for job step execution. Although

the default base is decimal, octal values can be speciﬁed by a B sufﬁx

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,nnn nn Increa se s the cent ra l proc essor time l imit b y nnnn n deci ma l se co nds.

Job execution continues. You can enter octal seconds by specifying a B

after the number.

T » * I n c r e a s e s t h e c e n t r a l p r o c e s s o r t i m e l i m i t t o y o u r m a x i m u m . J o b

execution continues.

Causes the job to go through normal abort procedures (for example, EXIT

processing which can be useful when using procedure ﬁles).

STOP Terminates the job step. Subsequent commands, if any, are not processed.

Any increase to the central processor time limit through either T or T,nnnn is in effect

only for the current job step. When the job step terminates, the central processor time

limit reverts to its original value, previously set by default or by the SETTL command.

When a limit occurs, any typed ahead input will be discarded since it would be processed as

a response to the limit message.

In the following example, a program exceeds its allocated time limit. The user enters T to

increase the time limit and the program then runs to completion.

List

00100 PROGRAM T

00110 DO 6 1=1,2500

00120 DO 6 J=1,4000

00130 A=1

00140 6 CONTINUE

00150 END

READY.

set t l,,10

READY.

run

*TIME LIMIT*

ENTER T TO CONTINUE OR STOP TO END JOB STEP.

TYPED AHEAD INPUT MUST BE REENTERED.

t

SRU 66.835 UNTS.

RUN COMPLETE.

60459680 H 7-65

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 redeﬁnes 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 deﬁning an alternate command or series of commands to be executed

whenever the user enters the original command. For example, you could redeﬁne a

user's ATTACH command to execute both an ATTACH and a LIBRARY command for the

speciﬁed ﬁle, thus making the ﬁle 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-deﬁned 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 Speciﬁes the shell program name to be executed.

Pi Speciﬁes 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 ﬁle loading of the shell program. When

loading the program from a local ﬁle, the program must be ^

s t o r e d i n A B S - t y p e r e c o r d s . ( R e f e r t o s e c t i o n 1 5 f o r a ^ ^ %

description of record types.)

7-66 60459680 D

/i|f«£-\

G A l l o w s g l o b a l l i b r a r y l o a d o f t h e s h e l l p r o g r a m .

S Allows system library load of the shell program.

T Speciﬁes that the system monitor commands directly from the

terminal.

B Speciﬁes that the system monitor commands outside

procedures.

C Speciﬁes that the system monitor commands inside procedures.

The ﬁrst format disables shell control.

The second format, specifying only the shell program name, sets the default for pi as A,

S, and B.

The last format speciﬁes 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

dayﬁle.

Format:

STIME.

Dayﬁle message format:

STIME nnnnnn.nnn UNTS.

60459680 D 7-67

SUBMIT COMMAND

The SUBMIT command places a user-supplied job ﬁle into the input queue as a separate job.

SUBMIT can reformat the ﬁle according to directives within the ﬁle. Refer to Job Names in

section 3 for a description of the names associated with the submitted job.

Format:

SUBMIT,Ifn,q,NR.c

Parameter Description

lfn Speciﬁes the name of the ﬁle to be submitted to the system for

processing as a batch job. The ﬁrst record of the ﬁle must be in

6-bit display code. The default is the job's primary ﬁle.

q Spec iﬁes dispositio n of j ob output (OU TPUT, PUNCH, PUNCHB, and P8) as

follows:

BC or B Use the default processing for local batch jobs to

dispose of job output at the central site.

NO or N Discard job output at job termination unless the ﬁles

have been explicitly routed (default value for

interactive origin jobs). The dayﬁle is not written to

ﬁle OUTPUT.

RB=un or Route job output to the remote batch or interactive

E=un user speciﬁed by the user name un. The default for un

is the user name associated with the submitting job.

TO J ob ou tpu t (i ncl ud in g t he da yﬁl e) is q ue ue d w it h a w ai t

disposition.

N R N o r ew i nd opt i on ; t h e s ub m it ﬁ le and t he ﬁ le s pe c iﬁe d o n a c RE A D

reformatting directive are not rewound before or after processing. If

NR is omitted, the ﬁles are rewound before, but not after processing.

c P r e ﬁ 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 ﬁ 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 dayﬁle, and the SUBMIT command is

not processed.

For SUBMIT to process reformatting directives, the ﬁrst line of the submit ﬁle must be a

cJOB directive. Each line preceded by a preﬁx character is recognized as a reformatting

directive. The preﬁx character is speciﬁed on the SUBMIT command (/ by default).

Throughout this description, the letter c, preceding a directive, denotes the preﬁx

character. Reformatting directives may be interspersed throughout the submit ﬁle 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 ﬁle (refer to description of TRANS and NOTRANS directives).

7"68 60459680 E

The system does not process reformatting directives unless the ﬁrst line of the submit ﬁle

contains the cJOB directive. Other directives can follow the cJOB directive (that is, they

can precede the job and/or USER commands), but the ﬁrst two commands following the cJOB

directive must be a Job command and a USER command, respectively. The USER command can be

inserted in the form of a cUSER directive. For example, the following sequences of lines

are both valid:

lnj cJOB

ln2 ujn,parameters.

ln^ USER,username,password, (or cUSER)

or

lnj cJOB

ln2 cNOSEQ

ln3

ln4

ujn,parameters.

USER,username,password, (or cUSER)

lnj, ln2, ln3, and ln^ are optional line numbers.

You can include line numbers on the submit ﬁle and specify which line numbers are to be

removed during reformatting with the cSEQ and cNOSEQ directives. This is especially useful

if the submit ﬁle contains a BASIC program where line numbers are a requirement of the

language. If line numbers are included in a submit ﬁle, the ﬁle must begin with a cJOB

directive.

The reformatting directives available are described as follows:

Directive

cJOB

cUSER

cCHARGE

Description

Indicates that the submit ﬁle is to be reformatted and selects the

following default reformatting directives. The default directives

re main in eff ect unt il s pe ciﬁ ed o ther wise .

cNOTRANS (disabled by cTRANS)

cSEQ (disabled by cNOSEQ)

cPACK (disabled by cNOPACK)

Th e cJ OB d ir ectiv e mu st be th e ﬁr st l in e of th e su bm it ﬁ le. If

omitted, the ﬁle is not reformatted. If line numbers are included in a

submit ﬁle, the ﬁle must begin with a cJOB directive.

Inserts a USER command identical to that of the submitting job during

reformatting. SUBMIT does not insert a password in the new USER

command. Hence, you cannot use the cUSER directive when routing jobs to

remote hosts (ST=lid parameter of the Job command) that do not support

NOS 2 security features. Further, you can only use this directive to

create the ﬁrst USER command in a job.

Inserts a CHARGE command that is identical to the CHARGE command

currently in effect for the submitting job. If no CHARGE command is in

effect for the submitting job, this directive has no effect on the

SUBMIT ﬁle.

60459680 E 7-69

Directive Description

c E O R I n d i c a t e s t h a t a n e n d - o f - r e c o r d m a r k i s t o b e p l a c e d a t t h i s p o i n t i n

the submit ﬁle during reformatting.

cEOF Indicates that an end-of-ﬁle mark is to be placed at this point in

the submit ﬁle during reformatting.

c S E Q I n d i c a t e s t h a t t h e f o l l o w i n g l i n e s m a y b e p r e c e d e d b y l i n e n u m b e r s a n d

requests that they be removed (default value).

cNOSEQ Reverses the effect of the cSEQ directive. No attempt is made to

remove leading line numbers from subsequent lines. This is especially

useful when line numbers are required (such as in a BASIC program).

cPACK Requests that all succeeding end-of-record and end-of-ﬁle marks be ^

removed (default value). This directive applies only to internal EOR

and EOF marks that currently exist. The cEOR and cEOF reformatting

directives are not affected.

cNOPACK Reverses the effect of the cPACK directive. Requests the system not

to discard succeeding internal end-of-record and end-of-ﬁle marks

that currently exist.

cTRANS Requests transparent submit mode. In transparent submit mode, SUBMIT

ignores reformatting directives until an EOR or EOF mark is

encountered. The EOR or EOF mark cannot be a mark to be created by a ^^^

cEOR or cEOF directive. SUBMIT performs the following procedure for

transparent submit mode processing.

1. Read cTRANS directive.

2. Check if the next line is a reformatting directive. If it is not,

skip steps 3 and 4.

3. Process reformatting directive. If it is a cNOTRANS directive,

end transparent submit mode processing.

4 . R e t u r n t o s t e p 2 . )

5. Select transparent submit mode and read lines until an internal

EOR or EOF mark is encountered.

6. If the cPACK directive is in effect, remove the EOR or EOF mark.

7. Return to step 2.

7-70 60459680 G

Directive Description

The cTRANS directive is typically used in conjunction with the cREAD

directive. The cREAD directive copies the contents of an existing

ﬁle into the submit ﬁle at the location of the cREAD directive.

Because the ﬁle 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 ﬁrst 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 ﬁle or the ﬁle being read

(cREAD) while transparent submit mode is in effect. However, the

cPACK or cNOPACK directive in effect before transparent submit mode

was selected remains in effect after it is selected.

cNOTRANS Reverses the effect of the cTRANS directive and informs the system

th at th e sub mit ﬁl e is t o be e xa min ed o n a li ne -by -li ne b as is. Al l

directives encountered in the submit ﬁle while the cNOTRANS directive

is in effect are processed. This directive is initially selected by

default and remains in effect until a cTRANS directive is encountered

in the submit ﬁle.

/SP^N

Be careful in placing this directive in the submit ﬁle. If

transparent submit mode is selected, this directive can possibly be

ignored unless it immediately follows either a cREAD directive or an

internal EOR or EOF mark.

cREAD.lfn Requests that the system read the contents of the speciﬁed ﬁle, lfn,

and insert that ﬁle in place of the cREAD directive in the submit

ﬁle, during reformatting. Reading terminates when an EOF or EOI is

encountered on lfn. If the ﬁle to be read is not currently local to

the job, the system automatically attempts a GET and then an ATTACH on

the ﬁle. If lfn is not speciﬁed in the directive, TAPE1 is

ass umed . If th e ﬁle spe ci ﬁe d canno t be fo un d or th e rea d ﬁle i s

found to be busy (direct access ﬁles only), the job is terminated.

The ﬁle speciﬁed by lfn in the cREAD directive is automatically

rewound before the read operation unless the NR parameter is speciﬁed

on the SUBMIT command. In this case, the rewind directive must

precede the cREAD directive in the submit ﬁle if it is desired to

rewind ﬁle lfn before the read operation begins. The system returns

all ﬁles speciﬁed in cREAD directives before completion of the job.

If the cPACK directive is in effect when the ﬁle lfn is read, all

internal EOR marks are removed. If the cNOPACK directive is in

effect, all internal EOR marks are read into the submit ﬁle in the

proper position during reformatting.

60459680 D 7 -71 |

Directive Description

Unless transparent submit mode is in effect when ﬁle lfn is read,

each line of that ﬁle is also checked for a reformatting directive.

Any directives contained in the ﬁle, 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 ﬁle being read, unless transparent submit mode is

selected. Then, only the cPACK or cNOPACK directive remains in effect

fo r the ﬁl e bei ng r ea d. M or eov er, on ly t ho se d ir ect ive s that

immediately follow an internal EOR in the ﬁle being read are

processed.

If the ﬁle to be read is a binary ﬁle, 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 ﬁle, if used.

cREWIND,lfn Requests that the system rewind ﬁle lfn to the beginning-of-

information (BOI). If lfn is not supplied, TAPE1 is assumed. This

directive is required only if the NR parameter is included in the

SUBMIT command. Otherwise, ﬁle lfn is automatically rewound.

This directive is used in conjunction with the cREAD directive. Thus,

if it is desired to rewind a ﬁle before the read operation begins,

this directive must precede the cREAD directive in the submit ﬁle.

cjEC=c2 Indicates that the preﬁx character is to be changed from c^ j

(current preﬁx character) to c2 (new pre ﬁx ch aracter). The new

preﬁx character code is used to recognize all subsequent reformatting

directives until further changed.

Input lines must not exceed 150 6-bit characters. SUBMIT processes the ﬁrst 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 ﬂ 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 dayﬁle to determine the cause of any errors that occurred during job

processing. The dayﬁle for the submitted job is disposed according to the disposition

parameter on the SUBMIT command.

When you submit a batch job from an interactive job, all output is dropped (unless requested

otherwise by the disposition parameter). This includes the dayﬁle output. Therefore, make

provisions within your job to save the contents of the dayﬁle if a processing error

occurs. You can do this by including the following commands at the end of the command

record.

EXIT.

- DAY FILE ,l fn.

REPLACE,lfn.

7-72 60459680 D

SWITCH COMMAND

The SWITCH command sets the sense switches for reference by one of your programs.

Format:

SWITCH,switchj,switch2,...,switchn,jsn.

Parameter Description

switch^ Speciﬁes the switch(es) to be set. You must denote each switch

switch^ by an integer in the range of 1 through 6. If you specify 0

for this parameter, the system sets all sense switches.

jsn Speciﬁes the job sequence name (JSN) of the job whose sense switches

will be changed, jsn is an optional parameter, its default is the

current job. The system recognizes the jsn parameter by its alphabetic

characters; therefore, jsn can appear anywhere in the parameter list and

can be omitted without leaving a blank parameter ﬁeld.

UPROC COMMAND

The UPROC command speciﬁes a user prologue, a program the system executes each time you

start a job.

Format:

UPROC,FN=pﬁle.

UPROC,pﬁle.

Parameter Description

pﬁle One of your permanent ﬁles that contains the desired prologue. If

pﬁle contains more than one procedure, the system executes only the

ﬁrst one. If you omit the FN=pﬁle parameter or give pﬁle the value

of zero, the system will no longer execute a user prologue.

The system executes your user prologue only after it processes your user validation and

charge information but before it initiates job recovery processing. Depending on the length

and nature of your user prologue, you may want to initiate recovery processing before your

user prologue ends. For example, if your user prologue aborts, the system does not initiate

recovery processing. To do this, place the RECOVER command within your user prologue (refer

to section 8 for the RECOVER command and section 4 for the writing of procedures).

60459680 H 7-73

USECPU COMMAND

The USECPU command speciﬁes which central processor is to be used when more than one is

available for processing.

Format:

USECPU,n.

Parameter Description

n Speciﬁes which central processor to use.

Jft Description

0 Use either central processor.

1 U s e C P U 0 .

2 U s e C P U 1 .

The USECPU command may be used only when the system is running on a model 72-2x, 73-2x,

74-2x, 174, 720-2, 730-2, 6500, 6700, 830-2, 865-2, or 875-2. On a model 74-2x or 6700, CPU

0 is the parallel processor, and CPU 1 is the serial processor. On the other systems, both

CPUs are serial processors. This command is ignored on single CPU machines.

USER COMMAND

The system uses the parameters on the USER command to determine if you are an authorized

user, which resources you are validated to.use, and the extent (limits) to which you may use

those resources.

No commands are allowed between the Job and USER commands in noninteractive jobs. If this

is attempted, the ﬁrst command is interpreted as an invalid USER command, and the submitting

job is aborted with appropriate messages to the dayﬁle. The submitted job is dropped.

Format:

USER,username,password,familyname.

Parameter Description

username Speciﬁes a one- to seven-character alphanumeric user name.

password

familyname

Speciﬁes an alphanumeric password. Its maximum length is seven

characters; its minimum length is deﬁned by the installation.

Speciﬁes an optional parameter identifying the familytof permanent ﬁle

devices on which your permanent ﬁles reside. Specify a family name

when the system can access more than one permanent ﬁle device family.

If this is not the ﬁrst USER command of the job or it is the ﬁrst 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 ﬁle device families,

| 7-74

'-^\

60459680 H

This command also deﬁnes controls and validation limits for the job and deﬁnes your

permanent ﬁle 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

ﬁle catalog or family during job processing by issuing another USER command. The system

only associates permanent ﬁle validation limits with this new user name. The remaining

v al i d at i o n l imi t s s til l r e ﬂec t t h o se o f t h e u ser n ame s pe c i ﬁe d a t j ob i n it i a ti o n ( r ef e r t o

the LIMITS command earlier in this section).

On a secured system or on an unsecured system with secondary USER commands enabled, an

invalid USER command is processed as a security conﬂict. 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 dayﬁle messages issued to the terminal. If the security count is not zero, the job

rstep is aborted with appropriate messages to the terminal and the dayﬁle and with EXIT

processing enabled (unless explicitly disabled).

On an unsecured system with secondary USER commands disabled, any secondary USER command

will be invalid and aborts the job. This is not a security conﬂict and the security count

is not decremented.

The password is deleted from the USER command before this command is issued to the dayﬁle.

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 ﬁle family is moved to a backup system. If, after the ﬁrst USER command, you do

not specify a familyname on the USER command, your permanent ﬁle family remains the same.

If you specify the 0 (zero) familyname, your permanent ﬁle family becomes the system

default family.

Example:

An installation has two systems, A and B. System B provides backup service for system A.

The system default family name for system A is AFAM, and the system default family name for

system B is BFAM.

During normal operations, system A user CWJONES with password JPWD could enter either of the

following USER commands.

USER,CWJONES,JPWD.

USER,CWJONES,JPWD,AFAM.

System B user JDSMITH with password SPWD could enter either of the following commands.

USER,JDSMITH,SPWD.

USER,JDSMITH,SPWD,BFAM.

If system A failed, user CWJONES would be required to enter

USER, CWJONES, JPWD, AFAM .

to identify his family of permanent ﬁle 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 ﬁle family is moved to a backup system. If, after the ﬁrst USER command, you do

not specify a familyname on the USER command, your permanent ﬁle family remains the same.

If you specify the 0 (zero) familyname, your permanent ﬁle family becomes the system

default family.

Example:

An installation has two systems, A and B. System B provides backup service for system A.

The system default family name for system A is AFAM, and the system default family name for

system B is BFAM.

During normal operations, system A user CWJONES with password JPWD could enter either of the

following USER commands.

USER,CWJONES,JPWD.

USER,CWJONES,JPWD,AFAM.

System B user JDSMITH with password SPWD could enter either of the following commands.

USER,JDSMITH,SPWD.

USER, JDSMITH, SPWD, BFAM.

If system A failed, user CWJONES would be required to enter

USER,CWJONES,JPWD,AFAM.

to identify his family of permanent ﬁle devices. User JDSMITH could enter either of the

USER commands as before because the default family name would still be valid.

7-76 60459680 D

■^5v

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 speciﬁed otherwise, these commands cannot

be used in procedures. This section describes these commands under the following headings:

Terminal Control Commands

ASCII LINE

AUTO NORMAL

BRIEF SCREEN

CSET TDU

EFFECT TIMEOUT

KEY TRMDEF

• Subsystem Selection Commands

ACCESS FORTRAN

BASIC FTNTS

BATCH NULL

EXECUTE

• Interactive Status Commands

ctD

ctE

ctS

• Job Processing Commands

0^\

APPSW LOGOUT

BYE NOSORT

DIAL RECOVER

EXPLAIN REDO

GOODBYE RUN

HELLO Secure Login

HELL07 SHOW

HELP TEXT

HELPME WHATJSN

LIB

LIST XMODEM

LOGIN

Primary File Editing Commands

ALTER

DELETE

DUP

LIST

MOVE

READ

RESEQ

WRITE

WRITEN

60459680 G 8-1

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 deﬁned 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 ﬁrst 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

yﬂ^Stey

AUTO COMMAND

The AUTO command automatically generates ﬁve-digit line numbers.

Format:

AUTO,nnnnn,iiii

Parameter

iiii

Description

Speciﬁes the beginning line number; default value is 00100.

Speciﬁes 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 ﬁle, the original contents of that line are lost and must be reentered. The

increment value cannot be altered unless a new AUTO command is entered.

In the following example of the AUTO command, the user deletes a line number to change the

numbering sequence and then deletes another line number in order to place a character in

column 6.

READY,

auto

00100 program header

00110 write 1000

00120

•DEL*

00230 1000 format(15x,' headings')

00240 write 2000

00250 2000 formatd5x,'author',9x,'title',15x,

00260

*DEL*

00260+ 'publisher'^,'cost')

00270 stop

00280 end

00290

•DEL*

List

00100 PROGRAM HEADER

00110 WRITE 1000

00230 1000 FORMAT(15X,'HEADINGS')

00240 WRITE 2000

00250 2000 FORMAT (15X,'AlfTH0R',9X,'TITLE',15X,

00260+ 'PUBLISHER',6X,'C0ST')

00270 STOP

00280 END

READY.

User enters cancel line character.

User enters entire line.

User enters cancel line character.

User completes the line.

User enters cancel line character.

60459680 C 8-3

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 ﬁle when using the primary ﬁle 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 Speciﬁes 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 ﬁle.

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 ﬁrst character of each output line; the system interprets the ﬁrst character of

each line as an effector and inhibits printing of the character.

Format effectors control carriage positioning on output operations. The effectors for

speciﬁc 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

Speciﬁes whether or not IAF automatically supplies format effectors.

Values that can be entered for mode are as follows:

Value Description

SYSTEM Format effectors are supplied by IAF. This is the default |

value.

U S E R F o r m a t e f f e c t o r s a r e u s e r -su p p l i e d a s t h e ﬁ r s t c h a r a c t e r |

of each output line.

When format effectors are user-supplied (i.e., EFFECT,USER |

is speciﬁed), all format effectors are supported except

those that specify carriage positioning after output.

Speciﬁcally, the slant (/) and period (.) effectors are

not supported.

You can include this command in a procedure.

KEY COMMAND

The KEY command maintains key deﬁnition ﬁles which deﬁne the function keys for a CDC 721

terminal. KEY is used to create, edit, display, or load a deﬁnition ﬁle.

The KEY command is valid only for a CDC 721 terminal operating in screen mode. To use this

command, select the appropriate option from those listed below and enter the command with

that option. The KEY command provides you with interactive help to assist you in creating,

editing, or loading the deﬁnition ﬁle.

Format:

KEY,option,ﬁlename.

or

KEY?

/jfp&V,

60459680 H 8-5

Parameter

option

Description

Any of the following options.

Opti on Description

HELP Gives a brief description of each option available. The

ﬁlename parameter is ignored.

CHECK Checks to see if function key deﬁnitions are already

loaded into the terminal. If not, the deﬁnitions in ﬁle

ﬁlename are loaded.

DEFAULT Sets key deﬁnitions to the NOS system default keys. The

ﬁlename parameter is ignored. The default keys are:

HELP key = HELP

EDIT key = FSE

STOP key = CTRL-T followed by carriage return

DISPLAY Displays the key labels for function keys Fl through F16.

EDIT Initiates creation or editing of a key deﬁnition ﬁle.

KEY ﬁrst searches for a local ﬁle by the speciﬁed name,

the n fo r an indirect access permanen t ﬁle. If ﬁl en ame

does not exist, it is created. The edited ﬁle is saved

or replaced at completion of editing.

LOAD Loads key deﬁnitions into the terminal from the speciﬁed

ﬁle.

PRINT Creates a local ﬁle called KEYPRNT on which the key

deﬁnitions are listed from the speciﬁed ﬁlename.

ﬁlename The name of the key deﬁnition ﬁle. Default is KEYDEFS.

? Lists the options and prompts you for an option and ﬁlename.

The KEY command may appear in a procedure ﬁle.

/*^^\

8-6 60459680 F

LINE COMMAND

The LINE command speciﬁes 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 identiﬁes the terminal model to the system and initiates a search for

the terminal deﬁnition ﬁle for that model (unless the CDC 721 terminal was speciﬁed;

characteristics of this terminal are preloaded into the system so that no deﬁnition ﬁle is

required). The system uses the following search order in attempting to ﬁnd the deﬁnition

ﬁle:

• A loc al fi le ca lle d T ERMLI B (cr ea ted usi ng th e TD U uti lity) .

• An indirect access permanent file called TERMLIB under your user name.

• An indirect access permanent file called TERMLIB under user name LIBRARY

(UN=LIBRARY). Your site may maintain a system ﬁle containing common terminal

deﬁnitions.

If TERMLIB is found under your user name or under user name LIBRARY, the system copies the

terminal deﬁnition to a local ﬁle called ZZZZTRM for later use by NOS full screen display

features. The terminal ﬁles listed below for the TM parameter are released with the system

and are always available once you have identiﬁed your terminal in a LINE or SCREEN command.

Format:

LINE,TM=model.

LINE,model.

Jf^N

60459680 F 8-6.1

Parameter Description

TM=model Speciﬁes the terminal model. The value speciﬁed for model is the

terminal mnemonic deﬁned in the terminal deﬁnition ﬁle or the

terminal mnemonic for one of the following preloaded terminal

deﬁnitions:

model Description

721 CDC 721 terminal.

721V3 CDC 721 terminal version 3.

722 CDC 722 terminal.

72230 CDC 722-30 terminal.

VT100 DEC VT100 terminal.t

Z19 Zenith Z19 or Z29 terminal or Heathkit H19 terminal.tt

ADM3A Lear Siegler ADM3A terminal.ttt

A D M 5 L e a r S i e g l e r A D M 5 t e r m i n a l . t t t

TV924 TeleVideo 924 terminal .tttttt

TV950 TeleVideo 950 terminal.tttttt

TV955 TeleVideo 955 terminal.tttttt

T 4 1 1 5 Te k t r o n i x 4 1 1 5 t e r m i n a l . t t t t

3270 IBM 3270 terminal.ttttt

PCONxx IBM PC using CDC CONNECT, xx is the current level of

CONNECT.

If you want your terminal to have the type-ahead capability, append T

to the model name you are using in the LINE command. Type-ahead

allows you to press a function key two or more times in quick

succession, rather than pressing it once and waiting for the system to

execute it before pressing it a second time.

If this parameter is omitted, the terminal model is left unchanged.

You can include this command in a procedure.

tDEC is a registered trademark of the Digital Equipment Corporation,

tt Zenith Z19 and Z29 are products of the Zenith Corporation. Heathkit H19 is a product

of the Heath Corporation,

ttt Lear Siegler ADM3A and ADM5 are products of the Lear Siegler Corporation,

tttt Tektronix 4115 is a product of the Tektronix Corporation.

tttttlBM 3270 is a product of the IBM Corporation.

| tttttt TeleVideo 924, 950, and 955 are products of TeleVideo Systems, Inc.

^ S S ^ .

8-6.2 60459680 H

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 speciﬁes 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 identiﬁes the terminal model to the system and initiates a search for the

terminal deﬁnition ﬁle for that model (unless the CDC 721 terminal was speciﬁed;

characteristics of this terminal are preloaded into the system so that no deﬁnition ﬁle is

required). The system uses the following search order in attempting to ﬁnd the deﬁnition

ﬁle:

• 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 ﬁle containing common terminal

deﬁnitions.

If TERMLIB is found under your user name or under user name LIBRARY, the system copies the

terminal deﬁnition to a local ﬁle called ZZZZTRM for later use by NOS full screen display

features. The terminal ﬁles are always available once you have identiﬁed your terminal in

a SCREEN or LINE command.

Format:

SCREEN,TM=model.

SCREEN,model.

60459680 G 8-7 |

Parameter Description

TM=model Speciﬁes the terminal model. The value speciﬁed for model is the

terminal mnemonic deﬁned in the terminal deﬁnition ﬁle or the

terminal mnemonic for one of the following preloaded terminal

deﬁnitions:

model Description

721 CDC 721 terminal.

721V3 CDC 721 terminal version 3.

722 CDC 722 terminal.

72230 CDC 722-30 terminal.

VT100 DEC VT100 terminal.t

Z 1 9 Z e n i t h Z 1 9 o r Z 2 9 t e r m i n a l o r H e a t h k i t H 1 9 t e r m i n a l . t t

ADM3A Lear Siegler ADM3A terminal.ttt

A D M 5 L e a r S i e g l e r A D M 5 t e r m i n a l . t t t

T4115 Tektronix 4115 terminal.tttt

3270 IBM 3270 terminal, ttttt

PCONxx IBM PC using CDC CONNECT, xx is the current level of

CONNECT.

If you want your terminal to have the type-ahead capability, append T

to the model name you are using in the SCREEN command. Type-ahead

allows you to press a function key two or more times in quick

succession, rather than pressing it once and waiting for the system to

execute it before pressing it a second time.

If this parameter is omitted, the terminal model is left unchanged.

You can include this command in a procedure.

tDEC is a registered trademark of the Digital Equipment Corporation,

ttZenith Z19 and Z29 are products of the Zenith Corporation. Heathkit H19 is a product of

the Heath Corporation,

tttLear Siegler ADM3A and ADM5 are products of the Lear Siegler Corporation.

ttttTektronix 4115 is a product of the Tektronix Corporation,

ttttt IBM 3270 is a product of the IBM Corporation.

8-8 60459680 G

TDU COMMAND

The TDU command calls an interactive procedure to compile a terminal deﬁnition ﬁle and

store the compiled deﬁnition (in load capsule form) in a user library. The user library

can later be accessed by a SCREEN or LINE command to deﬁne terminal characteristics to the

system.

The user library to receive the load capsule must be a local ﬁle. If the library ﬁle you

specify does not exist as a local ﬁle, TDU creates it. If you do not specify a library

ﬁle, TDU uses a local ﬁle with the name TERMLIB. If no ﬁle TERMLIB exists, TDU creates

it.

Format:

TDU,I=deﬁnition,L=listing,LIB=library

Parameter Description

I=deﬁnition Speciﬁes the terminal deﬁnition ﬁle. The ﬁle must be in 6/12-bit

display code. For information on how to create a terminal deﬁnition

ﬁle, refer to the Screen Formatting Reference manual.

L = l i s t i n g S p e c i ﬁ e s t h e l i s t i n g ﬁ l e . T h e l i s t i n g ﬁ l e i s a c o p y o f t h e i n p u t

ﬁle with error messages, if any, interspersed. The default name is

OUTPUT.

LIB=library Speciﬁes the library ﬁle to receive the load capsule. The default

name is TERMLIB. To be used by the SCREEN and LINE commands, the

libra ry ﬁl e m us t b e a l oc al ﬁl e o r a n in dir ec t acces s ﬁl e c al le d

TERMLIB.

The TDU command may appear in a procedure ﬁle.

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 deﬁnition 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-ﬂy

changes during a given terminal session.

The network commands for a NAM/CCP network are in appendix J. The CDCNET Terminal Interface

Usage manual describes network commands for a NAM/CDCNET network.

Format:

TRMDEF,L=lfn,tCl=vi,...,tcn=vn

Parameter Description

L=lfn Speciﬁes an optional ﬁle on which the terminal redeﬁnition

information is written. If lfn is omitted, ﬁle OUTPUT is assumed,

If another ﬁle is speciﬁed, the changes are implemented when the

ﬁle is li s te d o r c op i ed t o the ter mi n al .

tCi=Vi Speciﬁes the terminal characteristic to be changed, tci is speci

ﬁed by a two-character mnemonic listed in table J-l in appendix J.

The NUL and DEL characters can be speciﬁed on the TRMDEF command

although they cannot be used with the terminal deﬁnition commands

(refer to table J-l). You may not use the mnemonics AR, CH, HN, HS,

MS, and TM for tCi.

The new option, Vi, is any value in the range given for that termi

nal c haracterist ic i n table J-l. It can be a d ecima l value , a coded

value with a special meaning (such as PR for printer), or a single

character. You can specify multiple values for DL, EB, EL, and XL if

you separate the values with slants (/), but only as speciﬁed in

appendix J. If the new option is a single character, it can be given

in any of the following formats.

>^P^V

Description

Any alphanumeric character (a character with a display

code in the range from 0 through 44g).

60459680 G 8-9

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 speciﬁed 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 speciﬁed 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 deﬁnes 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 speciﬁcations 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

TRMDEF,IN=PT This command changes the input device to a paper tape reader, thus

allowing you to read data and commands from a tape. It has the

same effect as the corresponding terminal deﬁnition command (that

is, entry of the control character followed by IN^PT).

TRMDEF,DL=C20/X03/TO This command deﬁnes three different transparent input delimiters.

• the transmission of 20 characters

• the entry of an ETX character code

• a t i m e o u t

The ﬁrst 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 notiﬁcation of the error is where you have

speciﬁed the L=lfn parameter and the system does not detect the error in its preliminary

check. However, the network notiﬁes you of the error as soon as you try to actualize the

changes (copy ﬁle 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 speciﬁc subsystem. You should always be aware of the sub

system that is currently active. For example, attempting to execute a FORTRAN program while

operating under the BASIC subsystem causes meaningless diagnostic messages to be issued. To

determine which subsystem is currently active, enter the ENQUIRE command.

NOTE

The subsystem may be automatically selected

by the system at login if this has been set

in th e val id at io n ﬁl e (r ef er t o th e LIM IT S

command). You can also set the subsystem in

your prologue with the SET command.

60459680 G 8-11 |

Use the execute subsystem whenever possible to conserve system resources. Efﬁciency can be

achieved when certain programs are used frequently. For example, a source code program

created under the FORTRAN subsystem must ﬁrst 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 efﬁciency can be achieved by retaining

INTERACTIVE STATUS COMMANDS

The system executes interactive status commands immediately. You may enter them while the

system is executing another command. The system queues other commands that are typed prior

to prompts (refer to section 17).

Format:

ct x

Parameter Description

ct ct is the network control character deﬁned for the terminal (refer to

the CT command in appendix J). Do not include a space between ct and

x. We show one here only for clarity.

x x c a n b e t h e l e t t e r D , E , o r S .

With the exception of the Detach command (ctD), the system generates only a line feed if you

enter an interactive status command during one of the following states:

Text mode

Auto mode

Input mode (a program is waiting for input)

During login

During the processing of the interruption or termination sequence

DETACH COMMAND (ctD)

The Detach command detaches a terminal job from the terminal. You can detach a job at any

time d uring a terminal s ession. To deta ch th e job during o utput, ﬁrst enter the i nterrup

tion sequence and then enter the Detach command. Otherwise, ctD alone is sufﬁcient.

When you detach a job, the following message appears at the terminal:

JOB DETACHED, JSN=jsn

All ﬁles assigned to the detached job remain assigned to it.

0H^\

yf^N

J$<fﬁs<\

Examples

TRMDEF,IN=PT This command changes the input device to a paper tape reader, thus

allowing you to read data and commands from a tape. It has the

same effect as the corresponding terminal deﬁnition command (that

is, entry of the control character followed by IN=PT).