Gould MPX-32
™
Release 1.5E Reference Manual
Volume IT
April 1985
Publication Order Number: 323-003662-000
TMMPX_32 is a· trademark of Gould Inc.
rn} GOULD
Electronics
(
\
(
HISTORY .
The MPX-32 Release 1.0 Reference Manual, Publication Order Number 323-001012-000, was printed June, 1979.
Publication Order Number 323-001012-100 (Revision 1, Release 1.3) was printed February, 1980.
Publication Order Number 323-001012-200 (Revision 2, Release 1.4) was printed July, 1980.
Publication Order Number 323-003662-000 (Revision 3, Rele<;lse 1.58) was printed Septem ber, 1982.
Publication Order Number 323-003662-001 (Change 1 to Revision 3, Release 1.5D) was printed February, 1984.
Publication Order Number 323-003662-002 (Change 2 to Revision 3, Release 1.5E) was printed April, 1985. The updated manual contains the following pages:
*
Change Number Ti tIe page •• ,. ••• ,.. c • • • • • • ,. • e 2 Copyright page ••••••••••••••• 1 iii and iv Change 2 •••••••••••• 2!~~ ~nd iv Change 1 •••••••••••• 1
Ill/IV • 0 fI ,. • ,. ,. • • • • • • • • • • • • • • •
a
v through viii •••••••••••••••• 0 ix ,. •••••••••••••••••••• CI • 0 1 x through xvii/xviii •••••••••••• 0 1-1 • II! • • • • • • • • • • • • • • • • • • • • • 1 1-2 through 1-10 •••••••••••••• 0 2-1 through 2-15 •••••••••••••• 0 2-16 e o • • • • • • • • • • • • • • • • • • • • 1 2-17 through 2-27 ••••••••••••• 0 2-28 •••• ,. ••• e o • • • • • • • • • • • • 1 2-29 through 2-56 ••••••••••••• 0 3-1 through 3-13 •••••••••••••• 0 3-14 and 3-15 • • • • • • • • • • • • • • • • 1 3-16 through 3-18 ••••••••••••• 0 4-1 through 4-63/4-64., ••••••••• 0 5-1 ••••••• G • • • • • • • • • • 0 • • • • 2 5-2 through 5-6 •••••••••••••• 0
;-7 0 " . 8 • 0 • • • • • • • II 0 . . . c • " 1
*
Change Number 5-8 through 5-58 ••••••••••••••• 0 6-1 through 6-4 ••••••••••••••• 0 6-5 through 6-7 ••••••••••••••• 1 6-8 through 6-30 ••••••••••••••• 0 6- .31 • tID ,. • • • • • • •0-. . •
£I • ,. • • • • • ,. 1 6-32 through 6-33/6-34 •••••••••• 0 7-1 through 7-7/7-8 •••••••••••• 0 8-1 through 8-9/8-10 ••••••••• ••• 0 9-1 •••• II • • .. • • e • • • • • • • e • • • • • 0 9-2 •••• fi) • • • • • • • • • • III • • • • ,. II 0 • 1 9-3 through 9-14 ••••••••••••••• 0 10-1 through 10-24 ••••••••••••• 0 11-1 through 11-3 ••••••.••••••• 0 11-4.0 ••••••••••••••••••••• 1 11-5 through 11-29/11-.30 •••••••• 0 A-I through A-7/ A-8 ••••••••••• 0 B-1 through 8-21/8-22 •••••••••• 0 C-l and C-2 .... g o . QiI . . . 0c ..
:3 • '" • • • • • • • • • 0 ill 0 • e o . • • It • • • 1 C-4 through C-6 ••••••••••••••• 0 C-7 and C-8 ••••••• 0 0 Co CI • • • 11'1 " 0 • 1 C-9 through C-21 •••••••••••••• 0 Continued*
Zero in this column indicates an original page.Change 2 iii
*Change Number C-22 . . . 1 C-23 through C-26 •••••••••••• 0 C-27 through C-30 •••••••••••• 1 C-31 through C-35 •••••••••••• 0 C-36 through C-38 •••••••••••• 1 G-I . . . • . . . 0 G-2 ••••••••••••••••••••••. 1
*Change Number G-3/G-4 . . . 0 GL-l through GL-6 ••••••••••••• 0 GL-7 ••••••••••.•.•••..•••.• 1 GL-8 through GL-ll/GL-12 ••••••• 0 IN-l through IN-15 ••••••••••••• 0 IN-16 •..•••••.•••.••..••.••. 1 IN-17/IN-18 •••••••••••••••••• 0
* Zero in this column indicates an original page.
(
(--
CONTENTS
1. THE ASSEMBLER (ASSEMBLE) 1.1
1.2
1.3 1.4 1.5 1.6 1.7 1.8
General Description ••.••••
Files and File Assignments ••
1.2.1 Source Code (PRE and SI) •••••.
1.2.2 Macro Libraries (MAC, MA2) ••
1.2.3 Listing (LO) •••••••••••
1.2.4 Object Code (BO and GO) •••
1.2.5 Compressed Source (CS) •••
1.2.6 Temporary Files (UTI, UT2) Options . . . ,., 0 • • • • • • • • .
Accessing the Assembler ••
Assembler Directives Listings •••••••••
Errors and Aborts ••
1.7.1 Aborts • Examples ••••••••
2. THE CATALOGER (CATALOG) 2.1
2.2
General Description ••••••.••••••
2.1.1 Load Module Information 2.1.2 Resource Requirements 2.1.3 Absolute Load Modules •••
2.1.4 Sectioned versus Nonsectioned Tasks 2.1.5 Segmented versus Nonsegmented Tasks 2.1.6 Object Modules and Load Modules 2.1.7 Password Protected Load Modules 2.1.8 The Cataloging Process.
2.1.8.1 First Pass 2.1.8.2 Second Pass.
2.1.8.3 Common References ••
2.1.8.4 Included or Excluded Object Modules 2.1.8.5 Selective Retrieval from SGO.
2.1.8.6 Symbol Tables (SYMT AS's)
2.1.9 Allocation and Use of Global Common and DAT APOOL Partitions ••••.••.•
Files and File Assignments
2.2.1 File Assignments Chart ••
Options ,. Ii 0 • • • 0 • G Cl 0 0 D • • e • 0 • Using the Cataloger •••••••••••
2.4.1 Cataloging a Nonsegmented Task ••
2.4.1.1 Job Organization ••••••••••
2.4.1.2 Recataloging the Load Module ••
2.4.2 Cataloging a Segmented Task 2.4.2.1 Job Organization 2.4.2.2 Overlay Levels ••.
1-1 1-2 1-2 1-2 1-2 1-3 1-3 1-3 1-7 1-8 1-8 1-9 1-9 1-9 1-10
2-1 2-3 2-5 2-6 2-6 2-7 2-7 2-8 2-8 2-8 2-9 2-9 2-9 2-9 2-10 2-10 2-11 2-13 2-18 2-18 2-18 2-18 2-21 2-21 2-21 2-23
v
2.5 2.6
2.7 2.8 2.9 2.10
2.4.2.3 2.4.2.4
The Over lay Transient Area •••••••••••••••
Resolution of External References in Segmented Tasks . . . • . • . . .
2.4.2.5 Cataloging a Segmented Task in Stages 2.4.2.6 Recataloging with Overlays •••
Accessing the Cataloger •••••
Cataloger Directives •••••••••••
2.6.1 ABSOLUTE Directive •••••
2.6.2 ALLOC ATE Directive ••••
2.6.3 ASSIGN 1 Directive ••
2.6.4 ASSIGN2 Directive •••••••
2.6.5 ASSIGN3 Directive ••
2.6.6 ASSIGN4 Directive ••
2.6.7 BUFFERS Directive • 2.6.8 CATALOG Directive
2.6.9 ENVIRONMENT Directive •••
2.6.10 EXCLUDE Directive.
2.6.11 EXIT Directive •••••
2.6.12 FILES Directive ••••
2.6.13 INCLUDE Directive.
2.6.14 LINK BACK Directive 2.6.15 LORIGIN Directive ••
2.6.16 OPTION Directive ••
2.6.17 ORIGIN Directive •••
2.6.18 PASSWORD Directive •• ~ • 2.6.19 PROGRAM Directive.
2.6.20 PROGRAMX Directive 2.6.21 SYMTAB Directive •••
2.6.22 USERNAME Directive ••••••
Errors •••••
Examples •••
Listings . . . • . . . • • • . . . • • . .
. . .
Creating RTM Tasks on the MPX-32 System ••
....
. ...
...
2.10.1 Assembling RTM Object Modules ••••
2.10.2 Running RTMCATL •••••••••••••
2.10.3 Semantic Differences •••••••••••
2.10.4 Transporting the Cataloged Task to an RTM System 2.10.5 RTMCATL Load Modules Cannot by Used on MPX-32
. . . . .
. ..
Systems . . . . • • • • • • • • • • • • • • • • e • • • • • • e • • • • • •
3.. TASK STRUCTIJRE AND OPERATION
3.1 General Description •.. 11 . . . .
3.1.1 Multiple Dictionaries ••••••••••• • ••••
3.1.2 Static versus Dynamic D AT APOOL • • • • • • • ••••
3.1.3 DPEDIT Directives. • • • • • • • • • ••••• • e· •
3.1.4 Input Data Format •••
3.1.5 Dictionary Records ••
3.2 Files and File Assignments •••••••••
3.2.1 The Input File (SYC) •••••
3.2.2 The DATAPOOL Dictionary (DPD) •••
2-28 2-29 2-31 2-32 2-34 2-35 2-38 2-38 2-39 2-40 2-42 2-43 2-43 2-44 2-45 2-46 2-46 2-46 2-47 2-47 2-47 2-48 2-48 2-49 2-49 2-50 2-50 2-50 2-51 2-53 2-55 2-55 2-55 2-56 2-56 2-56 2-56
3-1 3-1 3-2 3-2 3-3 3-6 3-7 3-7 3-7
(-
(~
3.4 3.5 3.6
3.7 3.8 3.9
.. . . . . . . . .
Using DPEDIT ••••
Accessing DPEDIT ••
DPEDIT Directives.
. . . . . . . . .
3.6.1 IDPD Directive
· ..
· . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . .
· ... . . . . . . . . . . . .
3.6.2 IENTER Directive
. . . . . . . . . . . . . . . · ... .
3.6.3 ILOG Directive •••
. . . . .. · ..
3.6.4 IREMAP Directive
· ...
3.6.5 ISAVE Directive •••
· ... . · ....
3.6.6 IVERIFY Directive.
· ... .
Listings ••••
. . . . . · ...
Errors ••
Examples. '.
4. nlE DEBUGGER (DEBUG) 4.1
4.2 4.3
4.4 4.5
General Description ••••••••••••••••••
4.1.1 Attaching DEBUG to a User Task 4.1.2 I/O . . . • . . .
....
4.1.2.1 4.1.2.2
Terminal I/O ••
Command Files
· ... .
4.1.2.3 SLO Files ••
4.1.3 Control Transfers.
· .
4.1.4 Break Handling ••••••
· . . . . . . . . .
Files and File Assignments ••••••
4.2.1 File Assignments Chart.
. . . . .
Using the Debugger •••••••••
· ... .
4.3.1 Expressions ••••••••• 4.3.1.1 Constants ••
· . · ... . . .
4.3.1.2 Register Content References •••••••••••
4.3.1.3 Memory Content (Indirect) References.
4.3.1.4 Bases •••••
. . . . . . .
4.3.1.5 COUNT •••
· ... .
4.3.1.6 Operators
...
. ..
. ..
4.3.2 4.3.3 4.3.4 4.3.5
Relative versus Absolute Expression Evaluation ••••••••••
...
Address Displays and References.
Address Restrictions •••••
....
Traps and Trap Lists ••••••••
4.3.5.1 Setting a Trap ••••••
4.3.5.2 Nesting Trap Lists
...
Accessing the Debugger •••••••
· ..
Commands ••••••••••••••••
4.5.1 ABSOLUTE Command ••
4.5.2 BASE Command •••
· .... . ...
...
4.5.3 BREAK Command
· ... · ....
4.5.4 CC Command •••• • • • 0 • • "
. . .
4.5.5 CLEAR Command
· ... .. . ....
4.5.6 CM Command
4.5.7 CR Command •••••
... · . . . . . · .
4.5.8 DELETE Command ••
· ... · . . . . .
4.5.9 DET ACH Command
· ....
• • • 0 • •...
4.5.10 DUMP Command
· ...
4.5.11 END Command ••
4.5.12 EXIT Command
· ...
4.5.13 EXIT Command
· ....
4.5.14 FILE Command
· .... ...
3-11 3-11 3-12 3-12 3-12 3-14 3-14 3-15 3-15 3-16 3-17 3-17
4-1 4-5 4-7 4-7 4-9 4-9 4-9 4-11 4-11 4-11 4-13 4-13 4-15 4-16 4-16 4-17 4-19 4-19 4-21 4-21 4-21 4-23 4-23 4-24 4-27 4-29 4-34 4-35 4-36 4-36 4-37 4-38 4-39 4-40 4-41 4-42 4-42 4-43 4-44 4-45 vii
4.6 4.7 4.8 4.9
FORMAT Command GO Command •••••••••
IF Command LIST Command ••
LOG Command ••
MSG Command.
RELATIVE Command REVIEW Command 4.5.15
4.5.16 4.5.17 4.5.18 4.5.19 4.5.20 4.5.21 4.5.22 4.5.23 4.5.24 4.5.25 4.5.26 4.5.27 4.5.28 4.5.29 4.5.30 4.5.31 4.5.32
RUN Command
. . . . .
SET Command ••••••••
SHOW Command SNAP Command ••
STATUS Command •••••
STEP Command ••
TIME Command •••••••••
TRACE Command •••
TRACK Command •••••
WATCH Command ••••••
Batch Considerations Listings and Reports ••
Errors •••
Examples.
. . ...
. . . ...
.. ..
. . . . . . . . . . .
..
5. INTERACTIVE PROCESSING 5.1
5.2 5.3 5.4
5.5 5.6
General Description •••••
Files and File Assignments •••
Options . . . 0 • • • • • • • •
Using the Editor •••••••••••••••
5.4.1 Addressing Techniques •••
5.4.1.1 Special Characters
5.4.1.2 Line and Range Addressing 5.4.1.3 Groups •••••••••••
5.4.1.4 Content Identifiers 5.4.1.5 Defaults •••••••
. . .
5.4.1.6 Special Command Defaults •••••••••••
5.4.2
5.4.3 5.4.4 5.4.5 5.4.6
5.4.1.7 Descrition in Syntax Sections
Lines and Line Numbers ••••••••••••••••••
5.4.2.1 Line Numbers Generated by the Editor ••
5.4.2.2 Line Numbers at the Beginning and End of the Workfile .•••....•.. 0 0 • a • • c
5.4.2.3 Physical Position of Line Numbers.
5.4.2.4 Text Output without Line Numbers Accessing Files Created Outside the Editor Accessing Password Protected Files ••••••••
Accessing System Files ••••••••••••••
Entering and Editing Upper/Lower Case Text 5.4.7 Using the Break Key ••
Accessing EDIT ••••••••••
EDIT Commands ••••••••••
5.6.1 APPEND Command
4-46 4-47 4-49 4-50 4-50 4-51 4-51 4-52 4-52 4-53 4-54 4-55 4-55 4-56 4-56 4-57 4-60 4-61 4-62 4-63 4-63 4-63
5-1 5-1 5-1 5-2 5-2 5-2 5-3 5-3 5-4 5-4 5-4 5-5 5-6 5-6 5-7 5-7 5-7 5-8 5-8 5-8 5-9 5-9 5-10 5-11 5-13
\
/
(
,(
(~
5.7 6- 6.1
6.2 6.3 6.4
6.5 6.6
5.6.6 COMMAND Command
. . . ...
5.6.7 COPY Command 5.6.8 DEBUG Command
5.6.9 DELETE Command.
...
5.6.10 EXIT Command
. . . . . .
5.6.11 INSERT Command
. ...
5.6.12 LIST Command ••••
.
...
.. .. • • D • • ..5.6.13 MODIFY Command.
. . .
5.6.14 MOVE Command
...
B • • .. 0· ...
5.6.15 NUMBER Command
...
• • c • • •5.6.16 PREFACE Command CI . . .
5.6.17 PRINT Command •••• l D o o e e Q • • c
5.6.18 PUNCH Command
. .
5.6.19 REPLACE Command
5.6.20 SA VE Command •••••
. . .
5.6.21 SCRATCH Command 5.6.22 SET Command ••••
5.6.23 SHOW Command
...
... . . . · ...
5.6.24 STORE Command ••
5.6.25 USE Command ••••
5.6.26 VERIFY Command
...
• • • • • • CI5.6.27 WORKFILE Command ••
. . . . . . . .
Edit Errors . . .
. . . . .
THE FILE MANAGER (FILEMGR)
General Description •••••••••••••••••••••••••
6.1.1 The System Master Directory (SMD) 6.1.2 System Files versus User Files ••
6.1.3 The Save/Restore Process ••
Files and File Assignments •••••
6.2.1 File Assignments Chart ••
Options CI . . . ., . . . .
Using the File Manager •••••••••••••••
6.4.1 Computing the Size of a File ••
6.4.2 Using Wild Card Characters in File Names 6.4.3 Password-Protected Files •••••••
6.4.4 Special Characters in File Names 6.4.5 Notes on File-to-Tape Transfers 6.4.6 Device Specifications.
Accessing the File Manager ••••••
FILEMGR Directives .••••••••••
6.6.1 CREATE and CREATEU Directives 6.6.2 CREATEM Directive ••••••••••
6.6.3 DELETE and DELETEU Directives ••
6.6.4 DELETEW Directive ••••••••••••
EXIT Directive ••••••••••••••••
EXPAND and EXPANDU Directives ••
LOG, LOGU, LOGC, and LOGS Directives
...
. . . . 0 • • • • •
. ...
• • • • 0
CI . . .
e . . .
• • 0 e . . .
. . . .
...
. . . .
• • • • • It •
6.6.5 6.6.6 6.6.7 6.6.8 6.6.9 6.6.10 6.6.11 6.6.12 6.6.13
MEMO Directive ••••••••••••••• • • c • • • D • • • • • 8 •
PAGE Directive ••••••••••••••••
RESTORE and RESTOREU Directives REWIND Directive ••••••••
SA VE and SA VEU Directives SAVELOG Directive ••••••
5-21 5-22 5-26 5-26 5-27 5-28 5-30 5-32 5-33 5-35 5-37 5-39 5-40 5-41 5-42 5-44 5-45 5-50 5-52 5-54 5-56 5-57 5-58
6-1 6-1 6-2 6-3 6-3 6-3 6-5 6-5 6-5 6-6 6-6 6-7 6-7 6-9 6-9 6-10 6-12 6-14 6-17 6-17 6-19 6-19 6-20 6-21 6-22 6-22 6-25 6-26 6-30
ix
6.7 6.8 6.9
6.6.14 6.6.15
DST Directive ••••••
SKIPFILE Directive ••
· . . . . . . . . . . . ...
· ..
6.6.16 Examples •• USERNAME Directive
. . . . . . . . . . · · .... ... . · .
Errors •••••••••
. . . ... . . · ... . · ... .
Listings
. . · ... .
· ...
· ... .
7. M.KEY EDITOR (KEY) 7.1
7.2 7.3 7.4 7.5
General Description •••••••••
File and File Assignments Using Key •••••••••••••
7.3.1 Input Record Syntax.
7.3.2 Sample Input File ••
Accessing the M.KEY Editor Example ••••••••••••••••
· ... · ... . · ... · ...
· .. · . · . · .. · ...
· . . . . . . . . .
· .. · . . ... . . · .. . . . . . . . . · ... . . . . .
· ... · ....
8. THE SU8ROUTINE UBRARY EDITOR (UBED) 8.1
8.2
8.3 8.4 8.5 8.6
8.7 8.8 8.9
General Description ••••••••••••••••
· ....
8.1.1 LIBED Directives Summary ••
· . . · . . .
Files and File Assignments ••••••••••••••••
8.2.1 The Object Module File (LGO).
· ... · . . . . . . . . . .
8.2.2 The Directive File (CTL) •••••
· ...
8.2.3 The Subroutine Library File (LIB) •••••
8.2.4 The Directory (DIR) •••••
· ....
8.2.5 Listed Output (LLO)
· . · ....
Options ••••••••
. . . . . · ... . · . . . . . . . . . .
Using LIBED
Accessing LIBED •
•
•· . . . . . . . . . . .
Subroutine Library Editor Directives ••••••••
8.6.1 DELETE Directive •••••••••••••••
· ..
8.6.2 EXIT Directive •••••••••
· ...
· ..
· .. · . . . . .
· .
· ..
8.6.3 LOG Directive
· . . · .. . . . . .
Listings ••
Errors.
Examples •
. . . . . . . . . · . . ... . . . . . . . . . . . .
. . . . · .. ...
· ...
· . . . . . . . . .
· ....
· . . ..
..
9. THE MACRO U8RARY EDITOR (MACUBR) 9.1
9.2
9.3 9.4 9.5
General Description •••••••••••••••••••••••••
· ....
9.1.1 MACLIBR Command.Summary ••••••••••
Files and File Assignments • ~ ••
9.2.1 Macro Library (MAC) •••
... ... · ....
9.2.2 Macro Input File (SI) ••••
· ... . · ...
9.2.3 Directives (DIR) ••••
· ... · ... . · ... .
9.2.4 Audit Trail (LO) •••••
· . · .
9.2.5 Scratch File •••
· .... · ... · . · ...
Options ••••••••••••••• e, • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • .•
...
Using the Macro Library Editor
Accessing the Macro Library Editor ••
· .... · ... · .. · ....
6-30 6-32 6-32 6-33 6-33 6-33
7-1 7-2 7-3 7-3 7-5 7-6 7-7
8-1 8-1 8-2 8-2 8-2 8-2 8-2 8-2 8-5 8-5 8-6 8-7 8-7 8-7 8-7 8-8 8-8 8-8
9-1 9-2 9-2 9-2 9-3 9-3 9-3 9-3 9-6 9-6
,/
\ ',,--
)
t
(
'.
... -,.-
(
.. ' ... .9.6.4 IDISPLAY Directive
· . . . .
9.6.5 lEND Directive
... · ....
9.6.6 IEXIT Directive ••
9.6.7 /INSERT Directive
· ...
9.6.8 /LOG Directive ••
. . .
9.6.9 /MACLIST Directive.
9.6.10 /REPLACE Directive 9.7 Listings
9.8 Errors ••
9.9 Examples • flo • • • 10. MEDIA CONVERSION UTILITY (MEDIA) 10.1
10.2 10.3 10.4 10.5 10.6
10.7 10.8 10.9
MEDIA Directives Summary Files and File Assignments Options ••••••••
Using MEnIA ••••
10.4.1 Labels Accessing MEDIA MEDIA Directives 10.6.1 General
10.6.2 BACK FILE Directive 10.6.3 BACKREC Directive 10.6.4 BUFFER Directive ••
10.6.5 CONVERT Directive ••
10.6.6 COpy Directive.
10.6.7 DUM P Directive •••••••
10.6.8 END Directive.
10.6.9 EXIT Directive ••
10.6.10 GOTO Directive 10.6.11 INCR Directive 10.6.12 MESSAGE Directive 10.6.13 MOVE Directive ••••
10.6.14 OPTION Directive 10.6.15 READ Directive ••
10.6.16 REWIND Directive 10.6.17 SETC Directive •••
10.6.18 SKIPFILE Directive •••••
10.6.19 SKIPREC Directive •••••
10.6.20 VERIFY Directive 10.6.21 WEOF Directive ••
10.6.22 WRITE Directive Listings
Errors ••
Examples ••
11. SOURCE UPDATE UTILITY (UPDATE) 11.1
11.2 11.3 11.4
General Description •••••••
11.1.1 UPDATE Directives Files and File Assignments Options . . . • Using UPDATE •••••••••
11.4.1 Compressed Source Formatting 11..4.2 Library Mode of Operation •••
...
· . . . .
· ... . . . . . .
• • CI • • II '"
. . . . .
o II e 0 e
• • • • tI
. . .
9-9 9-9 9-9 9-10 9-10 9-10 9-11 9-11 9-12 9-13
10-1 10-2 10-4 . . . . • •. 10-4 10-4 10-4 10-5 10-5 10-6 10-6
• • • • • • • • • • • • • • •• 10-7 10-7 10-8 10-8 10-9 10-9 10-10
••••••••••••••••• 10-11
• 10-11
• ••• 10-12 .10-13 .10-15 .10-15
• 10-15
• •• 10-16
• •• 10-16
• •• 10-16
• •• 10-17 10-17
• 10-18
• •• 10-19
• 10-21
11-1 11-1
11~3
11-6 11-7 11-7 11-7
xi
11.5 11.6
Accessing UPDATE
UPDATE Directives
. . . . . .
11.6.1 General •
11.6.2
I
ADD Directive...
11.6.3
I
ASI Directive (Reassign LFC to Disc File) 11.6.4 I AS3 Directive (Reassign LFC to Device). • 11.6.5 IBKSP (Backspace) Directive •••••••••11.6.6 IBLK (Blank Sequence Field) Directive ••••••••
11.6.7 /COPY Directive ••
11.6.8 IDELETE Directive 11.6.9 lEND Directive •••••
11.6.10 IEXIT Directive •••
11.6.11 IINSERT Directive ••••••
11.6.12 ILIST Directive ••••
11.6.13 /MOUNT Directive ••
11.6.14 INBL (No Blank Sequence Field) Directive
11.7 11.8 11.9
11.6.15 INOLIST Directive •••
11.6.16 INOSEQN Directive •••••
11.6.17 /REPLACE Directive 11.6.18 IREWIND Directive 11.6.19 ISCAN Directive •••
11.6.20 ISELECT Directive •••
11.6.21 /SEQUENCE Directive 11.6.22 ISKIP Directive.
11.6.23 IUSR Directive •••
11.6.24 /WEOF Directive listings
Errors ••
Examples ••
Appendix A Appendix 8 Appendix C Appendix D Appendix E Appendix F Appendix G
MPX-32 Device Access . . . . System Services Cross Reference Charts MPX-32 Abort and Crash Codes . .
Numerical Information . .. .
. ..
Powers of Integers . . . . ASCB Interchange Code Set lOP Panel Commands . . .
• • • • • • • I)
11-11 .11-12 .11-12 .11-12
••••••• 11-13
• • 11-13
• • 11-14
• ••• 11-14
• • 11-15 .11-15 .11-15
• 11-16
• 11-16
• • 11-17
• 11-18 .11-18 ..11-19
• .11-19 11-19
••• 11-20 11-20
• • 11-20
•••• 11-21
• • 11-21
• • 11-22
• • 11-22 11-23 .11-24 .11-26 A-I B-1 C-l 0-1 E-l F-l G-l Glossary
. . . .0. . .
GL-IIndex . .• • • • • • • • • • • • • • 0 • • • • • • • • • • • • • • • • s" • • • • • e o • • • • • • • • • • • • • • • • IN-l
(
Figure 2-1 2-2 2-3 2-4 2-5 2-6 2-7 3-1 3-2 3-3 4-1 4-2 4-3 4-4 6-1 11-1 11-2 11-3 11-4
ILLUSTRA nONS
Title Cataloging a Load Module.
1/0 Overview ••••••••••
Simple Over lay Structure ••••
More Complex Over lay Structure •••••
Default Memory Allocation for Overlays ••
Modified Memory Allocation for Overlays Recataloging Illustration •••••••••
Datapool Editor Input Data Format ••
Datapool Dictionary Entry Format ••••
Datapoo! Editor Audit Trail Format ••
DEBUG Memory Map ••••••••.•••
DEBUG Base Names ••••••••••••
DEBUG Command Address Restrictions Nested Trap Lists •••••••••••••••••
.. . 'f.
2-2 2-11 2-23 2-24 2-25 2-27 2-33 3-5 3-6 3-16 4-6 4-18 4-22 4-25 File-to-Tape Transfers
. . . . . . . . . . . . . . . . . . .
6-8Compressed Record Card Format Library Format (Magnetic Tape) Header Record Format ••••
Library End-of-Tape Format •••
11-8 11-9
••••• 11-10
••• 11-10
xiii
Table 1-1 2-1 3-1 4-1 4-2 4-3 4-4 6-1 8-1 9-1 10-1 10-2 11-1
TABLES
Title
Assembler File Assignments
. . . . . . . . . . . . . . . .
Cataloger File Assignments ••
. . . . . . . . . . . . . . . .
DPEDIT File Assignments ••
DEBUG Prompts and Labels Debugger File Assignments ••••
Valid Use of Expressions. • • • • • • •••
Instructions that Break a Trace ••••••••
File Manager File Assignments LISED File Assignments •••
MACLISR File Assignments
1-4 2-14 3-9 4-8 4-12 4-29 4-59 6-4 8-3 9-4 MEDIA File Assignments ••••
MEDIA Option Definitions ••
10-3
• • 10-14
UPDATE File Assignments ••
. . . . . . . . . . . . . . . . .
11-4'"
)
Documentation Conventions
Notation conventions used in command syntax and message examples throughout this manual are described below.
lowercase letters
In command syntax, lowercase letters identify a generic element that must be replaced with a value. For example,
!ACTIVATE taskname
means replace taskname with the name of a task, e.g.,
!ACTIVATE DOCCONV
In messages, lowercase letters identify a variable element. For example,
**BREAK ** ON:taskname
means a break occurred on the specified task.
UPPERCASE LETTERS
In command syntax, uppercase letters specify a keyword must be entered as shown for input, and will be printed as shown in output. For example,
SAVE filename
means enter SAVE followed by a filename, e.g., SAVE DOCCONV
In messages, uppercase letters specify status or information. For example, taskname, taskno ABORTED
*YOUR TASK IS IN HOLD. ENTER CONTINUE TO RESUME IT Braces {
J
Elements placed one under the other inside- braces specify a required choice. You must enter one of the arguments from the specified group. For example,
} counter
I
1
startbytemeans enter the value for either counter or startbyte.
xv
Brackets [ ]
An element inside brackets is optional. For example, [CURRJ
means the term CURR is optional.
Items placed one under the other within brackets specify you may optionally enter one of the group of options or none at all. For example,
[ base name]- progname
means enter the base name or the program name or neither.
Items in brackets within encompassing brackets specify one item is required only when the other item is used. For example,
TRACE [lower address [ upper address]]
means both the lower address and the upper address are optional, and the lower address may be used alone. However, if the upper address is used, the lower address must also be used.
Commas between mUltiple brackets within an encompassing set of brackets are semi- optional; that is, they are not required unless subsequent elements are selected. For example,
M.DFCB fcb,lfc [, [a] ,[ b] , [c
J,
[d] , [ e]]could be coded as
M.DFCB FCB12,IN or
M.DFCB FCB12,IN"ERRAD or
M.DFCB FCB13,OUT"ERAD"PCK Horizontal Ellipsis
,
The horizontal ellipsis indicates the previous element may be repeated. For example, name , ••• ,name
(
Vertical EllipsisThe vertical ellipsis specifies commands, parameters, or instructions have been omitted. For example,
COLLECT 1
LIST
means one or more commands have been omitted between the COLLECT and LIST commands.
Nu~ and Special Characters
In a syntax statement, any number, symbol, or special character must be entered as shown. For example,
(value)
means enter the proper value enclosed in parentheses; e.g., (234).
Underscore
In syntax statements, underscoring specifies the letters, numbers or characters that may be typed by the user as an abbreviation. For example,
ACTIV A TE taskname
means spell out the command verb ACTIVATE or abbreviate it to ACTI.
RESET
means type either RESET or RST.
In examples, all terminal input is underscored; terminal output is not. For example, TSM >EDIT
means TSM was written to the terminal; EDIT is typed by the user.
Subscript Delta ...
A subscript delta specifies a required space. For example, EDT >STOIlSSPGM
means a space is required between 0 and T.
xvii/xviii
1. THE ASSEMBLER (ASSEMBLE)
The Macro Assembler (or Assembler) translates source code mnemonics into binary- equivalent machine instructions for the 32/7x CPU and interprets Assembler directives.
Assembler directives provide the ability to use symbolic addresses and storage areas, equate symbols, define references to external object modules, control listed output characteristics, etc.
Within source provided to the Assembler, the user can access system services. This is done either by setting up appropriate registers and using SVC or CALM instructions, and/or using macro calls which are expanded into assembly-level code by the Assembler.
The Assembler uses the MPX-32 System Macro Library (M.MPXMAC) for MPX-32 SVC- related services by default. The RTM System Macro Library (M.MACLlB) can also be assigned for assembly to access RTM CALM equivalent services.
On a CONCEPT/32 computer, a new SVC type 15 replaces CALM instructions. During reassembly of a program, the Assembler automatically converts CALM instructions to their equivalent SVC 15,X'nn' number if OPTION 20 is set.
Also, an address exception trap will be generated when a douljleword operation code is used with an incorrectly bounded operand; therefore coding changes will be required when a trap occurs.
1.1 General Description
In developing Assembly language source code, four separate, non-MPX-32 documents are key:
o The Macro Assembler Reference Manual, publication number 323-001220, which documents Assembler directives.
o The SYSTEMS 32/70 Computer Reference Manual, publication number 301-000140, which documents the SYSTEMS 32/70 CPU instruction set and mnemonics.
o The SYSTEMS 32/27 Single Slot Central Processing Unit, publication number 301-000400, which documents the SYSTEMS 32/27 CPU instruction set and mnemonics.
o The CONCEPT 32/87 Reference Manual, publication number 301-000810, which documents the SYSTEMS 32/87 CPU instruction set and mnemonics.
After a successful assembly, the user has an object module which can be output to a subroutine library file, output to a permanent file or device medium, or cataloged immediately into a task suitable for execution on MPX-32. Object modules can be linked together into a single task by assembling and cataloging them in the same job (an SGO file is the default output for assembly and default input for the Cataloger), by accessing the Subroutine Library during a separate Cataloger run, or by using $SELECT job control statements prior to cataloging (batch only).
1-1
The Assembler dynamically establishes botn a macro storage table and a symbol table in memory before it starts assembly. As a default option, all available memory is allocated for the symbol table and zero for the macro storage table. The ratio of available space allocated for macro storage can be changed. From 0 to 80 percent of available memory can be allocated to macro storage. The percentage is specified with an OPTION statement as described in Section 1.3.
1.2 Files and File Assignments
This section describes the input and output files used by the Assembler.
1.2.1 Source Code (PRE and SI)
Source code is assigned to logical file codes Ofc's) PRE and 51. Source is input first from PRE and then from 51. User program source should be assigned to 51 while source consisting of non-executable assembler directives (such as SET directives) can be assigned to PRE. The user can input source code from any device or file. The default aSSignment for SI is to SYC and for PRE is to NU (the null device).
1.2.2 Macro Libraries (MAC, MA2)
The System Macro Library provides a collection of macro definitions which can be used by source programs. The user can add macros to the system library or create his own macro library using the macro library Editor (MACLIBR) as described in Chapter 9 of this volume. Rules and conventions for using macros residing in a macro library are the same as for macros defined and used only within one program, and are described in the Macro Assembler Reference Manual. In general, a macro is accessed in a source program by using its name in the opcode/instruction field of a source statement and supplying any required or optional parameters in the operand field.
The System Macro Library, M.MPXMAC, 1s assigned by default for assembly to lfc MAC. A different macro library (e.g., M.MACLIB for RTM-compatible macros) can be assigned to MAC if desired.
The Assembler also supports another macro library, MA2. This library is searched by the Assembler for every name found in the opcode/instruction field. It is searched before the permanent symbol table and may be useful to override an existing opcode or Assembler directive.
1.2.3 Listing (LO)
The Assembler produces a listing that pairs hexadecimal representation of object code with the corresponding source statements. The listing lfc is LO. An SLO file is assigned to LO by default. Listings are further described in the Macro Assembler Reference
{
... --"1.2.4 Object Code (80 and GO)
Object code is output on the file or device assigned to lfc BO as well as to lfc GO. The default assignment for BO is to a system SBO file which is output to the system device defined as POD at SYSGEN or via the OPCOM SYSASSIGN command. The default assignment for lfc GO is to an SGO file. Other utilities such as LIBED and CATALOG will access an SGO file for the job automatically; however, SGO is temporary and will be lost if not used in the same job.
1.2..5 Compressed Source (CS)
The Assembler will optionally accept source program input or produce source output in compressed format. To output compressed source, assign a file or device to lfc CS.
Compressed source as input is specified by assigning the name of the file or device to lfc 51.
If both BO and CS are assigned to SBO files, the binary output is output prior to the compressed source output.
1.2.6 Temporary Files (UTI, UT2)
UT 1 is a temporary file used to hold the source text for processing on pass 2 of the Assembler. On pass 1, the Assembler writes the source text, along with the expanded macro text, to UTI and on pass 2 reads UTI.
UT2 is a temporary file used for the cross reference and symbol table during the assembly.
1-3
Table I-I
-
Assembler File ASStKnments+::" I
Previous
"put/Output Lollcal Assll"menti Processar How Specified
OeserlpUan File Code for Assembl, Asslenment for Assembly Comment
Source Code PRE Default: Permanent file built ASSICN statements If the user specifies
ASSIGN 1 usina EDIT or MEOlA an assignment to PRE,
PRE=MPXPRE source is read from PRE
untU an EOF Is readied,
Optlansa then source Is read from SI.
ASSIGNn . PRE: {lIIename }
devmnc
51 Defaultt Work file built usina EDT> BATCH
ASSKiN2 EDIT.
SI .. SYC Permanent file built EDT> M TCH Iob!lIe For further deta'lpdon
usi"l EDIT or MEDIA or see II Accessinc the
Assembler"'
Cards nBATCH
~'devmnc}
P,JobflleOther device medium Same route Ihown for The IUe or device CM
e.I., macnetlc tape, cards. contain compreaed IOW'CL
where file was copied from cards of a file via MEDIA.
Interactlvel,. See IOAccessi"l the Anembler"'
Opdonsl $SeLECT CM only be ....
ASSlGNn In batch.
St.
{filename}
devmncor
$SELECT
Maao Ubrar, MAC Defaultl Macro Ubrarles are Accessed autumatlcall, MACUB contains
ASSIGN. maintained or created for macro calls RTM ~ compatible macros.
MAC .. M.MPXMAC.,U via the MACUBR Included In the source RTMMAC contal .. RTM macroa
utllit,. code. for use with the RTM
-
VI I~
Input/Output DescrlptlClft Binary Obje'Ct Code
IoKleal File Code 80 and GO
Asslpments lor Assembly Defaults:
ASSIGN2 80 = 580 GO = SGO Options:
ASSI~Nn 80= lilename}
devnmc ASSIGNn GO= 1fi1ename}
tdevnmc
~
Table I-I (Cont'd) Assembler File Assilllnments
Previous Processor AssiKnment If a user file is assigned to 80 or GO, it must be pre-established via the FllEMGR utility.
How Specilled lor Assembly ASSIGN statements.
.~
Comment If an S80 file fills up, the Assembler automatically allocates an additional
.If
sectors
"00
cards). If other than S80, the utility aborts. S80 output {the delault assiKnment for lie 80) is routed to the device specified as the Punched Output Device (POD) during SYSGEN (see Volume 3) or reassigned via the OPCOM SYSASSIGN command. (See Volume I, Section If.)seo output Is routed to a temp file accumulated
'0(
a job so that the object code can be accessed by utilities such as L1BED and the CataloKer.
Thus, to enter the object module(s) directly in a library, run L1BED. To catalog the object module(s), immediately run the Cataloger.
Note that if you want to retain output and you are not going to catalog or enter the object module(s) into a library durinl the same job, make a permanent copy on the Ii Ie or device assigned either to 80 or GO.
Table I-I (Cont'd)
I Assembler File A55ignments
0'\
Previous
Input IOu lput Logical Assignments Processor How Specified
Description File Code for Anembly Assignment for Assembly Comment
Compressed CS No delault. Output is generated in
Output ASSIGNn compressed form. See
CS: {filename} the Macro Assembler
devnmc Reference Manual.
Listed Output- LO Default: NIA If an SLO file fills up
Source, Object. LO:; SLO (comes to £Of) the
errors, if any. Assembler allocates an
Options: extra 2000 lines. If the
allocation fails or if
LO:
~ename}
LO is a55ilned to othervnmc than SLO, the Assembler
aborts in thillituation.
Temporary UTI ASSIGN) Temporary file for
Source UTI=OC,IOO source text on pasa
z.
Temporary un ASSIGN)
Source Table UT2=DC,200,U
(
'i~
C'
(,--
1.3 Options
The options used by the Assembler include control options and macro percentage options. The default output control options are a listing, an object file, and a cross- reference. The additional options are the compressed source output and the object output to an SGO file. The macro percentage option is defaulted to 0 percent. Options 10-18 inclusive indicate a percentage of from 0-80. If more than one percentage is specified, the lowest percentage is used.
Option Description
1 No listed Output (Source Listing) 2 No Punched Output (Binary Object)
3 List Internally Generated Symbols with Cross Reference 4 No Symbol Cross-Reference
5 Binary Output Directed to SGO File 7 Compressed Source Output
8 SI Not Blocked
9 LO, BO, and CS Not Blocked 10 Allot 0 Percent to Macro Storage 11 Allot 10 Percent to Macro Storage 12 Allot 20 Percent to Macro Storage 13 Allot 30 Percent to Macro Storage 14 Allot 40 Percent to Macro Storage 15 Allot 50 Percent to Macro Storage 16 Allot 60 Percent to Macro Storage 17 Allot 70 Percent to Macro Storage 18 Allot 80 Percent to Macro Storage
19 Outputs Symbolic Information to the Cataloger for use by the Symbolic Debugger
20 Generates Replacement 15,X'nn' Instructions for Call Monitor Instructions
1-7
1.4 Accessing the Assembler
To access the Assembler as part of a batch job, create a job file using the EnITOR, punch cards, or other media. The job file can be read to SYC and the job activated in several ways:
from the OPCOM consol~:
" <Attention>"
??BATCH {F,jObfile
t
D,devrnnc)
from the OPCOM program:
TSM>OPCOM
??BATCH {F,jObfile}
D,devmnc
from the EDITOR:
TSM>~
EDT>BA TCH . [jobfile]
.
If the jobfUe is the current EDITOR work file, issue just the BATCH command.
To activate the Assembler and run online, use the TSM ASSIGN commands to make Assembler assignments equivalent to those preceding the EXECUTE ASSEMBLE command on a job file, then proceed to issue Assembler directives. (SELECT and OBJECT statements are not available when running the Assembler online.)
TSM>ASSEMBLE ASS>
At the Assembler prompt, ent~r Assembler directives and source code.
1 • .5 Assembler Directives
See the Macro Assembler Reference Manual.
.~,
i
(
c
1.6 Listings
The Assembler produces a listing of source code, object code equivalents, symbol cross references, and error diagnostics.
Typical Assembler output is shown and described in Chapter 7 of the Macro Assembler Reference Manual.
1.7 Errors and Aborts
Errors are detected during both passes of Assembler processing. They are described in Appendix H of the Macro Assembler Reference Manual. Abort codes are described in Appendix C of this volume.
1.7.1 Aborts
When LO is assigned to an SLO file and end-of-file is detected, an additional allocation of 2000 lines will be attempted. If the attempt is unsuccessful or if LO is not assigned to an SLO file, the assembly will be aborted with abort code AS03.
When BO is assigned to an SBO file and end-of-file is detected, an additional allocation of 500 cards ( 84 sectors) will be attempted. If the attempt is unsuccessful or BO is not assigned to an SBO file, the assembly will be aborted with abort code AS02.
A macro library is not required by the Assembler, but if one is provided, it must be in the proper format if an attempt is made to read it. If the format is invalid, the assembly is aborted. If a macro prototype from a macro library exceeds the remaining size of the macro storage table, the following message is printed on the listing just preceding the macro call, and the macro call is flagged by the Assembler:
THE FOLLOWING MACRO CAUSED A TABLE OVERFLOW
In some cases, a cross-reference is not generated because there is not enough memory available to sort the cross-reference information. If this occurs, the following message will be printed on LO:
**XREF COULD NOT BE PERFORMED**
There is not enough memory to store required macros and the symbol table. See Sections 1.1 and 1.3.
If the number of symbols in a program exceeds the maximum number of symbols that the symbol table can hold, the following message is printed on the file or device assigned to LO:
SYMBOL TABLE OVERFLOW
1-9
If the macro table size is exceeded due to too many bytes of in-line macros, in-line FORM skeletons, repeated code, or macro-call argument data, the following message is printed on the file or device assigned to to:
MACRO TABtE OVERFLOW
1.8 Examples
Example 1 - In· the sequence, the user assembles source code from a file name SJ.MEDIA, outputs object code to a file name OJ.MEDIA, then catalogs the object into a load module file named MEDIA. SLO output for the job is directed to a file named MOUT.
$JOB SJ.MEDIA OWNER SLOF=MOUT
$OPTION 17 (Allocates 7096 of Assembler address
$ALLOCATE 16000
$ASStGN3 UTl=DC,400
$ASSIGN3 UT2=DC,800,U
$ASSIGNI MAC=M.MACLIB"U
$Al BO=OJ.MEDIA
$Al SI=SJ.MEDIA
$EXECUTE ASSEMBLE
$Al SGO=OJ.MEDIA
$EXECUTE CATALOG FILES 64
BUFFERS 16
ENVIRONMENT MUL TICOPY ASSIGN2 *IN =SYC
ASSIGN2 *OT=SLO,.500 OPTION PROMPT
CATALOG MEDIA
$EOJ
$$
space for macros)
(Allocates 16,000 bytes beyond minimum Assembler requirement)
(Temporary file for Assembly) (l'emporary file for Assembly)
(Uses R TM-compatible macro library)
(Object code cataloging)
is now assigned for
(Up to 64 files can be allocated dynamically)
(Up to 16 buffers can be allocated dynamically)
(More than one copy of MEDIA can be active at the same time)
(Default assignment for MEDIA) (Default assignment for MEDIA)
(Provides MED prompt automatically in interactive environment. User does not have to use the TSM OPTION PROMPT command)
(
2. THE CATALOGER (CATALOG)
The Cataloger produces load modules that are ready to activate in one of three task operating environments: real time, interactive, or batch.
2.1 General Description
To produce the desired load module, the user creates a job stream of job control commands and Cataloger directives. A careful distinction must be made between job control commands for the job that executes the Cataloger, and directives which will reside in the cataloged load module.
The Cataloger creates a load module which contains the transfer address of the task, a Resource Requirement Summary Table, and relocation matrices, in addition to the program code.
The load module resides in a permanent system file of the same name specified in the CATALOG directive.
Assignment statements occurring between the $EXECUTE CATALOG command and the CATALOG directive cause the Cataloger to create entries in the Resource Requirement Summary Table (see the MPX-32 Technical Manual, Chapter 2) located in the load module file (see the MPX-32 Technical Manual, Chapter 6). Directives and assignment statements to the Cataloger are coded without the dollar sign ($). All directives must begin in column one of their respective line.
A sample job stream follows:
$JOB TESTCAT DALE}
$ALLOCATE 28000
$EXECUTE CATALOG
A2INP=SYC
t
A2 OUT =SLO, 100 ALLOC ATE 18000 OPTION PROMPT CAT ALOG TEST I
$EOJ
$$
Job Control Commands
Directives which will be cataloged in load module TEST!.
A simple load module is illustrated in Figure 2-1.
2-1
N I IV
;]
OQ C
..,
tl N I
() I» r+
I» 0- t!9.
:J OQ
I»
r'
g
a.
!: o a. c ii"
ASSEMBLER OR COMPILER
RUN (EXECUTE
ASSEMBLE)
----.
LOAD IMODULE INFORMATION DEFINED
OBJECT MODULE
. - .
...
1/////////////////1 1/////////////////1 11///////11///////1.
-
'1//////1///1///1/1 '111///11/1/1////11
OBJECT CODE
· . . . .
" ..
.
.. ..• II .. • ..
· . . . .
-
· . . . .
• • .. II •
LOAD MODULE ON DISC READY TO ACTIVATE ON MPX·32
DEFAULT RESOURCE REOUIREMENTS DEFINED
REL.OCATION MATRIX
C/
',-'2.1.1 Load Module Information
The Cataloger ENVIRONMENT and CATALOG directives establish the following special characteristics for a task:
Residency - a task defined as resident either remains in physical memory unless it aborts (R TM-compatible) or remains resident until it exits or aborts (MPX). In either case, it is not a candidate for swap to disc. Default is nonresident, i.e., a task is swappable.
The task needs to execute in a special class of physical memory. E=requires Class E memory; must execute within the first 128KWof memory. H=requires high-speed memory; must execute in H or E. S=the task can execute in slow memory or in any other class of memory .. that is available; this is the default definition.
Multicopying - the task can be active concurrently in several logical address spaces. The entire task is copied to physical memory each time it is activated.
Sectioned Sharing - the task can be active concurrently in several logical address spaces. The CSECT area of the task is copied into physical memory once and a new DSECT area is established in physical memory each time the task is activated. DSECT areas are deallocated as sharers exit. CSECT remains allocated until all sharers exit.
No Sharing - the task is unique. Only one copy of the load module can be active in one logical address space at a time (the default).
Privilege - any task which accesses a privileged system service must be cataloged as privileged in order for the service to be executed. A privileged task is allowed to write into any area of memory in its logical address space, including the system area, and to execute the 32/75 privileged instruction set. Default is unprivileged.
Base Priority - the priority (1-64) at which the task is executed if activated in a real time environment (by the OPCOM ACTIVATE or ESTABLISH command, another task, a timer, or an interrupt). If activated via TSM or in the batchstream, this priority will be overridden.
Unless defined otherwise with the ENVIRONMENT directive, a task is:
nonresident, unique,
executable in any memory class available (S, H, or E).
2-3
If not specified with the CATALOG directive, the base priority of a task is 60 and its status is unprivileged.
(For further description of multicopying and sharing, see Section 2.1.3.)
The information on residency, priority, etc., is output by the Cataloger at the beginning of the main load module for a task so that it is available for the MPX-32 allocator and execution scheduler immediately upon activation.
